Wikibooks:Requests for deletion

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>Wikibooks</sitename>
    <dbname>enwikibooks</dbname>
    <base>https://en.wikibooks.org/wiki/Main_Page</base>
    <generator>MediaWiki 1.47.0-wmf.18</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">Wikibooks</namespace>
      <namespace key="5" case="first-letter">Wikibooks talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
      <namespace key="102" case="first-letter">Cookbook</namespace>
      <namespace key="103" case="first-letter">Cookbook talk</namespace>
      <namespace key="108" case="first-letter">Transwiki</namespace>
      <namespace key="109" case="first-letter">Transwiki talk</namespace>
      <namespace key="110" case="first-letter">Wikijunior</namespace>
      <namespace key="111" case="first-letter">Wikijunior talk</namespace>
      <namespace key="112" case="first-letter">Subject</namespace>
      <namespace key="113" case="first-letter">Subject talk</namespace>
      <namespace key="710" case="first-letter">TimedText</namespace>
      <namespace key="711" case="first-letter">TimedText talk</namespace>
      <namespace key="828" case="first-letter">Module</namespace>
      <namespace key="829" case="first-letter">Module talk</namespace>
      <namespace key="1728" case="first-letter">Event</namespace>
      <namespace key="1729" case="first-letter">Event talk</namespace>
    </namespaces>
  </siteinfo>
  <page>
    <title>Wikibooks:Requests for deletion</title>
    <ns>4</ns>
    <id>385</id>
    <revision>
      <id>4668985</id>
      <parentid>4666899</parentid>
      <timestamp>2026-09-05T18:48:29Z</timestamp>
      <contributor>
        <username>Omphalographer</username>
        <id>3427146</id>
      </contributor>
      <comment>/* Suicide */ Reply</comment>
      <origin>4668985</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="44928" sha1="hl21ps2214xeiiep5yjxru3yc6reixs" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original)
* [[Òla, Ionatà!|Audià]]
* [[Holo, Jonathan!|Cristianés]]
* [[Terve, Jonathan!|Ekumenski]]
* [[Hej, Jonathan! (Germanisch)|Germanisch]]
* [[Salom, Jonatan!|Globasa]]
* [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]])
* [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]])
* [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]])
* [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]])
* [[Salut, Jonathan! (Interocidental)|Interocidental]]
* [[Bune Ğonatan!|Lingaust]]
* [[Oila, Jonatan!|Lingue Simple]]
* [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]])
* [[Sin Chao, Jonathan!|Masa Tang]]
* [[Salut, ionatano!|Meteza]]
* [[Salu, Jon!|Mini]]
* [[Hay, Jonathan!|Mirad]]
* [[Hai, Jon!|Monav]]
* [[Sesan Jon!|Monkel]]
* [[Salam, Jonathan!|Mundeze]]
* [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]])
* [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]])
* [[Hej, Jonathan!|Nordien]]
* [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]])
* [[Salute, Jonathan! (Novlingue)|Novlingue]]
* [[Alo, Jonathan!|Numo]]
* [[Hela, Jonathan!|Proyo]]
* [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]])
* [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]])
* [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]])
* [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]])
&lt;/div&gt;

There are a couple of issues here:

# Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks.
# All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself.
# Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them.

While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC)

: I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC)

: Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15.
:If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC)

: Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine
: How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC)

:: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC)

::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias.
::: So the idea is the following:
:::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest.
:::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua).
:::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere).
:::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo.
::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out.
::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added.  — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC)

:::: Thanks for taking the time to consider this! Here are my responses/questions:
::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks.
::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time.
::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC)

::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
::::: [[Salute, Jonathan!/Capitul 1 - with notes]]
::::: [[Salute, Jonathan!/Capitul 2 - with notes]]
::::: [[Salute, Jonathan!/Capitul 3 - with notes]]
::::: [[Salute, Jonathan!/Capitul 4 - with notes]]
::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC)
:::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC)

::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained.
::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere.
::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC)

:::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC)

::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content.
::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC)

: {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük.
: Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know):
:* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/]
:* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/]
: {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know.
: In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know.
: I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC)

:: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC)

::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC)

:::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC)

{{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC)

: I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC)

:: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC)

== [[International Baccalaureate]] ==

Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC)
: Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC)
::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC)

== [[Character List for Baxter&amp;Sagart]] ==

Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC)

:Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC)

:These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC)
::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC)
:::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. 
:::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC)
::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC)
::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. 
::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work.  [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC)
:Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:32, 3 November 2024 (UTC)

== [[Suomen kieli käyttöön]] ==

Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC)

:I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC)
::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for &quot;tethering&quot; a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC)

:I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC)
::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC)
:::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest.
:::Any chance we can get a separate namespace (maybe &quot;Archive:&quot;) set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC)
::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC)

== Algebra/Chapter 10/Symmetric Polynomials ==

I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC)

:'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC)
:{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC)
::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC)
== [[Puredyne]] ==

Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC)

:I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC)

== [[Template:Qr-twwp]] ==
This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC)

== [[Ghouls of the Miskatonic]] ==

I don't think that a plot summary of a book is in-scope here. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:43, 20 August 2025 (UTC)

:{{vd}} - at least, not a summary of ''this'' book. A summary and/or study guide to a notable work of literature might be in scope, but this is certainly not one. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:23, 25 August 2025 (UTC)
::Hi. I am the creator of the pages of this book. If I understand correctly, it has to be a summary of a notable work of literature? So what exactly is defined as such? I only started this as I thought it would be fun, interesting and encouraging to others who read the Arkham Horror novels, and I thought it was permitted as I've seen other summaries of books on wikibooks. [[User:Dayne90|Dayne90]] ([[User talk:Dayne90|discuss]] • [[Special:Contributions/Dayne90|contribs]]) 13:27, 26 August 2025 (UTC)
:::Your problem is it is just the plot... it needs to include an educational textual analysis to be in scope [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:47, 28 August 2025 (UTC)
::::And ideally it'd be a text which has ''already'' been the subject of literary analysis, such that the analysis on Wikibooks isn't original research. A notable work of literature like ''Frankenstein'' or ''Moby-Dick'' would easily meet that requirement; a tie-in novel for a tabletop RPG probably does not. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:08, 29 August 2025 (UTC)

== [[Objective Projection: Why the Brain Never Forgets Some Stories]] ==

Undisclosed AI-generated content. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:13, 9 May 2026 (UTC)

:&lt;nowiki&gt;'''Keep'''&lt;/nowiki&gt; — Comment from page author/subject expert.
:I am Levent Bulut, the originator of the &lt;nowiki&gt;''&lt;/nowiki&gt;Objective Projection&lt;nowiki&gt;''&lt;/nowiki&gt; methodology described in this book (ORCID: 0009-0007-7500-2261, Wikidata: Q138048287). I want to address the AI-generated content concern directly and transparently.
:&lt;nowiki&gt;'''&lt;/nowiki&gt;On the content itself:&lt;nowiki&gt;'''&lt;/nowiki&gt; The methodology, theoretical framework (the six-variable operator E(r) = projS(M, T, V, Δ, Ω, Ng), the Six Golden Rules, the Six-Layer Framework), and all original arguments are my own intellectual work, developed and published independently. This is documented through:
:* 26 DOI-registered academic publications on Zenodo (search: &quot;Levent Bulut Objective Projection&quot;)
:* A peer-reviewed submission currently under review at &lt;nowiki&gt;''&lt;/nowiki&gt;Digital Humanities Quarterly&lt;nowiki&gt;''&lt;/nowiki&gt;
:* Parallel Turkish-language Wikibook and Wikiversity pages on the same methodology
:* An open-source SFT dataset on Hugging Face (leventbulut/objective-projection)
:&lt;nowiki&gt;'''&lt;/nowiki&gt;On AI assistance:&lt;nowiki&gt;'''&lt;/nowiki&gt; I used AI tools (Claude) for English translation polish and copy-editing from my Turkish source materials — the same way a non-native English-speaking academic would use a human translator or editor. The &lt;nowiki&gt;''&lt;/nowiki&gt;ideas, structure, terminology, citations, and arguments&lt;nowiki&gt;''&lt;/nowiki&gt; are entirely my own and pre-date the Wikibooks version, traceable through Zenodo DOI timestamps starting in 2025.
:&lt;nowiki&gt;'''&lt;/nowiki&gt;Proposed remedy instead of deletion:&lt;nowiki&gt;'''&lt;/nowiki&gt; I am happy to:
:# Add a clear AI-assistance disclosure to the book's preface, per Wikibooks transparency norms
:# Add inline citations to the underlying DOI-registered publications for every major claim
:# Link to the parallel Turkish version and academic record
:This would address the &lt;nowiki&gt;''&lt;/nowiki&gt;undisclosed&lt;nowiki&gt;''&lt;/nowiki&gt; part of the concern (which is the actionable policy issue) while preserving content that is original academic work by an identifiable author with a published track record. Deletion of original scholarship because translation assistance was used would set a concerning precedent for non-native English contributors.
:&lt;nowiki&gt;I request a few days to add the disclosure and citations before any deletion action. ~~~~&lt;/nowiki&gt; [[Special:Contributions/&amp;#126;2026-28847-60|&amp;#126;2026-28847-60]] ([[User talk:&amp;#126;2026-28847-60|talk]]) 18:46, 13 May 2026 (UTC)
::Administrative assistance needed: Automated filters blocking structural improvements and disclosures
::'''Request for Help''' — I am Levent Bulut, the author of this book. I have already provided my AI disclosure and academic credentials (ORCID, DOI list) here in this discussion.
::I am trying to update the book to comply with Wikibooks standards by:
::Adding a formal '''AI assistance disclosure''' at the top of the page.
::Restructuring the content into an '''instructional textbook format''' (adding Learning Objectives).
::Converting plain text formulas into '''LaTeX''' ( format).
::Updating references to include full academic '''DOI''' records.
::However, the automated filter is blocking all my attempts:
::If I try to replace the content with the improved version, it triggers the '''&quot;large amount of content removal&quot;''' filter.
::If I try to add specific academic links, it triggers the '''&quot;automated link/spam&quot;''' filter.
::I am essentially trapped by the filters while trying to improve the book and follow transparency norms. Could an administrator please either whitelist my account or manually apply the improved version of the text? I am ready to provide the full MediaWiki code here if requested. My intent is purely constructive and academic. [[Special:Contributions/&amp;#126;2026-28847-60|&amp;#126;2026-28847-60]] ([[User talk:&amp;#126;2026-28847-60|talk]]) 19:15, 13 May 2026 (UTC)
::: Hi, @[[User:~2026-28847-60|~2026-28847-60]]. Your account was incorrectly locked by a steward. It is now currently unlocked. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:44, 15 May 2026 (UTC)
:::: Pinging @[[User:Projection Architect|Projection Architect]], who was previously LeventBulut. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:51, 4 July 2026 (UTC)
::Please review [[Wikibooks:Artificial intelligence]]. It states unequivocally that {{tq|LLMs may not be used to generate or summarize material and ideas at Wikibooks}}, and that {{tq|translations made by LLMs are not allowed on Wikibooks}}. The fact that you did not disclose your usage of AI is part of the problem, but disclosing it does not make it allowable either.
::More broadly, based on what you've said above, the content of this book is a reflection of your personal theories on writing. This is essentially [[Wikibooks:Original research]] and is not permitted. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:36, 13 May 2026 (UTC)

== [[Suicide]] ==

I realize this book has been nominated for deletion before ([[Wikibooks:Requests for deletion/Suicide|1]], [[Wikibooks:Requests for deletion/Suicide (2)|2]], [[Wikibooks:Requests for deletion/Suicide/Suffocation|3]]), but it's been over ten years since the last nomination. The project's position on what material is in its educational scope has shifted, as have some of the facts on the ground.

* The chartered purpose of Wikibooks is to produce &quot;open-content textbooks&quot; (cf. [[Wikibooks:What is Wikibooks?]]) which are suitable for use in an instructional environment. Providing educational information about suicide in the context of psychiatry could certainly be in scope, as psychiatry is an educational topic; however, instructional material on how to commit suicide is not an educational topic, and should not be considered in scope.
* This book is, and has always been, primarily intended as an instructional work guiding users on how to commit suicide. It provides effectively no meaningful analytical content ''about'' suicide as a topic. Most of the original content in the book was imported from an early-2000s wiki associated with the &lt;code&gt;alt.suicide.holiday&lt;/code&gt; Usenet group, the &quot;ASH wiki&quot;, which was specifically and unequivocally dedicated to describing and recommending methods by which readers could commit suicide, and this has carried through to the current version of the book.
* Most of the content in the book was removed in 2020 (by redirecting it to the book's main page, e.g. [[Special:Diff/3660495]]) over concerns that it was created by a WMF-banned user ([[User:Leucosticte]]), and because it was likely in violation of the ASH wiki's (unclear) copyright. These changes removed most of the content of the book; much of what remains is image gallery pages like [[Suicide/Blades]] which have no educational value.

Suicide is a sensitive topic; if it is covered by a textbook, it should be covered tastefully and with an aim to educate. This book is largely the opposite of that. Having it here is doing more harm than good.

If this book is deleted, the following related pages should be deleted as well:
* [[Template:Suicide methods]]
* [[Template:Infobox suicide method]] (currently unused)
* [[User:Leucosticte/About ASH]] - from the ASH wiki, as mentioned above
* [[User:Leucosticte/Frequently Asked Questions]] - also from the ASH wiki
[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:41, 21 July 2026 (UTC)
: {{keep|weak keep}} a)&amp;nbsp;Age is no argument. There are many stale underdeveloped books I would rather delete than keeping around. b)&amp;nbsp;The book’s topic is exceptionally difficult to write about. ''This'' impedes collaborative authoring. c)&amp;nbsp;The book does not really explain ''how'' to commit suicide (like a step‐by‐step guide), neither is it the book’s learning objective. d)&amp;nbsp;Even if ''you construed'' the chapter summarizing various suicide methods ''as instructions'', instructional material on how to commit suicide ''is'' an educational topic. In most ''present‐day societies'' it is not ''ethical'' to teach students how to commit suicide, though. e)&amp;nbsp;Therefore the correct path is to first alter the [[WB:WIW#Wikibooks includes instructional texts|project scope]] to censor books on ethical grounds ''and then'' nominate the book for censorship. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 04:50, 28 July 2026 (UTC)
::Re. c: most of the explicit directions were edited out in 2020, as noted in my nomination, but are still visible in page history. For a couple of explicit examples, see e.g. [[Special:Permalink/3318613]] or [[Special:Permalink/3654645]]. Providing specific instructions was the original intent of this book, and it has never escaped that legacy. If someone were interested in writing a book ''about'' the phenomenon of suicide, they would be better off starting afresh. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:26, 28 July 2026 (UTC)
*'''Delete all'''. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:17, 28 July 2026 (UTC)
* '''Delete all''' per the nomination above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:17, 30 July 2026 (UTC)
* '''Keep''' with caution. Rename to &quot;suicide prevention&quot;?--[[User:TunnelESON|TunnelESON]] ([[User talk:TunnelESON|discuss]] • [[Special:Contributions/TunnelESON|contribs]]) 04:03, 2 September 2026 (UTC)
*:Re. the rename: absolutely not. There is no content in the book about suicide prevention. If you are interested in writing a book on that topic, please start a new one. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 5 September 2026 (UTC)

== [[User:PETER A. SAUL/You Become What You Think: Transform Your Life]] ==
Overall reads like a violation of [[WB:SOAP]]. Mass addition of pages. Bold claims with no reputable sources/support. See e.g. [[Peter A. Saul: Personal Development and Mindset Anthology/You Become What You Think/Chapter 9|here]]. Markdown errors that suggest LLM use (e.g. [[Peter A. Saul: Personal Development and Mindset Anthology/You Become What You Think/Chapter 16|here]], [[Peter A. Saul: Personal Development and Mindset Anthology/You Become What You Think/Chapter 17|here]], etc. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:21, 5 August 2026 (UTC)

:I'll also note a significant amount of self-promo. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:32, 5 August 2026 (UTC)
:'''Speedy delete''' Obviously inappropriate. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 17:17, 5 August 2026 (UTC)
::{{done}}. I was on the fence for speedy, but since another admin agrees, I went ahead and deleted. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:38, 5 August 2026 (UTC)

== [[User:PETER A. SAUL/Why 95 Percent of Your Life Is a Lie: How to Control Your Mind]] ==
Same reasons as RFD for other pages by this editor. Violation of [[WB:SOAP]], no support for extreme claims, potential LLM use, self-promo. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:28, 5 August 2026 (UTC)

:'''Speedy delete''' Obviously inappropriate. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 17:17, 5 August 2026 (UTC)
::{{done}}. As with other contributions. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:38, 5 August 2026 (UTC)</text>
      <sha1>hl21ps2214xeiiep5yjxru3yc6reixs</sha1>
    </revision>
  </page>
  <page>
    <title>World History/World Religions</title>
    <ns>0</ns>
    <id>497</id>
    <revision>
      <id>4669092</id>
      <parentid>4445174</parentid>
      <timestamp>2026-09-06T10:23:53Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <minor />
      <comment>typo</comment>
      <origin>4669092</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="10746" sha1="tjk90f1z27sarh1vvcj96j494l3xnkk" xml:space="preserve">{{WHP - page top 1}}
'''''&lt;u&gt;This page is for an elementary explanation of the origins and nature of the religions. It is not meant to be an in depth study by any means.&lt;/u&gt;'''''

==Animism==
Animism (from Latin animus, -i &quot;soul, life&quot;) is the worldview that non-human entities (animals, plants, and inanimate objects or phenomena), possess a spiritual essence.

==Baha'i Faith==
[[File:Bahai star.svg|thumb|The nine pointed star]]
The ''Bahá'í Faith'' is the youngest of the world's independent religions. Its founder, [[w:Baha'u'llah|Bahá'u'lláh]] (1817–1892), is regarded by Bahá'ís as the most recent in the line of [[w:Manifestations of God|Messengers of God]] that stretches back beyond recorded time and that includes Abraham, Moses, Buddha, Zoroaster, Christ and Muhammad.

The central theme of Bahá'u'lláh's message is that humanity is one single race and that the day has come for its unification in one global society. God, Bahá'u'lláh said, has set in motion historical forces that are breaking down traditional barriers of race, class, creed, and nation and that will, in time, give birth to a universal civilization. The principal challenge facing the peoples of the earth is to accept the fact of their oneness and to assist the processes of unification. [http://www.bahai.org/faq/facts/bahai_faith]

Wikipedia article: [[w:Baha'i Faith|Bahá'í Faith]]

==Buddhism==
[[File:Dharma Wheel (2).svg|thumb|Dharmachakra, a significant symbol in many religions, including Buddhism.]]
Buddhism is a religion based largely around the teachings of the Siddhārtha Gautama (although his exact status is still controversial and changes by sect) and is now the central religion of most of Southeast Asia, Mongolia, Sri Lanka, and parts of China, Nepal, India, and a small part of Russia. It is also a major religion in Korea and Japan and has a growing influence in the west.

[[File:Four Scenes from the Life of the Buddha - Enlightenment - Kushan dynasty, late 2nd to early 3rd century AD, Gandhara, schist - Freer Gallery of Art - DSC05124.JPG|thumb|A depiction of scenes from the Life of Buddha.]]
Gautama was born in ancient Nepal around the 6th century BC, son of a King and relieved of all tasks. One day, while being brought around by his charioteer, he saw the four passing sights (an old man, a sickly man, a decaying corpse, and a holy man), which brought him to the realization that birth, old age, sickness, and death happen to all people over countless lives. He left his wife, children, rank, and his entire life to solve that problem.
Gautama tried everything to achieve inner peace (he nearly killed himself numerous times) but found nothing that worked. He then tried sitting peacefully under a Bohdi tree and meditating. This proved very successful, and he soon achieved the inner peace he wanted. He then traveled the lands, preaching his new faith. (Postscript-Buddhism is largely based on Jainism, and shares many beliefs with Jainism.)

Within the context of postclassical China, dominations such as pure land and Zen Buddhism appealed to both aristocratic elites and the mass peasantry. A commonality of religion in the global context: the induction of fervent belief system in the presence of societal corruption and lack of intellectual synthesis.

Modern Buddhism still follows the ideals of Gautama-peace, kindness to man, and love of nature (including vegetarianism). There are three modern sects of Buddhism - Theravada, Mahāyāna, and Vajrayāna (practiced in southeast Asia, East Asia, and scattered parts of Asia, respectively).

For information on the sects of Buddhism, or some tenets of Buddhism, go to the Wikipedia articles on:

[[w:Buddhism|Buddhism]]

[[w:Theravada|Theravada]]

[[w:Mahayana|Mahayana]]

[[w:Vajrayana|Vajrayana]]

==Christianity==
[[File:Christian cross.svg|thumb|100px|A cross, the symbol of Christianity.]]

{{Clear}}The story of Jesus and the Gospel of salvation is central to the Christian faith. It begins with the life and teachings of Jesus Christ, who is believed by Christians to be the Son of God and the Savior of humanity.

=== 1. The Birth of Jesus ===
Jesus was born in Bethlehem around 2,000 years ago to Mary and Joseph. His birth is considered a miraculous event, as Christians believe Mary was a virgin when she conceived Jesus through the Holy Spirit. His birth is seen as the fulfillment of ancient prophecies that a Messiah (Savior) would come to deliver the people.

=== 2. The Life and Ministry of Jesus ===
Jesus grew up in Nazareth and began his public ministry around the age of 30. He taught about love, forgiveness, repentance, and the coming of the Kingdom of God. He performed many miracles, such as healing the sick, raising the dead, and feeding the hungry, all of which demonstrated his divine authority. His teachings emphasized love for God and neighbor, and he often challenged the religious leaders of his time, calling for a deeper, more sincere relationship with God.

=== 3. The Crucifixion and Atonement ===
Jesus' teachings and actions eventually led to conflict with the religious authorities and the Roman authorities, who saw him as a threat. He was arrested, tried, and sentenced to death by crucifixion. Christians believe that Jesus' death on the cross was not just a tragic event but a sacrifice for the sins of humanity. This is known as the &quot;atonement,&quot; where Jesus, who lived a sinless life, took upon himself the punishment for the sins of the world.

Through his death, Christians believe that Jesus reconciled humanity with God, offering forgiveness for sins and the opportunity for eternal life. His crucifixion is seen as a fulfillment of Old Testament prophecies that a Savior would suffer for the sins of the people.

=== 4. The Resurrection ===
Three days after Jesus' death, Christians believe that he rose from the dead—an event known as the Resurrection. This miraculous event is seen as proof of his divine nature and the power of God over death. The Resurrection also signifies the hope of eternal life for all who believe in him.

=== 5. The Ascension and the Gospel of Salvation ===
After appearing to his disciples for forty days following his Resurrection, Jesus ascended into heaven, promising to send the Holy Spirit to guide and empower his followers. His final words to his disciples were to go and make disciples of all nations, baptizing them and teaching them to obey his commandments (Matthew 28:18-20).

The '''Gospel of salvation''' refers to the &quot;good news&quot; that through Jesus’ life, death, and resurrection, salvation is available to all people. Salvation means being forgiven for sins and being reconciled to God, which is a free gift offered to everyone, regardless of background or past mistakes. Christians believe that faith in Jesus Christ as Lord and Savior is the way to receive this salvation (John 14:6, Ephesians 2:8-9).

=== 6. The Promise of Eternal Life ===
Christians believe that by trusting in Jesus and accepting his sacrifice, they can receive eternal life with God. This hope is rooted in the belief that Jesus will return one day to judge the living and the dead, and that those who have faith in him will live with God forever in a restored, perfect world.

In summary, the story of Jesus and the Gospel of salvation is about God's love for humanity, demonstrated through the life, death, and resurrection of Jesus Christ. It is the message that salvation—freedom from sin and eternal life—is available to all through faith in Jesus Christ.

==Confucianism==
[[File:木鐸 --- Confucian wooden-clapper bell.svg|thumb|100px|Symbol of a wooden clapper bell, associated with Confucianism.]]
Wikipedia article on [[w:Confucianism|Confucianism]]
{{Clear}}

==Hinduism==
[[File:Aum Om navy blue circle coral.svg|thumb|''Om'', a symbol of Hinduism]]
''Hinduism'' is a term coined to designate the traditional socio-religious systems of the people of India. This term does not appear in any of the sacred literature of India. Hindus refer to their religion as ''Sanatana Dharma'' which loosely translated means “The Eternal Path”. ''Sanatana'' means ''eternal'', ''perpetual'' or ''sustained''. ''Dharma'' means any method by which one sees reality for what it is, and that by which one is drawn closer to the Absolute Truth and Ultimate Reality — it is the ''Philosophia Perenis''.

In a context of world history, the Hindu emphasis placed upon social divisions as ample means for a productive society led to the highly stratified caste system in which birth and socio-economic position determined semi-permanent placement. 

There are two world religions which have formed the cultural and ethical basis of the world as we know it. Both have an unbroken history going back thousands of years. Judaism with a 5000 year old tradition is the mother of the western civilization through its offshoot Christianity. Hinduism is the older of the two with a literature going back to the beginning of recorded history. 

Hindu civilisation originated in the Gangetic and Indus valleys and from there spread out over the entire region of southeast Asia. Its offshoot — Buddhism, shaped and molded the civilizations of Japan, China, Tibet and the rest of Asia. There is evidence to suggest that the Ancient pre-Biblical kingdom of the Mittani in Asia minor was ruled by Kings with Hindu/Sanskrit names. The Hittites were an Indo-European people and according to some sources are said to have originated in the Gangetic Basin of India. Hindu philosophy/theology influenced the ancient Greeks since the time Alexander the Great conquered parts of north India. A remarkable similarity has also been demonstrated between the religion and mythology of the ancient Scandinavian people and that of the people of India. 

The ancient civilizations such as the Roman, Greek, Egyptian, Sumerian, Babylonian, Mayan, Aztec, and Inca have all passed away. Even the Jewish culture has undergone many radical changes since its inception 5000 years ago – yet the Hindu civilisation continues as a vibrant and living vector, and has remained virtually unchanged for over 6000 years. Today, Hindu communities are to be found in almost every country on earth.

[[w:Hinduism|Hinduism]]

==Islam==
[http://en.wikipedia.org/wiki/Islam Islam]

==Jainism==
[http://en.wikipedia.org/wiki/Jainism Jainism]

==Judaism==
[http://en.wikipedia.org/wiki/Judaism Judaism]

==Sikhism==
[http://en.wikipedia.org/wiki/Sikhism Sikhism]

==Shinto==
[http://en.wikipedia.org/wiki/Shinto Shinto]

==Taoism==
[http://en.wikipedia.org/wiki/Taoism Taoism/Daoism]

==Marxism-Leninism==
[http://en.wikipedia.org/wiki/Marxism]

==Legalism==
==Other notable religions==
==New Age Alternative Religions==

{{BookCat}}</text>
      <sha1>tjk90f1z27sarh1vvcj96j494l3xnkk</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/Developer/Docs</title>
    <ns>0</ns>
    <id>13107</id>
    <revision>
      <id>4668959</id>
      <parentid>4666501</parentid>
      <timestamp>2026-09-05T17:26:35Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668959</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="125558" sha1="9qd2mfbp9o8lt8w558ody2lmjzkem4q" xml:space="preserve">{{ArosNav}}

==A technical overview of AROS==

Google translation [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=de&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs German], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=fr&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs French], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=it&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Italian], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=es&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Spanish], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=hi&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Hindi], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=zh-CN&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Chinese], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ru&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Russian], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pl&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Polish],
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pt&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Portuguese]

{{Uncited}}

AROS,&lt;ref&gt;[http://aros.sourceforge.net/download.php References and sources]&lt;/ref&gt; like AmigaOS (TM), is a [[w:Message passing|message-passing]], [[w:Preemption (computing)|preemptive]] [[w:Multitasking|multitasking]] [[w:Operating system|OS]].

It uses [[w:Reentrant (subroutine)|re-entrant]] shared libraries to save memory space.

AROS is based around an executive library kernel (Exec) and two other libraries:

* Exec (the &quot;kernel&quot;, which is not a kernel in the modern sense), 
* Intuition (graphics and GUI, integrated into the system) and 
* AmigaDOS (Disk Operating System, the Metacomco's Tripos modified to work with Exec).

The design philosophies of AmigaDOS and Intuition are rather different, the former adopting a C-like API and the latter creating an [http://www.basden.demon.co.uk/amiga/amiga.oo.html object-oriented], message passing aware environment for the programmer. The system base is the only absolute address in AmigaOS (located at 0x00000004) this does differ with AROS as AROS SysBase is automatically provided (no $4) but everything else is dynamically loaded. The OS is well known for delivering high performance due to its close connections with the hardware, while simultaneously having the flexibility to support re-targetable graphics (Cybergraphics) and retargetable audio subsystems (AHI).

: Diagram showing relationships of libraries to system needed


Remember, AROS is a [http://en.wikibooks.org/wiki/Aros/Developer/ABIv1 research] operating system, and while all contributions to the base AROS code are welcome, please contact the dev list first for any core changes. Writing applications for AROS does not have this requirement. 

While AROS appears and feels almost feature complete, it is still [[Aros/Developer/IncompleteAPIs|missing a small number of functions]] from the Amiga API. 


[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1201 This thread provides] information for setup, [http://www.aros.org/documentation/developers/index.php documentation] and whether you are interested in core OS changes and/or writing/porting software apps 

*you compile directly under AROS, which can be running on either real hardware, virtual hardware
*in hosted mode under linux/window, cross-compile from that host OS (save your files as ISO-8859-15 encoding instead of UTF-8) [https://github.com/BlitterStudio/aros-compiler-docker Docker images] 


'''The repository''' for 64bit and 32bit ABIv1 all hardware platforms is [https://github.com/aros-development-team/AROS current development version]. 
There are many forks of this so that developers can work on their own and forward changes at a later date as discussed on the dev forum 


64bit PC is one of two hardware platform with another fork called [https://github.com/deadwood2/AROS abiv11] which is used for Aros One x64 PC 

32bit PC is the other fork [https://github.com/deadw00d/AROS/tree/alt-abiv0 repository for current stable PC version ABIv0 with backported ABIv1 features is located which is used on AROS One and Icaros x86 32bit based distros] this is for historic reasons 


Any [https://github.com/aros-development-team/AROS/issues bugs / issues can be added for ABIv1 issues]. The two individual PC forks have their own issues tab on their github webpages 

We have a [https://arosdevteam.slack.com/archives/CUFV48U3H slack here], discord on [https://discord.gg/UKp9qdEBuQ Discord@AmigaDev], 


==Software Development for AROS==

===Programming languages===

====Common to all====

'The Developer Environment', which primarily supports C/C++ code, there are other programming languages available for AROS:

'''Scripting''' 
:[[Aros/User/DOS|DOS]] 
:[[Aros/Developer/Docs/LUA|LUA]] 
:REXX [[Aros/Developer/Docs/Rexx|Regina (AROS' ARexx)]] 


====Needs to be compiled/ported====

::[[Aros/Developer/Docs/LLVM|LLVM]] 
::Python [ Info], [], 
::[https://ae.arosworld.org/index.php?board=11.0 FreePascal FPC Aros-Exec thread], [https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language fpc arm here is very old and will not work], FreePascal for AROS has its own [http://fpcaroswiki.alb42.de/ Wikibook], 


::[http://sourceforge.net/projects/xamos/ X-Amos Basic] 
::[http://sdlbasic.sourceforge.net/ SDLBasic] ([https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language ])
::[[Aros/Developer/Basic/Basic4SDL|Basic4SDL]] ([https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language ])
::[http://alvyn.sourceforge.net/ Alvyn] ([http://www.dusabledanslherbe.eu/AROSPage/MISC.14.html download]) 


::[http://www.airsoftsoftwair.com/ Hollywood when enough users warrant a port - paid one time fee language] 


::[[Aros/Developer/Docs/E|AmigaE Portable E]]


====Hardware Restricted====

'''Basic'''

:[http://amos.pspuae.com/AmosProManual/contents/c1.html '''Amos Pro'''] [http://amos.pspuae.com/index.php?action=forum#1 compatible] [http://www.amigacoding.com/index.php/Main_Page commands] (all incomplete) 

:'''Blitz Basic''' [http://aros-exec.org/modules/newbb/viewtopic.php?post_id=46537#forumpost46537 none on AROS] 
:: [http://www.amiforce.de/main.php Amiblitz] on amiga(TM) emulator

:'''Amiga Basic'''
:: [ ACEBasic]

'''Misc''' 
:Ruby [http://www.ruby-lang.org/en Info]/[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language Ruby 32bit PC], 


===Where to get the C/C++ Environment===

If you want to develop for AROS, its generally easier to be running linux hosted AROS development environment especially for C++, cross compiling the code. That's how most developers now are doing it. g++ is used to compile owb web browser as well as some other AROS software. If you were hoping for a rich set of C++ libraries or classes defined for the OS feature set, you might be disappointed.

AROS Native compiling is possible, but you're much more likely to run into the odd bug(s) in the dev environment since it gets little testing and fixing by other developers.

Is there a sftp software or scp over ssh available?
Maybe. At least the security part would be handled by [https://github.com/jens-maus/amissl amissl] [https://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc port]. [https://github.com/BlitterStudio/dopus5 DOpus5] has recently added sftp support. See here for a [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1974&amp;highlight=ssh&amp;pid=12073#post_12073 ssh scp client]

[https://arosdevteam.slack.com/join/shared_invite/enQtOTc4Mzg0NDIzNzQ0LWQ2NWZmNmMwNGIwNGEyNTgxNzU3MGFjMTk3ZThmOTQ1MTVjMzhmNTllYWQ0ZTUxMjBjMGE0Y2VjMDJmNTc5MzI#/shared-invite/email Slack Dev Forum] 


====Cross compilers from Windows or Linux====

*Windows WSL2 walkthrough can be [https://arosnews.github.io/how-to-cross-compile-aros-hosted-wsl/ found here] 


you want to build AROS. No problem.

Here are instructions for PC 64-bit:
https://github.com/deadw00d/AROS/blob/master/INSTALL.md

Here are instructions for PC 32-bit:
https://github.com/deadw00d/AROS/blob/alt-abiv0/INSTALL.md

And as always has been the case you can use the contrib archive to 'obtain' the development directory which contains the /native/ AROS gcc compiler and tools. That compiler is used to build AROS itself but can be used outside the AROS build process by providing --sysroot with indicated directory to cross compile for AROS.


=====Older guides for Linux hosted compiler=====

Please install these packages before moving to next step. Below is a reference list for Debian-based distributions. Reference build system was Ubuntu 18.04/20.04 amd64.

subversion git-core gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libx11-dev libxext-dev libc6-dev liblzo2-dev libxxf86vm-dev libpng-dev gcc-multilib libsdl1.2-dev byacc python-mako libxcursor-dev cmake zsh mingw64

Do all of these operations under home directory of your user or another directory where your user has write permissions.

Specifically, in a section &quot;Linux-i386&quot;, be sure first to build the cross-compiler (toolchain-alt-abiv0-i386) and only then AROS itself (alt-abiv0-linux-i386).


Clone &amp; build
&lt;pre&gt;
$ mkdir myrepo
$ cd myrepo
$ git clone https://github.com/deadw00d/AROS.git AROS
$ cd AROS
$ git checkout alt-abiv0
$ cd ..
$ cp ./AROS/scripts/rebuild.sh .
$ ./rebuild.sh
&lt;/pre&gt;

Now to the build selection below - Linux-i386 

Select toolchain-alt-abiv0-i386 - Select alt-abiv0-linux-i386 (DEBUG) 

Start AROS by:
&lt;pre&gt;
$ cd alt-abiv0-linux-i386/bin/linux-i386/AROS
$ ./Arch/linux/AROSBootstrap
&lt;/pre&gt;


Pc-i386 Select toolchain-alt-abiv0-i386 (if not built yet) - Select alt-abiv0-pc-i386

ISO image available in alt-abiv0-pc-i386/distfiles


Now that we have linux-hosted build, we can resume native (option 2).
Run ./rebuild.sh and selection option 2. Wait until it finished, then:
&lt;pre&gt;
$ cd alt-abiv0-pc-i386
$ make
&lt;/pre&gt;

Now
&lt;pre&gt;
$ make bootiso
&lt;/pre&gt;


Now, your compiler is located in toolchain-alt-abiv0-i386 directory and named i386-aros-gcc. Includes are in alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development/include and libraries are in alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development.lib.

This is how then can be passed to the compiler:

/home/xxx/toolchain-alt-abiv0-i386/i386-aros-gcc --sysroot /home/xxx/alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development -L/home/xxx/alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development/lib 

../toolchain-alt-abiv0-i386/i386-aros-gcc --sysroot bin/linux-i386/AROS/Development local/helloworld/helloworld.c -o local/helloworld/helloworld


Another method was using Debian like distros and download the gimmearos.sh script (on [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/cross aros-archives]) to setup the developer environment by downloading necessary packages ...
The gimmearos script is a good start in that direction, building the cross compilers and hosted AROS environment, but gimmearos.sh might be out of date or not be completely compatible with any given linux distro. 

In order to do that, you have to compile AROS yourself. Download AROS source archive not contrib. Compile AROS by entering the main directory

 ./configure
 make

([http://aros.sourceforge.net/documentation/developers/compiling.php More on compiling AROS]). The result will be a basic AROS system without development tools.

To compile C++ on Linux, type 'make gnu-contrib-crosstools', creating the cross-compilers in ./bin/linux-i386/tools/, named i386-aros-gcc, etc.

'''Note''': Currently, to make the cross compilers usable copy 'collect-aros' from tools/ to tools/i386-aros/bin/. At the moment the cross compilers if used from the Linux command line will only find it when it's there.

If you want to compile native compilers (the Developer Environment), type 'make contrib-gnu-gcc', creating native compilers in AROS' System:Development/bin directory.

When the output needs to be stripped &lt;code&gt;--strip-unneeded --remove-section .comment&lt;/code&gt;

The Obj-C backend should build out of the box.

Open contrib/gnu/gcc/mmakefile.src and search for the line which contains &quot;--enable-languages&quot; and add &quot;objc&quot; to the list of languages that follows it.

    --enable-languages=c,c++,objc

Better make it—enable-languages=c,c++,objc,obj-c++

ObjC++ is broken as soon as you try to use exceptions, but that might change in future GCC versions and it does not hurt having it there already.


Do you need a cross-compiler or a real compiler? In the first case you can get away with just downloading the proper gcc archive, apply the patch and proceed with the normal gcc build. In the case of a real cross-compiler then when downloading the contrib sources, also need to download the normal sources, place the contrib sources into a directory called contrib, need to install autoconf+automake+perl+python, call ./configure, cd into the subdirectory and type make.

to rebuild GCC with host == build == target == i386-pc-aros. So just get the vanilla sources and apply the patches without bothering about the build system?


[https://vmwaros.blogspot.com/2019/10/a-pre-configured-development-machine.html pre-configured VM environment vmware virtual machine to develop AROS and AROS software]


'''64 bit'''


'''32 bit'''

A good option for multiple OS is [https://axrt.org/index.php?tab=download-aros AxRuntime lets developers compile their Amiga API-based applications as Linux binaries being able to utilize modern development tools available on Linux, like IDEs, debuggers, profilers, etc] 


====Native compilers for AROS====

Namely gcc for C or g++ for C++ are supplied with the [[Aros/Developer/Docs#The Developer Environment|Developer Environment]], which is already '''setup''' and part of any current AROS distribution like AROS One or the nightlies 

* Current GCC 6.5 (32bit) though moving to 10.5 and 15.1 (64bit) 
* Older software components. GNU GCC 4.x GNU BinUtils, GNU Fileutils 4.x, GNU Textutils and others usually deprecated 

On single partition systems and the Boot ISO, the AROS Developer environment is installed under &quot;SYS:Development/&quot;. Systems with multiple partitions - such as a Work: partition - tend to install it to there instead, however it can be installed manually to any location. Please remember, if moving, that you will need to correct the Development packages 'install location' env variable to point to the new locations root - look in SYS:S/startup-sequence.

&lt;pre&gt;
Assign Development: SYS:Development 
Assign C: Development:bin ADD 
&lt;/pre&gt;


In the aros build instructions. you need to check out contrib and/or ports into your AROS source directory, as subdirs. then, assuming you are building in an external build dir, as you should, you simply configure and &quot;make contrib&quot; for instance or whatever submodule you might want to build.


===Beginners Tutorials in C C++===

As AROS is [http://eab.abime.net/showthread.php?t=29856 C based] API compatible to AmigaOS 3.x, so most of the information on programming C on the Amiga applies to AROS as well. Please note that there is a lot of AmigaOS 1.3 (1985-1989) and [https://www.markround.com/amigaguide AmigaOS AOS 2.x (1990-1992)] information around but OS3.1 is recommended but limited in amount. 

Brief overview of what is required to write AROS Applications

# Using [[Aros/Developer/Docs/Libraries/Intuition|Intuition]] for basic screens/windows 
# Using graphics within windows via 8bit [[Aros/Developer/Docs/Libraries/Graphics|graphics]] and so onto  15-16-24bit [[Aros/Developer/Docs/Libraries/CGFX|cybergraphx]]
# Load and save work to [[Aros/Developer/Docs/Libraries/DOS|dos]] disk drives
# Using the [[Aros/Developer/Zune|ZUNE GUI Environment]]


Writing native games require this extra information

# Using [[Aros/Developer/AHIDrivers|AHI audio hardware independent API]]
# Using USB joystick/joypad with the Poseidon USB stack through [[Aros/Developer/Docs/Libraries/LowLevel|LowLevel]] library


Additional features that could be added later

# Adding additional [[Aros/Developer/Docs/Libraries/Locale|Locale]] language translations to your program 
# Adding a [[Aros/Developer/Docs/Rexx|AREXX/Regina]] port to your application 
# Executing Amiga(TM) [[Aros/User/DOS|DOS]] commands from your application
# Using [[Aros/Developer/Docs/Libraries/Icon|icons]] (.info files) and icon tooltypes (stack, version, and program startup options)
# Local couch or IP based SANA2 networking co-op multi player gaming support 


Most AmigaOS programming books are nowadays very much out of date as most are from the late 1980s and do not cover later amigaOS releases like 3.1 for example, Rob Peck's book &quot;Programmer's Guide to the Amiga&quot;. The Amiga ROM Kernel manuals aka RKMs like Libraries (3rd edition), Devices (), the AmigaDOS manual (3rd edition) and the Style Guide may have their uses. There are some reference examples from AmigaMail and Devcon notes (available again on an Amiga developers CD 2.1). 

For Arexx then &quot;The Amiga Programmer's Guide to ARexx&quot; by Eric Giguere, which was published by Commodore is useful as well as an &quot;Arexx Cookbook&quot;.

Curly brackets missing - try SHIFT + ALT + 7 or 0.


* Beginners C Guide [http://www.iu.hio.no/~mark/CTutorial/CTutorial.html C Tutorial], 
* [http://thecguru.com/ C for beginners],
* [http://fresh2refresh.com/c/c-basic-program/ C programming basics] for students, 
* [https://www.edx.org/courses Free Online course] from American Universities 
* Reference Amiga [http://amigadev.elowar.com/ API reference].


* AROS based c source can be found [[Aros/Developer/Docs/Examples|here]] and lots of example code can be found inside [https://github.com/aros-development-team AROS sources] themselves and from the contrib section of the archives from [https://github.com/aros-development-team/contrib Aros site], and study the AROS applications source code, e.g. the test programs from the Tests drawer (folder/directory). Take a look at the code of some smaller AROS programs might be a better and more up to date 

When you upload your builds, please write the architecture (like i386-aros, x86_64-aros, armPi-64 etc.) in the archive name 
and it is also advisable to write in the field &quot;Requirements&quot; what ABI (ABIv1 or for PC forks ABIv11 or ABIv0) 


===Compiling C/C++ Code===

Native, although we have a IDE Integrated Development Environment (Murks), it does lack a debugger. Whilst others use a combination of a text editor and shell to edit code. Most though use an AROS hosted on Linux to take advantage of the better GCC tools like GDB and various IDEs.

Open shell - its a menu option at the top left of Wanderer (desktop). Or by using the right Win key and w (or F12 and w) within the directory with the source code. Type in
 sh 
to change the amiga shell into a unix shell. You can then type in ls (unix equivalent to amiga dir). Take a look [http://en.wikibooks.org/wiki/Linux_commands here] for more commands.

For a single file program-name.c or program-name.cpp
 gcc -o program-name program-name.c  
or 
 g++ -o program-name program-name.cpp
or
 g++ -o test -Wall -g main.cc texturelib.cpp xmodelib.cc -lsdl -lgl

To close the shell, click on the top left-hand corner to close (twice). Once to get back the aros shell and then again to close finally. Use [http://freshmeat.net/projects/cksfv/ cksfv] as a test.

Some source code requires the addition of Amiga API libraries, like dos, which you can flag at the compile time as 
 gcc -o julia.exe julia.c -ldos

For DOS use -ldos as example and if you are compiling mui codes it will be -lmui or intuition -lintuition. Other missing symbols are due to linker libraries being necessary for linking in functions that aren't in the standard C libraries. For example some source code would need added

 -lz or -lm or -lpng or -larosc etc.

use this in unix line command mode to search for 'search-item' in many .c files (*.cpp for c++, etc.)
 grep -l 'search-item' *.c

If the program is not executable, try using parameter fno-common 

&quot;Delete #?.o&quot;? Or if you are using abcshell then &quot;rm *.o&quot;


:''More information: [[Aros/Developer/Porting software]]''


=== How to make Apps have AROS 64-bit specific support code ===

[http://www.aros.org/cs/documentation/developers/app-dev/portable.php Portable code] 

AROS64 already uses 64bit addressing, it just doesn't setup the MMU for more than 4GB physical memory currently.
When porting software to AROS64 it is &quot;mostly&quot; a case of converting ULONG's that are used to store pointers, into IPTR's instead, etc. Another quirk, is making sure items on the stack are the correct size by using the STACKED attribute for them. 

* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.

compiling mui stuff for aros setting -std=gnu99 is necessary, had -std=c99 usually 
A MUI application most likely needs only the HOOKPROTOxxx SDI macros. They are compatible with AROS, only the attributes (hook, object attribute) must be given in the right order.

crash which suggest memory corruption. From my experience porting from 32-bit to 64-bit these kinds of errors can happen if a pointer is passed somewhere via ULONG variable. Then half of the pointer is cut.

To generate this error, please run AROSBootstrap with -m 1024. This will allocate heap to 64-bit address space which will make these errors immediatelly visible. These types of crashes are hard to debug. Disabled as little code as possible to stop corruption from occurring and then try to read from the code where it can be broken

Crashing in tslf_freevec is another symptom of memory corruption and these memory corruptions will manifest differently on different setups.


==Coding conventions==

As the AROS core source is a shared developer experience, there are rules regarding structure and style. When it comes to your creating your own app and coding, the structure and style should be your own, i.e. you should enjoy what you do and do it so that you can understand what is going on.

===Layout===

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
static void 1st_function()
{
    program
    exit(0);    
}

int main(void)
{
    1st_function();
    2nd_function();
    3rd_function();
    return 0;
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;

struct Screen * openscreen(void);
struct Window *openwindow(struct Screen *screen, const char *title, LONG x, LONG y, LONG w, LONG h);

VOID 1st_function();
VOID 2nd_function();

int main(int argc, char **argv)
{
    program
    return 0;
} /* main */

VOID 1st_function()
{

}

VOID 2nd_function()
{

}
&lt;/syntaxhighlight&gt;

===General style===

This code is used by many people and therefore you should keep some things in mind when you submit source code:

* Keep things simple 
* Keep the source clean 
* Always know what you are doing, if not flag it and describe what needs to be done... 
* Explain clearly/simply what you are doing 
* Remember that you write code once but that it is read many times by many people

===Comments===

AROS uses some of the comments in the source to generate the documentation. Therefore it's necessary to keep a certain format so the tools can find their information. Other comments are ignored but they should explain what you thought when you wrote the code. If you really can't think of an explanation, then don't write the code a second time like this:

&lt;pre&gt;
/* This adds 1 to t */
t ++;
&lt;/pre&gt;

What we think of is this:

&lt;pre&gt;
/* Go on with next element */
t ++;
&lt;/pre&gt;

===Formatting===

This is only '''IMPORTANT''' if you are going to work on the core AROS code or contrib but not applications which may reside outside like on AROS Archives or other websites.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
{
    /* a */
    struct RastPort * rp;
    int               a;

    /* b */
    rp = NULL;
    a  = 1;

    /* c */
    if (a == 1)
        printf (&quot;Init worked\n&quot;);

    /* d */
    if
    (
        !(rp = Get_a_pointer_to_the_RastPort
            (
                some
                , long
                , arguments
            )
        )
    ||
        a &lt;= 0
    )
    {
        printf (&quot;Something failed\n&quot;);
        return FAIL;
    }

    /* e */
    a = printf (&quot;My RastPort is %p, a=%d\n&quot;
        , rp
        , a
    );

    return OK;
}
&lt;/syntaxhighlight&gt;

Looks ugly, eh ? :-) Ok, here are the rules:

&lt;pre&gt;
If several lines contain similar code, put similar things below each other (see a and b);
Put spaces between operands and operators
Put braces {}, brackets [] and parentheses () below each other (d) if there is much code between. 
Brackets and parentheses may be in one line if the code between is small (c)
Indent by 4 Spaces. Two indent levels may be abbreviated by one tab.
&lt;/pre&gt;

'''Before committing please normalize the indentation - if you have a mixture of tabs and spaced - please always use spaces, 1 tab = 4 spaces.'''

The reasons for this are:

# While some editors can use an arbitrary sizes for tabs, it's a bit complicated to tell another editor which tab size was used by the one used to write the code. 
# Most code in AROS was written this way and your code should look like the rest. 
# You can print this code on any printer without special tools to &quot;fix&quot; the tabs. 
# Most editors have smart tabs which do exactly this. If your editor doesn't, write a bug report.

If you have a function with many arguments (d, e) you should put the parentheses in lines of their own and each argument in one line (d) or put the first argument behind the opening parentheses (e) and each following argument in a line of its own with the comma in front. The closing parentheses is in a line of its own and aligned with the beginning of the expression (i.e. the a and not the opening parentheses or the printf()).

Use a single blank line to separate logical blocks. Large comments should have a blank line before and after them, small comments should be put before the code they explain with only one blank line before them.

If you see any TABS in AROS core sources then the suggestion is to &quot;detab the file and commit that separately&quot; either before or afterwards from making functionality changes. Make two commits instead of one. This makes it easier for others to see the real changes instead of having to dig through multiple lines of irrelevant diffs.

===Eliminating Global Variables===

i.e. pass variables to functions (local scope) or classes making it easier to track and debug your code.

Any time you find that you need a particular thing in 'a lot of different places', chances are that all those places are conceptually related, and so you can create a class, a namespace, a function, or some other higher-level organizational unit to represent that relationship. This makes the program easier to understand.

Bad Designs

* All variables are global. 
* There are no standalone functions, only sub-procedures which act on the global variables. 
* Every sub-procedure is at least 500 lines to several thousand 
* Every sub-procedure has more than one task to perform 
* Copy-paste is preferred to writing methods, AND subtle changes are made in the middle of the code

Good Designs

* structure program into functions (C or basic) - top-down procedural approach 
* put in class(es) (freepascal or C++) - the object is fixed and you use methods to access the object

&lt;pre&gt;
 class String_List
 {
 private:
 list&lt;string&gt; m_List;  // member
 public:
 void read_strings() { /* read strings into m_List */ }
 void print_strings() { /* write contents of m_List to stdout */ }
 void sort_strings() { /* sort contents of m_List */ }
 void sort_strings_reverse() { /* reverse-sort contents of m_List */ }
 void unique_strings() { /* remove duplicate strings */ }
 };

 int main()
 {
 String_List myList;  // local
 myList.read_strings();
 myList.sort_strings();
 myList.print_strings();
 myList.sort_strings_reverse();
 myList.print_strings();
 myList.unique_strings();
 myList.print_strings();
 return 0;
 }
&lt;/pre&gt;

This way it is very easy to replace the list with new list for debugging purposes, or replacing the methods without replacing the list, when you want different results. You only have to replace the content of the local variables.

 So create the structure that matches your data (linked lists, trees, arrays, etc.) and what to do with them (sorting, searching, etc.)

&lt;pre&gt;
.h usually contain #define #include typedef enum struct extern screen and window definitions (data structures)
.c should contains functions and algorithms
&lt;/pre&gt;

One way to look at it is that menu headings act as the .c file and sub-menu headings as functions.

When you start a project, you place a couple of declarations in the include file. As the project continues, you place more and more declarations in the include file, some of which refer to or contain previous declarations. Before you know it, you have a real mess on your hands. The majority of your source files have knowledge of the data structures and directly reference elements from the structures.
Making changes in an environment where many data structures directly refer to other data structures becomes, at best, a headache. Consider what happens when you change a data structure.

Use good variables names to help clarify code and only comment when you need to explain why a certain programming approach was made.

You're Refactoring Legacy Code, you see a global, you want to get rid of it. How do you do this?

Exactly what to do depends on how the global is used. The first step is to find all uses of the global throughout the code, and get a feel for what the significance of the variable is and how it relates to the rest of the program. Pay particular attention to the &quot;lifetime&quot; of the variable (when it gets initialized, when it is first used, when it is last used, how it gets cleaned up). Then, you will probably make the global a data member of a class (for OO languages), or you will write some get/set functions. Converting to the Singleton Pattern is common, but you may discover that it makes more sense for the data element to be a member of an existing singleton, or maybe even an instance variable.

# Create a basic read method, either as a class or a global function. Replace all reads with the access method, but leave the variable defined as a global.
# Review each of the writes to the method and extract action functions one at a time. Unless two operations are coded identically in the original code, extract each write access separately.
# Change the variable scope from global to local.
# Analyze similar action functions to determine if any can be merged, i.e., there are no functional differences in the results of the function, just differences in the implementation details.
# Review the calls to the read method and see if a more complex functionality should be applied. Follow the approach for writes and unless implementations are identical, create separate access functions. 
# Analyze the access functions for duplication.

As returning variables by &quot;passing by value&quot; are forgotten, so &quot;passing by reference&quot; is often used instead. The reference is a pointer to the variable so the value is remembered when returned.

Alternatives

* Hidden Globals
* Singleton Pattern
* Database or TupleSpace
* Context Object 
* Dependency Injection 
* Stateful Procedures


==AROS/AmigaOS APIs and Docs==

&lt;pre&gt;
Library:
   - Private data structure
   - Many public access methods

Device:
   - Private data structure
   - Two (BeginIO/AbortIO) access methods

Resource:
   - Public data structure
   - *NO* access methods
&lt;/pre&gt;

And, being Amiga OS-compatible, there are exceptions to all of these.


===System Libraries===

The [http://developers.aros.org/ AROS Guide To Libraries] can be used as a guide to individual commands and old Dev Docs are used in application programming.

Amiga/Aros styles libraries are very different from windows and linux libs. Typical .so/dll libraries are foreign to most Amiga-like OS 


*[[Aros/Developer/Docs/Libraries/AROSC|arosc.library]]
*[[Aros/Developer/Docs/Libraries/AmigaGuide|amigaguide.library]]
*[[Aros/Developer/Docs/Libraries/ASL|asl.library]]
*[[Aros/Developer/Docs/Libraries/Bullet|bullet.library]]
*[[Aros/Developer/Docs/Libraries/BSDsocket|bsdsocket.library]]
*[[Aros/Developer/Docs/Libraries/CAMD|camd.library]]
*[[Aros/Developer/Docs/Libraries/Codesets|codesets.library]]
*[[Aros/Developer/Docs/Libraries/CGFX|cybergraphics.library]]
*[[Aros/Developer/Docs/Libraries/CGXVIDEO|cgxvideo.library]]
*[[Aros/Developer/Docs/Libraries/Commodities|commodities.library]]
*[[Aros/Developer/Docs/Libraries/DataTypes|datatypes.library]]
*[[Aros/Developer/Docs/Libraries/DiskFont|diskfont.library]]
*[[Aros/Developer/Docs/Libraries/DOS|dos.library]]
*[[Aros/Developer/Docs/Libraries/Exec|exec.library]]
*[[Aros/Developer/Docs/Libraries/Expansion|expansion.library]]
*[[Aros/Developer/Docs/Libraries/FreeType2|freetype.library]]
*[[Aros/Developer/Docs/Libraries/GadTools|gadtools.library]]
*[[Aros/Developer/Docs/Libraries/Graphics|graphics.library]]
*[[Aros/Developer/Docs/Libraries/Icon|icon.library]]
*[[Aros/Developer/Docs/Libraries/Identify|identify.library]]
*[[Aros/Developer/Docs/Libraries/IFFParse|iffparse.library]]
*[[Aros/Developer/Docs/Libraries/Intuition|intuition.library]]
*[[Aros/Developer/Docs/Libraries/Keymap|keymap.library]]
*[[Aros/Developer/Docs/Libraries/Layers|layers.library]]
*[[Aros/Developer/Docs/Libraries/Locale|locale.library]]
*[[Aros/Developer/Docs/Libraries/LowLevel|lowlevel.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEESingBas|mathieeesingbas.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEEDoubBas|mathieeedoubbas.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEESingTrans|mathieeesingtrans.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEEDoubTrans|mathieeedoubtrans.library]]
*[[Aros/Developer/Docs/Libraries/Mathtrans|mathtrans.library]]
*[[Aros/Developer/Docs/Libraries/MUIMaster|muimaster.library]]
*[[Aros/Developer/Docs/Libraries/Partition|partition.library]]
*[[Aros/Developer/Docs/Libraries/PopUpMenu|popupmenu.library]]
*[[Aros/Developer/Docs/Libraries/OOP|oop.library]]
*[[Aros/Developer/Docs/Libraries/Regina|regina.library]]
*[[Aros/Developer/Docs/Libraries/Reqtools|reqtools.library]]
*[[Aros/Developer/Docs/Libraries/RexxSysLib|rexxsyslib.library]]
*[[Aros/Developer/Docs/Libraries/ScreenNotify|screennotify.library]]
*[[Aros/Developer/Docs/Libraries/TTEngine|ttengine.library]]
*[[Aros/Developer/Docs/Libraries/Thread|thread.library]]
*[[Aros/Developer/Docs/Libraries/Utility|utility.library]]
*[[Aros/Developer/Docs/Libraries/Xadmaster|xadmaster.library]]
*[[Aros/Developer/Docs/Libraries/Workbench|workbench.library]]
*[https://github.com/aros-development-team/AROS/commit/c82e86b8480277998014cc327b56c7664023a52f ClassAct Reaction boopsi class]


===AROS Subsystems===

# [[Aros/Developer/Zune|Zune MUI compatible GUI]]
# [[Aros/Developer/AROSAppPackages|AROS Application Packages]]
# AHI Audio Drivers - [[Aros/Developer/AHIDrivers|Usage]]/[[Aros/Developer/AHIDriversDev|Development]]
# AROSTCP Sana2 Network Interface Drivers - [[Aros/Developer/NICDrivers|Usage]]/[[Aros/Developer/NICDriversDev|Development]]
# [[Aros/Developer/AmiSSL|AmiSSL]]
# gfx.hidd/cybergraphics Video Drivers - [[Aros/Developer/GfxDrivers|Usage]]/[[Aros/Developer/GfxDriversDev|Development]]
# IO Device Drivers - [[Aros/Developer/IODeviceDrivers|Usage]]/[[Aros/Developer/IODeviceDriversDev|Development]]
# USB Device Drivers - [[Aros/Developer/USBDrivers|Usage]]/[[Aros/Developer/USBDriversDev|Development]]
# PCI Device Drivers - [[Aros/Developer/PCIDrivers|Usage]]/[[Aros/Developer/PCIDriversDev|Development]]
# [http://www.libsdl.org/ SDL] [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2013&amp;pid=13333#post_13333 SDL2 coding usage], [https://github.com/search?q=repo%3Aaros-development-team%2Fcontrib%20SDL2&amp;type=code SDL2 commits], [https://github.com/aros-development-team/contrib/commit/c62c3c425c35bac19dadc23be092b0b13a66c76c SDL3 initial commit], []
# [[w:Gallium3D|Gallium 3D]] [http://www.mesa3d.org/ openGL aka Mesa] - [[Aros/Developer/OpenGL|Usage]]/[[Aros/Developer/OpenGLDev|Development]] [http://www.swiftless.com/opengltuts.html Swfitless]
# A small subset of GTK2 through [http://sourceforge.net/projects/gtk-mui/ MUI-GTK] 
# Cairo 2D Engine - [[Aros/Developer/Cairo|Usage]]/[[Aros/Developer/Cairo|Development]]
# [[Aros/Developer/Scalos|Scalos desktop API and plugin modules]]
# [[Aros/Developer/VHI|VHI video driver]]


====HIDDs====

*[[Aros/Developer/Docs/HIDD/HIDDClass|hiddclass.hidd]]
*[[Aros/Developer/Docs/HIDD/Graphics|graphics.hidd]]
*[[Aros/Developer/Docs/HIDD/VesaGfx|vesagfx.hidd]]
*[[Aros/Developer/Docs/HIDD/ATI|radeon.hidd]]
*[[Aros/Developer/Docs/HIDD/NVidia|nvidia.hidd]]
*[[Aros/Developer/Docs/HIDD/Nouveau|nouveau.hidd]]
*[[Aros/Developer/Docs/HIDD/Kbd|kbd.hidd]]
*[[Aros/Developer/Docs/HIDD/Mouse|mouse.hidd]]
*[[Aros/Developer/Docs/HIDD/i2c|i2c.hidd]]
*[[Aros/Developer/Docs/HIDD/IRQ|irq.hidd (deprecated)]]
*[[Aros/Developer/Docs/HIDD/PCI|pci.hidd]]
*[[Aros/Developer/Docs/HIDD/PCIPC|pcipc.hidd]]
*[[Aros/Developer/Docs/HIDD/Serial|serial.hidd]]
*[[Aros/Developer/Docs/HIDD/Thunderbolt|thunderbolt.hidd]]
https://github.com/aros-development-team/AROS/commit/4f02ea691799aff3a01f60cfa5f9182c82fc57a8

HIDD are used for device/peripheral low level hardware support drivers. The HIDD system is split up into a collection of classes with a strict inheritance hierarchy. A HIDD class implements a device driver for a single device or in rare cases a group of devices and provides an interface for other programs and devices to access.
      
In order to maintain portability of interfaces across a wide range of hardware this interface will in general not present the raw interface to the underlying hardware. Instead it will present a generic interface that describes many different hardware implementations. This allows for the best reuse of both interfaces and code.

HIDD API is heavyweight though. You need to open a HIDD library, open oop.library, instantiate an object (even if there's no object); and object calls are more costly compared to plain library calls.


Basically your task is to implement a subclass of hidd.ata.bus for your hardware. just implementing the XXXATA__Hidd_ATABus__xxxxxx methods for the Amiga chipset - and appropriate versions of the interface_xxx.c file(s). pretty much everything in probe.c could be ignored - just write a replacement scan for relevant amiga devices and store whatever info you need in the bus data? only the &quot;SUPPORT_LEGACY&quot; blocks might be related.

You do not need to depend on PCI API. PCI is just a way to discover the hardware on PCs, etc. 
&lt;hidd/pci.h&gt; includes (at some depth) &lt;interface/HW.h&gt;, which defines IID_HW. This comes from the 'generic' HIDD class in: 
 rom/hidds/hidd/hiddclass.conf
did not split up HIDD and HW because they are always used in pair. It's the same as hidd/pci.h bringing definition for: PCI, PCIDriver and PCIDevice. PCI is actually PCIHW, just the name was not changed for backwards compatibility reasons. HW is a 'hub' where HIDD instances plug in.

ATA HIDD aoHidd_ATABus_Use32Bit value is completely ignored unless ata.device first detects correct command line parameter.
Yes. Unfortunately I was unable to find any comment in code or svn history with explanations. Looked  at Linux source, there 32-bit PIO is also controller driver's property. Some of them enable it, some don't.

Actually, switching the default to ON should be safe. ata.device is fail-safe at this because during IDENTIFY command it validates upper 16  bits,  and  if they appear to be zeroes in all 128 longwords, then 32-bit mode is switched off. But, nevertheless, I know how tricky hardware can be, so I decided not to change original behavior. If  you think it's wrong in some cases, then it's possible to add one more  attribute  like  aHidd_ATABus_Default32Bit. If set to YES, then  this means that 32-bit PIO is safe to use by default.


====Devices====

*[[Aros/Developer/Docs/Devices/ATA|ata.device]]
*[[Aros/Developer/Docs/Devices/Console|console.device]]
*[[Aros/Developer/Docs/Devices/Narrator|narrator.device]]
*[[Aros/Developer/Docs/Devices/Printer|printer.device]]
*[[Aros/Developer/Docs/Devices/Trackdisk|trackdisk.device]]
*[[Aros/Developer/Docs/Devices/AmberRAM|amberram.device]]
*[[Aros/Developer/Docs/Devices/Timer|timer.device]]
*[[Aros/Developer/Docs/Devices/|.device]]

The Amiga used [[Aros/Developer/Docs/Devices|Devices]] to communicate with [http://aros-exec.org/modules/newbb/viewtopic.php?start=0&amp;topic_id=3475&amp;viewmode=flat&amp;order=ASC additional hardware]. AROS has replaced these hardware devices with hidd equivalents but some are still retained for backwards compatibility.

Local libraries/devices/handlers,etc. are supposed to override the ones in ROM if their version is higher than the one in ROM.

Here is the list of commands exec default: 
{| class=&quot;wikitable&quot;
| CMD_CLEAR
|  Purge the buffer of the device
|----
| CMD_READ
|  Playback Control
|----
| CMD_STOP
|  Stopped the activity of the device
|----
| CMD_FLUSH
|  Empty the queue of commands
|----
| CMD_RESET
|  Reset a device
|----
| CMD_WRITE
|  Playback Control
|----
| CMD_INVALID
|  Create an error
|----
| CMD_UPDATE
|  Gets updated device
|----
| CMD_START
|  Will restart the device
|----
|}

While most other &quot;stuff you communicate with&quot; in AmigaOS are devices &lt;ref&gt;AMIGA ROM Kernel Reference Manual: Devices, 3rd Edition. Commodore-Amiga, Inc. Addison-Wesley, 1991. {{ISBN|0-201-56775-X}}&lt;/ref&gt; that share a [http://gega.homelinux.net/AmigaDevDocs/ common base interface]. [[Aros/Developer/Docs/Devices1.3|OS 1.3 Device Drivers]].


====Handlers====

:[[Aros/Developer/Docs/Handlers/Pipe|pipe.handler]]
:[[Aros/Developer/Docs/Handlers/Port|port.handler]]
:[[Aros/Developer/Docs/Handlers/SFS|sfs.handler]]
:[[Aros/Developer/Docs/Handlers/FAT|fat.handler]]
:[[Aros/Developer/Docs/Handlers/PFS|pfs.handler]]
:[[Aros/Developer/Docs/Handlers/NTFS|fuse.handler]]
:[[Aros/Developer/Docs/Handlers/FFS|ffs.handler]]

filesystem handlers have their own separate system consisting of completely differently structured messages that dos.library use to pass requests (for things like reading, writing, getting directory contents etc.) to them. AROS originally went with implementing filesystem handlers as devices, which might arguably be more consistent with the rest of the AmigaOS API but which is quite incompatible with AmigaOS itself. However, it made it far harder to port filesystems and the gains were comparatively small, and so there's been a long standing goal of fixing this incompatibility. It has now, June 2011, been reintroduced to all AROS flavors.

are argstr and argsize valid for the handler startup environment?
DOS/RunHandler() calls DOS/CreateNewProcTags(), and then CallEntry() (in rom/dos/exit.c) to start the handler, so yes, argstr and argsize are *present* in the call signature of the handler.

Granted, argstr will be NULL and argsize 0, but those values *are* passed to the handler function using:

&lt;pre&gt;
AROS_UFC3(ULONG, entry,
                         AROS_UFCA(STRPTR, argptr, A0),
                         AROS_UFCA(ULONG, argsize, D0),
                         AROS_UFCA(struct ExecBase *, SysBase, A6));
&lt;/pre&gt;

Creating your own [without the whole build tree http://pagesperso-orange.fr/franck.charlet/temp/radeon.zip] and then  
&lt;pre&gt;
make stub
make
make install
&lt;/pre&gt;

SFS has two Root blocks, one at the start and one at the end of the disk. The Root blocks both contain the same information.  They hold various information about the disk structure and have the locations of some important blocks used by the filesystem.  

The Root ObjectContainer contains the Root directory Object. The name of this Object is the name of the volume. It is identical to a normal directory Object.

The Bitmap is used to keep track of free space. Each bit in a bitmap represents a single block. A set bit indicates a free block and a cleared bit a used block.

AdminSpaceContainers are used to keep track of space which has been reserved for storing administration blocks. Only the Bitmap, the Root blocks and the actual data stored in files aren't stored in administration space. Administration space is allocated in chunks of 32 blocks at a time. A single AdminSpaceContainer can hold information about a large number of such areas each of which has its own little bitmap of 32 bits.

Extents are stored in a B-Tree. The Root block holds a pointer to the root of the Extent B-Tree. Extents keep track of space in use by a specific file. Each fragment a file consists of has its own Extent. Extents are in a double linked list. The list can be used to locate the next or previous fragment of a file.

Below is the standard block header. This header is found before EVERY type of block used in the filesystem, except data blocks.  The id field is used to check if the block is of the correct type when it is being referred to using a BLCK pointer.  The checksum field is the SUM of all LONGs in a block plus one, and then negated. When applying a checksum the checksum field itself should be set to zero. The checking a checksum the checksum is okay if the result of the checksum equals zero. The ownblock BLCK pointer points to the block itself. This field is an extra safety check to ensure we are using a valid block.

Field	Type	Description
id	ULONG	The id field is used to identify the type of block we are dealing with. It is used to make sure that when referencing a block we got a block of the correct type. The id consist of 4 bytes and each blocktype has its own unique foure letter code.
checksum	ULONG	This field contains the sum of all longs in this block, plus one and then negated. The checksum can be used to check if the block hasn't been corrupted in any way.
ownblock	BLCK	Points to itself, or in other words, this field contains the block number of this block. This is yet another way to check whether or not a block is valid.

&lt;pre&gt;
struct fsBlockHeader {
    ULONG id;
    ULONG checksum;
    BLCK ownblock;
};
&lt;/pre&gt;
The algorithm to calculate the checksum of a block:
&lt;pre&gt;
ULONG calcchecksum(struct fsBlockHeader *block, LONG blocksize} {
    ULONG *data=(ULONG *)block;
    ULONG checksum=1;

    block-&gt;checksum=0;

    while(blocksize&gt;0) {
        checksum+=*data++;
        blocksize-=4;
    }

    return(-checksum);
} 
&lt;/pre&gt;

A Root block contains very important information about the structure of a SFS disk. It has information on the location and size of the disk, the blocksize used, locations of various important blocks, version information and some filesystem specific settings.

A SFS disk has two Root blocks; one located at the start of the partition and one at the end. On startup the filesystem will check both Roots to see if it is a valid SFS disk. If either one is missing SFS can still continue (although at the moment it won't).

A Root block could be missing on purpose. For example, if you extend the partition at the end (adding a few MB's) then SFS can detect this with the information stored in the Root block located at the beginning (since only the end-offset has changed).   Same goes for the other way around, as long as you don't change start and end point at the same time.

When a Root block is missing because the partition has been made a bit larger, then SFS will in the future be able to resize itself without re-formatting the disk.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
version	UWORD	The version of the filesystem block structure. You can check this field to identify what version of the filesystem your dealing with it and to see if you can handle this structure correctly. Don't try to interpret the disk's structure when this field contains an unknown version number!

sequencenumber	UWORD	Used to identify which Root block was written last in case the sequencenumber on both Root blocks don't match.
datecreated	ULONG	Creation date of this volume. This is the date when the disk was last formatted and will never be changed.

bits	UBYTE	Various settings, see below.
&lt;pre&gt;
pad1	UBYTE	Reserved, leave zero.
pad2	UWORD	Reserved, leave zero.
reserved1	ULONG[2]	Reserved, leave zero.
firstbyteh	ULONG	High 32-bits of a 64-bit number. This is the first byte of our partition relative to the start of the disk.
firstbyte	ULONG	Low 32-bits of a 64-bit number.
lastbyteh	ULONG	High 32-bits of a 64-bit number. This is the last byte (exclusive) of our partition relative to the start of the disk.
lastbyte	ULONG	Low 32-bits of a 64-bit number.
totalblocks	ULONG	The total number of blocks this partition consists of.
blocksize	ULONG	The size of a block of this partition.
reserved2	ULONG[2]	Reserved, leave zero.
reserved3	ULONG[8]	Reserved, leave zero.
bitmapbase	BLCK	Block number of the start of the Bitmap.
adminspacecontainer	BLCK	Block number of the first AdminSpaceContainer.
rootobjectcontainer	BLCK	Block number of the ObjectContainer which contains the root of the disk (this is where the volume name is stored).
extentbnoderoot	BLCK	Block number of the root of the Extent B-Tree.
reserved4	ULONG[4]	Reserved, leave zero.
&lt;/pre&gt;

&lt;pre&gt;
struct fsRootBlock {
  struct fsBlockHeader bheader;
  UWORD version;
  UWORD sequencenumber;
  ULONG datecreated;
  UBYTE bits;
  UBYTE pad1;
  UWORD pad2;
  ULONG reserved1[2];
  ULONG firstbyteh;
  ULONG firstbyte;
  ULONG lastbyteh;
  ULONG lastbyte;
  BLCK  totalblocks;
  ULONG blocksize;
  ULONG reserved2[2];
  ULONG reserved3[8];
  BLCK  bitmapbase;
  BLCK  adminspacecontainer;
  BLCK  rootobjectcontainer;
  BLCK  extentbnoderoot;
  ULONG reserved4[4];
};
&lt;/pre&gt;

AdminSpaceContainers are used to store the location and bitmap of each administration space. The AdminSpaceContainers are located in a double linked list and they contain an array of fsAdminSpace structures.  There is one fsAdminSpace structure for every administration space on disk.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
next	BLCK	The next AdminSpaceContainer, or zero if it is the last in the chain.
previous	BLCK	The previous AdminSpaceContainer, or zero if it is the first AdminSpaceContainer.
bits	UBYTE	The number of bits in each in the bits ULONG in the fsAdminSpace structure.
pad1	UBYTE	Reserved, leave zero.
pad2	UWORD	Reserved, leave zero.
adminspace	struct fsAdminSpace	An array of fsAdminSpace structures. The size of the array is determined by the current blocksize.
&lt;pre&gt;
struct fsAdminSpaceContainer {
  struct fsBlockHeader bheader;
  BLCK next;
  BLCK previous;
  UBYTE bits;
  UBYTE pad1;
  UWORD pad2;
  struct fsAdminSpace adminspace[0];
};
&lt;/pre&gt;
Field	Type	Description
space	BLCK	The first block of an administration space.
bits	ULONG	A small bitmap which is used to determine which blocks in an administration space are already in use. The number of bits in this bitmap is determined by the bits field in the AdminSpaceContainer.
&lt;pre&gt;
struct fsAdminSpace {
  BLCK  space;
  ULONG bits;
};
&lt;/pre&gt;

The fsBitmap structure is used for Bitmap blocks. A bitmap block is used to keep track of which space is in use and which isn't for a particular area of a disk.  All bitmap blocks together keep track of the free space for an entire disk. The location of the first bitmap block is known and all other bitmap blocks are stored in order after the first one.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
bitmap	ULONG	An array of ULONG's.  These hold the actual information on which blocks are in use and which aren't.
&lt;pre&gt;
struct fsBitmap {
    struct fsBlockHeader bheader;
    ULONG bitmap[0];
};
&lt;/pre&gt;
Each bit in a bitmap block (except for the block header) represents a single block. If the bit is set than the block is free, and if the bit is clear then it is full. The first ULONG in the bitmap area of the first bitmap block represents blocks 0 through 31 on the disk. Bit 31 of this ULONG is block 0, 30 is block 1, and so on. Bit 0 of the first ULONG represents block 31.

Below is a table to clarify how bitmaps work even further. The first column is the bitmap block number, the second column is the number of the ULONG in the bitmap array. The third column is the bit number in this ULONG, and the last column is the block which this specific bit, in this specific bitmap block represents.

We'll assume here that a bitmap block has room for 120 ULONG's (meaning there is room for storing 32 * 120 bits).

&lt;pre&gt;
Bitmap block	ULONG number	Bit number	Block represented
1 (first)	0	31	0
1	0	30	1
...	...	...	...
1	0	1	30
1	0	0	31
1	1	31	32
...	...	...	...
1	2	31	64
1	2	30	65
...	...	...	...
1	119	0	3839
2	0	31	3840
2	0	30	3841
...	...	...	...
&lt;/pre&gt;
The last bitmap block doesn't need to be completely used. The unused bits (which belong to blocks which do not exist) all have to be clear, to indicate that these blocks are in use.

The fsObjectContainer structure is used to hold a variable number of fsObjects structures (Objects) which have the same parent directory. Each ObjectContainer must contain at least one Object. If there is space in the ObjectContainer not used by the variable number of Objects then that space is zero filled. Objects always start at 2-byte boundaries, which means sometimes a padding byte is inserted between two Objects.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
parent	NODE	The node number of the parent Object, or 0 if this object has no parent (which is only the case for the Root directory).
next	BLCK	The next ObjectContainer belonging to this directory, or zero if it is the last in the chain.
previous	BLCK	The previous ObjectContainer belonging to this directory, or zero if it is the first ObjectContainer in this directory.
object	struct fsObject	A variable number of fsObject structures. The number of structures depends on the individual sizes of each fsObject structure and the blocksize. These structures are located directly after each other with at most 1 byte of padding between them to get the structures aligned on a 2 byte boundary.
&lt;pre&gt;
struct fsObjectContainer {
    struct fsBlockHeader bheader;
    NODE parent;
    BLCK next;
    BLCK previous;
    struct fsObject object[0];
}; 
&lt;/pre&gt;

fsHashTable is the structure of a HashTable block. It functions much like the hash table found in FFS user directory blocks, except that it is stored in a separate block. This block contains a number of hash-chains (about 120 for a 512 byte block). Each hash-chain is a chain of Nodes. Each Node has a pointer to an Object and a pointer to the next entry in the hash-chain.  Using such a hash-chain you can locate an object quickly by only knowing its name.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
parent	NODE	The node number of the directory Object this HashTable block belongs to.
hashentry	NODE	An array of Nodes. Each Node represents the start of a hash-chain (singly linked). A hash-value is calculated using the name of a file or directory, and this value determines in which chain the Object is linked. If there are no entries in a hash-chain then the hashentry value is zero.
&lt;pre&gt;
struct fsHashTable {
    struct fsBlockHeader bheader;
    NODE parent;
    NODE hashentry[0];
};
&lt;/pre&gt;
To calculate the hash-value using a name of an Object as input use these routines:
&lt;pre&gt;
UWORD calchash(UBYTE *name) {
    UWORD hash=0;
    /* Calculates a hash value over the passed in string.
       The end of the string can be either a NUL byte or a
       slash. The hash function is the same as the one
       used in FastFileSystem set to international mode. */
    while(name[hash]!=0 &amp;&amp; name[hash]!='/') {
        hash++;
    }
    while(*name!=0 &amp;&amp; *name!='/') {
        hash=hash*13+upperchar(*name++);
    }

    return((UWORD)(hash % (UWORD)((blocksize-sizeof(struct fsHashTable))&gt;&gt;2)));
}
UBYTE upperchar(UBYTE c) {
    if((c&gt;=224 &amp;&amp; c&lt;=254 &amp;&amp; c!=247) || (c&gt;='a' &amp;&amp; c&lt;='z')) {
        c-=32;
    }
    return(c);
}
&lt;/pre&gt;

The BNodeContainer is used to store B-Trees. Currently only one B-Tree is in use by this filesystem and it is used to store the location of file data. The fsBNodeContainer structure contains two other structures. The fsBlockHeader structure and the BTreeContainer structure.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
btc	struct BTreeContainer	Contains information about the B-Tree and its nodes contained in this block.
&lt;pre&gt;
struct fsBNodeContainer {
    struct fsBlockHeader bheader;
    struct BTreeContainer btc;
}; 
&lt;/pre&gt;


First try and locate the Root block. It should start with &quot;ROOT&quot;.  SFS has two of these, one at the start of the partition and one at the end.  One of the fields contains the block size, which will be the size of all important SFS blocks.

The root block has the root object container, which contains information about files and directories in the root directory.  The object 
containers basically hold one or more smaller structures that represent files and directories.  Scanning them all should give you a list of 
files and directories.

The root block also has the root of the Extent B-Tree.  This is a standard B-Tree structure (not a binary tree) that is used commonly in 
all kinds of system, you can read about how they work on Wikipedia if needed.  The B-Tree holds the information about *where* all the data is 
located for your files.

To recover your files, I'd do this:

* Find one of the root blocks, if not present, then figure out the block size your disk was using, and scan every block in turn to see if it 
looks like an ObjectContainer (check the fsBlockHeader's ID, check if the ownblock number is equal to the block you are currently scanning, 
and check its checksum).  So if you currently have block 12, and you see a block with the correct id, and ownblock = 12 and its checksum is good, 
then that's probably a valid ObjectContainer.

* With all the ObjectContainers found, you can extract filenames and directory names from these, but also the number of their first data 
block (in the field data) and the file size.  For small files (less than blocksize) this data block will be enough to recover the data.
For larger files, you might be lucky and all the remaining blocks are found after the first one (if the file was defragmented).  You can't be
sure of that though so...

* For larger files, you need to find all the BNodeContainers.  You could scan these in the same way you found all the ObjectContainers (look for 
blocks with the correct id, ownblock number and checksum). 

* With all the BNodeContainers found, you can try looking up the first data block of a file in the B-Tree structure.  This is a bit complicated 
-- the B-Tree consists of non-leaf nodes (blocks that only contain pointers to other B-Tree blocks), the isLeaf flag indicates this.  Or it 
can be a B-Tree leaf block.  The leaf blocks contain extra information per entry (see https://hjohn.home.xs4all.nl/SFS/extents.htm)
&lt;pre&gt;
struct fsExtentBNode {
     ULONG key;
     ULONG next;
     ULONG prev;
     UWORD blocks;
};
&lt;/pre&gt;

The key should be a block of a file (the first of a range), that is 1 to 65535 block long (depending the &quot;blocks&quot; field).  If the file is split 
up into more parts, then &quot;next&quot; will contain block number of the next range of blocks.  You need to look this up again in the B-Tree 
structure to find out how large it is. 

You can for the most part ignore the other structures (bitmap, admin containers).  The fsObjects and B-tree containers is what you'll need to 
recover the data. 


====Resources====

&lt;pre&gt;
rom/storage/mmakefile.src 
rom/storage/storage.conf 
rom/storage/storage_device.c 
rom/storage/storage_ids.c 
rom/storage/storage_init.c 
rom/storage/storage_intern.h 
rom/storage/storage_mount.c 
rom/storage/storage_unit.c
&lt;/pre&gt;

&lt;pre&gt;
rom/storage/includes/device.h 
rom/storage/includes/unit.h 
rom/storage/includes/volume.h 
rom/storage/storage_intern.h 
&lt;/pre&gt;

&lt;pre&gt;

&lt;/pre&gt;

*[[Aros/Developer/Docs/Resources/ACPI|acpi.resource]]
*[[Aros/Developer/Docs/Resources/Battclock|battclock.resource]]
*[[Aros/Developer/Docs/Resources/Bootloader|bootloader.resource]]
*[[Aros/Developer/Docs/Resources/Cia|cia.resource]]
*[[Aros/Developer/Docs/Resources/Filesystem|FileSystem.resource]]
*[[Aros/Developer/Docs/Resources/Hostlib|hostlib.resource]]
*[[Aros/Developer/Docs/Resources/Kernel|kernel.resource]]
*[[Aros/Developer/Docs/Resources/Misc|misc.resource]]
*[[Aros/Developer/Docs/Resources/Processor|processor.resource]]


==Debugging Code==

Please use the [http://sourceforge.net/tracker/?group_id=43586&amp;atid=439463 AROS Bug Tracker] if any issues are found.


GRUB Command line list

&lt;pre&gt;
sysdebug  
usbdebug - allows to see Poseidon's log in debug output
&lt;/pre&gt;


How do I get debugging out of InitResident ? If running i386 hosted on linux sysdebug=initresident on command line.
This  way  you can enable any of listed flags. sysdebug=all stands for &quot;everything&quot;


Have an executable (crosscompiled C++ code) which has 6 MB size on disk, but after loading it in memory, 250 MB RAM is taken. Any software that would split AROS executable into ELF part which would show actual size values?

 readelf -S executable

it will show you all sections in elf file, including sizes and requested alignment.

 objdump -h filename

That's will give you a quick overview of the sections and sizes. Ignore all the .debug.* sections. 
Would hazard a guess that you have a large .bss section. That's pretty common in C++.

Next step:

 nm—size-sort filename | grep ' [bB] '

The last few will be your biggest consumers. Would suggest -C to demangle the symbols... ;)


Suggest profiling the program (just use some printf's in the main loop for time spent in each part), it usually is quite easy to spot slow parts in games or apps.

If someone has '#define IPTR ULONG' somewhere. To see where that define is, redefine IPTR in the source code that fails, just above the line that fails, and the preprocessor will tell you where it was defined first.

===How to setup gdb with AROS/hosted===

Download AROS sources (AROS-xxxxxxxx-source.tar.bz2, where xxxxxxxx is the current date) and AROS contrib sources (AROS-xxxxxxxx-contrib-source) from 

Untar-bzip2 and cd to the unpacked archive directory.

 &gt; tar -xvjf AROS-xxxxxxxx-source.tar.bz2
 &gt; cd AROS-xxxxxxxx-source

Check the link to &quot;contrib&quot; (contrib-source) inside directory, e.g. correct like this:

 &gt; rm contrib
 &gt; ln -s ../AROS-xxxxxxxx-contrib-source.tar.bz2 contrib

Make sure you have the correct locale setting, otherwise compilation will fail at some point. See [http://aros.sourceforge.net/documentation/developers/compiling.php#setting-the-locale-to-iso8859 here] (or link below) for more on that. You might have to enter this:

 &gt; export LANG=&quot;en_US.ISO-8859-1&quot;

Now configure for a debug build - see &quot;./configure --help&quot; for more - here are two examples:

 &gt; ./configure—enable-debug=stack,modules,symbols
 
 &gt; ./configure—enable-debug=all

You may &quot;make&quot; now, or choose a separate directory for your build (e.g. for easy removal), for example if compiling for i386 architecture you could create a directory like this:

 &gt; mkdir linux-i386
 &gt; cd linux-i386
 &gt; ../AROS/configure—enable-debug=stack,symbols,modules

When done configuring you're ready to go:

 &gt; make

Building AROS takes some time - minutes on fast machines (e.g. 2.5&amp;nbsp;GHz quadcore), up to hours on slower machines.
The result will be AROS Linux hosted with gdb debugging enabled.

See aros.org documentation for more on compiling AROS, including more [http://aros.sourceforge.net/documentation/developers/compiling.php --enable-debug] options.


When finished, enter bin/linux-i386/AROS directory (replace &quot;linux-i386&quot; with your compilation target platform, e.g. linux-x86_64, etc.) inside the unpacked archive directory. This directory contains the required .gdbinit file for properly running AROS inside gdb.

 &gt; cd bin/linux-i386/AROS

Run AROS (here: with 128MB of memory) from gdb:

 &gt; gdb—args boot/aros-unix -m 128
or
 &gt; gdb—args boot/arosboot -m 128

 (gdb) r

Watch the shell output - in case AROS complains about &quot;LoadKeyCode2RawKeyTable: Loading &quot;DEVS:Keymaps/X11/keycode2rawkey.table&quot; failed!&quot; you should also see some instructions on how to create a keymap table. (see link above &quot;more on compiling&quot;, too.)
Quit gdb, and try default keymap table:

 (gdb) q
 The program is running.  Quit anyway (and kill it)? (y or n) y
 &gt; cd ../../..
 &gt; make default-x11keymaptable

Re-run AROS, as described above. Try e.g. RAros (= right windows key) + W to open a shell. If this doesn't work you have to create a keymap table yourself, quit gdb again, and make a new keytable:

 &gt; make change-x11keymaptable

A window will open. Watch the window's title bar, and follow the instructions.

When done, re-run AROS. RAros + W should now open a shell.

Next, compile your program with gdb support.


When you start GDB is there a warning which says

   warning: File &quot;&lt;whatever&gt;/.gdbinit&quot; auto-loading has been declined by your `auto-load safe-path' set to ...

If so start gdb with &quot;-ix .gdbinit&quot;


&lt;pre&gt;
Summary - In short:

* build AROS with debugging support (i.e. ./configure --enable-debug=all)
* build your application with debugging support (i.e. option -g)
* run AROS in the GNU debugger (you may use the GUI frontend &quot;ddd&quot; which simplifies usage a bit)
* start your application
* use the commands &quot;findaddr&quot; and &quot;add-symbol-file&quot; as written in the debugging manual
* if the debugger doesn't find the source code of your application use the &quot;dir&quot; command of the debugger. 
&lt;/pre&gt;

===How to use gdb===

In AROS open a shell, then (in host shell) use CTRL-Z to go into gdb. Use &quot;b Exec_CreatePool&quot; (one of the functions used early on by startup code in programs) to add a breakpoint, then &quot;cont&quot; and gdb will interrupt somewhere early during startup of &quot;program&quot;. Use &quot;bt&quot; to show backtrace and &quot;loadseg&quot; for &quot;??&quot; entries. One of them will be for &quot;program&quot;. After that you can use &quot;disassemble program&quot;.

One thing you need to make sure is that .gdbinit you have in your build directory is the same as in source tree. It has been modified some time ago, but the build system does not refresh it - you need to copy it manually

To recap, please read our debugging [http://aros.sourceforge.net/documentation/developers/debugging.php manual]:


To detect segfaulting when loading, try...

 ./configure—enable-debug—with-optimization=&quot;-O2&quot;

Because crash or no crash may depend on optimization. For newer compilers maybe this helps...

 --with-optimization=-&quot;-O2 -fno-strict-aliasing&quot;

One way to make crashes less random (more easily reproducible) is to activate the munging of free memory in rom/exec/freemem.c which is normally commented out:

&lt;pre&gt;
Index: freemem.c
===================================================================
--- freemem.c   (revision 34289)
+++ freemem.c   (working copy)
@@ -154,11 +154,12 @@
         * created with their TCB placed in the tc_MemEntry list. The workaround
         * is to avoid munging when FreeMem() is called with task switching disabled.
         */
+
        /* DOH! it doesn't work even this way. What's wrong???
-        *
-        * if ((SysBase-&gt;TDNestCnt &lt; 0) &amp;&amp; (SysBase-&gt;IDNestCnt &lt; 0))
-        *      MUNGE_BLOCK(memoryBlock, MEMFILL_FREE, byteSize);
         */
+
+       if ((SysBase-&gt;TDNestCnt &lt; 0) &amp;&amp; (SysBase-&gt;IDNestCnt &lt; 0))
+           MUNGE_BLOCK(memoryBlock, MEMFILL_FREE, byteSize);

     }
&lt;/pre&gt;

Mungwall can be turned on at runtime. Currently this works in all hosted versions. Just specify &quot;mungwall&quot; on kernel command line and it works. It can work on native too. In order to enable it you need to parse kernel command line, and if &quot;mungwall&quot; is present, set EXECF_MungWall bit in IntExecBase.IntFlags.

This needs to be done before the first AllocMem() for obvious reasons. And never reset back this flag! If you change it on a working system, you are doomed.

Hosted ports do the processing in rom/exec/prepareexecbase.c --enable-debug=mungwall option in configure still works but is going obsolete.  A kludge in rom/exec/allocmem.c is responsible for this and it needs to be removed when the transition is done.

BTW,  on  i386-pc  port it can be activated by &quot;mungwall&quot; argument on command line, you don't need to rebuild AROS.
New mungwall affects not only AllocMem()/FreeMem(), but also pools. I also tested it with AllocAbs(), seems to work correctly.

Runtime mungwall works on:

* pc-i386
* pc-x86_64
* linux-i386
* linux-x86_64
* darwin-x86
* linux-ppc

Works on all hosted ports, if the port itself is working.

* amiga-m68k
* Not on sam440-ppc and efika-chrp-ppc, even if they would be able to be built at moment. Does not work on (for now, need NVRAM support)

When starting my freshly rebuilt i386-linux-aros which was compiled with full debugging support I get sometimes the error &quot;Program exited with code 0377&quot;. Add the following to your .gdbinit: 
 set follow-fork-mode child

Here are some of the custom AROS gdb functions (defined in &quot;.gdbinit&quot; file) to resolve &quot;in ?? ()&quot; entries in backtrace: 
&lt;pre&gt;
#0 0xb7ffd424 in __kernel_vsyscall ()
#1 0xb7e2a657 in sigsuspend () from /lib/libc.so.6
#2 0xb7c63900 in ?? ()
#3 0xb7c640e3 in ?? ()
#4 0xb7c641e0 in ?? ()
&lt;/pre&gt;

You can use

 loadseg 0xb7c63900
 loadframe 2
or
 loadbt
and some others. Use &quot;help &quot; for a little help text. If the commands do not work try &quot;loadkick&quot; first.


Use &quot;thistask&quot;, &quot;taskready&quot;, &quot;taskwait&quot; to get list of AROS tasks. &quot;bttask &quot; shows backtrace of a task which is in ready or in wait queue and &quot;loadseg&quot; to resolve &quot;??&quot; entries in it's backtrace (&quot;loadframe&quot; would not work as it assume current running task).

===Native debugging tools for AROS===

 to enable debugging at boot time entering the GRUB menu editing line (E key) and adding &quot;debug=memory&quot; to your boot line, then press Ctrl+X to complete booting.


SYS:Tools/Debug/'''Bifteck'''

Open a shell and enter the line below to run Biftek and grab the debug messages collected in RAM into a text file.

 tools/debug/bifteck &gt; ram:debug.txt

and certainly does not open a window. It is a shell tool and only dumps data located from the debug location.
It is therefore important to 'catch' that debug data as soon as possible (before it gets overridden). You should invoke bifteck at the first opportunity before doing anything else.  You can use the TO option to store bifteck output to a file or you can pipe it manually to a file.  


SYS:Tools/Debug/'''Sashimi''' - displays error messages

One suggestion is to do a bug() debugging. Each time bug() is executed it will be output on sashimi. 
You include &lt;aros/debug.h&gt; and place bug(&quot;something\n&quot;); in your source code at location though which control passes.

To get the output - open an aros shell

 SYS:Tools/Debug/sashimi &gt; RAM:out.txt

'''Ctrl C''' to end the output to the RAM Disk.

# open shell, and type
# ram: (to switch to ram drive)
# System:Tools/Debug/Sashimi &gt; mylogfile.txt
# open AHI prefs using wanderer (or use another opened shell)
# play test sound
# close AHI prefs
# shell still open with Sashimi running: press ctrl-c to break Sashimi and return to prompt.
# in shell: copy mylogfile.txt System: (or to your required location)


SYS:Utilities/'''Snoopy''' - monitors OS function calls, run &quot;Sashimi&quot; to see Snoopy's output


SYS:Tools/'''WiMP'''    - the Window (and Screens) Manipulation Program

You can use the -E option of gcc to find out how preprocessor macros are expanded.

===Errors===

crash in strcasecmp usually means that one of its arguments is NULL.

empty space between these two names, prossibly some invisible character 

Old Amiga [http://www.amigacoding.com/index.php?title=Guru_codes&amp;redirect=no Guru Codes]

If the crash is in intuition. Sometimes, if it relates to text, a null pointer sets it off. 
an uninitialised pointer can have any address (this is a common fault).


Compiling on 64bit, Many old code would not properly typecast when doing pointer-integer conversions and thus at least throw a warning. This can easily be located and fixed.

[http://www.aros.org/cs/documentation/developers/app-dev/portable.php Portable code] 

* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.
* Fix (change IPTR/SIPTR back to ULONG/LONG) the few places which really rely on ULONG/LONG being exactly 32 bit. That's for things like pixel (ARGB) buffers, structs written/read to disk, colormaps, but probably not much else.

Then again, many current compilers also throw a warning when you try to assign a pointer value to an integer and the integer is possibly too small. This happens under .NET for example when a 64 bit pointer is assigned to something like an ULONG - so exactly the case which you described.


=== AI ===
                  Multimodal
                   Context
                   Prompt
                    &lt;---
  Model &lt;---&gt; Agent ---&gt; End user
 engine 

 Gemini      LMStudio
  Qwen       Comfyui
   etc

Recent, self hosting locally on laptops, mini pcs or desktops with '''quantization''' 4bit has reduced memory requirements but still require 16Gb+ and no high end gpu for text based 

*[https://lmstudio.ai/download LMstudio single gpu],

Google Gemma 4 Model 
*[ 12B QAT] 


Alibaba Cloud's [https://huggingface.co/ Qwen] team series of large language models LLMs 
*[https://huggingface.co/models?other=qwen3 Qwen 3], [], 
*[https://huggingface.co/models?other=qwen2 Qwen 2], [https://huggingface.co/Qwen/Qwen2.5-Coder-32B qwen 2.5 Coder],  


Small models 
*[ glm-ocr]
*[ medGemma]
*[ qwen 3.5-4b]
*[https://github.com/sipeed/picoclaw picoclaw claude] 


Bigger LLMs but with settings 
*[https://ollama.com/download Ollama single gpu]
*[https://github.com/ggml-org/llama.cpp/releases llama.CPP multi gpus],
*[ VLM multiple gpus],
Multimedia 
*[ Kimi K3], 


For the full experience 
#Training learning using 1+ high end GPUs at least 16GB VRAM per GPU card or 64Gb+ of unified, 16Core CPU with at least 64Gb of RAM system memory, though training can take weeks 
#Inference with custom asics or GPUs 

*[ MiniMax H3] for audio and video but gpu 8Gb+ 
*[https://github.com/jamiepine/voicebox voicebox]
*[https://github.com/ideogram-oss/ideogram4 ideogram4]
*[https://github.com/calesthio/OpenMontage OpenMontage]

&lt;pre&gt;
Text to Audio --\
Text to Video --/ Reference Video --&gt; Video and Audio output 
&lt;/pre&gt;

=== Linux ===

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/* 1. Header for your name,date,purpose of program.
2. Pre-processor directives. This will include the #includes for files you want to add. 
3. Includes for function prototypes if necessary.
4. Main()
Create Pointers for Libraries and any Window you want to open.
5. Open necessary libraries.
6. Check if open exit program if fail.
7. Open a window exit program if fail.
8. Add your program
9. Close Window
10 Close Libraries.
11 End Program. */

/* standard os included headers &lt;.h&gt; */
#include &lt;dos/dos.h&gt;
#include &lt;dos/dosasl.h&gt;
#include &lt;dos/dosextens.h&gt;
#include &lt;dos/exall.h&gt;
#include &lt;dos/rdargs.h&gt;
#include &lt;exec/memory.h&gt;
#include &lt;exec/types.h&gt;
#include &lt;utility/utility.h&gt;
#include &lt;intuition/intuition.h&gt;

/* define as unresolved external references (proto/xxx.h) and compiler will link to auto(matically) open library */ 
#include &lt;proto/arossupport.h&gt;
#include &lt;proto/dos.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/graphics.h&gt;
#include &lt;proto/cybergraphics.h&gt;
#include &lt;proto/datatypes.h&gt;
#include &lt;proto/icon.h&gt;

#include &lt;workbench/workbench.h&gt;
#include &lt;workbench/icon.h&gt;

#include &lt;datatypes/pictureclass.h&gt;

#include &lt;proto/muimaster.h&gt;
#include &lt;libraries/mui.h&gt;

#include proto/bsdsocket.h

#include &lt;ctype.h&gt;
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;string.h&gt;

/* my own headers &quot;.h&quot; */

#define CTRL_C      (SetSignal(0L,0L) &amp; SIGBREAKF_CTRL_C)
#define  isDir(fib) ((fib)-&gt;fib_DirEntryType &gt;= 0)

#define ARG_TEMPLATE    &quot;FILE/A,ALL/S,QUIET/S,W=WIDTH/N,H=HEIGHT/N,M=METHOD,DEFTOOL&quot;

int main(void)
{


	return retval;
} /* main */
&lt;/syntaxhighlight&gt;

If you used c++, there is not yet c++ support in our shared library system. 
The easiest way to create / compile a shared library would be to use the AROS build system but the libraries can be created manually. You have to create a ROMTAG structure and some header files.  

A shared library is built with the %build_module macro with a line like this:

 %build_module mmake=MetaTarget modname=mylib modtype=library files=SourceFiles 

This macro can build different AROS module types, like devices, Zune classes, HIDDs, etc.

&lt;pre&gt;
##begin config
version 1.0
##end config

##begin functionlist
void func1(LONG a, LONG b)
int func2(char *s, ULONG a)
##end functionlist
&lt;/pre&gt;

There is more [http://aros.sourceforge.net/documentation/developers/sys-dev/libraries.php here]

Alternatively,  

&lt;pre&gt;
#ifndef LIB_H
#define LIB_H

#define __NOLIBBASE__

#include &lt;exec/libraries.h&gt;
#include &lt;exec/semaphores.h&gt;
#include &lt;dos/dos.h&gt;

#ifdef __AROS__
//#include &lt;aros/debug.h&gt;
#define reg(x)
#define __saveds
#endif

#define USESYSBASE struct ExecBase *SysBase = Base-&gt;My_SysBase;

struct MyTestBase
{
  struct Library   My_Test_Lib;
	struct ExecBase *My_SysBase;
	APTR             My_SegList;
  int              testint;
};

#endif
&lt;/pre&gt;

&lt;pre&gt;
/*--------------------------------------------------------------------------*/
/* Resident header written for mytest.library */
/*--------------------------------------------------------------------------*/

#define __NOLIBBASE__

#define VERSION         1
#define REVISION        0

#define LIBHEADNAME     mytest
#define LIBHEADNAMESTR &quot;mytest&quot;
#define COMPDATE        &quot;04.10.2015&quot;
#define VERS            &quot;1.0&quot;

#define LIBBASETYPE 	struct MyTestBase
#define LIBBASETYPEPTR  LIBBASETYPE *

#include &lt;aros/debug.h&gt;
#include &lt;exec/exec.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;exec/resident.h&gt;
#include &lt;exec/nodes.h&gt;
#include &lt;exec/libraries.h&gt;
#include &lt;aros/symbolsets.h&gt;
#include &quot;lib.h&quot;

const UBYTE lib_name[] = LIBHEADNAMESTR &quot;.library&quot;;

const UBYTE lib_id[] = &quot;$VER: &quot; LIBHEADNAMESTR &quot;.library &quot; VERS &quot; (&quot; COMPDATE &quot;) by ALB42\n&quot;;

extern const APTR FuncTable[];

AROS_UFP3 (LIBBASETYPEPTR, InitLib,
    AROS_UFPA(LIBBASETYPEPTR, Base, D0),
    AROS_UFPA(BPTR, seglist, A0),
    AROS_UFPA(struct ExecBase *, sysbase, A6)
);

static struct LibInitStruct
{
    IPTR                   LibSize;
    const APTR             *FuncTable;
    const struct DataTable *DataTable;
    APTR                    InitFunc;
}
const LibInitStruct =
{
    sizeof(LIBBASETYPE),
    FuncTable,
    NULL,
    (APTR)InitLib
};

const struct Resident romtag =
{
  RTC_MATCHWORD,              /* match word */
  (APTR)&amp;romtag,              /* back pointer */
  (APTR)(&amp;romtag + 1),        /* skip pointer */
  RTF_AUTOINIT | RTF_EXTENDED,/* flags */
  VERSION,                    /* version */
  NT_LIBRARY,                 /* type of module */
  0,                          /* init priority */
  (STRPTR)lib_name,           /* module name */
  (STRPTR)lib_id + 6,
  (APTR)&amp;LibInitStruct,
  REVISION, NULL
};

AROS_UFH3 (LIBBASETYPEPTR, InitLib,
    AROS_UFHA(LIBBASETYPEPTR, Base, D0),
    AROS_UFHA(BPTR, seglist, A0),
    AROS_UFHA(struct ExecBase *, sysbase, A6)
    )
{
    AROS_USERFUNC_INIT
    
    Base-&gt;My_SegList = seglist;
    Base-&gt;My_SysBase = (APTR)sysbase;
    Base-&gt;testint = 0;
    
    USESYSBASE
    bug(&quot;InitLib\n&quot;);
    
    if (!set_open_libraries())
    {
      set_close_libraries();
      return NULL;
    }
    
    return Base;
    
    AROS_USERFUNC_EXIT
}

AROS_LH1(LIBBASETYPEPTR, LibOpen,
    AROS_LHA (ULONG, version, D0),
    LIBBASETYPEPTR, Base, 1, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    
    USESYSBASE
    bug(&quot;LibOpen\n&quot;);

    (void)version;
    
    Base-&gt;My_Test_Lib.lib_OpenCnt++;
    return Base;

    AROS_LIBFUNC_EXIT
    
}

__saveds APTR LibExpungeInternal(LIBBASETYPE *Base reg(a6))
{
  USESYSBASE
  APTR seglist;
  bug(&quot;LibExpungeInternal\n&quot;);

  if (Base-&gt;My_Test_Lib.lib_OpenCnt)
  {
    return 0;
  }

  seglist = Base-&gt;My_SegList;

  Forbid();
  Remove((struct Node*)Base);
  Permit();
  FreeMem((APTR)Base - Base-&gt;My_Test_Lib.lib_NegSize, (LONG)Base-&gt;My_Test_Lib.lib_PosSize +
    (LONG)Base-&gt;My_Test_Lib.lib_NegSize);
  
  set_close_libraries();
  return seglist;
}

AROS_LH0(BPTR, LibClose,
    LIBBASETYPEPTR, Base, 2, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;LibClose\n&quot;);

    if (!(--Base-&gt;My_Test_Lib.lib_OpenCnt))
    {
      return LibExpungeInternal(Base);          
    }
    return 0;
	
    AROS_LIBFUNC_EXIT
}

AROS_LH1(BPTR, LibExpunge,
    AROS_LHA(LIBBASETYPEPTR, Base, D0),
    struct ExecBase *, sysBase, 3, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT

    (void)sysBase;
    
    USESYSBASE
    bug(&quot;LibExpunge\n&quot;);

    return LibExpungeInternal(Base);
	
    AROS_LIBFUNC_EXIT
}

AROS_LH0(LIBBASETYPEPTR, LibReserved,
    LIBBASETYPEPTR, Base, 4, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;LibReserved\n&quot;);

    return 0;
    //return (APTR)LibReserved();
    
    AROS_LIBFUNC_EXIT
}


// Space for your own functions
// do not forget to update the FuncTable as well

AROS_LH1(int, TestFunction,
    AROS_LHA(int, TestValue, D0),
    LIBBASETYPEPTR, Base, 5, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;TestFunction\n&quot;);

    Base-&gt;testint = TestValue + Base-&gt;testint;
    
    return Base-&gt;testint;
    
    AROS_LIBFUNC_EXIT
}

// Functable -&gt; Table of all functions in the Library, in right order - important!

const APTR FuncTable[] = 
{
    &amp;AROS_SLIB_ENTRY(LibOpen,LIBHEADNAME,1),
    &amp;AROS_SLIB_ENTRY(LibClose,LIBHEADNAME,2),
    &amp;AROS_SLIB_ENTRY(LibExpunge,LIBHEADNAME,3),
    &amp;AROS_SLIB_ENTRY(LibReserved,LIBHEADNAME,4),
    &amp;AROS_SLIB_ENTRY(TestFunction,LIBHEADNAME,5),
    (void *)-1
};

// AutoInit stuff
void *__PROGRAM_ENTRIES__symbol_set_handler_missing;
void *__LIBS__symbol_set_handler_missing;
// end of AutoInitStuff
&lt;/pre&gt;

Makefile
&lt;pre&gt;
VPATH = 
CFLAGS = -O2 -g -fomit-frame-pointer -W -Wall -Wno-parentheses
CC = i386-aros-gcc
LD = i386-aros-gcc
LDFLAGS = -nostartfiles -Wl,-Map -Xlinker linkermap
LIBS = -lautoinit -llibinit
STRIP = i386-aros-strip --strip-unneeded --remove-section .comment

OBJS = lib_header.o 

all: mytest.library

mytest.library: $(OBJS)
	$(LD) $(LDFLAGS) $^ $(LIBS) -o $@

lib_header.o: lib_header.c lib.h

clean:
	rm -f *.o *.library *.ppu testlibrary linkermap
&lt;/pre&gt;


Porting UNIX library to AROS - dealing with static variables which would make it easy to port such libraries to AROS, keeping the benefits of sharing them on disk, but losing the benefit of actually sharing them in memory.

Our problem arises by the fact we want to share the actual code (the .text section of the library) and constant data, but we need to have per-task .bss and .data sections. If we get rid of our intention to share the .text and .rodata sections, things get quite easy: just load and relocate the library whenever it's open, by whoever it's open. It's like statically linking the library into the executable, except that the final linking is done at runtime.

In the V0 branch, in workbench/hidds/hidd.nouveau was committed pcimock.hidd. This is a pci driver that allows mocking real PCI devices under linux-hosted. The main idea is to be able to run the real hardware driver under linux-hosted with as little changes as possible (some changes will always be needed though unless someone wants to write complete device simulator) so that driver's code paths can be executed and debugged using gdb. This was a very helpful capability when porting nouveau. Now it is externalized from nouveau.hidd and can be used by other people porting drivers. The pcimock.hidd can currently mock 4 different nvidia cards, 1 AGP bridge and also mock irq.hidd.

What's the difference between this driver and the pcilinux.hidd? I used that one to develop many different HW drivers for aros. As far as I understood the intention of pcilinux.hidd it is supposed to get access to real hardware that is running under linux. The pcimock.hidd goal is to mock the hardware. For example my dev box is a PCIE system, but I still would like to run the AGP codes paths in nouveau under linux-hosted to check if they don't seg fault. The other case would be to run codes paths for hardware that the developer does not have (Fermi cards in my case). In the case of pcimock.hidd, the AROS driver's code paths will execute as long as you add proper mocking (for example fill in PCI config area or values for registers in BARs). This is an advantage for ported drivers - the code should already work (since it worked on another system) but there might have been mistakes made during porting which can be detected easily with gdb.

In case you are writing your driver from scratch, pcilinux.hidd hidd will give you more advantage, since you can actually access the real hardware from linux-hosted.


== Misc ==

===APL, MPL, BSD, GPL and LGPL Licences===

The majority of AROS sources in licensed under AROS Public License ([http://aros.sourceforge.net/license.html APL]) which (to a degree) protects us from someone taking AROS sources and not contributing improvements back (for example MorphOS took some AROS source and then contributed changes back)

It is written to allow the use of AROS code in other open source or commercial projects without exception whilst providing a mechanism so that improvements/additions can find their way back to the original source in one form or another.

There are &quot;3rd&quot; party applications used by AROS that do not fall under this license, which are an extra &quot;Contrib&quot; download for convenience.

Anyone can port GPL-ed network and sound drivers as AROSTCP and AHI are GPLed. Direct using (porting) [http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs GPL]-ed code in other parts of AROS (gfx, sata, usb) is not possible because AROS license is not compatible with GPL. You need to utilize permissive licensed code like BSD or MIT/X11.


BSD and MPL license are the closest to APL.

APL however is not so compatible with LGPL/GPL.

LGPL case - you cannot statically combine APL code with LGPL. You can, however thank to LGPL being &quot;lesser&quot; restrictive, use LGPL dynamically loaded libraries in APL codes.

GPL case - you cannot combine APL code with GPL in any way if there is no explicit clause by GPLed code authors allowing that. If you do combine APL with GPL in &quot;bad&quot; ways described above - you have a problem (you violate GPL). This problem might result in everything in AROS becoming GPL or everything running or AROS becoming GPL (here I'm not sure really). The other scenario is that you are not allowed to legally distribute such code at all. To be honest I have grasped how to violate GPL, but I'm still no exactly sure what happens when you violate it (but I'm sure it's not anything nice)

GPL software can run on top of non-GPL &quot;system components&quot; (see system components exception of GPL), but the other way around (non-GPL using GPL) leads to problems. This means applications like scout, or Quake III are ok (in the majority of cases).

Theres no reason GPL drivers cannot be ported - but they cant be in AROS's ROM (requires linking APL code with GPL), nor can AROS depend on them (e.g. they must use existing apis).
If they are launched (dynamically linked) by a user action that is allowed. It is also allowed to distribute such binaries together for convenience.

GPL is not about statical or dynamic linking but is about executing process and function calls.


These components - SFS, isapnp, Zune texteditor, AHi, network drivers, freetype, openuirl, BHFormat, Edit and (&quot; dynamically loaded libraries&quot;) are LGPL, not GPL. Mesa/Nouveau stuff is MIT. Some user tools are GPL though.

'''AROS (system)'''
* system components (libraries/classes/devices/etc) cannot be GPL as they would propagate GPL to complete system as well as GPL is not compatible with MPL from which APL is based 
* system components can be LGPL v2 or a permissive license (MIT/BSD)
* system applications can be anything you like (but still I would prefer APL or permissive so the code can be reused if needed)

'''Contrib:'''
* no rules - contrib does not impact AROS system since nothing in AROS system depends on contrib.

About stealing code: The chances of this happening is exactly the same whether we are APL or GPL. If any closed-source option wanted to do it, there is no one that can validate otherwise. MorphOS has used some AROS codes, but contributed changes back.

The rationale behind APL is that while it guarantees that the original developer will get the improvements back (to a certain degree - file based), the person who uses the codes does not have to open his original codes. BSD does not guarantee that the original developer gets improvements. GPL requires the person using the codes to open his codes as well.

The copyright holders needs to stay - we just need information from them that the codes are available under APL (for example a checked-in file like in case of Poseidon). We don't do transfer of copyrights.

; Ultimately what can and cannot be done is up to the author(s) - not the licence.

===AROS source code tree===

* http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-trunk.txt
* http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-contrib.txt


Found this interesting (non-GPL) licensing 'anomaly' - to keep in mind for distributors.

Programs that lose their license if sold (&quot;non-profit only&quot; licensed):
  contrib/aminet/comm/term/TinyTerminal
  contrib/aminet/dev/basic/bwBASIC
  contrib/aminet/text/edit/xdme
  contrib/fish/aroach
  contrib/fish/lotto
  contrib/fish/shuffle
  contrib/fish/touch
  + cdvdfs.


Here is a list of all the GPL/GPLv2/GPLv3 licenses fossology found, what have explicit licenses in their comments.


 excluded LGPL, BSD/GPL dual licensed and programs (such as Prefs/Edit and BHFormat)

&lt;pre&gt;
AROS/rom/dbus/include/  AFL_v2.1 ,GPL_v2+  (supposedly AFL &lt; 3 is GPL incompatible) 
AROS/workbench/classes/zune/betterstring/include/  GPL_v2+
AROS/workbench/classes/zune/texteditor/include/  GPL_v2+
AROS/workbench/classes/datatypes/gemimage/ GPL_v2+ GPL
AROS/workbench/classes/datatypes/degas/  GPL_v2+
AROS/workbench/libs/openurl/README: GPL
AROS/workbench/network/smbfs/documentation/  GPL_v2
AROS/workbench/network/smbfs/source_code/  GPL_v2+
AROS/workbench/network/stacks/AROSTCP/bsdsocket/kern/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/mmakefile.src conf.h  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/sys/  CMU ,GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/net/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/api/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/conf/conf.h: GPL_v2
AROS/workbench/network/stacks/AROSTCP/netinclude/net/radix.h: CMU ,GPL_v2
AROS/workbench/devs/AHI/AHI/  GPL_v2+
AROS/workbench/devs/AHI/AddAudioModes/ GPL_v2+  AROS/workbench/devs/AHI/AddAudioModes/COPYING: GPL 
AROS/workbench/devs/AHI/Docs/texinfo.tex: GPL_v2+
AROS/workbench/devs/AHI/COPYING: GPL
AROS/workbench/devs/AHI/Drivers/EMU10kx/  GPL_v2+
AROS/workbench/devs/AHI/AHI-Handler/  GPL_v2+
AROS/workbench/devs/networks/rtl8029/  GPL   GPL_v2+
AROS/workbench/devs/networks/pcnet32/  GPL   GPL_v2+
AROS/workbench/devs/networks/ppp/LEGAL: GPL
AROS/workbench/devs/networks/atheros5000/  GPL_v2+
AROS/workbench/devs/networks/rhine/  GPL_v2+
AROS/workbench/devs/networks/nForce/  GPL_v2+  GPL
AROS/workbench/devs/networks/prism2/  GPL  GPL_v2+
AROS/workbench/devs/networks/fec/LEGAL: GPL
AROS/workbench/devs/networks/rtl8139/  GPL  GPL_v2+
AROS/workbench/devs/networks/etherlink3/  GPL  GPL_v2+
AROS/workbench/devs/networks/intelpro100/  GPL  GPL_v2+
AROS/workbench/devs/networks/rtl8169/  GPL   GPL_v2+
AROS/workbench/devs/networks/emac/   GPL   GPL_v2+
AROS/workbench/devs/networks/rtl8168/  GPL  GPL_v2+
AROS/workbench/devs/networks/realtek8180/   GPL_v2+
AROS/workbench/devs/networks/via-rhine/via-rhine.c: GPL_v2+
AROS/workbench/devs/networks/via-rhine/   GPL  GPL_v2+
AROS/workbench/devs/networks/e1000/  GPL_v2
AROS/workbench/devs/networks/sis900/  GPL   GPL_v2+
&lt;/pre&gt;

AHI: it has special provisions (COPYING.DRIVERS). The library is LGPL, preferences software is GPL and drivers can be anything without breaking GPL/LGPL.

Network stack: well, we are long overdue for a new, IPv6 enabled network stack anyway, anyone interested? ;) Seriously though it seems like the glue code is GPL and as all the drivers. However some of the drivers are our own code, so they could be relicensed to LGPL.

 Same filter as the AROS trunk list. These should all be libraries or plugins - no programs.

&lt;pre&gt;
contrib/regina/utsname.h: GPL_v2+

contrib/mui/classes/nlist/include/default-align.h: GPL_v2+
contrib/mui/classes/nlist/include/amiga-align.h: GPL_v2+

contrib/mui/classes/BWins/include/MUI/BWin_mcc.h: GPL
contrib/mui/classes/BWins/include/BWin_private_mcc.h: GPL
contrib/mui/classes/BWins/COPYING: GPL_v2
contrib/mui/classes/BWins/MCC_BWins.readme: GPL_v2

contrib/mui/classes/thebar/include/default-align.h: GPL_v2+
contrib/mui/classes/thebar/include/amiga-align.h: GPL_v2+

contrib/gfx/libs/wazp3d/LEGAL: GPL
contrib/gfx/libs/wazp3d/Wazp3D.readme: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d.c: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d_opengl.h: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d_opengl.c: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/Wazp3D.h: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/Wazp3D.c: GPL

contrib/libs/mpega/  GPL_v2+
&lt;/pre&gt;

http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-contrib.txt

===Types===

On AROS following rules apply:
&lt;pre&gt; 
1. BYTE/UBYTE is 8bit, WORD/UWORD is 16bit, LONG/ULONG is 32bit, QUAD/UQUAD is 64bit, the types are comparable with stdint types (int8_t, int16_t, int32_t, int64_t)
2. IPTR/SIPTR are integer types large enough to fit pointer, that is sizeof(IPTR) = sizeof(APTR) = 4 on 32bit system, and = 8 on 64bit system
3. ti_Data in TagList is large enough to hold a IPTR/APTR type.
4. never store a pointer in integer of type LONG. It may work (if the pointer has upper 32bits clear), but does not have to. Compiler should warn you about that.
5. If you are unsure about point 4, allocate your memory with MEMF_31BIT flag set. But don't expect that AROS internals will do the same.
&lt;/pre&gt; 
point 4 is actually important.


* UBYTE/BYTE for 8bit
* UWORD/WORD for 16bit
* ULONG/LONG for 32bit
* UQUAD/QUAD for 64bit

&lt;pre&gt;
UBYTE    Unsigned 8 bit integer variable (byte).
BYTE     Signed 8 bit integer variable (byte).
UWORD    Unsigned 16 bit integer variable (word).
WORD     Signed 16 bit integer variable (word).
ULONG    Unsigned 32 bit integer variable (longword).
LONG     Signed 32 bit integer variable (longword).
FLOAT    32 bit IEEE floating point variable.
UQUAD    Unsigned 64 bit integer variable.
QUAD     Signed 64 bit integer variable.
DOUBLE   64bit IEEE floating point variable.
BOOL     Boolean variable, TRUE and FALSE are also defined in exec/types.h.
VOID     Void.

APTR     A generic pointer for multiple purposes - Arrays.
STRPTR   A pointer to a null-terminated string.
IPTR     Really important in AROS, the only way to declare a field that can contain both: an integer or a pointer.
&lt;/pre&gt;

if you want to write really portable app, you may be interested in standard datatypes defined in C99: int8_t, uint8_t, int16_t, uint16_t, int32_t, uint32_t, int64_t, uint64_t, intptr_t, uintptr_t. They are all defined in inttypes.h include file.

In exec/types.h the following short-cuts are typedef'd. They are used often in AROS, so you should nearly always include exec/types.h and soon only they will be removed from sys/_types.h include, all types are now defined in include files named aros/types/xxx.h.

(Preparation for C library split; sys/xxx.h include will only be available there when compiling with POSIX C library)


Compiler specific types, like int and long might change their size. In case of AROS, similar to linux, int remains 32 bit whereas long grows to 64 bits in size.

If you use Amiga-like data types, i.e. BYTE/UBYTE, WORD/UWORD, LONG/ULONG and QUAD/UQUAD or the C99 standard types (uint8_t and so on, see stdint.h include) then you should have less issues to solve than by using types without size guarantee.

Of course, all pointers grow to 64 bytes using 64bit cpu. Most of the code can be just recompiled and will work. In rare cases, where e.g. pointers are casted to integers, a special care must be taken. Especially in the cases, where pointer is casted to LONG/ULONG (this code will break on 64 bit AROS) e.g.  '#define IPTR ULONG'.

With compiler delint patches which the majority of them are simple casting issues to make the compiler happy. Notice some of the changes involve introducing double casts. In very recent versions of GCC. Yes, the bulk of the double casts are for converting 32 bit addresses (ie from a 32 bit PCI DMA address register) to a 64 bit pointer. First cast is to IPTR (to expand to 64 bits, and prevent sign extension if the address is above 0x7FFFFFFF), and then to APTR.

ULONG != IPTR except on 32bit .. so if you need to store pointers make sure and use IPTR and not ULONG (which some old code does). For this reason things like Taglist elements are 64bit (since the tag data can be a pointer). 
If your passing items on the stack you should use the STACKED attribute to make sure they are correctly aligned (on 64bit all items on the stack are 64bit..)

There is more issues like using &quot;== 0L&quot; causes problems.

===Endian===

*BE 
*LE

Use the macros from &lt;endian.h&gt; instead making a guess based upon architecture defines
 
&lt;pre&gt;
#if _BYTE_ORDER == _BIG_ENDIAN

#elif _BYTE_ORDER == _LITTLE_ENDIAN

#else
+
#error &lt;whatever.h&gt; - Byte order for this architecture is unsupported! 
&lt;/pre&gt;


===SVN and GIT===

If you want to help develop AROS OS itself, you can 

* view current GIT/SVN entries [http://aros.sourceforge.net/ Aros Org website] or [https://github.com/aros-development-team/AROS Github], [https://github.com/ezrec older ezrec mirror], [https://github.com/michalsc/AROS/ older mirror], [https://trac.aros.org/trac/timeline TRAC], [], 
* awaiting update [http://repo.or.cz/w/AROS.git git repo], [http://www.ohloh.net/p/aros/commits ohloh] or [https://svn.aros.org/svn/aros/trunk/ svn repo] and access [Git version git://repo.or.cz/AROS.git here], 
* deprecated [https://www.gitorious.org/aros/aros/commit/a7fda9e ARIX commits] or [https://gitorious.org/aros/aros GIT old]

If you have SVN access (early 2015 introduced a new SVN server, create a new account at trac aros org) and/or have obtained the source [http://aros.sourceforge.net/download.php AROS site] - you can compile the current build tools/environment using: 

 &gt; make development

and follow this [http://aros.sourceforge.net/documentation/developers/compiling.php#building procedure] or [https://github.com/apiraino/aros_guide Guide] 


https://trac.aros.org/trac#Developing

If you plan on contributing back changes, please post information about such changes first on this [http://mail.aros.org/mailman/listinfo/aros-dev/ mailing list] for more experience developers can validate whether they are correct.


Then there are the nightly build machines. They svn update before the build and run configure as one of the next steps. autoconf might be added to the nightly build scripts.

Our build relies on packages downloaded from Internet (SDL for example) - it always worked this way. The minimal requirement (when just building core AROS) is binutils and gcc. If you build contrib as well, you need many more packages to be downloaded.

https://gitorious.org/aros/aros/commits/crosstools-II

git://gitorious.org/aros/aros.git

Branch crosstools-II there is only one commit on top of ABI_V1 
&lt;pre&gt;
../../aros-src/AROS/configure --enable-ccache
--with-portssources=~/aros/Sources --target=pc-x86_64
--with-aros-toolchain-install=/home/weissms/media/data/aros/test/crosstools/pc-x86_64
&lt;/pre&gt;
and
&lt;pre&gt;
../../aros-src/AROS/configure --enable-ccache
--with-portssources=~/aros/Sources --target=pc-i386
--with-aros-toolchain-install=/home/weissms/media/data/aros/test/crosstools/pc-i386
&lt;/pre&gt;
build OK.


:''More information: [[Aros/Developer/Maintainer|AROS Maintainer Docs]]''

===SDI Calls===

Integrate the 'SDI'-headers to allow easier porting to all amiga-like platforms.

&lt;pre&gt;
PUTCHARPROTO( PutTheChar, char c, struct SPrintfStream *s  )
{
 // REAL CODE
}
&lt;/pre&gt;

have &quot;SDI_compiler.h&quot; and &quot;SDI_hook.h&quot; included

its more organized like

 #include SDI/SDI_hook.h

than

 #include SDI_hook.h

option 1 --- i also use when back porting from amiga's..

&lt;pre&gt;
#ifdef __AROS__
#include SDI/SDI_hook.h
#else
#include SDI_hook.h
#endif
&lt;/pre&gt;

also

you can add the -i include/sdi/ location if you do not want to add or edit any files.


Defining HOOKPROTO to IPTR name(struct IClass * cl, Object * obj, Msg msg); solved the problem

A MUI application most likely needs only the HOOKPROTOxxx SDI macros. They are compatible with AROS, only the attributes (hook, object attribute) must be given in the right order. examine compiler/include/aros/symbolsets.h (AROS_LIBREQ)

compiling mui stuff for aros setting -std=gnu99 is necessary (i have had -std=c99 most of the time).

===Locale with Flexcat===

Most languages have a locale, but not every app is localized, the only thing needed is to translate the &quot;catalog&quot; files. It is a case of locating the correct catalog and saving the translated version.

For every app that lacks of your language catalog and is localized anyway, you should find (in the sources) files related to locale:

* file.cd = catalog descriptor, contains base msg, with internal language (usually english)
* language.ct = catalog translation, contains every translated msg, indexed as in the file.cd.

Compare with other localized apps... Then, &quot;make my_app-catalogs&quot; should create and install your translated catalogs. ex : for, saying, sys:prefs/wanderer:

on root of AROS sources, type:
 &quot;make workbench-prefs-wanderer-catalogs&quot;
then (if you changed the .cd file):
 &quot;make workbench-prefs-wanderer&quot;

For apps not localized, you have to adapt their code to support it, if it is possible...

noticed the original .cd file has many (//) strings at the end of any voice, so added them also to the .ct file. 
That (//) is only for cd files. I'm highly recommending to use FlexCat for updating ct files, e.g. like this:

 flexcat app.cd deutsch.ct newctfile deutsch.ct

You'll get error checking and new entries are marked in the resulting ct file.

When editing .ct files, only change those lines containing translation and perhaps version string, nothing else.
The rest is up to the relevant tool, flexcat. In order to update your translation, type in the following in your shell:

 flexcat xyz.cd xyz.ct NEWCTFILE xyz_upd.ct COPYMSGNEW

This way you will not only make sure you have correct translation file but flexcat also pre-fills newly added strings with &quot;*** NEW *** text. Even better tool for checking cd/ct/catalog files is catcheck, but this one is sadly only available for AmigaOS/68k...

Some languages have variations, like portugues from portugal and portugues from brasil differs...

This is the way to go. I will have a look at language files, but basically if those two languages differ you have to do two separated set of translation files, yes.
(you could create a brazilian slang language localization too)

* At system level localization for one language is a dot language file.
(ex: locale:languages/klingon.language)

* At app level localization is a dot catalog file
(ex: locale:catalogs/klingon/system/libs/dos.catalog)

* At sources level, the dot ct file, and &quot;$language&quot; dot cd files and some building framework.
(ex: catalogs/my_app.ct catalogs/klingon.cd catalogs/mmakefile.src support.c support.h)

Please, use Flexcat to generate CT files: 
 FlexCat wanderer.cd NEWCTFILE=deutsch.ct

Then fill the first 2 lines with something useful:
&lt;pre&gt;
## version $VER: wanderer.catalog 1.1 (9.2.2006)
## language deutsch
&lt;/pre&gt;

You can even update the CT-File: (This adds the new strings)
 FlexCat wanderer.cd deutsch.ct NEWCTFILE=deutsch.ct


To compile a catalog you only need the .cd file and your translation (.ct file):
 FlexCat multiview.cd deutsch.ct CATALOG=MultiView.catalog


[http://murks-ide.svn.sourceforge.net/viewvc/murks-ide/trunk/src/Catalogs/flexcat_linux?revision=100 Linux version of FlexCat]

: [http://aros.sourceforge.net/documentation/developers/app-dev/localization.php#localization-for-non-developers More information]


A script which compares the required version (i.e. the version which an application/module etc. tries to open) with the version of the existing CT files. The result is in this table:

https://github.com/aros-translation-team/translations/wiki/Progress

The following cases are highlighted:

    n/a i.e. CT misses at all
    version in existing CT file is lower than the required version


It might be a bit difficult to participate if you haven't worked with Git before but alternatively you can send your CT files to our Slack channel.

When the ct file has been generated via flexcat (flexcat keyshow.cd NEWCTFILE=spanish.ct) it has the following header:

---------------------------------------------------------------------------------------------------------------
## version $VER: &lt;name&gt;.catalog &lt;ver&gt;.&lt;rev&gt; (04.01.2021)
## language nolanguage
## codeset 0
;
---------------------------------------------------------------------------------------------------------------

Those values &lt;ver&gt;.&lt;rev&gt; are the version and revision of the CT file for the languaje or are the values of the application being localized?

The &lt;ver&gt; part must match with version which the application tries to open. You can find the value either in the column &quot;Required Version&quot; in the table which I've linked above, our you can look in the git repository. For keyshow it would be https://github.com/aros-translation-team/keyshow. You can find in the file &quot;catalog_version.h&quot; the right version number.
The &lt;rev&gt; part starts for new CT files with 0 and should be increased every time the CT file is updated.

Updated several files and created a few more that were missing on the spanish catalog.

The catalogs are in Git repositories at https://github.com/aros-translation-team

a) You tell me your Github user name. I'll invite you. You can work directly with the Git repositories.

b) You create Github forks of the catalog repositories and create pull requests.

c) You send the CT files to mrustler  gmx de


===C Utils Misc===

The AROS source uses at several places the __DATE__ macro to fill the date entry of a $VER tag. Problem is that c:version doesn't understand that date format (e.g. &quot;May 21, 2011&quot;). As a result the output of e.g.
&gt; &quot;version c:shell full&quot; contains &quot;(null)&quot;. Is extending the version command to understand the format of __DATE__  the right solution for that problem?

AmigaOs compilers should use __AMIGADATE__ macro or similar form, if it isn't implemented it could be emulated in makefile: -D__AMIGADATE__=\&quot;$(shell date &quot;+%d.%m.%Y&quot;)\&quot;

BTW. I think DD.MM.YYYY is better format than &quot;Month DD YYY&quot; because &quot;Month DD YYY&quot; is not localized in any way.

&quot;strnicmp&quot; shouldn't work with NULL pointers

The Situation:

compiled a linklib using c++ object files (using the c++ cross compiler).
compiled a C stub that uses the linklib (using the c++ cross compiler).

Try to link them together (using the c++ cross compiler) with C object
files (using the normal target c compiler) that need to use -nostartup
= cant do because using the c++ files pulls in arosc (for stdio etc.) -
so wants to have the autoinit stuff present.

What can I do about this??

If it is possible to manually open it then what do I need to do exactly?

=== ENV ===

The philosophy behind ENV: is that keeping configuration files there allows you to  'Use'  preferences  by  keeping  a copy in ENVARC: intact. However in some cases (like this one) it is not required.

99% of the time that statement is true (not required) for pretty much every file in ENV: or do people change their default icons - and prefs settings - every boot?

There seem to be a bad habit of late with developers changing things to reflect their own personal preference when the change isn't actually necessary - It would be nice if people could refrain from doing that in the tree without at least discussing it on the dev-list first (and with good reasoning unless they committed said work in the first place..)

We're not keen on the pollution of the &quot;S:&quot; dir: it's meant to be for scripts. What's wrong with &quot;ENV:&quot;?
Only the fact that it takes up RAM. I  understand  that  for  PCs  with  several gigabytes of RAM this is
irrelevant. But let's remember about other machines. The philosophy behind ENV: is that keeping configuration files there allows you to  'Use'  preferences  by  keeping  a copy in ENVARC: intact.

However in some cases (like this one) it is not required.

How about implementing in the style of HappyENV then? RAM-disk handler that falls through to reading from ENVARC: if there is no such file stored in it already. Removes RAM usage for unchanged files, removes the need to copy ENVARC to ENV in startup-sequence. 
Shouldn't be too hard to make from AmberRAM, or even just extend AmberRAM to provide this service.

Is it feasable to build a special version of AmberRAM handling ENV: that will try and copy the requested file from ENVARC: if it isnt found in ENV: ? 
Additionaly it could mark closed &quot;files&quot; as untouched - and expunge them from ENV: after a period of time to free up additional RAM:, or when the system is running low on free memory?

Silenty disappearing files may not be a good plan. Would be nice if the following would work:

ASSIGN :ENV SYS:Prefs/Env-Arc ADD
ASSIGN :ENV RAM:ENV  ADD

Where new files put in ENV: end up in RAM:ENV, and opening files looks in RAM:ENV first, then SYS:Prefs/Env-Arc

Well - that's essentially what im proposing but without the assigns - or need for a RAM:ENV directory. 
Adding it as a feature of AmberRAM sounds like the most memory efficient way (one handler to load in RAM) but that's only if it is possible to make it handle ENV: additionally to RAM:, and if it is even possible to add the proposed functionality (...and how to make it enable it when accessing ENV:).

===(AS)MP support===

If one has to recompile software for SMP multi core, is there any thing special one has to do to get software to run?   
Use task.resource if you need to query information about what tasks are running, and clear msgports completely when they are allocated.

Most code should not need Forbid. Use Semaphores, Messages etc. to sync your own code. 

Accessing system structures is a different thing. Use the proper API whenever possible.

How single structures will be protected in the future is still a moving target, at least it is not documented. And you should never  use undocumented stuff  


Ideas on for SMP multi-core

Another suggestion is ... Forbid/Permit function calls are meant to halt multitasking so as no other task could intervene with what ever the calling task is doing, e.g. setting semaphores. Disable/Enable calls are meant to halt interrupts and as a side effect they also halt task switching.

One option is to make it compulsory to protect shared resources with semaphores and forbid the use of simple Forbid() calls as to protect something. Setting semaphore should be done if possible with atomic instructions (check and alter in one instruction). Or make the second concurrent ObtainSemaphore call halt the second calling task and force if possible a task switch which ever gives better results. 

Semaphores could store the owning tasks task pointer instead of boolean to make things easier.

As long as the CPU initiates the DMA transfers through the OS, and the OS ensures that the transferred memory is within the region accessible to the user initiating the transfer, everything is fine. The CPU is the conductor, and the CPU by that has the control of which DMA transfer is initiated and which is not.
All you need to do is to write device drivers reasonable. Hint: CachePreDMA and CachePostDMA exist.
All the Os has to do is to verify that the memory regions to be transferred are valid, and prohibit direct access to the DMA control registers from user space. None of these algorithms imply huge costs.
The current OS design doesn't really allow virtual memory in first place, Forbid() is again the problem.

[http://www.tbs-software.com/guide/index.php?guide=autodocs.doc%2Fmemory.doc&amp;node=1 memory.library API] seem to low level. IMHO the programs should not know how the swapping is implemented. I would just go for one new memory flag
MEMF_SWAPPABLE that indicates that a certain memory region or a whole memory pool won't be accessed during Forbid()/Permit() etc. It only solves part of the problem, it only implements virtual memory and not memory protection. For the latter you need to be able make certain memory inaccessible by other programs, some memory read-only for one task and read-write for other tasks, etc. And I think this should be done in the same Address Space in order to avoid you constantly need to swap between different address spaces. 
So to summarize, if there are programs using this API we may provide a wrapper layer to get them working but I am not convinced this API should be the reference API with whom to provide VM to AROS programs.

=== Variadic ===

variadic functions (i.e. functions with an arbitrary amount of arguments).

&lt;pre&gt;
    #include &lt;stdarg.h&gt;
    [...]

    char * STDARGS GetKeyWord(int value, char *def, ...)
    {
        [...]
        va_list va;
        [...]
        va_start(va, def);
        [...]
        va_end (args);

&lt;/pre&gt;

Please keep with using stdarg rather than having va casted to a LONG * type and varargs handled manually. Doing so, prevents tons of casting, where a simple va_arg can be used. So, string = *((char **) args) instead of string=va_arg(va, char *).

&lt;pre&gt;
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;

int printf (const char * format, ...)

{
    int     retval;
    va_list args;

    va_start (args, format);

    retval = vfprintf (stdout, format, args);

    va_end (args);

    fflush (stdout);

    return retval;
} /* printf */
&lt;/pre&gt;

Couldn't find varargs.h or stdarg.h. and have no use for AROS_SLOWSTACKHOOKS or AROS_SLOWSTACKTAGS.

GCC looks for stdarg.h in a different place: 
 /bin/linux-i386/tools/lib/gcc/i386-aros/4.2.2/include/stdarg.h

Here is a path for a &quot;normal&quot; header:
 bin/linux-i386/tools/lib/gcc/i386-aros/4.2.2/../../../../i386-aros/sys-include/aros/system.h


The use of vararg.h isn't supported by newer gcc versions. If you want your code to run on architectures that pass part of variadic arguments in a number of registers you need to use AROS_SLOWSTACK macros. Otherwise your program will not work on powerpc and x86_64 ports.

Of course the SLOWSTACK stuff is not needed in a function that can use va_list, va_start, va_arg and va_end. It's only needed if you want to write functions like DoMethod or similar.

 #include &lt;stdarg.h&gt;

should be enough no matter if you do cross or native compiling. If it does not work, something is wrong and should be corrected.

Stdarg.h is here, Development:lib/gcc/i386-aros/4.2.2/include/

...which is part of the compiler's default include paths. In other words, #include &lt;stdarg.h&gt; works out of the box, indeed. (sorry, I should have just tried it before invoking &quot;search&quot; or &quot;find&quot;...)

furthermore, myprintf() as shown above won't work, because...

 printf(format, args);

...is wrong - the second argument does not match printf() prototype, it expects a argument list, but args is of type va_list (obviously) - so one has to use...

 vfprintf(stdout, format, args);

...instead, just like in the original printf(), and add fflush(stdout).

additionally, one could use...

 int myarg = va_arg(args, int);

...between va_start() and va_end() to access individual arguments, where each call to va_arg() returns an argument casted to the desired type (here: &quot;int&quot;) from the list given (here: &quot;args&quot;) and advances to the next one.

wrapping up vfprintf() and modifying the format string now is a major speedup! no more backslash-n typing! this has been haunting me for years!

On MOS and AmigaOS, the NewObject variadic function is kept in the static library. It takes most of the parameters on the stack - thanks to that the implementation of NewObject calls the NewObjectA function. Everything works perfect, and the typical MUI macros may be easily used.

This, however, is not the case when you compile for AROS. Here, NewObject is a variadic macro, not a function. Thanks such approach we do not need any custom compiler in case of systems, where the arguments of variadic functions are passed partially through registers and partially through the stack (This is the case of PPC and x86_64, this is also the reason why both OS4 and MOS require specially patched compilers).

Since NewObject is a macro, the gcc's preprocessor expects the list of macros arguments enclosed within parentheses. In MUI macros it is not the case. Imagine the following test code:

&lt;pre&gt;
#define foo(a,b) ((a)+(b))

int loosy_function(int a, int b)
{
    return foo(a,b);
}
&lt;/pre&gt;

This will compile and work, but the following piece of code:

&lt;pre&gt;
#define foo(a,b) ((a)+(b))
#define END )

int loosy_function(int a, int b)
{
    return foo(a,b END;
}
&lt;/pre&gt;

will fail with the error: unterminated argument list invoking macro &quot;foo&quot;

There are two ways of fixing your issue. Either create your new objects outside this huge MUI constructions, and in there use just a pointer, or get rid of the &quot;End&quot; macro and exchange it with &quot;TAG_DONE)&quot;.


Badly written software is, for example, casting va_list to an APTR or even doing so as if va_list were a plain table of function arguments. Such code needs to be fixed because it has very few chances to work anywhere but on author's machine ;)

The problem is nOt that they assume sizeof(APTR) == 4, its that they often do not use APTR, and use ULONG to store pointers exclusively. If the code used APTR/IPTR as it should - most of the &quot;problems&quot; wouldn't exist.

It would also help if people would start using variadic arguments properly. Many coders do assumptions which shall never be made. Instead, they should consider using stdarg.h file and all the va_* functions :)

===ABI===

In the head of our SVN repository there are now only 3 directories:

&lt;pre&gt;
admin/
branches/
trunk/
&lt;/pre&gt;

We have added two extra dirs there: tags and imports

As discussed when we branch ABI V0 and [[Aros/Developer/ABIv1|ABI V1]] it would also be good to introduce tags. Normally this is done in a directory in the repository called tags. Currently we don't have this directory there. (We do have branches/tags that is a hack I have done because one doesn't have write access in the top directory. I think this directory is not clean and should be removed).

The second directory I would introduce is an imports directory for implementing vendor branches as discussed in the svn [http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html book]. Currently we use code from several different projects and that code is stored inside the AROS tree; we seem to have problems with keeping this code up to date and merge our changes upstream. Maintainers of up stream projects like the MUI classes etc. have complained about this (to put it lightly).

Introducing these vendor branches would make it easier to see what changes we have made and make patches to be sent upstream and make it easier to import newer upstream versions of their code. Although can't &quot;copy&quot; the vendor branch into the main branch because it's already there, so start with a &quot;merge&quot;.

Yes, the first step to make the code already in the repository compatible with the vendor branches will be the most difficult. The best way to do it the following way:

* first import the version on which the current AROS code is based into the vendor branch
* then import the new version over it in the vendor branch
* finally merge the difference between these two version in the AROS code present in the repository.

For example, place NList directly under vendor and not in a subdirectory like &quot;contrib/zune/classes&quot;.

Actually after we have a stable [http://aros.sourceforge.net/documentation/developers/specifications/drafts/abiv1.php ABIv1 (2012 or later)]. We need to move away as much as possible from the contrib directory to some other repositories. The reasons are ...

* The AROS repository should be for the core AROS code.
* other contrib projects should be tried to be compiled for all Amiga-like OSes.
* The release scheme for AROS and the other programs should not have to be aligned.
* Binary versions should be provided on aros-archives and on aminet and/or OS4Depot to install them. (Some clever programs should maybe be provided to make the life of distribution developers easier). 
* avoid parallel forks of programs for AROS and the other amiga OSes.

If there is really a need for a place for hosting AROS projects we may investigate setting up such a server but then including bug tracking, governance, maillist, etc. for each project separately. I personally think there are already enough places like sourceforge, google code, savannah, etc. where people can go for hosting such projects.

==Links==

* http://amigadocs.hokstad.com
* http://amigadocs.hokstad.com/doku.php?id=dev-links
* http://www.liquido2.com/tutorial/index.html
* Amiga(TM) OS4 has a [http://www.ast-workshops.co.uk/os4pg/ workshop] page and hope to produce a [http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=31117&amp;forum=42#549091 book] soon. [http://www.solie.ca/articles/map/map.html Brief Guide].

 In the future...?
*AROS 64bit - SMP, Vulkan with OpenGL compability layer
*AROS 32bit - keep for historic reasons 

What would you like to see implemented in AROS?
ABIv1 completed, SMP (x86_64),  SendMsg()/GetMsg() to support memory protection between target and destination, in that order.   Michal Schulz and Jason McMullan have been toying with the question &quot;What are the minimal changes needed to the AmigaOS 3.1 API to support SMP&quot;?  The answer so far seems to be &quot;few, but subtle&quot;.  For example, SysBase-&gt;ThisTask is no longer meaningful on SMP, but FindTask(NULL) is.  Disable() and Forbid() are shockingly bad on performance, but adding a spinlock semaphore mode to SignalSemaphore will help new code on SMP.  

Leveraging a 'common' OS with a lot of machine support (Linux, MacOS, Windows, QNX, etc.) is something that AROS has been doing for quite a long time, and it is the biggest strength of AROS. This AROS experience and programming model, in the same way the Google's Android layers on top of Linux, or MacOS X layers on top of the Darwin/BSD kernel, as a first step 

* The graphics + layers subsystem could be implemented as a shim on top of a OpenGL ES implementation (ie on any modern Linux system, or the RaspberryPI's hardware, MacOS X, etc). 
  - This also allows every window to be on its own 3D surface with backing store, allowing Wanderer (or a Commodity)
rearrange/zoom/animate app windows without having to send a pile or refreshes to them

* Use OpenAL as the sound backend
* AROSTCP would be a thin layer over the native OS's TCP/IP stack
* dos.library, poseidon.library, and input.device would be slim shims over the native APIs
* If we move to loading all libraries' into the application's task space, instead of a single global instance of the library, this will allow SMP and MMU more easily. 
  - Yes, it will require a lot of work in the libraries to make this transition
  - Yes, I do think it will be worth it in the end.

* A 'fat binary' install format (or, maybe LLVM bytecode) that can be 'flattend' to the target architecture on installation.

So, what would this 'AROS of the future' look like?

* AmigaOS 3.x style API, with certain 'fundamental changes' to message passing
* Uses the underlying OS' device drivers, so more AROS developer effort can go to user-visible features and bugfixes 
* Allows AROS applications to run side-by-side with the OS's native apps


And why would anyone want to program on such a system?

* AROS applications would run on any system that has the AROS Framework installed
* AROS applications are pixel-for-pixel the same on all platforms. 
* Develop with the knowledge that you are guaranteed OpenGL and OpenAL, and the rest of the AROS Framework

an option for mmake to dump its dependency of metatarget in a graphviz[*] input file. This should make it possible to visualize the dependencies and hopefully be inspiration for cleaning up some mess, circular or unneeded dependencies and so on.


AmigaOS gcc 9 [https://franke.ms/amiga/gcc.wiki Old versions] able to create binaries for AmigaOS and [https://eab.abime.net/showthread.php?t=93813 Upgrading gcc versions] 


==References==
{{reflist}}
{{status|50%}}

{{BookCat}}</text>
      <sha1>9qd2mfbp9o8lt8w558ody2lmjzkem4q</sha1>
    </revision>
    <revision>
      <id>4668962</id>
      <parentid>4668959</parentid>
      <timestamp>2026-09-05T17:29:53Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668962</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="125465" sha1="cns6icscq65bgb30auhv36k881skbgq" xml:space="preserve">{{ArosNav}}

==A technical overview of AROS==

Google translation [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=de&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs German], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=fr&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs French], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=it&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Italian], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=es&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Spanish], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=hi&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Hindi], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=zh-CN&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Chinese], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ru&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Russian], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pl&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Polish],
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pt&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Portuguese]

{{Uncited}}

AROS,&lt;ref&gt;[http://aros.sourceforge.net/download.php References and sources]&lt;/ref&gt; like AmigaOS (TM), is a [[w:Message passing|message-passing]], [[w:Preemption (computing)|preemptive]] [[w:Multitasking|multitasking]] [[w:Operating system|OS]].

It uses [[w:Reentrant (subroutine)|re-entrant]] shared libraries to save memory space.

AROS is based around an executive library kernel (Exec) and two other libraries:

* Exec (the &quot;kernel&quot;, which is not a kernel in the modern sense), 
* Intuition (graphics and GUI, integrated into the system) and 
* AmigaDOS (Disk Operating System, the Metacomco's Tripos modified to work with Exec).

The design philosophies of AmigaDOS and Intuition are rather different, the former adopting a C-like API and the latter creating an [http://www.basden.demon.co.uk/amiga/amiga.oo.html object-oriented], message passing aware environment for the programmer. The system base is the only absolute address in AmigaOS (located at 0x00000004) this does differ with AROS as AROS SysBase is automatically provided (no $4) but everything else is dynamically loaded. The OS is well known for delivering high performance due to its close connections with the hardware, while simultaneously having the flexibility to support re-targetable graphics (Cybergraphics) and retargetable audio subsystems (AHI).

: Diagram showing relationships of libraries to system needed


Remember, AROS is a [http://en.wikibooks.org/wiki/Aros/Developer/ABIv1 research] operating system, and while all contributions to the base AROS code are welcome, please contact the dev list first for any core changes. Writing applications for AROS does not have this requirement. 

While AROS appears and feels almost feature complete, it is still [[Aros/Developer/IncompleteAPIs|missing a small number of functions]] from the Amiga API. 


[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1201 This thread provides] information for setup, [http://www.aros.org/documentation/developers/index.php documentation] and whether you are interested in core OS changes and/or writing/porting software apps 

*you compile directly under AROS, which can be running on either real hardware, virtual hardware
*in hosted mode under linux/window, cross-compile from that host OS (save your files as ISO-8859-15 encoding instead of UTF-8) [https://github.com/BlitterStudio/aros-compiler-docker Docker images] 


'''The repository''' for 64bit and 32bit ABIv1 all hardware platforms is [https://github.com/aros-development-team/AROS current development version]. 
There are many forks of this so that developers can work on their own and forward changes at a later date as discussed on the dev forum 


64bit PC is one of two hardware platform with another fork called [https://github.com/deadwood2/AROS abiv11] which is used for Aros One x64 PC 

32bit PC is the other fork [https://github.com/deadw00d/AROS/tree/alt-abiv0 repository for current stable PC version ABIv0 with backported ABIv1 features is located which is used on AROS One and Icaros x86 32bit based distros] this is for historic reasons 


Any [https://github.com/aros-development-team/AROS/issues bugs / issues can be added for ABIv1 issues]. The two individual PC forks have their own issues tab on their github webpages 

We have a [https://arosdevteam.slack.com/archives/CUFV48U3H slack here], discord on [https://discord.gg/UKp9qdEBuQ Discord@AmigaDev], 


==Software Development for AROS==

===Programming languages===

====Common to all====

'The Developer Environment', which primarily supports C/C++ code, there are other programming languages available for AROS:

'''Scripting''' 
:[[Aros/User/DOS|DOS]] 
:[[Aros/Developer/Docs/LUA|LUA]] 
:REXX [[Aros/Developer/Docs/Rexx|Regina (AROS' ARexx)]] 


====Needs to be compiled/ported====

::[[Aros/Developer/Docs/LLVM|LLVM]] 
::Python [ Info], [], 
::[https://ae.arosworld.org/index.php?board=11.0 FreePascal FPC Aros-Exec thread], [https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language fpc arm here is very old and will not work], FreePascal for AROS has its own [http://fpcaroswiki.alb42.de/ Wikibook], 


::[http://sourceforge.net/projects/xamos/ X-Amos Basic] 
::[http://sdlbasic.sourceforge.net/ SDLBasic] ([https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language ])
::[[Aros/Developer/Basic/Basic4SDL|Basic4SDL]] ([https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language ])
::[http://alvyn.sourceforge.net/ Alvyn] ([http://www.dusabledanslherbe.eu/AROSPage/MISC.14.html download]) 


::[http://www.airsoftsoftwair.com/ Hollywood when enough users warrant a port - paid one time fee language] 


::[[Aros/Developer/Docs/E|AmigaE Portable E]]


====Hardware Restricted====

'''Basic'''

:[http://amos.pspuae.com/AmosProManual/contents/c1.html '''Amos Pro'''] [http://amos.pspuae.com/index.php?action=forum#1 compatible] [http://www.amigacoding.com/index.php/Main_Page commands] (all incomplete) 

:'''Blitz Basic''' [http://aros-exec.org/modules/newbb/viewtopic.php?post_id=46537#forumpost46537 none on AROS] 
:: [http://www.amiforce.de/main.php Amiblitz] on amiga(TM) emulator

:'''Amiga Basic'''
:: [ ACEBasic]

'''Misc''' 
:Ruby [http://www.ruby-lang.org/en Info]/[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language Ruby 32bit PC], 


===Where to get the C/C++ Environment===

If you want to develop for AROS, its generally easier to be running linux hosted AROS development environment especially for C++, cross compiling the code. That's how most developers now are doing it. g++ is used to compile owb web browser as well as some other AROS software. If you were hoping for a rich set of C++ libraries or classes defined for the OS feature set, you might be disappointed.

AROS Native compiling is possible, but you're much more likely to run into the odd bug(s) in the dev environment since it gets little testing and fixing by other developers.

Is there a sftp software or scp over ssh available?
Maybe. At least the security part would be handled by [https://github.com/jens-maus/amissl amissl] [https://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc port]. [https://github.com/BlitterStudio/dopus5 DOpus5] has recently added sftp support. See here for a [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1974&amp;highlight=ssh&amp;pid=12073#post_12073 ssh scp client]

[https://arosdevteam.slack.com/join/shared_invite/enQtOTc4Mzg0NDIzNzQ0LWQ2NWZmNmMwNGIwNGEyNTgxNzU3MGFjMTk3ZThmOTQ1MTVjMzhmNTllYWQ0ZTUxMjBjMGE0Y2VjMDJmNTc5MzI#/shared-invite/email Slack Dev Forum] 


====Cross compilers from Windows or Linux====

*Windows WSL2 walkthrough can be [https://arosnews.github.io/how-to-cross-compile-aros-hosted-wsl/ found here] 


you want to build AROS. No problem.

Here are instructions for PC 64-bit:
https://github.com/deadw00d/AROS/blob/master/INSTALL.md

Here are instructions for PC 32-bit:
https://github.com/deadw00d/AROS/blob/alt-abiv0/INSTALL.md

And as always has been the case you can use the contrib archive to 'obtain' the development directory which contains the /native/ AROS gcc compiler and tools. That compiler is used to build AROS itself but can be used outside the AROS build process by providing --sysroot with indicated directory to cross compile for AROS.


=====Older guides for Linux hosted compiler=====

Please install these packages before moving to next step. Below is a reference list for Debian-based distributions. Reference build system was Ubuntu 18.04/20.04 amd64.

subversion git-core gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libx11-dev libxext-dev libc6-dev liblzo2-dev libxxf86vm-dev libpng-dev gcc-multilib libsdl1.2-dev byacc python-mako libxcursor-dev cmake zsh mingw64

Do all of these operations under home directory of your user or another directory where your user has write permissions.

Specifically, in a section &quot;Linux-i386&quot;, be sure first to build the cross-compiler (toolchain-alt-abiv0-i386) and only then AROS itself (alt-abiv0-linux-i386).


Clone &amp; build
&lt;pre&gt;
$ mkdir myrepo
$ cd myrepo
$ git clone https://github.com/deadw00d/AROS.git AROS
$ cd AROS
$ git checkout alt-abiv0
$ cd ..
$ cp ./AROS/scripts/rebuild.sh .
$ ./rebuild.sh
&lt;/pre&gt;

Now to the build selection below - Linux-i386 

Select toolchain-alt-abiv0-i386 - Select alt-abiv0-linux-i386 (DEBUG) 

Start AROS by:
&lt;pre&gt;
$ cd alt-abiv0-linux-i386/bin/linux-i386/AROS
$ ./Arch/linux/AROSBootstrap
&lt;/pre&gt;


Pc-i386 Select toolchain-alt-abiv0-i386 (if not built yet) - Select alt-abiv0-pc-i386

ISO image available in alt-abiv0-pc-i386/distfiles


Now that we have linux-hosted build, we can resume native (option 2).
Run ./rebuild.sh and selection option 2. Wait until it finished, then:
&lt;pre&gt;
$ cd alt-abiv0-pc-i386
$ make
&lt;/pre&gt;

Now
&lt;pre&gt;
$ make bootiso
&lt;/pre&gt;


Now, your compiler is located in toolchain-alt-abiv0-i386 directory and named i386-aros-gcc. Includes are in alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development/include and libraries are in alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development.lib.

This is how then can be passed to the compiler:

/home/xxx/toolchain-alt-abiv0-i386/i386-aros-gcc --sysroot /home/xxx/alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development -L/home/xxx/alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development/lib 

../toolchain-alt-abiv0-i386/i386-aros-gcc --sysroot bin/linux-i386/AROS/Development local/helloworld/helloworld.c -o local/helloworld/helloworld


Another method was using Debian like distros and download the gimmearos.sh script (on [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/cross aros-archives]) to setup the developer environment by downloading necessary packages ...
The gimmearos script is a good start in that direction, building the cross compilers and hosted AROS environment, but gimmearos.sh might be out of date or not be completely compatible with any given linux distro. 

In order to do that, you have to compile AROS yourself. Download AROS source archive not contrib. Compile AROS by entering the main directory

 ./configure
 make

([http://aros.sourceforge.net/documentation/developers/compiling.php More on compiling AROS]). The result will be a basic AROS system without development tools.

To compile C++ on Linux, type 'make gnu-contrib-crosstools', creating the cross-compilers in ./bin/linux-i386/tools/, named i386-aros-gcc, etc.

'''Note''': Currently, to make the cross compilers usable copy 'collect-aros' from tools/ to tools/i386-aros/bin/. At the moment the cross compilers if used from the Linux command line will only find it when it's there.

If you want to compile native compilers (the Developer Environment), type 'make contrib-gnu-gcc', creating native compilers in AROS' System:Development/bin directory.

When the output needs to be stripped &lt;code&gt;--strip-unneeded --remove-section .comment&lt;/code&gt;

The Obj-C backend should build out of the box.

Open contrib/gnu/gcc/mmakefile.src and search for the line which contains &quot;--enable-languages&quot; and add &quot;objc&quot; to the list of languages that follows it.

    --enable-languages=c,c++,objc

Better make it—enable-languages=c,c++,objc,obj-c++

ObjC++ is broken as soon as you try to use exceptions, but that might change in future GCC versions and it does not hurt having it there already.


Do you need a cross-compiler or a real compiler? In the first case you can get away with just downloading the proper gcc archive, apply the patch and proceed with the normal gcc build. In the case of a real cross-compiler then when downloading the contrib sources, also need to download the normal sources, place the contrib sources into a directory called contrib, need to install autoconf+automake+perl+python, call ./configure, cd into the subdirectory and type make.

to rebuild GCC with host == build == target == i386-pc-aros. So just get the vanilla sources and apply the patches without bothering about the build system?


[https://vmwaros.blogspot.com/2019/10/a-pre-configured-development-machine.html pre-configured VM environment vmware virtual machine to develop AROS and AROS software]


'''64 bit'''


'''32 bit'''

A good option for multiple OS is [https://axrt.org/index.php?tab=download-aros AxRuntime lets developers compile their Amiga API-based applications as Linux binaries being able to utilize modern development tools available on Linux, like IDEs, debuggers, profilers, etc] 


====Native compilers for AROS====

Namely gcc for C or g++ for C++ are supplied with the [[Aros/Developer/Docs#The Developer Environment|Developer Environment]], which is already '''setup''' and part of any current AROS distribution like AROS One or the nightlies 

* Current GCC 6.5 (32bit) though moving to 10.5 and 15.1 (64bit) 
* Older software components. GNU GCC 4.x GNU BinUtils, GNU Fileutils 4.x, GNU Textutils and others usually deprecated 

On single partition systems and the Boot ISO, the AROS Developer environment is installed under &quot;SYS:Development/&quot;. Systems with multiple partitions - such as a Work: partition - tend to install it to there instead, however it can be installed manually to any location. Please remember, if moving, that you will need to correct the Development packages 'install location' env variable to point to the new locations root - look in SYS:S/startup-sequence.

&lt;pre&gt;
Assign Development: SYS:Development 
Assign C: Development:bin ADD 
&lt;/pre&gt;


In the aros build instructions. you need to check out contrib and/or ports into your AROS source directory, as subdirs. then, assuming you are building in an external build dir, as you should, you simply configure and &quot;make contrib&quot; for instance or whatever submodule you might want to build.


===Beginners Tutorials in C C++===

As AROS is [http://eab.abime.net/showthread.php?t=29856 C based] API compatible to AmigaOS 3.x, so most of the information on programming C on the Amiga applies to AROS as well. Please note that there is a lot of AmigaOS 1.3 (1985-1989) and [https://www.markround.com/amigaguide AmigaOS AOS 2.x (1990-1992)] information around but OS3.1 is recommended but limited in amount. 

Brief overview of what is required to write AROS Applications

# Using [[Aros/Developer/Docs/Libraries/Intuition|Intuition]] for basic screens/windows 
# Using graphics within windows via 8bit [[Aros/Developer/Docs/Libraries/Graphics|graphics]] and so onto  15-16-24bit [[Aros/Developer/Docs/Libraries/CGFX|cybergraphx]]
# Load and save work to [[Aros/Developer/Docs/Libraries/DOS|dos]] disk drives
# Using the [[Aros/Developer/Zune|ZUNE GUI Environment]]


Writing native games require this extra information

# Using [[Aros/Developer/AHIDrivers|AHI audio hardware independent API]]
# Using USB joystick/joypad with the Poseidon USB stack through [[Aros/Developer/Docs/Libraries/LowLevel|LowLevel]] library


Additional features that could be added later

# Adding additional [[Aros/Developer/Docs/Libraries/Locale|Locale]] language translations to your program 
# Adding a [[Aros/Developer/Docs/Rexx|AREXX/Regina]] port to your application 
# Executing Amiga(TM) [[Aros/User/DOS|DOS]] commands from your application
# Using [[Aros/Developer/Docs/Libraries/Icon|icons]] (.info files) and icon tooltypes (stack, version, and program startup options)
# Local couch or IP based SANA2 networking co-op multi player gaming support 


Most AmigaOS programming books are nowadays very much out of date as most are from the late 1980s and do not cover later amigaOS releases like 3.1 for example, Rob Peck's book &quot;Programmer's Guide to the Amiga&quot;. The Amiga ROM Kernel manuals aka RKMs like Libraries (3rd edition), Devices (), the AmigaDOS manual (3rd edition) and the Style Guide may have their uses. There are some reference examples from AmigaMail and Devcon notes (available again on an Amiga developers CD 2.1). 

For Arexx then &quot;The Amiga Programmer's Guide to ARexx&quot; by Eric Giguere, which was published by Commodore is useful as well as an &quot;Arexx Cookbook&quot;.

Curly brackets missing - try SHIFT + ALT + 7 or 0.


* Beginners C Guide [http://www.iu.hio.no/~mark/CTutorial/CTutorial.html C Tutorial], 
* [http://thecguru.com/ C for beginners],
* [http://fresh2refresh.com/c/c-basic-program/ C programming basics] for students, 
* [https://www.edx.org/courses Free Online course] from American Universities 
* Reference Amiga [http://amigadev.elowar.com/ API reference].


* AROS based c source can be found [[Aros/Developer/Docs/Examples|here]] and lots of example code can be found inside [https://github.com/aros-development-team AROS sources] themselves and from the contrib section of the archives from [https://github.com/aros-development-team/contrib Aros site], and study the AROS applications source code, e.g. the test programs from the Tests drawer (folder/directory). Take a look at the code of some smaller AROS programs might be a better and more up to date 

When you upload your builds, please write the architecture (like i386-aros, x86_64-aros, armPi-64 etc.) in the archive name 
and it is also advisable to write in the field &quot;Requirements&quot; what ABI (ABIv1 or for PC forks ABIv11 or ABIv0) 


===Compiling C/C++ Code===

Native, although we have a IDE Integrated Development Environment (Murks), it does lack a debugger. Whilst others use a combination of a text editor and shell to edit code. Most though use an AROS hosted on Linux to take advantage of the better GCC tools like GDB and various IDEs.

Open shell - its a menu option at the top left of Wanderer (desktop). Or by using the right Win key and w (or F12 and w) within the directory with the source code. Type in
 sh 
to change the amiga shell into a unix shell. You can then type in ls (unix equivalent to amiga dir). Take a look [http://en.wikibooks.org/wiki/Linux_commands here] for more commands.

For a single file program-name.c or program-name.cpp
 gcc -o program-name program-name.c  
or 
 g++ -o program-name program-name.cpp
or
 g++ -o test -Wall -g main.cc texturelib.cpp xmodelib.cc -lsdl -lgl

To close the shell, click on the top left-hand corner to close (twice). Once to get back the aros shell and then again to close finally. Use [http://freshmeat.net/projects/cksfv/ cksfv] as a test.

Some source code requires the addition of Amiga API libraries, like dos, which you can flag at the compile time as 
 gcc -o julia.exe julia.c -ldos

For DOS use -ldos as example and if you are compiling mui codes it will be -lmui or intuition -lintuition. Other missing symbols are due to linker libraries being necessary for linking in functions that aren't in the standard C libraries. For example some source code would need added

 -lz or -lm or -lpng or -larosc etc.

use this in unix line command mode to search for 'search-item' in many .c files (*.cpp for c++, etc.)
 grep -l 'search-item' *.c

If the program is not executable, try using parameter fno-common 

&quot;Delete #?.o&quot;? Or if you are using abcshell then &quot;rm *.o&quot;


:''More information: [[Aros/Developer/Porting software]]''


=== How to make Apps have AROS 64-bit specific support code ===

[http://www.aros.org/cs/documentation/developers/app-dev/portable.php Portable code] 

AROS64 already uses 64bit addressing, it just doesn't setup the MMU for more than 4GB physical memory currently.
When porting software to AROS64 it is &quot;mostly&quot; a case of converting ULONG's that are used to store pointers, into IPTR's instead, etc. Another quirk, is making sure items on the stack are the correct size by using the STACKED attribute for them. 

* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.

compiling mui stuff for aros setting -std=gnu99 is necessary, had -std=c99 usually 
A MUI application most likely needs only the HOOKPROTOxxx SDI macros. They are compatible with AROS, only the attributes (hook, object attribute) must be given in the right order.

crash which suggest memory corruption. From my experience porting from 32-bit to 64-bit these kinds of errors can happen if a pointer is passed somewhere via ULONG variable. Then half of the pointer is cut.

To generate this error, please run AROSBootstrap with -m 1024. This will allocate heap to 64-bit address space which will make these errors immediatelly visible. These types of crashes are hard to debug. Disabled as little code as possible to stop corruption from occurring and then try to read from the code where it can be broken

Crashing in tslf_freevec is another symptom of memory corruption and these memory corruptions will manifest differently on different setups.


==Coding conventions==

As the AROS core source is a shared developer experience, there are rules regarding structure and style. When it comes to your creating your own app and coding, the structure and style should be your own, i.e. you should enjoy what you do and do it so that you can understand what is going on.

===Layout===

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
static void 1st_function()
{
    program
    exit(0);    
}

int main(void)
{
    1st_function();
    2nd_function();
    3rd_function();
    return 0;
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;

struct Screen * openscreen(void);
struct Window *openwindow(struct Screen *screen, const char *title, LONG x, LONG y, LONG w, LONG h);

VOID 1st_function();
VOID 2nd_function();

int main(int argc, char **argv)
{
    program
    return 0;
} /* main */

VOID 1st_function()
{

}

VOID 2nd_function()
{

}
&lt;/syntaxhighlight&gt;

===General style===

This code is used by many people and therefore you should keep some things in mind when you submit source code:

* Keep things simple 
* Keep the source clean 
* Always know what you are doing, if not flag it and describe what needs to be done... 
* Explain clearly/simply what you are doing 
* Remember that you write code once but that it is read many times by many people

===Comments===

AROS uses some of the comments in the source to generate the documentation. Therefore it's necessary to keep a certain format so the tools can find their information. Other comments are ignored but they should explain what you thought when you wrote the code. If you really can't think of an explanation, then don't write the code a second time like this:

&lt;pre&gt;
/* This adds 1 to t */
t ++;
&lt;/pre&gt;

What we think of is this:

&lt;pre&gt;
/* Go on with next element */
t ++;
&lt;/pre&gt;

===Formatting===

This is only '''IMPORTANT''' if you are going to work on the core AROS code or contrib but not applications which may reside outside like on AROS Archives or other websites.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
{
    /* a */
    struct RastPort * rp;
    int               a;

    /* b */
    rp = NULL;
    a  = 1;

    /* c */
    if (a == 1)
        printf (&quot;Init worked\n&quot;);

    /* d */
    if
    (
        !(rp = Get_a_pointer_to_the_RastPort
            (
                some
                , long
                , arguments
            )
        )
    ||
        a &lt;= 0
    )
    {
        printf (&quot;Something failed\n&quot;);
        return FAIL;
    }

    /* e */
    a = printf (&quot;My RastPort is %p, a=%d\n&quot;
        , rp
        , a
    );

    return OK;
}
&lt;/syntaxhighlight&gt;

Looks ugly, eh ? :-) Ok, here are the rules:

&lt;pre&gt;
If several lines contain similar code, put similar things below each other (see a and b);
Put spaces between operands and operators
Put braces {}, brackets [] and parentheses () below each other (d) if there is much code between. 
Brackets and parentheses may be in one line if the code between is small (c)
Indent by 4 Spaces. Two indent levels may be abbreviated by one tab.
&lt;/pre&gt;

'''Before committing please normalize the indentation - if you have a mixture of tabs and spaced - please always use spaces, 1 tab = 4 spaces.'''

The reasons for this are:

# While some editors can use an arbitrary sizes for tabs, it's a bit complicated to tell another editor which tab size was used by the one used to write the code. 
# Most code in AROS was written this way and your code should look like the rest. 
# You can print this code on any printer without special tools to &quot;fix&quot; the tabs. 
# Most editors have smart tabs which do exactly this. If your editor doesn't, write a bug report.

If you have a function with many arguments (d, e) you should put the parentheses in lines of their own and each argument in one line (d) or put the first argument behind the opening parentheses (e) and each following argument in a line of its own with the comma in front. The closing parentheses is in a line of its own and aligned with the beginning of the expression (i.e. the a and not the opening parentheses or the printf()).

Use a single blank line to separate logical blocks. Large comments should have a blank line before and after them, small comments should be put before the code they explain with only one blank line before them.

If you see any TABS in AROS core sources then the suggestion is to &quot;detab the file and commit that separately&quot; either before or afterwards from making functionality changes. Make two commits instead of one. This makes it easier for others to see the real changes instead of having to dig through multiple lines of irrelevant diffs.

===Eliminating Global Variables===

i.e. pass variables to functions (local scope) or classes making it easier to track and debug your code.

Any time you find that you need a particular thing in 'a lot of different places', chances are that all those places are conceptually related, and so you can create a class, a namespace, a function, or some other higher-level organizational unit to represent that relationship. This makes the program easier to understand.

Bad Designs

* All variables are global. 
* There are no standalone functions, only sub-procedures which act on the global variables. 
* Every sub-procedure is at least 500 lines to several thousand 
* Every sub-procedure has more than one task to perform 
* Copy-paste is preferred to writing methods, AND subtle changes are made in the middle of the code

Good Designs

* structure program into functions (C or basic) - top-down procedural approach 
* put in class(es) (freepascal or C++) - the object is fixed and you use methods to access the object

&lt;pre&gt;
 class String_List
 {
 private:
 list&lt;string&gt; m_List;  // member
 public:
 void read_strings() { /* read strings into m_List */ }
 void print_strings() { /* write contents of m_List to stdout */ }
 void sort_strings() { /* sort contents of m_List */ }
 void sort_strings_reverse() { /* reverse-sort contents of m_List */ }
 void unique_strings() { /* remove duplicate strings */ }
 };

 int main()
 {
 String_List myList;  // local
 myList.read_strings();
 myList.sort_strings();
 myList.print_strings();
 myList.sort_strings_reverse();
 myList.print_strings();
 myList.unique_strings();
 myList.print_strings();
 return 0;
 }
&lt;/pre&gt;

This way it is very easy to replace the list with new list for debugging purposes, or replacing the methods without replacing the list, when you want different results. You only have to replace the content of the local variables.

 So create the structure that matches your data (linked lists, trees, arrays, etc.) and what to do with them (sorting, searching, etc.)

&lt;pre&gt;
.h usually contain #define #include typedef enum struct extern screen and window definitions (data structures)
.c should contains functions and algorithms
&lt;/pre&gt;

One way to look at it is that menu headings act as the .c file and sub-menu headings as functions.

When you start a project, you place a couple of declarations in the include file. As the project continues, you place more and more declarations in the include file, some of which refer to or contain previous declarations. Before you know it, you have a real mess on your hands. The majority of your source files have knowledge of the data structures and directly reference elements from the structures.
Making changes in an environment where many data structures directly refer to other data structures becomes, at best, a headache. Consider what happens when you change a data structure.

Use good variables names to help clarify code and only comment when you need to explain why a certain programming approach was made.

You're Refactoring Legacy Code, you see a global, you want to get rid of it. How do you do this?

Exactly what to do depends on how the global is used. The first step is to find all uses of the global throughout the code, and get a feel for what the significance of the variable is and how it relates to the rest of the program. Pay particular attention to the &quot;lifetime&quot; of the variable (when it gets initialized, when it is first used, when it is last used, how it gets cleaned up). Then, you will probably make the global a data member of a class (for OO languages), or you will write some get/set functions. Converting to the Singleton Pattern is common, but you may discover that it makes more sense for the data element to be a member of an existing singleton, or maybe even an instance variable.

# Create a basic read method, either as a class or a global function. Replace all reads with the access method, but leave the variable defined as a global.
# Review each of the writes to the method and extract action functions one at a time. Unless two operations are coded identically in the original code, extract each write access separately.
# Change the variable scope from global to local.
# Analyze similar action functions to determine if any can be merged, i.e., there are no functional differences in the results of the function, just differences in the implementation details.
# Review the calls to the read method and see if a more complex functionality should be applied. Follow the approach for writes and unless implementations are identical, create separate access functions. 
# Analyze the access functions for duplication.

As returning variables by &quot;passing by value&quot; are forgotten, so &quot;passing by reference&quot; is often used instead. The reference is a pointer to the variable so the value is remembered when returned.

Alternatives

* Hidden Globals
* Singleton Pattern
* Database or TupleSpace
* Context Object 
* Dependency Injection 
* Stateful Procedures


==AROS/AmigaOS APIs and Docs==

&lt;pre&gt;
Library:
   - Private data structure
   - Many public access methods

Device:
   - Private data structure
   - Two (BeginIO/AbortIO) access methods

Resource:
   - Public data structure
   - *NO* access methods
&lt;/pre&gt;

And, being Amiga OS-compatible, there are exceptions to all of these.


===System Libraries===

The [http://developers.aros.org/ AROS Guide To Libraries] can be used as a guide to individual commands and old Dev Docs are used in application programming.

Amiga/Aros styles libraries are very different from windows and linux libs. Typical .so/dll libraries are foreign to most Amiga-like OS 


*[[Aros/Developer/Docs/Libraries/AROSC|arosc.library]]
*[[Aros/Developer/Docs/Libraries/AmigaGuide|amigaguide.library]]
*[[Aros/Developer/Docs/Libraries/ASL|asl.library]]
*[[Aros/Developer/Docs/Libraries/Bullet|bullet.library]]
*[[Aros/Developer/Docs/Libraries/BSDsocket|bsdsocket.library]]
*[[Aros/Developer/Docs/Libraries/CAMD|camd.library]]
*[[Aros/Developer/Docs/Libraries/Codesets|codesets.library]]
*[[Aros/Developer/Docs/Libraries/CGFX|cybergraphics.library]]
*[[Aros/Developer/Docs/Libraries/CGXVIDEO|cgxvideo.library]]
*[[Aros/Developer/Docs/Libraries/Commodities|commodities.library]]
*[[Aros/Developer/Docs/Libraries/DataTypes|datatypes.library]]
*[[Aros/Developer/Docs/Libraries/DiskFont|diskfont.library]]
*[[Aros/Developer/Docs/Libraries/DOS|dos.library]]
*[[Aros/Developer/Docs/Libraries/Exec|exec.library]]
*[[Aros/Developer/Docs/Libraries/Expansion|expansion.library]]
*[[Aros/Developer/Docs/Libraries/FreeType2|freetype.library]]
*[[Aros/Developer/Docs/Libraries/GadTools|gadtools.library]]
*[[Aros/Developer/Docs/Libraries/Graphics|graphics.library]]
*[[Aros/Developer/Docs/Libraries/Icon|icon.library]]
*[[Aros/Developer/Docs/Libraries/Identify|identify.library]]
*[[Aros/Developer/Docs/Libraries/IFFParse|iffparse.library]]
*[[Aros/Developer/Docs/Libraries/Intuition|intuition.library]]
*[[Aros/Developer/Docs/Libraries/Keymap|keymap.library]]
*[[Aros/Developer/Docs/Libraries/Layers|layers.library]]
*[[Aros/Developer/Docs/Libraries/Locale|locale.library]]
*[[Aros/Developer/Docs/Libraries/LowLevel|lowlevel.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEESingBas|mathieeesingbas.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEEDoubBas|mathieeedoubbas.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEESingTrans|mathieeesingtrans.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEEDoubTrans|mathieeedoubtrans.library]]
*[[Aros/Developer/Docs/Libraries/Mathtrans|mathtrans.library]]
*[[Aros/Developer/Docs/Libraries/MUIMaster|muimaster.library]]
*[[Aros/Developer/Docs/Libraries/Partition|partition.library]]
*[[Aros/Developer/Docs/Libraries/PopUpMenu|popupmenu.library]]
*[[Aros/Developer/Docs/Libraries/OOP|oop.library]]
*[[Aros/Developer/Docs/Libraries/Regina|regina.library]]
*[[Aros/Developer/Docs/Libraries/Reqtools|reqtools.library]]
*[[Aros/Developer/Docs/Libraries/RexxSysLib|rexxsyslib.library]]
*[[Aros/Developer/Docs/Libraries/ScreenNotify|screennotify.library]]
*[[Aros/Developer/Docs/Libraries/TTEngine|ttengine.library]]
*[[Aros/Developer/Docs/Libraries/Thread|thread.library]]
*[[Aros/Developer/Docs/Libraries/Utility|utility.library]]
*[[Aros/Developer/Docs/Libraries/Xadmaster|xadmaster.library]]
*[[Aros/Developer/Docs/Libraries/Workbench|workbench.library]]
*[https://github.com/aros-development-team/AROS/commit/c82e86b8480277998014cc327b56c7664023a52f ClassAct Reaction boopsi class]


===AROS Subsystems===

# [[Aros/Developer/Zune|Zune MUI compatible GUI]]
# [[Aros/Developer/AROSAppPackages|AROS Application Packages]]
# AHI Audio Drivers - [[Aros/Developer/AHIDrivers|Usage]]/[[Aros/Developer/AHIDriversDev|Development]]
# AROSTCP Sana2 Network Interface Drivers - [[Aros/Developer/NICDrivers|Usage]]/[[Aros/Developer/NICDriversDev|Development]]
# [[Aros/Developer/AmiSSL|AmiSSL]]
# gfx.hidd/cybergraphics Video Drivers - [[Aros/Developer/GfxDrivers|Usage]]/[[Aros/Developer/GfxDriversDev|Development]]
# IO Device Drivers - [[Aros/Developer/IODeviceDrivers|Usage]]/[[Aros/Developer/IODeviceDriversDev|Development]]
# USB Device Drivers - [[Aros/Developer/USBDrivers|Usage]]/[[Aros/Developer/USBDriversDev|Development]]
# PCI Device Drivers - [[Aros/Developer/PCIDrivers|Usage]]/[[Aros/Developer/PCIDriversDev|Development]]
# [http://www.libsdl.org/ SDL] [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2013&amp;pid=13333#post_13333 SDL2 coding usage], [https://github.com/search?q=repo%3Aaros-development-team%2Fcontrib%20SDL2&amp;type=code SDL2 commits], [https://github.com/aros-development-team/contrib/commit/c62c3c425c35bac19dadc23be092b0b13a66c76c SDL3 initial commit], []
# [[w:Gallium3D|Gallium 3D]] [http://www.mesa3d.org/ openGL aka Mesa] - [[Aros/Developer/OpenGL|Usage]]/[[Aros/Developer/OpenGLDev|Development]] [http://www.swiftless.com/opengltuts.html Swfitless]
# A small subset of GTK2 through [http://sourceforge.net/projects/gtk-mui/ MUI-GTK] 
# Cairo 2D Engine - [[Aros/Developer/Cairo|Usage]]/[[Aros/Developer/Cairo|Development]]
# [[Aros/Developer/Scalos|Scalos desktop API and plugin modules]]
# [[Aros/Developer/VHI|VHI video driver]]


====HIDDs====

*[[Aros/Developer/Docs/HIDD/HIDDClass|hiddclass.hidd]]
*[[Aros/Developer/Docs/HIDD/Graphics|graphics.hidd]]
*[[Aros/Developer/Docs/HIDD/VesaGfx|vesagfx.hidd]]
*[[Aros/Developer/Docs/HIDD/ATI|radeon.hidd]]
*[[Aros/Developer/Docs/HIDD/NVidia|nvidia.hidd]]
*[[Aros/Developer/Docs/HIDD/Nouveau|nouveau.hidd]]
*[[Aros/Developer/Docs/HIDD/Kbd|kbd.hidd]]
*[[Aros/Developer/Docs/HIDD/Mouse|mouse.hidd]]
*[[Aros/Developer/Docs/HIDD/i2c|i2c.hidd]]
*[[Aros/Developer/Docs/HIDD/IRQ|irq.hidd (deprecated)]]
*[[Aros/Developer/Docs/HIDD/PCI|pci.hidd]]
*[[Aros/Developer/Docs/HIDD/PCIPC|pcipc.hidd]]
*[[Aros/Developer/Docs/HIDD/Serial|serial.hidd]]
*[[Aros/Developer/Docs/HIDD/Thunderbolt|thunderbolt.hidd]]
https://github.com/aros-development-team/AROS/commit/4f02ea691799aff3a01f60cfa5f9182c82fc57a8

HIDD are used for device/peripheral low level hardware support drivers. The HIDD system is split up into a collection of classes with a strict inheritance hierarchy. A HIDD class implements a device driver for a single device or in rare cases a group of devices and provides an interface for other programs and devices to access.
      
In order to maintain portability of interfaces across a wide range of hardware this interface will in general not present the raw interface to the underlying hardware. Instead it will present a generic interface that describes many different hardware implementations. This allows for the best reuse of both interfaces and code.

HIDD API is heavyweight though. You need to open a HIDD library, open oop.library, instantiate an object (even if there's no object); and object calls are more costly compared to plain library calls.


Basically your task is to implement a subclass of hidd.ata.bus for your hardware. just implementing the XXXATA__Hidd_ATABus__xxxxxx methods for the Amiga chipset - and appropriate versions of the interface_xxx.c file(s). pretty much everything in probe.c could be ignored - just write a replacement scan for relevant amiga devices and store whatever info you need in the bus data? only the &quot;SUPPORT_LEGACY&quot; blocks might be related.

You do not need to depend on PCI API. PCI is just a way to discover the hardware on PCs, etc. 
&lt;hidd/pci.h&gt; includes (at some depth) &lt;interface/HW.h&gt;, which defines IID_HW. This comes from the 'generic' HIDD class in: 
 rom/hidds/hidd/hiddclass.conf
did not split up HIDD and HW because they are always used in pair. It's the same as hidd/pci.h bringing definition for: PCI, PCIDriver and PCIDevice. PCI is actually PCIHW, just the name was not changed for backwards compatibility reasons. HW is a 'hub' where HIDD instances plug in.

ATA HIDD aoHidd_ATABus_Use32Bit value is completely ignored unless ata.device first detects correct command line parameter.
Yes. Unfortunately I was unable to find any comment in code or svn history with explanations. Looked  at Linux source, there 32-bit PIO is also controller driver's property. Some of them enable it, some don't.

Actually, switching the default to ON should be safe. ata.device is fail-safe at this because during IDENTIFY command it validates upper 16  bits,  and  if they appear to be zeroes in all 128 longwords, then 32-bit mode is switched off. But, nevertheless, I know how tricky hardware can be, so I decided not to change original behavior. If  you think it's wrong in some cases, then it's possible to add one more  attribute  like  aHidd_ATABus_Default32Bit. If set to YES, then  this means that 32-bit PIO is safe to use by default.


====Devices====

*[[Aros/Developer/Docs/Devices/ATA|ata.device]]
*[[Aros/Developer/Docs/Devices/Console|console.device]]
*[[Aros/Developer/Docs/Devices/Narrator|narrator.device]]
*[[Aros/Developer/Docs/Devices/Printer|printer.device]]
*[[Aros/Developer/Docs/Devices/Trackdisk|trackdisk.device]]
*[[Aros/Developer/Docs/Devices/AmberRAM|amberram.device]]
*[[Aros/Developer/Docs/Devices/Timer|timer.device]]
*[[Aros/Developer/Docs/Devices/|.device]]

The Amiga used [[Aros/Developer/Docs/Devices|Devices]] to communicate with [http://aros-exec.org/modules/newbb/viewtopic.php?start=0&amp;topic_id=3475&amp;viewmode=flat&amp;order=ASC additional hardware]. AROS has replaced these hardware devices with hidd equivalents but some are still retained for backwards compatibility.

Local libraries/devices/handlers,etc. are supposed to override the ones in ROM if their version is higher than the one in ROM.

Here is the list of commands exec default: 
{| class=&quot;wikitable&quot;
| CMD_CLEAR
|  Purge the buffer of the device
|----
| CMD_READ
|  Playback Control
|----
| CMD_STOP
|  Stopped the activity of the device
|----
| CMD_FLUSH
|  Empty the queue of commands
|----
| CMD_RESET
|  Reset a device
|----
| CMD_WRITE
|  Playback Control
|----
| CMD_INVALID
|  Create an error
|----
| CMD_UPDATE
|  Gets updated device
|----
| CMD_START
|  Will restart the device
|----
|}

While most other &quot;stuff you communicate with&quot; in AmigaOS are devices &lt;ref&gt;AMIGA ROM Kernel Reference Manual: Devices, 3rd Edition. Commodore-Amiga, Inc. Addison-Wesley, 1991. {{ISBN|0-201-56775-X}}&lt;/ref&gt; that share a [http://gega.homelinux.net/AmigaDevDocs/ common base interface]. [[Aros/Developer/Docs/Devices1.3|OS 1.3 Device Drivers]].


====Handlers====

:[[Aros/Developer/Docs/Handlers/Pipe|pipe.handler]]
:[[Aros/Developer/Docs/Handlers/Port|port.handler]]
:[[Aros/Developer/Docs/Handlers/SFS|sfs.handler]]
:[[Aros/Developer/Docs/Handlers/FAT|fat.handler]]
:[[Aros/Developer/Docs/Handlers/PFS|pfs.handler]]
:[[Aros/Developer/Docs/Handlers/NTFS|fuse.handler]]
:[[Aros/Developer/Docs/Handlers/FFS|ffs.handler]]

filesystem handlers have their own separate system consisting of completely differently structured messages that dos.library use to pass requests (for things like reading, writing, getting directory contents etc.) to them. AROS originally went with implementing filesystem handlers as devices, which might arguably be more consistent with the rest of the AmigaOS API but which is quite incompatible with AmigaOS itself. However, it made it far harder to port filesystems and the gains were comparatively small, and so there's been a long standing goal of fixing this incompatibility. It has now, June 2011, been reintroduced to all AROS flavors.

are argstr and argsize valid for the handler startup environment?
DOS/RunHandler() calls DOS/CreateNewProcTags(), and then CallEntry() (in rom/dos/exit.c) to start the handler, so yes, argstr and argsize are *present* in the call signature of the handler.

Granted, argstr will be NULL and argsize 0, but those values *are* passed to the handler function using:

&lt;pre&gt;
AROS_UFC3(ULONG, entry,
                         AROS_UFCA(STRPTR, argptr, A0),
                         AROS_UFCA(ULONG, argsize, D0),
                         AROS_UFCA(struct ExecBase *, SysBase, A6));
&lt;/pre&gt;

Creating your own [without the whole build tree http://pagesperso-orange.fr/franck.charlet/temp/radeon.zip] and then  
&lt;pre&gt;
make stub
make
make install
&lt;/pre&gt;

SFS has two Root blocks, one at the start and one at the end of the disk. The Root blocks both contain the same information.  They hold various information about the disk structure and have the locations of some important blocks used by the filesystem.  

The Root ObjectContainer contains the Root directory Object. The name of this Object is the name of the volume. It is identical to a normal directory Object.

The Bitmap is used to keep track of free space. Each bit in a bitmap represents a single block. A set bit indicates a free block and a cleared bit a used block.

AdminSpaceContainers are used to keep track of space which has been reserved for storing administration blocks. Only the Bitmap, the Root blocks and the actual data stored in files aren't stored in administration space. Administration space is allocated in chunks of 32 blocks at a time. A single AdminSpaceContainer can hold information about a large number of such areas each of which has its own little bitmap of 32 bits.

Extents are stored in a B-Tree. The Root block holds a pointer to the root of the Extent B-Tree. Extents keep track of space in use by a specific file. Each fragment a file consists of has its own Extent. Extents are in a double linked list. The list can be used to locate the next or previous fragment of a file.

Below is the standard block header. This header is found before EVERY type of block used in the filesystem, except data blocks.  The id field is used to check if the block is of the correct type when it is being referred to using a BLCK pointer.  The checksum field is the SUM of all LONGs in a block plus one, and then negated. When applying a checksum the checksum field itself should be set to zero. The checking a checksum the checksum is okay if the result of the checksum equals zero. The ownblock BLCK pointer points to the block itself. This field is an extra safety check to ensure we are using a valid block.

Field	Type	Description
id	ULONG	The id field is used to identify the type of block we are dealing with. It is used to make sure that when referencing a block we got a block of the correct type. The id consist of 4 bytes and each blocktype has its own unique foure letter code.
checksum	ULONG	This field contains the sum of all longs in this block, plus one and then negated. The checksum can be used to check if the block hasn't been corrupted in any way.
ownblock	BLCK	Points to itself, or in other words, this field contains the block number of this block. This is yet another way to check whether or not a block is valid.

&lt;pre&gt;
struct fsBlockHeader {
    ULONG id;
    ULONG checksum;
    BLCK ownblock;
};
&lt;/pre&gt;
The algorithm to calculate the checksum of a block:
&lt;pre&gt;
ULONG calcchecksum(struct fsBlockHeader *block, LONG blocksize} {
    ULONG *data=(ULONG *)block;
    ULONG checksum=1;

    block-&gt;checksum=0;

    while(blocksize&gt;0) {
        checksum+=*data++;
        blocksize-=4;
    }

    return(-checksum);
} 
&lt;/pre&gt;

A Root block contains very important information about the structure of a SFS disk. It has information on the location and size of the disk, the blocksize used, locations of various important blocks, version information and some filesystem specific settings.

A SFS disk has two Root blocks; one located at the start of the partition and one at the end. On startup the filesystem will check both Roots to see if it is a valid SFS disk. If either one is missing SFS can still continue (although at the moment it won't).

A Root block could be missing on purpose. For example, if you extend the partition at the end (adding a few MB's) then SFS can detect this with the information stored in the Root block located at the beginning (since only the end-offset has changed).   Same goes for the other way around, as long as you don't change start and end point at the same time.

When a Root block is missing because the partition has been made a bit larger, then SFS will in the future be able to resize itself without re-formatting the disk.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
version	UWORD	The version of the filesystem block structure. You can check this field to identify what version of the filesystem your dealing with it and to see if you can handle this structure correctly. Don't try to interpret the disk's structure when this field contains an unknown version number!

sequencenumber	UWORD	Used to identify which Root block was written last in case the sequencenumber on both Root blocks don't match.
datecreated	ULONG	Creation date of this volume. This is the date when the disk was last formatted and will never be changed.

bits	UBYTE	Various settings, see below.
&lt;pre&gt;
pad1	UBYTE	Reserved, leave zero.
pad2	UWORD	Reserved, leave zero.
reserved1	ULONG[2]	Reserved, leave zero.
firstbyteh	ULONG	High 32-bits of a 64-bit number. This is the first byte of our partition relative to the start of the disk.
firstbyte	ULONG	Low 32-bits of a 64-bit number.
lastbyteh	ULONG	High 32-bits of a 64-bit number. This is the last byte (exclusive) of our partition relative to the start of the disk.
lastbyte	ULONG	Low 32-bits of a 64-bit number.
totalblocks	ULONG	The total number of blocks this partition consists of.
blocksize	ULONG	The size of a block of this partition.
reserved2	ULONG[2]	Reserved, leave zero.
reserved3	ULONG[8]	Reserved, leave zero.
bitmapbase	BLCK	Block number of the start of the Bitmap.
adminspacecontainer	BLCK	Block number of the first AdminSpaceContainer.
rootobjectcontainer	BLCK	Block number of the ObjectContainer which contains the root of the disk (this is where the volume name is stored).
extentbnoderoot	BLCK	Block number of the root of the Extent B-Tree.
reserved4	ULONG[4]	Reserved, leave zero.
&lt;/pre&gt;

&lt;pre&gt;
struct fsRootBlock {
  struct fsBlockHeader bheader;
  UWORD version;
  UWORD sequencenumber;
  ULONG datecreated;
  UBYTE bits;
  UBYTE pad1;
  UWORD pad2;
  ULONG reserved1[2];
  ULONG firstbyteh;
  ULONG firstbyte;
  ULONG lastbyteh;
  ULONG lastbyte;
  BLCK  totalblocks;
  ULONG blocksize;
  ULONG reserved2[2];
  ULONG reserved3[8];
  BLCK  bitmapbase;
  BLCK  adminspacecontainer;
  BLCK  rootobjectcontainer;
  BLCK  extentbnoderoot;
  ULONG reserved4[4];
};
&lt;/pre&gt;

AdminSpaceContainers are used to store the location and bitmap of each administration space. The AdminSpaceContainers are located in a double linked list and they contain an array of fsAdminSpace structures.  There is one fsAdminSpace structure for every administration space on disk.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
next	BLCK	The next AdminSpaceContainer, or zero if it is the last in the chain.
previous	BLCK	The previous AdminSpaceContainer, or zero if it is the first AdminSpaceContainer.
bits	UBYTE	The number of bits in each in the bits ULONG in the fsAdminSpace structure.
pad1	UBYTE	Reserved, leave zero.
pad2	UWORD	Reserved, leave zero.
adminspace	struct fsAdminSpace	An array of fsAdminSpace structures. The size of the array is determined by the current blocksize.
&lt;pre&gt;
struct fsAdminSpaceContainer {
  struct fsBlockHeader bheader;
  BLCK next;
  BLCK previous;
  UBYTE bits;
  UBYTE pad1;
  UWORD pad2;
  struct fsAdminSpace adminspace[0];
};
&lt;/pre&gt;
Field	Type	Description
space	BLCK	The first block of an administration space.
bits	ULONG	A small bitmap which is used to determine which blocks in an administration space are already in use. The number of bits in this bitmap is determined by the bits field in the AdminSpaceContainer.
&lt;pre&gt;
struct fsAdminSpace {
  BLCK  space;
  ULONG bits;
};
&lt;/pre&gt;

The fsBitmap structure is used for Bitmap blocks. A bitmap block is used to keep track of which space is in use and which isn't for a particular area of a disk.  All bitmap blocks together keep track of the free space for an entire disk. The location of the first bitmap block is known and all other bitmap blocks are stored in order after the first one.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
bitmap	ULONG	An array of ULONG's.  These hold the actual information on which blocks are in use and which aren't.
&lt;pre&gt;
struct fsBitmap {
    struct fsBlockHeader bheader;
    ULONG bitmap[0];
};
&lt;/pre&gt;
Each bit in a bitmap block (except for the block header) represents a single block. If the bit is set than the block is free, and if the bit is clear then it is full. The first ULONG in the bitmap area of the first bitmap block represents blocks 0 through 31 on the disk. Bit 31 of this ULONG is block 0, 30 is block 1, and so on. Bit 0 of the first ULONG represents block 31.

Below is a table to clarify how bitmaps work even further. The first column is the bitmap block number, the second column is the number of the ULONG in the bitmap array. The third column is the bit number in this ULONG, and the last column is the block which this specific bit, in this specific bitmap block represents.

We'll assume here that a bitmap block has room for 120 ULONG's (meaning there is room for storing 32 * 120 bits).

&lt;pre&gt;
Bitmap block	ULONG number	Bit number	Block represented
1 (first)	0	31	0
1	0	30	1
...	...	...	...
1	0	1	30
1	0	0	31
1	1	31	32
...	...	...	...
1	2	31	64
1	2	30	65
...	...	...	...
1	119	0	3839
2	0	31	3840
2	0	30	3841
...	...	...	...
&lt;/pre&gt;
The last bitmap block doesn't need to be completely used. The unused bits (which belong to blocks which do not exist) all have to be clear, to indicate that these blocks are in use.

The fsObjectContainer structure is used to hold a variable number of fsObjects structures (Objects) which have the same parent directory. Each ObjectContainer must contain at least one Object. If there is space in the ObjectContainer not used by the variable number of Objects then that space is zero filled. Objects always start at 2-byte boundaries, which means sometimes a padding byte is inserted between two Objects.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
parent	NODE	The node number of the parent Object, or 0 if this object has no parent (which is only the case for the Root directory).
next	BLCK	The next ObjectContainer belonging to this directory, or zero if it is the last in the chain.
previous	BLCK	The previous ObjectContainer belonging to this directory, or zero if it is the first ObjectContainer in this directory.
object	struct fsObject	A variable number of fsObject structures. The number of structures depends on the individual sizes of each fsObject structure and the blocksize. These structures are located directly after each other with at most 1 byte of padding between them to get the structures aligned on a 2 byte boundary.
&lt;pre&gt;
struct fsObjectContainer {
    struct fsBlockHeader bheader;
    NODE parent;
    BLCK next;
    BLCK previous;
    struct fsObject object[0];
}; 
&lt;/pre&gt;

fsHashTable is the structure of a HashTable block. It functions much like the hash table found in FFS user directory blocks, except that it is stored in a separate block. This block contains a number of hash-chains (about 120 for a 512 byte block). Each hash-chain is a chain of Nodes. Each Node has a pointer to an Object and a pointer to the next entry in the hash-chain.  Using such a hash-chain you can locate an object quickly by only knowing its name.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
parent	NODE	The node number of the directory Object this HashTable block belongs to.
hashentry	NODE	An array of Nodes. Each Node represents the start of a hash-chain (singly linked). A hash-value is calculated using the name of a file or directory, and this value determines in which chain the Object is linked. If there are no entries in a hash-chain then the hashentry value is zero.
&lt;pre&gt;
struct fsHashTable {
    struct fsBlockHeader bheader;
    NODE parent;
    NODE hashentry[0];
};
&lt;/pre&gt;
To calculate the hash-value using a name of an Object as input use these routines:
&lt;pre&gt;
UWORD calchash(UBYTE *name) {
    UWORD hash=0;
    /* Calculates a hash value over the passed in string.
       The end of the string can be either a NUL byte or a
       slash. The hash function is the same as the one
       used in FastFileSystem set to international mode. */
    while(name[hash]!=0 &amp;&amp; name[hash]!='/') {
        hash++;
    }
    while(*name!=0 &amp;&amp; *name!='/') {
        hash=hash*13+upperchar(*name++);
    }

    return((UWORD)(hash % (UWORD)((blocksize-sizeof(struct fsHashTable))&gt;&gt;2)));
}
UBYTE upperchar(UBYTE c) {
    if((c&gt;=224 &amp;&amp; c&lt;=254 &amp;&amp; c!=247) || (c&gt;='a' &amp;&amp; c&lt;='z')) {
        c-=32;
    }
    return(c);
}
&lt;/pre&gt;

The BNodeContainer is used to store B-Trees. Currently only one B-Tree is in use by this filesystem and it is used to store the location of file data. The fsBNodeContainer structure contains two other structures. The fsBlockHeader structure and the BTreeContainer structure.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
btc	struct BTreeContainer	Contains information about the B-Tree and its nodes contained in this block.
&lt;pre&gt;
struct fsBNodeContainer {
    struct fsBlockHeader bheader;
    struct BTreeContainer btc;
}; 
&lt;/pre&gt;


First try and locate the Root block. It should start with &quot;ROOT&quot;.  SFS has two of these, one at the start of the partition and one at the end.  One of the fields contains the block size, which will be the size of all important SFS blocks.

The root block has the root object container, which contains information about files and directories in the root directory.  The object 
containers basically hold one or more smaller structures that represent files and directories.  Scanning them all should give you a list of 
files and directories.

The root block also has the root of the Extent B-Tree.  This is a standard B-Tree structure (not a binary tree) that is used commonly in 
all kinds of system, you can read about how they work on Wikipedia if needed.  The B-Tree holds the information about *where* all the data is 
located for your files.

To recover your files, I'd do this:

* Find one of the root blocks, if not present, then figure out the block size your disk was using, and scan every block in turn to see if it 
looks like an ObjectContainer (check the fsBlockHeader's ID, check if the ownblock number is equal to the block you are currently scanning, 
and check its checksum).  So if you currently have block 12, and you see a block with the correct id, and ownblock = 12 and its checksum is good, 
then that's probably a valid ObjectContainer.

* With all the ObjectContainers found, you can extract filenames and directory names from these, but also the number of their first data 
block (in the field data) and the file size.  For small files (less than blocksize) this data block will be enough to recover the data.
For larger files, you might be lucky and all the remaining blocks are found after the first one (if the file was defragmented).  You can't be
sure of that though so...

* For larger files, you need to find all the BNodeContainers.  You could scan these in the same way you found all the ObjectContainers (look for 
blocks with the correct id, ownblock number and checksum). 

* With all the BNodeContainers found, you can try looking up the first data block of a file in the B-Tree structure.  This is a bit complicated 
-- the B-Tree consists of non-leaf nodes (blocks that only contain pointers to other B-Tree blocks), the isLeaf flag indicates this.  Or it 
can be a B-Tree leaf block.  The leaf blocks contain extra information per entry (see https://hjohn.home.xs4all.nl/SFS/extents.htm)
&lt;pre&gt;
struct fsExtentBNode {
     ULONG key;
     ULONG next;
     ULONG prev;
     UWORD blocks;
};
&lt;/pre&gt;

The key should be a block of a file (the first of a range), that is 1 to 65535 block long (depending the &quot;blocks&quot; field).  If the file is split 
up into more parts, then &quot;next&quot; will contain block number of the next range of blocks.  You need to look this up again in the B-Tree 
structure to find out how large it is. 

You can for the most part ignore the other structures (bitmap, admin containers).  The fsObjects and B-tree containers is what you'll need to 
recover the data. 


====Resources====

&lt;pre&gt;
rom/storage/mmakefile.src 
rom/storage/storage.conf 
rom/storage/storage_device.c 
rom/storage/storage_ids.c 
rom/storage/storage_init.c 
rom/storage/storage_intern.h 
rom/storage/storage_mount.c 
rom/storage/storage_unit.c
&lt;/pre&gt;

&lt;pre&gt;
rom/storage/includes/device.h 
rom/storage/includes/unit.h 
rom/storage/includes/volume.h 
rom/storage/storage_intern.h 
&lt;/pre&gt;

&lt;pre&gt;

&lt;/pre&gt;

*[[Aros/Developer/Docs/Resources/ACPI|acpi.resource]]
*[[Aros/Developer/Docs/Resources/Battclock|battclock.resource]]
*[[Aros/Developer/Docs/Resources/Bootloader|bootloader.resource]]
*[[Aros/Developer/Docs/Resources/Cia|cia.resource]]
*[[Aros/Developer/Docs/Resources/Filesystem|FileSystem.resource]]
*[[Aros/Developer/Docs/Resources/Hostlib|hostlib.resource]]
*[[Aros/Developer/Docs/Resources/Kernel|kernel.resource]]
*[[Aros/Developer/Docs/Resources/Misc|misc.resource]]
*[[Aros/Developer/Docs/Resources/Processor|processor.resource]]


==Debugging Code==

Please use the [http://sourceforge.net/tracker/?group_id=43586&amp;atid=439463 AROS Bug Tracker] if any issues are found.


GRUB Command line list

&lt;pre&gt;
sysdebug  
usbdebug - allows to see Poseidon's log in debug output
&lt;/pre&gt;


How do I get debugging out of InitResident ? If running i386 hosted on linux sysdebug=initresident on command line.
This  way  you can enable any of listed flags. sysdebug=all stands for &quot;everything&quot;


Have an executable (crosscompiled C++ code) which has 6 MB size on disk, but after loading it in memory, 250 MB RAM is taken. Any software that would split AROS executable into ELF part which would show actual size values?

 readelf -S executable

it will show you all sections in elf file, including sizes and requested alignment.

 objdump -h filename

That's will give you a quick overview of the sections and sizes. Ignore all the .debug.* sections. 
Would hazard a guess that you have a large .bss section. That's pretty common in C++.

Next step:

 nm—size-sort filename | grep ' [bB] '

The last few will be your biggest consumers. Would suggest -C to demangle the symbols... ;)


Suggest profiling the program (just use some printf's in the main loop for time spent in each part), it usually is quite easy to spot slow parts in games or apps.

If someone has '#define IPTR ULONG' somewhere. To see where that define is, redefine IPTR in the source code that fails, just above the line that fails, and the preprocessor will tell you where it was defined first.

===How to setup gdb with AROS/hosted===

Download AROS sources (AROS-xxxxxxxx-source.tar.bz2, where xxxxxxxx is the current date) and AROS contrib sources (AROS-xxxxxxxx-contrib-source) from 

Untar-bzip2 and cd to the unpacked archive directory.

 &gt; tar -xvjf AROS-xxxxxxxx-source.tar.bz2
 &gt; cd AROS-xxxxxxxx-source

Check the link to &quot;contrib&quot; (contrib-source) inside directory, e.g. correct like this:

 &gt; rm contrib
 &gt; ln -s ../AROS-xxxxxxxx-contrib-source.tar.bz2 contrib

Make sure you have the correct locale setting, otherwise compilation will fail at some point. See [http://aros.sourceforge.net/documentation/developers/compiling.php#setting-the-locale-to-iso8859 here] (or link below) for more on that. You might have to enter this:

 &gt; export LANG=&quot;en_US.ISO-8859-1&quot;

Now configure for a debug build - see &quot;./configure --help&quot; for more - here are two examples:

 &gt; ./configure—enable-debug=stack,modules,symbols
 
 &gt; ./configure—enable-debug=all

You may &quot;make&quot; now, or choose a separate directory for your build (e.g. for easy removal), for example if compiling for i386 architecture you could create a directory like this:

 &gt; mkdir linux-i386
 &gt; cd linux-i386
 &gt; ../AROS/configure—enable-debug=stack,symbols,modules

When done configuring you're ready to go:

 &gt; make

Building AROS takes some time - minutes on fast machines (e.g. 2.5&amp;nbsp;GHz quadcore), up to hours on slower machines.
The result will be AROS Linux hosted with gdb debugging enabled.

See aros.org documentation for more on compiling AROS, including more [http://aros.sourceforge.net/documentation/developers/compiling.php --enable-debug] options.


When finished, enter bin/linux-i386/AROS directory (replace &quot;linux-i386&quot; with your compilation target platform, e.g. linux-x86_64, etc.) inside the unpacked archive directory. This directory contains the required .gdbinit file for properly running AROS inside gdb.

 &gt; cd bin/linux-i386/AROS

Run AROS (here: with 128MB of memory) from gdb:

 &gt; gdb—args boot/aros-unix -m 128
or
 &gt; gdb—args boot/arosboot -m 128

 (gdb) r

Watch the shell output - in case AROS complains about &quot;LoadKeyCode2RawKeyTable: Loading &quot;DEVS:Keymaps/X11/keycode2rawkey.table&quot; failed!&quot; you should also see some instructions on how to create a keymap table. (see link above &quot;more on compiling&quot;, too.)
Quit gdb, and try default keymap table:

 (gdb) q
 The program is running.  Quit anyway (and kill it)? (y or n) y
 &gt; cd ../../..
 &gt; make default-x11keymaptable

Re-run AROS, as described above. Try e.g. RAros (= right windows key) + W to open a shell. If this doesn't work you have to create a keymap table yourself, quit gdb again, and make a new keytable:

 &gt; make change-x11keymaptable

A window will open. Watch the window's title bar, and follow the instructions.

When done, re-run AROS. RAros + W should now open a shell.

Next, compile your program with gdb support.


When you start GDB is there a warning which says

   warning: File &quot;&lt;whatever&gt;/.gdbinit&quot; auto-loading has been declined by your `auto-load safe-path' set to ...

If so start gdb with &quot;-ix .gdbinit&quot;


&lt;pre&gt;
Summary - In short:

* build AROS with debugging support (i.e. ./configure --enable-debug=all)
* build your application with debugging support (i.e. option -g)
* run AROS in the GNU debugger (you may use the GUI frontend &quot;ddd&quot; which simplifies usage a bit)
* start your application
* use the commands &quot;findaddr&quot; and &quot;add-symbol-file&quot; as written in the debugging manual
* if the debugger doesn't find the source code of your application use the &quot;dir&quot; command of the debugger. 
&lt;/pre&gt;

===How to use gdb===

In AROS open a shell, then (in host shell) use CTRL-Z to go into gdb. Use &quot;b Exec_CreatePool&quot; (one of the functions used early on by startup code in programs) to add a breakpoint, then &quot;cont&quot; and gdb will interrupt somewhere early during startup of &quot;program&quot;. Use &quot;bt&quot; to show backtrace and &quot;loadseg&quot; for &quot;??&quot; entries. One of them will be for &quot;program&quot;. After that you can use &quot;disassemble program&quot;.

One thing you need to make sure is that .gdbinit you have in your build directory is the same as in source tree. It has been modified some time ago, but the build system does not refresh it - you need to copy it manually

To recap, please read our debugging [http://aros.sourceforge.net/documentation/developers/debugging.php manual]:


To detect segfaulting when loading, try...

 ./configure—enable-debug—with-optimization=&quot;-O2&quot;

Because crash or no crash may depend on optimization. For newer compilers maybe this helps...

 --with-optimization=-&quot;-O2 -fno-strict-aliasing&quot;

One way to make crashes less random (more easily reproducible) is to activate the munging of free memory in rom/exec/freemem.c which is normally commented out:

&lt;pre&gt;
Index: freemem.c
===================================================================
--- freemem.c   (revision 34289)
+++ freemem.c   (working copy)
@@ -154,11 +154,12 @@
         * created with their TCB placed in the tc_MemEntry list. The workaround
         * is to avoid munging when FreeMem() is called with task switching disabled.
         */
+
        /* DOH! it doesn't work even this way. What's wrong???
-        *
-        * if ((SysBase-&gt;TDNestCnt &lt; 0) &amp;&amp; (SysBase-&gt;IDNestCnt &lt; 0))
-        *      MUNGE_BLOCK(memoryBlock, MEMFILL_FREE, byteSize);
         */
+
+       if ((SysBase-&gt;TDNestCnt &lt; 0) &amp;&amp; (SysBase-&gt;IDNestCnt &lt; 0))
+           MUNGE_BLOCK(memoryBlock, MEMFILL_FREE, byteSize);

     }
&lt;/pre&gt;

Mungwall can be turned on at runtime. Currently this works in all hosted versions. Just specify &quot;mungwall&quot; on kernel command line and it works. It can work on native too. In order to enable it you need to parse kernel command line, and if &quot;mungwall&quot; is present, set EXECF_MungWall bit in IntExecBase.IntFlags.

This needs to be done before the first AllocMem() for obvious reasons. And never reset back this flag! If you change it on a working system, you are doomed.

Hosted ports do the processing in rom/exec/prepareexecbase.c --enable-debug=mungwall option in configure still works but is going obsolete.  A kludge in rom/exec/allocmem.c is responsible for this and it needs to be removed when the transition is done.

BTW,  on  i386-pc  port it can be activated by &quot;mungwall&quot; argument on command line, you don't need to rebuild AROS.
New mungwall affects not only AllocMem()/FreeMem(), but also pools. I also tested it with AllocAbs(), seems to work correctly.

Runtime mungwall works on:

* pc-i386
* pc-x86_64
* linux-i386
* linux-x86_64
* darwin-x86
* linux-ppc

Works on all hosted ports, if the port itself is working.

* amiga-m68k
* Not on sam440-ppc and efika-chrp-ppc, even if they would be able to be built at moment. Does not work on (for now, need NVRAM support)

When starting my freshly rebuilt i386-linux-aros which was compiled with full debugging support I get sometimes the error &quot;Program exited with code 0377&quot;. Add the following to your .gdbinit: 
 set follow-fork-mode child

Here are some of the custom AROS gdb functions (defined in &quot;.gdbinit&quot; file) to resolve &quot;in ?? ()&quot; entries in backtrace: 
&lt;pre&gt;
#0 0xb7ffd424 in __kernel_vsyscall ()
#1 0xb7e2a657 in sigsuspend () from /lib/libc.so.6
#2 0xb7c63900 in ?? ()
#3 0xb7c640e3 in ?? ()
#4 0xb7c641e0 in ?? ()
&lt;/pre&gt;

You can use

 loadseg 0xb7c63900
 loadframe 2
or
 loadbt
and some others. Use &quot;help &quot; for a little help text. If the commands do not work try &quot;loadkick&quot; first.


Use &quot;thistask&quot;, &quot;taskready&quot;, &quot;taskwait&quot; to get list of AROS tasks. &quot;bttask &quot; shows backtrace of a task which is in ready or in wait queue and &quot;loadseg&quot; to resolve &quot;??&quot; entries in it's backtrace (&quot;loadframe&quot; would not work as it assume current running task).

===Native debugging tools for AROS===

 to enable debugging at boot time entering the GRUB menu editing line (E key) and adding &quot;debug=memory&quot; to your boot line, then press Ctrl+X to complete booting.


SYS:Tools/Debug/'''Bifteck'''

Open a shell and enter the line below to run Biftek and grab the debug messages collected in RAM into a text file.

 tools/debug/bifteck &gt; ram:debug.txt

and certainly does not open a window. It is a shell tool and only dumps data located from the debug location.
It is therefore important to 'catch' that debug data as soon as possible (before it gets overridden). You should invoke bifteck at the first opportunity before doing anything else.  You can use the TO option to store bifteck output to a file or you can pipe it manually to a file.  


SYS:Tools/Debug/'''Sashimi''' - displays error messages

One suggestion is to do a bug() debugging. Each time bug() is executed it will be output on sashimi. 
You include &lt;aros/debug.h&gt; and place bug(&quot;something\n&quot;); in your source code at location though which control passes.

To get the output - open an aros shell

 SYS:Tools/Debug/sashimi &gt; RAM:out.txt

'''Ctrl C''' to end the output to the RAM Disk.

# open shell, and type
# ram: (to switch to ram drive)
# System:Tools/Debug/Sashimi &gt; mylogfile.txt
# open AHI prefs using wanderer (or use another opened shell)
# play test sound
# close AHI prefs
# shell still open with Sashimi running: press ctrl-c to break Sashimi and return to prompt.
# in shell: copy mylogfile.txt System: (or to your required location)


SYS:Utilities/'''Snoopy''' - monitors OS function calls, run &quot;Sashimi&quot; to see Snoopy's output


SYS:Tools/'''WiMP'''    - the Window (and Screens) Manipulation Program

You can use the -E option of gcc to find out how preprocessor macros are expanded.

===Errors===

crash in strcasecmp usually means that one of its arguments is NULL.

empty space between these two names, prossibly some invisible character 

Old Amiga [http://www.amigacoding.com/index.php?title=Guru_codes&amp;redirect=no Guru Codes]

If the crash is in intuition. Sometimes, if it relates to text, a null pointer sets it off. 
an uninitialised pointer can have any address (this is a common fault).


Compiling on 64bit, Many old code would not properly typecast when doing pointer-integer conversions and thus at least throw a warning. This can easily be located and fixed.

[http://www.aros.org/cs/documentation/developers/app-dev/portable.php Portable code] 

* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.
* Fix (change IPTR/SIPTR back to ULONG/LONG) the few places which really rely on ULONG/LONG being exactly 32 bit. That's for things like pixel (ARGB) buffers, structs written/read to disk, colormaps, but probably not much else.

Then again, many current compilers also throw a warning when you try to assign a pointer value to an integer and the integer is possibly too small. This happens under .NET for example when a 64 bit pointer is assigned to something like an ULONG - so exactly the case which you described.


=== AI ===
                  Multimodal
                   Context
                   Prompt
                    &lt;---
  Model &lt;---&gt; Agent ---&gt; End user
 engine 

 Gemini      LMStudio
  Qwen       Comfyui
   etc

Recent, self hosting locally on laptops, mini pcs or desktops with '''quantization''' 4bit has reduced memory requirements but still require 16Gb+ and no high end gpu for text based 

*[https://lmstudio.ai/download LMstudio single gpu],

Google Gemma 4 Model 
*[ 12B QAT] 


Alibaba Cloud's [https://huggingface.co/ Qwen] team series of large language models LLMs 
*[https://huggingface.co/models?other=qwen3 Qwen 3], [], 
*[https://huggingface.co/models?other=qwen2 Qwen 2], [https://huggingface.co/Qwen/Qwen2.5-Coder-32B qwen 2.5 Coder],  


Small models 
*[ glm-ocr]
*[ medGemma]
*[ qwen 3.5-4b]
*[https://github.com/sipeed/picoclaw picoclaw claude] 


Bigger LLMs but with settings 
*[https://ollama.com/download Ollama single gpu]
*[https://github.com/ggml-org/llama.cpp/releases llama.CPP multi gpus],
*[ VLM multiple gpus],
Multimedia 
*[ Kimi K3], 


For the full experience 
#Training learning using 1+ high end GPUs at least 16GB VRAM per GPU card or 64Gb+ of unified, 16Core CPU with at least 64Gb of RAM system memory, though training can take weeks 
#Inference with custom asics or GPUs 

*[ MiniMax H3] for audio and video but gpu 8Gb+ 
*[https://github.com/jamiepine/voicebox voicebox]
*[https://github.com/ideogram-oss/ideogram4 ideogram4]
*[https://github.com/calesthio/OpenMontage OpenMontage]

&lt;pre&gt;
Text to Audio --\
Text to Video --/ Reference Video --&gt; Video and Audio output 
&lt;/pre&gt;

=== Example ===

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/* 1. Header for your name,date,purpose of program.
2. Pre-processor directives. This will include the #includes for files you want to add. 
3. Includes for function prototypes if necessary.
4. Main()
Create Pointers for Libraries and any Window you want to open.
5. Open necessary libraries.
6. Check if open exit program if fail.
7. Open a window exit program if fail.
8. Add your program
9. Close Window
10 Close Libraries.
11 End Program. */

/* standard os included headers &lt;.h&gt; */
#include &lt;dos/dos.h&gt;
#include &lt;dos/dosasl.h&gt;
#include &lt;dos/dosextens.h&gt;
#include &lt;dos/exall.h&gt;
#include &lt;dos/rdargs.h&gt;
#include &lt;exec/memory.h&gt;
#include &lt;exec/types.h&gt;
#include &lt;utility/utility.h&gt;
#include &lt;intuition/intuition.h&gt;

/* define as unresolved external references (proto/xxx.h) and compiler will link to auto(matically) open library */ 
#include &lt;proto/arossupport.h&gt;
#include &lt;proto/dos.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/graphics.h&gt;
#include &lt;proto/cybergraphics.h&gt;
#include &lt;proto/datatypes.h&gt;
#include &lt;proto/icon.h&gt;

#include &lt;workbench/workbench.h&gt;
#include &lt;workbench/icon.h&gt;

#include &lt;datatypes/pictureclass.h&gt;

#include &lt;proto/muimaster.h&gt;
#include &lt;libraries/mui.h&gt;

#include proto/bsdsocket.h

#include &lt;ctype.h&gt;
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;string.h&gt;

/* my own headers &quot;.h&quot; */

#define CTRL_C      (SetSignal(0L,0L) &amp; SIGBREAKF_CTRL_C)
#define  isDir(fib) ((fib)-&gt;fib_DirEntryType &gt;= 0)

#define ARG_TEMPLATE    &quot;FILE/A,ALL/S,QUIET/S,W=WIDTH/N,H=HEIGHT/N,M=METHOD,DEFTOOL&quot;

int main(void)
{


	return retval;
} /* main */
&lt;/syntaxhighlight&gt;

If you used c++, there is not yet c++ support in our shared library system. 
The easiest way to create / compile a shared library would be to use the AROS build system but the libraries can be created manually. You have to create a ROMTAG structure and some header files.  

A shared library is built with the %build_module macro with a line like this:

 %build_module mmake=MetaTarget modname=mylib modtype=library files=SourceFiles 

This macro can build different AROS module types, like devices, Zune classes, HIDDs, etc.

&lt;pre&gt;
##begin config
version 1.0
##end config

##begin functionlist
void func1(LONG a, LONG b)
int func2(char *s, ULONG a)
##end functionlist
&lt;/pre&gt;


Alternatively,  

&lt;pre&gt;
#ifndef LIB_H
#define LIB_H

#define __NOLIBBASE__

#include &lt;exec/libraries.h&gt;
#include &lt;exec/semaphores.h&gt;
#include &lt;dos/dos.h&gt;

#ifdef __AROS__
//#include &lt;aros/debug.h&gt;
#define reg(x)
#define __saveds
#endif

#define USESYSBASE struct ExecBase *SysBase = Base-&gt;My_SysBase;

struct MyTestBase
{
  struct Library   My_Test_Lib;
	struct ExecBase *My_SysBase;
	APTR             My_SegList;
  int              testint;
};

#endif
&lt;/pre&gt;

&lt;pre&gt;
/*--------------------------------------------------------------------------*/
/* Resident header written for mytest.library */
/*--------------------------------------------------------------------------*/

#define __NOLIBBASE__

#define VERSION         1
#define REVISION        0

#define LIBHEADNAME     mytest
#define LIBHEADNAMESTR &quot;mytest&quot;
#define COMPDATE        &quot;04.10.2015&quot;
#define VERS            &quot;1.0&quot;

#define LIBBASETYPE 	struct MyTestBase
#define LIBBASETYPEPTR  LIBBASETYPE *

#include &lt;aros/debug.h&gt;
#include &lt;exec/exec.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;exec/resident.h&gt;
#include &lt;exec/nodes.h&gt;
#include &lt;exec/libraries.h&gt;
#include &lt;aros/symbolsets.h&gt;
#include &quot;lib.h&quot;

const UBYTE lib_name[] = LIBHEADNAMESTR &quot;.library&quot;;

const UBYTE lib_id[] = &quot;$VER: &quot; LIBHEADNAMESTR &quot;.library &quot; VERS &quot; (&quot; COMPDATE &quot;) by ALB42\n&quot;;

extern const APTR FuncTable[];

AROS_UFP3 (LIBBASETYPEPTR, InitLib,
    AROS_UFPA(LIBBASETYPEPTR, Base, D0),
    AROS_UFPA(BPTR, seglist, A0),
    AROS_UFPA(struct ExecBase *, sysbase, A6)
);

static struct LibInitStruct
{
    IPTR                   LibSize;
    const APTR             *FuncTable;
    const struct DataTable *DataTable;
    APTR                    InitFunc;
}
const LibInitStruct =
{
    sizeof(LIBBASETYPE),
    FuncTable,
    NULL,
    (APTR)InitLib
};

const struct Resident romtag =
{
  RTC_MATCHWORD,              /* match word */
  (APTR)&amp;romtag,              /* back pointer */
  (APTR)(&amp;romtag + 1),        /* skip pointer */
  RTF_AUTOINIT | RTF_EXTENDED,/* flags */
  VERSION,                    /* version */
  NT_LIBRARY,                 /* type of module */
  0,                          /* init priority */
  (STRPTR)lib_name,           /* module name */
  (STRPTR)lib_id + 6,
  (APTR)&amp;LibInitStruct,
  REVISION, NULL
};

AROS_UFH3 (LIBBASETYPEPTR, InitLib,
    AROS_UFHA(LIBBASETYPEPTR, Base, D0),
    AROS_UFHA(BPTR, seglist, A0),
    AROS_UFHA(struct ExecBase *, sysbase, A6)
    )
{
    AROS_USERFUNC_INIT
    
    Base-&gt;My_SegList = seglist;
    Base-&gt;My_SysBase = (APTR)sysbase;
    Base-&gt;testint = 0;
    
    USESYSBASE
    bug(&quot;InitLib\n&quot;);
    
    if (!set_open_libraries())
    {
      set_close_libraries();
      return NULL;
    }
    
    return Base;
    
    AROS_USERFUNC_EXIT
}

AROS_LH1(LIBBASETYPEPTR, LibOpen,
    AROS_LHA (ULONG, version, D0),
    LIBBASETYPEPTR, Base, 1, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    
    USESYSBASE
    bug(&quot;LibOpen\n&quot;);

    (void)version;
    
    Base-&gt;My_Test_Lib.lib_OpenCnt++;
    return Base;

    AROS_LIBFUNC_EXIT
    
}

__saveds APTR LibExpungeInternal(LIBBASETYPE *Base reg(a6))
{
  USESYSBASE
  APTR seglist;
  bug(&quot;LibExpungeInternal\n&quot;);

  if (Base-&gt;My_Test_Lib.lib_OpenCnt)
  {
    return 0;
  }

  seglist = Base-&gt;My_SegList;

  Forbid();
  Remove((struct Node*)Base);
  Permit();
  FreeMem((APTR)Base - Base-&gt;My_Test_Lib.lib_NegSize, (LONG)Base-&gt;My_Test_Lib.lib_PosSize +
    (LONG)Base-&gt;My_Test_Lib.lib_NegSize);
  
  set_close_libraries();
  return seglist;
}

AROS_LH0(BPTR, LibClose,
    LIBBASETYPEPTR, Base, 2, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;LibClose\n&quot;);

    if (!(--Base-&gt;My_Test_Lib.lib_OpenCnt))
    {
      return LibExpungeInternal(Base);          
    }
    return 0;
	
    AROS_LIBFUNC_EXIT
}

AROS_LH1(BPTR, LibExpunge,
    AROS_LHA(LIBBASETYPEPTR, Base, D0),
    struct ExecBase *, sysBase, 3, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT

    (void)sysBase;
    
    USESYSBASE
    bug(&quot;LibExpunge\n&quot;);

    return LibExpungeInternal(Base);
	
    AROS_LIBFUNC_EXIT
}

AROS_LH0(LIBBASETYPEPTR, LibReserved,
    LIBBASETYPEPTR, Base, 4, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;LibReserved\n&quot;);

    return 0;
    //return (APTR)LibReserved();
    
    AROS_LIBFUNC_EXIT
}


// Space for your own functions
// do not forget to update the FuncTable as well

AROS_LH1(int, TestFunction,
    AROS_LHA(int, TestValue, D0),
    LIBBASETYPEPTR, Base, 5, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;TestFunction\n&quot;);

    Base-&gt;testint = TestValue + Base-&gt;testint;
    
    return Base-&gt;testint;
    
    AROS_LIBFUNC_EXIT
}

// Functable -&gt; Table of all functions in the Library, in right order - important!

const APTR FuncTable[] = 
{
    &amp;AROS_SLIB_ENTRY(LibOpen,LIBHEADNAME,1),
    &amp;AROS_SLIB_ENTRY(LibClose,LIBHEADNAME,2),
    &amp;AROS_SLIB_ENTRY(LibExpunge,LIBHEADNAME,3),
    &amp;AROS_SLIB_ENTRY(LibReserved,LIBHEADNAME,4),
    &amp;AROS_SLIB_ENTRY(TestFunction,LIBHEADNAME,5),
    (void *)-1
};

// AutoInit stuff
void *__PROGRAM_ENTRIES__symbol_set_handler_missing;
void *__LIBS__symbol_set_handler_missing;
// end of AutoInitStuff
&lt;/pre&gt;

Makefile
&lt;pre&gt;
VPATH = 
CFLAGS = -O2 -g -fomit-frame-pointer -W -Wall -Wno-parentheses
CC = i386-aros-gcc
LD = i386-aros-gcc
LDFLAGS = -nostartfiles -Wl,-Map -Xlinker linkermap
LIBS = -lautoinit -llibinit
STRIP = i386-aros-strip --strip-unneeded --remove-section .comment

OBJS = lib_header.o 

all: mytest.library

mytest.library: $(OBJS)
	$(LD) $(LDFLAGS) $^ $(LIBS) -o $@

lib_header.o: lib_header.c lib.h

clean:
	rm -f *.o *.library *.ppu testlibrary linkermap
&lt;/pre&gt;


Porting UNIX library to AROS - dealing with static variables which would make it easy to port such libraries to AROS, keeping the benefits of sharing them on disk, but losing the benefit of actually sharing them in memory.

Our problem arises by the fact we want to share the actual code (the .text section of the library) and constant data, but we need to have per-task .bss and .data sections. If we get rid of our intention to share the .text and .rodata sections, things get quite easy: just load and relocate the library whenever it's open, by whoever it's open. It's like statically linking the library into the executable, except that the final linking is done at runtime.

In the V0 branch, in workbench/hidds/hidd.nouveau was committed pcimock.hidd. This is a pci driver that allows mocking real PCI devices under linux-hosted. The main idea is to be able to run the real hardware driver under linux-hosted with as little changes as possible (some changes will always be needed though unless someone wants to write complete device simulator) so that driver's code paths can be executed and debugged using gdb. This was a very helpful capability when porting nouveau. Now it is externalized from nouveau.hidd and can be used by other people porting drivers. The pcimock.hidd can currently mock 4 different nvidia cards, 1 AGP bridge and also mock irq.hidd.

What's the difference between this driver and the pcilinux.hidd? I used that one to develop many different HW drivers for aros. As far as I understood the intention of pcilinux.hidd it is supposed to get access to real hardware that is running under linux. The pcimock.hidd goal is to mock the hardware. For example my dev box is a PCIE system, but I still would like to run the AGP codes paths in nouveau under linux-hosted to check if they don't seg fault. The other case would be to run codes paths for hardware that the developer does not have (Fermi cards in my case). In the case of pcimock.hidd, the AROS driver's code paths will execute as long as you add proper mocking (for example fill in PCI config area or values for registers in BARs). This is an advantage for ported drivers - the code should already work (since it worked on another system) but there might have been mistakes made during porting which can be detected easily with gdb.

In case you are writing your driver from scratch, pcilinux.hidd hidd will give you more advantage, since you can actually access the real hardware from linux-hosted.


== Misc ==

===APL, MPL, BSD, GPL and LGPL Licences===

The majority of AROS sources in licensed under AROS Public License ([http://aros.sourceforge.net/license.html APL]) which (to a degree) protects us from someone taking AROS sources and not contributing improvements back (for example MorphOS took some AROS source and then contributed changes back)

It is written to allow the use of AROS code in other open source or commercial projects without exception whilst providing a mechanism so that improvements/additions can find their way back to the original source in one form or another.

There are &quot;3rd&quot; party applications used by AROS that do not fall under this license, which are an extra &quot;Contrib&quot; download for convenience.

Anyone can port GPL-ed network and sound drivers as AROSTCP and AHI are GPLed. Direct using (porting) [http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs GPL]-ed code in other parts of AROS (gfx, sata, usb) is not possible because AROS license is not compatible with GPL. You need to utilize permissive licensed code like BSD or MIT/X11.


BSD and MPL license are the closest to APL.

APL however is not so compatible with LGPL/GPL.

LGPL case - you cannot statically combine APL code with LGPL. You can, however thank to LGPL being &quot;lesser&quot; restrictive, use LGPL dynamically loaded libraries in APL codes.

GPL case - you cannot combine APL code with GPL in any way if there is no explicit clause by GPLed code authors allowing that. If you do combine APL with GPL in &quot;bad&quot; ways described above - you have a problem (you violate GPL). This problem might result in everything in AROS becoming GPL or everything running or AROS becoming GPL (here I'm not sure really). The other scenario is that you are not allowed to legally distribute such code at all. To be honest I have grasped how to violate GPL, but I'm still no exactly sure what happens when you violate it (but I'm sure it's not anything nice)

GPL software can run on top of non-GPL &quot;system components&quot; (see system components exception of GPL), but the other way around (non-GPL using GPL) leads to problems. This means applications like scout, or Quake III are ok (in the majority of cases).

Theres no reason GPL drivers cannot be ported - but they cant be in AROS's ROM (requires linking APL code with GPL), nor can AROS depend on them (e.g. they must use existing apis).
If they are launched (dynamically linked) by a user action that is allowed. It is also allowed to distribute such binaries together for convenience.

GPL is not about statical or dynamic linking but is about executing process and function calls.


These components - SFS, isapnp, Zune texteditor, AHi, network drivers, freetype, openuirl, BHFormat, Edit and (&quot; dynamically loaded libraries&quot;) are LGPL, not GPL. Mesa/Nouveau stuff is MIT. Some user tools are GPL though.

'''AROS (system)'''
* system components (libraries/classes/devices/etc) cannot be GPL as they would propagate GPL to complete system as well as GPL is not compatible with MPL from which APL is based 
* system components can be LGPL v2 or a permissive license (MIT/BSD)
* system applications can be anything you like (but still I would prefer APL or permissive so the code can be reused if needed)

'''Contrib:'''
* no rules - contrib does not impact AROS system since nothing in AROS system depends on contrib.

About stealing code: The chances of this happening is exactly the same whether we are APL or GPL. If any closed-source option wanted to do it, there is no one that can validate otherwise. MorphOS has used some AROS codes, but contributed changes back.

The rationale behind APL is that while it guarantees that the original developer will get the improvements back (to a certain degree - file based), the person who uses the codes does not have to open his original codes. BSD does not guarantee that the original developer gets improvements. GPL requires the person using the codes to open his codes as well.

The copyright holders needs to stay - we just need information from them that the codes are available under APL (for example a checked-in file like in case of Poseidon). We don't do transfer of copyrights.

; Ultimately what can and cannot be done is up to the author(s) - not the licence.

===AROS source code tree===

* http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-trunk.txt
* http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-contrib.txt


Found this interesting (non-GPL) licensing 'anomaly' - to keep in mind for distributors.

Programs that lose their license if sold (&quot;non-profit only&quot; licensed):
  contrib/aminet/comm/term/TinyTerminal
  contrib/aminet/dev/basic/bwBASIC
  contrib/aminet/text/edit/xdme
  contrib/fish/aroach
  contrib/fish/lotto
  contrib/fish/shuffle
  contrib/fish/touch
  + cdvdfs.


Here is a list of all the GPL/GPLv2/GPLv3 licenses fossology found, what have explicit licenses in their comments.


 excluded LGPL, BSD/GPL dual licensed and programs (such as Prefs/Edit and BHFormat)

&lt;pre&gt;
AROS/rom/dbus/include/  AFL_v2.1 ,GPL_v2+  (supposedly AFL &lt; 3 is GPL incompatible) 
AROS/workbench/classes/zune/betterstring/include/  GPL_v2+
AROS/workbench/classes/zune/texteditor/include/  GPL_v2+
AROS/workbench/classes/datatypes/gemimage/ GPL_v2+ GPL
AROS/workbench/classes/datatypes/degas/  GPL_v2+
AROS/workbench/libs/openurl/README: GPL
AROS/workbench/network/smbfs/documentation/  GPL_v2
AROS/workbench/network/smbfs/source_code/  GPL_v2+
AROS/workbench/network/stacks/AROSTCP/bsdsocket/kern/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/mmakefile.src conf.h  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/sys/  CMU ,GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/net/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/api/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/conf/conf.h: GPL_v2
AROS/workbench/network/stacks/AROSTCP/netinclude/net/radix.h: CMU ,GPL_v2
AROS/workbench/devs/AHI/AHI/  GPL_v2+
AROS/workbench/devs/AHI/AddAudioModes/ GPL_v2+  AROS/workbench/devs/AHI/AddAudioModes/COPYING: GPL 
AROS/workbench/devs/AHI/Docs/texinfo.tex: GPL_v2+
AROS/workbench/devs/AHI/COPYING: GPL
AROS/workbench/devs/AHI/Drivers/EMU10kx/  GPL_v2+
AROS/workbench/devs/AHI/AHI-Handler/  GPL_v2+
AROS/workbench/devs/networks/rtl8029/  GPL   GPL_v2+
AROS/workbench/devs/networks/pcnet32/  GPL   GPL_v2+
AROS/workbench/devs/networks/ppp/LEGAL: GPL
AROS/workbench/devs/networks/atheros5000/  GPL_v2+
AROS/workbench/devs/networks/rhine/  GPL_v2+
AROS/workbench/devs/networks/nForce/  GPL_v2+  GPL
AROS/workbench/devs/networks/prism2/  GPL  GPL_v2+
AROS/workbench/devs/networks/fec/LEGAL: GPL
AROS/workbench/devs/networks/rtl8139/  GPL  GPL_v2+
AROS/workbench/devs/networks/etherlink3/  GPL  GPL_v2+
AROS/workbench/devs/networks/intelpro100/  GPL  GPL_v2+
AROS/workbench/devs/networks/rtl8169/  GPL   GPL_v2+
AROS/workbench/devs/networks/emac/   GPL   GPL_v2+
AROS/workbench/devs/networks/rtl8168/  GPL  GPL_v2+
AROS/workbench/devs/networks/realtek8180/   GPL_v2+
AROS/workbench/devs/networks/via-rhine/via-rhine.c: GPL_v2+
AROS/workbench/devs/networks/via-rhine/   GPL  GPL_v2+
AROS/workbench/devs/networks/e1000/  GPL_v2
AROS/workbench/devs/networks/sis900/  GPL   GPL_v2+
&lt;/pre&gt;

AHI: it has special provisions (COPYING.DRIVERS). The library is LGPL, preferences software is GPL and drivers can be anything without breaking GPL/LGPL.

Network stack: well, we are long overdue for a new, IPv6 enabled network stack anyway, anyone interested? ;) Seriously though it seems like the glue code is GPL and as all the drivers. However some of the drivers are our own code, so they could be relicensed to LGPL.

 Same filter as the AROS trunk list. These should all be libraries or plugins - no programs.

&lt;pre&gt;
contrib/regina/utsname.h: GPL_v2+

contrib/mui/classes/nlist/include/default-align.h: GPL_v2+
contrib/mui/classes/nlist/include/amiga-align.h: GPL_v2+

contrib/mui/classes/BWins/include/MUI/BWin_mcc.h: GPL
contrib/mui/classes/BWins/include/BWin_private_mcc.h: GPL
contrib/mui/classes/BWins/COPYING: GPL_v2
contrib/mui/classes/BWins/MCC_BWins.readme: GPL_v2

contrib/mui/classes/thebar/include/default-align.h: GPL_v2+
contrib/mui/classes/thebar/include/amiga-align.h: GPL_v2+

contrib/gfx/libs/wazp3d/LEGAL: GPL
contrib/gfx/libs/wazp3d/Wazp3D.readme: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d.c: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d_opengl.h: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d_opengl.c: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/Wazp3D.h: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/Wazp3D.c: GPL

contrib/libs/mpega/  GPL_v2+
&lt;/pre&gt;

http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-contrib.txt

===Types===

On AROS following rules apply:
&lt;pre&gt; 
1. BYTE/UBYTE is 8bit, WORD/UWORD is 16bit, LONG/ULONG is 32bit, QUAD/UQUAD is 64bit, the types are comparable with stdint types (int8_t, int16_t, int32_t, int64_t)
2. IPTR/SIPTR are integer types large enough to fit pointer, that is sizeof(IPTR) = sizeof(APTR) = 4 on 32bit system, and = 8 on 64bit system
3. ti_Data in TagList is large enough to hold a IPTR/APTR type.
4. never store a pointer in integer of type LONG. It may work (if the pointer has upper 32bits clear), but does not have to. Compiler should warn you about that.
5. If you are unsure about point 4, allocate your memory with MEMF_31BIT flag set. But don't expect that AROS internals will do the same.
&lt;/pre&gt; 
point 4 is actually important.


* UBYTE/BYTE for 8bit
* UWORD/WORD for 16bit
* ULONG/LONG for 32bit
* UQUAD/QUAD for 64bit

&lt;pre&gt;
UBYTE    Unsigned 8 bit integer variable (byte).
BYTE     Signed 8 bit integer variable (byte).
UWORD    Unsigned 16 bit integer variable (word).
WORD     Signed 16 bit integer variable (word).
ULONG    Unsigned 32 bit integer variable (longword).
LONG     Signed 32 bit integer variable (longword).
FLOAT    32 bit IEEE floating point variable.
UQUAD    Unsigned 64 bit integer variable.
QUAD     Signed 64 bit integer variable.
DOUBLE   64bit IEEE floating point variable.
BOOL     Boolean variable, TRUE and FALSE are also defined in exec/types.h.
VOID     Void.

APTR     A generic pointer for multiple purposes - Arrays.
STRPTR   A pointer to a null-terminated string.
IPTR     Really important in AROS, the only way to declare a field that can contain both: an integer or a pointer.
&lt;/pre&gt;

if you want to write really portable app, you may be interested in standard datatypes defined in C99: int8_t, uint8_t, int16_t, uint16_t, int32_t, uint32_t, int64_t, uint64_t, intptr_t, uintptr_t. They are all defined in inttypes.h include file.

In exec/types.h the following short-cuts are typedef'd. They are used often in AROS, so you should nearly always include exec/types.h and soon only they will be removed from sys/_types.h include, all types are now defined in include files named aros/types/xxx.h.

(Preparation for C library split; sys/xxx.h include will only be available there when compiling with POSIX C library)


Compiler specific types, like int and long might change their size. In case of AROS, similar to linux, int remains 32 bit whereas long grows to 64 bits in size.

If you use Amiga-like data types, i.e. BYTE/UBYTE, WORD/UWORD, LONG/ULONG and QUAD/UQUAD or the C99 standard types (uint8_t and so on, see stdint.h include) then you should have less issues to solve than by using types without size guarantee.

Of course, all pointers grow to 64 bytes using 64bit cpu. Most of the code can be just recompiled and will work. In rare cases, where e.g. pointers are casted to integers, a special care must be taken. Especially in the cases, where pointer is casted to LONG/ULONG (this code will break on 64 bit AROS) e.g.  '#define IPTR ULONG'.

With compiler delint patches which the majority of them are simple casting issues to make the compiler happy. Notice some of the changes involve introducing double casts. In very recent versions of GCC. Yes, the bulk of the double casts are for converting 32 bit addresses (ie from a 32 bit PCI DMA address register) to a 64 bit pointer. First cast is to IPTR (to expand to 64 bits, and prevent sign extension if the address is above 0x7FFFFFFF), and then to APTR.

ULONG != IPTR except on 32bit .. so if you need to store pointers make sure and use IPTR and not ULONG (which some old code does). For this reason things like Taglist elements are 64bit (since the tag data can be a pointer). 
If your passing items on the stack you should use the STACKED attribute to make sure they are correctly aligned (on 64bit all items on the stack are 64bit..)

There is more issues like using &quot;== 0L&quot; causes problems.

===Endian===

*BE 
*LE

Use the macros from &lt;endian.h&gt; instead making a guess based upon architecture defines
 
&lt;pre&gt;
#if _BYTE_ORDER == _BIG_ENDIAN

#elif _BYTE_ORDER == _LITTLE_ENDIAN

#else
+
#error &lt;whatever.h&gt; - Byte order for this architecture is unsupported! 
&lt;/pre&gt;


===SVN and GIT===

If you want to help develop AROS OS itself, you can 

* view current GIT/SVN entries [http://aros.sourceforge.net/ Aros Org website] or [https://github.com/aros-development-team/AROS Github], [https://github.com/ezrec older ezrec mirror], [https://github.com/michalsc/AROS/ older mirror], [https://trac.aros.org/trac/timeline TRAC], [], 
* awaiting update [http://repo.or.cz/w/AROS.git git repo], [http://www.ohloh.net/p/aros/commits ohloh] or [https://svn.aros.org/svn/aros/trunk/ svn repo] and access [Git version git://repo.or.cz/AROS.git here], 
* deprecated [https://www.gitorious.org/aros/aros/commit/a7fda9e ARIX commits] or [https://gitorious.org/aros/aros GIT old]

If you have SVN access (early 2015 introduced a new SVN server, create a new account at trac aros org) and/or have obtained the source [http://aros.sourceforge.net/download.php AROS site] - you can compile the current build tools/environment using: 

 &gt; make development

and follow this [http://aros.sourceforge.net/documentation/developers/compiling.php#building procedure] or [https://github.com/apiraino/aros_guide Guide] 


https://trac.aros.org/trac#Developing

If you plan on contributing back changes, please post information about such changes first on this [http://mail.aros.org/mailman/listinfo/aros-dev/ mailing list] for more experience developers can validate whether they are correct.


Then there are the nightly build machines. They svn update before the build and run configure as one of the next steps. autoconf might be added to the nightly build scripts.

Our build relies on packages downloaded from Internet (SDL for example) - it always worked this way. The minimal requirement (when just building core AROS) is binutils and gcc. If you build contrib as well, you need many more packages to be downloaded.

https://gitorious.org/aros/aros/commits/crosstools-II

git://gitorious.org/aros/aros.git

Branch crosstools-II there is only one commit on top of ABI_V1 
&lt;pre&gt;
../../aros-src/AROS/configure --enable-ccache
--with-portssources=~/aros/Sources --target=pc-x86_64
--with-aros-toolchain-install=/home/weissms/media/data/aros/test/crosstools/pc-x86_64
&lt;/pre&gt;
and
&lt;pre&gt;
../../aros-src/AROS/configure --enable-ccache
--with-portssources=~/aros/Sources --target=pc-i386
--with-aros-toolchain-install=/home/weissms/media/data/aros/test/crosstools/pc-i386
&lt;/pre&gt;
build OK.


:''More information: [[Aros/Developer/Maintainer|AROS Maintainer Docs]]''

===SDI Calls===

Integrate the 'SDI'-headers to allow easier porting to all amiga-like platforms.

&lt;pre&gt;
PUTCHARPROTO( PutTheChar, char c, struct SPrintfStream *s  )
{
 // REAL CODE
}
&lt;/pre&gt;

have &quot;SDI_compiler.h&quot; and &quot;SDI_hook.h&quot; included

its more organized like

 #include SDI/SDI_hook.h

than

 #include SDI_hook.h

option 1 --- i also use when back porting from amiga's..

&lt;pre&gt;
#ifdef __AROS__
#include SDI/SDI_hook.h
#else
#include SDI_hook.h
#endif
&lt;/pre&gt;

also

you can add the -i include/sdi/ location if you do not want to add or edit any files.


Defining HOOKPROTO to IPTR name(struct IClass * cl, Object * obj, Msg msg); solved the problem

A MUI application most likely needs only the HOOKPROTOxxx SDI macros. They are compatible with AROS, only the attributes (hook, object attribute) must be given in the right order. examine compiler/include/aros/symbolsets.h (AROS_LIBREQ)

compiling mui stuff for aros setting -std=gnu99 is necessary (i have had -std=c99 most of the time).

===Locale with Flexcat===

Most languages have a locale, but not every app is localized, the only thing needed is to translate the &quot;catalog&quot; files. It is a case of locating the correct catalog and saving the translated version.

For every app that lacks of your language catalog and is localized anyway, you should find (in the sources) files related to locale:

* file.cd = catalog descriptor, contains base msg, with internal language (usually english)
* language.ct = catalog translation, contains every translated msg, indexed as in the file.cd.

Compare with other localized apps... Then, &quot;make my_app-catalogs&quot; should create and install your translated catalogs. ex : for, saying, sys:prefs/wanderer:

on root of AROS sources, type:
 &quot;make workbench-prefs-wanderer-catalogs&quot;
then (if you changed the .cd file):
 &quot;make workbench-prefs-wanderer&quot;

For apps not localized, you have to adapt their code to support it, if it is possible...

noticed the original .cd file has many (//) strings at the end of any voice, so added them also to the .ct file. 
That (//) is only for cd files. I'm highly recommending to use FlexCat for updating ct files, e.g. like this:

 flexcat app.cd deutsch.ct newctfile deutsch.ct

You'll get error checking and new entries are marked in the resulting ct file.

When editing .ct files, only change those lines containing translation and perhaps version string, nothing else.
The rest is up to the relevant tool, flexcat. In order to update your translation, type in the following in your shell:

 flexcat xyz.cd xyz.ct NEWCTFILE xyz_upd.ct COPYMSGNEW

This way you will not only make sure you have correct translation file but flexcat also pre-fills newly added strings with &quot;*** NEW *** text. Even better tool for checking cd/ct/catalog files is catcheck, but this one is sadly only available for AmigaOS/68k...

Some languages have variations, like portugues from portugal and portugues from brasil differs...

This is the way to go. I will have a look at language files, but basically if those two languages differ you have to do two separated set of translation files, yes.
(you could create a brazilian slang language localization too)

* At system level localization for one language is a dot language file.
(ex: locale:languages/klingon.language)

* At app level localization is a dot catalog file
(ex: locale:catalogs/klingon/system/libs/dos.catalog)

* At sources level, the dot ct file, and &quot;$language&quot; dot cd files and some building framework.
(ex: catalogs/my_app.ct catalogs/klingon.cd catalogs/mmakefile.src support.c support.h)

Please, use Flexcat to generate CT files: 
 FlexCat wanderer.cd NEWCTFILE=deutsch.ct

Then fill the first 2 lines with something useful:
&lt;pre&gt;
## version $VER: wanderer.catalog 1.1 (9.2.2006)
## language deutsch
&lt;/pre&gt;

You can even update the CT-File: (This adds the new strings)
 FlexCat wanderer.cd deutsch.ct NEWCTFILE=deutsch.ct


To compile a catalog you only need the .cd file and your translation (.ct file):
 FlexCat multiview.cd deutsch.ct CATALOG=MultiView.catalog


[http://murks-ide.svn.sourceforge.net/viewvc/murks-ide/trunk/src/Catalogs/flexcat_linux?revision=100 Linux version of FlexCat]

: [http://aros.sourceforge.net/documentation/developers/app-dev/localization.php#localization-for-non-developers More information]


A script which compares the required version (i.e. the version which an application/module etc. tries to open) with the version of the existing CT files. The result is in this table:

https://github.com/aros-translation-team/translations/wiki/Progress

The following cases are highlighted:

    n/a i.e. CT misses at all
    version in existing CT file is lower than the required version


It might be a bit difficult to participate if you haven't worked with Git before but alternatively you can send your CT files to our Slack channel.

When the ct file has been generated via flexcat (flexcat keyshow.cd NEWCTFILE=spanish.ct) it has the following header:

---------------------------------------------------------------------------------------------------------------
## version $VER: &lt;name&gt;.catalog &lt;ver&gt;.&lt;rev&gt; (04.01.2021)
## language nolanguage
## codeset 0
;
---------------------------------------------------------------------------------------------------------------

Those values &lt;ver&gt;.&lt;rev&gt; are the version and revision of the CT file for the languaje or are the values of the application being localized?

The &lt;ver&gt; part must match with version which the application tries to open. You can find the value either in the column &quot;Required Version&quot; in the table which I've linked above, our you can look in the git repository. For keyshow it would be https://github.com/aros-translation-team/keyshow. You can find in the file &quot;catalog_version.h&quot; the right version number.
The &lt;rev&gt; part starts for new CT files with 0 and should be increased every time the CT file is updated.

Updated several files and created a few more that were missing on the spanish catalog.

The catalogs are in Git repositories at https://github.com/aros-translation-team

a) You tell me your Github user name. I'll invite you. You can work directly with the Git repositories.

b) You create Github forks of the catalog repositories and create pull requests.

c) You send the CT files to mrustler  gmx de


===C Utils Misc===

The AROS source uses at several places the __DATE__ macro to fill the date entry of a $VER tag. Problem is that c:version doesn't understand that date format (e.g. &quot;May 21, 2011&quot;). As a result the output of e.g.
&gt; &quot;version c:shell full&quot; contains &quot;(null)&quot;. Is extending the version command to understand the format of __DATE__  the right solution for that problem?

AmigaOs compilers should use __AMIGADATE__ macro or similar form, if it isn't implemented it could be emulated in makefile: -D__AMIGADATE__=\&quot;$(shell date &quot;+%d.%m.%Y&quot;)\&quot;

BTW. I think DD.MM.YYYY is better format than &quot;Month DD YYY&quot; because &quot;Month DD YYY&quot; is not localized in any way.

&quot;strnicmp&quot; shouldn't work with NULL pointers

The Situation:

compiled a linklib using c++ object files (using the c++ cross compiler).
compiled a C stub that uses the linklib (using the c++ cross compiler).

Try to link them together (using the c++ cross compiler) with C object
files (using the normal target c compiler) that need to use -nostartup
= cant do because using the c++ files pulls in arosc (for stdio etc.) -
so wants to have the autoinit stuff present.

What can I do about this??

If it is possible to manually open it then what do I need to do exactly?

=== ENV ===

The philosophy behind ENV: is that keeping configuration files there allows you to  'Use'  preferences  by  keeping  a copy in ENVARC: intact. However in some cases (like this one) it is not required.

99% of the time that statement is true (not required) for pretty much every file in ENV: or do people change their default icons - and prefs settings - every boot?

There seem to be a bad habit of late with developers changing things to reflect their own personal preference when the change isn't actually necessary - It would be nice if people could refrain from doing that in the tree without at least discussing it on the dev-list first (and with good reasoning unless they committed said work in the first place..)

We're not keen on the pollution of the &quot;S:&quot; dir: it's meant to be for scripts. What's wrong with &quot;ENV:&quot;?
Only the fact that it takes up RAM. I  understand  that  for  PCs  with  several gigabytes of RAM this is
irrelevant. But let's remember about other machines. The philosophy behind ENV: is that keeping configuration files there allows you to  'Use'  preferences  by  keeping  a copy in ENVARC: intact.

However in some cases (like this one) it is not required.

How about implementing in the style of HappyENV then? RAM-disk handler that falls through to reading from ENVARC: if there is no such file stored in it already. Removes RAM usage for unchanged files, removes the need to copy ENVARC to ENV in startup-sequence. 
Shouldn't be too hard to make from AmberRAM, or even just extend AmberRAM to provide this service.

Is it feasable to build a special version of AmberRAM handling ENV: that will try and copy the requested file from ENVARC: if it isnt found in ENV: ? 
Additionaly it could mark closed &quot;files&quot; as untouched - and expunge them from ENV: after a period of time to free up additional RAM:, or when the system is running low on free memory?

Silenty disappearing files may not be a good plan. Would be nice if the following would work:

ASSIGN :ENV SYS:Prefs/Env-Arc ADD
ASSIGN :ENV RAM:ENV  ADD

Where new files put in ENV: end up in RAM:ENV, and opening files looks in RAM:ENV first, then SYS:Prefs/Env-Arc

Well - that's essentially what im proposing but without the assigns - or need for a RAM:ENV directory. 
Adding it as a feature of AmberRAM sounds like the most memory efficient way (one handler to load in RAM) but that's only if it is possible to make it handle ENV: additionally to RAM:, and if it is even possible to add the proposed functionality (...and how to make it enable it when accessing ENV:).

===(AS)MP support===

If one has to recompile software for SMP multi core, is there any thing special one has to do to get software to run?   
Use task.resource if you need to query information about what tasks are running, and clear msgports completely when they are allocated.

Most code should not need Forbid. Use Semaphores, Messages etc. to sync your own code. 

Accessing system structures is a different thing. Use the proper API whenever possible.

How single structures will be protected in the future is still a moving target, at least it is not documented. And you should never  use undocumented stuff  


Ideas on for SMP multi-core

Another suggestion is ... Forbid/Permit function calls are meant to halt multitasking so as no other task could intervene with what ever the calling task is doing, e.g. setting semaphores. Disable/Enable calls are meant to halt interrupts and as a side effect they also halt task switching.

One option is to make it compulsory to protect shared resources with semaphores and forbid the use of simple Forbid() calls as to protect something. Setting semaphore should be done if possible with atomic instructions (check and alter in one instruction). Or make the second concurrent ObtainSemaphore call halt the second calling task and force if possible a task switch which ever gives better results. 

Semaphores could store the owning tasks task pointer instead of boolean to make things easier.

As long as the CPU initiates the DMA transfers through the OS, and the OS ensures that the transferred memory is within the region accessible to the user initiating the transfer, everything is fine. The CPU is the conductor, and the CPU by that has the control of which DMA transfer is initiated and which is not.
All you need to do is to write device drivers reasonable. Hint: CachePreDMA and CachePostDMA exist.
All the Os has to do is to verify that the memory regions to be transferred are valid, and prohibit direct access to the DMA control registers from user space. None of these algorithms imply huge costs.
The current OS design doesn't really allow virtual memory in first place, Forbid() is again the problem.

[http://www.tbs-software.com/guide/index.php?guide=autodocs.doc%2Fmemory.doc&amp;node=1 memory.library API] seem to low level. IMHO the programs should not know how the swapping is implemented. I would just go for one new memory flag
MEMF_SWAPPABLE that indicates that a certain memory region or a whole memory pool won't be accessed during Forbid()/Permit() etc. It only solves part of the problem, it only implements virtual memory and not memory protection. For the latter you need to be able make certain memory inaccessible by other programs, some memory read-only for one task and read-write for other tasks, etc. And I think this should be done in the same Address Space in order to avoid you constantly need to swap between different address spaces. 
So to summarize, if there are programs using this API we may provide a wrapper layer to get them working but I am not convinced this API should be the reference API with whom to provide VM to AROS programs.

=== Variadic ===

variadic functions (i.e. functions with an arbitrary amount of arguments).

&lt;pre&gt;
    #include &lt;stdarg.h&gt;
    [...]

    char * STDARGS GetKeyWord(int value, char *def, ...)
    {
        [...]
        va_list va;
        [...]
        va_start(va, def);
        [...]
        va_end (args);

&lt;/pre&gt;

Please keep with using stdarg rather than having va casted to a LONG * type and varargs handled manually. Doing so, prevents tons of casting, where a simple va_arg can be used. So, string = *((char **) args) instead of string=va_arg(va, char *).

&lt;pre&gt;
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;

int printf (const char * format, ...)

{
    int     retval;
    va_list args;

    va_start (args, format);

    retval = vfprintf (stdout, format, args);

    va_end (args);

    fflush (stdout);

    return retval;
} /* printf */
&lt;/pre&gt;

Couldn't find varargs.h or stdarg.h. and have no use for AROS_SLOWSTACKHOOKS or AROS_SLOWSTACKTAGS.

GCC looks for stdarg.h in a different place: 
 /bin/linux-i386/tools/lib/gcc/i386-aros/4.2.2/include/stdarg.h

Here is a path for a &quot;normal&quot; header:
 bin/linux-i386/tools/lib/gcc/i386-aros/4.2.2/../../../../i386-aros/sys-include/aros/system.h


The use of vararg.h isn't supported by newer gcc versions. If you want your code to run on architectures that pass part of variadic arguments in a number of registers you need to use AROS_SLOWSTACK macros. Otherwise your program will not work on powerpc and x86_64 ports.

Of course the SLOWSTACK stuff is not needed in a function that can use va_list, va_start, va_arg and va_end. It's only needed if you want to write functions like DoMethod or similar.

 #include &lt;stdarg.h&gt;

should be enough no matter if you do cross or native compiling. If it does not work, something is wrong and should be corrected.

Stdarg.h is here, Development:lib/gcc/i386-aros/4.2.2/include/

...which is part of the compiler's default include paths. In other words, #include &lt;stdarg.h&gt; works out of the box, indeed. (sorry, I should have just tried it before invoking &quot;search&quot; or &quot;find&quot;...)

furthermore, myprintf() as shown above won't work, because...

 printf(format, args);

...is wrong - the second argument does not match printf() prototype, it expects a argument list, but args is of type va_list (obviously) - so one has to use...

 vfprintf(stdout, format, args);

...instead, just like in the original printf(), and add fflush(stdout).

additionally, one could use...

 int myarg = va_arg(args, int);

...between va_start() and va_end() to access individual arguments, where each call to va_arg() returns an argument casted to the desired type (here: &quot;int&quot;) from the list given (here: &quot;args&quot;) and advances to the next one.

wrapping up vfprintf() and modifying the format string now is a major speedup! no more backslash-n typing! this has been haunting me for years!

On MOS and AmigaOS, the NewObject variadic function is kept in the static library. It takes most of the parameters on the stack - thanks to that the implementation of NewObject calls the NewObjectA function. Everything works perfect, and the typical MUI macros may be easily used.

This, however, is not the case when you compile for AROS. Here, NewObject is a variadic macro, not a function. Thanks such approach we do not need any custom compiler in case of systems, where the arguments of variadic functions are passed partially through registers and partially through the stack (This is the case of PPC and x86_64, this is also the reason why both OS4 and MOS require specially patched compilers).

Since NewObject is a macro, the gcc's preprocessor expects the list of macros arguments enclosed within parentheses. In MUI macros it is not the case. Imagine the following test code:

&lt;pre&gt;
#define foo(a,b) ((a)+(b))

int loosy_function(int a, int b)
{
    return foo(a,b);
}
&lt;/pre&gt;

This will compile and work, but the following piece of code:

&lt;pre&gt;
#define foo(a,b) ((a)+(b))
#define END )

int loosy_function(int a, int b)
{
    return foo(a,b END;
}
&lt;/pre&gt;

will fail with the error: unterminated argument list invoking macro &quot;foo&quot;

There are two ways of fixing your issue. Either create your new objects outside this huge MUI constructions, and in there use just a pointer, or get rid of the &quot;End&quot; macro and exchange it with &quot;TAG_DONE)&quot;.


Badly written software is, for example, casting va_list to an APTR or even doing so as if va_list were a plain table of function arguments. Such code needs to be fixed because it has very few chances to work anywhere but on author's machine ;)

The problem is nOt that they assume sizeof(APTR) == 4, its that they often do not use APTR, and use ULONG to store pointers exclusively. If the code used APTR/IPTR as it should - most of the &quot;problems&quot; wouldn't exist.

It would also help if people would start using variadic arguments properly. Many coders do assumptions which shall never be made. Instead, they should consider using stdarg.h file and all the va_* functions :)

===ABI===

In the head of our SVN repository there are now only 3 directories:

&lt;pre&gt;
admin/
branches/
trunk/
&lt;/pre&gt;

We have added two extra dirs there: tags and imports

As discussed when we branch ABI V0 and [[Aros/Developer/ABIv1|ABI V1]] it would also be good to introduce tags. Normally this is done in a directory in the repository called tags. Currently we don't have this directory there. (We do have branches/tags that is a hack I have done because one doesn't have write access in the top directory. I think this directory is not clean and should be removed).

The second directory I would introduce is an imports directory for implementing vendor branches as discussed in the svn [http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html book]. Currently we use code from several different projects and that code is stored inside the AROS tree; we seem to have problems with keeping this code up to date and merge our changes upstream. Maintainers of up stream projects like the MUI classes etc. have complained about this (to put it lightly).

Introducing these vendor branches would make it easier to see what changes we have made and make patches to be sent upstream and make it easier to import newer upstream versions of their code. Although can't &quot;copy&quot; the vendor branch into the main branch because it's already there, so start with a &quot;merge&quot;.

Yes, the first step to make the code already in the repository compatible with the vendor branches will be the most difficult. The best way to do it the following way:

* first import the version on which the current AROS code is based into the vendor branch
* then import the new version over it in the vendor branch
* finally merge the difference between these two version in the AROS code present in the repository.

For example, place NList directly under vendor and not in a subdirectory like &quot;contrib/zune/classes&quot;.

Actually after we have a stable [http://aros.sourceforge.net/documentation/developers/specifications/drafts/abiv1.php ABIv1 (2012 or later)]. We need to move away as much as possible from the contrib directory to some other repositories. The reasons are ...

* The AROS repository should be for the core AROS code.
* other contrib projects should be tried to be compiled for all Amiga-like OSes.
* The release scheme for AROS and the other programs should not have to be aligned.
* Binary versions should be provided on aros-archives and on aminet and/or OS4Depot to install them. (Some clever programs should maybe be provided to make the life of distribution developers easier). 
* avoid parallel forks of programs for AROS and the other amiga OSes.

If there is really a need for a place for hosting AROS projects we may investigate setting up such a server but then including bug tracking, governance, maillist, etc. for each project separately. I personally think there are already enough places like sourceforge, google code, savannah, etc. where people can go for hosting such projects.

==Links==

* http://amigadocs.hokstad.com
* http://amigadocs.hokstad.com/doku.php?id=dev-links
* http://www.liquido2.com/tutorial/index.html
* Amiga(TM) OS4 has a [http://www.ast-workshops.co.uk/os4pg/ workshop] page and hope to produce a [http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=31117&amp;forum=42#549091 book] soon. [http://www.solie.ca/articles/map/map.html Brief Guide].

 In the future...?
*AROS 64bit - SMP, Vulkan with OpenGL compability layer
*AROS 32bit - keep for historic reasons 

What would you like to see implemented in AROS?
ABIv1 completed, SMP (x86_64),  SendMsg()/GetMsg() to support memory protection between target and destination, in that order.   Michal Schulz and Jason McMullan have been toying with the question &quot;What are the minimal changes needed to the AmigaOS 3.1 API to support SMP&quot;?  The answer so far seems to be &quot;few, but subtle&quot;.  For example, SysBase-&gt;ThisTask is no longer meaningful on SMP, but FindTask(NULL) is.  Disable() and Forbid() are shockingly bad on performance, but adding a spinlock semaphore mode to SignalSemaphore will help new code on SMP.  

Leveraging a 'common' OS with a lot of machine support (Linux, MacOS, Windows, QNX, etc.) is something that AROS has been doing for quite a long time, and it is the biggest strength of AROS. This AROS experience and programming model, in the same way the Google's Android layers on top of Linux, or MacOS X layers on top of the Darwin/BSD kernel, as a first step 

* The graphics + layers subsystem could be implemented as a shim on top of a OpenGL ES implementation (ie on any modern Linux system, or the RaspberryPI's hardware, MacOS X, etc). 
  - This also allows every window to be on its own 3D surface with backing store, allowing Wanderer (or a Commodity)
rearrange/zoom/animate app windows without having to send a pile or refreshes to them

* Use OpenAL as the sound backend
* AROSTCP would be a thin layer over the native OS's TCP/IP stack
* dos.library, poseidon.library, and input.device would be slim shims over the native APIs
* If we move to loading all libraries' into the application's task space, instead of a single global instance of the library, this will allow SMP and MMU more easily. 
  - Yes, it will require a lot of work in the libraries to make this transition
  - Yes, I do think it will be worth it in the end.

* A 'fat binary' install format (or, maybe LLVM bytecode) that can be 'flattend' to the target architecture on installation.

So, what would this 'AROS of the future' look like?

* AmigaOS 3.x style API, with certain 'fundamental changes' to message passing
* Uses the underlying OS' device drivers, so more AROS developer effort can go to user-visible features and bugfixes 
* Allows AROS applications to run side-by-side with the OS's native apps


And why would anyone want to program on such a system?

* AROS applications would run on any system that has the AROS Framework installed
* AROS applications are pixel-for-pixel the same on all platforms. 
* Develop with the knowledge that you are guaranteed OpenGL and OpenAL, and the rest of the AROS Framework

an option for mmake to dump its dependency of metatarget in a graphviz[*] input file. This should make it possible to visualize the dependencies and hopefully be inspiration for cleaning up some mess, circular or unneeded dependencies and so on.


AmigaOS gcc 9 [https://franke.ms/amiga/gcc.wiki Old versions] able to create binaries for AmigaOS and [https://eab.abime.net/showthread.php?t=93813 Upgrading gcc versions] 


==References==
{{reflist}}
{{status|50%}}

{{BookCat}}</text>
      <sha1>cns6icscq65bgb30auhv36k881skbgq</sha1>
    </revision>
    <revision>
      <id>4668982</id>
      <parentid>4668962</parentid>
      <timestamp>2026-09-05T18:29:52Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668982</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="125171" sha1="t8xy7wn0fkpwqjx4rx8fwu6zq75kcd8" xml:space="preserve">{{ArosNav}}

==A technical overview of AROS==

Google translation [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=de&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs German], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=fr&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs French], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=it&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Italian], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=es&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Spanish], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=hi&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Hindi], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=zh-CN&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Chinese], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ru&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Russian], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pl&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Polish],
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pt&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Portuguese]

{{Uncited}}

AROS,&lt;ref&gt;[http://aros.sourceforge.net/download.php References and sources]&lt;/ref&gt; like AmigaOS (TM), is a [[w:Message passing|message-passing]], [[w:Preemption (computing)|preemptive]] [[w:Multitasking|multitasking]] [[w:Operating system|OS]].

It uses [[w:Reentrant (subroutine)|re-entrant]] shared libraries to save memory space.

AROS is based around an executive library kernel (Exec) and two other libraries:

* Exec (the &quot;kernel&quot;, which is not a kernel in the modern sense), 
* Intuition (graphics and GUI, integrated into the system) and 
* AmigaDOS (Disk Operating System, the Metacomco's Tripos modified to work with Exec).

The design philosophies of AmigaDOS and Intuition are rather different, the former adopting a C-like API and the latter creating an [http://www.basden.demon.co.uk/amiga/amiga.oo.html object-oriented], message passing aware environment for the programmer. The system base is the only absolute address in AmigaOS (located at 0x00000004) this does differ with AROS as AROS SysBase is automatically provided (no $4) but everything else is dynamically loaded. The OS is well known for delivering high performance due to its close connections with the hardware, while simultaneously having the flexibility to support re-targetable graphics (Cybergraphics) and retargetable audio subsystems (AHI).

: Diagram showing relationships of libraries to system needed


Remember, AROS is a [http://en.wikibooks.org/wiki/Aros/Developer/ABIv1 research] operating system, and while all contributions to the base AROS code are welcome, please contact the dev list first for any core changes. Writing applications for AROS does not have this requirement. 

While AROS appears and feels almost feature complete, it is still [[Aros/Developer/IncompleteAPIs|missing a small number of functions]] from the Amiga API. 


[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1201 This thread provides] information for setup, [http://www.aros.org/documentation/developers/index.php documentation] and whether you are interested in core OS changes and/or writing/porting software apps 

*you compile directly under AROS, which can be running on either real hardware, virtual hardware
*in hosted mode under linux/window, cross-compile from that host OS (save your files as ISO-8859-15 encoding instead of UTF-8) [https://github.com/BlitterStudio/aros-compiler-docker Docker images] 


'''The repository''' for 64bit and 32bit ABIv1 all hardware platforms is [https://github.com/aros-development-team/AROS current development version]. 
There are many forks of this so that developers can work on their own and forward changes at a later date as discussed on the dev forum 


64bit PC is one of two hardware platform with another fork called [https://github.com/deadwood2/AROS abiv11] which is used for Aros One x64 PC 

32bit PC is the other fork [https://github.com/deadw00d/AROS/tree/alt-abiv0 repository for current stable PC version ABIv0 with backported ABIv1 features is located which is used on AROS One and Icaros x86 32bit based distros] this is for historic reasons 


Any [https://github.com/aros-development-team/AROS/issues bugs / issues can be added for ABIv1 issues]. The two individual PC forks have their own issues tab on their github webpages 

We have a [https://arosdevteam.slack.com/archives/CUFV48U3H slack here], discord on [https://discord.gg/UKp9qdEBuQ Discord@AmigaDev], 


==Software Development for AROS==

===Programming languages===

====Common to all====

'The Developer Environment', which primarily supports C/C++ code, there are other programming languages available for AROS:

'''Scripting''' 
:[[Aros/User/DOS|DOS]] 
:[[Aros/Developer/Docs/LUA|LUA]] 
:REXX [[Aros/Developer/Docs/Rexx|Regina (AROS' ARexx)]] 


====Needs to be compiled/ported====

::[[Aros/Developer/Docs/LLVM|LLVM]] 
::Python [ Info], [], 
::[https://ae.arosworld.org/index.php?board=11.0 FreePascal FPC Aros-Exec thread], [https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language fpc arm here is very old and will not work], FreePascal for AROS has its own [http://fpcaroswiki.alb42.de/ Wikibook], 


::[http://sourceforge.net/projects/xamos/ X-Amos Basic] 
::[http://sdlbasic.sourceforge.net/ SDLBasic] ([https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language ])
::[[Aros/Developer/Basic/Basic4SDL|Basic4SDL]] ([https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language ])
::[http://alvyn.sourceforge.net/ Alvyn] ([http://www.dusabledanslherbe.eu/AROSPage/MISC.14.html download]) 


::[http://www.airsoftsoftwair.com/ Hollywood when enough users warrant a port - paid one time fee language] 


::[[Aros/Developer/Docs/E|AmigaE Portable E]]


====Hardware Restricted====

'''Basic'''

:[http://amos.pspuae.com/AmosProManual/contents/c1.html '''Amos Pro'''] [http://amos.pspuae.com/index.php?action=forum#1 compatible] [http://www.amigacoding.com/index.php/Main_Page commands] (all incomplete) 

:'''Blitz Basic''' [http://aros-exec.org/modules/newbb/viewtopic.php?post_id=46537#forumpost46537 none on AROS] 
:: [http://www.amiforce.de/main.php Amiblitz] on amiga(TM) emulator

:'''Amiga Basic'''
:: [ ACEBasic]

'''Misc''' 
:Ruby [http://www.ruby-lang.org/en Info]/[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language Ruby 32bit PC], 


===Where to get the C/C++ Environment===

If you want to develop for AROS, its generally easier to be running linux hosted AROS development environment especially for C++, cross compiling the code. That's how most developers now are doing it. g++ is used to compile owb web browser as well as some other AROS software. If you were hoping for a rich set of C++ libraries or classes defined for the OS feature set, you might be disappointed.

AROS Native compiling is possible, but you're much more likely to run into the odd bug(s) in the dev environment since it gets little testing and fixing by other developers.

Is there a sftp software or scp over ssh available?
Maybe. At least the security part would be handled by [https://github.com/jens-maus/amissl amissl] [https://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc port]. [https://github.com/BlitterStudio/dopus5 DOpus5] has recently added sftp support. See here for a [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1974&amp;highlight=ssh&amp;pid=12073#post_12073 ssh scp client]

[https://arosdevteam.slack.com/join/shared_invite/enQtOTc4Mzg0NDIzNzQ0LWQ2NWZmNmMwNGIwNGEyNTgxNzU3MGFjMTk3ZThmOTQ1MTVjMzhmNTllYWQ0ZTUxMjBjMGE0Y2VjMDJmNTc5MzI#/shared-invite/email Slack Dev Forum] 


====Cross compilers from Windows or Linux====

*Windows WSL2 walkthrough can be [https://arosnews.github.io/how-to-cross-compile-aros-hosted-wsl/ found here] 


you want to build AROS. No problem.

Here are instructions for PC 64-bit:
https://github.com/deadw00d/AROS/blob/master/INSTALL.md

Here are instructions for PC 32-bit:
https://github.com/deadw00d/AROS/blob/alt-abiv0/INSTALL.md

And as always has been the case you can use the contrib archive to 'obtain' the development directory which contains the /native/ AROS gcc compiler and tools. That compiler is used to build AROS itself but can be used outside the AROS build process by providing --sysroot with indicated directory to cross compile for AROS.


=====Older guides for Linux hosted compiler=====

Please install these packages before moving to next step. Below is a reference list for Debian-based distributions. Reference build system was Ubuntu 18.04/20.04 amd64.

subversion git-core gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libx11-dev libxext-dev libc6-dev liblzo2-dev libxxf86vm-dev libpng-dev gcc-multilib libsdl1.2-dev byacc python-mako libxcursor-dev cmake zsh mingw64

Do all of these operations under home directory of your user or another directory where your user has write permissions.

Specifically, in a section &quot;Linux-i386&quot;, be sure first to build the cross-compiler (toolchain-alt-abiv0-i386) and only then AROS itself (alt-abiv0-linux-i386).


Clone &amp; build
&lt;pre&gt;
$ mkdir myrepo
$ cd myrepo
$ git clone https://github.com/deadw00d/AROS.git AROS
$ cd AROS
$ git checkout alt-abiv0
$ cd ..
$ cp ./AROS/scripts/rebuild.sh .
$ ./rebuild.sh
&lt;/pre&gt;

Now to the build selection below - Linux-i386 

Select toolchain-alt-abiv0-i386 - Select alt-abiv0-linux-i386 (DEBUG) 

Start AROS by:
&lt;pre&gt;
$ cd alt-abiv0-linux-i386/bin/linux-i386/AROS
$ ./Arch/linux/AROSBootstrap
&lt;/pre&gt;


Pc-i386 Select toolchain-alt-abiv0-i386 (if not built yet) - Select alt-abiv0-pc-i386

ISO image available in alt-abiv0-pc-i386/distfiles


Now that we have linux-hosted build, we can resume native (option 2).
Run ./rebuild.sh and selection option 2. Wait until it finished, then:
&lt;pre&gt;
$ cd alt-abiv0-pc-i386
$ make
&lt;/pre&gt;

Now
&lt;pre&gt;
$ make bootiso
&lt;/pre&gt;


Now, your compiler is located in toolchain-alt-abiv0-i386 directory and named i386-aros-gcc. Includes are in alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development/include and libraries are in alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development.lib.

This is how then can be passed to the compiler:

/home/xxx/toolchain-alt-abiv0-i386/i386-aros-gcc --sysroot /home/xxx/alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development -L/home/xxx/alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development/lib 

../toolchain-alt-abiv0-i386/i386-aros-gcc --sysroot bin/linux-i386/AROS/Development local/helloworld/helloworld.c -o local/helloworld/helloworld


Another method was using Debian like distros and download the gimmearos.sh script (on [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/cross aros-archives]) to setup the developer environment by downloading necessary packages ...
The gimmearos script is a good start in that direction, building the cross compilers and hosted AROS environment, but gimmearos.sh might be out of date or not be completely compatible with any given linux distro. 

In order to do that, you have to compile AROS yourself. Download AROS source archive not contrib. Compile AROS by entering the main directory

 ./configure
 make

([http://aros.sourceforge.net/documentation/developers/compiling.php More on compiling AROS]). The result will be a basic AROS system without development tools.

To compile C++ on Linux, type 'make gnu-contrib-crosstools', creating the cross-compilers in ./bin/linux-i386/tools/, named i386-aros-gcc, etc.

'''Note''': Currently, to make the cross compilers usable copy 'collect-aros' from tools/ to tools/i386-aros/bin/. At the moment the cross compilers if used from the Linux command line will only find it when it's there.

If you want to compile native compilers (the Developer Environment), type 'make contrib-gnu-gcc', creating native compilers in AROS' System:Development/bin directory.

When the output needs to be stripped &lt;code&gt;--strip-unneeded --remove-section .comment&lt;/code&gt;

The Obj-C backend should build out of the box.

Open contrib/gnu/gcc/mmakefile.src and search for the line which contains &quot;--enable-languages&quot; and add &quot;objc&quot; to the list of languages that follows it.

    --enable-languages=c,c++,objc

Better make it—enable-languages=c,c++,objc,obj-c++

ObjC++ is broken as soon as you try to use exceptions, but that might change in future GCC versions and it does not hurt having it there already.


Do you need a cross-compiler or a real compiler? In the first case you can get away with just downloading the proper gcc archive, apply the patch and proceed with the normal gcc build. In the case of a real cross-compiler then when downloading the contrib sources, also need to download the normal sources, place the contrib sources into a directory called contrib, need to install autoconf+automake+perl+python, call ./configure, cd into the subdirectory and type make.

to rebuild GCC with host == build == target == i386-pc-aros. So just get the vanilla sources and apply the patches without bothering about the build system?


[https://vmwaros.blogspot.com/2019/10/a-pre-configured-development-machine.html pre-configured VM environment vmware virtual machine to develop AROS and AROS software]


'''64 bit'''


'''32 bit'''

A good option for multiple OS is [https://axrt.org/index.php?tab=download-aros AxRuntime lets developers compile their Amiga API-based applications as Linux binaries being able to utilize modern development tools available on Linux, like IDEs, debuggers, profilers, etc] 


====Native compilers for AROS====

Namely gcc for C or g++ for C++ are supplied with the [[Aros/Developer/Docs#The Developer Environment|Developer Environment]], which is already '''setup''' and part of any current AROS distribution like AROS One or the nightlies 

* Current GCC 6.5 (32bit) though moving to 10.5 and 15.1 (64bit) 
* Older software components. GNU GCC 4.x GNU BinUtils, GNU Fileutils 4.x, GNU Textutils and others usually deprecated 

On single partition systems and the Boot ISO, the AROS Developer environment is installed under &quot;SYS:Development/&quot;. Systems with multiple partitions - such as a Work: partition - tend to install it to there instead, however it can be installed manually to any location. Please remember, if moving, that you will need to correct the Development packages 'install location' env variable to point to the new locations root - look in SYS:S/startup-sequence.

&lt;pre&gt;
Assign Development: SYS:Development 
Assign C: Development:bin ADD 
&lt;/pre&gt;


In the aros build instructions. you need to check out contrib and/or ports into your AROS source directory, as subdirs. then, assuming you are building in an external build dir, as you should, you simply configure and &quot;make contrib&quot; for instance or whatever submodule you might want to build.


===Beginners Tutorials in C C++===

As AROS is [http://eab.abime.net/showthread.php?t=29856 C based] API compatible to AmigaOS 3.x, so most of the information on programming C on the Amiga applies to AROS as well. Please note that there is a lot of AmigaOS 1.3 (1985-1989) and [https://www.markround.com/amigaguide AmigaOS AOS 2.x (1990-1992)] information around but OS3.1 is recommended but limited in amount. 

Brief overview of what is required to write AROS Applications

# Using [[Aros/Developer/Docs/Libraries/Intuition|Intuition]] for basic screens/windows 
# Using graphics within windows via 8bit [[Aros/Developer/Docs/Libraries/Graphics|graphics]] and so onto  15-16-24bit [[Aros/Developer/Docs/Libraries/CGFX|cybergraphx]]
# Load and save work to [[Aros/Developer/Docs/Libraries/DOS|dos]] disk drives
# Using the [[Aros/Developer/Zune|ZUNE GUI Environment]]


Writing native games require this extra information

# Using [[Aros/Developer/AHIDrivers|AHI audio hardware independent API]]
# Using USB joystick/joypad with the Poseidon USB stack through [[Aros/Developer/Docs/Libraries/LowLevel|LowLevel]] library


Additional features that could be added later

# Adding additional [[Aros/Developer/Docs/Libraries/Locale|Locale]] language translations to your program 
# Adding a [[Aros/Developer/Docs/Rexx|AREXX/Regina]] port to your application 
# Executing Amiga(TM) [[Aros/User/DOS|DOS]] commands from your application
# Using [[Aros/Developer/Docs/Libraries/Icon|icons]] (.info files) and icon tooltypes (stack, version, and program startup options)
# Local couch or IP based SANA2 networking co-op multi player gaming support 


Most AmigaOS programming books are nowadays very much out of date as most are from the late 1980s and do not cover later amigaOS releases like 3.1 for example, Rob Peck's book &quot;Programmer's Guide to the Amiga&quot;. The Amiga ROM Kernel manuals aka RKMs like Libraries (3rd edition), Devices (), the AmigaDOS manual (3rd edition) and the Style Guide may have their uses. There are some reference examples from AmigaMail and Devcon notes (available again on an Amiga developers CD 2.1). 

For Arexx then &quot;The Amiga Programmer's Guide to ARexx&quot; by Eric Giguere, which was published by Commodore is useful as well as an &quot;Arexx Cookbook&quot;.

Curly brackets missing - try SHIFT + ALT + 7 or 0.


* Beginners C Guide [http://www.iu.hio.no/~mark/CTutorial/CTutorial.html C Tutorial], 
* [http://thecguru.com/ C for beginners],
* [http://fresh2refresh.com/c/c-basic-program/ C programming basics] for students, 
* [https://www.edx.org/courses Free Online course] from American Universities 
* Reference Amiga [http://amigadev.elowar.com/ API reference].


* AROS based c source can be found [[Aros/Developer/Docs/Examples|here]] and lots of example code can be found inside [https://github.com/aros-development-team AROS sources] themselves and from the contrib section of the archives from [https://github.com/aros-development-team/contrib Aros site], and study the AROS applications source code, e.g. the test programs from the Tests drawer (folder/directory). Take a look at the code of some smaller AROS programs might be a better and more up to date 

When you upload your builds, please write the architecture (like i386-aros, x86_64-aros, armPi-64 etc.) in the archive name 
and it is also advisable to write in the field &quot;Requirements&quot; what ABI (ABIv1 or for PC forks ABIv11 or ABIv0) 


===Compiling C/C++ Code===

Native, although we have a IDE Integrated Development Environment (Murks), it does lack a debugger. Whilst others use a combination of a text editor and shell to edit code. Most though use an AROS hosted on Linux to take advantage of the better GCC tools like GDB and various IDEs.

Open shell - its a menu option at the top left of Wanderer (desktop). Or by using the right Win key and w (or F12 and w) within the directory with the source code. Type in
 sh 
to change the amiga shell into a unix shell. You can then type in ls (unix equivalent to amiga dir). Take a look [http://en.wikibooks.org/wiki/Linux_commands here] for more commands.

For a single file program-name.c or program-name.cpp
 gcc -o program-name program-name.c  
or 
 g++ -o program-name program-name.cpp
or
 g++ -o test -Wall -g main.cc texturelib.cpp xmodelib.cc -lsdl -lgl

To close the shell, click on the top left-hand corner to close (twice). Once to get back the aros shell and then again to close finally. Use [http://freshmeat.net/projects/cksfv/ cksfv] as a test.

Some source code requires the addition of Amiga API libraries, like dos, which you can flag at the compile time as 
 gcc -o julia.exe julia.c -ldos

For DOS use -ldos as example and if you are compiling mui codes it will be -lmui or intuition -lintuition. Other missing symbols are due to linker libraries being necessary for linking in functions that aren't in the standard C libraries. For example some source code would need added

 -lz or -lm or -lpng or -larosc etc.

use this in unix line command mode to search for 'search-item' in many .c files (*.cpp for c++, etc.)
 grep -l 'search-item' *.c

If the program is not executable, try using parameter fno-common 

&quot;Delete #?.o&quot;? Or if you are using abcshell then &quot;rm *.o&quot;


:''More information: [[Aros/Developer/Porting software]]''


=== How to make Apps have AROS 64-bit specific support code ===

[http://www.aros.org/cs/documentation/developers/app-dev/portable.php Portable code] 

AROS64 already uses 64bit addressing, it just doesn't setup the MMU for more than 4GB physical memory currently.
When porting software to AROS64 it is &quot;mostly&quot; a case of converting ULONG's that are used to store pointers, into IPTR's instead, etc. Another quirk, is making sure items on the stack are the correct size by using the STACKED attribute for them. 

* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.

compiling mui stuff for aros setting -std=gnu99 is necessary, had -std=c99 usually 
A MUI application most likely needs only the HOOKPROTOxxx SDI macros. They are compatible with AROS, only the attributes (hook, object attribute) must be given in the right order.

crash which suggest memory corruption. From my experience porting from 32-bit to 64-bit these kinds of errors can happen if a pointer is passed somewhere via ULONG variable. Then half of the pointer is cut.

To generate this error, please run AROSBootstrap with -m 1024. This will allocate heap to 64-bit address space which will make these errors immediatelly visible. These types of crashes are hard to debug. Disabled as little code as possible to stop corruption from occurring and then try to read from the code where it can be broken

Crashing in tslf_freevec is another symptom of memory corruption and these memory corruptions will manifest differently on different setups.


==Coding conventions==

As the AROS core source is a shared developer experience, there are rules regarding structure and style. When it comes to your creating your own app and coding, the structure and style should be your own, i.e. you should enjoy what you do and do it so that you can understand what is going on.

===Layout===

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
static void 1st_function()
{
    program
    exit(0);    
}

int main(void)
{
    1st_function();
    2nd_function();
    3rd_function();
    return 0;
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;

struct Screen * openscreen(void);
struct Window *openwindow(struct Screen *screen, const char *title, LONG x, LONG y, LONG w, LONG h);

VOID 1st_function();
VOID 2nd_function();

int main(int argc, char **argv)
{
    program
    return 0;
} /* main */

VOID 1st_function()
{

}

VOID 2nd_function()
{

}
&lt;/syntaxhighlight&gt;

===General style===

This code is used by many people and therefore you should keep some things in mind when you submit source code:

* Keep things simple 
* Keep the source clean 
* Always know what you are doing, if not flag it and describe what needs to be done... 
* Explain clearly/simply what you are doing 
* Remember that you write code once but that it is read many times by many people

===Comments===

AROS uses some of the comments in the source to generate the documentation. Therefore it's necessary to keep a certain format so the tools can find their information. Other comments are ignored but they should explain what you thought when you wrote the code. If you really can't think of an explanation, then don't write the code a second time like this:

&lt;pre&gt;
/* This adds 1 to t */
t ++;
&lt;/pre&gt;

What we think of is this:

&lt;pre&gt;
/* Go on with next element */
t ++;
&lt;/pre&gt;

===Formatting===

This is only '''IMPORTANT''' if you are going to work on the core AROS code or contrib but not applications which may reside outside like on AROS Archives or other websites.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
{
    /* a */
    struct RastPort * rp;
    int               a;

    /* b */
    rp = NULL;
    a  = 1;

    /* c */
    if (a == 1)
        printf (&quot;Init worked\n&quot;);

    /* d */
    if
    (
        !(rp = Get_a_pointer_to_the_RastPort
            (
                some
                , long
                , arguments
            )
        )
    ||
        a &lt;= 0
    )
    {
        printf (&quot;Something failed\n&quot;);
        return FAIL;
    }

    /* e */
    a = printf (&quot;My RastPort is %p, a=%d\n&quot;
        , rp
        , a
    );

    return OK;
}
&lt;/syntaxhighlight&gt;

Looks ugly, eh ? :-) Ok, here are the rules:

&lt;pre&gt;
If several lines contain similar code, put similar things below each other (see a and b);
Put spaces between operands and operators
Put braces {}, brackets [] and parentheses () below each other (d) if there is much code between. 
Brackets and parentheses may be in one line if the code between is small (c)
Indent by 4 Spaces. Two indent levels may be abbreviated by one tab.
&lt;/pre&gt;

'''Before committing please normalize the indentation - if you have a mixture of tabs and spaced - please always use spaces, 1 tab = 4 spaces.'''

The reasons for this are:

# While some editors can use an arbitrary sizes for tabs, it's a bit complicated to tell another editor which tab size was used by the one used to write the code. 
# Most code in AROS was written this way and your code should look like the rest. 
# You can print this code on any printer without special tools to &quot;fix&quot; the tabs. 
# Most editors have smart tabs which do exactly this. If your editor doesn't, write a bug report.

If you have a function with many arguments (d, e) you should put the parentheses in lines of their own and each argument in one line (d) or put the first argument behind the opening parentheses (e) and each following argument in a line of its own with the comma in front. The closing parentheses is in a line of its own and aligned with the beginning of the expression (i.e. the a and not the opening parentheses or the printf()).

Use a single blank line to separate logical blocks. Large comments should have a blank line before and after them, small comments should be put before the code they explain with only one blank line before them.

If you see any TABS in AROS core sources then the suggestion is to &quot;detab the file and commit that separately&quot; either before or afterwards from making functionality changes. Make two commits instead of one. This makes it easier for others to see the real changes instead of having to dig through multiple lines of irrelevant diffs.

===Eliminating Global Variables===

i.e. pass variables to functions (local scope) or classes making it easier to track and debug your code.

Any time you find that you need a particular thing in 'a lot of different places', chances are that all those places are conceptually related, and so you can create a class, a namespace, a function, or some other higher-level organizational unit to represent that relationship. This makes the program easier to understand.

Bad Designs

* All variables are global. 
* There are no standalone functions, only sub-procedures which act on the global variables. 
* Every sub-procedure is at least 500 lines to several thousand 
* Every sub-procedure has more than one task to perform 
* Copy-paste is preferred to writing methods, AND subtle changes are made in the middle of the code

Good Designs

* structure program into functions (C or basic) - top-down procedural approach 
* put in class(es) (freepascal or C++) - the object is fixed and you use methods to access the object

&lt;pre&gt;
 class String_List
 {
 private:
 list&lt;string&gt; m_List;  // member
 public:
 void read_strings() { /* read strings into m_List */ }
 void print_strings() { /* write contents of m_List to stdout */ }
 void sort_strings() { /* sort contents of m_List */ }
 void sort_strings_reverse() { /* reverse-sort contents of m_List */ }
 void unique_strings() { /* remove duplicate strings */ }
 };

 int main()
 {
 String_List myList;  // local
 myList.read_strings();
 myList.sort_strings();
 myList.print_strings();
 myList.sort_strings_reverse();
 myList.print_strings();
 myList.unique_strings();
 myList.print_strings();
 return 0;
 }
&lt;/pre&gt;

This way it is very easy to replace the list with new list for debugging purposes, or replacing the methods without replacing the list, when you want different results. You only have to replace the content of the local variables.

 So create the structure that matches your data (linked lists, trees, arrays, etc.) and what to do with them (sorting, searching, etc.)

&lt;pre&gt;
.h usually contain #define #include typedef enum struct extern screen and window definitions (data structures)
.c should contains functions and algorithms
&lt;/pre&gt;

One way to look at it is that menu headings act as the .c file and sub-menu headings as functions.

When you start a project, you place a couple of declarations in the include file. As the project continues, you place more and more declarations in the include file, some of which refer to or contain previous declarations. Before you know it, you have a real mess on your hands. The majority of your source files have knowledge of the data structures and directly reference elements from the structures.
Making changes in an environment where many data structures directly refer to other data structures becomes, at best, a headache. Consider what happens when you change a data structure.

Use good variables names to help clarify code and only comment when you need to explain why a certain programming approach was made.

You're Refactoring Legacy Code, you see a global, you want to get rid of it. How do you do this?

Exactly what to do depends on how the global is used. The first step is to find all uses of the global throughout the code, and get a feel for what the significance of the variable is and how it relates to the rest of the program. Pay particular attention to the &quot;lifetime&quot; of the variable (when it gets initialized, when it is first used, when it is last used, how it gets cleaned up). Then, you will probably make the global a data member of a class (for OO languages), or you will write some get/set functions. Converting to the Singleton Pattern is common, but you may discover that it makes more sense for the data element to be a member of an existing singleton, or maybe even an instance variable.

# Create a basic read method, either as a class or a global function. Replace all reads with the access method, but leave the variable defined as a global.
# Review each of the writes to the method and extract action functions one at a time. Unless two operations are coded identically in the original code, extract each write access separately.
# Change the variable scope from global to local.
# Analyze similar action functions to determine if any can be merged, i.e., there are no functional differences in the results of the function, just differences in the implementation details.
# Review the calls to the read method and see if a more complex functionality should be applied. Follow the approach for writes and unless implementations are identical, create separate access functions. 
# Analyze the access functions for duplication.

As returning variables by &quot;passing by value&quot; are forgotten, so &quot;passing by reference&quot; is often used instead. The reference is a pointer to the variable so the value is remembered when returned.

Alternatives

* Hidden Globals
* Singleton Pattern
* Database or TupleSpace
* Context Object 
* Dependency Injection 
* Stateful Procedures


==AROS/AmigaOS APIs and Docs==

&lt;pre&gt;
Library:
   - Private data structure
   - Many public access methods

Device:
   - Private data structure
   - Two (BeginIO/AbortIO) access methods

Resource:
   - Public data structure
   - *NO* access methods
&lt;/pre&gt;

And, being Amiga OS-compatible, there are exceptions to all of these.


===System Libraries===

The [http://developers.aros.org/ AROS Guide To Libraries] can be used as a guide to individual commands and old Dev Docs are used in application programming.

Amiga/Aros styles libraries are very different from windows and linux libs. Typical .so/dll libraries are foreign to most Amiga-like OS 


*[[Aros/Developer/Docs/Libraries/AROSC|arosc.library]]
*[[Aros/Developer/Docs/Libraries/AmigaGuide|amigaguide.library]]
*[[Aros/Developer/Docs/Libraries/ASL|asl.library]]
*[[Aros/Developer/Docs/Libraries/Bullet|bullet.library]]
*[[Aros/Developer/Docs/Libraries/BSDsocket|bsdsocket.library]]
*[[Aros/Developer/Docs/Libraries/CAMD|camd.library]]
*[[Aros/Developer/Docs/Libraries/Codesets|codesets.library]]
*[[Aros/Developer/Docs/Libraries/CGFX|cybergraphics.library]]
*[[Aros/Developer/Docs/Libraries/CGXVIDEO|cgxvideo.library]]
*[[Aros/Developer/Docs/Libraries/Commodities|commodities.library]]
*[[Aros/Developer/Docs/Libraries/DataTypes|datatypes.library]]
*[[Aros/Developer/Docs/Libraries/DiskFont|diskfont.library]]
*[[Aros/Developer/Docs/Libraries/DOS|dos.library]]
*[[Aros/Developer/Docs/Libraries/Exec|exec.library]]
*[[Aros/Developer/Docs/Libraries/Expansion|expansion.library]]
*[[Aros/Developer/Docs/Libraries/FreeType2|freetype.library]]
*[[Aros/Developer/Docs/Libraries/GadTools|gadtools.library]]
*[[Aros/Developer/Docs/Libraries/Graphics|graphics.library]]
*[[Aros/Developer/Docs/Libraries/Icon|icon.library]]
*[[Aros/Developer/Docs/Libraries/Identify|identify.library]]
*[[Aros/Developer/Docs/Libraries/IFFParse|iffparse.library]]
*[[Aros/Developer/Docs/Libraries/Intuition|intuition.library]]
*[[Aros/Developer/Docs/Libraries/Keymap|keymap.library]]
*[[Aros/Developer/Docs/Libraries/Layers|layers.library]]
*[[Aros/Developer/Docs/Libraries/Locale|locale.library]]
*[[Aros/Developer/Docs/Libraries/LowLevel|lowlevel.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEESingBas|mathieeesingbas.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEEDoubBas|mathieeedoubbas.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEESingTrans|mathieeesingtrans.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEEDoubTrans|mathieeedoubtrans.library]]
*[[Aros/Developer/Docs/Libraries/Mathtrans|mathtrans.library]]
*[[Aros/Developer/Docs/Libraries/MUIMaster|muimaster.library]]
*[[Aros/Developer/Docs/Libraries/Partition|partition.library]]
*[[Aros/Developer/Docs/Libraries/PopUpMenu|popupmenu.library]]
*[[Aros/Developer/Docs/Libraries/OOP|oop.library]]
*[[Aros/Developer/Docs/Libraries/Regina|regina.library]]
*[[Aros/Developer/Docs/Libraries/Reqtools|reqtools.library]]
*[[Aros/Developer/Docs/Libraries/RexxSysLib|rexxsyslib.library]]
*[[Aros/Developer/Docs/Libraries/ScreenNotify|screennotify.library]]
*[[Aros/Developer/Docs/Libraries/TTEngine|ttengine.library]]
*[[Aros/Developer/Docs/Libraries/Thread|thread.library]]
*[[Aros/Developer/Docs/Libraries/Utility|utility.library]]
*[[Aros/Developer/Docs/Libraries/Xadmaster|xadmaster.library]]
*[[Aros/Developer/Docs/Libraries/Workbench|workbench.library]]
*[https://github.com/aros-development-team/AROS/commit/c82e86b8480277998014cc327b56c7664023a52f ClassAct Reaction boopsi class]


===AROS Subsystems===

# [[Aros/Developer/Zune|Zune MUI compatible GUI]]
# [[Aros/Developer/AROSAppPackages|AROS Application Packages]]
# AHI Audio Drivers - [[Aros/Developer/AHIDrivers|Usage]]/[[Aros/Developer/AHIDriversDev|Development]]
# AROSTCP Sana2 Network Interface Drivers - [[Aros/Developer/NICDrivers|Usage]]/[[Aros/Developer/NICDriversDev|Development]]
# [[Aros/Developer/AmiSSL|AmiSSL]]
# gfx.hidd/cybergraphics Video Drivers - [[Aros/Developer/GfxDrivers|Usage]]/[[Aros/Developer/GfxDriversDev|Development]]
# IO Device Drivers - [[Aros/Developer/IODeviceDrivers|Usage]]/[[Aros/Developer/IODeviceDriversDev|Development]]
# USB Device Drivers - [[Aros/Developer/USBDrivers|Usage]]/[[Aros/Developer/USBDriversDev|Development]]
# PCI Device Drivers - [[Aros/Developer/PCIDrivers|Usage]]/[[Aros/Developer/PCIDriversDev|Development]]
# [http://www.libsdl.org/ SDL] [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2013&amp;pid=13333#post_13333 SDL2 coding usage], [https://github.com/search?q=repo%3Aaros-development-team%2Fcontrib%20SDL2&amp;type=code SDL2 commits], [https://github.com/aros-development-team/contrib/commit/c62c3c425c35bac19dadc23be092b0b13a66c76c SDL3 initial commit], []
# [[w:Gallium3D|Gallium 3D]] [http://www.mesa3d.org/ openGL aka Mesa] - [[Aros/Developer/OpenGL|Usage]]/[[Aros/Developer/OpenGLDev|Development]] [http://www.swiftless.com/opengltuts.html Swfitless]
# A small subset of GTK2 through [http://sourceforge.net/projects/gtk-mui/ MUI-GTK] 
# Cairo 2D Engine - [[Aros/Developer/Cairo|Usage]]/[[Aros/Developer/Cairo|Development]]
# [[Aros/Developer/Scalos|Scalos desktop API and plugin modules]]
# [[Aros/Developer/VHI|VHI video driver]]


====HIDDs====

*[[Aros/Developer/Docs/HIDD/HIDDClass|hiddclass.hidd]]
*[[Aros/Developer/Docs/HIDD/Graphics|graphics.hidd]]
*[[Aros/Developer/Docs/HIDD/VesaGfx|vesagfx.hidd]]
*[[Aros/Developer/Docs/HIDD/ATI|radeon.hidd]]
*[[Aros/Developer/Docs/HIDD/NVidia|nvidia.hidd]]
*[[Aros/Developer/Docs/HIDD/Nouveau|nouveau.hidd]]
*[[Aros/Developer/Docs/HIDD/Kbd|kbd.hidd]]
*[[Aros/Developer/Docs/HIDD/Mouse|mouse.hidd]]
*[[Aros/Developer/Docs/HIDD/i2c|i2c.hidd]]
*[[Aros/Developer/Docs/HIDD/IRQ|irq.hidd (deprecated)]]
*[[Aros/Developer/Docs/HIDD/PCI|pci.hidd]]
*[[Aros/Developer/Docs/HIDD/PCIPC|pcipc.hidd]]
*[[Aros/Developer/Docs/HIDD/Serial|serial.hidd]]
*[[Aros/Developer/Docs/HIDD/Thunderbolt|thunderbolt.hidd]]
https://github.com/aros-development-team/AROS/commit/4f02ea691799aff3a01f60cfa5f9182c82fc57a8

HIDD are used for device/peripheral low level hardware support drivers. The HIDD system is split up into a collection of classes with a strict inheritance hierarchy. A HIDD class implements a device driver for a single device or in rare cases a group of devices and provides an interface for other programs and devices to access.
      
In order to maintain portability of interfaces across a wide range of hardware this interface will in general not present the raw interface to the underlying hardware. Instead it will present a generic interface that describes many different hardware implementations. This allows for the best reuse of both interfaces and code.

HIDD API is heavyweight though. You need to open a HIDD library, open oop.library, instantiate an object (even if there's no object); and object calls are more costly compared to plain library calls.


Basically your task is to implement a subclass of hidd.ata.bus for your hardware. just implementing the XXXATA__Hidd_ATABus__xxxxxx methods for the Amiga chipset - and appropriate versions of the interface_xxx.c file(s). pretty much everything in probe.c could be ignored - just write a replacement scan for relevant amiga devices and store whatever info you need in the bus data? only the &quot;SUPPORT_LEGACY&quot; blocks might be related.

You do not need to depend on PCI API. PCI is just a way to discover the hardware on PCs, etc. 
&lt;hidd/pci.h&gt; includes (at some depth) &lt;interface/HW.h&gt;, which defines IID_HW. This comes from the 'generic' HIDD class in: 
 rom/hidds/hidd/hiddclass.conf
did not split up HIDD and HW because they are always used in pair. It's the same as hidd/pci.h bringing definition for: PCI, PCIDriver and PCIDevice. PCI is actually PCIHW, just the name was not changed for backwards compatibility reasons. HW is a 'hub' where HIDD instances plug in.

ATA HIDD aoHidd_ATABus_Use32Bit value is completely ignored unless ata.device first detects correct command line parameter.
Yes. Unfortunately I was unable to find any comment in code or svn history with explanations. Looked  at Linux source, there 32-bit PIO is also controller driver's property. Some of them enable it, some don't.

Actually, switching the default to ON should be safe. ata.device is fail-safe at this because during IDENTIFY command it validates upper 16  bits,  and  if they appear to be zeroes in all 128 longwords, then 32-bit mode is switched off. But, nevertheless, I know how tricky hardware can be, so I decided not to change original behavior. If  you think it's wrong in some cases, then it's possible to add one more  attribute  like  aHidd_ATABus_Default32Bit. If set to YES, then  this means that 32-bit PIO is safe to use by default.


====Devices====

*[[Aros/Developer/Docs/Devices/ATA|ata.device]]
*[[Aros/Developer/Docs/Devices/Console|console.device]]
*[[Aros/Developer/Docs/Devices/Narrator|narrator.device]]
*[[Aros/Developer/Docs/Devices/Printer|printer.device]]
*[[Aros/Developer/Docs/Devices/Trackdisk|trackdisk.device]]
*[[Aros/Developer/Docs/Devices/AmberRAM|amberram.device]]
*[[Aros/Developer/Docs/Devices/Timer|timer.device]]
*[[Aros/Developer/Docs/Devices/|.device]]

The Amiga used [[Aros/Developer/Docs/Devices|Devices]] to communicate with [http://aros-exec.org/modules/newbb/viewtopic.php?start=0&amp;topic_id=3475&amp;viewmode=flat&amp;order=ASC additional hardware]. AROS has replaced these hardware devices with hidd equivalents but some are still retained for backwards compatibility.

Local libraries/devices/handlers,etc. are supposed to override the ones in ROM if their version is higher than the one in ROM.

Here is the list of commands exec default: 
{| class=&quot;wikitable&quot;
| CMD_CLEAR
|  Purge the buffer of the device
|----
| CMD_READ
|  Playback Control
|----
| CMD_STOP
|  Stopped the activity of the device
|----
| CMD_FLUSH
|  Empty the queue of commands
|----
| CMD_RESET
|  Reset a device
|----
| CMD_WRITE
|  Playback Control
|----
| CMD_INVALID
|  Create an error
|----
| CMD_UPDATE
|  Gets updated device
|----
| CMD_START
|  Will restart the device
|----
|}

While most other &quot;stuff you communicate with&quot; in AmigaOS are devices &lt;ref&gt;AMIGA ROM Kernel Reference Manual: Devices, 3rd Edition. Commodore-Amiga, Inc. Addison-Wesley, 1991. {{ISBN|0-201-56775-X}}&lt;/ref&gt; that share a [http://gega.homelinux.net/AmigaDevDocs/ common base interface]. [[Aros/Developer/Docs/Devices1.3|OS 1.3 Device Drivers]].


====Handlers====

:[[Aros/Developer/Docs/Handlers/Pipe|pipe.handler]]
:[[Aros/Developer/Docs/Handlers/Port|port.handler]]
:[[Aros/Developer/Docs/Handlers/SFS|sfs.handler]]
:[[Aros/Developer/Docs/Handlers/FAT|fat.handler]]
:[[Aros/Developer/Docs/Handlers/PFS|pfs.handler]]
:[[Aros/Developer/Docs/Handlers/NTFS|fuse.handler]]
:[[Aros/Developer/Docs/Handlers/FFS|ffs.handler]]

filesystem handlers have their own separate system consisting of completely differently structured messages that dos.library use to pass requests (for things like reading, writing, getting directory contents etc.) to them. AROS originally went with implementing filesystem handlers as devices, which might arguably be more consistent with the rest of the AmigaOS API but which is quite incompatible with AmigaOS itself. However, it made it far harder to port filesystems and the gains were comparatively small, and so there's been a long standing goal of fixing this incompatibility. It has now, June 2011, been reintroduced to all AROS flavors.

are argstr and argsize valid for the handler startup environment?
DOS/RunHandler() calls DOS/CreateNewProcTags(), and then CallEntry() (in rom/dos/exit.c) to start the handler, so yes, argstr and argsize are *present* in the call signature of the handler.

Granted, argstr will be NULL and argsize 0, but those values *are* passed to the handler function using:

&lt;pre&gt;
AROS_UFC3(ULONG, entry,
                         AROS_UFCA(STRPTR, argptr, A0),
                         AROS_UFCA(ULONG, argsize, D0),
                         AROS_UFCA(struct ExecBase *, SysBase, A6));
&lt;/pre&gt;

Creating your own [without the whole build tree http://pagesperso-orange.fr/franck.charlet/temp/radeon.zip] and then  
&lt;pre&gt;
make stub
make
make install
&lt;/pre&gt;

SFS has two Root blocks, one at the start and one at the end of the disk. The Root blocks both contain the same information.  They hold various information about the disk structure and have the locations of some important blocks used by the filesystem.  

The Root ObjectContainer contains the Root directory Object. The name of this Object is the name of the volume. It is identical to a normal directory Object.

The Bitmap is used to keep track of free space. Each bit in a bitmap represents a single block. A set bit indicates a free block and a cleared bit a used block.

AdminSpaceContainers are used to keep track of space which has been reserved for storing administration blocks. Only the Bitmap, the Root blocks and the actual data stored in files aren't stored in administration space. Administration space is allocated in chunks of 32 blocks at a time. A single AdminSpaceContainer can hold information about a large number of such areas each of which has its own little bitmap of 32 bits.

Extents are stored in a B-Tree. The Root block holds a pointer to the root of the Extent B-Tree. Extents keep track of space in use by a specific file. Each fragment a file consists of has its own Extent. Extents are in a double linked list. The list can be used to locate the next or previous fragment of a file.

Below is the standard block header. This header is found before EVERY type of block used in the filesystem, except data blocks.  The id field is used to check if the block is of the correct type when it is being referred to using a BLCK pointer.  The checksum field is the SUM of all LONGs in a block plus one, and then negated. When applying a checksum the checksum field itself should be set to zero. The checking a checksum the checksum is okay if the result of the checksum equals zero. The ownblock BLCK pointer points to the block itself. This field is an extra safety check to ensure we are using a valid block.

Field	Type	Description
id	ULONG	The id field is used to identify the type of block we are dealing with. It is used to make sure that when referencing a block we got a block of the correct type. The id consist of 4 bytes and each blocktype has its own unique foure letter code.
checksum	ULONG	This field contains the sum of all longs in this block, plus one and then negated. The checksum can be used to check if the block hasn't been corrupted in any way.
ownblock	BLCK	Points to itself, or in other words, this field contains the block number of this block. This is yet another way to check whether or not a block is valid.

&lt;pre&gt;
struct fsBlockHeader {
    ULONG id;
    ULONG checksum;
    BLCK ownblock;
};
&lt;/pre&gt;
The algorithm to calculate the checksum of a block:
&lt;pre&gt;
ULONG calcchecksum(struct fsBlockHeader *block, LONG blocksize} {
    ULONG *data=(ULONG *)block;
    ULONG checksum=1;

    block-&gt;checksum=0;

    while(blocksize&gt;0) {
        checksum+=*data++;
        blocksize-=4;
    }

    return(-checksum);
} 
&lt;/pre&gt;

A Root block contains very important information about the structure of a SFS disk. It has information on the location and size of the disk, the blocksize used, locations of various important blocks, version information and some filesystem specific settings.

A SFS disk has two Root blocks; one located at the start of the partition and one at the end. On startup the filesystem will check both Roots to see if it is a valid SFS disk. If either one is missing SFS can still continue (although at the moment it won't).

A Root block could be missing on purpose. For example, if you extend the partition at the end (adding a few MB's) then SFS can detect this with the information stored in the Root block located at the beginning (since only the end-offset has changed).   Same goes for the other way around, as long as you don't change start and end point at the same time.

When a Root block is missing because the partition has been made a bit larger, then SFS will in the future be able to resize itself without re-formatting the disk.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
version	UWORD	The version of the filesystem block structure. You can check this field to identify what version of the filesystem your dealing with it and to see if you can handle this structure correctly. Don't try to interpret the disk's structure when this field contains an unknown version number!

sequencenumber	UWORD	Used to identify which Root block was written last in case the sequencenumber on both Root blocks don't match.
datecreated	ULONG	Creation date of this volume. This is the date when the disk was last formatted and will never be changed.

bits	UBYTE	Various settings, see below.
&lt;pre&gt;
pad1	UBYTE	Reserved, leave zero.
pad2	UWORD	Reserved, leave zero.
reserved1	ULONG[2]	Reserved, leave zero.
firstbyteh	ULONG	High 32-bits of a 64-bit number. This is the first byte of our partition relative to the start of the disk.
firstbyte	ULONG	Low 32-bits of a 64-bit number.
lastbyteh	ULONG	High 32-bits of a 64-bit number. This is the last byte (exclusive) of our partition relative to the start of the disk.
lastbyte	ULONG	Low 32-bits of a 64-bit number.
totalblocks	ULONG	The total number of blocks this partition consists of.
blocksize	ULONG	The size of a block of this partition.
reserved2	ULONG[2]	Reserved, leave zero.
reserved3	ULONG[8]	Reserved, leave zero.
bitmapbase	BLCK	Block number of the start of the Bitmap.
adminspacecontainer	BLCK	Block number of the first AdminSpaceContainer.
rootobjectcontainer	BLCK	Block number of the ObjectContainer which contains the root of the disk (this is where the volume name is stored).
extentbnoderoot	BLCK	Block number of the root of the Extent B-Tree.
reserved4	ULONG[4]	Reserved, leave zero.
&lt;/pre&gt;

&lt;pre&gt;
struct fsRootBlock {
  struct fsBlockHeader bheader;
  UWORD version;
  UWORD sequencenumber;
  ULONG datecreated;
  UBYTE bits;
  UBYTE pad1;
  UWORD pad2;
  ULONG reserved1[2];
  ULONG firstbyteh;
  ULONG firstbyte;
  ULONG lastbyteh;
  ULONG lastbyte;
  BLCK  totalblocks;
  ULONG blocksize;
  ULONG reserved2[2];
  ULONG reserved3[8];
  BLCK  bitmapbase;
  BLCK  adminspacecontainer;
  BLCK  rootobjectcontainer;
  BLCK  extentbnoderoot;
  ULONG reserved4[4];
};
&lt;/pre&gt;

AdminSpaceContainers are used to store the location and bitmap of each administration space. The AdminSpaceContainers are located in a double linked list and they contain an array of fsAdminSpace structures.  There is one fsAdminSpace structure for every administration space on disk.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
next	BLCK	The next AdminSpaceContainer, or zero if it is the last in the chain.
previous	BLCK	The previous AdminSpaceContainer, or zero if it is the first AdminSpaceContainer.
bits	UBYTE	The number of bits in each in the bits ULONG in the fsAdminSpace structure.
pad1	UBYTE	Reserved, leave zero.
pad2	UWORD	Reserved, leave zero.
adminspace	struct fsAdminSpace	An array of fsAdminSpace structures. The size of the array is determined by the current blocksize.
&lt;pre&gt;
struct fsAdminSpaceContainer {
  struct fsBlockHeader bheader;
  BLCK next;
  BLCK previous;
  UBYTE bits;
  UBYTE pad1;
  UWORD pad2;
  struct fsAdminSpace adminspace[0];
};
&lt;/pre&gt;
Field	Type	Description
space	BLCK	The first block of an administration space.
bits	ULONG	A small bitmap which is used to determine which blocks in an administration space are already in use. The number of bits in this bitmap is determined by the bits field in the AdminSpaceContainer.
&lt;pre&gt;
struct fsAdminSpace {
  BLCK  space;
  ULONG bits;
};
&lt;/pre&gt;

The fsBitmap structure is used for Bitmap blocks. A bitmap block is used to keep track of which space is in use and which isn't for a particular area of a disk.  All bitmap blocks together keep track of the free space for an entire disk. The location of the first bitmap block is known and all other bitmap blocks are stored in order after the first one.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
bitmap	ULONG	An array of ULONG's.  These hold the actual information on which blocks are in use and which aren't.
&lt;pre&gt;
struct fsBitmap {
    struct fsBlockHeader bheader;
    ULONG bitmap[0];
};
&lt;/pre&gt;
Each bit in a bitmap block (except for the block header) represents a single block. If the bit is set than the block is free, and if the bit is clear then it is full. The first ULONG in the bitmap area of the first bitmap block represents blocks 0 through 31 on the disk. Bit 31 of this ULONG is block 0, 30 is block 1, and so on. Bit 0 of the first ULONG represents block 31.

Below is a table to clarify how bitmaps work even further. The first column is the bitmap block number, the second column is the number of the ULONG in the bitmap array. The third column is the bit number in this ULONG, and the last column is the block which this specific bit, in this specific bitmap block represents.

We'll assume here that a bitmap block has room for 120 ULONG's (meaning there is room for storing 32 * 120 bits).

&lt;pre&gt;
Bitmap block	ULONG number	Bit number	Block represented
1 (first)	0	31	0
1	0	30	1
...	...	...	...
1	0	1	30
1	0	0	31
1	1	31	32
...	...	...	...
1	2	31	64
1	2	30	65
...	...	...	...
1	119	0	3839
2	0	31	3840
2	0	30	3841
...	...	...	...
&lt;/pre&gt;
The last bitmap block doesn't need to be completely used. The unused bits (which belong to blocks which do not exist) all have to be clear, to indicate that these blocks are in use.

The fsObjectContainer structure is used to hold a variable number of fsObjects structures (Objects) which have the same parent directory. Each ObjectContainer must contain at least one Object. If there is space in the ObjectContainer not used by the variable number of Objects then that space is zero filled. Objects always start at 2-byte boundaries, which means sometimes a padding byte is inserted between two Objects.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
parent	NODE	The node number of the parent Object, or 0 if this object has no parent (which is only the case for the Root directory).
next	BLCK	The next ObjectContainer belonging to this directory, or zero if it is the last in the chain.
previous	BLCK	The previous ObjectContainer belonging to this directory, or zero if it is the first ObjectContainer in this directory.
object	struct fsObject	A variable number of fsObject structures. The number of structures depends on the individual sizes of each fsObject structure and the blocksize. These structures are located directly after each other with at most 1 byte of padding between them to get the structures aligned on a 2 byte boundary.
&lt;pre&gt;
struct fsObjectContainer {
    struct fsBlockHeader bheader;
    NODE parent;
    BLCK next;
    BLCK previous;
    struct fsObject object[0];
}; 
&lt;/pre&gt;

fsHashTable is the structure of a HashTable block. It functions much like the hash table found in FFS user directory blocks, except that it is stored in a separate block. This block contains a number of hash-chains (about 120 for a 512 byte block). Each hash-chain is a chain of Nodes. Each Node has a pointer to an Object and a pointer to the next entry in the hash-chain.  Using such a hash-chain you can locate an object quickly by only knowing its name.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
parent	NODE	The node number of the directory Object this HashTable block belongs to.
hashentry	NODE	An array of Nodes. Each Node represents the start of a hash-chain (singly linked). A hash-value is calculated using the name of a file or directory, and this value determines in which chain the Object is linked. If there are no entries in a hash-chain then the hashentry value is zero.
&lt;pre&gt;
struct fsHashTable {
    struct fsBlockHeader bheader;
    NODE parent;
    NODE hashentry[0];
};
&lt;/pre&gt;
To calculate the hash-value using a name of an Object as input use these routines:
&lt;pre&gt;
UWORD calchash(UBYTE *name) {
    UWORD hash=0;
    /* Calculates a hash value over the passed in string.
       The end of the string can be either a NUL byte or a
       slash. The hash function is the same as the one
       used in FastFileSystem set to international mode. */
    while(name[hash]!=0 &amp;&amp; name[hash]!='/') {
        hash++;
    }
    while(*name!=0 &amp;&amp; *name!='/') {
        hash=hash*13+upperchar(*name++);
    }

    return((UWORD)(hash % (UWORD)((blocksize-sizeof(struct fsHashTable))&gt;&gt;2)));
}
UBYTE upperchar(UBYTE c) {
    if((c&gt;=224 &amp;&amp; c&lt;=254 &amp;&amp; c!=247) || (c&gt;='a' &amp;&amp; c&lt;='z')) {
        c-=32;
    }
    return(c);
}
&lt;/pre&gt;

The BNodeContainer is used to store B-Trees. Currently only one B-Tree is in use by this filesystem and it is used to store the location of file data. The fsBNodeContainer structure contains two other structures. The fsBlockHeader structure and the BTreeContainer structure.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
btc	struct BTreeContainer	Contains information about the B-Tree and its nodes contained in this block.
&lt;pre&gt;
struct fsBNodeContainer {
    struct fsBlockHeader bheader;
    struct BTreeContainer btc;
}; 
&lt;/pre&gt;


First try and locate the Root block. It should start with &quot;ROOT&quot;.  SFS has two of these, one at the start of the partition and one at the end.  One of the fields contains the block size, which will be the size of all important SFS blocks.

The root block has the root object container, which contains information about files and directories in the root directory.  The object 
containers basically hold one or more smaller structures that represent files and directories.  Scanning them all should give you a list of 
files and directories.

The root block also has the root of the Extent B-Tree.  This is a standard B-Tree structure (not a binary tree) that is used commonly in 
all kinds of system, you can read about how they work on Wikipedia if needed.  The B-Tree holds the information about *where* all the data is 
located for your files.

To recover your files, I'd do this:

* Find one of the root blocks, if not present, then figure out the block size your disk was using, and scan every block in turn to see if it 
looks like an ObjectContainer (check the fsBlockHeader's ID, check if the ownblock number is equal to the block you are currently scanning, 
and check its checksum).  So if you currently have block 12, and you see a block with the correct id, and ownblock = 12 and its checksum is good, 
then that's probably a valid ObjectContainer.

* With all the ObjectContainers found, you can extract filenames and directory names from these, but also the number of their first data 
block (in the field data) and the file size.  For small files (less than blocksize) this data block will be enough to recover the data.
For larger files, you might be lucky and all the remaining blocks are found after the first one (if the file was defragmented).  You can't be
sure of that though so...

* For larger files, you need to find all the BNodeContainers.  You could scan these in the same way you found all the ObjectContainers (look for 
blocks with the correct id, ownblock number and checksum). 

* With all the BNodeContainers found, you can try looking up the first data block of a file in the B-Tree structure.  This is a bit complicated 
-- the B-Tree consists of non-leaf nodes (blocks that only contain pointers to other B-Tree blocks), the isLeaf flag indicates this.  Or it 
can be a B-Tree leaf block.  The leaf blocks contain extra information per entry (see https://hjohn.home.xs4all.nl/SFS/extents.htm)
&lt;pre&gt;
struct fsExtentBNode {
     ULONG key;
     ULONG next;
     ULONG prev;
     UWORD blocks;
};
&lt;/pre&gt;

The key should be a block of a file (the first of a range), that is 1 to 65535 block long (depending the &quot;blocks&quot; field).  If the file is split 
up into more parts, then &quot;next&quot; will contain block number of the next range of blocks.  You need to look this up again in the B-Tree 
structure to find out how large it is. 

You can for the most part ignore the other structures (bitmap, admin containers).  The fsObjects and B-tree containers is what you'll need to 
recover the data. 


====Resources====

&lt;pre&gt;
rom/storage/mmakefile.src 
rom/storage/storage.conf 
rom/storage/storage_device.c 
rom/storage/storage_ids.c 
rom/storage/storage_init.c 
rom/storage/storage_intern.h 
rom/storage/storage_mount.c 
rom/storage/storage_unit.c
&lt;/pre&gt;

&lt;pre&gt;
rom/storage/includes/device.h 
rom/storage/includes/unit.h 
rom/storage/includes/volume.h 
rom/storage/storage_intern.h 
&lt;/pre&gt;

&lt;pre&gt;

&lt;/pre&gt;

*[[Aros/Developer/Docs/Resources/ACPI|acpi.resource]]
*[[Aros/Developer/Docs/Resources/Battclock|battclock.resource]]
*[[Aros/Developer/Docs/Resources/Bootloader|bootloader.resource]]
*[[Aros/Developer/Docs/Resources/Cia|cia.resource]]
*[[Aros/Developer/Docs/Resources/Filesystem|FileSystem.resource]]
*[[Aros/Developer/Docs/Resources/Hostlib|hostlib.resource]]
*[[Aros/Developer/Docs/Resources/Kernel|kernel.resource]]
*[[Aros/Developer/Docs/Resources/Misc|misc.resource]]
*[[Aros/Developer/Docs/Resources/Processor|processor.resource]]


==Debugging Code==

Please use the [http://sourceforge.net/tracker/?group_id=43586&amp;atid=439463 AROS Bug Tracker] if any issues are found.


GRUB Command line list

&lt;pre&gt;
sysdebug  
usbdebug - allows to see Poseidon's log in debug output
&lt;/pre&gt;


How do I get debugging out of InitResident ? If running i386 hosted on linux sysdebug=initresident on command line.
This  way  you can enable any of listed flags. sysdebug=all stands for &quot;everything&quot;


Have an executable (crosscompiled C++ code) which has 6 MB size on disk, but after loading it in memory, 250 MB RAM is taken. Any software that would split AROS executable into ELF part which would show actual size values?

 readelf -S executable

it will show you all sections in elf file, including sizes and requested alignment.

 objdump -h filename

That's will give you a quick overview of the sections and sizes. Ignore all the .debug.* sections. 
Would hazard a guess that you have a large .bss section. That's pretty common in C++.

Next step:

 nm—size-sort filename | grep ' [bB] '

The last few will be your biggest consumers. Would suggest -C to demangle the symbols... ;)


Suggest profiling the program (just use some printf's in the main loop for time spent in each part), it usually is quite easy to spot slow parts in games or apps.

If someone has '#define IPTR ULONG' somewhere. To see where that define is, redefine IPTR in the source code that fails, just above the line that fails, and the preprocessor will tell you where it was defined first.

===How to setup gdb with AROS/hosted===

Download AROS sources (AROS-xxxxxxxx-source.tar.bz2, where xxxxxxxx is the current date) and AROS contrib sources (AROS-xxxxxxxx-contrib-source) from 

Untar-bzip2 and cd to the unpacked archive directory.

 &gt; tar -xvjf AROS-xxxxxxxx-source.tar.bz2
 &gt; cd AROS-xxxxxxxx-source

Check the link to &quot;contrib&quot; (contrib-source) inside directory, e.g. correct like this:

 &gt; rm contrib
 &gt; ln -s ../AROS-xxxxxxxx-contrib-source.tar.bz2 contrib

Make sure you have the correct locale setting, otherwise compilation will fail at some point. See [http://aros.sourceforge.net/documentation/developers/compiling.php#setting-the-locale-to-iso8859 here] (or link below) for more on that. You might have to enter this:

 &gt; export LANG=&quot;en_US.ISO-8859-1&quot;

Now configure for a debug build - see &quot;./configure --help&quot; for more - here are two examples:

 &gt; ./configure—enable-debug=stack,modules,symbols
 
 &gt; ./configure—enable-debug=all

You may &quot;make&quot; now, or choose a separate directory for your build (e.g. for easy removal), for example if compiling for i386 architecture you could create a directory like this:

 &gt; mkdir linux-i386
 &gt; cd linux-i386
 &gt; ../AROS/configure—enable-debug=stack,symbols,modules

When done configuring you're ready to go:

 &gt; make

Building AROS takes some time - minutes on fast machines (e.g. 2.5&amp;nbsp;GHz quadcore), up to hours on slower machines.
The result will be AROS Linux hosted with gdb debugging enabled.

See aros.org documentation for more on compiling AROS, including more [http://aros.sourceforge.net/documentation/developers/compiling.php --enable-debug] options.


When finished, enter bin/linux-i386/AROS directory (replace &quot;linux-i386&quot; with your compilation target platform, e.g. linux-x86_64, etc.) inside the unpacked archive directory. This directory contains the required .gdbinit file for properly running AROS inside gdb.

 &gt; cd bin/linux-i386/AROS

Run AROS (here: with 128MB of memory) from gdb:

 &gt; gdb—args boot/aros-unix -m 128
or
 &gt; gdb—args boot/arosboot -m 128

 (gdb) r

Watch the shell output - in case AROS complains about &quot;LoadKeyCode2RawKeyTable: Loading &quot;DEVS:Keymaps/X11/keycode2rawkey.table&quot; failed!&quot; you should also see some instructions on how to create a keymap table. (see link above &quot;more on compiling&quot;, too.)
Quit gdb, and try default keymap table:

 (gdb) q
 The program is running.  Quit anyway (and kill it)? (y or n) y
 &gt; cd ../../..
 &gt; make default-x11keymaptable

Re-run AROS, as described above. Try e.g. RAros (= right windows key) + W to open a shell. If this doesn't work you have to create a keymap table yourself, quit gdb again, and make a new keytable:

 &gt; make change-x11keymaptable

A window will open. Watch the window's title bar, and follow the instructions.

When done, re-run AROS. RAros + W should now open a shell.

Next, compile your program with gdb support.


When you start GDB is there a warning which says

   warning: File &quot;&lt;whatever&gt;/.gdbinit&quot; auto-loading has been declined by your `auto-load safe-path' set to ...

If so start gdb with &quot;-ix .gdbinit&quot;


&lt;pre&gt;
Summary - In short:

* build AROS with debugging support (i.e. ./configure --enable-debug=all)
* build your application with debugging support (i.e. option -g)
* run AROS in the GNU debugger (you may use the GUI frontend &quot;ddd&quot; which simplifies usage a bit)
* start your application
* use the commands &quot;findaddr&quot; and &quot;add-symbol-file&quot; as written in the debugging manual
* if the debugger doesn't find the source code of your application use the &quot;dir&quot; command of the debugger. 
&lt;/pre&gt;

===How to use gdb===

In AROS open a shell, then (in host shell) use CTRL-Z to go into gdb. Use &quot;b Exec_CreatePool&quot; (one of the functions used early on by startup code in programs) to add a breakpoint, then &quot;cont&quot; and gdb will interrupt somewhere early during startup of &quot;program&quot;. Use &quot;bt&quot; to show backtrace and &quot;loadseg&quot; for &quot;??&quot; entries. One of them will be for &quot;program&quot;. After that you can use &quot;disassemble program&quot;.

One thing you need to make sure is that .gdbinit you have in your build directory is the same as in source tree. It has been modified some time ago, but the build system does not refresh it - you need to copy it manually

To recap, please read our debugging [http://aros.sourceforge.net/documentation/developers/debugging.php manual]:


To detect segfaulting when loading, try...

 ./configure—enable-debug—with-optimization=&quot;-O2&quot;

Because crash or no crash may depend on optimization. For newer compilers maybe this helps...

 --with-optimization=-&quot;-O2 -fno-strict-aliasing&quot;

One way to make crashes less random (more easily reproducible) is to activate the munging of free memory in rom/exec/freemem.c which is normally commented out:

&lt;pre&gt;
Index: freemem.c
===================================================================
--- freemem.c   (revision 34289)
+++ freemem.c   (working copy)
@@ -154,11 +154,12 @@
         * created with their TCB placed in the tc_MemEntry list. The workaround
         * is to avoid munging when FreeMem() is called with task switching disabled.
         */
+
        /* DOH! it doesn't work even this way. What's wrong???
-        *
-        * if ((SysBase-&gt;TDNestCnt &lt; 0) &amp;&amp; (SysBase-&gt;IDNestCnt &lt; 0))
-        *      MUNGE_BLOCK(memoryBlock, MEMFILL_FREE, byteSize);
         */
+
+       if ((SysBase-&gt;TDNestCnt &lt; 0) &amp;&amp; (SysBase-&gt;IDNestCnt &lt; 0))
+           MUNGE_BLOCK(memoryBlock, MEMFILL_FREE, byteSize);

     }
&lt;/pre&gt;

Mungwall can be turned on at runtime. Currently this works in all hosted versions. Just specify &quot;mungwall&quot; on kernel command line and it works. It can work on native too. In order to enable it you need to parse kernel command line, and if &quot;mungwall&quot; is present, set EXECF_MungWall bit in IntExecBase.IntFlags.

This needs to be done before the first AllocMem() for obvious reasons. And never reset back this flag! If you change it on a working system, you are doomed.

Hosted ports do the processing in rom/exec/prepareexecbase.c --enable-debug=mungwall option in configure still works but is going obsolete.  A kludge in rom/exec/allocmem.c is responsible for this and it needs to be removed when the transition is done.

BTW,  on  i386-pc  port it can be activated by &quot;mungwall&quot; argument on command line, you don't need to rebuild AROS.
New mungwall affects not only AllocMem()/FreeMem(), but also pools. I also tested it with AllocAbs(), seems to work correctly.

Runtime mungwall works on:

* pc-i386
* pc-x86_64
* linux-i386
* linux-x86_64
* darwin-x86
* linux-ppc

Works on all hosted ports, if the port itself is working.

* amiga-m68k
* Not on sam440-ppc and efika-chrp-ppc, even if they would be able to be built at moment. Does not work on (for now, need NVRAM support)

When starting my freshly rebuilt i386-linux-aros which was compiled with full debugging support I get sometimes the error &quot;Program exited with code 0377&quot;. Add the following to your .gdbinit: 
 set follow-fork-mode child

Here are some of the custom AROS gdb functions (defined in &quot;.gdbinit&quot; file) to resolve &quot;in ?? ()&quot; entries in backtrace: 
&lt;pre&gt;
#0 0xb7ffd424 in __kernel_vsyscall ()
#1 0xb7e2a657 in sigsuspend () from /lib/libc.so.6
#2 0xb7c63900 in ?? ()
#3 0xb7c640e3 in ?? ()
#4 0xb7c641e0 in ?? ()
&lt;/pre&gt;

You can use

 loadseg 0xb7c63900
 loadframe 2
or
 loadbt
and some others. Use &quot;help &quot; for a little help text. If the commands do not work try &quot;loadkick&quot; first.


Use &quot;thistask&quot;, &quot;taskready&quot;, &quot;taskwait&quot; to get list of AROS tasks. &quot;bttask &quot; shows backtrace of a task which is in ready or in wait queue and &quot;loadseg&quot; to resolve &quot;??&quot; entries in it's backtrace (&quot;loadframe&quot; would not work as it assume current running task).

===Native debugging tools for AROS===

 to enable debugging at boot time entering the GRUB menu editing line (E key) and adding &quot;debug=memory&quot; to your boot line, then press Ctrl+X to complete booting.


SYS:Tools/Debug/'''Bifteck'''

Open a shell and enter the line below to run Biftek and grab the debug messages collected in RAM into a text file.

 tools/debug/bifteck &gt; ram:debug.txt

and certainly does not open a window. It is a shell tool and only dumps data located from the debug location.
It is therefore important to 'catch' that debug data as soon as possible (before it gets overridden). You should invoke bifteck at the first opportunity before doing anything else.  You can use the TO option to store bifteck output to a file or you can pipe it manually to a file.  


SYS:Tools/Debug/'''Sashimi''' - displays error messages

One suggestion is to do a bug() debugging. Each time bug() is executed it will be output on sashimi. 
You include &lt;aros/debug.h&gt; and place bug(&quot;something\n&quot;); in your source code at location though which control passes.

To get the output - open an aros shell

 SYS:Tools/Debug/sashimi &gt; RAM:out.txt

'''Ctrl C''' to end the output to the RAM Disk.

# open shell, and type
# ram: (to switch to ram drive)
# System:Tools/Debug/Sashimi &gt; mylogfile.txt
# open AHI prefs using wanderer (or use another opened shell)
# play test sound
# close AHI prefs
# shell still open with Sashimi running: press ctrl-c to break Sashimi and return to prompt.
# in shell: copy mylogfile.txt System: (or to your required location)


SYS:Utilities/'''Snoopy''' - monitors OS function calls, run &quot;Sashimi&quot; to see Snoopy's output


SYS:Tools/'''WiMP'''    - the Window (and Screens) Manipulation Program

You can use the -E option of gcc to find out how preprocessor macros are expanded.

===Errors===

crash in strcasecmp usually means that one of its arguments is NULL.

empty space between these two names, prossibly some invisible character 

Old Amiga [http://www.amigacoding.com/index.php?title=Guru_codes&amp;redirect=no Guru Codes]

If the crash is in intuition. Sometimes, if it relates to text, a null pointer sets it off. 
an uninitialised pointer can have any address (this is a common fault).


Compiling on 64bit, Many old code would not properly typecast when doing pointer-integer conversions and thus at least throw a warning. This can easily be located and fixed.

[http://www.aros.org/cs/documentation/developers/app-dev/portable.php Portable code] 

* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.
* Fix (change IPTR/SIPTR back to ULONG/LONG) the few places which really rely on ULONG/LONG being exactly 32 bit. That's for things like pixel (ARGB) buffers, structs written/read to disk, colormaps, but probably not much else.

Then again, many current compilers also throw a warning when you try to assign a pointer value to an integer and the integer is possibly too small. This happens under .NET for example when a 64 bit pointer is assigned to something like an ULONG - so exactly the case which you described.


=== AI ===
                  Multimodal
                   Context
                   Prompt
                    &lt;---
  Model &lt;---&gt; Agent ---&gt; End user
 engine 

 Gemini      LMStudio
  Qwen       Comfyui
   etc

Recent, self hosting locally on laptops, mini pcs or desktops with '''quantization''' 4bit has reduced memory requirements but still require 16Gb+ and no high end gpu for text based 

*[https://lmstudio.ai/download LMstudio single gpu],

Google Gemma 4 Model 
*[ 12B QAT] 


Alibaba Cloud's [https://huggingface.co/ Qwen] team series of large language models LLMs 
*[https://huggingface.co/models?other=qwen3 Qwen 3], [], 
*[https://huggingface.co/models?other=qwen2 Qwen 2], [https://huggingface.co/Qwen/Qwen2.5-Coder-32B qwen 2.5 Coder],  


Small models 
*[ glm-ocr]
*[ medGemma]
*[ qwen 3.5-4b]
*[https://github.com/sipeed/picoclaw picoclaw claude] 


Bigger LLMs but with settings 
*[https://ollama.com/download Ollama single gpu]
*[https://github.com/ggml-org/llama.cpp/releases llama.CPP multi gpus],
*[ VLM multiple gpus],
Multimedia 
*[ Kimi K3], 


For the full experience 
#Training learning using 1+ high end GPUs at least 16GB VRAM per GPU card or 64Gb+ of unified, 16Core CPU with at least 64Gb of RAM system memory, though training can take weeks 
#Inference with custom asics or GPUs 

*[ MiniMax H3] for audio and video but gpu 8Gb+ 
*[https://github.com/jamiepine/voicebox voicebox]
*[https://github.com/ideogram-oss/ideogram4 ideogram4]
*[https://github.com/calesthio/OpenMontage OpenMontage]

&lt;pre&gt;
Text to Audio --\
Text to Video --/ Reference Video --&gt; Video and Audio output 
&lt;/pre&gt;

=== Example ===

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/* 1. Header for your name,date,purpose of program.
2. Pre-processor directives. This will include the #includes for files you want to add. 
3. Includes for function prototypes if necessary.
4. Main()
Create Pointers for Libraries and any Window you want to open.
5. Open necessary libraries.
6. Check if open exit program if fail.
7. Open a window exit program if fail.
8. Add your program
9. Close Window
10 Close Libraries.
11 End Program. */

/* standard os included headers &lt;.h&gt; */
#include &lt;dos/dos.h&gt;
#include &lt;dos/dosasl.h&gt;
#include &lt;dos/dosextens.h&gt;
#include &lt;dos/exall.h&gt;
#include &lt;dos/rdargs.h&gt;
#include &lt;exec/memory.h&gt;
#include &lt;exec/types.h&gt;
#include &lt;utility/utility.h&gt;
#include &lt;intuition/intuition.h&gt;

/* define as unresolved external references (proto/xxx.h) and compiler will link to auto(matically) open library */ 
#include &lt;proto/arossupport.h&gt;
#include &lt;proto/dos.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/graphics.h&gt;
#include &lt;proto/cybergraphics.h&gt;
#include &lt;proto/datatypes.h&gt;
#include &lt;proto/icon.h&gt;

#include &lt;workbench/workbench.h&gt;
#include &lt;workbench/icon.h&gt;

#include &lt;datatypes/pictureclass.h&gt;

#include &lt;proto/muimaster.h&gt;
#include &lt;libraries/mui.h&gt;

#include proto/bsdsocket.h

#include &lt;ctype.h&gt;
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;string.h&gt;

/* my own headers &quot;.h&quot; */

#define CTRL_C      (SetSignal(0L,0L) &amp; SIGBREAKF_CTRL_C)
#define  isDir(fib) ((fib)-&gt;fib_DirEntryType &gt;= 0)

#define ARG_TEMPLATE    &quot;FILE/A,ALL/S,QUIET/S,W=WIDTH/N,H=HEIGHT/N,M=METHOD,DEFTOOL&quot;

int main(void)
{


	return retval;
} /* main */
&lt;/syntaxhighlight&gt;

If you used c++, there is not yet c++ support in our shared library system. 
The easiest way to create / compile a shared library would be to use the AROS build system but the libraries can be created manually. You have to create a ROMTAG structure and some header files.  

A shared library is built with the %build_module macro with a line like this:

 %build_module mmake=MetaTarget modname=mylib modtype=library files=SourceFiles 

This macro can build different AROS module types, like devices, Zune classes, HIDDs, etc.

&lt;pre&gt;
##begin config
version 1.0
##end config

##begin functionlist
void func1(LONG a, LONG b)
int func2(char *s, ULONG a)
##end functionlist
&lt;/pre&gt;


Alternatively,  

&lt;pre&gt;
#ifndef LIB_H
#define LIB_H

#define __NOLIBBASE__

#include &lt;exec/libraries.h&gt;
#include &lt;exec/semaphores.h&gt;
#include &lt;dos/dos.h&gt;

#ifdef __AROS__
//#include &lt;aros/debug.h&gt;
#define reg(x)
#define __saveds
#endif

#define USESYSBASE struct ExecBase *SysBase = Base-&gt;My_SysBase;

struct MyTestBase
{
  struct Library   My_Test_Lib;
	struct ExecBase *My_SysBase;
	APTR             My_SegList;
  int              testint;
};

#endif
&lt;/pre&gt;

&lt;pre&gt;
/*--------------------------------------------------------------------------*/
/* Resident header written for mytest.library */
/*--------------------------------------------------------------------------*/

#define __NOLIBBASE__

#define VERSION         1
#define REVISION        0

#define LIBHEADNAME     mytest
#define LIBHEADNAMESTR &quot;mytest&quot;
#define COMPDATE        &quot;04.10.2015&quot;
#define VERS            &quot;1.0&quot;

#define LIBBASETYPE 	struct MyTestBase
#define LIBBASETYPEPTR  LIBBASETYPE *

#include &lt;aros/debug.h&gt;
#include &lt;exec/exec.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;exec/resident.h&gt;
#include &lt;exec/nodes.h&gt;
#include &lt;exec/libraries.h&gt;
#include &lt;aros/symbolsets.h&gt;
#include &quot;lib.h&quot;

const UBYTE lib_name[] = LIBHEADNAMESTR &quot;.library&quot;;

const UBYTE lib_id[] = &quot;$VER: &quot; LIBHEADNAMESTR &quot;.library &quot; VERS &quot; (&quot; COMPDATE &quot;) by ALB42\n&quot;;

extern const APTR FuncTable[];

AROS_UFP3 (LIBBASETYPEPTR, InitLib,
    AROS_UFPA(LIBBASETYPEPTR, Base, D0),
    AROS_UFPA(BPTR, seglist, A0),
    AROS_UFPA(struct ExecBase *, sysbase, A6)
);

static struct LibInitStruct
{
    IPTR                   LibSize;
    const APTR             *FuncTable;
    const struct DataTable *DataTable;
    APTR                    InitFunc;
}
const LibInitStruct =
{
    sizeof(LIBBASETYPE),
    FuncTable,
    NULL,
    (APTR)InitLib
};

const struct Resident romtag =
{
  RTC_MATCHWORD,              /* match word */
  (APTR)&amp;romtag,              /* back pointer */
  (APTR)(&amp;romtag + 1),        /* skip pointer */
  RTF_AUTOINIT | RTF_EXTENDED,/* flags */
  VERSION,                    /* version */
  NT_LIBRARY,                 /* type of module */
  0,                          /* init priority */
  (STRPTR)lib_name,           /* module name */
  (STRPTR)lib_id + 6,
  (APTR)&amp;LibInitStruct,
  REVISION, NULL
};

AROS_UFH3 (LIBBASETYPEPTR, InitLib,
    AROS_UFHA(LIBBASETYPEPTR, Base, D0),
    AROS_UFHA(BPTR, seglist, A0),
    AROS_UFHA(struct ExecBase *, sysbase, A6)
    )
{
    AROS_USERFUNC_INIT
    
    Base-&gt;My_SegList = seglist;
    Base-&gt;My_SysBase = (APTR)sysbase;
    Base-&gt;testint = 0;
    
    USESYSBASE
    bug(&quot;InitLib\n&quot;);
    
    if (!set_open_libraries())
    {
      set_close_libraries();
      return NULL;
    }
    
    return Base;
    
    AROS_USERFUNC_EXIT
}

AROS_LH1(LIBBASETYPEPTR, LibOpen,
    AROS_LHA (ULONG, version, D0),
    LIBBASETYPEPTR, Base, 1, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    
    USESYSBASE
    bug(&quot;LibOpen\n&quot;);

    (void)version;
    
    Base-&gt;My_Test_Lib.lib_OpenCnt++;
    return Base;

    AROS_LIBFUNC_EXIT
    
}

__saveds APTR LibExpungeInternal(LIBBASETYPE *Base reg(a6))
{
  USESYSBASE
  APTR seglist;
  bug(&quot;LibExpungeInternal\n&quot;);

  if (Base-&gt;My_Test_Lib.lib_OpenCnt)
  {
    return 0;
  }

  seglist = Base-&gt;My_SegList;

  Forbid();
  Remove((struct Node*)Base);
  Permit();
  FreeMem((APTR)Base - Base-&gt;My_Test_Lib.lib_NegSize, (LONG)Base-&gt;My_Test_Lib.lib_PosSize +
    (LONG)Base-&gt;My_Test_Lib.lib_NegSize);
  
  set_close_libraries();
  return seglist;
}

AROS_LH0(BPTR, LibClose,
    LIBBASETYPEPTR, Base, 2, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;LibClose\n&quot;);

    if (!(--Base-&gt;My_Test_Lib.lib_OpenCnt))
    {
      return LibExpungeInternal(Base);          
    }
    return 0;
	
    AROS_LIBFUNC_EXIT
}

AROS_LH1(BPTR, LibExpunge,
    AROS_LHA(LIBBASETYPEPTR, Base, D0),
    struct ExecBase *, sysBase, 3, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT

    (void)sysBase;
    
    USESYSBASE
    bug(&quot;LibExpunge\n&quot;);

    return LibExpungeInternal(Base);
	
    AROS_LIBFUNC_EXIT
}

AROS_LH0(LIBBASETYPEPTR, LibReserved,
    LIBBASETYPEPTR, Base, 4, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;LibReserved\n&quot;);

    return 0;
    //return (APTR)LibReserved();
    
    AROS_LIBFUNC_EXIT
}


// Space for your own functions
// do not forget to update the FuncTable as well

AROS_LH1(int, TestFunction,
    AROS_LHA(int, TestValue, D0),
    LIBBASETYPEPTR, Base, 5, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;TestFunction\n&quot;);

    Base-&gt;testint = TestValue + Base-&gt;testint;
    
    return Base-&gt;testint;
    
    AROS_LIBFUNC_EXIT
}

// Functable -&gt; Table of all functions in the Library, in right order - important!

const APTR FuncTable[] = 
{
    &amp;AROS_SLIB_ENTRY(LibOpen,LIBHEADNAME,1),
    &amp;AROS_SLIB_ENTRY(LibClose,LIBHEADNAME,2),
    &amp;AROS_SLIB_ENTRY(LibExpunge,LIBHEADNAME,3),
    &amp;AROS_SLIB_ENTRY(LibReserved,LIBHEADNAME,4),
    &amp;AROS_SLIB_ENTRY(TestFunction,LIBHEADNAME,5),
    (void *)-1
};

// AutoInit stuff
void *__PROGRAM_ENTRIES__symbol_set_handler_missing;
void *__LIBS__symbol_set_handler_missing;
// end of AutoInitStuff
&lt;/pre&gt;

Makefile
&lt;pre&gt;
VPATH = 
CFLAGS = -O2 -g -fomit-frame-pointer -W -Wall -Wno-parentheses
CC = i386-aros-gcc
LD = i386-aros-gcc
LDFLAGS = -nostartfiles -Wl,-Map -Xlinker linkermap
LIBS = -lautoinit -llibinit
STRIP = i386-aros-strip --strip-unneeded --remove-section .comment

OBJS = lib_header.o 

all: mytest.library

mytest.library: $(OBJS)
	$(LD) $(LDFLAGS) $^ $(LIBS) -o $@

lib_header.o: lib_header.c lib.h

clean:
	rm -f *.o *.library *.ppu testlibrary linkermap
&lt;/pre&gt;


Porting UNIX library to AROS - dealing with static variables which would make it easy to port such libraries to AROS, keeping the benefits of sharing them on disk, but losing the benefit of actually sharing them in memory.

Our problem arises by the fact we want to share the actual code (the .text section of the library) and constant data, but we need to have per-task .bss and .data sections. If we get rid of our intention to share the .text and .rodata sections, things get quite easy: just load and relocate the library whenever it's open, by whoever it's open. It's like statically linking the library into the executable, except that the final linking is done at runtime.

In the V0 branch, in workbench/hidds/hidd.nouveau was committed pcimock.hidd. This is a pci driver that allows mocking real PCI devices under linux-hosted. The main idea is to be able to run the real hardware driver under linux-hosted with as little changes as possible (some changes will always be needed though unless someone wants to write complete device simulator) so that driver's code paths can be executed and debugged using gdb. This was a very helpful capability when porting nouveau. Now it is externalized from nouveau.hidd and can be used by other people porting drivers. The pcimock.hidd can currently mock 4 different nvidia cards, 1 AGP bridge and also mock irq.hidd.

What's the difference between this driver and the pcilinux.hidd? I used that one to develop many different HW drivers for aros. As far as I understood the intention of pcilinux.hidd it is supposed to get access to real hardware that is running under linux. The pcimock.hidd goal is to mock the hardware. For example my dev box is a PCIE system, but I still would like to run the AGP codes paths in nouveau under linux-hosted to check if they don't seg fault. The other case would be to run codes paths for hardware that the developer does not have (Fermi cards in my case). In the case of pcimock.hidd, the AROS driver's code paths will execute as long as you add proper mocking (for example fill in PCI config area or values for registers in BARs). This is an advantage for ported drivers - the code should already work (since it worked on another system) but there might have been mistakes made during porting which can be detected easily with gdb.

In case you are writing your driver from scratch, pcilinux.hidd hidd will give you more advantage, since you can actually access the real hardware from linux-hosted.


== Misc ==

===APL, MPL, BSD, GPL and LGPL Licences===

The majority of AROS sources in licensed under AROS Public License ([http://aros.sourceforge.net/license.html APL]) which (to a degree) protects us from someone taking AROS sources and not contributing improvements back (for example MorphOS took some AROS source and then contributed changes back)

It is written to allow the use of AROS code in other open source or commercial projects without exception whilst providing a mechanism so that improvements/additions can find their way back to the original source in one form or another.

There are &quot;3rd&quot; party applications used by AROS that do not fall under this license, which are an extra &quot;Contrib&quot; download for convenience.

Anyone can port GPL-ed network and sound drivers as AROSTCP and AHI are GPLed. Direct using (porting) [http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs GPL]-ed code in other parts of AROS (gfx, sata, usb) is not possible because AROS license is not compatible with GPL. You need to utilize permissive licensed code like BSD or MIT/X11.


BSD and MPL license are the closest to APL.

APL however is not so compatible with LGPL/GPL.

LGPL case - you cannot statically combine APL code with LGPL. You can, however thank to LGPL being &quot;lesser&quot; restrictive, use LGPL dynamically loaded libraries in APL codes.

GPL case - you cannot combine APL code with GPL in any way if there is no explicit clause by GPLed code authors allowing that. If you do combine APL with GPL in &quot;bad&quot; ways described above - you have a problem (you violate GPL). This problem might result in everything in AROS becoming GPL or everything running or AROS becoming GPL (here I'm not sure really). The other scenario is that you are not allowed to legally distribute such code at all. To be honest I have grasped how to violate GPL, but I'm still no exactly sure what happens when you violate it (but I'm sure it's not anything nice)

GPL software can run on top of non-GPL &quot;system components&quot; (see system components exception of GPL), but the other way around (non-GPL using GPL) leads to problems. This means applications like scout, or Quake III are ok (in the majority of cases).

Theres no reason GPL drivers cannot be ported - but they cant be in AROS's ROM (requires linking APL code with GPL), nor can AROS depend on them (e.g. they must use existing apis).
If they are launched (dynamically linked) by a user action that is allowed. It is also allowed to distribute such binaries together for convenience.

GPL is not about statical or dynamic linking but is about executing process and function calls.


These components - SFS, isapnp, Zune texteditor, AHi, network drivers, freetype, openuirl, BHFormat, Edit and (&quot; dynamically loaded libraries&quot;) are LGPL, not GPL. Mesa/Nouveau stuff is MIT. Some user tools are GPL though.

'''AROS (system)'''
* system components (libraries/classes/devices/etc) cannot be GPL as they would propagate GPL to complete system as well as GPL is not compatible with MPL from which APL is based 
* system components can be LGPL v2 or a permissive license (MIT/BSD)
* system applications can be anything you like (but still I would prefer APL or permissive so the code can be reused if needed)

'''Contrib:'''
* no rules - contrib does not impact AROS system since nothing in AROS system depends on contrib.

About stealing code: The chances of this happening is exactly the same whether we are APL or GPL. If any closed-source option wanted to do it, there is no one that can validate otherwise. MorphOS has used some AROS codes, but contributed changes back.

The rationale behind APL is that while it guarantees that the original developer will get the improvements back (to a certain degree - file based), the person who uses the codes does not have to open his original codes. BSD does not guarantee that the original developer gets improvements. GPL requires the person using the codes to open his codes as well.

The copyright holders needs to stay - we just need information from them that the codes are available under APL (for example a checked-in file like in case of Poseidon). We don't do transfer of copyrights.

; Ultimately what can and cannot be done is up to the author(s) - not the licence.

===AROS source code tree===

* http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-trunk.txt
* http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-contrib.txt


Found this interesting (non-GPL) licensing 'anomaly' - to keep in mind for distributors.

Programs that lose their license if sold (&quot;non-profit only&quot; licensed):
  contrib/aminet/comm/term/TinyTerminal
  contrib/aminet/dev/basic/bwBASIC
  contrib/aminet/text/edit/xdme
  contrib/fish/aroach
  contrib/fish/lotto
  contrib/fish/shuffle
  contrib/fish/touch
  + cdvdfs.


Here is a list of all the GPL/GPLv2/GPLv3 licenses fossology found, what have explicit licenses in their comments.


 excluded LGPL, BSD/GPL dual licensed and programs (such as Prefs/Edit and BHFormat)

&lt;pre&gt;
AROS/rom/dbus/include/  AFL_v2.1 ,GPL_v2+  (supposedly AFL &lt; 3 is GPL incompatible) 
AROS/workbench/classes/zune/betterstring/include/  GPL_v2+
AROS/workbench/classes/zune/texteditor/include/  GPL_v2+
AROS/workbench/classes/datatypes/gemimage/ GPL_v2+ GPL
AROS/workbench/classes/datatypes/degas/  GPL_v2+
AROS/workbench/libs/openurl/README: GPL
AROS/workbench/network/smbfs/documentation/  GPL_v2
AROS/workbench/network/smbfs/source_code/  GPL_v2+
AROS/workbench/network/stacks/AROSTCP/bsdsocket/kern/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/mmakefile.src conf.h  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/sys/  CMU ,GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/net/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/api/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/conf/conf.h: GPL_v2
AROS/workbench/network/stacks/AROSTCP/netinclude/net/radix.h: CMU ,GPL_v2
AROS/workbench/devs/AHI/AHI/  GPL_v2+
AROS/workbench/devs/AHI/AddAudioModes/ GPL_v2+  AROS/workbench/devs/AHI/AddAudioModes/COPYING: GPL 
AROS/workbench/devs/AHI/Docs/texinfo.tex: GPL_v2+
AROS/workbench/devs/AHI/COPYING: GPL
AROS/workbench/devs/AHI/Drivers/EMU10kx/  GPL_v2+
AROS/workbench/devs/AHI/AHI-Handler/  GPL_v2+
AROS/workbench/devs/networks/rtl8029/  GPL   GPL_v2+
AROS/workbench/devs/networks/pcnet32/  GPL   GPL_v2+
AROS/workbench/devs/networks/ppp/LEGAL: GPL
AROS/workbench/devs/networks/atheros5000/  GPL_v2+
AROS/workbench/devs/networks/rhine/  GPL_v2+
AROS/workbench/devs/networks/nForce/  GPL_v2+  GPL
AROS/workbench/devs/networks/prism2/  GPL  GPL_v2+
AROS/workbench/devs/networks/fec/LEGAL: GPL
AROS/workbench/devs/networks/rtl8139/  GPL  GPL_v2+
AROS/workbench/devs/networks/etherlink3/  GPL  GPL_v2+
AROS/workbench/devs/networks/intelpro100/  GPL  GPL_v2+
AROS/workbench/devs/networks/rtl8169/  GPL   GPL_v2+
AROS/workbench/devs/networks/emac/   GPL   GPL_v2+
AROS/workbench/devs/networks/rtl8168/  GPL  GPL_v2+
AROS/workbench/devs/networks/realtek8180/   GPL_v2+
AROS/workbench/devs/networks/via-rhine/via-rhine.c: GPL_v2+
AROS/workbench/devs/networks/via-rhine/   GPL  GPL_v2+
AROS/workbench/devs/networks/e1000/  GPL_v2
AROS/workbench/devs/networks/sis900/  GPL   GPL_v2+
&lt;/pre&gt;

AHI: it has special provisions (COPYING.DRIVERS). The library is LGPL, preferences software is GPL and drivers can be anything without breaking GPL/LGPL.

Network stack: well, we are long overdue for a new, IPv6 enabled network stack anyway, anyone interested? ;) Seriously though it seems like the glue code is GPL and as all the drivers. However some of the drivers are our own code, so they could be relicensed to LGPL.

 Same filter as the AROS trunk list. These should all be libraries or plugins - no programs.

&lt;pre&gt;
contrib/regina/utsname.h: GPL_v2+

contrib/mui/classes/nlist/include/default-align.h: GPL_v2+
contrib/mui/classes/nlist/include/amiga-align.h: GPL_v2+

contrib/mui/classes/BWins/include/MUI/BWin_mcc.h: GPL
contrib/mui/classes/BWins/include/BWin_private_mcc.h: GPL
contrib/mui/classes/BWins/COPYING: GPL_v2
contrib/mui/classes/BWins/MCC_BWins.readme: GPL_v2

contrib/mui/classes/thebar/include/default-align.h: GPL_v2+
contrib/mui/classes/thebar/include/amiga-align.h: GPL_v2+

contrib/gfx/libs/wazp3d/LEGAL: GPL
contrib/gfx/libs/wazp3d/Wazp3D.readme: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d.c: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d_opengl.h: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d_opengl.c: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/Wazp3D.h: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/Wazp3D.c: GPL

contrib/libs/mpega/  GPL_v2+
&lt;/pre&gt;

http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-contrib.txt

===Types===

On AROS following rules apply:
&lt;pre&gt; 
1. BYTE/UBYTE is 8bit, WORD/UWORD is 16bit, LONG/ULONG is 32bit, QUAD/UQUAD is 64bit, the types are comparable with stdint types (int8_t, int16_t, int32_t, int64_t)
2. IPTR/SIPTR are integer types large enough to fit pointer, that is sizeof(IPTR) = sizeof(APTR) = 4 on 32bit system, and = 8 on 64bit system
3. ti_Data in TagList is large enough to hold a IPTR/APTR type.
4. never store a pointer in integer of type LONG. It may work (if the pointer has upper 32bits clear), but does not have to. Compiler should warn you about that.
5. If you are unsure about point 4, allocate your memory with MEMF_31BIT flag set. But don't expect that AROS internals will do the same.
&lt;/pre&gt; 
point 4 is actually important.


* UBYTE/BYTE for 8bit
* UWORD/WORD for 16bit
* ULONG/LONG for 32bit
* UQUAD/QUAD for 64bit

&lt;pre&gt;
UBYTE    Unsigned 8 bit integer variable (byte).
BYTE     Signed 8 bit integer variable (byte).
UWORD    Unsigned 16 bit integer variable (word).
WORD     Signed 16 bit integer variable (word).
ULONG    Unsigned 32 bit integer variable (longword).
LONG     Signed 32 bit integer variable (longword).
FLOAT    32 bit IEEE floating point variable.
UQUAD    Unsigned 64 bit integer variable.
QUAD     Signed 64 bit integer variable.
DOUBLE   64bit IEEE floating point variable.
BOOL     Boolean variable, TRUE and FALSE are also defined in exec/types.h.
VOID     Void.

APTR     A generic pointer for multiple purposes - Arrays.
STRPTR   A pointer to a null-terminated string.
IPTR     Really important in AROS, the only way to declare a field that can contain both: an integer or a pointer.
&lt;/pre&gt;

if you want to write really portable app, you may be interested in standard datatypes defined in C99: int8_t, uint8_t, int16_t, uint16_t, int32_t, uint32_t, int64_t, uint64_t, intptr_t, uintptr_t. They are all defined in inttypes.h include file.

In exec/types.h the following short-cuts are typedef'd. They are used often in AROS, so you should nearly always include exec/types.h and soon only they will be removed from sys/_types.h include, all types are now defined in include files named aros/types/xxx.h.

(Preparation for C library split; sys/xxx.h include will only be available there when compiling with POSIX C library)


Compiler specific types, like int and long might change their size. In case of AROS, similar to linux, int remains 32 bit whereas long grows to 64 bits in size.

If you use Amiga-like data types, i.e. BYTE/UBYTE, WORD/UWORD, LONG/ULONG and QUAD/UQUAD or the C99 standard types (uint8_t and so on, see stdint.h include) then you should have less issues to solve than by using types without size guarantee.

Of course, all pointers grow to 64 bytes using 64bit cpu. Most of the code can be just recompiled and will work. In rare cases, where e.g. pointers are casted to integers, a special care must be taken. Especially in the cases, where pointer is casted to LONG/ULONG (this code will break on 64 bit AROS) e.g.  '#define IPTR ULONG'.

With compiler delint patches which the majority of them are simple casting issues to make the compiler happy. Notice some of the changes involve introducing double casts. In very recent versions of GCC. Yes, the bulk of the double casts are for converting 32 bit addresses (ie from a 32 bit PCI DMA address register) to a 64 bit pointer. First cast is to IPTR (to expand to 64 bits, and prevent sign extension if the address is above 0x7FFFFFFF), and then to APTR.

ULONG != IPTR except on 32bit .. so if you need to store pointers make sure and use IPTR and not ULONG (which some old code does). For this reason things like Taglist elements are 64bit (since the tag data can be a pointer). 
If your passing items on the stack you should use the STACKED attribute to make sure they are correctly aligned (on 64bit all items on the stack are 64bit..)

There is more issues like using &quot;== 0L&quot; causes problems.

===Endian===

*BE 
*LE

Use the macros from &lt;endian.h&gt; instead making a guess based upon architecture defines
 
&lt;pre&gt;
#if _BYTE_ORDER == _BIG_ENDIAN

#elif _BYTE_ORDER == _LITTLE_ENDIAN

#else
+
#error &lt;whatever.h&gt; - Byte order for this architecture is unsupported! 
&lt;/pre&gt;


===SVN and GIT===

If you want to help develop AROS OS itself, you can 

* view current GIT/SVN entries [http://aros.sourceforge.net/ Aros Org website] or [https://github.com/aros-development-team/AROS Github], [https://github.com/ezrec older ezrec mirror], [https://github.com/michalsc/AROS/ older mirror], [https://trac.aros.org/trac/timeline TRAC], [], 
* awaiting update [http://repo.or.cz/w/AROS.git git repo], [http://www.ohloh.net/p/aros/commits ohloh] or [https://svn.aros.org/svn/aros/trunk/ svn repo] and access [Git version git://repo.or.cz/AROS.git here], 
* deprecated [https://www.gitorious.org/aros/aros/commit/a7fda9e ARIX commits] or [https://gitorious.org/aros/aros GIT old]

If you have SVN access (early 2015 introduced a new SVN server, create a new account at trac aros org) and/or have obtained the source [http://aros.sourceforge.net/download.php AROS site] - you can compile the current build tools/environment using: 

 &gt; make development

and follow this [http://aros.sourceforge.net/documentation/developers/compiling.php#building procedure] or [https://github.com/apiraino/aros_guide Guide] 


https://trac.aros.org/trac#Developing

If you plan on contributing back changes, please post information about such changes first on this [http://mail.aros.org/mailman/listinfo/aros-dev/ mailing list] for more experience developers can validate whether they are correct.


Then there are the nightly build machines. They svn update before the build and run configure as one of the next steps. autoconf might be added to the nightly build scripts.

Our build relies on packages downloaded from Internet (SDL for example) - it always worked this way. The minimal requirement (when just building core AROS) is binutils and gcc. If you build contrib as well, you need many more packages to be downloaded.

https://gitorious.org/aros/aros/commits/crosstools-II

git://gitorious.org/aros/aros.git

Branch crosstools-II there is only one commit on top of ABI_V1 
&lt;pre&gt;
../../aros-src/AROS/configure --enable-ccache
--with-portssources=~/aros/Sources --target=pc-x86_64
--with-aros-toolchain-install=/home/weissms/media/data/aros/test/crosstools/pc-x86_64
&lt;/pre&gt;
and
&lt;pre&gt;
../../aros-src/AROS/configure --enable-ccache
--with-portssources=~/aros/Sources --target=pc-i386
--with-aros-toolchain-install=/home/weissms/media/data/aros/test/crosstools/pc-i386
&lt;/pre&gt;
build OK.


:''More information: [[Aros/Developer/Maintainer|AROS Maintainer Docs]]''

===SDI Calls===

Integrate the 'SDI'-headers to allow easier porting to all amiga-like platforms.

&lt;pre&gt;
PUTCHARPROTO( PutTheChar, char c, struct SPrintfStream *s  )
{
 // REAL CODE
}
&lt;/pre&gt;

have &quot;SDI_compiler.h&quot; and &quot;SDI_hook.h&quot; included

its more organized like

 #include SDI/SDI_hook.h

than

 #include SDI_hook.h

option 1 --- i also use when back porting from amiga's..

&lt;pre&gt;
#ifdef __AROS__
#include SDI/SDI_hook.h
#else
#include SDI_hook.h
#endif
&lt;/pre&gt;

also

you can add the -i include/sdi/ location if you do not want to add or edit any files.


Defining HOOKPROTO to IPTR name(struct IClass * cl, Object * obj, Msg msg); solved the problem

A MUI application most likely needs only the HOOKPROTOxxx SDI macros. They are compatible with AROS, only the attributes (hook, object attribute) must be given in the right order. examine compiler/include/aros/symbolsets.h (AROS_LIBREQ)

compiling mui stuff for aros setting -std=gnu99 is necessary (i have had -std=c99 most of the time).

===Locale with Flexcat===

Most languages have a locale, but not every app is localized, the only thing needed is to translate the &quot;catalog&quot; files. It is a case of locating the correct catalog and saving the translated version.

For every app that lacks of your language catalog and is localized anyway, you should find (in the sources) files related to locale:

* file.cd = catalog descriptor, contains base msg, with internal language (usually english)
* language.ct = catalog translation, contains every translated msg, indexed as in the file.cd.

Compare with other localized apps... Then, &quot;make my_app-catalogs&quot; should create and install your translated catalogs. ex : for, saying, sys:prefs/wanderer:

on root of AROS sources, type:
 &quot;make workbench-prefs-wanderer-catalogs&quot;
then (if you changed the .cd file):
 &quot;make workbench-prefs-wanderer&quot;

For apps not localized, you have to adapt their code to support it, if it is possible...

noticed the original .cd file has many (//) strings at the end of any voice, so added them also to the .ct file. 
That (//) is only for cd files. I'm highly recommending to use FlexCat for updating ct files, e.g. like this:

 flexcat app.cd deutsch.ct newctfile deutsch.ct

You'll get error checking and new entries are marked in the resulting ct file.

When editing .ct files, only change those lines containing translation and perhaps version string, nothing else.
The rest is up to the relevant tool, flexcat. In order to update your translation, type in the following in your shell:

 flexcat xyz.cd xyz.ct NEWCTFILE xyz_upd.ct COPYMSGNEW

This way you will not only make sure you have correct translation file but flexcat also pre-fills newly added strings with &quot;*** NEW *** text. Even better tool for checking cd/ct/catalog files is catcheck, but this one is sadly only available for AmigaOS/68k...

Some languages have variations, like portugues from portugal and portugues from brasil differs...

This is the way to go. I will have a look at language files, but basically if those two languages differ you have to do two separated set of translation files, yes.
(you could create a brazilian slang language localization too)

* At system level localization for one language is a dot language file.
(ex: locale:languages/klingon.language)

* At app level localization is a dot catalog file
(ex: locale:catalogs/klingon/system/libs/dos.catalog)

* At sources level, the dot ct file, and &quot;$language&quot; dot cd files and some building framework.
(ex: catalogs/my_app.ct catalogs/klingon.cd catalogs/mmakefile.src support.c support.h)

Please, use Flexcat to generate CT files: 
 FlexCat wanderer.cd NEWCTFILE=deutsch.ct

Then fill the first 2 lines with something useful:
&lt;pre&gt;
## version $VER: wanderer.catalog 1.1 (9.2.2006)
## language deutsch
&lt;/pre&gt;

You can even update the CT-File: (This adds the new strings)
 FlexCat wanderer.cd deutsch.ct NEWCTFILE=deutsch.ct


To compile a catalog you only need the .cd file and your translation (.ct file):
 FlexCat multiview.cd deutsch.ct CATALOG=MultiView.catalog


[http://murks-ide.svn.sourceforge.net/viewvc/murks-ide/trunk/src/Catalogs/flexcat_linux?revision=100 Linux version of FlexCat]

: [http://aros.sourceforge.net/documentation/developers/app-dev/localization.php#localization-for-non-developers More information]


A script which compares the required version (i.e. the version which an application/module etc. tries to open) with the version of the existing CT files. The result is in this table:

https://github.com/aros-translation-team/translations/wiki/Progress

The following cases are highlighted:

    n/a i.e. CT misses at all
    version in existing CT file is lower than the required version


It might be a bit difficult to participate if you haven't worked with Git before but alternatively you can send your CT files to our Slack channel.

When the ct file has been generated via flexcat (flexcat keyshow.cd NEWCTFILE=spanish.ct) it has the following header:

---------------------------------------------------------------------------------------------------------------
## version $VER: &lt;name&gt;.catalog &lt;ver&gt;.&lt;rev&gt; (04.01.2021)
## language nolanguage
## codeset 0
;
---------------------------------------------------------------------------------------------------------------

Those values &lt;ver&gt;.&lt;rev&gt; are the version and revision of the CT file for the languaje or are the values of the application being localized?

The &lt;ver&gt; part must match with version which the application tries to open. You can find the value either in the column &quot;Required Version&quot; in the table which I've linked above, our you can look in the git repository. For keyshow it would be https://github.com/aros-translation-team/keyshow. You can find in the file &quot;catalog_version.h&quot; the right version number.
The &lt;rev&gt; part starts for new CT files with 0 and should be increased every time the CT file is updated.

Updated several files and created a few more that were missing on the spanish catalog.

The catalogs are in Git repositories at https://github.com/aros-translation-team

a) You tell me your Github user name. I'll invite you. You can work directly with the Git repositories.

b) You create Github forks of the catalog repositories and create pull requests.

c) You send the CT files to mrustler  gmx de


===C Utils Misc===

The AROS source uses at several places the __DATE__ macro to fill the date entry of a $VER tag. Problem is that c:version doesn't understand that date format (e.g. &quot;May 21, 2011&quot;). As a result the output of e.g.
&gt; &quot;version c:shell full&quot; contains &quot;(null)&quot;. Is extending the version command to understand the format of __DATE__  the right solution for that problem?

AmigaOs compilers should use __AMIGADATE__ macro or similar form, if it isn't implemented it could be emulated in makefile: -D__AMIGADATE__=\&quot;$(shell date &quot;+%d.%m.%Y&quot;)\&quot;

BTW. I think DD.MM.YYYY is better format than &quot;Month DD YYY&quot; because &quot;Month DD YYY&quot; is not localized in any way.

&quot;strnicmp&quot; shouldn't work with NULL pointers

The Situation:

compiled a linklib using c++ object files (using the c++ cross compiler).
compiled a C stub that uses the linklib (using the c++ cross compiler).

Try to link them together (using the c++ cross compiler) with C object
files (using the normal target c compiler) that need to use -nostartup
= cant do because using the c++ files pulls in arosc (for stdio etc.) -
so wants to have the autoinit stuff present.

What can I do about this??

If it is possible to manually open it then what do I need to do exactly?

=== ENV ===

The philosophy behind ENV: is that keeping configuration files there allows you to  'Use'  preferences  by  keeping  a copy in ENVARC: intact. However in some cases (like this one) it is not required.

99% of the time that statement is true (not required) for pretty much every file in ENV: or do people change their default icons - and prefs settings - every boot?

There seem to be a bad habit of late with developers changing things to reflect their own personal preference when the change isn't actually necessary - It would be nice if people could refrain from doing that in the tree without at least discussing it on the dev-list first (and with good reasoning unless they committed said work in the first place..)

We're not keen on the pollution of the &quot;S:&quot; dir: it's meant to be for scripts. What's wrong with &quot;ENV:&quot;?
Only the fact that it takes up RAM. I  understand  that  for  PCs  with  several gigabytes of RAM this is
irrelevant. But let's remember about other machines. The philosophy behind ENV: is that keeping configuration files there allows you to  'Use'  preferences  by  keeping  a copy in ENVARC: intact.

However in some cases (like this one) it is not required.

How about implementing in the style of HappyENV then? RAM-disk handler that falls through to reading from ENVARC: if there is no such file stored in it already. Removes RAM usage for unchanged files, removes the need to copy ENVARC to ENV in startup-sequence. 
Shouldn't be too hard to make from AmberRAM, or even just extend AmberRAM to provide this service.

Is it feasable to build a special version of AmberRAM handling ENV: that will try and copy the requested file from ENVARC: if it isnt found in ENV: ? 
Additionaly it could mark closed &quot;files&quot; as untouched - and expunge them from ENV: after a period of time to free up additional RAM:, or when the system is running low on free memory?

Silenty disappearing files may not be a good plan. Would be nice if the following would work:

ASSIGN :ENV SYS:Prefs/Env-Arc ADD
ASSIGN :ENV RAM:ENV  ADD

Where new files put in ENV: end up in RAM:ENV, and opening files looks in RAM:ENV first, then SYS:Prefs/Env-Arc

Well - that's essentially what im proposing but without the assigns - or need for a RAM:ENV directory. 
Adding it as a feature of AmberRAM sounds like the most memory efficient way (one handler to load in RAM) but that's only if it is possible to make it handle ENV: additionally to RAM:, and if it is even possible to add the proposed functionality (...and how to make it enable it when accessing ENV:).

===(AS)MP support===

If one has to recompile software for SMP multi core, is there any thing special one has to do to get software to run?   
Use task.resource if you need to query information about what tasks are running, and clear msgports completely when they are allocated.

Most code should not need Forbid. Use Semaphores, Messages etc. to sync your own code. 

Accessing system structures is a different thing. Use the proper API whenever possible.

How single structures will be protected in the future is still a moving target, at least it is not documented. And you should never  use undocumented stuff  


Ideas on for SMP multi-core

Another suggestion is ... Forbid/Permit function calls are meant to halt multitasking so as no other task could intervene with what ever the calling task is doing, e.g. setting semaphores. Disable/Enable calls are meant to halt interrupts and as a side effect they also halt task switching.

One option is to make it compulsory to protect shared resources with semaphores and forbid the use of simple Forbid() calls as to protect something. Setting semaphore should be done if possible with atomic instructions (check and alter in one instruction). Or make the second concurrent ObtainSemaphore call halt the second calling task and force if possible a task switch which ever gives better results. 

Semaphores could store the owning tasks task pointer instead of boolean to make things easier.

As long as the CPU initiates the DMA transfers through the OS, and the OS ensures that the transferred memory is within the region accessible to the user initiating the transfer, everything is fine. The CPU is the conductor, and the CPU by that has the control of which DMA transfer is initiated and which is not.
All you need to do is to write device drivers reasonable. Hint: CachePreDMA and CachePostDMA exist.
All the Os has to do is to verify that the memory regions to be transferred are valid, and prohibit direct access to the DMA control registers from user space. None of these algorithms imply huge costs.
The current OS design doesn't really allow virtual memory in first place, Forbid() is again the problem.

[http://www.tbs-software.com/guide/index.php?guide=autodocs.doc%2Fmemory.doc&amp;node=1 memory.library API] seem to low level. IMHO the programs should not know how the swapping is implemented. I would just go for one new memory flag
MEMF_SWAPPABLE that indicates that a certain memory region or a whole memory pool won't be accessed during Forbid()/Permit() etc. It only solves part of the problem, it only implements virtual memory and not memory protection. For the latter you need to be able make certain memory inaccessible by other programs, some memory read-only for one task and read-write for other tasks, etc. And I think this should be done in the same Address Space in order to avoid you constantly need to swap between different address spaces. 
So to summarize, if there are programs using this API we may provide a wrapper layer to get them working but I am not convinced this API should be the reference API with whom to provide VM to AROS programs.

=== Variadic ===

variadic functions (i.e. functions with an arbitrary amount of arguments).

&lt;pre&gt;
    #include &lt;stdarg.h&gt;
    [...]

    char * STDARGS GetKeyWord(int value, char *def, ...)
    {
        [...]
        va_list va;
        [...]
        va_start(va, def);
        [...]
        va_end (args);

&lt;/pre&gt;

Please keep with using stdarg rather than having va casted to a LONG * type and varargs handled manually. Doing so, prevents tons of casting, where a simple va_arg can be used. So, string = *((char **) args) instead of string=va_arg(va, char *).

&lt;pre&gt;
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;

int printf (const char * format, ...)

{
    int     retval;
    va_list args;

    va_start (args, format);

    retval = vfprintf (stdout, format, args);

    va_end (args);

    fflush (stdout);

    return retval;
} /* printf */
&lt;/pre&gt;

Couldn't find varargs.h or stdarg.h. and have no use for AROS_SLOWSTACKHOOKS or AROS_SLOWSTACKTAGS.

GCC looks for stdarg.h in a different place: 
 /bin/linux-i386/tools/lib/gcc/i386-aros/4.2.2/include/stdarg.h

Here is a path for a &quot;normal&quot; header:
 bin/linux-i386/tools/lib/gcc/i386-aros/4.2.2/../../../../i386-aros/sys-include/aros/system.h


The use of vararg.h isn't supported by newer gcc versions. If you want your code to run on architectures that pass part of variadic arguments in a number of registers you need to use AROS_SLOWSTACK macros. Otherwise your program will not work on powerpc and x86_64 ports.

Of course the SLOWSTACK stuff is not needed in a function that can use va_list, va_start, va_arg and va_end. It's only needed if you want to write functions like DoMethod or similar.

 #include &lt;stdarg.h&gt;

should be enough no matter if you do cross or native compiling. If it does not work, something is wrong and should be corrected.

Stdarg.h is here, Development:lib/gcc/i386-aros/4.2.2/include/

...which is part of the compiler's default include paths. In other words, #include &lt;stdarg.h&gt; works out of the box, indeed. (sorry, I should have just tried it before invoking &quot;search&quot; or &quot;find&quot;...)

furthermore, myprintf() as shown above won't work, because...

 printf(format, args);

...is wrong - the second argument does not match printf() prototype, it expects a argument list, but args is of type va_list (obviously) - so one has to use...

 vfprintf(stdout, format, args);

...instead, just like in the original printf(), and add fflush(stdout).

additionally, one could use...

 int myarg = va_arg(args, int);

...between va_start() and va_end() to access individual arguments, where each call to va_arg() returns an argument casted to the desired type (here: &quot;int&quot;) from the list given (here: &quot;args&quot;) and advances to the next one.

wrapping up vfprintf() and modifying the format string now is a major speedup! no more backslash-n typing! this has been haunting me for years!

On MOS and AmigaOS, the NewObject variadic function is kept in the static library. It takes most of the parameters on the stack - thanks to that the implementation of NewObject calls the NewObjectA function. Everything works perfect, and the typical MUI macros may be easily used.

This, however, is not the case when you compile for AROS. Here, NewObject is a variadic macro, not a function. Thanks such approach we do not need any custom compiler in case of systems, where the arguments of variadic functions are passed partially through registers and partially through the stack (This is the case of PPC and x86_64, this is also the reason why both OS4 and MOS require specially patched compilers).

Since NewObject is a macro, the gcc's preprocessor expects the list of macros arguments enclosed within parentheses. In MUI macros it is not the case. Imagine the following test code:

&lt;pre&gt;
#define foo(a,b) ((a)+(b))

int loosy_function(int a, int b)
{
    return foo(a,b);
}
&lt;/pre&gt;

This will compile and work, but the following piece of code:

&lt;pre&gt;
#define foo(a,b) ((a)+(b))
#define END )

int loosy_function(int a, int b)
{
    return foo(a,b END;
}
&lt;/pre&gt;

will fail with the error: unterminated argument list invoking macro &quot;foo&quot;

There are two ways of fixing your issue. Either create your new objects outside this huge MUI constructions, and in there use just a pointer, or get rid of the &quot;End&quot; macro and exchange it with &quot;TAG_DONE)&quot;.


Badly written software is, for example, casting va_list to an APTR or even doing so as if va_list were a plain table of function arguments. Such code needs to be fixed because it has very few chances to work anywhere but on author's machine ;)

The problem is nOt that they assume sizeof(APTR) == 4, its that they often do not use APTR, and use ULONG to store pointers exclusively. If the code used APTR/IPTR as it should - most of the &quot;problems&quot; wouldn't exist.

It would also help if people would start using variadic arguments properly. Many coders do assumptions which shall never be made. Instead, they should consider using stdarg.h file and all the va_* functions :)

===ABI===

In the head of our SVN repository there are now only 3 directories:

&lt;pre&gt;
admin/
branches/
trunk/
&lt;/pre&gt;

We have added two extra dirs there: tags and imports

As discussed when we branch ABI V0 and [[Aros/Developer/ABIv1|ABI V1]] it would also be good to introduce tags. Normally this is done in a directory in the repository called tags. Currently we don't have this directory there. (We do have branches/tags that is a hack I have done because one doesn't have write access in the top directory. I think this directory is not clean and should be removed).

The second directory I would introduce is an imports directory for implementing vendor branches as discussed in the svn [http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html book]. Currently we use code from several different projects and that code is stored inside the AROS tree; we seem to have problems with keeping this code up to date and merge our changes upstream. Maintainers of up stream projects like the MUI classes etc. have complained about this (to put it lightly).

Introducing these vendor branches would make it easier to see what changes we have made and make patches to be sent upstream and make it easier to import newer upstream versions of their code. Although can't &quot;copy&quot; the vendor branch into the main branch because it's already there, so start with a &quot;merge&quot;.

Yes, the first step to make the code already in the repository compatible with the vendor branches will be the most difficult. The best way to do it the following way:

* first import the version on which the current AROS code is based into the vendor branch
* then import the new version over it in the vendor branch
* finally merge the difference between these two version in the AROS code present in the repository.

For example, place NList directly under vendor and not in a subdirectory like &quot;contrib/zune/classes&quot;.

Actually after we have a stable [http://aros.sourceforge.net/documentation/developers/specifications/drafts/abiv1.php ABIv1 (2012 or later)]. We need to move away as much as possible from the contrib directory to some other repositories. The reasons are ...

* The AROS repository should be for the core AROS code.
* other contrib projects should be tried to be compiled for all Amiga-like OSes.
* The release scheme for AROS and the other programs should not have to be aligned.
* Binary versions should be provided on aros-archives and on aminet and/or OS4Depot to install them. (Some clever programs should maybe be provided to make the life of distribution developers easier). 
* avoid parallel forks of programs for AROS and the other amiga OSes.

If there is really a need for a place for hosting AROS projects we may investigate setting up such a server but then including bug tracking, governance, maillist, etc. for each project separately. I personally think there are already enough places like sourceforge, google code, savannah, etc. where people can go for hosting such projects.

==Links==

* http://amigadocs.hokstad.com
* http://amigadocs.hokstad.com/doku.php?id=dev-links


 In the future...?
*AROS 64bit - SMP, Vulkan with OpenGL compability layer
*AROS 32bit - keep for historic reasons 

What would you like to see implemented in AROS?
ABIv1 completed, SMP (x86_64),  SendMsg()/GetMsg() to support memory protection between target and destination, in that order.   Michal Schulz and Jason McMullan have been toying with the question &quot;What are the minimal changes needed to the AmigaOS 3.1 API to support SMP&quot;?  The answer so far seems to be &quot;few, but subtle&quot;.  For example, SysBase-&gt;ThisTask is no longer meaningful on SMP, but FindTask(NULL) is.  Disable() and Forbid() are shockingly bad on performance, but adding a spinlock semaphore mode to SignalSemaphore will help new code on SMP.  

Leveraging a 'common' OS with a lot of machine support (Linux, MacOS, Windows, QNX, etc.) is something that AROS has been doing for quite a long time, and it is the biggest strength of AROS. This AROS experience and programming model, in the same way the Google's Android layers on top of Linux, or MacOS X layers on top of the Darwin/BSD kernel, as a first step 

* The graphics + layers subsystem could be implemented as a shim on top of a OpenGL ES implementation (ie on any modern Linux system, or the RaspberryPI's hardware, MacOS X, etc). 
  - This also allows every window to be on its own 3D surface with backing store, allowing Wanderer (or a Commodity)
rearrange/zoom/animate app windows without having to send a pile or refreshes to them

* Use OpenAL as the sound backend
* AROSTCP would be a thin layer over the native OS's TCP/IP stack
* dos.library, poseidon.library, and input.device would be slim shims over the native APIs
* If we move to loading all libraries' into the application's task space, instead of a single global instance of the library, this will allow SMP and MMU more easily. 
  - Yes, it will require a lot of work in the libraries to make this transition
  - Yes, I do think it will be worth it in the end.

* A 'fat binary' install format (or, maybe LLVM bytecode) that can be 'flattend' to the target architecture on installation.

So, what would this 'AROS of the future' look like?

* AmigaOS 3.x style API, with certain 'fundamental changes' to message passing
* Uses the underlying OS' device drivers, so more AROS developer effort can go to user-visible features and bugfixes 
* Allows AROS applications to run side-by-side with the OS's native apps


And why would anyone want to program on such a system?

* AROS applications would run on any system that has the AROS Framework installed
* AROS applications are pixel-for-pixel the same on all platforms. 
* Develop with the knowledge that you are guaranteed OpenGL and OpenAL, and the rest of the AROS Framework

an option for mmake to dump its dependency of metatarget in a graphviz[*] input file. This should make it possible to visualize the dependencies and hopefully be inspiration for cleaning up some mess, circular or unneeded dependencies and so on.


AmigaOS gcc 9 [https://franke.ms/amiga/gcc.wiki Old versions] able to create binaries for AmigaOS and [https://eab.abime.net/showthread.php?t=93813 Upgrading gcc versions] 


==References==
{{reflist}}
{{status|50%}}

{{BookCat}}</text>
      <sha1>t8xy7wn0fkpwqjx4rx8fwu6zq75kcd8</sha1>
    </revision>
    <revision>
      <id>4668983</id>
      <parentid>4668982</parentid>
      <timestamp>2026-09-05T18:34:53Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668983</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="125167" sha1="rpstz2px7etbpw28381hudnrbec86og" xml:space="preserve">{{ArosNav}}

==A technical overview of AROS==

Google translation [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=de&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs German], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=fr&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs French], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=it&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Italian], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=es&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Spanish], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=hi&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Hindi], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=zh-CN&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Chinese], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ru&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Russian], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pl&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Polish],
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pt&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Portuguese]

{{Uncited}}

AROS,&lt;ref&gt;[http://aros.sourceforge.net/download.php References and sources]&lt;/ref&gt; like AmigaOS (TM), is a [[w:Message passing|message-passing]], [[w:Preemption (computing)|preemptive]] [[w:Multitasking|multitasking]] [[w:Operating system|OS]].

It uses [[w:Reentrant (subroutine)|re-entrant]] shared libraries to save memory space.

AROS is based around an executive library kernel (Exec) and two other libraries:

* Exec (the &quot;kernel&quot;, which is not a kernel in the modern sense), 
* Intuition (graphics and GUI, integrated into the system) and 
* AmigaDOS (Disk Operating System, the Metacomco's Tripos modified to work with Exec).

The design philosophies of AmigaDOS and Intuition are rather different, the former adopting a C-like API and the latter creating an [http://www.basden.demon.co.uk/amiga/amiga.oo.html object-oriented], message passing aware environment for the programmer. The system base is the only absolute address in AmigaOS (located at 0x00000004) this does differ with AROS as AROS SysBase is automatically provided (no $4) but everything else is dynamically loaded. The OS is well known for delivering high performance due to its close connections with the hardware, while simultaneously having the flexibility to support re-targetable graphics (Cybergraphics) and retargetable audio subsystems (AHI).

: Diagram showing relationships of libraries to system needed


Remember, AROS is a [http://en.wikibooks.org/wiki/Aros/Developer/ABIv1 research] operating system, and while all contributions to the base AROS code are welcome, please contact the dev list first for any core changes. Writing applications for AROS does not have this requirement. 

While AROS appears and feels almost feature complete, it is still [[Aros/Developer/IncompleteAPIs|missing a small number of functions]] from the Amiga API. 


[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1201 This thread provides] information for setup, [http://www.aros.org/documentation/developers/index.php documentation] and whether you are interested in core OS changes and/or writing/porting software apps 

*you compile directly under AROS, which can be running on either real hardware, virtual hardware
*in hosted mode under linux/window, cross-compile from that host OS (save your files as ISO-8859-15 encoding instead of UTF-8) [https://github.com/BlitterStudio/aros-compiler-docker Docker images] 


'''The repository''' for 64bit and 32bit ABIv1 all hardware platforms is [https://github.com/aros-development-team/AROS current development version]. 
There are many forks of this so that developers can work on their own and forward changes at a later date as discussed on the dev forum 


64bit PC is one of two hardware platform with another fork called [https://github.com/deadwood2/AROS abiv11] which is used for Aros One x64 PC 

32bit PC is the other fork [https://github.com/deadw00d/AROS/tree/alt-abiv0 repository for current stable PC version ABIv0 with backported ABIv1 features is located which is used on AROS One and Icaros x86 32bit based distros] this is for historic reasons 


Any [https://github.com/aros-development-team/AROS/issues bugs / issues can be added for ABIv1 issues]. The two individual PC forks have their own issues tab on their github webpages 

We have a [https://arosdevteam.slack.com/archives/CUFV48U3H slack here], discord on [https://discord.gg/UKp9qdEBuQ Discord@AmigaDev], 


==Software Development for AROS==

===Programming languages===

====Common to all====

'The Developer Environment', which primarily supports C/C++ code, there are other programming languages available for AROS:

'''Scripting''' 
:[[Aros/User/DOS|DOS]] 
:[[Aros/Developer/Docs/LUA|LUA]] 
:REXX [[Aros/Developer/Docs/Rexx|Regina (AROS' ARexx)]] 


====Needs to be compiled/ported====

::[[Aros/Developer/Docs/LLVM|LLVM]] 
::Python [ Info], [], 
::[https://ae.arosworld.org/index.php?board=11.0 FreePascal FPC Aros-Exec thread], [https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language fpc arm here is very old and will not work], FreePascal for AROS has its own [http://fpcaroswiki.alb42.de/ Wikibook], 


::[http://sourceforge.net/projects/xamos/ X-Amos Basic] 
::[http://sdlbasic.sourceforge.net/ SDLBasic] ([https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language ])
::[[Aros/Developer/Basic/Basic4SDL|Basic4SDL]] ([https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language ])
::[http://alvyn.sourceforge.net/ Alvyn] ([http://www.dusabledanslherbe.eu/AROSPage/MISC.14.html download]) 


::[http://www.airsoftsoftwair.com/ Hollywood when enough users warrant a port - paid one time fee language] 


::[[Aros/Developer/Docs/E|AmigaE Portable E]]


====Hardware Restricted====

'''Basic'''

:[http://amos.pspuae.com/AmosProManual/contents/c1.html '''Amos Pro'''] [http://amos.pspuae.com/index.php?action=forum#1 compatible] [http://www.amigacoding.com/index.php/Main_Page commands] (all incomplete) 

:'''Blitz Basic''' [http://aros-exec.org/modules/newbb/viewtopic.php?post_id=46537#forumpost46537 none on AROS] 
:: [http://www.amiforce.de/main.php Amiblitz] on amiga(TM) emulator

:'''Amiga Basic'''
:: [ ACEBasic]

'''Misc''' 
:Ruby [http://www.ruby-lang.org/en Info]/[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language Ruby 32bit PC], 


===Where to get the C/C++ Environment===

If you want to develop for AROS, its generally easier to be running linux hosted AROS development environment especially for C++, cross compiling the code. That's how most developers now are doing it. g++ is used to compile owb web browser as well as some other AROS software. If you were hoping for a rich set of C++ libraries or classes defined for the OS feature set, you might be disappointed.

AROS Native compiling is possible, but you're much more likely to run into the odd bug(s) in the dev environment since it gets little testing and fixing by other developers.

Is there a sftp software or scp over ssh available?
Maybe. At least the security part would be handled by [https://github.com/jens-maus/amissl amissl] [https://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc port]. [https://github.com/BlitterStudio/dopus5 DOpus5] has recently added sftp support. See here for a [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1974&amp;highlight=ssh&amp;pid=12073#post_12073 ssh scp client]

[https://arosdevteam.slack.com/join/shared_invite/enQtOTc4Mzg0NDIzNzQ0LWQ2NWZmNmMwNGIwNGEyNTgxNzU3MGFjMTk3ZThmOTQ1MTVjMzhmNTllYWQ0ZTUxMjBjMGE0Y2VjMDJmNTc5MzI#/shared-invite/email Slack Dev Forum] 


====Cross compilers from Windows or Linux====

*Windows WSL2 walkthrough can be [https://arosnews.github.io/how-to-cross-compile-aros-hosted-wsl/ found here] 


you want to build AROS. No problem.

Here are instructions for PC 64-bit:
https://github.com/deadw00d/AROS/blob/master/INSTALL.md

Here are instructions for PC 32-bit:
https://github.com/deadw00d/AROS/blob/alt-abiv0/INSTALL.md

And as always has been the case you can use the contrib archive to 'obtain' the development directory which contains the /native/ AROS gcc compiler and tools. That compiler is used to build AROS itself but can be used outside the AROS build process by providing --sysroot with indicated directory to cross compile for AROS.


'''64 bit'''


'''32 bit'''

A good option for multiple OS is [https://axrt.org/index.php?tab=download-aros AxRuntime lets developers compile their Amiga API-based applications as Linux binaries being able to utilize modern development tools available on Linux, like IDEs, debuggers, profilers, etc] 


Older 32bit guides for Linux hosted compiler

Please install these packages before moving to next step. Below is a reference list for Debian-based distributions. Reference build system was Ubuntu 18.04/20.04 amd64.

subversion git-core gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libx11-dev libxext-dev libc6-dev liblzo2-dev libxxf86vm-dev libpng-dev gcc-multilib libsdl1.2-dev byacc python-mako libxcursor-dev cmake zsh mingw64

Do all of these operations under home directory of your user or another directory where your user has write permissions.

Specifically, in a section &quot;Linux-i386&quot;, be sure first to build the cross-compiler (toolchain-alt-abiv0-i386) and only then AROS itself (alt-abiv0-linux-i386).


Clone &amp; build
&lt;pre&gt;
$ mkdir myrepo
$ cd myrepo
$ git clone https://github.com/deadw00d/AROS.git AROS
$ cd AROS
$ git checkout alt-abiv0
$ cd ..
$ cp ./AROS/scripts/rebuild.sh .
$ ./rebuild.sh
&lt;/pre&gt;

Now to the build selection below - Linux-i386 

Select toolchain-alt-abiv0-i386 - Select alt-abiv0-linux-i386 (DEBUG) 

Start AROS by:
&lt;pre&gt;
$ cd alt-abiv0-linux-i386/bin/linux-i386/AROS
$ ./Arch/linux/AROSBootstrap
&lt;/pre&gt;


Pc-i386 Select toolchain-alt-abiv0-i386 (if not built yet) - Select alt-abiv0-pc-i386

ISO image available in alt-abiv0-pc-i386/distfiles


Now that we have linux-hosted build, we can resume native (option 2).
Run ./rebuild.sh and selection option 2. Wait until it finished, then:
&lt;pre&gt;
$ cd alt-abiv0-pc-i386
$ make
&lt;/pre&gt;

Now
&lt;pre&gt;
$ make bootiso
&lt;/pre&gt;


Now, your compiler is located in toolchain-alt-abiv0-i386 directory and named i386-aros-gcc. Includes are in alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development/include and libraries are in alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development.lib.

This is how then can be passed to the compiler:

/home/xxx/toolchain-alt-abiv0-i386/i386-aros-gcc --sysroot /home/xxx/alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development -L/home/xxx/alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development/lib 

../toolchain-alt-abiv0-i386/i386-aros-gcc --sysroot bin/linux-i386/AROS/Development local/helloworld/helloworld.c -o local/helloworld/helloworld


Another method was using Debian like distros and download the gimmearos.sh script (on [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/cross aros-archives]) to setup the developer environment by downloading necessary packages ...
The gimmearos script is a good start in that direction, building the cross compilers and hosted AROS environment, but gimmearos.sh might be out of date or not be completely compatible with any given linux distro. 

In order to do that, you have to compile AROS yourself. Download AROS source archive not contrib. Compile AROS by entering the main directory

 ./configure
 make

([http://aros.sourceforge.net/documentation/developers/compiling.php More on compiling AROS]). The result will be a basic AROS system without development tools.

To compile C++ on Linux, type 'make gnu-contrib-crosstools', creating the cross-compilers in ./bin/linux-i386/tools/, named i386-aros-gcc, etc.

'''Note''': Currently, to make the cross compilers usable copy 'collect-aros' from tools/ to tools/i386-aros/bin/. At the moment the cross compilers if used from the Linux command line will only find it when it's there.

If you want to compile native compilers (the Developer Environment), type 'make contrib-gnu-gcc', creating native compilers in AROS' System:Development/bin directory.

When the output needs to be stripped &lt;code&gt;--strip-unneeded --remove-section .comment&lt;/code&gt;

The Obj-C backend should build out of the box.

Open contrib/gnu/gcc/mmakefile.src and search for the line which contains &quot;--enable-languages&quot; and add &quot;objc&quot; to the list of languages that follows it.

    --enable-languages=c,c++,objc

Better make it—enable-languages=c,c++,objc,obj-c++

ObjC++ is broken as soon as you try to use exceptions, but that might change in future GCC versions and it does not hurt having it there already.


Do you need a cross-compiler or a real compiler? In the first case you can get away with just downloading the proper gcc archive, apply the patch and proceed with the normal gcc build. In the case of a real cross-compiler then when downloading the contrib sources, also need to download the normal sources, place the contrib sources into a directory called contrib, need to install autoconf+automake+perl+python, call ./configure, cd into the subdirectory and type make.

to rebuild GCC with host == build == target == i386-pc-aros. So just get the vanilla sources and apply the patches without bothering about the build system?


[https://vmwaros.blogspot.com/2019/10/a-pre-configured-development-machine.html pre-configured VM environment vmware virtual machine to develop AROS and AROS software]


====Native compilers for AROS====

Namely gcc for C or g++ for C++ are supplied with the [[Aros/Developer/Docs#The Developer Environment|Developer Environment]], which is already '''setup''' and part of any current AROS distribution like AROS One or the nightlies 

* Current GCC 6.5 (32bit) though moving to 10.5 and 15.1 (64bit) 
* Older software components. GNU GCC 4.x GNU BinUtils, GNU Fileutils 4.x, GNU Textutils and others usually deprecated 

On single partition systems and the Boot ISO, the AROS Developer environment is installed under &quot;SYS:Development/&quot;. Systems with multiple partitions - such as a Work: partition - tend to install it to there instead, however it can be installed manually to any location. Please remember, if moving, that you will need to correct the Development packages 'install location' env variable to point to the new locations root - look in SYS:S/startup-sequence.

&lt;pre&gt;
Assign Development: SYS:Development 
Assign C: Development:bin ADD 
&lt;/pre&gt;


In the aros build instructions. you need to check out contrib and/or ports into your AROS source directory, as subdirs. then, assuming you are building in an external build dir, as you should, you simply configure and &quot;make contrib&quot; for instance or whatever submodule you might want to build.


===Beginners Tutorials in C C++===

As AROS is [http://eab.abime.net/showthread.php?t=29856 C based] API compatible to AmigaOS 3.x, so most of the information on programming C on the Amiga applies to AROS as well. Please note that there is a lot of AmigaOS 1.3 (1985-1989) and [https://www.markround.com/amigaguide AmigaOS AOS 2.x (1990-1992)] information around but OS3.1 is recommended but limited in amount. 

Brief overview of what is required to write AROS Applications

# Using [[Aros/Developer/Docs/Libraries/Intuition|Intuition]] for basic screens/windows 
# Using graphics within windows via 8bit [[Aros/Developer/Docs/Libraries/Graphics|graphics]] and so onto  15-16-24bit [[Aros/Developer/Docs/Libraries/CGFX|cybergraphx]]
# Load and save work to [[Aros/Developer/Docs/Libraries/DOS|dos]] disk drives
# Using the [[Aros/Developer/Zune|ZUNE GUI Environment]]


Writing native games require this extra information

# Using [[Aros/Developer/AHIDrivers|AHI audio hardware independent API]]
# Using USB joystick/joypad with the Poseidon USB stack through [[Aros/Developer/Docs/Libraries/LowLevel|LowLevel]] library


Additional features that could be added later

# Adding additional [[Aros/Developer/Docs/Libraries/Locale|Locale]] language translations to your program 
# Adding a [[Aros/Developer/Docs/Rexx|AREXX/Regina]] port to your application 
# Executing Amiga(TM) [[Aros/User/DOS|DOS]] commands from your application
# Using [[Aros/Developer/Docs/Libraries/Icon|icons]] (.info files) and icon tooltypes (stack, version, and program startup options)
# Local couch or IP based SANA2 networking co-op multi player gaming support 


Most AmigaOS programming books are nowadays very much out of date as most are from the late 1980s and do not cover later amigaOS releases like 3.1 for example, Rob Peck's book &quot;Programmer's Guide to the Amiga&quot;. The Amiga ROM Kernel manuals aka RKMs like Libraries (3rd edition), Devices (), the AmigaDOS manual (3rd edition) and the Style Guide may have their uses. There are some reference examples from AmigaMail and Devcon notes (available again on an Amiga developers CD 2.1). 

For Arexx then &quot;The Amiga Programmer's Guide to ARexx&quot; by Eric Giguere, which was published by Commodore is useful as well as an &quot;Arexx Cookbook&quot;.

Curly brackets missing - try SHIFT + ALT + 7 or 0.


* Beginners C Guide [http://www.iu.hio.no/~mark/CTutorial/CTutorial.html C Tutorial], 
* [http://thecguru.com/ C for beginners],
* [http://fresh2refresh.com/c/c-basic-program/ C programming basics] for students, 
* [https://www.edx.org/courses Free Online course] from American Universities 
* Reference Amiga [http://amigadev.elowar.com/ API reference].


* AROS based c source can be found [[Aros/Developer/Docs/Examples|here]] and lots of example code can be found inside [https://github.com/aros-development-team AROS sources] themselves and from the contrib section of the archives from [https://github.com/aros-development-team/contrib Aros site], and study the AROS applications source code, e.g. the test programs from the Tests drawer (folder/directory). Take a look at the code of some smaller AROS programs might be a better and more up to date 

When you upload your builds, please write the architecture (like i386-aros, x86_64-aros, armPi-64 etc.) in the archive name 
and it is also advisable to write in the field &quot;Requirements&quot; what ABI (ABIv1 or for PC forks ABIv11 or ABIv0) 


===Compiling C/C++ Code===

Native, although we have a IDE Integrated Development Environment (Murks), it does lack a debugger. Whilst others use a combination of a text editor and shell to edit code. Most though use an AROS hosted on Linux to take advantage of the better GCC tools like GDB and various IDEs.

Open shell - its a menu option at the top left of Wanderer (desktop). Or by using the right Win key and w (or F12 and w) within the directory with the source code. Type in
 sh 
to change the amiga shell into a unix shell. You can then type in ls (unix equivalent to amiga dir). Take a look [http://en.wikibooks.org/wiki/Linux_commands here] for more commands.

For a single file program-name.c or program-name.cpp
 gcc -o program-name program-name.c  
or 
 g++ -o program-name program-name.cpp
or
 g++ -o test -Wall -g main.cc texturelib.cpp xmodelib.cc -lsdl -lgl

To close the shell, click on the top left-hand corner to close (twice). Once to get back the aros shell and then again to close finally. Use [http://freshmeat.net/projects/cksfv/ cksfv] as a test.

Some source code requires the addition of Amiga API libraries, like dos, which you can flag at the compile time as 
 gcc -o julia.exe julia.c -ldos

For DOS use -ldos as example and if you are compiling mui codes it will be -lmui or intuition -lintuition. Other missing symbols are due to linker libraries being necessary for linking in functions that aren't in the standard C libraries. For example some source code would need added

 -lz or -lm or -lpng or -larosc etc.

use this in unix line command mode to search for 'search-item' in many .c files (*.cpp for c++, etc.)
 grep -l 'search-item' *.c

If the program is not executable, try using parameter fno-common 

&quot;Delete #?.o&quot;? Or if you are using abcshell then &quot;rm *.o&quot;


:''More information: [[Aros/Developer/Porting software]]''


=== How to make Apps have AROS 64-bit specific support code ===

[http://www.aros.org/cs/documentation/developers/app-dev/portable.php Portable code] 

AROS64 already uses 64bit addressing, it just doesn't setup the MMU for more than 4GB physical memory currently.
When porting software to AROS64 it is &quot;mostly&quot; a case of converting ULONG's that are used to store pointers, into IPTR's instead, etc. Another quirk, is making sure items on the stack are the correct size by using the STACKED attribute for them. 

* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.

compiling mui stuff for aros setting -std=gnu99 is necessary, had -std=c99 usually 
A MUI application most likely needs only the HOOKPROTOxxx SDI macros. They are compatible with AROS, only the attributes (hook, object attribute) must be given in the right order.

crash which suggest memory corruption. From my experience porting from 32-bit to 64-bit these kinds of errors can happen if a pointer is passed somewhere via ULONG variable. Then half of the pointer is cut.

To generate this error, please run AROSBootstrap with -m 1024. This will allocate heap to 64-bit address space which will make these errors immediatelly visible. These types of crashes are hard to debug. Disabled as little code as possible to stop corruption from occurring and then try to read from the code where it can be broken

Crashing in tslf_freevec is another symptom of memory corruption and these memory corruptions will manifest differently on different setups.


==Coding conventions==

As the AROS core source is a shared developer experience, there are rules regarding structure and style. When it comes to your creating your own app and coding, the structure and style should be your own, i.e. you should enjoy what you do and do it so that you can understand what is going on.

===Layout===

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
static void 1st_function()
{
    program
    exit(0);    
}

int main(void)
{
    1st_function();
    2nd_function();
    3rd_function();
    return 0;
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;

struct Screen * openscreen(void);
struct Window *openwindow(struct Screen *screen, const char *title, LONG x, LONG y, LONG w, LONG h);

VOID 1st_function();
VOID 2nd_function();

int main(int argc, char **argv)
{
    program
    return 0;
} /* main */

VOID 1st_function()
{

}

VOID 2nd_function()
{

}
&lt;/syntaxhighlight&gt;

===General style===

This code is used by many people and therefore you should keep some things in mind when you submit source code:

* Keep things simple 
* Keep the source clean 
* Always know what you are doing, if not flag it and describe what needs to be done... 
* Explain clearly/simply what you are doing 
* Remember that you write code once but that it is read many times by many people

===Comments===

AROS uses some of the comments in the source to generate the documentation. Therefore it's necessary to keep a certain format so the tools can find their information. Other comments are ignored but they should explain what you thought when you wrote the code. If you really can't think of an explanation, then don't write the code a second time like this:

&lt;pre&gt;
/* This adds 1 to t */
t ++;
&lt;/pre&gt;

What we think of is this:

&lt;pre&gt;
/* Go on with next element */
t ++;
&lt;/pre&gt;

===Formatting===

This is only '''IMPORTANT''' if you are going to work on the core AROS code or contrib but not applications which may reside outside like on AROS Archives or other websites.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
{
    /* a */
    struct RastPort * rp;
    int               a;

    /* b */
    rp = NULL;
    a  = 1;

    /* c */
    if (a == 1)
        printf (&quot;Init worked\n&quot;);

    /* d */
    if
    (
        !(rp = Get_a_pointer_to_the_RastPort
            (
                some
                , long
                , arguments
            )
        )
    ||
        a &lt;= 0
    )
    {
        printf (&quot;Something failed\n&quot;);
        return FAIL;
    }

    /* e */
    a = printf (&quot;My RastPort is %p, a=%d\n&quot;
        , rp
        , a
    );

    return OK;
}
&lt;/syntaxhighlight&gt;

Looks ugly, eh ? :-) Ok, here are the rules:

&lt;pre&gt;
If several lines contain similar code, put similar things below each other (see a and b);
Put spaces between operands and operators
Put braces {}, brackets [] and parentheses () below each other (d) if there is much code between. 
Brackets and parentheses may be in one line if the code between is small (c)
Indent by 4 Spaces. Two indent levels may be abbreviated by one tab.
&lt;/pre&gt;

'''Before committing please normalize the indentation - if you have a mixture of tabs and spaced - please always use spaces, 1 tab = 4 spaces.'''

The reasons for this are:

# While some editors can use an arbitrary sizes for tabs, it's a bit complicated to tell another editor which tab size was used by the one used to write the code. 
# Most code in AROS was written this way and your code should look like the rest. 
# You can print this code on any printer without special tools to &quot;fix&quot; the tabs. 
# Most editors have smart tabs which do exactly this. If your editor doesn't, write a bug report.

If you have a function with many arguments (d, e) you should put the parentheses in lines of their own and each argument in one line (d) or put the first argument behind the opening parentheses (e) and each following argument in a line of its own with the comma in front. The closing parentheses is in a line of its own and aligned with the beginning of the expression (i.e. the a and not the opening parentheses or the printf()).

Use a single blank line to separate logical blocks. Large comments should have a blank line before and after them, small comments should be put before the code they explain with only one blank line before them.

If you see any TABS in AROS core sources then the suggestion is to &quot;detab the file and commit that separately&quot; either before or afterwards from making functionality changes. Make two commits instead of one. This makes it easier for others to see the real changes instead of having to dig through multiple lines of irrelevant diffs.

===Eliminating Global Variables===

i.e. pass variables to functions (local scope) or classes making it easier to track and debug your code.

Any time you find that you need a particular thing in 'a lot of different places', chances are that all those places are conceptually related, and so you can create a class, a namespace, a function, or some other higher-level organizational unit to represent that relationship. This makes the program easier to understand.

Bad Designs

* All variables are global. 
* There are no standalone functions, only sub-procedures which act on the global variables. 
* Every sub-procedure is at least 500 lines to several thousand 
* Every sub-procedure has more than one task to perform 
* Copy-paste is preferred to writing methods, AND subtle changes are made in the middle of the code

Good Designs

* structure program into functions (C or basic) - top-down procedural approach 
* put in class(es) (freepascal or C++) - the object is fixed and you use methods to access the object

&lt;pre&gt;
 class String_List
 {
 private:
 list&lt;string&gt; m_List;  // member
 public:
 void read_strings() { /* read strings into m_List */ }
 void print_strings() { /* write contents of m_List to stdout */ }
 void sort_strings() { /* sort contents of m_List */ }
 void sort_strings_reverse() { /* reverse-sort contents of m_List */ }
 void unique_strings() { /* remove duplicate strings */ }
 };

 int main()
 {
 String_List myList;  // local
 myList.read_strings();
 myList.sort_strings();
 myList.print_strings();
 myList.sort_strings_reverse();
 myList.print_strings();
 myList.unique_strings();
 myList.print_strings();
 return 0;
 }
&lt;/pre&gt;

This way it is very easy to replace the list with new list for debugging purposes, or replacing the methods without replacing the list, when you want different results. You only have to replace the content of the local variables.

 So create the structure that matches your data (linked lists, trees, arrays, etc.) and what to do with them (sorting, searching, etc.)

&lt;pre&gt;
.h usually contain #define #include typedef enum struct extern screen and window definitions (data structures)
.c should contains functions and algorithms
&lt;/pre&gt;

One way to look at it is that menu headings act as the .c file and sub-menu headings as functions.

When you start a project, you place a couple of declarations in the include file. As the project continues, you place more and more declarations in the include file, some of which refer to or contain previous declarations. Before you know it, you have a real mess on your hands. The majority of your source files have knowledge of the data structures and directly reference elements from the structures.
Making changes in an environment where many data structures directly refer to other data structures becomes, at best, a headache. Consider what happens when you change a data structure.

Use good variables names to help clarify code and only comment when you need to explain why a certain programming approach was made.

You're Refactoring Legacy Code, you see a global, you want to get rid of it. How do you do this?

Exactly what to do depends on how the global is used. The first step is to find all uses of the global throughout the code, and get a feel for what the significance of the variable is and how it relates to the rest of the program. Pay particular attention to the &quot;lifetime&quot; of the variable (when it gets initialized, when it is first used, when it is last used, how it gets cleaned up). Then, you will probably make the global a data member of a class (for OO languages), or you will write some get/set functions. Converting to the Singleton Pattern is common, but you may discover that it makes more sense for the data element to be a member of an existing singleton, or maybe even an instance variable.

# Create a basic read method, either as a class or a global function. Replace all reads with the access method, but leave the variable defined as a global.
# Review each of the writes to the method and extract action functions one at a time. Unless two operations are coded identically in the original code, extract each write access separately.
# Change the variable scope from global to local.
# Analyze similar action functions to determine if any can be merged, i.e., there are no functional differences in the results of the function, just differences in the implementation details.
# Review the calls to the read method and see if a more complex functionality should be applied. Follow the approach for writes and unless implementations are identical, create separate access functions. 
# Analyze the access functions for duplication.

As returning variables by &quot;passing by value&quot; are forgotten, so &quot;passing by reference&quot; is often used instead. The reference is a pointer to the variable so the value is remembered when returned.

Alternatives

* Hidden Globals
* Singleton Pattern
* Database or TupleSpace
* Context Object 
* Dependency Injection 
* Stateful Procedures


==AROS/AmigaOS APIs and Docs==

&lt;pre&gt;
Library:
   - Private data structure
   - Many public access methods

Device:
   - Private data structure
   - Two (BeginIO/AbortIO) access methods

Resource:
   - Public data structure
   - *NO* access methods
&lt;/pre&gt;

And, being Amiga OS-compatible, there are exceptions to all of these.


===System Libraries===

The [http://developers.aros.org/ AROS Guide To Libraries] can be used as a guide to individual commands and old Dev Docs are used in application programming.

Amiga/Aros styles libraries are very different from windows and linux libs. Typical .so/dll libraries are foreign to most Amiga-like OS 


*[[Aros/Developer/Docs/Libraries/AROSC|arosc.library]]
*[[Aros/Developer/Docs/Libraries/AmigaGuide|amigaguide.library]]
*[[Aros/Developer/Docs/Libraries/ASL|asl.library]]
*[[Aros/Developer/Docs/Libraries/Bullet|bullet.library]]
*[[Aros/Developer/Docs/Libraries/BSDsocket|bsdsocket.library]]
*[[Aros/Developer/Docs/Libraries/CAMD|camd.library]]
*[[Aros/Developer/Docs/Libraries/Codesets|codesets.library]]
*[[Aros/Developer/Docs/Libraries/CGFX|cybergraphics.library]]
*[[Aros/Developer/Docs/Libraries/CGXVIDEO|cgxvideo.library]]
*[[Aros/Developer/Docs/Libraries/Commodities|commodities.library]]
*[[Aros/Developer/Docs/Libraries/DataTypes|datatypes.library]]
*[[Aros/Developer/Docs/Libraries/DiskFont|diskfont.library]]
*[[Aros/Developer/Docs/Libraries/DOS|dos.library]]
*[[Aros/Developer/Docs/Libraries/Exec|exec.library]]
*[[Aros/Developer/Docs/Libraries/Expansion|expansion.library]]
*[[Aros/Developer/Docs/Libraries/FreeType2|freetype.library]]
*[[Aros/Developer/Docs/Libraries/GadTools|gadtools.library]]
*[[Aros/Developer/Docs/Libraries/Graphics|graphics.library]]
*[[Aros/Developer/Docs/Libraries/Icon|icon.library]]
*[[Aros/Developer/Docs/Libraries/Identify|identify.library]]
*[[Aros/Developer/Docs/Libraries/IFFParse|iffparse.library]]
*[[Aros/Developer/Docs/Libraries/Intuition|intuition.library]]
*[[Aros/Developer/Docs/Libraries/Keymap|keymap.library]]
*[[Aros/Developer/Docs/Libraries/Layers|layers.library]]
*[[Aros/Developer/Docs/Libraries/Locale|locale.library]]
*[[Aros/Developer/Docs/Libraries/LowLevel|lowlevel.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEESingBas|mathieeesingbas.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEEDoubBas|mathieeedoubbas.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEESingTrans|mathieeesingtrans.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEEDoubTrans|mathieeedoubtrans.library]]
*[[Aros/Developer/Docs/Libraries/Mathtrans|mathtrans.library]]
*[[Aros/Developer/Docs/Libraries/MUIMaster|muimaster.library]]
*[[Aros/Developer/Docs/Libraries/Partition|partition.library]]
*[[Aros/Developer/Docs/Libraries/PopUpMenu|popupmenu.library]]
*[[Aros/Developer/Docs/Libraries/OOP|oop.library]]
*[[Aros/Developer/Docs/Libraries/Regina|regina.library]]
*[[Aros/Developer/Docs/Libraries/Reqtools|reqtools.library]]
*[[Aros/Developer/Docs/Libraries/RexxSysLib|rexxsyslib.library]]
*[[Aros/Developer/Docs/Libraries/ScreenNotify|screennotify.library]]
*[[Aros/Developer/Docs/Libraries/TTEngine|ttengine.library]]
*[[Aros/Developer/Docs/Libraries/Thread|thread.library]]
*[[Aros/Developer/Docs/Libraries/Utility|utility.library]]
*[[Aros/Developer/Docs/Libraries/Xadmaster|xadmaster.library]]
*[[Aros/Developer/Docs/Libraries/Workbench|workbench.library]]
*[https://github.com/aros-development-team/AROS/commit/c82e86b8480277998014cc327b56c7664023a52f ClassAct Reaction boopsi class]


===AROS Subsystems===

# [[Aros/Developer/Zune|Zune MUI compatible GUI]]
# [[Aros/Developer/AROSAppPackages|AROS Application Packages]]
# AHI Audio Drivers - [[Aros/Developer/AHIDrivers|Usage]]/[[Aros/Developer/AHIDriversDev|Development]]
# AROSTCP Sana2 Network Interface Drivers - [[Aros/Developer/NICDrivers|Usage]]/[[Aros/Developer/NICDriversDev|Development]]
# [[Aros/Developer/AmiSSL|AmiSSL]]
# gfx.hidd/cybergraphics Video Drivers - [[Aros/Developer/GfxDrivers|Usage]]/[[Aros/Developer/GfxDriversDev|Development]]
# IO Device Drivers - [[Aros/Developer/IODeviceDrivers|Usage]]/[[Aros/Developer/IODeviceDriversDev|Development]]
# USB Device Drivers - [[Aros/Developer/USBDrivers|Usage]]/[[Aros/Developer/USBDriversDev|Development]]
# PCI Device Drivers - [[Aros/Developer/PCIDrivers|Usage]]/[[Aros/Developer/PCIDriversDev|Development]]
# [http://www.libsdl.org/ SDL] [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2013&amp;pid=13333#post_13333 SDL2 coding usage], [https://github.com/search?q=repo%3Aaros-development-team%2Fcontrib%20SDL2&amp;type=code SDL2 commits], [https://github.com/aros-development-team/contrib/commit/c62c3c425c35bac19dadc23be092b0b13a66c76c SDL3 initial commit], []
# [[w:Gallium3D|Gallium 3D]] [http://www.mesa3d.org/ openGL aka Mesa] - [[Aros/Developer/OpenGL|Usage]]/[[Aros/Developer/OpenGLDev|Development]] [http://www.swiftless.com/opengltuts.html Swfitless]
# A small subset of GTK2 through [http://sourceforge.net/projects/gtk-mui/ MUI-GTK] 
# Cairo 2D Engine - [[Aros/Developer/Cairo|Usage]]/[[Aros/Developer/Cairo|Development]]
# [[Aros/Developer/Scalos|Scalos desktop API and plugin modules]]
# [[Aros/Developer/VHI|VHI video driver]]


====HIDDs====

*[[Aros/Developer/Docs/HIDD/HIDDClass|hiddclass.hidd]]
*[[Aros/Developer/Docs/HIDD/Graphics|graphics.hidd]]
*[[Aros/Developer/Docs/HIDD/VesaGfx|vesagfx.hidd]]
*[[Aros/Developer/Docs/HIDD/ATI|radeon.hidd]]
*[[Aros/Developer/Docs/HIDD/NVidia|nvidia.hidd]]
*[[Aros/Developer/Docs/HIDD/Nouveau|nouveau.hidd]]
*[[Aros/Developer/Docs/HIDD/Kbd|kbd.hidd]]
*[[Aros/Developer/Docs/HIDD/Mouse|mouse.hidd]]
*[[Aros/Developer/Docs/HIDD/i2c|i2c.hidd]]
*[[Aros/Developer/Docs/HIDD/IRQ|irq.hidd (deprecated)]]
*[[Aros/Developer/Docs/HIDD/PCI|pci.hidd]]
*[[Aros/Developer/Docs/HIDD/PCIPC|pcipc.hidd]]
*[[Aros/Developer/Docs/HIDD/Serial|serial.hidd]]
*[[Aros/Developer/Docs/HIDD/Thunderbolt|thunderbolt.hidd]]
https://github.com/aros-development-team/AROS/commit/4f02ea691799aff3a01f60cfa5f9182c82fc57a8

HIDD are used for device/peripheral low level hardware support drivers. The HIDD system is split up into a collection of classes with a strict inheritance hierarchy. A HIDD class implements a device driver for a single device or in rare cases a group of devices and provides an interface for other programs and devices to access.
      
In order to maintain portability of interfaces across a wide range of hardware this interface will in general not present the raw interface to the underlying hardware. Instead it will present a generic interface that describes many different hardware implementations. This allows for the best reuse of both interfaces and code.

HIDD API is heavyweight though. You need to open a HIDD library, open oop.library, instantiate an object (even if there's no object); and object calls are more costly compared to plain library calls.


Basically your task is to implement a subclass of hidd.ata.bus for your hardware. just implementing the XXXATA__Hidd_ATABus__xxxxxx methods for the Amiga chipset - and appropriate versions of the interface_xxx.c file(s). pretty much everything in probe.c could be ignored - just write a replacement scan for relevant amiga devices and store whatever info you need in the bus data? only the &quot;SUPPORT_LEGACY&quot; blocks might be related.

You do not need to depend on PCI API. PCI is just a way to discover the hardware on PCs, etc. 
&lt;hidd/pci.h&gt; includes (at some depth) &lt;interface/HW.h&gt;, which defines IID_HW. This comes from the 'generic' HIDD class in: 
 rom/hidds/hidd/hiddclass.conf
did not split up HIDD and HW because they are always used in pair. It's the same as hidd/pci.h bringing definition for: PCI, PCIDriver and PCIDevice. PCI is actually PCIHW, just the name was not changed for backwards compatibility reasons. HW is a 'hub' where HIDD instances plug in.

ATA HIDD aoHidd_ATABus_Use32Bit value is completely ignored unless ata.device first detects correct command line parameter.
Yes. Unfortunately I was unable to find any comment in code or svn history with explanations. Looked  at Linux source, there 32-bit PIO is also controller driver's property. Some of them enable it, some don't.

Actually, switching the default to ON should be safe. ata.device is fail-safe at this because during IDENTIFY command it validates upper 16  bits,  and  if they appear to be zeroes in all 128 longwords, then 32-bit mode is switched off. But, nevertheless, I know how tricky hardware can be, so I decided not to change original behavior. If  you think it's wrong in some cases, then it's possible to add one more  attribute  like  aHidd_ATABus_Default32Bit. If set to YES, then  this means that 32-bit PIO is safe to use by default.


====Devices====

*[[Aros/Developer/Docs/Devices/ATA|ata.device]]
*[[Aros/Developer/Docs/Devices/Console|console.device]]
*[[Aros/Developer/Docs/Devices/Narrator|narrator.device]]
*[[Aros/Developer/Docs/Devices/Printer|printer.device]]
*[[Aros/Developer/Docs/Devices/Trackdisk|trackdisk.device]]
*[[Aros/Developer/Docs/Devices/AmberRAM|amberram.device]]
*[[Aros/Developer/Docs/Devices/Timer|timer.device]]
*[[Aros/Developer/Docs/Devices/|.device]]

The Amiga used [[Aros/Developer/Docs/Devices|Devices]] to communicate with [http://aros-exec.org/modules/newbb/viewtopic.php?start=0&amp;topic_id=3475&amp;viewmode=flat&amp;order=ASC additional hardware]. AROS has replaced these hardware devices with hidd equivalents but some are still retained for backwards compatibility.

Local libraries/devices/handlers,etc. are supposed to override the ones in ROM if their version is higher than the one in ROM.

Here is the list of commands exec default: 
{| class=&quot;wikitable&quot;
| CMD_CLEAR
|  Purge the buffer of the device
|----
| CMD_READ
|  Playback Control
|----
| CMD_STOP
|  Stopped the activity of the device
|----
| CMD_FLUSH
|  Empty the queue of commands
|----
| CMD_RESET
|  Reset a device
|----
| CMD_WRITE
|  Playback Control
|----
| CMD_INVALID
|  Create an error
|----
| CMD_UPDATE
|  Gets updated device
|----
| CMD_START
|  Will restart the device
|----
|}

While most other &quot;stuff you communicate with&quot; in AmigaOS are devices &lt;ref&gt;AMIGA ROM Kernel Reference Manual: Devices, 3rd Edition. Commodore-Amiga, Inc. Addison-Wesley, 1991. {{ISBN|0-201-56775-X}}&lt;/ref&gt; that share a [http://gega.homelinux.net/AmigaDevDocs/ common base interface]. [[Aros/Developer/Docs/Devices1.3|OS 1.3 Device Drivers]].


====Handlers====

:[[Aros/Developer/Docs/Handlers/Pipe|pipe.handler]]
:[[Aros/Developer/Docs/Handlers/Port|port.handler]]
:[[Aros/Developer/Docs/Handlers/SFS|sfs.handler]]
:[[Aros/Developer/Docs/Handlers/FAT|fat.handler]]
:[[Aros/Developer/Docs/Handlers/PFS|pfs.handler]]
:[[Aros/Developer/Docs/Handlers/NTFS|fuse.handler]]
:[[Aros/Developer/Docs/Handlers/FFS|ffs.handler]]

filesystem handlers have their own separate system consisting of completely differently structured messages that dos.library use to pass requests (for things like reading, writing, getting directory contents etc.) to them. AROS originally went with implementing filesystem handlers as devices, which might arguably be more consistent with the rest of the AmigaOS API but which is quite incompatible with AmigaOS itself. However, it made it far harder to port filesystems and the gains were comparatively small, and so there's been a long standing goal of fixing this incompatibility. It has now, June 2011, been reintroduced to all AROS flavors.

are argstr and argsize valid for the handler startup environment?
DOS/RunHandler() calls DOS/CreateNewProcTags(), and then CallEntry() (in rom/dos/exit.c) to start the handler, so yes, argstr and argsize are *present* in the call signature of the handler.

Granted, argstr will be NULL and argsize 0, but those values *are* passed to the handler function using:

&lt;pre&gt;
AROS_UFC3(ULONG, entry,
                         AROS_UFCA(STRPTR, argptr, A0),
                         AROS_UFCA(ULONG, argsize, D0),
                         AROS_UFCA(struct ExecBase *, SysBase, A6));
&lt;/pre&gt;

Creating your own [without the whole build tree http://pagesperso-orange.fr/franck.charlet/temp/radeon.zip] and then  
&lt;pre&gt;
make stub
make
make install
&lt;/pre&gt;

SFS has two Root blocks, one at the start and one at the end of the disk. The Root blocks both contain the same information.  They hold various information about the disk structure and have the locations of some important blocks used by the filesystem.  

The Root ObjectContainer contains the Root directory Object. The name of this Object is the name of the volume. It is identical to a normal directory Object.

The Bitmap is used to keep track of free space. Each bit in a bitmap represents a single block. A set bit indicates a free block and a cleared bit a used block.

AdminSpaceContainers are used to keep track of space which has been reserved for storing administration blocks. Only the Bitmap, the Root blocks and the actual data stored in files aren't stored in administration space. Administration space is allocated in chunks of 32 blocks at a time. A single AdminSpaceContainer can hold information about a large number of such areas each of which has its own little bitmap of 32 bits.

Extents are stored in a B-Tree. The Root block holds a pointer to the root of the Extent B-Tree. Extents keep track of space in use by a specific file. Each fragment a file consists of has its own Extent. Extents are in a double linked list. The list can be used to locate the next or previous fragment of a file.

Below is the standard block header. This header is found before EVERY type of block used in the filesystem, except data blocks.  The id field is used to check if the block is of the correct type when it is being referred to using a BLCK pointer.  The checksum field is the SUM of all LONGs in a block plus one, and then negated. When applying a checksum the checksum field itself should be set to zero. The checking a checksum the checksum is okay if the result of the checksum equals zero. The ownblock BLCK pointer points to the block itself. This field is an extra safety check to ensure we are using a valid block.

Field	Type	Description
id	ULONG	The id field is used to identify the type of block we are dealing with. It is used to make sure that when referencing a block we got a block of the correct type. The id consist of 4 bytes and each blocktype has its own unique foure letter code.
checksum	ULONG	This field contains the sum of all longs in this block, plus one and then negated. The checksum can be used to check if the block hasn't been corrupted in any way.
ownblock	BLCK	Points to itself, or in other words, this field contains the block number of this block. This is yet another way to check whether or not a block is valid.

&lt;pre&gt;
struct fsBlockHeader {
    ULONG id;
    ULONG checksum;
    BLCK ownblock;
};
&lt;/pre&gt;
The algorithm to calculate the checksum of a block:
&lt;pre&gt;
ULONG calcchecksum(struct fsBlockHeader *block, LONG blocksize} {
    ULONG *data=(ULONG *)block;
    ULONG checksum=1;

    block-&gt;checksum=0;

    while(blocksize&gt;0) {
        checksum+=*data++;
        blocksize-=4;
    }

    return(-checksum);
} 
&lt;/pre&gt;

A Root block contains very important information about the structure of a SFS disk. It has information on the location and size of the disk, the blocksize used, locations of various important blocks, version information and some filesystem specific settings.

A SFS disk has two Root blocks; one located at the start of the partition and one at the end. On startup the filesystem will check both Roots to see if it is a valid SFS disk. If either one is missing SFS can still continue (although at the moment it won't).

A Root block could be missing on purpose. For example, if you extend the partition at the end (adding a few MB's) then SFS can detect this with the information stored in the Root block located at the beginning (since only the end-offset has changed).   Same goes for the other way around, as long as you don't change start and end point at the same time.

When a Root block is missing because the partition has been made a bit larger, then SFS will in the future be able to resize itself without re-formatting the disk.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
version	UWORD	The version of the filesystem block structure. You can check this field to identify what version of the filesystem your dealing with it and to see if you can handle this structure correctly. Don't try to interpret the disk's structure when this field contains an unknown version number!

sequencenumber	UWORD	Used to identify which Root block was written last in case the sequencenumber on both Root blocks don't match.
datecreated	ULONG	Creation date of this volume. This is the date when the disk was last formatted and will never be changed.

bits	UBYTE	Various settings, see below.
&lt;pre&gt;
pad1	UBYTE	Reserved, leave zero.
pad2	UWORD	Reserved, leave zero.
reserved1	ULONG[2]	Reserved, leave zero.
firstbyteh	ULONG	High 32-bits of a 64-bit number. This is the first byte of our partition relative to the start of the disk.
firstbyte	ULONG	Low 32-bits of a 64-bit number.
lastbyteh	ULONG	High 32-bits of a 64-bit number. This is the last byte (exclusive) of our partition relative to the start of the disk.
lastbyte	ULONG	Low 32-bits of a 64-bit number.
totalblocks	ULONG	The total number of blocks this partition consists of.
blocksize	ULONG	The size of a block of this partition.
reserved2	ULONG[2]	Reserved, leave zero.
reserved3	ULONG[8]	Reserved, leave zero.
bitmapbase	BLCK	Block number of the start of the Bitmap.
adminspacecontainer	BLCK	Block number of the first AdminSpaceContainer.
rootobjectcontainer	BLCK	Block number of the ObjectContainer which contains the root of the disk (this is where the volume name is stored).
extentbnoderoot	BLCK	Block number of the root of the Extent B-Tree.
reserved4	ULONG[4]	Reserved, leave zero.
&lt;/pre&gt;

&lt;pre&gt;
struct fsRootBlock {
  struct fsBlockHeader bheader;
  UWORD version;
  UWORD sequencenumber;
  ULONG datecreated;
  UBYTE bits;
  UBYTE pad1;
  UWORD pad2;
  ULONG reserved1[2];
  ULONG firstbyteh;
  ULONG firstbyte;
  ULONG lastbyteh;
  ULONG lastbyte;
  BLCK  totalblocks;
  ULONG blocksize;
  ULONG reserved2[2];
  ULONG reserved3[8];
  BLCK  bitmapbase;
  BLCK  adminspacecontainer;
  BLCK  rootobjectcontainer;
  BLCK  extentbnoderoot;
  ULONG reserved4[4];
};
&lt;/pre&gt;

AdminSpaceContainers are used to store the location and bitmap of each administration space. The AdminSpaceContainers are located in a double linked list and they contain an array of fsAdminSpace structures.  There is one fsAdminSpace structure for every administration space on disk.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
next	BLCK	The next AdminSpaceContainer, or zero if it is the last in the chain.
previous	BLCK	The previous AdminSpaceContainer, or zero if it is the first AdminSpaceContainer.
bits	UBYTE	The number of bits in each in the bits ULONG in the fsAdminSpace structure.
pad1	UBYTE	Reserved, leave zero.
pad2	UWORD	Reserved, leave zero.
adminspace	struct fsAdminSpace	An array of fsAdminSpace structures. The size of the array is determined by the current blocksize.
&lt;pre&gt;
struct fsAdminSpaceContainer {
  struct fsBlockHeader bheader;
  BLCK next;
  BLCK previous;
  UBYTE bits;
  UBYTE pad1;
  UWORD pad2;
  struct fsAdminSpace adminspace[0];
};
&lt;/pre&gt;
Field	Type	Description
space	BLCK	The first block of an administration space.
bits	ULONG	A small bitmap which is used to determine which blocks in an administration space are already in use. The number of bits in this bitmap is determined by the bits field in the AdminSpaceContainer.
&lt;pre&gt;
struct fsAdminSpace {
  BLCK  space;
  ULONG bits;
};
&lt;/pre&gt;

The fsBitmap structure is used for Bitmap blocks. A bitmap block is used to keep track of which space is in use and which isn't for a particular area of a disk.  All bitmap blocks together keep track of the free space for an entire disk. The location of the first bitmap block is known and all other bitmap blocks are stored in order after the first one.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
bitmap	ULONG	An array of ULONG's.  These hold the actual information on which blocks are in use and which aren't.
&lt;pre&gt;
struct fsBitmap {
    struct fsBlockHeader bheader;
    ULONG bitmap[0];
};
&lt;/pre&gt;
Each bit in a bitmap block (except for the block header) represents a single block. If the bit is set than the block is free, and if the bit is clear then it is full. The first ULONG in the bitmap area of the first bitmap block represents blocks 0 through 31 on the disk. Bit 31 of this ULONG is block 0, 30 is block 1, and so on. Bit 0 of the first ULONG represents block 31.

Below is a table to clarify how bitmaps work even further. The first column is the bitmap block number, the second column is the number of the ULONG in the bitmap array. The third column is the bit number in this ULONG, and the last column is the block which this specific bit, in this specific bitmap block represents.

We'll assume here that a bitmap block has room for 120 ULONG's (meaning there is room for storing 32 * 120 bits).

&lt;pre&gt;
Bitmap block	ULONG number	Bit number	Block represented
1 (first)	0	31	0
1	0	30	1
...	...	...	...
1	0	1	30
1	0	0	31
1	1	31	32
...	...	...	...
1	2	31	64
1	2	30	65
...	...	...	...
1	119	0	3839
2	0	31	3840
2	0	30	3841
...	...	...	...
&lt;/pre&gt;
The last bitmap block doesn't need to be completely used. The unused bits (which belong to blocks which do not exist) all have to be clear, to indicate that these blocks are in use.

The fsObjectContainer structure is used to hold a variable number of fsObjects structures (Objects) which have the same parent directory. Each ObjectContainer must contain at least one Object. If there is space in the ObjectContainer not used by the variable number of Objects then that space is zero filled. Objects always start at 2-byte boundaries, which means sometimes a padding byte is inserted between two Objects.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
parent	NODE	The node number of the parent Object, or 0 if this object has no parent (which is only the case for the Root directory).
next	BLCK	The next ObjectContainer belonging to this directory, or zero if it is the last in the chain.
previous	BLCK	The previous ObjectContainer belonging to this directory, or zero if it is the first ObjectContainer in this directory.
object	struct fsObject	A variable number of fsObject structures. The number of structures depends on the individual sizes of each fsObject structure and the blocksize. These structures are located directly after each other with at most 1 byte of padding between them to get the structures aligned on a 2 byte boundary.
&lt;pre&gt;
struct fsObjectContainer {
    struct fsBlockHeader bheader;
    NODE parent;
    BLCK next;
    BLCK previous;
    struct fsObject object[0];
}; 
&lt;/pre&gt;

fsHashTable is the structure of a HashTable block. It functions much like the hash table found in FFS user directory blocks, except that it is stored in a separate block. This block contains a number of hash-chains (about 120 for a 512 byte block). Each hash-chain is a chain of Nodes. Each Node has a pointer to an Object and a pointer to the next entry in the hash-chain.  Using such a hash-chain you can locate an object quickly by only knowing its name.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
parent	NODE	The node number of the directory Object this HashTable block belongs to.
hashentry	NODE	An array of Nodes. Each Node represents the start of a hash-chain (singly linked). A hash-value is calculated using the name of a file or directory, and this value determines in which chain the Object is linked. If there are no entries in a hash-chain then the hashentry value is zero.
&lt;pre&gt;
struct fsHashTable {
    struct fsBlockHeader bheader;
    NODE parent;
    NODE hashentry[0];
};
&lt;/pre&gt;
To calculate the hash-value using a name of an Object as input use these routines:
&lt;pre&gt;
UWORD calchash(UBYTE *name) {
    UWORD hash=0;
    /* Calculates a hash value over the passed in string.
       The end of the string can be either a NUL byte or a
       slash. The hash function is the same as the one
       used in FastFileSystem set to international mode. */
    while(name[hash]!=0 &amp;&amp; name[hash]!='/') {
        hash++;
    }
    while(*name!=0 &amp;&amp; *name!='/') {
        hash=hash*13+upperchar(*name++);
    }

    return((UWORD)(hash % (UWORD)((blocksize-sizeof(struct fsHashTable))&gt;&gt;2)));
}
UBYTE upperchar(UBYTE c) {
    if((c&gt;=224 &amp;&amp; c&lt;=254 &amp;&amp; c!=247) || (c&gt;='a' &amp;&amp; c&lt;='z')) {
        c-=32;
    }
    return(c);
}
&lt;/pre&gt;

The BNodeContainer is used to store B-Trees. Currently only one B-Tree is in use by this filesystem and it is used to store the location of file data. The fsBNodeContainer structure contains two other structures. The fsBlockHeader structure and the BTreeContainer structure.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
btc	struct BTreeContainer	Contains information about the B-Tree and its nodes contained in this block.
&lt;pre&gt;
struct fsBNodeContainer {
    struct fsBlockHeader bheader;
    struct BTreeContainer btc;
}; 
&lt;/pre&gt;


First try and locate the Root block. It should start with &quot;ROOT&quot;.  SFS has two of these, one at the start of the partition and one at the end.  One of the fields contains the block size, which will be the size of all important SFS blocks.

The root block has the root object container, which contains information about files and directories in the root directory.  The object 
containers basically hold one or more smaller structures that represent files and directories.  Scanning them all should give you a list of 
files and directories.

The root block also has the root of the Extent B-Tree.  This is a standard B-Tree structure (not a binary tree) that is used commonly in 
all kinds of system, you can read about how they work on Wikipedia if needed.  The B-Tree holds the information about *where* all the data is 
located for your files.

To recover your files, I'd do this:

* Find one of the root blocks, if not present, then figure out the block size your disk was using, and scan every block in turn to see if it 
looks like an ObjectContainer (check the fsBlockHeader's ID, check if the ownblock number is equal to the block you are currently scanning, 
and check its checksum).  So if you currently have block 12, and you see a block with the correct id, and ownblock = 12 and its checksum is good, 
then that's probably a valid ObjectContainer.

* With all the ObjectContainers found, you can extract filenames and directory names from these, but also the number of their first data 
block (in the field data) and the file size.  For small files (less than blocksize) this data block will be enough to recover the data.
For larger files, you might be lucky and all the remaining blocks are found after the first one (if the file was defragmented).  You can't be
sure of that though so...

* For larger files, you need to find all the BNodeContainers.  You could scan these in the same way you found all the ObjectContainers (look for 
blocks with the correct id, ownblock number and checksum). 

* With all the BNodeContainers found, you can try looking up the first data block of a file in the B-Tree structure.  This is a bit complicated 
-- the B-Tree consists of non-leaf nodes (blocks that only contain pointers to other B-Tree blocks), the isLeaf flag indicates this.  Or it 
can be a B-Tree leaf block.  The leaf blocks contain extra information per entry (see https://hjohn.home.xs4all.nl/SFS/extents.htm)
&lt;pre&gt;
struct fsExtentBNode {
     ULONG key;
     ULONG next;
     ULONG prev;
     UWORD blocks;
};
&lt;/pre&gt;

The key should be a block of a file (the first of a range), that is 1 to 65535 block long (depending the &quot;blocks&quot; field).  If the file is split 
up into more parts, then &quot;next&quot; will contain block number of the next range of blocks.  You need to look this up again in the B-Tree 
structure to find out how large it is. 

You can for the most part ignore the other structures (bitmap, admin containers).  The fsObjects and B-tree containers is what you'll need to 
recover the data. 


====Resources====

&lt;pre&gt;
rom/storage/mmakefile.src 
rom/storage/storage.conf 
rom/storage/storage_device.c 
rom/storage/storage_ids.c 
rom/storage/storage_init.c 
rom/storage/storage_intern.h 
rom/storage/storage_mount.c 
rom/storage/storage_unit.c
&lt;/pre&gt;

&lt;pre&gt;
rom/storage/includes/device.h 
rom/storage/includes/unit.h 
rom/storage/includes/volume.h 
rom/storage/storage_intern.h 
&lt;/pre&gt;

&lt;pre&gt;

&lt;/pre&gt;

*[[Aros/Developer/Docs/Resources/ACPI|acpi.resource]]
*[[Aros/Developer/Docs/Resources/Battclock|battclock.resource]]
*[[Aros/Developer/Docs/Resources/Bootloader|bootloader.resource]]
*[[Aros/Developer/Docs/Resources/Cia|cia.resource]]
*[[Aros/Developer/Docs/Resources/Filesystem|FileSystem.resource]]
*[[Aros/Developer/Docs/Resources/Hostlib|hostlib.resource]]
*[[Aros/Developer/Docs/Resources/Kernel|kernel.resource]]
*[[Aros/Developer/Docs/Resources/Misc|misc.resource]]
*[[Aros/Developer/Docs/Resources/Processor|processor.resource]]


==Debugging Code==

Please use the [http://sourceforge.net/tracker/?group_id=43586&amp;atid=439463 AROS Bug Tracker] if any issues are found.


GRUB Command line list

&lt;pre&gt;
sysdebug  
usbdebug - allows to see Poseidon's log in debug output
&lt;/pre&gt;


How do I get debugging out of InitResident ? If running i386 hosted on linux sysdebug=initresident on command line.
This  way  you can enable any of listed flags. sysdebug=all stands for &quot;everything&quot;


Have an executable (crosscompiled C++ code) which has 6 MB size on disk, but after loading it in memory, 250 MB RAM is taken. Any software that would split AROS executable into ELF part which would show actual size values?

 readelf -S executable

it will show you all sections in elf file, including sizes and requested alignment.

 objdump -h filename

That's will give you a quick overview of the sections and sizes. Ignore all the .debug.* sections. 
Would hazard a guess that you have a large .bss section. That's pretty common in C++.

Next step:

 nm—size-sort filename | grep ' [bB] '

The last few will be your biggest consumers. Would suggest -C to demangle the symbols... ;)


Suggest profiling the program (just use some printf's in the main loop for time spent in each part), it usually is quite easy to spot slow parts in games or apps.

If someone has '#define IPTR ULONG' somewhere. To see where that define is, redefine IPTR in the source code that fails, just above the line that fails, and the preprocessor will tell you where it was defined first.

===How to setup gdb with AROS/hosted===

Download AROS sources (AROS-xxxxxxxx-source.tar.bz2, where xxxxxxxx is the current date) and AROS contrib sources (AROS-xxxxxxxx-contrib-source) from 

Untar-bzip2 and cd to the unpacked archive directory.

 &gt; tar -xvjf AROS-xxxxxxxx-source.tar.bz2
 &gt; cd AROS-xxxxxxxx-source

Check the link to &quot;contrib&quot; (contrib-source) inside directory, e.g. correct like this:

 &gt; rm contrib
 &gt; ln -s ../AROS-xxxxxxxx-contrib-source.tar.bz2 contrib

Make sure you have the correct locale setting, otherwise compilation will fail at some point. See [http://aros.sourceforge.net/documentation/developers/compiling.php#setting-the-locale-to-iso8859 here] (or link below) for more on that. You might have to enter this:

 &gt; export LANG=&quot;en_US.ISO-8859-1&quot;

Now configure for a debug build - see &quot;./configure --help&quot; for more - here are two examples:

 &gt; ./configure—enable-debug=stack,modules,symbols
 
 &gt; ./configure—enable-debug=all

You may &quot;make&quot; now, or choose a separate directory for your build (e.g. for easy removal), for example if compiling for i386 architecture you could create a directory like this:

 &gt; mkdir linux-i386
 &gt; cd linux-i386
 &gt; ../AROS/configure—enable-debug=stack,symbols,modules

When done configuring you're ready to go:

 &gt; make

Building AROS takes some time - minutes on fast machines (e.g. 2.5&amp;nbsp;GHz quadcore), up to hours on slower machines.
The result will be AROS Linux hosted with gdb debugging enabled.

See aros.org documentation for more on compiling AROS, including more [http://aros.sourceforge.net/documentation/developers/compiling.php --enable-debug] options.


When finished, enter bin/linux-i386/AROS directory (replace &quot;linux-i386&quot; with your compilation target platform, e.g. linux-x86_64, etc.) inside the unpacked archive directory. This directory contains the required .gdbinit file for properly running AROS inside gdb.

 &gt; cd bin/linux-i386/AROS

Run AROS (here: with 128MB of memory) from gdb:

 &gt; gdb—args boot/aros-unix -m 128
or
 &gt; gdb—args boot/arosboot -m 128

 (gdb) r

Watch the shell output - in case AROS complains about &quot;LoadKeyCode2RawKeyTable: Loading &quot;DEVS:Keymaps/X11/keycode2rawkey.table&quot; failed!&quot; you should also see some instructions on how to create a keymap table. (see link above &quot;more on compiling&quot;, too.)
Quit gdb, and try default keymap table:

 (gdb) q
 The program is running.  Quit anyway (and kill it)? (y or n) y
 &gt; cd ../../..
 &gt; make default-x11keymaptable

Re-run AROS, as described above. Try e.g. RAros (= right windows key) + W to open a shell. If this doesn't work you have to create a keymap table yourself, quit gdb again, and make a new keytable:

 &gt; make change-x11keymaptable

A window will open. Watch the window's title bar, and follow the instructions.

When done, re-run AROS. RAros + W should now open a shell.

Next, compile your program with gdb support.


When you start GDB is there a warning which says

   warning: File &quot;&lt;whatever&gt;/.gdbinit&quot; auto-loading has been declined by your `auto-load safe-path' set to ...

If so start gdb with &quot;-ix .gdbinit&quot;


&lt;pre&gt;
Summary - In short:

* build AROS with debugging support (i.e. ./configure --enable-debug=all)
* build your application with debugging support (i.e. option -g)
* run AROS in the GNU debugger (you may use the GUI frontend &quot;ddd&quot; which simplifies usage a bit)
* start your application
* use the commands &quot;findaddr&quot; and &quot;add-symbol-file&quot; as written in the debugging manual
* if the debugger doesn't find the source code of your application use the &quot;dir&quot; command of the debugger. 
&lt;/pre&gt;

===How to use gdb===

In AROS open a shell, then (in host shell) use CTRL-Z to go into gdb. Use &quot;b Exec_CreatePool&quot; (one of the functions used early on by startup code in programs) to add a breakpoint, then &quot;cont&quot; and gdb will interrupt somewhere early during startup of &quot;program&quot;. Use &quot;bt&quot; to show backtrace and &quot;loadseg&quot; for &quot;??&quot; entries. One of them will be for &quot;program&quot;. After that you can use &quot;disassemble program&quot;.

One thing you need to make sure is that .gdbinit you have in your build directory is the same as in source tree. It has been modified some time ago, but the build system does not refresh it - you need to copy it manually

To recap, please read our debugging [http://aros.sourceforge.net/documentation/developers/debugging.php manual]:


To detect segfaulting when loading, try...

 ./configure—enable-debug—with-optimization=&quot;-O2&quot;

Because crash or no crash may depend on optimization. For newer compilers maybe this helps...

 --with-optimization=-&quot;-O2 -fno-strict-aliasing&quot;

One way to make crashes less random (more easily reproducible) is to activate the munging of free memory in rom/exec/freemem.c which is normally commented out:

&lt;pre&gt;
Index: freemem.c
===================================================================
--- freemem.c   (revision 34289)
+++ freemem.c   (working copy)
@@ -154,11 +154,12 @@
         * created with their TCB placed in the tc_MemEntry list. The workaround
         * is to avoid munging when FreeMem() is called with task switching disabled.
         */
+
        /* DOH! it doesn't work even this way. What's wrong???
-        *
-        * if ((SysBase-&gt;TDNestCnt &lt; 0) &amp;&amp; (SysBase-&gt;IDNestCnt &lt; 0))
-        *      MUNGE_BLOCK(memoryBlock, MEMFILL_FREE, byteSize);
         */
+
+       if ((SysBase-&gt;TDNestCnt &lt; 0) &amp;&amp; (SysBase-&gt;IDNestCnt &lt; 0))
+           MUNGE_BLOCK(memoryBlock, MEMFILL_FREE, byteSize);

     }
&lt;/pre&gt;

Mungwall can be turned on at runtime. Currently this works in all hosted versions. Just specify &quot;mungwall&quot; on kernel command line and it works. It can work on native too. In order to enable it you need to parse kernel command line, and if &quot;mungwall&quot; is present, set EXECF_MungWall bit in IntExecBase.IntFlags.

This needs to be done before the first AllocMem() for obvious reasons. And never reset back this flag! If you change it on a working system, you are doomed.

Hosted ports do the processing in rom/exec/prepareexecbase.c --enable-debug=mungwall option in configure still works but is going obsolete.  A kludge in rom/exec/allocmem.c is responsible for this and it needs to be removed when the transition is done.

BTW,  on  i386-pc  port it can be activated by &quot;mungwall&quot; argument on command line, you don't need to rebuild AROS.
New mungwall affects not only AllocMem()/FreeMem(), but also pools. I also tested it with AllocAbs(), seems to work correctly.

Runtime mungwall works on:

* pc-i386
* pc-x86_64
* linux-i386
* linux-x86_64
* darwin-x86
* linux-ppc

Works on all hosted ports, if the port itself is working.

* amiga-m68k
* Not on sam440-ppc and efika-chrp-ppc, even if they would be able to be built at moment. Does not work on (for now, need NVRAM support)

When starting my freshly rebuilt i386-linux-aros which was compiled with full debugging support I get sometimes the error &quot;Program exited with code 0377&quot;. Add the following to your .gdbinit: 
 set follow-fork-mode child

Here are some of the custom AROS gdb functions (defined in &quot;.gdbinit&quot; file) to resolve &quot;in ?? ()&quot; entries in backtrace: 
&lt;pre&gt;
#0 0xb7ffd424 in __kernel_vsyscall ()
#1 0xb7e2a657 in sigsuspend () from /lib/libc.so.6
#2 0xb7c63900 in ?? ()
#3 0xb7c640e3 in ?? ()
#4 0xb7c641e0 in ?? ()
&lt;/pre&gt;

You can use

 loadseg 0xb7c63900
 loadframe 2
or
 loadbt
and some others. Use &quot;help &quot; for a little help text. If the commands do not work try &quot;loadkick&quot; first.


Use &quot;thistask&quot;, &quot;taskready&quot;, &quot;taskwait&quot; to get list of AROS tasks. &quot;bttask &quot; shows backtrace of a task which is in ready or in wait queue and &quot;loadseg&quot; to resolve &quot;??&quot; entries in it's backtrace (&quot;loadframe&quot; would not work as it assume current running task).

===Native debugging tools for AROS===

 to enable debugging at boot time entering the GRUB menu editing line (E key) and adding &quot;debug=memory&quot; to your boot line, then press Ctrl+X to complete booting.


SYS:Tools/Debug/'''Bifteck'''

Open a shell and enter the line below to run Biftek and grab the debug messages collected in RAM into a text file.

 tools/debug/bifteck &gt; ram:debug.txt

and certainly does not open a window. It is a shell tool and only dumps data located from the debug location.
It is therefore important to 'catch' that debug data as soon as possible (before it gets overridden). You should invoke bifteck at the first opportunity before doing anything else.  You can use the TO option to store bifteck output to a file or you can pipe it manually to a file.  


SYS:Tools/Debug/'''Sashimi''' - displays error messages

One suggestion is to do a bug() debugging. Each time bug() is executed it will be output on sashimi. 
You include &lt;aros/debug.h&gt; and place bug(&quot;something\n&quot;); in your source code at location though which control passes.

To get the output - open an aros shell

 SYS:Tools/Debug/sashimi &gt; RAM:out.txt

'''Ctrl C''' to end the output to the RAM Disk.

# open shell, and type
# ram: (to switch to ram drive)
# System:Tools/Debug/Sashimi &gt; mylogfile.txt
# open AHI prefs using wanderer (or use another opened shell)
# play test sound
# close AHI prefs
# shell still open with Sashimi running: press ctrl-c to break Sashimi and return to prompt.
# in shell: copy mylogfile.txt System: (or to your required location)


SYS:Utilities/'''Snoopy''' - monitors OS function calls, run &quot;Sashimi&quot; to see Snoopy's output


SYS:Tools/'''WiMP'''    - the Window (and Screens) Manipulation Program

You can use the -E option of gcc to find out how preprocessor macros are expanded.

===Errors===

crash in strcasecmp usually means that one of its arguments is NULL.

empty space between these two names, prossibly some invisible character 

Old Amiga [http://www.amigacoding.com/index.php?title=Guru_codes&amp;redirect=no Guru Codes]

If the crash is in intuition. Sometimes, if it relates to text, a null pointer sets it off. 
an uninitialised pointer can have any address (this is a common fault).


Compiling on 64bit, Many old code would not properly typecast when doing pointer-integer conversions and thus at least throw a warning. This can easily be located and fixed.

[http://www.aros.org/cs/documentation/developers/app-dev/portable.php Portable code] 

* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.
* Fix (change IPTR/SIPTR back to ULONG/LONG) the few places which really rely on ULONG/LONG being exactly 32 bit. That's for things like pixel (ARGB) buffers, structs written/read to disk, colormaps, but probably not much else.

Then again, many current compilers also throw a warning when you try to assign a pointer value to an integer and the integer is possibly too small. This happens under .NET for example when a 64 bit pointer is assigned to something like an ULONG - so exactly the case which you described.


=== AI ===
                  Multimodal
                   Context
                   Prompt
                    &lt;---
  Model &lt;---&gt; Agent ---&gt; End user
 engine 

 Gemini      LMStudio
  Qwen       Comfyui
   etc

Recent, self hosting locally on laptops, mini pcs or desktops with '''quantization''' 4bit has reduced memory requirements but still require 16Gb+ and no high end gpu for text based 

*[https://lmstudio.ai/download LMstudio single gpu],

Google Gemma 4 Model 
*[ 12B QAT] 


Alibaba Cloud's [https://huggingface.co/ Qwen] team series of large language models LLMs 
*[https://huggingface.co/models?other=qwen3 Qwen 3], [], 
*[https://huggingface.co/models?other=qwen2 Qwen 2], [https://huggingface.co/Qwen/Qwen2.5-Coder-32B qwen 2.5 Coder],  


Small models 
*[ glm-ocr]
*[ medGemma]
*[ qwen 3.5-4b]
*[https://github.com/sipeed/picoclaw picoclaw claude] 


Bigger LLMs but with settings 
*[https://ollama.com/download Ollama single gpu]
*[https://github.com/ggml-org/llama.cpp/releases llama.CPP multi gpus],
*[ VLM multiple gpus],
Multimedia 
*[ Kimi K3], 


For the full experience 
#Training learning using 1+ high end GPUs at least 16GB VRAM per GPU card or 64Gb+ of unified, 16Core CPU with at least 64Gb of RAM system memory, though training can take weeks 
#Inference with custom asics or GPUs 

*[ MiniMax H3] for audio and video but gpu 8Gb+ 
*[https://github.com/jamiepine/voicebox voicebox]
*[https://github.com/ideogram-oss/ideogram4 ideogram4]
*[https://github.com/calesthio/OpenMontage OpenMontage]

&lt;pre&gt;
Text to Audio --\
Text to Video --/ Reference Video --&gt; Video and Audio output 
&lt;/pre&gt;

=== Example ===

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/* 1. Header for your name,date,purpose of program.
2. Pre-processor directives. This will include the #includes for files you want to add. 
3. Includes for function prototypes if necessary.
4. Main()
Create Pointers for Libraries and any Window you want to open.
5. Open necessary libraries.
6. Check if open exit program if fail.
7. Open a window exit program if fail.
8. Add your program
9. Close Window
10 Close Libraries.
11 End Program. */

/* standard os included headers &lt;.h&gt; */
#include &lt;dos/dos.h&gt;
#include &lt;dos/dosasl.h&gt;
#include &lt;dos/dosextens.h&gt;
#include &lt;dos/exall.h&gt;
#include &lt;dos/rdargs.h&gt;
#include &lt;exec/memory.h&gt;
#include &lt;exec/types.h&gt;
#include &lt;utility/utility.h&gt;
#include &lt;intuition/intuition.h&gt;

/* define as unresolved external references (proto/xxx.h) and compiler will link to auto(matically) open library */ 
#include &lt;proto/arossupport.h&gt;
#include &lt;proto/dos.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/graphics.h&gt;
#include &lt;proto/cybergraphics.h&gt;
#include &lt;proto/datatypes.h&gt;
#include &lt;proto/icon.h&gt;

#include &lt;workbench/workbench.h&gt;
#include &lt;workbench/icon.h&gt;

#include &lt;datatypes/pictureclass.h&gt;

#include &lt;proto/muimaster.h&gt;
#include &lt;libraries/mui.h&gt;

#include proto/bsdsocket.h

#include &lt;ctype.h&gt;
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;string.h&gt;

/* my own headers &quot;.h&quot; */

#define CTRL_C      (SetSignal(0L,0L) &amp; SIGBREAKF_CTRL_C)
#define  isDir(fib) ((fib)-&gt;fib_DirEntryType &gt;= 0)

#define ARG_TEMPLATE    &quot;FILE/A,ALL/S,QUIET/S,W=WIDTH/N,H=HEIGHT/N,M=METHOD,DEFTOOL&quot;

int main(void)
{


	return retval;
} /* main */
&lt;/syntaxhighlight&gt;

If you used c++, there is not yet c++ support in our shared library system. 
The easiest way to create / compile a shared library would be to use the AROS build system but the libraries can be created manually. You have to create a ROMTAG structure and some header files.  

A shared library is built with the %build_module macro with a line like this:

 %build_module mmake=MetaTarget modname=mylib modtype=library files=SourceFiles 

This macro can build different AROS module types, like devices, Zune classes, HIDDs, etc.

&lt;pre&gt;
##begin config
version 1.0
##end config

##begin functionlist
void func1(LONG a, LONG b)
int func2(char *s, ULONG a)
##end functionlist
&lt;/pre&gt;


Alternatively,  

&lt;pre&gt;
#ifndef LIB_H
#define LIB_H

#define __NOLIBBASE__

#include &lt;exec/libraries.h&gt;
#include &lt;exec/semaphores.h&gt;
#include &lt;dos/dos.h&gt;

#ifdef __AROS__
//#include &lt;aros/debug.h&gt;
#define reg(x)
#define __saveds
#endif

#define USESYSBASE struct ExecBase *SysBase = Base-&gt;My_SysBase;

struct MyTestBase
{
  struct Library   My_Test_Lib;
	struct ExecBase *My_SysBase;
	APTR             My_SegList;
  int              testint;
};

#endif
&lt;/pre&gt;

&lt;pre&gt;
/*--------------------------------------------------------------------------*/
/* Resident header written for mytest.library */
/*--------------------------------------------------------------------------*/

#define __NOLIBBASE__

#define VERSION         1
#define REVISION        0

#define LIBHEADNAME     mytest
#define LIBHEADNAMESTR &quot;mytest&quot;
#define COMPDATE        &quot;04.10.2015&quot;
#define VERS            &quot;1.0&quot;

#define LIBBASETYPE 	struct MyTestBase
#define LIBBASETYPEPTR  LIBBASETYPE *

#include &lt;aros/debug.h&gt;
#include &lt;exec/exec.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;exec/resident.h&gt;
#include &lt;exec/nodes.h&gt;
#include &lt;exec/libraries.h&gt;
#include &lt;aros/symbolsets.h&gt;
#include &quot;lib.h&quot;

const UBYTE lib_name[] = LIBHEADNAMESTR &quot;.library&quot;;

const UBYTE lib_id[] = &quot;$VER: &quot; LIBHEADNAMESTR &quot;.library &quot; VERS &quot; (&quot; COMPDATE &quot;) by ALB42\n&quot;;

extern const APTR FuncTable[];

AROS_UFP3 (LIBBASETYPEPTR, InitLib,
    AROS_UFPA(LIBBASETYPEPTR, Base, D0),
    AROS_UFPA(BPTR, seglist, A0),
    AROS_UFPA(struct ExecBase *, sysbase, A6)
);

static struct LibInitStruct
{
    IPTR                   LibSize;
    const APTR             *FuncTable;
    const struct DataTable *DataTable;
    APTR                    InitFunc;
}
const LibInitStruct =
{
    sizeof(LIBBASETYPE),
    FuncTable,
    NULL,
    (APTR)InitLib
};

const struct Resident romtag =
{
  RTC_MATCHWORD,              /* match word */
  (APTR)&amp;romtag,              /* back pointer */
  (APTR)(&amp;romtag + 1),        /* skip pointer */
  RTF_AUTOINIT | RTF_EXTENDED,/* flags */
  VERSION,                    /* version */
  NT_LIBRARY,                 /* type of module */
  0,                          /* init priority */
  (STRPTR)lib_name,           /* module name */
  (STRPTR)lib_id + 6,
  (APTR)&amp;LibInitStruct,
  REVISION, NULL
};

AROS_UFH3 (LIBBASETYPEPTR, InitLib,
    AROS_UFHA(LIBBASETYPEPTR, Base, D0),
    AROS_UFHA(BPTR, seglist, A0),
    AROS_UFHA(struct ExecBase *, sysbase, A6)
    )
{
    AROS_USERFUNC_INIT
    
    Base-&gt;My_SegList = seglist;
    Base-&gt;My_SysBase = (APTR)sysbase;
    Base-&gt;testint = 0;
    
    USESYSBASE
    bug(&quot;InitLib\n&quot;);
    
    if (!set_open_libraries())
    {
      set_close_libraries();
      return NULL;
    }
    
    return Base;
    
    AROS_USERFUNC_EXIT
}

AROS_LH1(LIBBASETYPEPTR, LibOpen,
    AROS_LHA (ULONG, version, D0),
    LIBBASETYPEPTR, Base, 1, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    
    USESYSBASE
    bug(&quot;LibOpen\n&quot;);

    (void)version;
    
    Base-&gt;My_Test_Lib.lib_OpenCnt++;
    return Base;

    AROS_LIBFUNC_EXIT
    
}

__saveds APTR LibExpungeInternal(LIBBASETYPE *Base reg(a6))
{
  USESYSBASE
  APTR seglist;
  bug(&quot;LibExpungeInternal\n&quot;);

  if (Base-&gt;My_Test_Lib.lib_OpenCnt)
  {
    return 0;
  }

  seglist = Base-&gt;My_SegList;

  Forbid();
  Remove((struct Node*)Base);
  Permit();
  FreeMem((APTR)Base - Base-&gt;My_Test_Lib.lib_NegSize, (LONG)Base-&gt;My_Test_Lib.lib_PosSize +
    (LONG)Base-&gt;My_Test_Lib.lib_NegSize);
  
  set_close_libraries();
  return seglist;
}

AROS_LH0(BPTR, LibClose,
    LIBBASETYPEPTR, Base, 2, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;LibClose\n&quot;);

    if (!(--Base-&gt;My_Test_Lib.lib_OpenCnt))
    {
      return LibExpungeInternal(Base);          
    }
    return 0;
	
    AROS_LIBFUNC_EXIT
}

AROS_LH1(BPTR, LibExpunge,
    AROS_LHA(LIBBASETYPEPTR, Base, D0),
    struct ExecBase *, sysBase, 3, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT

    (void)sysBase;
    
    USESYSBASE
    bug(&quot;LibExpunge\n&quot;);

    return LibExpungeInternal(Base);
	
    AROS_LIBFUNC_EXIT
}

AROS_LH0(LIBBASETYPEPTR, LibReserved,
    LIBBASETYPEPTR, Base, 4, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;LibReserved\n&quot;);

    return 0;
    //return (APTR)LibReserved();
    
    AROS_LIBFUNC_EXIT
}


// Space for your own functions
// do not forget to update the FuncTable as well

AROS_LH1(int, TestFunction,
    AROS_LHA(int, TestValue, D0),
    LIBBASETYPEPTR, Base, 5, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;TestFunction\n&quot;);

    Base-&gt;testint = TestValue + Base-&gt;testint;
    
    return Base-&gt;testint;
    
    AROS_LIBFUNC_EXIT
}

// Functable -&gt; Table of all functions in the Library, in right order - important!

const APTR FuncTable[] = 
{
    &amp;AROS_SLIB_ENTRY(LibOpen,LIBHEADNAME,1),
    &amp;AROS_SLIB_ENTRY(LibClose,LIBHEADNAME,2),
    &amp;AROS_SLIB_ENTRY(LibExpunge,LIBHEADNAME,3),
    &amp;AROS_SLIB_ENTRY(LibReserved,LIBHEADNAME,4),
    &amp;AROS_SLIB_ENTRY(TestFunction,LIBHEADNAME,5),
    (void *)-1
};

// AutoInit stuff
void *__PROGRAM_ENTRIES__symbol_set_handler_missing;
void *__LIBS__symbol_set_handler_missing;
// end of AutoInitStuff
&lt;/pre&gt;

Makefile
&lt;pre&gt;
VPATH = 
CFLAGS = -O2 -g -fomit-frame-pointer -W -Wall -Wno-parentheses
CC = i386-aros-gcc
LD = i386-aros-gcc
LDFLAGS = -nostartfiles -Wl,-Map -Xlinker linkermap
LIBS = -lautoinit -llibinit
STRIP = i386-aros-strip --strip-unneeded --remove-section .comment

OBJS = lib_header.o 

all: mytest.library

mytest.library: $(OBJS)
	$(LD) $(LDFLAGS) $^ $(LIBS) -o $@

lib_header.o: lib_header.c lib.h

clean:
	rm -f *.o *.library *.ppu testlibrary linkermap
&lt;/pre&gt;


Porting UNIX library to AROS - dealing with static variables which would make it easy to port such libraries to AROS, keeping the benefits of sharing them on disk, but losing the benefit of actually sharing them in memory.

Our problem arises by the fact we want to share the actual code (the .text section of the library) and constant data, but we need to have per-task .bss and .data sections. If we get rid of our intention to share the .text and .rodata sections, things get quite easy: just load and relocate the library whenever it's open, by whoever it's open. It's like statically linking the library into the executable, except that the final linking is done at runtime.

In the V0 branch, in workbench/hidds/hidd.nouveau was committed pcimock.hidd. This is a pci driver that allows mocking real PCI devices under linux-hosted. The main idea is to be able to run the real hardware driver under linux-hosted with as little changes as possible (some changes will always be needed though unless someone wants to write complete device simulator) so that driver's code paths can be executed and debugged using gdb. This was a very helpful capability when porting nouveau. Now it is externalized from nouveau.hidd and can be used by other people porting drivers. The pcimock.hidd can currently mock 4 different nvidia cards, 1 AGP bridge and also mock irq.hidd.

What's the difference between this driver and the pcilinux.hidd? I used that one to develop many different HW drivers for aros. As far as I understood the intention of pcilinux.hidd it is supposed to get access to real hardware that is running under linux. The pcimock.hidd goal is to mock the hardware. For example my dev box is a PCIE system, but I still would like to run the AGP codes paths in nouveau under linux-hosted to check if they don't seg fault. The other case would be to run codes paths for hardware that the developer does not have (Fermi cards in my case). In the case of pcimock.hidd, the AROS driver's code paths will execute as long as you add proper mocking (for example fill in PCI config area or values for registers in BARs). This is an advantage for ported drivers - the code should already work (since it worked on another system) but there might have been mistakes made during porting which can be detected easily with gdb.

In case you are writing your driver from scratch, pcilinux.hidd hidd will give you more advantage, since you can actually access the real hardware from linux-hosted.


== Misc ==

===APL, MPL, BSD, GPL and LGPL Licences===

The majority of AROS sources in licensed under AROS Public License ([http://aros.sourceforge.net/license.html APL]) which (to a degree) protects us from someone taking AROS sources and not contributing improvements back (for example MorphOS took some AROS source and then contributed changes back)

It is written to allow the use of AROS code in other open source or commercial projects without exception whilst providing a mechanism so that improvements/additions can find their way back to the original source in one form or another.

There are &quot;3rd&quot; party applications used by AROS that do not fall under this license, which are an extra &quot;Contrib&quot; download for convenience.

Anyone can port GPL-ed network and sound drivers as AROSTCP and AHI are GPLed. Direct using (porting) [http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs GPL]-ed code in other parts of AROS (gfx, sata, usb) is not possible because AROS license is not compatible with GPL. You need to utilize permissive licensed code like BSD or MIT/X11.


BSD and MPL license are the closest to APL.

APL however is not so compatible with LGPL/GPL.

LGPL case - you cannot statically combine APL code with LGPL. You can, however thank to LGPL being &quot;lesser&quot; restrictive, use LGPL dynamically loaded libraries in APL codes.

GPL case - you cannot combine APL code with GPL in any way if there is no explicit clause by GPLed code authors allowing that. If you do combine APL with GPL in &quot;bad&quot; ways described above - you have a problem (you violate GPL). This problem might result in everything in AROS becoming GPL or everything running or AROS becoming GPL (here I'm not sure really). The other scenario is that you are not allowed to legally distribute such code at all. To be honest I have grasped how to violate GPL, but I'm still no exactly sure what happens when you violate it (but I'm sure it's not anything nice)

GPL software can run on top of non-GPL &quot;system components&quot; (see system components exception of GPL), but the other way around (non-GPL using GPL) leads to problems. This means applications like scout, or Quake III are ok (in the majority of cases).

Theres no reason GPL drivers cannot be ported - but they cant be in AROS's ROM (requires linking APL code with GPL), nor can AROS depend on them (e.g. they must use existing apis).
If they are launched (dynamically linked) by a user action that is allowed. It is also allowed to distribute such binaries together for convenience.

GPL is not about statical or dynamic linking but is about executing process and function calls.


These components - SFS, isapnp, Zune texteditor, AHi, network drivers, freetype, openuirl, BHFormat, Edit and (&quot; dynamically loaded libraries&quot;) are LGPL, not GPL. Mesa/Nouveau stuff is MIT. Some user tools are GPL though.

'''AROS (system)'''
* system components (libraries/classes/devices/etc) cannot be GPL as they would propagate GPL to complete system as well as GPL is not compatible with MPL from which APL is based 
* system components can be LGPL v2 or a permissive license (MIT/BSD)
* system applications can be anything you like (but still I would prefer APL or permissive so the code can be reused if needed)

'''Contrib:'''
* no rules - contrib does not impact AROS system since nothing in AROS system depends on contrib.

About stealing code: The chances of this happening is exactly the same whether we are APL or GPL. If any closed-source option wanted to do it, there is no one that can validate otherwise. MorphOS has used some AROS codes, but contributed changes back.

The rationale behind APL is that while it guarantees that the original developer will get the improvements back (to a certain degree - file based), the person who uses the codes does not have to open his original codes. BSD does not guarantee that the original developer gets improvements. GPL requires the person using the codes to open his codes as well.

The copyright holders needs to stay - we just need information from them that the codes are available under APL (for example a checked-in file like in case of Poseidon). We don't do transfer of copyrights.

; Ultimately what can and cannot be done is up to the author(s) - not the licence.

===AROS source code tree===

* http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-trunk.txt
* http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-contrib.txt


Found this interesting (non-GPL) licensing 'anomaly' - to keep in mind for distributors.

Programs that lose their license if sold (&quot;non-profit only&quot; licensed):
  contrib/aminet/comm/term/TinyTerminal
  contrib/aminet/dev/basic/bwBASIC
  contrib/aminet/text/edit/xdme
  contrib/fish/aroach
  contrib/fish/lotto
  contrib/fish/shuffle
  contrib/fish/touch
  + cdvdfs.


Here is a list of all the GPL/GPLv2/GPLv3 licenses fossology found, what have explicit licenses in their comments.


 excluded LGPL, BSD/GPL dual licensed and programs (such as Prefs/Edit and BHFormat)

&lt;pre&gt;
AROS/rom/dbus/include/  AFL_v2.1 ,GPL_v2+  (supposedly AFL &lt; 3 is GPL incompatible) 
AROS/workbench/classes/zune/betterstring/include/  GPL_v2+
AROS/workbench/classes/zune/texteditor/include/  GPL_v2+
AROS/workbench/classes/datatypes/gemimage/ GPL_v2+ GPL
AROS/workbench/classes/datatypes/degas/  GPL_v2+
AROS/workbench/libs/openurl/README: GPL
AROS/workbench/network/smbfs/documentation/  GPL_v2
AROS/workbench/network/smbfs/source_code/  GPL_v2+
AROS/workbench/network/stacks/AROSTCP/bsdsocket/kern/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/mmakefile.src conf.h  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/sys/  CMU ,GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/net/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/api/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/conf/conf.h: GPL_v2
AROS/workbench/network/stacks/AROSTCP/netinclude/net/radix.h: CMU ,GPL_v2
AROS/workbench/devs/AHI/AHI/  GPL_v2+
AROS/workbench/devs/AHI/AddAudioModes/ GPL_v2+  AROS/workbench/devs/AHI/AddAudioModes/COPYING: GPL 
AROS/workbench/devs/AHI/Docs/texinfo.tex: GPL_v2+
AROS/workbench/devs/AHI/COPYING: GPL
AROS/workbench/devs/AHI/Drivers/EMU10kx/  GPL_v2+
AROS/workbench/devs/AHI/AHI-Handler/  GPL_v2+
AROS/workbench/devs/networks/rtl8029/  GPL   GPL_v2+
AROS/workbench/devs/networks/pcnet32/  GPL   GPL_v2+
AROS/workbench/devs/networks/ppp/LEGAL: GPL
AROS/workbench/devs/networks/atheros5000/  GPL_v2+
AROS/workbench/devs/networks/rhine/  GPL_v2+
AROS/workbench/devs/networks/nForce/  GPL_v2+  GPL
AROS/workbench/devs/networks/prism2/  GPL  GPL_v2+
AROS/workbench/devs/networks/fec/LEGAL: GPL
AROS/workbench/devs/networks/rtl8139/  GPL  GPL_v2+
AROS/workbench/devs/networks/etherlink3/  GPL  GPL_v2+
AROS/workbench/devs/networks/intelpro100/  GPL  GPL_v2+
AROS/workbench/devs/networks/rtl8169/  GPL   GPL_v2+
AROS/workbench/devs/networks/emac/   GPL   GPL_v2+
AROS/workbench/devs/networks/rtl8168/  GPL  GPL_v2+
AROS/workbench/devs/networks/realtek8180/   GPL_v2+
AROS/workbench/devs/networks/via-rhine/via-rhine.c: GPL_v2+
AROS/workbench/devs/networks/via-rhine/   GPL  GPL_v2+
AROS/workbench/devs/networks/e1000/  GPL_v2
AROS/workbench/devs/networks/sis900/  GPL   GPL_v2+
&lt;/pre&gt;

AHI: it has special provisions (COPYING.DRIVERS). The library is LGPL, preferences software is GPL and drivers can be anything without breaking GPL/LGPL.

Network stack: well, we are long overdue for a new, IPv6 enabled network stack anyway, anyone interested? ;) Seriously though it seems like the glue code is GPL and as all the drivers. However some of the drivers are our own code, so they could be relicensed to LGPL.

 Same filter as the AROS trunk list. These should all be libraries or plugins - no programs.

&lt;pre&gt;
contrib/regina/utsname.h: GPL_v2+

contrib/mui/classes/nlist/include/default-align.h: GPL_v2+
contrib/mui/classes/nlist/include/amiga-align.h: GPL_v2+

contrib/mui/classes/BWins/include/MUI/BWin_mcc.h: GPL
contrib/mui/classes/BWins/include/BWin_private_mcc.h: GPL
contrib/mui/classes/BWins/COPYING: GPL_v2
contrib/mui/classes/BWins/MCC_BWins.readme: GPL_v2

contrib/mui/classes/thebar/include/default-align.h: GPL_v2+
contrib/mui/classes/thebar/include/amiga-align.h: GPL_v2+

contrib/gfx/libs/wazp3d/LEGAL: GPL
contrib/gfx/libs/wazp3d/Wazp3D.readme: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d.c: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d_opengl.h: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d_opengl.c: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/Wazp3D.h: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/Wazp3D.c: GPL

contrib/libs/mpega/  GPL_v2+
&lt;/pre&gt;

http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-contrib.txt

===Types===

On AROS following rules apply:
&lt;pre&gt; 
1. BYTE/UBYTE is 8bit, WORD/UWORD is 16bit, LONG/ULONG is 32bit, QUAD/UQUAD is 64bit, the types are comparable with stdint types (int8_t, int16_t, int32_t, int64_t)
2. IPTR/SIPTR are integer types large enough to fit pointer, that is sizeof(IPTR) = sizeof(APTR) = 4 on 32bit system, and = 8 on 64bit system
3. ti_Data in TagList is large enough to hold a IPTR/APTR type.
4. never store a pointer in integer of type LONG. It may work (if the pointer has upper 32bits clear), but does not have to. Compiler should warn you about that.
5. If you are unsure about point 4, allocate your memory with MEMF_31BIT flag set. But don't expect that AROS internals will do the same.
&lt;/pre&gt; 
point 4 is actually important.


* UBYTE/BYTE for 8bit
* UWORD/WORD for 16bit
* ULONG/LONG for 32bit
* UQUAD/QUAD for 64bit

&lt;pre&gt;
UBYTE    Unsigned 8 bit integer variable (byte).
BYTE     Signed 8 bit integer variable (byte).
UWORD    Unsigned 16 bit integer variable (word).
WORD     Signed 16 bit integer variable (word).
ULONG    Unsigned 32 bit integer variable (longword).
LONG     Signed 32 bit integer variable (longword).
FLOAT    32 bit IEEE floating point variable.
UQUAD    Unsigned 64 bit integer variable.
QUAD     Signed 64 bit integer variable.
DOUBLE   64bit IEEE floating point variable.
BOOL     Boolean variable, TRUE and FALSE are also defined in exec/types.h.
VOID     Void.

APTR     A generic pointer for multiple purposes - Arrays.
STRPTR   A pointer to a null-terminated string.
IPTR     Really important in AROS, the only way to declare a field that can contain both: an integer or a pointer.
&lt;/pre&gt;

if you want to write really portable app, you may be interested in standard datatypes defined in C99: int8_t, uint8_t, int16_t, uint16_t, int32_t, uint32_t, int64_t, uint64_t, intptr_t, uintptr_t. They are all defined in inttypes.h include file.

In exec/types.h the following short-cuts are typedef'd. They are used often in AROS, so you should nearly always include exec/types.h and soon only they will be removed from sys/_types.h include, all types are now defined in include files named aros/types/xxx.h.

(Preparation for C library split; sys/xxx.h include will only be available there when compiling with POSIX C library)


Compiler specific types, like int and long might change their size. In case of AROS, similar to linux, int remains 32 bit whereas long grows to 64 bits in size.

If you use Amiga-like data types, i.e. BYTE/UBYTE, WORD/UWORD, LONG/ULONG and QUAD/UQUAD or the C99 standard types (uint8_t and so on, see stdint.h include) then you should have less issues to solve than by using types without size guarantee.

Of course, all pointers grow to 64 bytes using 64bit cpu. Most of the code can be just recompiled and will work. In rare cases, where e.g. pointers are casted to integers, a special care must be taken. Especially in the cases, where pointer is casted to LONG/ULONG (this code will break on 64 bit AROS) e.g.  '#define IPTR ULONG'.

With compiler delint patches which the majority of them are simple casting issues to make the compiler happy. Notice some of the changes involve introducing double casts. In very recent versions of GCC. Yes, the bulk of the double casts are for converting 32 bit addresses (ie from a 32 bit PCI DMA address register) to a 64 bit pointer. First cast is to IPTR (to expand to 64 bits, and prevent sign extension if the address is above 0x7FFFFFFF), and then to APTR.

ULONG != IPTR except on 32bit .. so if you need to store pointers make sure and use IPTR and not ULONG (which some old code does). For this reason things like Taglist elements are 64bit (since the tag data can be a pointer). 
If your passing items on the stack you should use the STACKED attribute to make sure they are correctly aligned (on 64bit all items on the stack are 64bit..)

There is more issues like using &quot;== 0L&quot; causes problems.

===Endian===

*BE 
*LE

Use the macros from &lt;endian.h&gt; instead making a guess based upon architecture defines
 
&lt;pre&gt;
#if _BYTE_ORDER == _BIG_ENDIAN

#elif _BYTE_ORDER == _LITTLE_ENDIAN

#else
+
#error &lt;whatever.h&gt; - Byte order for this architecture is unsupported! 
&lt;/pre&gt;


===SVN and GIT===

If you want to help develop AROS OS itself, you can 

* view current GIT/SVN entries [http://aros.sourceforge.net/ Aros Org website] or [https://github.com/aros-development-team/AROS Github], [https://github.com/ezrec older ezrec mirror], [https://github.com/michalsc/AROS/ older mirror], [https://trac.aros.org/trac/timeline TRAC], [], 
* awaiting update [http://repo.or.cz/w/AROS.git git repo], [http://www.ohloh.net/p/aros/commits ohloh] or [https://svn.aros.org/svn/aros/trunk/ svn repo] and access [Git version git://repo.or.cz/AROS.git here], 
* deprecated [https://www.gitorious.org/aros/aros/commit/a7fda9e ARIX commits] or [https://gitorious.org/aros/aros GIT old]

If you have SVN access (early 2015 introduced a new SVN server, create a new account at trac aros org) and/or have obtained the source [http://aros.sourceforge.net/download.php AROS site] - you can compile the current build tools/environment using: 

 &gt; make development

and follow this [http://aros.sourceforge.net/documentation/developers/compiling.php#building procedure] or [https://github.com/apiraino/aros_guide Guide] 


https://trac.aros.org/trac#Developing

If you plan on contributing back changes, please post information about such changes first on this [http://mail.aros.org/mailman/listinfo/aros-dev/ mailing list] for more experience developers can validate whether they are correct.


Then there are the nightly build machines. They svn update before the build and run configure as one of the next steps. autoconf might be added to the nightly build scripts.

Our build relies on packages downloaded from Internet (SDL for example) - it always worked this way. The minimal requirement (when just building core AROS) is binutils and gcc. If you build contrib as well, you need many more packages to be downloaded.

https://gitorious.org/aros/aros/commits/crosstools-II

git://gitorious.org/aros/aros.git

Branch crosstools-II there is only one commit on top of ABI_V1 
&lt;pre&gt;
../../aros-src/AROS/configure --enable-ccache
--with-portssources=~/aros/Sources --target=pc-x86_64
--with-aros-toolchain-install=/home/weissms/media/data/aros/test/crosstools/pc-x86_64
&lt;/pre&gt;
and
&lt;pre&gt;
../../aros-src/AROS/configure --enable-ccache
--with-portssources=~/aros/Sources --target=pc-i386
--with-aros-toolchain-install=/home/weissms/media/data/aros/test/crosstools/pc-i386
&lt;/pre&gt;
build OK.


:''More information: [[Aros/Developer/Maintainer|AROS Maintainer Docs]]''

===SDI Calls===

Integrate the 'SDI'-headers to allow easier porting to all amiga-like platforms.

&lt;pre&gt;
PUTCHARPROTO( PutTheChar, char c, struct SPrintfStream *s  )
{
 // REAL CODE
}
&lt;/pre&gt;

have &quot;SDI_compiler.h&quot; and &quot;SDI_hook.h&quot; included

its more organized like

 #include SDI/SDI_hook.h

than

 #include SDI_hook.h

option 1 --- i also use when back porting from amiga's..

&lt;pre&gt;
#ifdef __AROS__
#include SDI/SDI_hook.h
#else
#include SDI_hook.h
#endif
&lt;/pre&gt;

also

you can add the -i include/sdi/ location if you do not want to add or edit any files.


Defining HOOKPROTO to IPTR name(struct IClass * cl, Object * obj, Msg msg); solved the problem

A MUI application most likely needs only the HOOKPROTOxxx SDI macros. They are compatible with AROS, only the attributes (hook, object attribute) must be given in the right order. examine compiler/include/aros/symbolsets.h (AROS_LIBREQ)

compiling mui stuff for aros setting -std=gnu99 is necessary (i have had -std=c99 most of the time).

===Locale with Flexcat===

Most languages have a locale, but not every app is localized, the only thing needed is to translate the &quot;catalog&quot; files. It is a case of locating the correct catalog and saving the translated version.

For every app that lacks of your language catalog and is localized anyway, you should find (in the sources) files related to locale:

* file.cd = catalog descriptor, contains base msg, with internal language (usually english)
* language.ct = catalog translation, contains every translated msg, indexed as in the file.cd.

Compare with other localized apps... Then, &quot;make my_app-catalogs&quot; should create and install your translated catalogs. ex : for, saying, sys:prefs/wanderer:

on root of AROS sources, type:
 &quot;make workbench-prefs-wanderer-catalogs&quot;
then (if you changed the .cd file):
 &quot;make workbench-prefs-wanderer&quot;

For apps not localized, you have to adapt their code to support it, if it is possible...

noticed the original .cd file has many (//) strings at the end of any voice, so added them also to the .ct file. 
That (//) is only for cd files. I'm highly recommending to use FlexCat for updating ct files, e.g. like this:

 flexcat app.cd deutsch.ct newctfile deutsch.ct

You'll get error checking and new entries are marked in the resulting ct file.

When editing .ct files, only change those lines containing translation and perhaps version string, nothing else.
The rest is up to the relevant tool, flexcat. In order to update your translation, type in the following in your shell:

 flexcat xyz.cd xyz.ct NEWCTFILE xyz_upd.ct COPYMSGNEW

This way you will not only make sure you have correct translation file but flexcat also pre-fills newly added strings with &quot;*** NEW *** text. Even better tool for checking cd/ct/catalog files is catcheck, but this one is sadly only available for AmigaOS/68k...

Some languages have variations, like portugues from portugal and portugues from brasil differs...

This is the way to go. I will have a look at language files, but basically if those two languages differ you have to do two separated set of translation files, yes.
(you could create a brazilian slang language localization too)

* At system level localization for one language is a dot language file.
(ex: locale:languages/klingon.language)

* At app level localization is a dot catalog file
(ex: locale:catalogs/klingon/system/libs/dos.catalog)

* At sources level, the dot ct file, and &quot;$language&quot; dot cd files and some building framework.
(ex: catalogs/my_app.ct catalogs/klingon.cd catalogs/mmakefile.src support.c support.h)

Please, use Flexcat to generate CT files: 
 FlexCat wanderer.cd NEWCTFILE=deutsch.ct

Then fill the first 2 lines with something useful:
&lt;pre&gt;
## version $VER: wanderer.catalog 1.1 (9.2.2006)
## language deutsch
&lt;/pre&gt;

You can even update the CT-File: (This adds the new strings)
 FlexCat wanderer.cd deutsch.ct NEWCTFILE=deutsch.ct


To compile a catalog you only need the .cd file and your translation (.ct file):
 FlexCat multiview.cd deutsch.ct CATALOG=MultiView.catalog


[http://murks-ide.svn.sourceforge.net/viewvc/murks-ide/trunk/src/Catalogs/flexcat_linux?revision=100 Linux version of FlexCat]

: [http://aros.sourceforge.net/documentation/developers/app-dev/localization.php#localization-for-non-developers More information]


A script which compares the required version (i.e. the version which an application/module etc. tries to open) with the version of the existing CT files. The result is in this table:

https://github.com/aros-translation-team/translations/wiki/Progress

The following cases are highlighted:

    n/a i.e. CT misses at all
    version in existing CT file is lower than the required version


It might be a bit difficult to participate if you haven't worked with Git before but alternatively you can send your CT files to our Slack channel.

When the ct file has been generated via flexcat (flexcat keyshow.cd NEWCTFILE=spanish.ct) it has the following header:

---------------------------------------------------------------------------------------------------------------
## version $VER: &lt;name&gt;.catalog &lt;ver&gt;.&lt;rev&gt; (04.01.2021)
## language nolanguage
## codeset 0
;
---------------------------------------------------------------------------------------------------------------

Those values &lt;ver&gt;.&lt;rev&gt; are the version and revision of the CT file for the languaje or are the values of the application being localized?

The &lt;ver&gt; part must match with version which the application tries to open. You can find the value either in the column &quot;Required Version&quot; in the table which I've linked above, our you can look in the git repository. For keyshow it would be https://github.com/aros-translation-team/keyshow. You can find in the file &quot;catalog_version.h&quot; the right version number.
The &lt;rev&gt; part starts for new CT files with 0 and should be increased every time the CT file is updated.

Updated several files and created a few more that were missing on the spanish catalog.

The catalogs are in Git repositories at https://github.com/aros-translation-team

a) You tell me your Github user name. I'll invite you. You can work directly with the Git repositories.

b) You create Github forks of the catalog repositories and create pull requests.

c) You send the CT files to mrustler  gmx de


===C Utils Misc===

The AROS source uses at several places the __DATE__ macro to fill the date entry of a $VER tag. Problem is that c:version doesn't understand that date format (e.g. &quot;May 21, 2011&quot;). As a result the output of e.g.
&gt; &quot;version c:shell full&quot; contains &quot;(null)&quot;. Is extending the version command to understand the format of __DATE__  the right solution for that problem?

AmigaOs compilers should use __AMIGADATE__ macro or similar form, if it isn't implemented it could be emulated in makefile: -D__AMIGADATE__=\&quot;$(shell date &quot;+%d.%m.%Y&quot;)\&quot;

BTW. I think DD.MM.YYYY is better format than &quot;Month DD YYY&quot; because &quot;Month DD YYY&quot; is not localized in any way.

&quot;strnicmp&quot; shouldn't work with NULL pointers

The Situation:

compiled a linklib using c++ object files (using the c++ cross compiler).
compiled a C stub that uses the linklib (using the c++ cross compiler).

Try to link them together (using the c++ cross compiler) with C object
files (using the normal target c compiler) that need to use -nostartup
= cant do because using the c++ files pulls in arosc (for stdio etc.) -
so wants to have the autoinit stuff present.

What can I do about this??

If it is possible to manually open it then what do I need to do exactly?

=== ENV ===

The philosophy behind ENV: is that keeping configuration files there allows you to  'Use'  preferences  by  keeping  a copy in ENVARC: intact. However in some cases (like this one) it is not required.

99% of the time that statement is true (not required) for pretty much every file in ENV: or do people change their default icons - and prefs settings - every boot?

There seem to be a bad habit of late with developers changing things to reflect their own personal preference when the change isn't actually necessary - It would be nice if people could refrain from doing that in the tree without at least discussing it on the dev-list first (and with good reasoning unless they committed said work in the first place..)

We're not keen on the pollution of the &quot;S:&quot; dir: it's meant to be for scripts. What's wrong with &quot;ENV:&quot;?
Only the fact that it takes up RAM. I  understand  that  for  PCs  with  several gigabytes of RAM this is
irrelevant. But let's remember about other machines. The philosophy behind ENV: is that keeping configuration files there allows you to  'Use'  preferences  by  keeping  a copy in ENVARC: intact.

However in some cases (like this one) it is not required.

How about implementing in the style of HappyENV then? RAM-disk handler that falls through to reading from ENVARC: if there is no such file stored in it already. Removes RAM usage for unchanged files, removes the need to copy ENVARC to ENV in startup-sequence. 
Shouldn't be too hard to make from AmberRAM, or even just extend AmberRAM to provide this service.

Is it feasable to build a special version of AmberRAM handling ENV: that will try and copy the requested file from ENVARC: if it isnt found in ENV: ? 
Additionaly it could mark closed &quot;files&quot; as untouched - and expunge them from ENV: after a period of time to free up additional RAM:, or when the system is running low on free memory?

Silenty disappearing files may not be a good plan. Would be nice if the following would work:

ASSIGN :ENV SYS:Prefs/Env-Arc ADD
ASSIGN :ENV RAM:ENV  ADD

Where new files put in ENV: end up in RAM:ENV, and opening files looks in RAM:ENV first, then SYS:Prefs/Env-Arc

Well - that's essentially what im proposing but without the assigns - or need for a RAM:ENV directory. 
Adding it as a feature of AmberRAM sounds like the most memory efficient way (one handler to load in RAM) but that's only if it is possible to make it handle ENV: additionally to RAM:, and if it is even possible to add the proposed functionality (...and how to make it enable it when accessing ENV:).

===(AS)MP support===

If one has to recompile software for SMP multi core, is there any thing special one has to do to get software to run?   
Use task.resource if you need to query information about what tasks are running, and clear msgports completely when they are allocated.

Most code should not need Forbid. Use Semaphores, Messages etc. to sync your own code. 

Accessing system structures is a different thing. Use the proper API whenever possible.

How single structures will be protected in the future is still a moving target, at least it is not documented. And you should never  use undocumented stuff  


Ideas on for SMP multi-core

Another suggestion is ... Forbid/Permit function calls are meant to halt multitasking so as no other task could intervene with what ever the calling task is doing, e.g. setting semaphores. Disable/Enable calls are meant to halt interrupts and as a side effect they also halt task switching.

One option is to make it compulsory to protect shared resources with semaphores and forbid the use of simple Forbid() calls as to protect something. Setting semaphore should be done if possible with atomic instructions (check and alter in one instruction). Or make the second concurrent ObtainSemaphore call halt the second calling task and force if possible a task switch which ever gives better results. 

Semaphores could store the owning tasks task pointer instead of boolean to make things easier.

As long as the CPU initiates the DMA transfers through the OS, and the OS ensures that the transferred memory is within the region accessible to the user initiating the transfer, everything is fine. The CPU is the conductor, and the CPU by that has the control of which DMA transfer is initiated and which is not.
All you need to do is to write device drivers reasonable. Hint: CachePreDMA and CachePostDMA exist.
All the Os has to do is to verify that the memory regions to be transferred are valid, and prohibit direct access to the DMA control registers from user space. None of these algorithms imply huge costs.
The current OS design doesn't really allow virtual memory in first place, Forbid() is again the problem.

[http://www.tbs-software.com/guide/index.php?guide=autodocs.doc%2Fmemory.doc&amp;node=1 memory.library API] seem to low level. IMHO the programs should not know how the swapping is implemented. I would just go for one new memory flag
MEMF_SWAPPABLE that indicates that a certain memory region or a whole memory pool won't be accessed during Forbid()/Permit() etc. It only solves part of the problem, it only implements virtual memory and not memory protection. For the latter you need to be able make certain memory inaccessible by other programs, some memory read-only for one task and read-write for other tasks, etc. And I think this should be done in the same Address Space in order to avoid you constantly need to swap between different address spaces. 
So to summarize, if there are programs using this API we may provide a wrapper layer to get them working but I am not convinced this API should be the reference API with whom to provide VM to AROS programs.

=== Variadic ===

variadic functions (i.e. functions with an arbitrary amount of arguments).

&lt;pre&gt;
    #include &lt;stdarg.h&gt;
    [...]

    char * STDARGS GetKeyWord(int value, char *def, ...)
    {
        [...]
        va_list va;
        [...]
        va_start(va, def);
        [...]
        va_end (args);

&lt;/pre&gt;

Please keep with using stdarg rather than having va casted to a LONG * type and varargs handled manually. Doing so, prevents tons of casting, where a simple va_arg can be used. So, string = *((char **) args) instead of string=va_arg(va, char *).

&lt;pre&gt;
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;

int printf (const char * format, ...)

{
    int     retval;
    va_list args;

    va_start (args, format);

    retval = vfprintf (stdout, format, args);

    va_end (args);

    fflush (stdout);

    return retval;
} /* printf */
&lt;/pre&gt;

Couldn't find varargs.h or stdarg.h. and have no use for AROS_SLOWSTACKHOOKS or AROS_SLOWSTACKTAGS.

GCC looks for stdarg.h in a different place: 
 /bin/linux-i386/tools/lib/gcc/i386-aros/4.2.2/include/stdarg.h

Here is a path for a &quot;normal&quot; header:
 bin/linux-i386/tools/lib/gcc/i386-aros/4.2.2/../../../../i386-aros/sys-include/aros/system.h


The use of vararg.h isn't supported by newer gcc versions. If you want your code to run on architectures that pass part of variadic arguments in a number of registers you need to use AROS_SLOWSTACK macros. Otherwise your program will not work on powerpc and x86_64 ports.

Of course the SLOWSTACK stuff is not needed in a function that can use va_list, va_start, va_arg and va_end. It's only needed if you want to write functions like DoMethod or similar.

 #include &lt;stdarg.h&gt;

should be enough no matter if you do cross or native compiling. If it does not work, something is wrong and should be corrected.

Stdarg.h is here, Development:lib/gcc/i386-aros/4.2.2/include/

...which is part of the compiler's default include paths. In other words, #include &lt;stdarg.h&gt; works out of the box, indeed. (sorry, I should have just tried it before invoking &quot;search&quot; or &quot;find&quot;...)

furthermore, myprintf() as shown above won't work, because...

 printf(format, args);

...is wrong - the second argument does not match printf() prototype, it expects a argument list, but args is of type va_list (obviously) - so one has to use...

 vfprintf(stdout, format, args);

...instead, just like in the original printf(), and add fflush(stdout).

additionally, one could use...

 int myarg = va_arg(args, int);

...between va_start() and va_end() to access individual arguments, where each call to va_arg() returns an argument casted to the desired type (here: &quot;int&quot;) from the list given (here: &quot;args&quot;) and advances to the next one.

wrapping up vfprintf() and modifying the format string now is a major speedup! no more backslash-n typing! this has been haunting me for years!

On MOS and AmigaOS, the NewObject variadic function is kept in the static library. It takes most of the parameters on the stack - thanks to that the implementation of NewObject calls the NewObjectA function. Everything works perfect, and the typical MUI macros may be easily used.

This, however, is not the case when you compile for AROS. Here, NewObject is a variadic macro, not a function. Thanks such approach we do not need any custom compiler in case of systems, where the arguments of variadic functions are passed partially through registers and partially through the stack (This is the case of PPC and x86_64, this is also the reason why both OS4 and MOS require specially patched compilers).

Since NewObject is a macro, the gcc's preprocessor expects the list of macros arguments enclosed within parentheses. In MUI macros it is not the case. Imagine the following test code:

&lt;pre&gt;
#define foo(a,b) ((a)+(b))

int loosy_function(int a, int b)
{
    return foo(a,b);
}
&lt;/pre&gt;

This will compile and work, but the following piece of code:

&lt;pre&gt;
#define foo(a,b) ((a)+(b))
#define END )

int loosy_function(int a, int b)
{
    return foo(a,b END;
}
&lt;/pre&gt;

will fail with the error: unterminated argument list invoking macro &quot;foo&quot;

There are two ways of fixing your issue. Either create your new objects outside this huge MUI constructions, and in there use just a pointer, or get rid of the &quot;End&quot; macro and exchange it with &quot;TAG_DONE)&quot;.


Badly written software is, for example, casting va_list to an APTR or even doing so as if va_list were a plain table of function arguments. Such code needs to be fixed because it has very few chances to work anywhere but on author's machine ;)

The problem is nOt that they assume sizeof(APTR) == 4, its that they often do not use APTR, and use ULONG to store pointers exclusively. If the code used APTR/IPTR as it should - most of the &quot;problems&quot; wouldn't exist.

It would also help if people would start using variadic arguments properly. Many coders do assumptions which shall never be made. Instead, they should consider using stdarg.h file and all the va_* functions :)

===ABI===

In the head of our SVN repository there are now only 3 directories:

&lt;pre&gt;
admin/
branches/
trunk/
&lt;/pre&gt;

We have added two extra dirs there: tags and imports

As discussed when we branch ABI V0 and [[Aros/Developer/ABIv1|ABI V1]] it would also be good to introduce tags. Normally this is done in a directory in the repository called tags. Currently we don't have this directory there. (We do have branches/tags that is a hack I have done because one doesn't have write access in the top directory. I think this directory is not clean and should be removed).

The second directory I would introduce is an imports directory for implementing vendor branches as discussed in the svn [http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html book]. Currently we use code from several different projects and that code is stored inside the AROS tree; we seem to have problems with keeping this code up to date and merge our changes upstream. Maintainers of up stream projects like the MUI classes etc. have complained about this (to put it lightly).

Introducing these vendor branches would make it easier to see what changes we have made and make patches to be sent upstream and make it easier to import newer upstream versions of their code. Although can't &quot;copy&quot; the vendor branch into the main branch because it's already there, so start with a &quot;merge&quot;.

Yes, the first step to make the code already in the repository compatible with the vendor branches will be the most difficult. The best way to do it the following way:

* first import the version on which the current AROS code is based into the vendor branch
* then import the new version over it in the vendor branch
* finally merge the difference between these two version in the AROS code present in the repository.

For example, place NList directly under vendor and not in a subdirectory like &quot;contrib/zune/classes&quot;.

Actually after we have a stable [http://aros.sourceforge.net/documentation/developers/specifications/drafts/abiv1.php ABIv1 (2012 or later)]. We need to move away as much as possible from the contrib directory to some other repositories. The reasons are ...

* The AROS repository should be for the core AROS code.
* other contrib projects should be tried to be compiled for all Amiga-like OSes.
* The release scheme for AROS and the other programs should not have to be aligned.
* Binary versions should be provided on aros-archives and on aminet and/or OS4Depot to install them. (Some clever programs should maybe be provided to make the life of distribution developers easier). 
* avoid parallel forks of programs for AROS and the other amiga OSes.

If there is really a need for a place for hosting AROS projects we may investigate setting up such a server but then including bug tracking, governance, maillist, etc. for each project separately. I personally think there are already enough places like sourceforge, google code, savannah, etc. where people can go for hosting such projects.

==Links==

* http://amigadocs.hokstad.com
* http://amigadocs.hokstad.com/doku.php?id=dev-links


 In the future...?
*AROS 64bit - SMP, Vulkan with OpenGL compability layer
*AROS 32bit - keep for historic reasons 

What would you like to see implemented in AROS?
ABIv1 completed, SMP (x86_64),  SendMsg()/GetMsg() to support memory protection between target and destination, in that order.   Michal Schulz and Jason McMullan have been toying with the question &quot;What are the minimal changes needed to the AmigaOS 3.1 API to support SMP&quot;?  The answer so far seems to be &quot;few, but subtle&quot;.  For example, SysBase-&gt;ThisTask is no longer meaningful on SMP, but FindTask(NULL) is.  Disable() and Forbid() are shockingly bad on performance, but adding a spinlock semaphore mode to SignalSemaphore will help new code on SMP.  

Leveraging a 'common' OS with a lot of machine support (Linux, MacOS, Windows, QNX, etc.) is something that AROS has been doing for quite a long time, and it is the biggest strength of AROS. This AROS experience and programming model, in the same way the Google's Android layers on top of Linux, or MacOS X layers on top of the Darwin/BSD kernel, as a first step 

* The graphics + layers subsystem could be implemented as a shim on top of a OpenGL ES implementation (ie on any modern Linux system, or the RaspberryPI's hardware, MacOS X, etc). 
  - This also allows every window to be on its own 3D surface with backing store, allowing Wanderer (or a Commodity)
rearrange/zoom/animate app windows without having to send a pile or refreshes to them

* Use OpenAL as the sound backend
* AROSTCP would be a thin layer over the native OS's TCP/IP stack
* dos.library, poseidon.library, and input.device would be slim shims over the native APIs
* If we move to loading all libraries' into the application's task space, instead of a single global instance of the library, this will allow SMP and MMU more easily. 
  - Yes, it will require a lot of work in the libraries to make this transition
  - Yes, I do think it will be worth it in the end.

* A 'fat binary' install format (or, maybe LLVM bytecode) that can be 'flattend' to the target architecture on installation.

So, what would this 'AROS of the future' look like?

* AmigaOS 3.x style API, with certain 'fundamental changes' to message passing
* Uses the underlying OS' device drivers, so more AROS developer effort can go to user-visible features and bugfixes 
* Allows AROS applications to run side-by-side with the OS's native apps


And why would anyone want to program on such a system?

* AROS applications would run on any system that has the AROS Framework installed
* AROS applications are pixel-for-pixel the same on all platforms. 
* Develop with the knowledge that you are guaranteed OpenGL and OpenAL, and the rest of the AROS Framework

an option for mmake to dump its dependency of metatarget in a graphviz[*] input file. This should make it possible to visualize the dependencies and hopefully be inspiration for cleaning up some mess, circular or unneeded dependencies and so on.


AmigaOS gcc 9 [https://franke.ms/amiga/gcc.wiki Old versions] able to create binaries for AmigaOS and [https://eab.abime.net/showthread.php?t=93813 Upgrading gcc versions] 


==References==
{{reflist}}
{{status|50%}}

{{BookCat}}</text>
      <sha1>rpstz2px7etbpw28381hudnrbec86og</sha1>
    </revision>
    <revision>
      <id>4668984</id>
      <parentid>4668983</parentid>
      <timestamp>2026-09-05T18:35:42Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668984</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="125151" sha1="bfy0rqzhy03vaeexifwatvy9sypkv65" xml:space="preserve">{{ArosNav}}

==A technical overview of AROS==

Google translation [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=de&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs German], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=fr&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs French], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=it&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Italian], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=es&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Spanish], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=hi&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Hindi], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=zh-CN&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fwiki%2FAros%2FDeveloper%2FDocs Chinese], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ru&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Russian], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pl&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Polish],
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pt&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FDeveloper%2FDocs Portuguese]

{{Uncited}}

AROS,&lt;ref&gt;[http://aros.sourceforge.net/download.php References and sources]&lt;/ref&gt; like AmigaOS (TM), is a [[w:Message passing|message-passing]], [[w:Preemption (computing)|preemptive]] [[w:Multitasking|multitasking]] [[w:Operating system|OS]].

It uses [[w:Reentrant (subroutine)|re-entrant]] shared libraries to save memory space.

AROS is based around an executive library kernel (Exec) and two other libraries:

* Exec (the &quot;kernel&quot;, which is not a kernel in the modern sense), 
* Intuition (graphics and GUI, integrated into the system) and 
* AmigaDOS (Disk Operating System, the Metacomco's Tripos modified to work with Exec).

The design philosophies of AmigaDOS and Intuition are rather different, the former adopting a C-like API and the latter creating an [http://www.basden.demon.co.uk/amiga/amiga.oo.html object-oriented], message passing aware environment for the programmer. The system base is the only absolute address in AmigaOS (located at 0x00000004) this does differ with AROS as AROS SysBase is automatically provided (no $4) but everything else is dynamically loaded. The OS is well known for delivering high performance due to its close connections with the hardware, while simultaneously having the flexibility to support re-targetable graphics (Cybergraphics) and retargetable audio subsystems (AHI).

: Diagram showing relationships of libraries to system needed


Remember, AROS is a [http://en.wikibooks.org/wiki/Aros/Developer/ABIv1 research] operating system, and while all contributions to the base AROS code are welcome, please contact the dev list first for any core changes. Writing applications for AROS does not have this requirement. 

While AROS appears and feels almost feature complete, it is still [[Aros/Developer/IncompleteAPIs|missing a small number of functions]] from the Amiga API. 


[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1201 This thread provides] information for setup, [http://www.aros.org/documentation/developers/index.php documentation] and whether you are interested in core OS changes and/or writing/porting software apps 

*you compile directly under AROS, which can be running on either real hardware, virtual hardware
*in hosted mode under linux/window, cross-compile from that host OS (save your files as ISO-8859-15 encoding instead of UTF-8) [https://github.com/BlitterStudio/aros-compiler-docker Docker images] 


'''The repository''' for 64bit and 32bit ABIv1 all hardware platforms is [https://github.com/aros-development-team/AROS current development version]. 
There are many forks of this so that developers can work on their own and forward changes at a later date as discussed on the dev forum 


64bit PC is one of two hardware platform with another fork called [https://github.com/deadwood2/AROS abiv11] which is used for Aros One x64 PC 

32bit PC is the other fork [https://github.com/deadw00d/AROS/tree/alt-abiv0 repository for current stable PC version ABIv0 with backported ABIv1 features is located which is used on AROS One and Icaros x86 32bit based distros] this is for historic reasons 


Any [https://github.com/aros-development-team/AROS/issues bugs / issues can be added for ABIv1 issues]. The two individual PC forks have their own issues tab on their github webpages 

We have a [https://arosdevteam.slack.com/archives/CUFV48U3H slack here], discord on [https://discord.gg/UKp9qdEBuQ Discord@AmigaDev], 


==Software Development for AROS==

===Programming languages===

====Common to all====

'The Developer Environment', which primarily supports C/C++ code, there are other scripting programming languages available 

:[[Aros/User/DOS|DOS]] 
:[[Aros/Developer/Docs/LUA|LUA]] 
:REXX [[Aros/Developer/Docs/Rexx|Regina (AROS' ARexx)]] 


====Needs to be compiled/ported====

::[[Aros/Developer/Docs/LLVM|LLVM]] 
::Python [ Info], [], 
::[https://ae.arosworld.org/index.php?board=11.0 FreePascal FPC Aros-Exec thread], [https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language fpc arm here is very old and will not work], FreePascal for AROS has its own [http://fpcaroswiki.alb42.de/ Wikibook], 


::[http://sourceforge.net/projects/xamos/ X-Amos Basic] 
::[http://sdlbasic.sourceforge.net/ SDLBasic] ([https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language ])
::[[Aros/Developer/Basic/Basic4SDL|Basic4SDL]] ([https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language ])
::[http://alvyn.sourceforge.net/ Alvyn] ([http://www.dusabledanslherbe.eu/AROSPage/MISC.14.html download]) 


::[http://www.airsoftsoftwair.com/ Hollywood when enough users warrant a port - paid one time fee language] 


::[[Aros/Developer/Docs/E|AmigaE Portable E]]


====Hardware Restricted====

'''Basic'''

:[http://amos.pspuae.com/AmosProManual/contents/c1.html '''Amos Pro'''] [http://amos.pspuae.com/index.php?action=forum#1 compatible] [http://www.amigacoding.com/index.php/Main_Page commands] (all incomplete) 

:'''Blitz Basic''' [http://aros-exec.org/modules/newbb/viewtopic.php?post_id=46537#forumpost46537 none on AROS] 
:: [http://www.amiforce.de/main.php Amiblitz] on amiga(TM) emulator

:'''Amiga Basic'''
:: [ ACEBasic]

'''Misc''' 
:Ruby [http://www.ruby-lang.org/en Info]/[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/language Ruby 32bit PC], 


===Where to get the C/C++ Environment===

If you want to develop for AROS, its generally easier to be running linux hosted AROS development environment especially for C++, cross compiling the code. That's how most developers now are doing it. g++ is used to compile owb web browser as well as some other AROS software. If you were hoping for a rich set of C++ libraries or classes defined for the OS feature set, you might be disappointed.

AROS Native compiling is possible, but you're much more likely to run into the odd bug(s) in the dev environment since it gets little testing and fixing by other developers.

Is there a sftp software or scp over ssh available?
Maybe. At least the security part would be handled by [https://github.com/jens-maus/amissl amissl] [https://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc port]. [https://github.com/BlitterStudio/dopus5 DOpus5] has recently added sftp support. See here for a [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1974&amp;highlight=ssh&amp;pid=12073#post_12073 ssh scp client]

[https://arosdevteam.slack.com/join/shared_invite/enQtOTc4Mzg0NDIzNzQ0LWQ2NWZmNmMwNGIwNGEyNTgxNzU3MGFjMTk3ZThmOTQ1MTVjMzhmNTllYWQ0ZTUxMjBjMGE0Y2VjMDJmNTc5MzI#/shared-invite/email Slack Dev Forum] 


====Cross compilers from Windows or Linux====

*Windows WSL2 walkthrough can be [https://arosnews.github.io/how-to-cross-compile-aros-hosted-wsl/ found here] 


you want to build AROS. No problem.

Here are instructions for PC 64-bit:
https://github.com/deadw00d/AROS/blob/master/INSTALL.md

Here are instructions for PC 32-bit:
https://github.com/deadw00d/AROS/blob/alt-abiv0/INSTALL.md

And as always has been the case you can use the contrib archive to 'obtain' the development directory which contains the /native/ AROS gcc compiler and tools. That compiler is used to build AROS itself but can be used outside the AROS build process by providing --sysroot with indicated directory to cross compile for AROS.


'''64 bit'''


'''32 bit'''

A good option for multiple OS is [https://axrt.org/index.php?tab=download-aros AxRuntime lets developers compile their Amiga API-based applications as Linux binaries being able to utilize modern development tools available on Linux, like IDEs, debuggers, profilers, etc] 


Older 32bit guides for Linux hosted compiler

Please install these packages before moving to next step. Below is a reference list for Debian-based distributions. Reference build system was Ubuntu 18.04/20.04 amd64.

subversion git-core gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libx11-dev libxext-dev libc6-dev liblzo2-dev libxxf86vm-dev libpng-dev gcc-multilib libsdl1.2-dev byacc python-mako libxcursor-dev cmake zsh mingw64

Do all of these operations under home directory of your user or another directory where your user has write permissions.

Specifically, in a section &quot;Linux-i386&quot;, be sure first to build the cross-compiler (toolchain-alt-abiv0-i386) and only then AROS itself (alt-abiv0-linux-i386).


Clone &amp; build
&lt;pre&gt;
$ mkdir myrepo
$ cd myrepo
$ git clone https://github.com/deadw00d/AROS.git AROS
$ cd AROS
$ git checkout alt-abiv0
$ cd ..
$ cp ./AROS/scripts/rebuild.sh .
$ ./rebuild.sh
&lt;/pre&gt;

Now to the build selection below - Linux-i386 

Select toolchain-alt-abiv0-i386 - Select alt-abiv0-linux-i386 (DEBUG) 

Start AROS by:
&lt;pre&gt;
$ cd alt-abiv0-linux-i386/bin/linux-i386/AROS
$ ./Arch/linux/AROSBootstrap
&lt;/pre&gt;


Pc-i386 Select toolchain-alt-abiv0-i386 (if not built yet) - Select alt-abiv0-pc-i386

ISO image available in alt-abiv0-pc-i386/distfiles


Now that we have linux-hosted build, we can resume native (option 2).
Run ./rebuild.sh and selection option 2. Wait until it finished, then:
&lt;pre&gt;
$ cd alt-abiv0-pc-i386
$ make
&lt;/pre&gt;

Now
&lt;pre&gt;
$ make bootiso
&lt;/pre&gt;


Now, your compiler is located in toolchain-alt-abiv0-i386 directory and named i386-aros-gcc. Includes are in alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development/include and libraries are in alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development.lib.

This is how then can be passed to the compiler:

/home/xxx/toolchain-alt-abiv0-i386/i386-aros-gcc --sysroot /home/xxx/alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development -L/home/xxx/alt-abiv0-linux-i386-d/bin/linux-i386/AROS/Development/lib 

../toolchain-alt-abiv0-i386/i386-aros-gcc --sysroot bin/linux-i386/AROS/Development local/helloworld/helloworld.c -o local/helloworld/helloworld


Another method was using Debian like distros and download the gimmearos.sh script (on [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/cross aros-archives]) to setup the developer environment by downloading necessary packages ...
The gimmearos script is a good start in that direction, building the cross compilers and hosted AROS environment, but gimmearos.sh might be out of date or not be completely compatible with any given linux distro. 

In order to do that, you have to compile AROS yourself. Download AROS source archive not contrib. Compile AROS by entering the main directory

 ./configure
 make

([http://aros.sourceforge.net/documentation/developers/compiling.php More on compiling AROS]). The result will be a basic AROS system without development tools.

To compile C++ on Linux, type 'make gnu-contrib-crosstools', creating the cross-compilers in ./bin/linux-i386/tools/, named i386-aros-gcc, etc.

'''Note''': Currently, to make the cross compilers usable copy 'collect-aros' from tools/ to tools/i386-aros/bin/. At the moment the cross compilers if used from the Linux command line will only find it when it's there.

If you want to compile native compilers (the Developer Environment), type 'make contrib-gnu-gcc', creating native compilers in AROS' System:Development/bin directory.

When the output needs to be stripped &lt;code&gt;--strip-unneeded --remove-section .comment&lt;/code&gt;

The Obj-C backend should build out of the box.

Open contrib/gnu/gcc/mmakefile.src and search for the line which contains &quot;--enable-languages&quot; and add &quot;objc&quot; to the list of languages that follows it.

    --enable-languages=c,c++,objc

Better make it—enable-languages=c,c++,objc,obj-c++

ObjC++ is broken as soon as you try to use exceptions, but that might change in future GCC versions and it does not hurt having it there already.


Do you need a cross-compiler or a real compiler? In the first case you can get away with just downloading the proper gcc archive, apply the patch and proceed with the normal gcc build. In the case of a real cross-compiler then when downloading the contrib sources, also need to download the normal sources, place the contrib sources into a directory called contrib, need to install autoconf+automake+perl+python, call ./configure, cd into the subdirectory and type make.

to rebuild GCC with host == build == target == i386-pc-aros. So just get the vanilla sources and apply the patches without bothering about the build system?


[https://vmwaros.blogspot.com/2019/10/a-pre-configured-development-machine.html pre-configured VM environment vmware virtual machine to develop AROS and AROS software]


====Native compilers for AROS====

Namely gcc for C or g++ for C++ are supplied with the [[Aros/Developer/Docs#The Developer Environment|Developer Environment]], which is already '''setup''' and part of any current AROS distribution like AROS One or the nightlies 

* Current GCC 6.5 (32bit) though moving to 10.5 and 15.1 (64bit) 
* Older software components. GNU GCC 4.x GNU BinUtils, GNU Fileutils 4.x, GNU Textutils and others usually deprecated 

On single partition systems and the Boot ISO, the AROS Developer environment is installed under &quot;SYS:Development/&quot;. Systems with multiple partitions - such as a Work: partition - tend to install it to there instead, however it can be installed manually to any location. Please remember, if moving, that you will need to correct the Development packages 'install location' env variable to point to the new locations root - look in SYS:S/startup-sequence.

&lt;pre&gt;
Assign Development: SYS:Development 
Assign C: Development:bin ADD 
&lt;/pre&gt;


In the aros build instructions. you need to check out contrib and/or ports into your AROS source directory, as subdirs. then, assuming you are building in an external build dir, as you should, you simply configure and &quot;make contrib&quot; for instance or whatever submodule you might want to build.


===Beginners Tutorials in C C++===

As AROS is [http://eab.abime.net/showthread.php?t=29856 C based] API compatible to AmigaOS 3.x, so most of the information on programming C on the Amiga applies to AROS as well. Please note that there is a lot of AmigaOS 1.3 (1985-1989) and [https://www.markround.com/amigaguide AmigaOS AOS 2.x (1990-1992)] information around but OS3.1 is recommended but limited in amount. 

Brief overview of what is required to write AROS Applications

# Using [[Aros/Developer/Docs/Libraries/Intuition|Intuition]] for basic screens/windows 
# Using graphics within windows via 8bit [[Aros/Developer/Docs/Libraries/Graphics|graphics]] and so onto  15-16-24bit [[Aros/Developer/Docs/Libraries/CGFX|cybergraphx]]
# Load and save work to [[Aros/Developer/Docs/Libraries/DOS|dos]] disk drives
# Using the [[Aros/Developer/Zune|ZUNE GUI Environment]]


Writing native games require this extra information

# Using [[Aros/Developer/AHIDrivers|AHI audio hardware independent API]]
# Using USB joystick/joypad with the Poseidon USB stack through [[Aros/Developer/Docs/Libraries/LowLevel|LowLevel]] library


Additional features that could be added later

# Adding additional [[Aros/Developer/Docs/Libraries/Locale|Locale]] language translations to your program 
# Adding a [[Aros/Developer/Docs/Rexx|AREXX/Regina]] port to your application 
# Executing Amiga(TM) [[Aros/User/DOS|DOS]] commands from your application
# Using [[Aros/Developer/Docs/Libraries/Icon|icons]] (.info files) and icon tooltypes (stack, version, and program startup options)
# Local couch or IP based SANA2 networking co-op multi player gaming support 


Most AmigaOS programming books are nowadays very much out of date as most are from the late 1980s and do not cover later amigaOS releases like 3.1 for example, Rob Peck's book &quot;Programmer's Guide to the Amiga&quot;. The Amiga ROM Kernel manuals aka RKMs like Libraries (3rd edition), Devices (), the AmigaDOS manual (3rd edition) and the Style Guide may have their uses. There are some reference examples from AmigaMail and Devcon notes (available again on an Amiga developers CD 2.1). 

For Arexx then &quot;The Amiga Programmer's Guide to ARexx&quot; by Eric Giguere, which was published by Commodore is useful as well as an &quot;Arexx Cookbook&quot;.

Curly brackets missing - try SHIFT + ALT + 7 or 0.


* Beginners C Guide [http://www.iu.hio.no/~mark/CTutorial/CTutorial.html C Tutorial], 
* [http://thecguru.com/ C for beginners],
* [http://fresh2refresh.com/c/c-basic-program/ C programming basics] for students, 
* [https://www.edx.org/courses Free Online course] from American Universities 
* Reference Amiga [http://amigadev.elowar.com/ API reference].


* AROS based c source can be found [[Aros/Developer/Docs/Examples|here]] and lots of example code can be found inside [https://github.com/aros-development-team AROS sources] themselves and from the contrib section of the archives from [https://github.com/aros-development-team/contrib Aros site], and study the AROS applications source code, e.g. the test programs from the Tests drawer (folder/directory). Take a look at the code of some smaller AROS programs might be a better and more up to date 

When you upload your builds, please write the architecture (like i386-aros, x86_64-aros, armPi-64 etc.) in the archive name 
and it is also advisable to write in the field &quot;Requirements&quot; what ABI (ABIv1 or for PC forks ABIv11 or ABIv0) 


===Compiling C/C++ Code===

Native, although we have a IDE Integrated Development Environment (Murks), it does lack a debugger. Whilst others use a combination of a text editor and shell to edit code. Most though use an AROS hosted on Linux to take advantage of the better GCC tools like GDB and various IDEs.

Open shell - its a menu option at the top left of Wanderer (desktop). Or by using the right Win key and w (or F12 and w) within the directory with the source code. Type in
 sh 
to change the amiga shell into a unix shell. You can then type in ls (unix equivalent to amiga dir). Take a look [http://en.wikibooks.org/wiki/Linux_commands here] for more commands.

For a single file program-name.c or program-name.cpp
 gcc -o program-name program-name.c  
or 
 g++ -o program-name program-name.cpp
or
 g++ -o test -Wall -g main.cc texturelib.cpp xmodelib.cc -lsdl -lgl

To close the shell, click on the top left-hand corner to close (twice). Once to get back the aros shell and then again to close finally. Use [http://freshmeat.net/projects/cksfv/ cksfv] as a test.

Some source code requires the addition of Amiga API libraries, like dos, which you can flag at the compile time as 
 gcc -o julia.exe julia.c -ldos

For DOS use -ldos as example and if you are compiling mui codes it will be -lmui or intuition -lintuition. Other missing symbols are due to linker libraries being necessary for linking in functions that aren't in the standard C libraries. For example some source code would need added

 -lz or -lm or -lpng or -larosc etc.

use this in unix line command mode to search for 'search-item' in many .c files (*.cpp for c++, etc.)
 grep -l 'search-item' *.c

If the program is not executable, try using parameter fno-common 

&quot;Delete #?.o&quot;? Or if you are using abcshell then &quot;rm *.o&quot;


:''More information: [[Aros/Developer/Porting software]]''


=== How to make Apps have AROS 64-bit specific support code ===

[http://www.aros.org/cs/documentation/developers/app-dev/portable.php Portable code] 

AROS64 already uses 64bit addressing, it just doesn't setup the MMU for more than 4GB physical memory currently.
When porting software to AROS64 it is &quot;mostly&quot; a case of converting ULONG's that are used to store pointers, into IPTR's instead, etc. Another quirk, is making sure items on the stack are the correct size by using the STACKED attribute for them. 

* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.

compiling mui stuff for aros setting -std=gnu99 is necessary, had -std=c99 usually 
A MUI application most likely needs only the HOOKPROTOxxx SDI macros. They are compatible with AROS, only the attributes (hook, object attribute) must be given in the right order.

crash which suggest memory corruption. From my experience porting from 32-bit to 64-bit these kinds of errors can happen if a pointer is passed somewhere via ULONG variable. Then half of the pointer is cut.

To generate this error, please run AROSBootstrap with -m 1024. This will allocate heap to 64-bit address space which will make these errors immediatelly visible. These types of crashes are hard to debug. Disabled as little code as possible to stop corruption from occurring and then try to read from the code where it can be broken

Crashing in tslf_freevec is another symptom of memory corruption and these memory corruptions will manifest differently on different setups.


==Coding conventions==

As the AROS core source is a shared developer experience, there are rules regarding structure and style. When it comes to your creating your own app and coding, the structure and style should be your own, i.e. you should enjoy what you do and do it so that you can understand what is going on.

===Layout===

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
static void 1st_function()
{
    program
    exit(0);    
}

int main(void)
{
    1st_function();
    2nd_function();
    3rd_function();
    return 0;
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;

struct Screen * openscreen(void);
struct Window *openwindow(struct Screen *screen, const char *title, LONG x, LONG y, LONG w, LONG h);

VOID 1st_function();
VOID 2nd_function();

int main(int argc, char **argv)
{
    program
    return 0;
} /* main */

VOID 1st_function()
{

}

VOID 2nd_function()
{

}
&lt;/syntaxhighlight&gt;

===General style===

This code is used by many people and therefore you should keep some things in mind when you submit source code:

* Keep things simple 
* Keep the source clean 
* Always know what you are doing, if not flag it and describe what needs to be done... 
* Explain clearly/simply what you are doing 
* Remember that you write code once but that it is read many times by many people

===Comments===

AROS uses some of the comments in the source to generate the documentation. Therefore it's necessary to keep a certain format so the tools can find their information. Other comments are ignored but they should explain what you thought when you wrote the code. If you really can't think of an explanation, then don't write the code a second time like this:

&lt;pre&gt;
/* This adds 1 to t */
t ++;
&lt;/pre&gt;

What we think of is this:

&lt;pre&gt;
/* Go on with next element */
t ++;
&lt;/pre&gt;

===Formatting===

This is only '''IMPORTANT''' if you are going to work on the core AROS code or contrib but not applications which may reside outside like on AROS Archives or other websites.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
{
    /* a */
    struct RastPort * rp;
    int               a;

    /* b */
    rp = NULL;
    a  = 1;

    /* c */
    if (a == 1)
        printf (&quot;Init worked\n&quot;);

    /* d */
    if
    (
        !(rp = Get_a_pointer_to_the_RastPort
            (
                some
                , long
                , arguments
            )
        )
    ||
        a &lt;= 0
    )
    {
        printf (&quot;Something failed\n&quot;);
        return FAIL;
    }

    /* e */
    a = printf (&quot;My RastPort is %p, a=%d\n&quot;
        , rp
        , a
    );

    return OK;
}
&lt;/syntaxhighlight&gt;

Looks ugly, eh ? :-) Ok, here are the rules:

&lt;pre&gt;
If several lines contain similar code, put similar things below each other (see a and b);
Put spaces between operands and operators
Put braces {}, brackets [] and parentheses () below each other (d) if there is much code between. 
Brackets and parentheses may be in one line if the code between is small (c)
Indent by 4 Spaces. Two indent levels may be abbreviated by one tab.
&lt;/pre&gt;

'''Before committing please normalize the indentation - if you have a mixture of tabs and spaced - please always use spaces, 1 tab = 4 spaces.'''

The reasons for this are:

# While some editors can use an arbitrary sizes for tabs, it's a bit complicated to tell another editor which tab size was used by the one used to write the code. 
# Most code in AROS was written this way and your code should look like the rest. 
# You can print this code on any printer without special tools to &quot;fix&quot; the tabs. 
# Most editors have smart tabs which do exactly this. If your editor doesn't, write a bug report.

If you have a function with many arguments (d, e) you should put the parentheses in lines of their own and each argument in one line (d) or put the first argument behind the opening parentheses (e) and each following argument in a line of its own with the comma in front. The closing parentheses is in a line of its own and aligned with the beginning of the expression (i.e. the a and not the opening parentheses or the printf()).

Use a single blank line to separate logical blocks. Large comments should have a blank line before and after them, small comments should be put before the code they explain with only one blank line before them.

If you see any TABS in AROS core sources then the suggestion is to &quot;detab the file and commit that separately&quot; either before or afterwards from making functionality changes. Make two commits instead of one. This makes it easier for others to see the real changes instead of having to dig through multiple lines of irrelevant diffs.

===Eliminating Global Variables===

i.e. pass variables to functions (local scope) or classes making it easier to track and debug your code.

Any time you find that you need a particular thing in 'a lot of different places', chances are that all those places are conceptually related, and so you can create a class, a namespace, a function, or some other higher-level organizational unit to represent that relationship. This makes the program easier to understand.

Bad Designs

* All variables are global. 
* There are no standalone functions, only sub-procedures which act on the global variables. 
* Every sub-procedure is at least 500 lines to several thousand 
* Every sub-procedure has more than one task to perform 
* Copy-paste is preferred to writing methods, AND subtle changes are made in the middle of the code

Good Designs

* structure program into functions (C or basic) - top-down procedural approach 
* put in class(es) (freepascal or C++) - the object is fixed and you use methods to access the object

&lt;pre&gt;
 class String_List
 {
 private:
 list&lt;string&gt; m_List;  // member
 public:
 void read_strings() { /* read strings into m_List */ }
 void print_strings() { /* write contents of m_List to stdout */ }
 void sort_strings() { /* sort contents of m_List */ }
 void sort_strings_reverse() { /* reverse-sort contents of m_List */ }
 void unique_strings() { /* remove duplicate strings */ }
 };

 int main()
 {
 String_List myList;  // local
 myList.read_strings();
 myList.sort_strings();
 myList.print_strings();
 myList.sort_strings_reverse();
 myList.print_strings();
 myList.unique_strings();
 myList.print_strings();
 return 0;
 }
&lt;/pre&gt;

This way it is very easy to replace the list with new list for debugging purposes, or replacing the methods without replacing the list, when you want different results. You only have to replace the content of the local variables.

 So create the structure that matches your data (linked lists, trees, arrays, etc.) and what to do with them (sorting, searching, etc.)

&lt;pre&gt;
.h usually contain #define #include typedef enum struct extern screen and window definitions (data structures)
.c should contains functions and algorithms
&lt;/pre&gt;

One way to look at it is that menu headings act as the .c file and sub-menu headings as functions.

When you start a project, you place a couple of declarations in the include file. As the project continues, you place more and more declarations in the include file, some of which refer to or contain previous declarations. Before you know it, you have a real mess on your hands. The majority of your source files have knowledge of the data structures and directly reference elements from the structures.
Making changes in an environment where many data structures directly refer to other data structures becomes, at best, a headache. Consider what happens when you change a data structure.

Use good variables names to help clarify code and only comment when you need to explain why a certain programming approach was made.

You're Refactoring Legacy Code, you see a global, you want to get rid of it. How do you do this?

Exactly what to do depends on how the global is used. The first step is to find all uses of the global throughout the code, and get a feel for what the significance of the variable is and how it relates to the rest of the program. Pay particular attention to the &quot;lifetime&quot; of the variable (when it gets initialized, when it is first used, when it is last used, how it gets cleaned up). Then, you will probably make the global a data member of a class (for OO languages), or you will write some get/set functions. Converting to the Singleton Pattern is common, but you may discover that it makes more sense for the data element to be a member of an existing singleton, or maybe even an instance variable.

# Create a basic read method, either as a class or a global function. Replace all reads with the access method, but leave the variable defined as a global.
# Review each of the writes to the method and extract action functions one at a time. Unless two operations are coded identically in the original code, extract each write access separately.
# Change the variable scope from global to local.
# Analyze similar action functions to determine if any can be merged, i.e., there are no functional differences in the results of the function, just differences in the implementation details.
# Review the calls to the read method and see if a more complex functionality should be applied. Follow the approach for writes and unless implementations are identical, create separate access functions. 
# Analyze the access functions for duplication.

As returning variables by &quot;passing by value&quot; are forgotten, so &quot;passing by reference&quot; is often used instead. The reference is a pointer to the variable so the value is remembered when returned.

Alternatives

* Hidden Globals
* Singleton Pattern
* Database or TupleSpace
* Context Object 
* Dependency Injection 
* Stateful Procedures


==AROS/AmigaOS APIs and Docs==

&lt;pre&gt;
Library:
   - Private data structure
   - Many public access methods

Device:
   - Private data structure
   - Two (BeginIO/AbortIO) access methods

Resource:
   - Public data structure
   - *NO* access methods
&lt;/pre&gt;

And, being Amiga OS-compatible, there are exceptions to all of these.


===System Libraries===

The [http://developers.aros.org/ AROS Guide To Libraries] can be used as a guide to individual commands and old Dev Docs are used in application programming.

Amiga/Aros styles libraries are very different from windows and linux libs. Typical .so/dll libraries are foreign to most Amiga-like OS 


*[[Aros/Developer/Docs/Libraries/AROSC|arosc.library]]
*[[Aros/Developer/Docs/Libraries/AmigaGuide|amigaguide.library]]
*[[Aros/Developer/Docs/Libraries/ASL|asl.library]]
*[[Aros/Developer/Docs/Libraries/Bullet|bullet.library]]
*[[Aros/Developer/Docs/Libraries/BSDsocket|bsdsocket.library]]
*[[Aros/Developer/Docs/Libraries/CAMD|camd.library]]
*[[Aros/Developer/Docs/Libraries/Codesets|codesets.library]]
*[[Aros/Developer/Docs/Libraries/CGFX|cybergraphics.library]]
*[[Aros/Developer/Docs/Libraries/CGXVIDEO|cgxvideo.library]]
*[[Aros/Developer/Docs/Libraries/Commodities|commodities.library]]
*[[Aros/Developer/Docs/Libraries/DataTypes|datatypes.library]]
*[[Aros/Developer/Docs/Libraries/DiskFont|diskfont.library]]
*[[Aros/Developer/Docs/Libraries/DOS|dos.library]]
*[[Aros/Developer/Docs/Libraries/Exec|exec.library]]
*[[Aros/Developer/Docs/Libraries/Expansion|expansion.library]]
*[[Aros/Developer/Docs/Libraries/FreeType2|freetype.library]]
*[[Aros/Developer/Docs/Libraries/GadTools|gadtools.library]]
*[[Aros/Developer/Docs/Libraries/Graphics|graphics.library]]
*[[Aros/Developer/Docs/Libraries/Icon|icon.library]]
*[[Aros/Developer/Docs/Libraries/Identify|identify.library]]
*[[Aros/Developer/Docs/Libraries/IFFParse|iffparse.library]]
*[[Aros/Developer/Docs/Libraries/Intuition|intuition.library]]
*[[Aros/Developer/Docs/Libraries/Keymap|keymap.library]]
*[[Aros/Developer/Docs/Libraries/Layers|layers.library]]
*[[Aros/Developer/Docs/Libraries/Locale|locale.library]]
*[[Aros/Developer/Docs/Libraries/LowLevel|lowlevel.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEESingBas|mathieeesingbas.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEEDoubBas|mathieeedoubbas.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEESingTrans|mathieeesingtrans.library]]
*[[Aros/Developer/Docs/Libraries/MathIEEEDoubTrans|mathieeedoubtrans.library]]
*[[Aros/Developer/Docs/Libraries/Mathtrans|mathtrans.library]]
*[[Aros/Developer/Docs/Libraries/MUIMaster|muimaster.library]]
*[[Aros/Developer/Docs/Libraries/Partition|partition.library]]
*[[Aros/Developer/Docs/Libraries/PopUpMenu|popupmenu.library]]
*[[Aros/Developer/Docs/Libraries/OOP|oop.library]]
*[[Aros/Developer/Docs/Libraries/Regina|regina.library]]
*[[Aros/Developer/Docs/Libraries/Reqtools|reqtools.library]]
*[[Aros/Developer/Docs/Libraries/RexxSysLib|rexxsyslib.library]]
*[[Aros/Developer/Docs/Libraries/ScreenNotify|screennotify.library]]
*[[Aros/Developer/Docs/Libraries/TTEngine|ttengine.library]]
*[[Aros/Developer/Docs/Libraries/Thread|thread.library]]
*[[Aros/Developer/Docs/Libraries/Utility|utility.library]]
*[[Aros/Developer/Docs/Libraries/Xadmaster|xadmaster.library]]
*[[Aros/Developer/Docs/Libraries/Workbench|workbench.library]]
*[https://github.com/aros-development-team/AROS/commit/c82e86b8480277998014cc327b56c7664023a52f ClassAct Reaction boopsi class]


===AROS Subsystems===

# [[Aros/Developer/Zune|Zune MUI compatible GUI]]
# [[Aros/Developer/AROSAppPackages|AROS Application Packages]]
# AHI Audio Drivers - [[Aros/Developer/AHIDrivers|Usage]]/[[Aros/Developer/AHIDriversDev|Development]]
# AROSTCP Sana2 Network Interface Drivers - [[Aros/Developer/NICDrivers|Usage]]/[[Aros/Developer/NICDriversDev|Development]]
# [[Aros/Developer/AmiSSL|AmiSSL]]
# gfx.hidd/cybergraphics Video Drivers - [[Aros/Developer/GfxDrivers|Usage]]/[[Aros/Developer/GfxDriversDev|Development]]
# IO Device Drivers - [[Aros/Developer/IODeviceDrivers|Usage]]/[[Aros/Developer/IODeviceDriversDev|Development]]
# USB Device Drivers - [[Aros/Developer/USBDrivers|Usage]]/[[Aros/Developer/USBDriversDev|Development]]
# PCI Device Drivers - [[Aros/Developer/PCIDrivers|Usage]]/[[Aros/Developer/PCIDriversDev|Development]]
# [http://www.libsdl.org/ SDL] [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2013&amp;pid=13333#post_13333 SDL2 coding usage], [https://github.com/search?q=repo%3Aaros-development-team%2Fcontrib%20SDL2&amp;type=code SDL2 commits], [https://github.com/aros-development-team/contrib/commit/c62c3c425c35bac19dadc23be092b0b13a66c76c SDL3 initial commit], []
# [[w:Gallium3D|Gallium 3D]] [http://www.mesa3d.org/ openGL aka Mesa] - [[Aros/Developer/OpenGL|Usage]]/[[Aros/Developer/OpenGLDev|Development]] [http://www.swiftless.com/opengltuts.html Swfitless]
# A small subset of GTK2 through [http://sourceforge.net/projects/gtk-mui/ MUI-GTK] 
# Cairo 2D Engine - [[Aros/Developer/Cairo|Usage]]/[[Aros/Developer/Cairo|Development]]
# [[Aros/Developer/Scalos|Scalos desktop API and plugin modules]]
# [[Aros/Developer/VHI|VHI video driver]]


====HIDDs====

*[[Aros/Developer/Docs/HIDD/HIDDClass|hiddclass.hidd]]
*[[Aros/Developer/Docs/HIDD/Graphics|graphics.hidd]]
*[[Aros/Developer/Docs/HIDD/VesaGfx|vesagfx.hidd]]
*[[Aros/Developer/Docs/HIDD/ATI|radeon.hidd]]
*[[Aros/Developer/Docs/HIDD/NVidia|nvidia.hidd]]
*[[Aros/Developer/Docs/HIDD/Nouveau|nouveau.hidd]]
*[[Aros/Developer/Docs/HIDD/Kbd|kbd.hidd]]
*[[Aros/Developer/Docs/HIDD/Mouse|mouse.hidd]]
*[[Aros/Developer/Docs/HIDD/i2c|i2c.hidd]]
*[[Aros/Developer/Docs/HIDD/IRQ|irq.hidd (deprecated)]]
*[[Aros/Developer/Docs/HIDD/PCI|pci.hidd]]
*[[Aros/Developer/Docs/HIDD/PCIPC|pcipc.hidd]]
*[[Aros/Developer/Docs/HIDD/Serial|serial.hidd]]
*[[Aros/Developer/Docs/HIDD/Thunderbolt|thunderbolt.hidd]]
https://github.com/aros-development-team/AROS/commit/4f02ea691799aff3a01f60cfa5f9182c82fc57a8

HIDD are used for device/peripheral low level hardware support drivers. The HIDD system is split up into a collection of classes with a strict inheritance hierarchy. A HIDD class implements a device driver for a single device or in rare cases a group of devices and provides an interface for other programs and devices to access.
      
In order to maintain portability of interfaces across a wide range of hardware this interface will in general not present the raw interface to the underlying hardware. Instead it will present a generic interface that describes many different hardware implementations. This allows for the best reuse of both interfaces and code.

HIDD API is heavyweight though. You need to open a HIDD library, open oop.library, instantiate an object (even if there's no object); and object calls are more costly compared to plain library calls.


Basically your task is to implement a subclass of hidd.ata.bus for your hardware. just implementing the XXXATA__Hidd_ATABus__xxxxxx methods for the Amiga chipset - and appropriate versions of the interface_xxx.c file(s). pretty much everything in probe.c could be ignored - just write a replacement scan for relevant amiga devices and store whatever info you need in the bus data? only the &quot;SUPPORT_LEGACY&quot; blocks might be related.

You do not need to depend on PCI API. PCI is just a way to discover the hardware on PCs, etc. 
&lt;hidd/pci.h&gt; includes (at some depth) &lt;interface/HW.h&gt;, which defines IID_HW. This comes from the 'generic' HIDD class in: 
 rom/hidds/hidd/hiddclass.conf
did not split up HIDD and HW because they are always used in pair. It's the same as hidd/pci.h bringing definition for: PCI, PCIDriver and PCIDevice. PCI is actually PCIHW, just the name was not changed for backwards compatibility reasons. HW is a 'hub' where HIDD instances plug in.

ATA HIDD aoHidd_ATABus_Use32Bit value is completely ignored unless ata.device first detects correct command line parameter.
Yes. Unfortunately I was unable to find any comment in code or svn history with explanations. Looked  at Linux source, there 32-bit PIO is also controller driver's property. Some of them enable it, some don't.

Actually, switching the default to ON should be safe. ata.device is fail-safe at this because during IDENTIFY command it validates upper 16  bits,  and  if they appear to be zeroes in all 128 longwords, then 32-bit mode is switched off. But, nevertheless, I know how tricky hardware can be, so I decided not to change original behavior. If  you think it's wrong in some cases, then it's possible to add one more  attribute  like  aHidd_ATABus_Default32Bit. If set to YES, then  this means that 32-bit PIO is safe to use by default.


====Devices====

*[[Aros/Developer/Docs/Devices/ATA|ata.device]]
*[[Aros/Developer/Docs/Devices/Console|console.device]]
*[[Aros/Developer/Docs/Devices/Narrator|narrator.device]]
*[[Aros/Developer/Docs/Devices/Printer|printer.device]]
*[[Aros/Developer/Docs/Devices/Trackdisk|trackdisk.device]]
*[[Aros/Developer/Docs/Devices/AmberRAM|amberram.device]]
*[[Aros/Developer/Docs/Devices/Timer|timer.device]]
*[[Aros/Developer/Docs/Devices/|.device]]

The Amiga used [[Aros/Developer/Docs/Devices|Devices]] to communicate with [http://aros-exec.org/modules/newbb/viewtopic.php?start=0&amp;topic_id=3475&amp;viewmode=flat&amp;order=ASC additional hardware]. AROS has replaced these hardware devices with hidd equivalents but some are still retained for backwards compatibility.

Local libraries/devices/handlers,etc. are supposed to override the ones in ROM if their version is higher than the one in ROM.

Here is the list of commands exec default: 
{| class=&quot;wikitable&quot;
| CMD_CLEAR
|  Purge the buffer of the device
|----
| CMD_READ
|  Playback Control
|----
| CMD_STOP
|  Stopped the activity of the device
|----
| CMD_FLUSH
|  Empty the queue of commands
|----
| CMD_RESET
|  Reset a device
|----
| CMD_WRITE
|  Playback Control
|----
| CMD_INVALID
|  Create an error
|----
| CMD_UPDATE
|  Gets updated device
|----
| CMD_START
|  Will restart the device
|----
|}

While most other &quot;stuff you communicate with&quot; in AmigaOS are devices &lt;ref&gt;AMIGA ROM Kernel Reference Manual: Devices, 3rd Edition. Commodore-Amiga, Inc. Addison-Wesley, 1991. {{ISBN|0-201-56775-X}}&lt;/ref&gt; that share a [http://gega.homelinux.net/AmigaDevDocs/ common base interface]. [[Aros/Developer/Docs/Devices1.3|OS 1.3 Device Drivers]].


====Handlers====

:[[Aros/Developer/Docs/Handlers/Pipe|pipe.handler]]
:[[Aros/Developer/Docs/Handlers/Port|port.handler]]
:[[Aros/Developer/Docs/Handlers/SFS|sfs.handler]]
:[[Aros/Developer/Docs/Handlers/FAT|fat.handler]]
:[[Aros/Developer/Docs/Handlers/PFS|pfs.handler]]
:[[Aros/Developer/Docs/Handlers/NTFS|fuse.handler]]
:[[Aros/Developer/Docs/Handlers/FFS|ffs.handler]]

filesystem handlers have their own separate system consisting of completely differently structured messages that dos.library use to pass requests (for things like reading, writing, getting directory contents etc.) to them. AROS originally went with implementing filesystem handlers as devices, which might arguably be more consistent with the rest of the AmigaOS API but which is quite incompatible with AmigaOS itself. However, it made it far harder to port filesystems and the gains were comparatively small, and so there's been a long standing goal of fixing this incompatibility. It has now, June 2011, been reintroduced to all AROS flavors.

are argstr and argsize valid for the handler startup environment?
DOS/RunHandler() calls DOS/CreateNewProcTags(), and then CallEntry() (in rom/dos/exit.c) to start the handler, so yes, argstr and argsize are *present* in the call signature of the handler.

Granted, argstr will be NULL and argsize 0, but those values *are* passed to the handler function using:

&lt;pre&gt;
AROS_UFC3(ULONG, entry,
                         AROS_UFCA(STRPTR, argptr, A0),
                         AROS_UFCA(ULONG, argsize, D0),
                         AROS_UFCA(struct ExecBase *, SysBase, A6));
&lt;/pre&gt;

Creating your own [without the whole build tree http://pagesperso-orange.fr/franck.charlet/temp/radeon.zip] and then  
&lt;pre&gt;
make stub
make
make install
&lt;/pre&gt;

SFS has two Root blocks, one at the start and one at the end of the disk. The Root blocks both contain the same information.  They hold various information about the disk structure and have the locations of some important blocks used by the filesystem.  

The Root ObjectContainer contains the Root directory Object. The name of this Object is the name of the volume. It is identical to a normal directory Object.

The Bitmap is used to keep track of free space. Each bit in a bitmap represents a single block. A set bit indicates a free block and a cleared bit a used block.

AdminSpaceContainers are used to keep track of space which has been reserved for storing administration blocks. Only the Bitmap, the Root blocks and the actual data stored in files aren't stored in administration space. Administration space is allocated in chunks of 32 blocks at a time. A single AdminSpaceContainer can hold information about a large number of such areas each of which has its own little bitmap of 32 bits.

Extents are stored in a B-Tree. The Root block holds a pointer to the root of the Extent B-Tree. Extents keep track of space in use by a specific file. Each fragment a file consists of has its own Extent. Extents are in a double linked list. The list can be used to locate the next or previous fragment of a file.

Below is the standard block header. This header is found before EVERY type of block used in the filesystem, except data blocks.  The id field is used to check if the block is of the correct type when it is being referred to using a BLCK pointer.  The checksum field is the SUM of all LONGs in a block plus one, and then negated. When applying a checksum the checksum field itself should be set to zero. The checking a checksum the checksum is okay if the result of the checksum equals zero. The ownblock BLCK pointer points to the block itself. This field is an extra safety check to ensure we are using a valid block.

Field	Type	Description
id	ULONG	The id field is used to identify the type of block we are dealing with. It is used to make sure that when referencing a block we got a block of the correct type. The id consist of 4 bytes and each blocktype has its own unique foure letter code.
checksum	ULONG	This field contains the sum of all longs in this block, plus one and then negated. The checksum can be used to check if the block hasn't been corrupted in any way.
ownblock	BLCK	Points to itself, or in other words, this field contains the block number of this block. This is yet another way to check whether or not a block is valid.

&lt;pre&gt;
struct fsBlockHeader {
    ULONG id;
    ULONG checksum;
    BLCK ownblock;
};
&lt;/pre&gt;
The algorithm to calculate the checksum of a block:
&lt;pre&gt;
ULONG calcchecksum(struct fsBlockHeader *block, LONG blocksize} {
    ULONG *data=(ULONG *)block;
    ULONG checksum=1;

    block-&gt;checksum=0;

    while(blocksize&gt;0) {
        checksum+=*data++;
        blocksize-=4;
    }

    return(-checksum);
} 
&lt;/pre&gt;

A Root block contains very important information about the structure of a SFS disk. It has information on the location and size of the disk, the blocksize used, locations of various important blocks, version information and some filesystem specific settings.

A SFS disk has two Root blocks; one located at the start of the partition and one at the end. On startup the filesystem will check both Roots to see if it is a valid SFS disk. If either one is missing SFS can still continue (although at the moment it won't).

A Root block could be missing on purpose. For example, if you extend the partition at the end (adding a few MB's) then SFS can detect this with the information stored in the Root block located at the beginning (since only the end-offset has changed).   Same goes for the other way around, as long as you don't change start and end point at the same time.

When a Root block is missing because the partition has been made a bit larger, then SFS will in the future be able to resize itself without re-formatting the disk.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
version	UWORD	The version of the filesystem block structure. You can check this field to identify what version of the filesystem your dealing with it and to see if you can handle this structure correctly. Don't try to interpret the disk's structure when this field contains an unknown version number!

sequencenumber	UWORD	Used to identify which Root block was written last in case the sequencenumber on both Root blocks don't match.
datecreated	ULONG	Creation date of this volume. This is the date when the disk was last formatted and will never be changed.

bits	UBYTE	Various settings, see below.
&lt;pre&gt;
pad1	UBYTE	Reserved, leave zero.
pad2	UWORD	Reserved, leave zero.
reserved1	ULONG[2]	Reserved, leave zero.
firstbyteh	ULONG	High 32-bits of a 64-bit number. This is the first byte of our partition relative to the start of the disk.
firstbyte	ULONG	Low 32-bits of a 64-bit number.
lastbyteh	ULONG	High 32-bits of a 64-bit number. This is the last byte (exclusive) of our partition relative to the start of the disk.
lastbyte	ULONG	Low 32-bits of a 64-bit number.
totalblocks	ULONG	The total number of blocks this partition consists of.
blocksize	ULONG	The size of a block of this partition.
reserved2	ULONG[2]	Reserved, leave zero.
reserved3	ULONG[8]	Reserved, leave zero.
bitmapbase	BLCK	Block number of the start of the Bitmap.
adminspacecontainer	BLCK	Block number of the first AdminSpaceContainer.
rootobjectcontainer	BLCK	Block number of the ObjectContainer which contains the root of the disk (this is where the volume name is stored).
extentbnoderoot	BLCK	Block number of the root of the Extent B-Tree.
reserved4	ULONG[4]	Reserved, leave zero.
&lt;/pre&gt;

&lt;pre&gt;
struct fsRootBlock {
  struct fsBlockHeader bheader;
  UWORD version;
  UWORD sequencenumber;
  ULONG datecreated;
  UBYTE bits;
  UBYTE pad1;
  UWORD pad2;
  ULONG reserved1[2];
  ULONG firstbyteh;
  ULONG firstbyte;
  ULONG lastbyteh;
  ULONG lastbyte;
  BLCK  totalblocks;
  ULONG blocksize;
  ULONG reserved2[2];
  ULONG reserved3[8];
  BLCK  bitmapbase;
  BLCK  adminspacecontainer;
  BLCK  rootobjectcontainer;
  BLCK  extentbnoderoot;
  ULONG reserved4[4];
};
&lt;/pre&gt;

AdminSpaceContainers are used to store the location and bitmap of each administration space. The AdminSpaceContainers are located in a double linked list and they contain an array of fsAdminSpace structures.  There is one fsAdminSpace structure for every administration space on disk.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
next	BLCK	The next AdminSpaceContainer, or zero if it is the last in the chain.
previous	BLCK	The previous AdminSpaceContainer, or zero if it is the first AdminSpaceContainer.
bits	UBYTE	The number of bits in each in the bits ULONG in the fsAdminSpace structure.
pad1	UBYTE	Reserved, leave zero.
pad2	UWORD	Reserved, leave zero.
adminspace	struct fsAdminSpace	An array of fsAdminSpace structures. The size of the array is determined by the current blocksize.
&lt;pre&gt;
struct fsAdminSpaceContainer {
  struct fsBlockHeader bheader;
  BLCK next;
  BLCK previous;
  UBYTE bits;
  UBYTE pad1;
  UWORD pad2;
  struct fsAdminSpace adminspace[0];
};
&lt;/pre&gt;
Field	Type	Description
space	BLCK	The first block of an administration space.
bits	ULONG	A small bitmap which is used to determine which blocks in an administration space are already in use. The number of bits in this bitmap is determined by the bits field in the AdminSpaceContainer.
&lt;pre&gt;
struct fsAdminSpace {
  BLCK  space;
  ULONG bits;
};
&lt;/pre&gt;

The fsBitmap structure is used for Bitmap blocks. A bitmap block is used to keep track of which space is in use and which isn't for a particular area of a disk.  All bitmap blocks together keep track of the free space for an entire disk. The location of the first bitmap block is known and all other bitmap blocks are stored in order after the first one.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
bitmap	ULONG	An array of ULONG's.  These hold the actual information on which blocks are in use and which aren't.
&lt;pre&gt;
struct fsBitmap {
    struct fsBlockHeader bheader;
    ULONG bitmap[0];
};
&lt;/pre&gt;
Each bit in a bitmap block (except for the block header) represents a single block. If the bit is set than the block is free, and if the bit is clear then it is full. The first ULONG in the bitmap area of the first bitmap block represents blocks 0 through 31 on the disk. Bit 31 of this ULONG is block 0, 30 is block 1, and so on. Bit 0 of the first ULONG represents block 31.

Below is a table to clarify how bitmaps work even further. The first column is the bitmap block number, the second column is the number of the ULONG in the bitmap array. The third column is the bit number in this ULONG, and the last column is the block which this specific bit, in this specific bitmap block represents.

We'll assume here that a bitmap block has room for 120 ULONG's (meaning there is room for storing 32 * 120 bits).

&lt;pre&gt;
Bitmap block	ULONG number	Bit number	Block represented
1 (first)	0	31	0
1	0	30	1
...	...	...	...
1	0	1	30
1	0	0	31
1	1	31	32
...	...	...	...
1	2	31	64
1	2	30	65
...	...	...	...
1	119	0	3839
2	0	31	3840
2	0	30	3841
...	...	...	...
&lt;/pre&gt;
The last bitmap block doesn't need to be completely used. The unused bits (which belong to blocks which do not exist) all have to be clear, to indicate that these blocks are in use.

The fsObjectContainer structure is used to hold a variable number of fsObjects structures (Objects) which have the same parent directory. Each ObjectContainer must contain at least one Object. If there is space in the ObjectContainer not used by the variable number of Objects then that space is zero filled. Objects always start at 2-byte boundaries, which means sometimes a padding byte is inserted between two Objects.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
parent	NODE	The node number of the parent Object, or 0 if this object has no parent (which is only the case for the Root directory).
next	BLCK	The next ObjectContainer belonging to this directory, or zero if it is the last in the chain.
previous	BLCK	The previous ObjectContainer belonging to this directory, or zero if it is the first ObjectContainer in this directory.
object	struct fsObject	A variable number of fsObject structures. The number of structures depends on the individual sizes of each fsObject structure and the blocksize. These structures are located directly after each other with at most 1 byte of padding between them to get the structures aligned on a 2 byte boundary.
&lt;pre&gt;
struct fsObjectContainer {
    struct fsBlockHeader bheader;
    NODE parent;
    BLCK next;
    BLCK previous;
    struct fsObject object[0];
}; 
&lt;/pre&gt;

fsHashTable is the structure of a HashTable block. It functions much like the hash table found in FFS user directory blocks, except that it is stored in a separate block. This block contains a number of hash-chains (about 120 for a 512 byte block). Each hash-chain is a chain of Nodes. Each Node has a pointer to an Object and a pointer to the next entry in the hash-chain.  Using such a hash-chain you can locate an object quickly by only knowing its name.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
parent	NODE	The node number of the directory Object this HashTable block belongs to.
hashentry	NODE	An array of Nodes. Each Node represents the start of a hash-chain (singly linked). A hash-value is calculated using the name of a file or directory, and this value determines in which chain the Object is linked. If there are no entries in a hash-chain then the hashentry value is zero.
&lt;pre&gt;
struct fsHashTable {
    struct fsBlockHeader bheader;
    NODE parent;
    NODE hashentry[0];
};
&lt;/pre&gt;
To calculate the hash-value using a name of an Object as input use these routines:
&lt;pre&gt;
UWORD calchash(UBYTE *name) {
    UWORD hash=0;
    /* Calculates a hash value over the passed in string.
       The end of the string can be either a NUL byte or a
       slash. The hash function is the same as the one
       used in FastFileSystem set to international mode. */
    while(name[hash]!=0 &amp;&amp; name[hash]!='/') {
        hash++;
    }
    while(*name!=0 &amp;&amp; *name!='/') {
        hash=hash*13+upperchar(*name++);
    }

    return((UWORD)(hash % (UWORD)((blocksize-sizeof(struct fsHashTable))&gt;&gt;2)));
}
UBYTE upperchar(UBYTE c) {
    if((c&gt;=224 &amp;&amp; c&lt;=254 &amp;&amp; c!=247) || (c&gt;='a' &amp;&amp; c&lt;='z')) {
        c-=32;
    }
    return(c);
}
&lt;/pre&gt;

The BNodeContainer is used to store B-Trees. Currently only one B-Tree is in use by this filesystem and it is used to store the location of file data. The fsBNodeContainer structure contains two other structures. The fsBlockHeader structure and the BTreeContainer structure.

Field	Type	Description
bheader	struct fsBlockHeader	Standard block header.
btc	struct BTreeContainer	Contains information about the B-Tree and its nodes contained in this block.
&lt;pre&gt;
struct fsBNodeContainer {
    struct fsBlockHeader bheader;
    struct BTreeContainer btc;
}; 
&lt;/pre&gt;


First try and locate the Root block. It should start with &quot;ROOT&quot;.  SFS has two of these, one at the start of the partition and one at the end.  One of the fields contains the block size, which will be the size of all important SFS blocks.

The root block has the root object container, which contains information about files and directories in the root directory.  The object 
containers basically hold one or more smaller structures that represent files and directories.  Scanning them all should give you a list of 
files and directories.

The root block also has the root of the Extent B-Tree.  This is a standard B-Tree structure (not a binary tree) that is used commonly in 
all kinds of system, you can read about how they work on Wikipedia if needed.  The B-Tree holds the information about *where* all the data is 
located for your files.

To recover your files, I'd do this:

* Find one of the root blocks, if not present, then figure out the block size your disk was using, and scan every block in turn to see if it 
looks like an ObjectContainer (check the fsBlockHeader's ID, check if the ownblock number is equal to the block you are currently scanning, 
and check its checksum).  So if you currently have block 12, and you see a block with the correct id, and ownblock = 12 and its checksum is good, 
then that's probably a valid ObjectContainer.

* With all the ObjectContainers found, you can extract filenames and directory names from these, but also the number of their first data 
block (in the field data) and the file size.  For small files (less than blocksize) this data block will be enough to recover the data.
For larger files, you might be lucky and all the remaining blocks are found after the first one (if the file was defragmented).  You can't be
sure of that though so...

* For larger files, you need to find all the BNodeContainers.  You could scan these in the same way you found all the ObjectContainers (look for 
blocks with the correct id, ownblock number and checksum). 

* With all the BNodeContainers found, you can try looking up the first data block of a file in the B-Tree structure.  This is a bit complicated 
-- the B-Tree consists of non-leaf nodes (blocks that only contain pointers to other B-Tree blocks), the isLeaf flag indicates this.  Or it 
can be a B-Tree leaf block.  The leaf blocks contain extra information per entry (see https://hjohn.home.xs4all.nl/SFS/extents.htm)
&lt;pre&gt;
struct fsExtentBNode {
     ULONG key;
     ULONG next;
     ULONG prev;
     UWORD blocks;
};
&lt;/pre&gt;

The key should be a block of a file (the first of a range), that is 1 to 65535 block long (depending the &quot;blocks&quot; field).  If the file is split 
up into more parts, then &quot;next&quot; will contain block number of the next range of blocks.  You need to look this up again in the B-Tree 
structure to find out how large it is. 

You can for the most part ignore the other structures (bitmap, admin containers).  The fsObjects and B-tree containers is what you'll need to 
recover the data. 


====Resources====

&lt;pre&gt;
rom/storage/mmakefile.src 
rom/storage/storage.conf 
rom/storage/storage_device.c 
rom/storage/storage_ids.c 
rom/storage/storage_init.c 
rom/storage/storage_intern.h 
rom/storage/storage_mount.c 
rom/storage/storage_unit.c
&lt;/pre&gt;

&lt;pre&gt;
rom/storage/includes/device.h 
rom/storage/includes/unit.h 
rom/storage/includes/volume.h 
rom/storage/storage_intern.h 
&lt;/pre&gt;

&lt;pre&gt;

&lt;/pre&gt;

*[[Aros/Developer/Docs/Resources/ACPI|acpi.resource]]
*[[Aros/Developer/Docs/Resources/Battclock|battclock.resource]]
*[[Aros/Developer/Docs/Resources/Bootloader|bootloader.resource]]
*[[Aros/Developer/Docs/Resources/Cia|cia.resource]]
*[[Aros/Developer/Docs/Resources/Filesystem|FileSystem.resource]]
*[[Aros/Developer/Docs/Resources/Hostlib|hostlib.resource]]
*[[Aros/Developer/Docs/Resources/Kernel|kernel.resource]]
*[[Aros/Developer/Docs/Resources/Misc|misc.resource]]
*[[Aros/Developer/Docs/Resources/Processor|processor.resource]]


==Debugging Code==

Please use the [http://sourceforge.net/tracker/?group_id=43586&amp;atid=439463 AROS Bug Tracker] if any issues are found.


GRUB Command line list

&lt;pre&gt;
sysdebug  
usbdebug - allows to see Poseidon's log in debug output
&lt;/pre&gt;


How do I get debugging out of InitResident ? If running i386 hosted on linux sysdebug=initresident on command line.
This  way  you can enable any of listed flags. sysdebug=all stands for &quot;everything&quot;


Have an executable (crosscompiled C++ code) which has 6 MB size on disk, but after loading it in memory, 250 MB RAM is taken. Any software that would split AROS executable into ELF part which would show actual size values?

 readelf -S executable

it will show you all sections in elf file, including sizes and requested alignment.

 objdump -h filename

That's will give you a quick overview of the sections and sizes. Ignore all the .debug.* sections. 
Would hazard a guess that you have a large .bss section. That's pretty common in C++.

Next step:

 nm—size-sort filename | grep ' [bB] '

The last few will be your biggest consumers. Would suggest -C to demangle the symbols... ;)


Suggest profiling the program (just use some printf's in the main loop for time spent in each part), it usually is quite easy to spot slow parts in games or apps.

If someone has '#define IPTR ULONG' somewhere. To see where that define is, redefine IPTR in the source code that fails, just above the line that fails, and the preprocessor will tell you where it was defined first.

===How to setup gdb with AROS/hosted===

Download AROS sources (AROS-xxxxxxxx-source.tar.bz2, where xxxxxxxx is the current date) and AROS contrib sources (AROS-xxxxxxxx-contrib-source) from 

Untar-bzip2 and cd to the unpacked archive directory.

 &gt; tar -xvjf AROS-xxxxxxxx-source.tar.bz2
 &gt; cd AROS-xxxxxxxx-source

Check the link to &quot;contrib&quot; (contrib-source) inside directory, e.g. correct like this:

 &gt; rm contrib
 &gt; ln -s ../AROS-xxxxxxxx-contrib-source.tar.bz2 contrib

Make sure you have the correct locale setting, otherwise compilation will fail at some point. See [http://aros.sourceforge.net/documentation/developers/compiling.php#setting-the-locale-to-iso8859 here] (or link below) for more on that. You might have to enter this:

 &gt; export LANG=&quot;en_US.ISO-8859-1&quot;

Now configure for a debug build - see &quot;./configure --help&quot; for more - here are two examples:

 &gt; ./configure—enable-debug=stack,modules,symbols
 
 &gt; ./configure—enable-debug=all

You may &quot;make&quot; now, or choose a separate directory for your build (e.g. for easy removal), for example if compiling for i386 architecture you could create a directory like this:

 &gt; mkdir linux-i386
 &gt; cd linux-i386
 &gt; ../AROS/configure—enable-debug=stack,symbols,modules

When done configuring you're ready to go:

 &gt; make

Building AROS takes some time - minutes on fast machines (e.g. 2.5&amp;nbsp;GHz quadcore), up to hours on slower machines.
The result will be AROS Linux hosted with gdb debugging enabled.

See aros.org documentation for more on compiling AROS, including more [http://aros.sourceforge.net/documentation/developers/compiling.php --enable-debug] options.


When finished, enter bin/linux-i386/AROS directory (replace &quot;linux-i386&quot; with your compilation target platform, e.g. linux-x86_64, etc.) inside the unpacked archive directory. This directory contains the required .gdbinit file for properly running AROS inside gdb.

 &gt; cd bin/linux-i386/AROS

Run AROS (here: with 128MB of memory) from gdb:

 &gt; gdb—args boot/aros-unix -m 128
or
 &gt; gdb—args boot/arosboot -m 128

 (gdb) r

Watch the shell output - in case AROS complains about &quot;LoadKeyCode2RawKeyTable: Loading &quot;DEVS:Keymaps/X11/keycode2rawkey.table&quot; failed!&quot; you should also see some instructions on how to create a keymap table. (see link above &quot;more on compiling&quot;, too.)
Quit gdb, and try default keymap table:

 (gdb) q
 The program is running.  Quit anyway (and kill it)? (y or n) y
 &gt; cd ../../..
 &gt; make default-x11keymaptable

Re-run AROS, as described above. Try e.g. RAros (= right windows key) + W to open a shell. If this doesn't work you have to create a keymap table yourself, quit gdb again, and make a new keytable:

 &gt; make change-x11keymaptable

A window will open. Watch the window's title bar, and follow the instructions.

When done, re-run AROS. RAros + W should now open a shell.

Next, compile your program with gdb support.


When you start GDB is there a warning which says

   warning: File &quot;&lt;whatever&gt;/.gdbinit&quot; auto-loading has been declined by your `auto-load safe-path' set to ...

If so start gdb with &quot;-ix .gdbinit&quot;


&lt;pre&gt;
Summary - In short:

* build AROS with debugging support (i.e. ./configure --enable-debug=all)
* build your application with debugging support (i.e. option -g)
* run AROS in the GNU debugger (you may use the GUI frontend &quot;ddd&quot; which simplifies usage a bit)
* start your application
* use the commands &quot;findaddr&quot; and &quot;add-symbol-file&quot; as written in the debugging manual
* if the debugger doesn't find the source code of your application use the &quot;dir&quot; command of the debugger. 
&lt;/pre&gt;

===How to use gdb===

In AROS open a shell, then (in host shell) use CTRL-Z to go into gdb. Use &quot;b Exec_CreatePool&quot; (one of the functions used early on by startup code in programs) to add a breakpoint, then &quot;cont&quot; and gdb will interrupt somewhere early during startup of &quot;program&quot;. Use &quot;bt&quot; to show backtrace and &quot;loadseg&quot; for &quot;??&quot; entries. One of them will be for &quot;program&quot;. After that you can use &quot;disassemble program&quot;.

One thing you need to make sure is that .gdbinit you have in your build directory is the same as in source tree. It has been modified some time ago, but the build system does not refresh it - you need to copy it manually

To recap, please read our debugging [http://aros.sourceforge.net/documentation/developers/debugging.php manual]:


To detect segfaulting when loading, try...

 ./configure—enable-debug—with-optimization=&quot;-O2&quot;

Because crash or no crash may depend on optimization. For newer compilers maybe this helps...

 --with-optimization=-&quot;-O2 -fno-strict-aliasing&quot;

One way to make crashes less random (more easily reproducible) is to activate the munging of free memory in rom/exec/freemem.c which is normally commented out:

&lt;pre&gt;
Index: freemem.c
===================================================================
--- freemem.c   (revision 34289)
+++ freemem.c   (working copy)
@@ -154,11 +154,12 @@
         * created with their TCB placed in the tc_MemEntry list. The workaround
         * is to avoid munging when FreeMem() is called with task switching disabled.
         */
+
        /* DOH! it doesn't work even this way. What's wrong???
-        *
-        * if ((SysBase-&gt;TDNestCnt &lt; 0) &amp;&amp; (SysBase-&gt;IDNestCnt &lt; 0))
-        *      MUNGE_BLOCK(memoryBlock, MEMFILL_FREE, byteSize);
         */
+
+       if ((SysBase-&gt;TDNestCnt &lt; 0) &amp;&amp; (SysBase-&gt;IDNestCnt &lt; 0))
+           MUNGE_BLOCK(memoryBlock, MEMFILL_FREE, byteSize);

     }
&lt;/pre&gt;

Mungwall can be turned on at runtime. Currently this works in all hosted versions. Just specify &quot;mungwall&quot; on kernel command line and it works. It can work on native too. In order to enable it you need to parse kernel command line, and if &quot;mungwall&quot; is present, set EXECF_MungWall bit in IntExecBase.IntFlags.

This needs to be done before the first AllocMem() for obvious reasons. And never reset back this flag! If you change it on a working system, you are doomed.

Hosted ports do the processing in rom/exec/prepareexecbase.c --enable-debug=mungwall option in configure still works but is going obsolete.  A kludge in rom/exec/allocmem.c is responsible for this and it needs to be removed when the transition is done.

BTW,  on  i386-pc  port it can be activated by &quot;mungwall&quot; argument on command line, you don't need to rebuild AROS.
New mungwall affects not only AllocMem()/FreeMem(), but also pools. I also tested it with AllocAbs(), seems to work correctly.

Runtime mungwall works on:

* pc-i386
* pc-x86_64
* linux-i386
* linux-x86_64
* darwin-x86
* linux-ppc

Works on all hosted ports, if the port itself is working.

* amiga-m68k
* Not on sam440-ppc and efika-chrp-ppc, even if they would be able to be built at moment. Does not work on (for now, need NVRAM support)

When starting my freshly rebuilt i386-linux-aros which was compiled with full debugging support I get sometimes the error &quot;Program exited with code 0377&quot;. Add the following to your .gdbinit: 
 set follow-fork-mode child

Here are some of the custom AROS gdb functions (defined in &quot;.gdbinit&quot; file) to resolve &quot;in ?? ()&quot; entries in backtrace: 
&lt;pre&gt;
#0 0xb7ffd424 in __kernel_vsyscall ()
#1 0xb7e2a657 in sigsuspend () from /lib/libc.so.6
#2 0xb7c63900 in ?? ()
#3 0xb7c640e3 in ?? ()
#4 0xb7c641e0 in ?? ()
&lt;/pre&gt;

You can use

 loadseg 0xb7c63900
 loadframe 2
or
 loadbt
and some others. Use &quot;help &quot; for a little help text. If the commands do not work try &quot;loadkick&quot; first.


Use &quot;thistask&quot;, &quot;taskready&quot;, &quot;taskwait&quot; to get list of AROS tasks. &quot;bttask &quot; shows backtrace of a task which is in ready or in wait queue and &quot;loadseg&quot; to resolve &quot;??&quot; entries in it's backtrace (&quot;loadframe&quot; would not work as it assume current running task).

===Native debugging tools for AROS===

 to enable debugging at boot time entering the GRUB menu editing line (E key) and adding &quot;debug=memory&quot; to your boot line, then press Ctrl+X to complete booting.


SYS:Tools/Debug/'''Bifteck'''

Open a shell and enter the line below to run Biftek and grab the debug messages collected in RAM into a text file.

 tools/debug/bifteck &gt; ram:debug.txt

and certainly does not open a window. It is a shell tool and only dumps data located from the debug location.
It is therefore important to 'catch' that debug data as soon as possible (before it gets overridden). You should invoke bifteck at the first opportunity before doing anything else.  You can use the TO option to store bifteck output to a file or you can pipe it manually to a file.  


SYS:Tools/Debug/'''Sashimi''' - displays error messages

One suggestion is to do a bug() debugging. Each time bug() is executed it will be output on sashimi. 
You include &lt;aros/debug.h&gt; and place bug(&quot;something\n&quot;); in your source code at location though which control passes.

To get the output - open an aros shell

 SYS:Tools/Debug/sashimi &gt; RAM:out.txt

'''Ctrl C''' to end the output to the RAM Disk.

# open shell, and type
# ram: (to switch to ram drive)
# System:Tools/Debug/Sashimi &gt; mylogfile.txt
# open AHI prefs using wanderer (or use another opened shell)
# play test sound
# close AHI prefs
# shell still open with Sashimi running: press ctrl-c to break Sashimi and return to prompt.
# in shell: copy mylogfile.txt System: (or to your required location)


SYS:Utilities/'''Snoopy''' - monitors OS function calls, run &quot;Sashimi&quot; to see Snoopy's output


SYS:Tools/'''WiMP'''    - the Window (and Screens) Manipulation Program

You can use the -E option of gcc to find out how preprocessor macros are expanded.

===Errors===

crash in strcasecmp usually means that one of its arguments is NULL.

empty space between these two names, prossibly some invisible character 

Old Amiga [http://www.amigacoding.com/index.php?title=Guru_codes&amp;redirect=no Guru Codes]

If the crash is in intuition. Sometimes, if it relates to text, a null pointer sets it off. 
an uninitialised pointer can have any address (this is a common fault).


Compiling on 64bit, Many old code would not properly typecast when doing pointer-integer conversions and thus at least throw a warning. This can easily be located and fixed.

[http://www.aros.org/cs/documentation/developers/app-dev/portable.php Portable code] 

* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.
* Fix (change IPTR/SIPTR back to ULONG/LONG) the few places which really rely on ULONG/LONG being exactly 32 bit. That's for things like pixel (ARGB) buffers, structs written/read to disk, colormaps, but probably not much else.

Then again, many current compilers also throw a warning when you try to assign a pointer value to an integer and the integer is possibly too small. This happens under .NET for example when a 64 bit pointer is assigned to something like an ULONG - so exactly the case which you described.


=== AI ===
                  Multimodal
                   Context
                   Prompt
                    &lt;---
  Model &lt;---&gt; Agent ---&gt; End user
 engine 

 Gemini      LMStudio
  Qwen       Comfyui
   etc

Recent, self hosting locally on laptops, mini pcs or desktops with '''quantization''' 4bit has reduced memory requirements but still require 16Gb+ and no high end gpu for text based 

*[https://lmstudio.ai/download LMstudio single gpu],

Google Gemma 4 Model 
*[ 12B QAT] 


Alibaba Cloud's [https://huggingface.co/ Qwen] team series of large language models LLMs 
*[https://huggingface.co/models?other=qwen3 Qwen 3], [], 
*[https://huggingface.co/models?other=qwen2 Qwen 2], [https://huggingface.co/Qwen/Qwen2.5-Coder-32B qwen 2.5 Coder],  


Small models 
*[ glm-ocr]
*[ medGemma]
*[ qwen 3.5-4b]
*[https://github.com/sipeed/picoclaw picoclaw claude] 


Bigger LLMs but with settings 
*[https://ollama.com/download Ollama single gpu]
*[https://github.com/ggml-org/llama.cpp/releases llama.CPP multi gpus],
*[ VLM multiple gpus],
Multimedia 
*[ Kimi K3], 


For the full experience 
#Training learning using 1+ high end GPUs at least 16GB VRAM per GPU card or 64Gb+ of unified, 16Core CPU with at least 64Gb of RAM system memory, though training can take weeks 
#Inference with custom asics or GPUs 

*[ MiniMax H3] for audio and video but gpu 8Gb+ 
*[https://github.com/jamiepine/voicebox voicebox]
*[https://github.com/ideogram-oss/ideogram4 ideogram4]
*[https://github.com/calesthio/OpenMontage OpenMontage]

&lt;pre&gt;
Text to Audio --\
Text to Video --/ Reference Video --&gt; Video and Audio output 
&lt;/pre&gt;

=== Example ===

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/* 1. Header for your name,date,purpose of program.
2. Pre-processor directives. This will include the #includes for files you want to add. 
3. Includes for function prototypes if necessary.
4. Main()
Create Pointers for Libraries and any Window you want to open.
5. Open necessary libraries.
6. Check if open exit program if fail.
7. Open a window exit program if fail.
8. Add your program
9. Close Window
10 Close Libraries.
11 End Program. */

/* standard os included headers &lt;.h&gt; */
#include &lt;dos/dos.h&gt;
#include &lt;dos/dosasl.h&gt;
#include &lt;dos/dosextens.h&gt;
#include &lt;dos/exall.h&gt;
#include &lt;dos/rdargs.h&gt;
#include &lt;exec/memory.h&gt;
#include &lt;exec/types.h&gt;
#include &lt;utility/utility.h&gt;
#include &lt;intuition/intuition.h&gt;

/* define as unresolved external references (proto/xxx.h) and compiler will link to auto(matically) open library */ 
#include &lt;proto/arossupport.h&gt;
#include &lt;proto/dos.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/graphics.h&gt;
#include &lt;proto/cybergraphics.h&gt;
#include &lt;proto/datatypes.h&gt;
#include &lt;proto/icon.h&gt;

#include &lt;workbench/workbench.h&gt;
#include &lt;workbench/icon.h&gt;

#include &lt;datatypes/pictureclass.h&gt;

#include &lt;proto/muimaster.h&gt;
#include &lt;libraries/mui.h&gt;

#include proto/bsdsocket.h

#include &lt;ctype.h&gt;
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;string.h&gt;

/* my own headers &quot;.h&quot; */

#define CTRL_C      (SetSignal(0L,0L) &amp; SIGBREAKF_CTRL_C)
#define  isDir(fib) ((fib)-&gt;fib_DirEntryType &gt;= 0)

#define ARG_TEMPLATE    &quot;FILE/A,ALL/S,QUIET/S,W=WIDTH/N,H=HEIGHT/N,M=METHOD,DEFTOOL&quot;

int main(void)
{


	return retval;
} /* main */
&lt;/syntaxhighlight&gt;

If you used c++, there is not yet c++ support in our shared library system. 
The easiest way to create / compile a shared library would be to use the AROS build system but the libraries can be created manually. You have to create a ROMTAG structure and some header files.  

A shared library is built with the %build_module macro with a line like this:

 %build_module mmake=MetaTarget modname=mylib modtype=library files=SourceFiles 

This macro can build different AROS module types, like devices, Zune classes, HIDDs, etc.

&lt;pre&gt;
##begin config
version 1.0
##end config

##begin functionlist
void func1(LONG a, LONG b)
int func2(char *s, ULONG a)
##end functionlist
&lt;/pre&gt;


Alternatively,  

&lt;pre&gt;
#ifndef LIB_H
#define LIB_H

#define __NOLIBBASE__

#include &lt;exec/libraries.h&gt;
#include &lt;exec/semaphores.h&gt;
#include &lt;dos/dos.h&gt;

#ifdef __AROS__
//#include &lt;aros/debug.h&gt;
#define reg(x)
#define __saveds
#endif

#define USESYSBASE struct ExecBase *SysBase = Base-&gt;My_SysBase;

struct MyTestBase
{
  struct Library   My_Test_Lib;
	struct ExecBase *My_SysBase;
	APTR             My_SegList;
  int              testint;
};

#endif
&lt;/pre&gt;

&lt;pre&gt;
/*--------------------------------------------------------------------------*/
/* Resident header written for mytest.library */
/*--------------------------------------------------------------------------*/

#define __NOLIBBASE__

#define VERSION         1
#define REVISION        0

#define LIBHEADNAME     mytest
#define LIBHEADNAMESTR &quot;mytest&quot;
#define COMPDATE        &quot;04.10.2015&quot;
#define VERS            &quot;1.0&quot;

#define LIBBASETYPE 	struct MyTestBase
#define LIBBASETYPEPTR  LIBBASETYPE *

#include &lt;aros/debug.h&gt;
#include &lt;exec/exec.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;exec/resident.h&gt;
#include &lt;exec/nodes.h&gt;
#include &lt;exec/libraries.h&gt;
#include &lt;aros/symbolsets.h&gt;
#include &quot;lib.h&quot;

const UBYTE lib_name[] = LIBHEADNAMESTR &quot;.library&quot;;

const UBYTE lib_id[] = &quot;$VER: &quot; LIBHEADNAMESTR &quot;.library &quot; VERS &quot; (&quot; COMPDATE &quot;) by ALB42\n&quot;;

extern const APTR FuncTable[];

AROS_UFP3 (LIBBASETYPEPTR, InitLib,
    AROS_UFPA(LIBBASETYPEPTR, Base, D0),
    AROS_UFPA(BPTR, seglist, A0),
    AROS_UFPA(struct ExecBase *, sysbase, A6)
);

static struct LibInitStruct
{
    IPTR                   LibSize;
    const APTR             *FuncTable;
    const struct DataTable *DataTable;
    APTR                    InitFunc;
}
const LibInitStruct =
{
    sizeof(LIBBASETYPE),
    FuncTable,
    NULL,
    (APTR)InitLib
};

const struct Resident romtag =
{
  RTC_MATCHWORD,              /* match word */
  (APTR)&amp;romtag,              /* back pointer */
  (APTR)(&amp;romtag + 1),        /* skip pointer */
  RTF_AUTOINIT | RTF_EXTENDED,/* flags */
  VERSION,                    /* version */
  NT_LIBRARY,                 /* type of module */
  0,                          /* init priority */
  (STRPTR)lib_name,           /* module name */
  (STRPTR)lib_id + 6,
  (APTR)&amp;LibInitStruct,
  REVISION, NULL
};

AROS_UFH3 (LIBBASETYPEPTR, InitLib,
    AROS_UFHA(LIBBASETYPEPTR, Base, D0),
    AROS_UFHA(BPTR, seglist, A0),
    AROS_UFHA(struct ExecBase *, sysbase, A6)
    )
{
    AROS_USERFUNC_INIT
    
    Base-&gt;My_SegList = seglist;
    Base-&gt;My_SysBase = (APTR)sysbase;
    Base-&gt;testint = 0;
    
    USESYSBASE
    bug(&quot;InitLib\n&quot;);
    
    if (!set_open_libraries())
    {
      set_close_libraries();
      return NULL;
    }
    
    return Base;
    
    AROS_USERFUNC_EXIT
}

AROS_LH1(LIBBASETYPEPTR, LibOpen,
    AROS_LHA (ULONG, version, D0),
    LIBBASETYPEPTR, Base, 1, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    
    USESYSBASE
    bug(&quot;LibOpen\n&quot;);

    (void)version;
    
    Base-&gt;My_Test_Lib.lib_OpenCnt++;
    return Base;

    AROS_LIBFUNC_EXIT
    
}

__saveds APTR LibExpungeInternal(LIBBASETYPE *Base reg(a6))
{
  USESYSBASE
  APTR seglist;
  bug(&quot;LibExpungeInternal\n&quot;);

  if (Base-&gt;My_Test_Lib.lib_OpenCnt)
  {
    return 0;
  }

  seglist = Base-&gt;My_SegList;

  Forbid();
  Remove((struct Node*)Base);
  Permit();
  FreeMem((APTR)Base - Base-&gt;My_Test_Lib.lib_NegSize, (LONG)Base-&gt;My_Test_Lib.lib_PosSize +
    (LONG)Base-&gt;My_Test_Lib.lib_NegSize);
  
  set_close_libraries();
  return seglist;
}

AROS_LH0(BPTR, LibClose,
    LIBBASETYPEPTR, Base, 2, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;LibClose\n&quot;);

    if (!(--Base-&gt;My_Test_Lib.lib_OpenCnt))
    {
      return LibExpungeInternal(Base);          
    }
    return 0;
	
    AROS_LIBFUNC_EXIT
}

AROS_LH1(BPTR, LibExpunge,
    AROS_LHA(LIBBASETYPEPTR, Base, D0),
    struct ExecBase *, sysBase, 3, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT

    (void)sysBase;
    
    USESYSBASE
    bug(&quot;LibExpunge\n&quot;);

    return LibExpungeInternal(Base);
	
    AROS_LIBFUNC_EXIT
}

AROS_LH0(LIBBASETYPEPTR, LibReserved,
    LIBBASETYPEPTR, Base, 4, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;LibReserved\n&quot;);

    return 0;
    //return (APTR)LibReserved();
    
    AROS_LIBFUNC_EXIT
}


// Space for your own functions
// do not forget to update the FuncTable as well

AROS_LH1(int, TestFunction,
    AROS_LHA(int, TestValue, D0),
    LIBBASETYPEPTR, Base, 5, LIBHEADNAME
    )
{
    AROS_LIBFUNC_INIT
    USESYSBASE
    bug(&quot;TestFunction\n&quot;);

    Base-&gt;testint = TestValue + Base-&gt;testint;
    
    return Base-&gt;testint;
    
    AROS_LIBFUNC_EXIT
}

// Functable -&gt; Table of all functions in the Library, in right order - important!

const APTR FuncTable[] = 
{
    &amp;AROS_SLIB_ENTRY(LibOpen,LIBHEADNAME,1),
    &amp;AROS_SLIB_ENTRY(LibClose,LIBHEADNAME,2),
    &amp;AROS_SLIB_ENTRY(LibExpunge,LIBHEADNAME,3),
    &amp;AROS_SLIB_ENTRY(LibReserved,LIBHEADNAME,4),
    &amp;AROS_SLIB_ENTRY(TestFunction,LIBHEADNAME,5),
    (void *)-1
};

// AutoInit stuff
void *__PROGRAM_ENTRIES__symbol_set_handler_missing;
void *__LIBS__symbol_set_handler_missing;
// end of AutoInitStuff
&lt;/pre&gt;

Makefile
&lt;pre&gt;
VPATH = 
CFLAGS = -O2 -g -fomit-frame-pointer -W -Wall -Wno-parentheses
CC = i386-aros-gcc
LD = i386-aros-gcc
LDFLAGS = -nostartfiles -Wl,-Map -Xlinker linkermap
LIBS = -lautoinit -llibinit
STRIP = i386-aros-strip --strip-unneeded --remove-section .comment

OBJS = lib_header.o 

all: mytest.library

mytest.library: $(OBJS)
	$(LD) $(LDFLAGS) $^ $(LIBS) -o $@

lib_header.o: lib_header.c lib.h

clean:
	rm -f *.o *.library *.ppu testlibrary linkermap
&lt;/pre&gt;


Porting UNIX library to AROS - dealing with static variables which would make it easy to port such libraries to AROS, keeping the benefits of sharing them on disk, but losing the benefit of actually sharing them in memory.

Our problem arises by the fact we want to share the actual code (the .text section of the library) and constant data, but we need to have per-task .bss and .data sections. If we get rid of our intention to share the .text and .rodata sections, things get quite easy: just load and relocate the library whenever it's open, by whoever it's open. It's like statically linking the library into the executable, except that the final linking is done at runtime.

In the V0 branch, in workbench/hidds/hidd.nouveau was committed pcimock.hidd. This is a pci driver that allows mocking real PCI devices under linux-hosted. The main idea is to be able to run the real hardware driver under linux-hosted with as little changes as possible (some changes will always be needed though unless someone wants to write complete device simulator) so that driver's code paths can be executed and debugged using gdb. This was a very helpful capability when porting nouveau. Now it is externalized from nouveau.hidd and can be used by other people porting drivers. The pcimock.hidd can currently mock 4 different nvidia cards, 1 AGP bridge and also mock irq.hidd.

What's the difference between this driver and the pcilinux.hidd? I used that one to develop many different HW drivers for aros. As far as I understood the intention of pcilinux.hidd it is supposed to get access to real hardware that is running under linux. The pcimock.hidd goal is to mock the hardware. For example my dev box is a PCIE system, but I still would like to run the AGP codes paths in nouveau under linux-hosted to check if they don't seg fault. The other case would be to run codes paths for hardware that the developer does not have (Fermi cards in my case). In the case of pcimock.hidd, the AROS driver's code paths will execute as long as you add proper mocking (for example fill in PCI config area or values for registers in BARs). This is an advantage for ported drivers - the code should already work (since it worked on another system) but there might have been mistakes made during porting which can be detected easily with gdb.

In case you are writing your driver from scratch, pcilinux.hidd hidd will give you more advantage, since you can actually access the real hardware from linux-hosted.


== Misc ==

===APL, MPL, BSD, GPL and LGPL Licences===

The majority of AROS sources in licensed under AROS Public License ([http://aros.sourceforge.net/license.html APL]) which (to a degree) protects us from someone taking AROS sources and not contributing improvements back (for example MorphOS took some AROS source and then contributed changes back)

It is written to allow the use of AROS code in other open source or commercial projects without exception whilst providing a mechanism so that improvements/additions can find their way back to the original source in one form or another.

There are &quot;3rd&quot; party applications used by AROS that do not fall under this license, which are an extra &quot;Contrib&quot; download for convenience.

Anyone can port GPL-ed network and sound drivers as AROSTCP and AHI are GPLed. Direct using (porting) [http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs GPL]-ed code in other parts of AROS (gfx, sata, usb) is not possible because AROS license is not compatible with GPL. You need to utilize permissive licensed code like BSD or MIT/X11.


BSD and MPL license are the closest to APL.

APL however is not so compatible with LGPL/GPL.

LGPL case - you cannot statically combine APL code with LGPL. You can, however thank to LGPL being &quot;lesser&quot; restrictive, use LGPL dynamically loaded libraries in APL codes.

GPL case - you cannot combine APL code with GPL in any way if there is no explicit clause by GPLed code authors allowing that. If you do combine APL with GPL in &quot;bad&quot; ways described above - you have a problem (you violate GPL). This problem might result in everything in AROS becoming GPL or everything running or AROS becoming GPL (here I'm not sure really). The other scenario is that you are not allowed to legally distribute such code at all. To be honest I have grasped how to violate GPL, but I'm still no exactly sure what happens when you violate it (but I'm sure it's not anything nice)

GPL software can run on top of non-GPL &quot;system components&quot; (see system components exception of GPL), but the other way around (non-GPL using GPL) leads to problems. This means applications like scout, or Quake III are ok (in the majority of cases).

Theres no reason GPL drivers cannot be ported - but they cant be in AROS's ROM (requires linking APL code with GPL), nor can AROS depend on them (e.g. they must use existing apis).
If they are launched (dynamically linked) by a user action that is allowed. It is also allowed to distribute such binaries together for convenience.

GPL is not about statical or dynamic linking but is about executing process and function calls.


These components - SFS, isapnp, Zune texteditor, AHi, network drivers, freetype, openuirl, BHFormat, Edit and (&quot; dynamically loaded libraries&quot;) are LGPL, not GPL. Mesa/Nouveau stuff is MIT. Some user tools are GPL though.

'''AROS (system)'''
* system components (libraries/classes/devices/etc) cannot be GPL as they would propagate GPL to complete system as well as GPL is not compatible with MPL from which APL is based 
* system components can be LGPL v2 or a permissive license (MIT/BSD)
* system applications can be anything you like (but still I would prefer APL or permissive so the code can be reused if needed)

'''Contrib:'''
* no rules - contrib does not impact AROS system since nothing in AROS system depends on contrib.

About stealing code: The chances of this happening is exactly the same whether we are APL or GPL. If any closed-source option wanted to do it, there is no one that can validate otherwise. MorphOS has used some AROS codes, but contributed changes back.

The rationale behind APL is that while it guarantees that the original developer will get the improvements back (to a certain degree - file based), the person who uses the codes does not have to open his original codes. BSD does not guarantee that the original developer gets improvements. GPL requires the person using the codes to open his codes as well.

The copyright holders needs to stay - we just need information from them that the codes are available under APL (for example a checked-in file like in case of Poseidon). We don't do transfer of copyrights.

; Ultimately what can and cannot be done is up to the author(s) - not the licence.

===AROS source code tree===

* http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-trunk.txt
* http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-contrib.txt


Found this interesting (non-GPL) licensing 'anomaly' - to keep in mind for distributors.

Programs that lose their license if sold (&quot;non-profit only&quot; licensed):
  contrib/aminet/comm/term/TinyTerminal
  contrib/aminet/dev/basic/bwBASIC
  contrib/aminet/text/edit/xdme
  contrib/fish/aroach
  contrib/fish/lotto
  contrib/fish/shuffle
  contrib/fish/touch
  + cdvdfs.


Here is a list of all the GPL/GPLv2/GPLv3 licenses fossology found, what have explicit licenses in their comments.


 excluded LGPL, BSD/GPL dual licensed and programs (such as Prefs/Edit and BHFormat)

&lt;pre&gt;
AROS/rom/dbus/include/  AFL_v2.1 ,GPL_v2+  (supposedly AFL &lt; 3 is GPL incompatible) 
AROS/workbench/classes/zune/betterstring/include/  GPL_v2+
AROS/workbench/classes/zune/texteditor/include/  GPL_v2+
AROS/workbench/classes/datatypes/gemimage/ GPL_v2+ GPL
AROS/workbench/classes/datatypes/degas/  GPL_v2+
AROS/workbench/libs/openurl/README: GPL
AROS/workbench/network/smbfs/documentation/  GPL_v2
AROS/workbench/network/smbfs/source_code/  GPL_v2+
AROS/workbench/network/stacks/AROSTCP/bsdsocket/kern/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/mmakefile.src conf.h  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/sys/  CMU ,GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/net/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/api/  GPL_v2
AROS/workbench/network/stacks/AROSTCP/bsdsocket/conf/conf.h: GPL_v2
AROS/workbench/network/stacks/AROSTCP/netinclude/net/radix.h: CMU ,GPL_v2
AROS/workbench/devs/AHI/AHI/  GPL_v2+
AROS/workbench/devs/AHI/AddAudioModes/ GPL_v2+  AROS/workbench/devs/AHI/AddAudioModes/COPYING: GPL 
AROS/workbench/devs/AHI/Docs/texinfo.tex: GPL_v2+
AROS/workbench/devs/AHI/COPYING: GPL
AROS/workbench/devs/AHI/Drivers/EMU10kx/  GPL_v2+
AROS/workbench/devs/AHI/AHI-Handler/  GPL_v2+
AROS/workbench/devs/networks/rtl8029/  GPL   GPL_v2+
AROS/workbench/devs/networks/pcnet32/  GPL   GPL_v2+
AROS/workbench/devs/networks/ppp/LEGAL: GPL
AROS/workbench/devs/networks/atheros5000/  GPL_v2+
AROS/workbench/devs/networks/rhine/  GPL_v2+
AROS/workbench/devs/networks/nForce/  GPL_v2+  GPL
AROS/workbench/devs/networks/prism2/  GPL  GPL_v2+
AROS/workbench/devs/networks/fec/LEGAL: GPL
AROS/workbench/devs/networks/rtl8139/  GPL  GPL_v2+
AROS/workbench/devs/networks/etherlink3/  GPL  GPL_v2+
AROS/workbench/devs/networks/intelpro100/  GPL  GPL_v2+
AROS/workbench/devs/networks/rtl8169/  GPL   GPL_v2+
AROS/workbench/devs/networks/emac/   GPL   GPL_v2+
AROS/workbench/devs/networks/rtl8168/  GPL  GPL_v2+
AROS/workbench/devs/networks/realtek8180/   GPL_v2+
AROS/workbench/devs/networks/via-rhine/via-rhine.c: GPL_v2+
AROS/workbench/devs/networks/via-rhine/   GPL  GPL_v2+
AROS/workbench/devs/networks/e1000/  GPL_v2
AROS/workbench/devs/networks/sis900/  GPL   GPL_v2+
&lt;/pre&gt;

AHI: it has special provisions (COPYING.DRIVERS). The library is LGPL, preferences software is GPL and drivers can be anything without breaking GPL/LGPL.

Network stack: well, we are long overdue for a new, IPv6 enabled network stack anyway, anyone interested? ;) Seriously though it seems like the glue code is GPL and as all the drivers. However some of the drivers are our own code, so they could be relicensed to LGPL.

 Same filter as the AROS trunk list. These should all be libraries or plugins - no programs.

&lt;pre&gt;
contrib/regina/utsname.h: GPL_v2+

contrib/mui/classes/nlist/include/default-align.h: GPL_v2+
contrib/mui/classes/nlist/include/amiga-align.h: GPL_v2+

contrib/mui/classes/BWins/include/MUI/BWin_mcc.h: GPL
contrib/mui/classes/BWins/include/BWin_private_mcc.h: GPL
contrib/mui/classes/BWins/COPYING: GPL_v2
contrib/mui/classes/BWins/MCC_BWins.readme: GPL_v2

contrib/mui/classes/thebar/include/default-align.h: GPL_v2+
contrib/mui/classes/thebar/include/amiga-align.h: GPL_v2+

contrib/gfx/libs/wazp3d/LEGAL: GPL
contrib/gfx/libs/wazp3d/Wazp3D.readme: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d.c: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d_opengl.h: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/soft3d_opengl.c: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/Wazp3D.h: GPL
contrib/gfx/libs/wazp3d/Wazp3D-src/Wazp3D.c: GPL

contrib/libs/mpega/  GPL_v2+
&lt;/pre&gt;

http://www.evillabs.net/AROS/Audit-2012-03-14/AROS-contrib.txt

===Types===

On AROS following rules apply:
&lt;pre&gt; 
1. BYTE/UBYTE is 8bit, WORD/UWORD is 16bit, LONG/ULONG is 32bit, QUAD/UQUAD is 64bit, the types are comparable with stdint types (int8_t, int16_t, int32_t, int64_t)
2. IPTR/SIPTR are integer types large enough to fit pointer, that is sizeof(IPTR) = sizeof(APTR) = 4 on 32bit system, and = 8 on 64bit system
3. ti_Data in TagList is large enough to hold a IPTR/APTR type.
4. never store a pointer in integer of type LONG. It may work (if the pointer has upper 32bits clear), but does not have to. Compiler should warn you about that.
5. If you are unsure about point 4, allocate your memory with MEMF_31BIT flag set. But don't expect that AROS internals will do the same.
&lt;/pre&gt; 
point 4 is actually important.


* UBYTE/BYTE for 8bit
* UWORD/WORD for 16bit
* ULONG/LONG for 32bit
* UQUAD/QUAD for 64bit

&lt;pre&gt;
UBYTE    Unsigned 8 bit integer variable (byte).
BYTE     Signed 8 bit integer variable (byte).
UWORD    Unsigned 16 bit integer variable (word).
WORD     Signed 16 bit integer variable (word).
ULONG    Unsigned 32 bit integer variable (longword).
LONG     Signed 32 bit integer variable (longword).
FLOAT    32 bit IEEE floating point variable.
UQUAD    Unsigned 64 bit integer variable.
QUAD     Signed 64 bit integer variable.
DOUBLE   64bit IEEE floating point variable.
BOOL     Boolean variable, TRUE and FALSE are also defined in exec/types.h.
VOID     Void.

APTR     A generic pointer for multiple purposes - Arrays.
STRPTR   A pointer to a null-terminated string.
IPTR     Really important in AROS, the only way to declare a field that can contain both: an integer or a pointer.
&lt;/pre&gt;

if you want to write really portable app, you may be interested in standard datatypes defined in C99: int8_t, uint8_t, int16_t, uint16_t, int32_t, uint32_t, int64_t, uint64_t, intptr_t, uintptr_t. They are all defined in inttypes.h include file.

In exec/types.h the following short-cuts are typedef'd. They are used often in AROS, so you should nearly always include exec/types.h and soon only they will be removed from sys/_types.h include, all types are now defined in include files named aros/types/xxx.h.

(Preparation for C library split; sys/xxx.h include will only be available there when compiling with POSIX C library)


Compiler specific types, like int and long might change their size. In case of AROS, similar to linux, int remains 32 bit whereas long grows to 64 bits in size.

If you use Amiga-like data types, i.e. BYTE/UBYTE, WORD/UWORD, LONG/ULONG and QUAD/UQUAD or the C99 standard types (uint8_t and so on, see stdint.h include) then you should have less issues to solve than by using types without size guarantee.

Of course, all pointers grow to 64 bytes using 64bit cpu. Most of the code can be just recompiled and will work. In rare cases, where e.g. pointers are casted to integers, a special care must be taken. Especially in the cases, where pointer is casted to LONG/ULONG (this code will break on 64 bit AROS) e.g.  '#define IPTR ULONG'.

With compiler delint patches which the majority of them are simple casting issues to make the compiler happy. Notice some of the changes involve introducing double casts. In very recent versions of GCC. Yes, the bulk of the double casts are for converting 32 bit addresses (ie from a 32 bit PCI DMA address register) to a 64 bit pointer. First cast is to IPTR (to expand to 64 bits, and prevent sign extension if the address is above 0x7FFFFFFF), and then to APTR.

ULONG != IPTR except on 32bit .. so if you need to store pointers make sure and use IPTR and not ULONG (which some old code does). For this reason things like Taglist elements are 64bit (since the tag data can be a pointer). 
If your passing items on the stack you should use the STACKED attribute to make sure they are correctly aligned (on 64bit all items on the stack are 64bit..)

There is more issues like using &quot;== 0L&quot; causes problems.

===Endian===

*BE 
*LE

Use the macros from &lt;endian.h&gt; instead making a guess based upon architecture defines
 
&lt;pre&gt;
#if _BYTE_ORDER == _BIG_ENDIAN

#elif _BYTE_ORDER == _LITTLE_ENDIAN

#else
+
#error &lt;whatever.h&gt; - Byte order for this architecture is unsupported! 
&lt;/pre&gt;


===SVN and GIT===

If you want to help develop AROS OS itself, you can 

* view current GIT/SVN entries [http://aros.sourceforge.net/ Aros Org website] or [https://github.com/aros-development-team/AROS Github], [https://github.com/ezrec older ezrec mirror], [https://github.com/michalsc/AROS/ older mirror], [https://trac.aros.org/trac/timeline TRAC], [], 
* awaiting update [http://repo.or.cz/w/AROS.git git repo], [http://www.ohloh.net/p/aros/commits ohloh] or [https://svn.aros.org/svn/aros/trunk/ svn repo] and access [Git version git://repo.or.cz/AROS.git here], 
* deprecated [https://www.gitorious.org/aros/aros/commit/a7fda9e ARIX commits] or [https://gitorious.org/aros/aros GIT old]

If you have SVN access (early 2015 introduced a new SVN server, create a new account at trac aros org) and/or have obtained the source [http://aros.sourceforge.net/download.php AROS site] - you can compile the current build tools/environment using: 

 &gt; make development

and follow this [http://aros.sourceforge.net/documentation/developers/compiling.php#building procedure] or [https://github.com/apiraino/aros_guide Guide] 


https://trac.aros.org/trac#Developing

If you plan on contributing back changes, please post information about such changes first on this [http://mail.aros.org/mailman/listinfo/aros-dev/ mailing list] for more experience developers can validate whether they are correct.


Then there are the nightly build machines. They svn update before the build and run configure as one of the next steps. autoconf might be added to the nightly build scripts.

Our build relies on packages downloaded from Internet (SDL for example) - it always worked this way. The minimal requirement (when just building core AROS) is binutils and gcc. If you build contrib as well, you need many more packages to be downloaded.

https://gitorious.org/aros/aros/commits/crosstools-II

git://gitorious.org/aros/aros.git

Branch crosstools-II there is only one commit on top of ABI_V1 
&lt;pre&gt;
../../aros-src/AROS/configure --enable-ccache
--with-portssources=~/aros/Sources --target=pc-x86_64
--with-aros-toolchain-install=/home/weissms/media/data/aros/test/crosstools/pc-x86_64
&lt;/pre&gt;
and
&lt;pre&gt;
../../aros-src/AROS/configure --enable-ccache
--with-portssources=~/aros/Sources --target=pc-i386
--with-aros-toolchain-install=/home/weissms/media/data/aros/test/crosstools/pc-i386
&lt;/pre&gt;
build OK.


:''More information: [[Aros/Developer/Maintainer|AROS Maintainer Docs]]''

===SDI Calls===

Integrate the 'SDI'-headers to allow easier porting to all amiga-like platforms.

&lt;pre&gt;
PUTCHARPROTO( PutTheChar, char c, struct SPrintfStream *s  )
{
 // REAL CODE
}
&lt;/pre&gt;

have &quot;SDI_compiler.h&quot; and &quot;SDI_hook.h&quot; included

its more organized like

 #include SDI/SDI_hook.h

than

 #include SDI_hook.h

option 1 --- i also use when back porting from amiga's..

&lt;pre&gt;
#ifdef __AROS__
#include SDI/SDI_hook.h
#else
#include SDI_hook.h
#endif
&lt;/pre&gt;

also

you can add the -i include/sdi/ location if you do not want to add or edit any files.


Defining HOOKPROTO to IPTR name(struct IClass * cl, Object * obj, Msg msg); solved the problem

A MUI application most likely needs only the HOOKPROTOxxx SDI macros. They are compatible with AROS, only the attributes (hook, object attribute) must be given in the right order. examine compiler/include/aros/symbolsets.h (AROS_LIBREQ)

compiling mui stuff for aros setting -std=gnu99 is necessary (i have had -std=c99 most of the time).

===Locale with Flexcat===

Most languages have a locale, but not every app is localized, the only thing needed is to translate the &quot;catalog&quot; files. It is a case of locating the correct catalog and saving the translated version.

For every app that lacks of your language catalog and is localized anyway, you should find (in the sources) files related to locale:

* file.cd = catalog descriptor, contains base msg, with internal language (usually english)
* language.ct = catalog translation, contains every translated msg, indexed as in the file.cd.

Compare with other localized apps... Then, &quot;make my_app-catalogs&quot; should create and install your translated catalogs. ex : for, saying, sys:prefs/wanderer:

on root of AROS sources, type:
 &quot;make workbench-prefs-wanderer-catalogs&quot;
then (if you changed the .cd file):
 &quot;make workbench-prefs-wanderer&quot;

For apps not localized, you have to adapt their code to support it, if it is possible...

noticed the original .cd file has many (//) strings at the end of any voice, so added them also to the .ct file. 
That (//) is only for cd files. I'm highly recommending to use FlexCat for updating ct files, e.g. like this:

 flexcat app.cd deutsch.ct newctfile deutsch.ct

You'll get error checking and new entries are marked in the resulting ct file.

When editing .ct files, only change those lines containing translation and perhaps version string, nothing else.
The rest is up to the relevant tool, flexcat. In order to update your translation, type in the following in your shell:

 flexcat xyz.cd xyz.ct NEWCTFILE xyz_upd.ct COPYMSGNEW

This way you will not only make sure you have correct translation file but flexcat also pre-fills newly added strings with &quot;*** NEW *** text. Even better tool for checking cd/ct/catalog files is catcheck, but this one is sadly only available for AmigaOS/68k...

Some languages have variations, like portugues from portugal and portugues from brasil differs...

This is the way to go. I will have a look at language files, but basically if those two languages differ you have to do two separated set of translation files, yes.
(you could create a brazilian slang language localization too)

* At system level localization for one language is a dot language file.
(ex: locale:languages/klingon.language)

* At app level localization is a dot catalog file
(ex: locale:catalogs/klingon/system/libs/dos.catalog)

* At sources level, the dot ct file, and &quot;$language&quot; dot cd files and some building framework.
(ex: catalogs/my_app.ct catalogs/klingon.cd catalogs/mmakefile.src support.c support.h)

Please, use Flexcat to generate CT files: 
 FlexCat wanderer.cd NEWCTFILE=deutsch.ct

Then fill the first 2 lines with something useful:
&lt;pre&gt;
## version $VER: wanderer.catalog 1.1 (9.2.2006)
## language deutsch
&lt;/pre&gt;

You can even update the CT-File: (This adds the new strings)
 FlexCat wanderer.cd deutsch.ct NEWCTFILE=deutsch.ct


To compile a catalog you only need the .cd file and your translation (.ct file):
 FlexCat multiview.cd deutsch.ct CATALOG=MultiView.catalog


[http://murks-ide.svn.sourceforge.net/viewvc/murks-ide/trunk/src/Catalogs/flexcat_linux?revision=100 Linux version of FlexCat]

: [http://aros.sourceforge.net/documentation/developers/app-dev/localization.php#localization-for-non-developers More information]


A script which compares the required version (i.e. the version which an application/module etc. tries to open) with the version of the existing CT files. The result is in this table:

https://github.com/aros-translation-team/translations/wiki/Progress

The following cases are highlighted:

    n/a i.e. CT misses at all
    version in existing CT file is lower than the required version


It might be a bit difficult to participate if you haven't worked with Git before but alternatively you can send your CT files to our Slack channel.

When the ct file has been generated via flexcat (flexcat keyshow.cd NEWCTFILE=spanish.ct) it has the following header:

---------------------------------------------------------------------------------------------------------------
## version $VER: &lt;name&gt;.catalog &lt;ver&gt;.&lt;rev&gt; (04.01.2021)
## language nolanguage
## codeset 0
;
---------------------------------------------------------------------------------------------------------------

Those values &lt;ver&gt;.&lt;rev&gt; are the version and revision of the CT file for the languaje or are the values of the application being localized?

The &lt;ver&gt; part must match with version which the application tries to open. You can find the value either in the column &quot;Required Version&quot; in the table which I've linked above, our you can look in the git repository. For keyshow it would be https://github.com/aros-translation-team/keyshow. You can find in the file &quot;catalog_version.h&quot; the right version number.
The &lt;rev&gt; part starts for new CT files with 0 and should be increased every time the CT file is updated.

Updated several files and created a few more that were missing on the spanish catalog.

The catalogs are in Git repositories at https://github.com/aros-translation-team

a) You tell me your Github user name. I'll invite you. You can work directly with the Git repositories.

b) You create Github forks of the catalog repositories and create pull requests.

c) You send the CT files to mrustler  gmx de


===C Utils Misc===

The AROS source uses at several places the __DATE__ macro to fill the date entry of a $VER tag. Problem is that c:version doesn't understand that date format (e.g. &quot;May 21, 2011&quot;). As a result the output of e.g.
&gt; &quot;version c:shell full&quot; contains &quot;(null)&quot;. Is extending the version command to understand the format of __DATE__  the right solution for that problem?

AmigaOs compilers should use __AMIGADATE__ macro or similar form, if it isn't implemented it could be emulated in makefile: -D__AMIGADATE__=\&quot;$(shell date &quot;+%d.%m.%Y&quot;)\&quot;

BTW. I think DD.MM.YYYY is better format than &quot;Month DD YYY&quot; because &quot;Month DD YYY&quot; is not localized in any way.

&quot;strnicmp&quot; shouldn't work with NULL pointers

The Situation:

compiled a linklib using c++ object files (using the c++ cross compiler).
compiled a C stub that uses the linklib (using the c++ cross compiler).

Try to link them together (using the c++ cross compiler) with C object
files (using the normal target c compiler) that need to use -nostartup
= cant do because using the c++ files pulls in arosc (for stdio etc.) -
so wants to have the autoinit stuff present.

What can I do about this??

If it is possible to manually open it then what do I need to do exactly?

=== ENV ===

The philosophy behind ENV: is that keeping configuration files there allows you to  'Use'  preferences  by  keeping  a copy in ENVARC: intact. However in some cases (like this one) it is not required.

99% of the time that statement is true (not required) for pretty much every file in ENV: or do people change their default icons - and prefs settings - every boot?

There seem to be a bad habit of late with developers changing things to reflect their own personal preference when the change isn't actually necessary - It would be nice if people could refrain from doing that in the tree without at least discussing it on the dev-list first (and with good reasoning unless they committed said work in the first place..)

We're not keen on the pollution of the &quot;S:&quot; dir: it's meant to be for scripts. What's wrong with &quot;ENV:&quot;?
Only the fact that it takes up RAM. I  understand  that  for  PCs  with  several gigabytes of RAM this is
irrelevant. But let's remember about other machines. The philosophy behind ENV: is that keeping configuration files there allows you to  'Use'  preferences  by  keeping  a copy in ENVARC: intact.

However in some cases (like this one) it is not required.

How about implementing in the style of HappyENV then? RAM-disk handler that falls through to reading from ENVARC: if there is no such file stored in it already. Removes RAM usage for unchanged files, removes the need to copy ENVARC to ENV in startup-sequence. 
Shouldn't be too hard to make from AmberRAM, or even just extend AmberRAM to provide this service.

Is it feasable to build a special version of AmberRAM handling ENV: that will try and copy the requested file from ENVARC: if it isnt found in ENV: ? 
Additionaly it could mark closed &quot;files&quot; as untouched - and expunge them from ENV: after a period of time to free up additional RAM:, or when the system is running low on free memory?

Silenty disappearing files may not be a good plan. Would be nice if the following would work:

ASSIGN :ENV SYS:Prefs/Env-Arc ADD
ASSIGN :ENV RAM:ENV  ADD

Where new files put in ENV: end up in RAM:ENV, and opening files looks in RAM:ENV first, then SYS:Prefs/Env-Arc

Well - that's essentially what im proposing but without the assigns - or need for a RAM:ENV directory. 
Adding it as a feature of AmberRAM sounds like the most memory efficient way (one handler to load in RAM) but that's only if it is possible to make it handle ENV: additionally to RAM:, and if it is even possible to add the proposed functionality (...and how to make it enable it when accessing ENV:).

===(AS)MP support===

If one has to recompile software for SMP multi core, is there any thing special one has to do to get software to run?   
Use task.resource if you need to query information about what tasks are running, and clear msgports completely when they are allocated.

Most code should not need Forbid. Use Semaphores, Messages etc. to sync your own code. 

Accessing system structures is a different thing. Use the proper API whenever possible.

How single structures will be protected in the future is still a moving target, at least it is not documented. And you should never  use undocumented stuff  


Ideas on for SMP multi-core

Another suggestion is ... Forbid/Permit function calls are meant to halt multitasking so as no other task could intervene with what ever the calling task is doing, e.g. setting semaphores. Disable/Enable calls are meant to halt interrupts and as a side effect they also halt task switching.

One option is to make it compulsory to protect shared resources with semaphores and forbid the use of simple Forbid() calls as to protect something. Setting semaphore should be done if possible with atomic instructions (check and alter in one instruction). Or make the second concurrent ObtainSemaphore call halt the second calling task and force if possible a task switch which ever gives better results. 

Semaphores could store the owning tasks task pointer instead of boolean to make things easier.

As long as the CPU initiates the DMA transfers through the OS, and the OS ensures that the transferred memory is within the region accessible to the user initiating the transfer, everything is fine. The CPU is the conductor, and the CPU by that has the control of which DMA transfer is initiated and which is not.
All you need to do is to write device drivers reasonable. Hint: CachePreDMA and CachePostDMA exist.
All the Os has to do is to verify that the memory regions to be transferred are valid, and prohibit direct access to the DMA control registers from user space. None of these algorithms imply huge costs.
The current OS design doesn't really allow virtual memory in first place, Forbid() is again the problem.

[http://www.tbs-software.com/guide/index.php?guide=autodocs.doc%2Fmemory.doc&amp;node=1 memory.library API] seem to low level. IMHO the programs should not know how the swapping is implemented. I would just go for one new memory flag
MEMF_SWAPPABLE that indicates that a certain memory region or a whole memory pool won't be accessed during Forbid()/Permit() etc. It only solves part of the problem, it only implements virtual memory and not memory protection. For the latter you need to be able make certain memory inaccessible by other programs, some memory read-only for one task and read-write for other tasks, etc. And I think this should be done in the same Address Space in order to avoid you constantly need to swap between different address spaces. 
So to summarize, if there are programs using this API we may provide a wrapper layer to get them working but I am not convinced this API should be the reference API with whom to provide VM to AROS programs.

=== Variadic ===

variadic functions (i.e. functions with an arbitrary amount of arguments).

&lt;pre&gt;
    #include &lt;stdarg.h&gt;
    [...]

    char * STDARGS GetKeyWord(int value, char *def, ...)
    {
        [...]
        va_list va;
        [...]
        va_start(va, def);
        [...]
        va_end (args);

&lt;/pre&gt;

Please keep with using stdarg rather than having va casted to a LONG * type and varargs handled manually. Doing so, prevents tons of casting, where a simple va_arg can be used. So, string = *((char **) args) instead of string=va_arg(va, char *).

&lt;pre&gt;
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;

int printf (const char * format, ...)

{
    int     retval;
    va_list args;

    va_start (args, format);

    retval = vfprintf (stdout, format, args);

    va_end (args);

    fflush (stdout);

    return retval;
} /* printf */
&lt;/pre&gt;

Couldn't find varargs.h or stdarg.h. and have no use for AROS_SLOWSTACKHOOKS or AROS_SLOWSTACKTAGS.

GCC looks for stdarg.h in a different place: 
 /bin/linux-i386/tools/lib/gcc/i386-aros/4.2.2/include/stdarg.h

Here is a path for a &quot;normal&quot; header:
 bin/linux-i386/tools/lib/gcc/i386-aros/4.2.2/../../../../i386-aros/sys-include/aros/system.h


The use of vararg.h isn't supported by newer gcc versions. If you want your code to run on architectures that pass part of variadic arguments in a number of registers you need to use AROS_SLOWSTACK macros. Otherwise your program will not work on powerpc and x86_64 ports.

Of course the SLOWSTACK stuff is not needed in a function that can use va_list, va_start, va_arg and va_end. It's only needed if you want to write functions like DoMethod or similar.

 #include &lt;stdarg.h&gt;

should be enough no matter if you do cross or native compiling. If it does not work, something is wrong and should be corrected.

Stdarg.h is here, Development:lib/gcc/i386-aros/4.2.2/include/

...which is part of the compiler's default include paths. In other words, #include &lt;stdarg.h&gt; works out of the box, indeed. (sorry, I should have just tried it before invoking &quot;search&quot; or &quot;find&quot;...)

furthermore, myprintf() as shown above won't work, because...

 printf(format, args);

...is wrong - the second argument does not match printf() prototype, it expects a argument list, but args is of type va_list (obviously) - so one has to use...

 vfprintf(stdout, format, args);

...instead, just like in the original printf(), and add fflush(stdout).

additionally, one could use...

 int myarg = va_arg(args, int);

...between va_start() and va_end() to access individual arguments, where each call to va_arg() returns an argument casted to the desired type (here: &quot;int&quot;) from the list given (here: &quot;args&quot;) and advances to the next one.

wrapping up vfprintf() and modifying the format string now is a major speedup! no more backslash-n typing! this has been haunting me for years!

On MOS and AmigaOS, the NewObject variadic function is kept in the static library. It takes most of the parameters on the stack - thanks to that the implementation of NewObject calls the NewObjectA function. Everything works perfect, and the typical MUI macros may be easily used.

This, however, is not the case when you compile for AROS. Here, NewObject is a variadic macro, not a function. Thanks such approach we do not need any custom compiler in case of systems, where the arguments of variadic functions are passed partially through registers and partially through the stack (This is the case of PPC and x86_64, this is also the reason why both OS4 and MOS require specially patched compilers).

Since NewObject is a macro, the gcc's preprocessor expects the list of macros arguments enclosed within parentheses. In MUI macros it is not the case. Imagine the following test code:

&lt;pre&gt;
#define foo(a,b) ((a)+(b))

int loosy_function(int a, int b)
{
    return foo(a,b);
}
&lt;/pre&gt;

This will compile and work, but the following piece of code:

&lt;pre&gt;
#define foo(a,b) ((a)+(b))
#define END )

int loosy_function(int a, int b)
{
    return foo(a,b END;
}
&lt;/pre&gt;

will fail with the error: unterminated argument list invoking macro &quot;foo&quot;

There are two ways of fixing your issue. Either create your new objects outside this huge MUI constructions, and in there use just a pointer, or get rid of the &quot;End&quot; macro and exchange it with &quot;TAG_DONE)&quot;.


Badly written software is, for example, casting va_list to an APTR or even doing so as if va_list were a plain table of function arguments. Such code needs to be fixed because it has very few chances to work anywhere but on author's machine ;)

The problem is nOt that they assume sizeof(APTR) == 4, its that they often do not use APTR, and use ULONG to store pointers exclusively. If the code used APTR/IPTR as it should - most of the &quot;problems&quot; wouldn't exist.

It would also help if people would start using variadic arguments properly. Many coders do assumptions which shall never be made. Instead, they should consider using stdarg.h file and all the va_* functions :)

===ABI===

In the head of our SVN repository there are now only 3 directories:

&lt;pre&gt;
admin/
branches/
trunk/
&lt;/pre&gt;

We have added two extra dirs there: tags and imports

As discussed when we branch ABI V0 and [[Aros/Developer/ABIv1|ABI V1]] it would also be good to introduce tags. Normally this is done in a directory in the repository called tags. Currently we don't have this directory there. (We do have branches/tags that is a hack I have done because one doesn't have write access in the top directory. I think this directory is not clean and should be removed).

The second directory I would introduce is an imports directory for implementing vendor branches as discussed in the svn [http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html book]. Currently we use code from several different projects and that code is stored inside the AROS tree; we seem to have problems with keeping this code up to date and merge our changes upstream. Maintainers of up stream projects like the MUI classes etc. have complained about this (to put it lightly).

Introducing these vendor branches would make it easier to see what changes we have made and make patches to be sent upstream and make it easier to import newer upstream versions of their code. Although can't &quot;copy&quot; the vendor branch into the main branch because it's already there, so start with a &quot;merge&quot;.

Yes, the first step to make the code already in the repository compatible with the vendor branches will be the most difficult. The best way to do it the following way:

* first import the version on which the current AROS code is based into the vendor branch
* then import the new version over it in the vendor branch
* finally merge the difference between these two version in the AROS code present in the repository.

For example, place NList directly under vendor and not in a subdirectory like &quot;contrib/zune/classes&quot;.

Actually after we have a stable [http://aros.sourceforge.net/documentation/developers/specifications/drafts/abiv1.php ABIv1 (2012 or later)]. We need to move away as much as possible from the contrib directory to some other repositories. The reasons are ...

* The AROS repository should be for the core AROS code.
* other contrib projects should be tried to be compiled for all Amiga-like OSes.
* The release scheme for AROS and the other programs should not have to be aligned.
* Binary versions should be provided on aros-archives and on aminet and/or OS4Depot to install them. (Some clever programs should maybe be provided to make the life of distribution developers easier). 
* avoid parallel forks of programs for AROS and the other amiga OSes.

If there is really a need for a place for hosting AROS projects we may investigate setting up such a server but then including bug tracking, governance, maillist, etc. for each project separately. I personally think there are already enough places like sourceforge, google code, savannah, etc. where people can go for hosting such projects.

==Links==

* http://amigadocs.hokstad.com
* http://amigadocs.hokstad.com/doku.php?id=dev-links


 In the future...?
*AROS 64bit - SMP, Vulkan with OpenGL compability layer
*AROS 32bit - keep for historic reasons 

What would you like to see implemented in AROS?
ABIv1 completed, SMP (x86_64),  SendMsg()/GetMsg() to support memory protection between target and destination, in that order.   Michal Schulz and Jason McMullan have been toying with the question &quot;What are the minimal changes needed to the AmigaOS 3.1 API to support SMP&quot;?  The answer so far seems to be &quot;few, but subtle&quot;.  For example, SysBase-&gt;ThisTask is no longer meaningful on SMP, but FindTask(NULL) is.  Disable() and Forbid() are shockingly bad on performance, but adding a spinlock semaphore mode to SignalSemaphore will help new code on SMP.  

Leveraging a 'common' OS with a lot of machine support (Linux, MacOS, Windows, QNX, etc.) is something that AROS has been doing for quite a long time, and it is the biggest strength of AROS. This AROS experience and programming model, in the same way the Google's Android layers on top of Linux, or MacOS X layers on top of the Darwin/BSD kernel, as a first step 

* The graphics + layers subsystem could be implemented as a shim on top of a OpenGL ES implementation (ie on any modern Linux system, or the RaspberryPI's hardware, MacOS X, etc). 
  - This also allows every window to be on its own 3D surface with backing store, allowing Wanderer (or a Commodity)
rearrange/zoom/animate app windows without having to send a pile or refreshes to them

* Use OpenAL as the sound backend
* AROSTCP would be a thin layer over the native OS's TCP/IP stack
* dos.library, poseidon.library, and input.device would be slim shims over the native APIs
* If we move to loading all libraries' into the application's task space, instead of a single global instance of the library, this will allow SMP and MMU more easily. 
  - Yes, it will require a lot of work in the libraries to make this transition
  - Yes, I do think it will be worth it in the end.

* A 'fat binary' install format (or, maybe LLVM bytecode) that can be 'flattend' to the target architecture on installation.

So, what would this 'AROS of the future' look like?

* AmigaOS 3.x style API, with certain 'fundamental changes' to message passing
* Uses the underlying OS' device drivers, so more AROS developer effort can go to user-visible features and bugfixes 
* Allows AROS applications to run side-by-side with the OS's native apps


And why would anyone want to program on such a system?

* AROS applications would run on any system that has the AROS Framework installed
* AROS applications are pixel-for-pixel the same on all platforms. 
* Develop with the knowledge that you are guaranteed OpenGL and OpenAL, and the rest of the AROS Framework

an option for mmake to dump its dependency of metatarget in a graphviz[*] input file. This should make it possible to visualize the dependencies and hopefully be inspiration for cleaning up some mess, circular or unneeded dependencies and so on.


AmigaOS gcc 9 [https://franke.ms/amiga/gcc.wiki Old versions] able to create binaries for AmigaOS and [https://eab.abime.net/showthread.php?t=93813 Upgrading gcc versions] 


==References==
{{reflist}}
{{status|50%}}

{{BookCat}}</text>
      <sha1>bfy0rqzhy03vaeexifwatvy9sypkv65</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/Developer/Zune</title>
    <ns>0</ns>
    <id>13165</id>
    <revision>
      <id>4668973</id>
      <parentid>4634674</parentid>
      <timestamp>2026-09-05T17:57:00Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668973</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20663" sha1="qs74a7i73z8vanct844l9535dakfat1" xml:space="preserve">{{ArosNav}}

==Introduction==

&lt;pre&gt;
version muimaster.library is 19 for 3.8 
                          is 20 for 3.9
                          is    for 4.0  dynamic tabs simplification 
                          is    for 5.0  
&lt;/pre&gt;

Zune is an object-oriented GUI toolkit. It is nearly a clone (at both API and Look&amp;Feel level) of MUI, a well-known Amiga shareware product by Stefan Stuntz. Therefore, MUI developers will feel at home here, while others will discover the concepts and qualities that Zune shares with MUI.

The programmer has a much easier time to design its GUI: no need for hardcoded values, Zune is font-sensitive, and adapts to any window size due to its layout system. He/she mostly needs to only specify the semantic of its GUI to Zune, which will arrange the low-level details automatically.

Zune is based on the [https://library.morph.zone/Short_BOOPSI_Overview BOOPSI] system, the framework inherited from AmigaOS (TM) for object-oriented programming in C. Zune [[Aros/Developer/Zune/Classes|classes]] does not derive from existing BOOPSI gadget classes; instead, the Notify class (base class of the Zune hierarchy) derives from the BOOPSI root class.

* Many AROS GUI components (windows, requesters, gadgets, images) are now programmed in an object-oriented way, using the BOOPSI/Zune toolkit. 
* Every such component is created as an object, not as a pointer to a system structure. That means no more filling structures with data. 
* Objects are manipulated using methods and by passing tags via the SetAttrs() function.

Creating Prefs from scratch with using our Zune Prefs classes.

A good introduction to the BOOPSI system is the [http://amigadev.elowar.com/read/ADCD_2.1/Libraries_Manual_guide/node01FF.html Chapter 12, &quot;BOOPSI - Object-oriented Intuition&quot;]. Here BOOPSI NewObject() has been replaced by MUI_NewObject(), DisposeObject() becomes MUI_DisposeObject(), etc.

==Prerequisites==

Some knowledge of [http://wiki.answers.com/Q/What_are_the_concepts_of_object_oriented_programming OOP] {{w|object-oriented programming}} is more than welcome.

Knowing AROS APIs and concepts like [[Aros/Developer/Docs/Libraries/Intuition|taglists]] and BOOPSI is essential. As Zune is a MUI clone, all the documentation pertaining to MUI is applicable to Zune. In particular, the latest available MUI developer kit and MUI autodocs can be found at [http://main.aminet.net/dev/mui/mui38dev.lha here]. In this LHA archive, 2 documents are warmly recommended:

 '''MUIdev.guide''', the MUI programmer documentation, some [https://arosarchives.os4depot.net/?function=showfile&amp;file=development/example/mui_examples.i386-aros.zip c src examples]
 and
 '''PSI.c''' source code, demonstrating Zune practices like OOP and dynamic object creation

==Zune basics and conventions==

MUI (= Zune) sticks a prefix on the start to signify what is being access/changed:

* MUIA_ attribute 
* MUIM_ method 
* MUIV_ special values

==BOOPSI Primer/Concepts==

===Class===
A class is defined by its name, its parent class and a dispatcher.

'''name''': either a string for the public classes, so that they may be used by any program in the system, or none if its a private class used only by a single application.

'''parent class''': all BOOPSI classes are forming a hierarchy rooted at the class aptly named rootclass. It allows each subclass to implement its own version of specific parent operation, or to fall back on the one provided by its parent. Also known as base class or super class.

'''dispatcher''': it gives access to all operations (called methods) provided by this class, ensuring that each operation is handled by the proper code or passed to its super class.

BOOPSI type for a class is Class * also known as IClass.

===Object===
An object is an instance of class: each object has its specific data, but all objects of the same class share the same behavior. An object has several classes if we count the parents of its true class (the most derived one) up to the rootclass.

BOOPSI type for an object is Object *. It has no field you can directly access.

When a Zune object is created and destroyed several methods are called:
&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;
If the documentation says that something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

===Attribute===
An attribute is related to the instance data of each object: you can not access these data directly, you can only set or get the attributes provided by an object to modify its internal state. An attribute is implemented as a Tag (ULONG value or'ed with TAG_USER).

GetAttr() and SetAttrs() are used to modify an object's attributes.

Attributes can be one or more of the following:

Initialization-settable (I) : the attribute can be given as parameter at the object creation.

Settable (S) : You can set this attribute at any time (or at least, not only creation).

Gettable (G) : You can get the value of this attribute.

===Method===
A BOOPSI method is a function which receives as parameters an object, a class and a message:

object: the object you act on

class: the considered class for this object.

message: contains a method ID which determines the function to call within a dispatcher, and is followed by its parameters.

To send a message to an object, use DoMethod(). It will use the true class first. If the class implements this method, it will handle it. Else it will try its parent class, until the message is handled or the rootclass is reached (in this case, the unknown message is silently discarded).

Summary, before a method can act on an object, it needs a BOOPSI message 
&lt;pre&gt;
    Function                     BOOPSI Method

    NewObject()                  OM_NEW
    DisposeObject()              OM_DISPOSE
    SetAttrs()/SetGadgetAttrs()  OM_SET
    GetAttr()                    OM_GET
&lt;/pre&gt;

==BOOPSI Examples==
Let's see basic examples of this OOP framework:

Getting an attribute
We'll query a MUI String object for its content:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
void f(Object *string)
{
    IPTR result;
    
    GetAttr(string, MUIA_String_Contents, &amp;result);
    printf(&quot;String content is: %s\n&quot;, (STRPTR)result);
}
&lt;/syntaxhighlight&gt;

Object * is the type of BOOPSI objects. 
IPTR must be used for the type of the result, which can be an integer or a pointer. An IPTR is always written in memory, so using a smaller type would lead to memory corruption! 
Here we query a MUI String object for its content: MUIA_String_Contents, as any other attribute, is a ULONG (it's a Tag) 
Zune applications use more often the get() and XGET() macros instead:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
get(string, MUIA_String_Contents, &amp;result);

result = XGET(string, MUIA_String_Contents);
&lt;/syntaxhighlight&gt;
Setting an attribute
Let's change the content of our string:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;, TAG_DONE);
&lt;/syntaxhighlight&gt;
Pointers parameters must be casted to IPTR to avoid warnings. 
After the object parameter, a taglist is passed to SetAttrs and thus must end with TAG_DONE. 
You'll find the set() macro useful:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
set(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;);
&lt;/syntaxhighlight&gt;
But it's only with SetAttrs() that you can set several attributes at once:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string,
         MUIA_Disabled, TRUE,
         MUIA_String_Contents, (IPTR)&quot;hmmm...&quot;,
         TAG_DONE);
&lt;/syntaxhighlight&gt;
Calling a method
Let's see the most called method in a Zune program, the event processing method called in your main loop:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
result = DoMethod(obj, MUIM_Application_NewInput, (IPTR)&amp;sigs);
&lt;/syntaxhighlight&gt;
Parameters are not a taglist, and thus don't end with TAG_DONE. 
You have to cast pointers to IPTR to avoid warnings.

==&quot;Hello world&quot; example sourcecode==

[http://www.aros.org/documentation/developers/zune/images/hello.png Screenshot 'Hello World']

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
// gcc hello.c -lmui
#include &lt;exec/types.h&gt;
#include &lt;libraries/mui.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

int main(void)
{
    Object *wnd, *app, *but;

    // GUI creation
    app = ApplicationObject,
        SubWindow, wnd = WindowObject,
            MUIA_Window_Title, &quot;Hello world!&quot;,
            WindowContents, VGroup,
                Child, TextObject,
                    MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,
                    End,
                Child, but = SimpleButton(&quot;_Ok&quot;),
                End,
            End,
        End;

    if (app != NULL)
    {
        ULONG sigs = 0;

        // Click Close gadget or hit Escape to quit
        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Click the button to quit
        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Open the window
        set(wnd, MUIA_Window_Open, TRUE);

        // Check that the window opened
        if (XGET(wnd, MUIA_Window_Open))
        {
            // Main loop
            while((LONG)DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
                  != MUIV_Application_ReturnID_Quit)
            {
                if (sigs)
                {
                    sigs = Wait(sigs | SIGBREAKF_CTRL_C);
                    if (sigs &amp; SIGBREAKF_CTRL_C)
                        break;
                }
            }
        }
        // Destroy our application and all its objects
        MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

===Remarks/General===
We don't manually open libraries, it's done automatically for us.

===GUI creation===
We use a macro-based language to easily build our GUI. A Zune application has always 1 and only 1 Application object:

:   &lt;code&gt;app = ApplicationObject,&lt;/code&gt;

An application can have 0, 1 or more Window objects. Most often a single one:

:       &lt;code&gt;SubWindow, wnd = WindowObject,&lt;/code&gt;

Be nice, give a title to the window:

:           &lt;code&gt;MUIA_Window_Title, &quot;Hello world!&quot;,&lt;/code&gt;

A window must have 1 and only 1 child, usually a group. This one is vertical, that means that its children will be arranged vertically:

:           &lt;code&gt;WindowContents, VGroup,&lt;/code&gt;

A group must have at least 1 child, here it's just a text:

:              &lt;code&gt; Child, TextObject,&lt;/code&gt;

Zune accepts various escape codes (here, to center the text) and newlines:

:                  &lt;code&gt; MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,&lt;/code&gt;

An End macro must match every xxxObject macro (here, TextObject):

:                   &lt;code&gt;End,&lt;/code&gt;

Let's add a second child to our group, a button! With a keyboard shortcut o indicated by an underscore:

:               &lt;code&gt;Child, but = SimpleButton(&quot;_Ok&quot;),&lt;/code&gt;

Finish the group:

:               &lt;code&gt;End,&lt;/code&gt;

Finish the window:

:           &lt;code&gt;End,&lt;/code&gt;

Finish the application:

:       &lt;code&gt;End;&lt;/code&gt;

So, who still needs a GUI builder? :-)

===Error handling===

If any of the object in the application tree can't be created, Zune destroys all the objects already created and application creation fails. If not, you have a fully working application:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
   if (app != NULL)
   {
       ...&lt;/syntaxhighlight&gt;

When you're done, just call MUI_DisposeObject() on your application object to destroy all the objects currently in the application, and free all the resources:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;       ...
       MUI_DisposeObject(app);
   }&lt;/syntaxhighlight&gt;

===Notifications===
[http://library.morphzone.org/Event_Driven_Programming,_Notifications Notifications] are the simplest way to react on events. The principle? We want to be notified when a certain attribute of a certain object is set to a certain value:

:        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,

Here we'll listen to the MUIA_Window_CloseRequest of our Window object and be notified whenever this attribute is set to TRUE. So what happens when a notification is triggered? A message is sent to an object, here we tell our Application to return MUIV_Application_ReturnID_Quit on the next event loop iteration:

:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

As we can specify anything we want here, we have to tell the number of extra parameters we are supplying to MUIM_Notify: here, 2 parameters.

For the button, we listen to its MUIA_Pressed attribute: it's set to FALSE whenever the button is being released (reacting when it's pressed is bad practice, you may want to release the mouse outside of the button to cancel your action - plus we want to see how it looks when it's pressed). The action is the same as the previous, send a message to the application:

:        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

===Opening the window===
Windows aren't open until you ask them to:

:        set(wnd, MUIA_Window_Open, TRUE);

If all goes well, your window should be displayed at this point. But it can fail! So don't forget to check by querying the attribute, which should be TRUE:

:        if (XGET(wnd, MUIA_Window_Open))

===Main loop===
Let me introduce you my lil' friend, the ideal Zune event loop:

:        ULONG sigs = 0;

Don't forget to initialize the signals to 0 ... The test of the loop is the MUIM_Application_NewInput method:

:        ...
:        while((LONG) DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
:              != MUIV_Application_ReturnID_Quit)

It takes as input the signals of the events it has to process (result from Wait(), or 0), will modify this value to place the signals Zune is waiting for (for the next Wait()) and will return a value. This return value mechanism was historically the only way to react on events, but it was ugly and has been deprecated in favor of custom classes and object-oriented design.

The body of the loop is quite empty, we only wait for signals and handle Ctrl-C to break out of the loop:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
    {
    if (sigs)
        {
        sigs = Wait(sigs | SIGBREAKF_CTRL_C);
        if (sigs &amp; SIGBREAKF_CTRL_C)
             break;
        }
    }
&lt;/syntaxhighlight&gt;

===Conclusion===

This program gets you started with Zune, and allows you to toy with GUI design, but not more.

==Notification actions==

Notification allows you to respond to events your application/gui or any other object might cause.  Due to the attribute and method based nature of Zune, and a few special attributes, most applications can be almost completely automated through the use of Notification(s).

As seen in hello.c, you use MUIM_Notify to call a method if a certain condition happens. If you want your application to react in a specific way to events, you can use one of these schemes:

* Set An attribute.  You can automate the passing of values from gadgets,
::etc to other gadgets.  Setting values may also trigger other notification
::events.
      
* Invoke a method, for example:    
::'''MUIM_Application_ReturnID:''' you can ask your application to return an
:: arbitrary ID on the next loop iteration, and check for the value in
:: the loop. This is the dirty old way of doing things.
      
:: '''MUIM_CallHook,''' to call a standard Amiga callback hook: this is an
::average choice, not object-oriented but not that ugly either.
      
::'''custom method:''' the method belongs to one of your custom class. It 
::is the best solution as it supports object-oriented design in
::applications. It needs you to create custom classes so it may not 
::the easiest for beginners or people in a hurry.

==Zune Examples/Tutorials==

*Being an AmigaOS3.x MUI clone, all AmigaOS3.x MUI code serves as example code for using AROS Zune.
*MUI example sourcecode &quot;PSI.c&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*[http://code.google.com/p/guidetoamigacompatibleprogramming/source/browse/#svn/trunk/english Shinkuro's] Cross-Platform Guide gives information about compatible programming on Amiga-related platforms (Amiga, AROS, MorphOS) and [http://guidetoamigacompatibleprogramming.googlecode.com/svn-history/r6/trunk/english/CAP_4.txt MUI]
*[http://archive.is/20121225201004/robertnegro.wordpress.com/2012/10/30/aros-zune-programming-tutorials-for-beginners/ Good examples of Zune Main Classes]
*AROS itself contains lots of Zune examples. Download AROS sources and AROS contrib sources archives, take a look at the sourcecode of Zune programs. A good starting point are the Zune test programs, located in the SYS:Tests/Zune folder of AROS' binary distributions (e.g. the nightly build) - their sources can be found in the &quot;test/Zune&quot; folder of the AROS source archive.
*[[Aros/Developer/Zune/Examples|Zune example code collection]]

Some other good examples are here:

*[http://www.liquido2.com/tutorial/ An Introduction to AMIGA Programming Using C]
*[http://www.pcguru.plus.com/tutorial/introduction.html Programming AmigaOS in C]
*[http://library.morphzone.org/Magic_User_Interface_Programming Magic User Interface Programming] at [http://www.morphzone.org morphzone.org]
*[https://github.com/emartisoft/AmigaOS3.X-MUI-Examples Examples]

==Zune Reference==

*[http://aros.sourceforge.net/documentation/developers/zune-dev/index.php AROS Zune Development Manual] at [http://www.aros.org aros.org]
*[http://web.archive.org/web/20110526115419/http://www.sasg.com/mui/autodocs/index.html MUI Autodocs] online at [http://www.sasg.com sasg.com]
*MUI (=Zune) reference guide &quot;MUIDev.guide&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*MUI Reference information from AmigaOS documentation can be found e.g. [http://utilitybase.com/forum/index.php?action=vtopic&amp;forum=13 utilitybase.com/forum/...] or at [http://utilitybase.com/ref/ utilitybase.com/ref], it has a section on MUI. (Note: Information at that site is a little outdated, but still very helpful.) (2011-10-31: utilitybase.com currently down.)

==Tools==

===MUIBuilder===

A [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool native build] and [http://sourceforge.net/projects/muibuilder/ sourceforge svn repository] has been started and [[Aros/Developer/ZuneFurther]] documentation can be read. v3 is W.I.P. so it is not recommended for now.

This [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=5578&amp;forum=1&amp;post_id=52900#forumpost52900 thread] discussed using the m68k build and [http://www.mazze-online.de/files/mbtest.zip diff] file which modifications were necessary to make it build-able under AROS.

Summary
* added &quot;#define MUI_OBSOLETE&quot; to get some deprecated but needed defines
* changed/added some #include
* changed variable name Object to obj because Object is a type
* changed the Hook for the callback function
* last not least: added main.c which calls the functions to open/close the GUI.

Just go ahead and create your GUIS under any version of AROS or under amiga 68k version and do some modifications (which would be necessary for MorphOS/AmigaOS3/AmigaOS4, too).

===ChocolateCastle===

The [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool binary] which makes creating MUI classes and applications easier. Programmers using this system often avoid writing custom classes, being discouraged by a lot of boring and schematical typing. A significant part of a typical custom class may be generated automatically. This is usually 2 to 5 kB of source code. Automating this work speeds programming up and helps avoiding simple typing errors.

==Errors==
&lt;pre&gt;
Message  
Solution SetAttrs() is vararg version of SetAttrsA() and expects a complete taglist so you must add TAG_DONE and not TAG_END. 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols ... KeyString
Solution finally replaced KeyString(0,256,'f') by MUIA_CreateObject(MUIO_String,&quot;f&quot;,256)
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols... GetAttr
Solution you need:  #include &lt;proto/intuition.h&gt;
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution  #define MUI_OBSOLETE
&lt;/pre&gt;

{{BookCat}}

[[ru:Zune]]</text>
      <sha1>qs74a7i73z8vanct844l9535dakfat1</sha1>
    </revision>
    <revision>
      <id>4668974</id>
      <parentid>4668973</parentid>
      <timestamp>2026-09-05T17:59:39Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668974</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20594" sha1="oy8tpdppi9ybdezz6ybob987wk3c1gd" xml:space="preserve">{{ArosNav}}

==Introduction==

&lt;pre&gt;
version muimaster.library is 19 for 3.8 
                          is 20 for 3.9
                          is    for 4.0  dynamic tabs simplification 
                          is    for 5.0  
&lt;/pre&gt;

Zune is an object-oriented GUI toolkit. It is nearly a clone (at both API and Look&amp;Feel level) of MUI, a well-known Amiga shareware product by Stefan Stuntz. Therefore, MUI developers will feel at home here, while others will discover the concepts and qualities that Zune shares with MUI.

The programmer has a much easier time to design its GUI: no need for hardcoded values, Zune is font-sensitive, and adapts to any window size due to its layout system. He/she mostly needs to only specify the semantic of its GUI to Zune, which will arrange the low-level details automatically.

Zune is based on the [https://library.morph.zone/Short_BOOPSI_Overview BOOPSI] system, the framework inherited from AmigaOS (TM) for object-oriented programming in C. Zune [[Aros/Developer/Zune/Classes|classes]] does not derive from existing BOOPSI gadget classes; instead, the Notify class (base class of the Zune hierarchy) derives from the BOOPSI root class.

* Many AROS GUI components (windows, requesters, gadgets, images) are now programmed in an object-oriented way, using the BOOPSI/Zune toolkit. 
* Every such component is created as an object, not as a pointer to a system structure. That means no more filling structures with data. 
* Objects are manipulated using methods and by passing tags via the SetAttrs() function.

Creating Prefs from scratch with using our Zune Prefs classes.

A good introduction to the BOOPSI system is the [http://amigadev.elowar.com/read/ADCD_2.1/Libraries_Manual_guide/node01FF.html Chapter 12, &quot;BOOPSI - Object-oriented Intuition&quot;]. Here BOOPSI NewObject() has been replaced by MUI_NewObject(), DisposeObject() becomes MUI_DisposeObject(), etc.

==Prerequisites==

Some knowledge of [http://wiki.answers.com/Q/What_are_the_concepts_of_object_oriented_programming OOP] {{w|object-oriented programming}} is more than welcome.

Knowing AROS APIs and concepts like [[Aros/Developer/Docs/Libraries/Intuition|taglists]] and BOOPSI is essential. As Zune is a MUI clone, all the documentation pertaining to MUI is applicable to Zune. In particular, the latest available MUI developer kit and MUI autodocs can be found at [http://main.aminet.net/dev/mui/mui38dev.lha here]. In this LHA archive, 2 documents are warmly recommended:

 '''MUIdev.guide''', the MUI programmer documentation, some [https://arosarchives.os4depot.net/?function=showfile&amp;file=development/example/mui_examples.i386-aros.zip c src examples]
 and
 '''PSI.c''' source code, demonstrating Zune practices like OOP and dynamic object creation

==Zune basics and conventions==

MUI (= Zune) sticks a prefix on the start to signify what is being access/changed:

* MUIA_ attribute 
* MUIM_ method 
* MUIV_ special values

==BOOPSI Primer/Concepts==

===Class===
A class is defined by its name, its parent class and a dispatcher.

'''name''': either a string for the public classes, so that they may be used by any program in the system, or none if its a private class used only by a single application.

'''parent class''': all BOOPSI classes are forming a hierarchy rooted at the class aptly named rootclass. It allows each subclass to implement its own version of specific parent operation, or to fall back on the one provided by its parent. Also known as base class or super class.

'''dispatcher''': it gives access to all operations (called methods) provided by this class, ensuring that each operation is handled by the proper code or passed to its super class.

BOOPSI type for a class is Class * also known as IClass.

===Object===
An object is an instance of class: each object has its specific data, but all objects of the same class share the same behavior. An object has several classes if we count the parents of its true class (the most derived one) up to the rootclass.

BOOPSI type for an object is Object *. It has no field you can directly access.

When a Zune object is created and destroyed several methods are called:
&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;
If the documentation says that something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

===Attribute===
An attribute is related to the instance data of each object: you can not access these data directly, you can only set or get the attributes provided by an object to modify its internal state. An attribute is implemented as a Tag (ULONG value or'ed with TAG_USER).

GetAttr() and SetAttrs() are used to modify an object's attributes.

Attributes can be one or more of the following:

Initialization-settable (I) : the attribute can be given as parameter at the object creation.

Settable (S) : You can set this attribute at any time (or at least, not only creation).

Gettable (G) : You can get the value of this attribute.

===Method===
A BOOPSI method is a function which receives as parameters an object, a class and a message:

object: the object you act on

class: the considered class for this object.

message: contains a method ID which determines the function to call within a dispatcher, and is followed by its parameters.

To send a message to an object, use DoMethod(). It will use the true class first. If the class implements this method, it will handle it. Else it will try its parent class, until the message is handled or the rootclass is reached (in this case, the unknown message is silently discarded).

Summary, before a method can act on an object, it needs a BOOPSI message 
&lt;pre&gt;
    Function                     BOOPSI Method

    NewObject()                  OM_NEW
    DisposeObject()              OM_DISPOSE
    SetAttrs()/SetGadgetAttrs()  OM_SET
    GetAttr()                    OM_GET
&lt;/pre&gt;

==BOOPSI Examples==
Let's see basic examples of this OOP framework:

Getting an attribute
We'll query a MUI String object for its content:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
void f(Object *string)
{
    IPTR result;
    
    GetAttr(string, MUIA_String_Contents, &amp;result);
    printf(&quot;String content is: %s\n&quot;, (STRPTR)result);
}
&lt;/syntaxhighlight&gt;

Object * is the type of BOOPSI objects. 
IPTR must be used for the type of the result, which can be an integer or a pointer. An IPTR is always written in memory, so using a smaller type would lead to memory corruption! 
Here we query a MUI String object for its content: MUIA_String_Contents, as any other attribute, is a ULONG (it's a Tag) 
Zune applications use more often the get() and XGET() macros instead:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
get(string, MUIA_String_Contents, &amp;result);

result = XGET(string, MUIA_String_Contents);
&lt;/syntaxhighlight&gt;
Setting an attribute
Let's change the content of our string:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;, TAG_DONE);
&lt;/syntaxhighlight&gt;
Pointers parameters must be casted to IPTR to avoid warnings. 
After the object parameter, a taglist is passed to SetAttrs and thus must end with TAG_DONE. 
You'll find the set() macro useful:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
set(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;);
&lt;/syntaxhighlight&gt;
But it's only with SetAttrs() that you can set several attributes at once:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string,
         MUIA_Disabled, TRUE,
         MUIA_String_Contents, (IPTR)&quot;hmmm...&quot;,
         TAG_DONE);
&lt;/syntaxhighlight&gt;
Calling a method
Let's see the most called method in a Zune program, the event processing method called in your main loop:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
result = DoMethod(obj, MUIM_Application_NewInput, (IPTR)&amp;sigs);
&lt;/syntaxhighlight&gt;
Parameters are not a taglist, and thus don't end with TAG_DONE. 
You have to cast pointers to IPTR to avoid warnings.

==&quot;Hello world&quot; example sourcecode==

[http://www.aros.org/documentation/developers/zune/images/hello.png Screenshot 'Hello World']

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
// gcc hello.c -lmui
#include &lt;exec/types.h&gt;
#include &lt;libraries/mui.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

int main(void)
{
    Object *wnd, *app, *but;

    // GUI creation
    app = ApplicationObject,
        SubWindow, wnd = WindowObject,
            MUIA_Window_Title, &quot;Hello world!&quot;,
            WindowContents, VGroup,
                Child, TextObject,
                    MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,
                    End,
                Child, but = SimpleButton(&quot;_Ok&quot;),
                End,
            End,
        End;

    if (app != NULL)
    {
        ULONG sigs = 0;

        // Click Close gadget or hit Escape to quit
        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Click the button to quit
        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Open the window
        set(wnd, MUIA_Window_Open, TRUE);

        // Check that the window opened
        if (XGET(wnd, MUIA_Window_Open))
        {
            // Main loop
            while((LONG)DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
                  != MUIV_Application_ReturnID_Quit)
            {
                if (sigs)
                {
                    sigs = Wait(sigs | SIGBREAKF_CTRL_C);
                    if (sigs &amp; SIGBREAKF_CTRL_C)
                        break;
                }
            }
        }
        // Destroy our application and all its objects
        MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

===Remarks/General===
We don't manually open libraries, it's done automatically for us.

===GUI creation===
We use a macro-based language to easily build our GUI. A Zune application has always 1 and only 1 Application object:

:   &lt;code&gt;app = ApplicationObject,&lt;/code&gt;

An application can have 0, 1 or more Window objects. Most often a single one:

:       &lt;code&gt;SubWindow, wnd = WindowObject,&lt;/code&gt;

Be nice, give a title to the window:

:           &lt;code&gt;MUIA_Window_Title, &quot;Hello world!&quot;,&lt;/code&gt;

A window must have 1 and only 1 child, usually a group. This one is vertical, that means that its children will be arranged vertically:

:           &lt;code&gt;WindowContents, VGroup,&lt;/code&gt;

A group must have at least 1 child, here it's just a text:

:              &lt;code&gt; Child, TextObject,&lt;/code&gt;

Zune accepts various escape codes (here, to center the text) and newlines:

:                  &lt;code&gt; MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,&lt;/code&gt;

An End macro must match every xxxObject macro (here, TextObject):

:                   &lt;code&gt;End,&lt;/code&gt;

Let's add a second child to our group, a button! With a keyboard shortcut o indicated by an underscore:

:               &lt;code&gt;Child, but = SimpleButton(&quot;_Ok&quot;),&lt;/code&gt;

Finish the group:

:               &lt;code&gt;End,&lt;/code&gt;

Finish the window:

:           &lt;code&gt;End,&lt;/code&gt;

Finish the application:

:       &lt;code&gt;End;&lt;/code&gt;

So, who still needs a GUI builder? :-)

===Error handling===

If any of the object in the application tree can't be created, Zune destroys all the objects already created and application creation fails. If not, you have a fully working application:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
   if (app != NULL)
   {
       ...&lt;/syntaxhighlight&gt;

When you're done, just call MUI_DisposeObject() on your application object to destroy all the objects currently in the application, and free all the resources:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;       ...
       MUI_DisposeObject(app);
   }&lt;/syntaxhighlight&gt;


===Notifications===

Notifications are the simplest way to react on events. The principle? We want to be notified when a certain attribute of a certain object is set to a certain value:

:        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,

Here we'll listen to the MUIA_Window_CloseRequest of our Window object and be notified whenever this attribute is set to TRUE. So what happens when a notification is triggered? A message is sent to an object, here we tell our Application to return MUIV_Application_ReturnID_Quit on the next event loop iteration:

:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

As we can specify anything we want here, we have to tell the number of extra parameters we are supplying to MUIM_Notify: here, 2 parameters.

For the button, we listen to its MUIA_Pressed attribute: it's set to FALSE whenever the button is being released (reacting when it's pressed is bad practice, you may want to release the mouse outside of the button to cancel your action - plus we want to see how it looks when it's pressed). The action is the same as the previous, send a message to the application:

:        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

===Opening the window===
Windows aren't open until you ask them to:

:        set(wnd, MUIA_Window_Open, TRUE);

If all goes well, your window should be displayed at this point. But it can fail! So don't forget to check by querying the attribute, which should be TRUE:

:        if (XGET(wnd, MUIA_Window_Open))

===Main loop===
Let me introduce you my lil' friend, the ideal Zune event loop:

:        ULONG sigs = 0;

Don't forget to initialize the signals to 0 ... The test of the loop is the MUIM_Application_NewInput method:

:        ...
:        while((LONG) DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
:              != MUIV_Application_ReturnID_Quit)

It takes as input the signals of the events it has to process (result from Wait(), or 0), will modify this value to place the signals Zune is waiting for (for the next Wait()) and will return a value. This return value mechanism was historically the only way to react on events, but it was ugly and has been deprecated in favor of custom classes and object-oriented design.

The body of the loop is quite empty, we only wait for signals and handle Ctrl-C to break out of the loop:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
    {
    if (sigs)
        {
        sigs = Wait(sigs | SIGBREAKF_CTRL_C);
        if (sigs &amp; SIGBREAKF_CTRL_C)
             break;
        }
    }
&lt;/syntaxhighlight&gt;

===Conclusion===

This program gets you started with Zune, and allows you to toy with GUI design, but not more.

==Notification actions==

Notification allows you to respond to events your application/gui or any other object might cause.  Due to the attribute and method based nature of Zune, and a few special attributes, most applications can be almost completely automated through the use of Notification(s).

As seen in hello.c, you use MUIM_Notify to call a method if a certain condition happens. If you want your application to react in a specific way to events, you can use one of these schemes:

* Set An attribute.  You can automate the passing of values from gadgets,
::etc to other gadgets.  Setting values may also trigger other notification
::events.
      
* Invoke a method, for example:    
::'''MUIM_Application_ReturnID:''' you can ask your application to return an
:: arbitrary ID on the next loop iteration, and check for the value in
:: the loop. This is the dirty old way of doing things.
      
:: '''MUIM_CallHook,''' to call a standard Amiga callback hook: this is an
::average choice, not object-oriented but not that ugly either.
      
::'''custom method:''' the method belongs to one of your custom class. It 
::is the best solution as it supports object-oriented design in
::applications. It needs you to create custom classes so it may not 
::the easiest for beginners or people in a hurry.

==Zune Examples/Tutorials==

*Being an AmigaOS3.x MUI clone, all AmigaOS3.x MUI code serves as example code for using AROS Zune.
*MUI example sourcecode &quot;PSI.c&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*[http://code.google.com/p/guidetoamigacompatibleprogramming/source/browse/#svn/trunk/english Shinkuro's] Cross-Platform Guide gives information about compatible programming on Amiga-related platforms (Amiga, AROS, MorphOS) and [http://guidetoamigacompatibleprogramming.googlecode.com/svn-history/r6/trunk/english/CAP_4.txt MUI]
*[http://archive.is/20121225201004/robertnegro.wordpress.com/2012/10/30/aros-zune-programming-tutorials-for-beginners/ Good examples of Zune Main Classes]
*AROS itself contains lots of Zune examples. Download AROS sources and AROS contrib sources archives, take a look at the sourcecode of Zune programs. A good starting point are the Zune test programs, located in the SYS:Tests/Zune folder of AROS' binary distributions (e.g. the nightly build) - their sources can be found in the &quot;test/Zune&quot; folder of the AROS source archive.
*[[Aros/Developer/Zune/Examples|Zune example code collection]]

Some other good examples are here:

*[http://www.liquido2.com/tutorial/ An Introduction to AMIGA Programming Using C]
*[http://www.pcguru.plus.com/tutorial/introduction.html Programming AmigaOS in C]
*[http://library.morphzone.org/Magic_User_Interface_Programming Magic User Interface Programming] at [http://www.morphzone.org morphzone.org]
*[https://github.com/emartisoft/AmigaOS3.X-MUI-Examples Examples]

==Zune Reference==

*[http://aros.sourceforge.net/documentation/developers/zune-dev/index.php AROS Zune Development Manual] at [http://www.aros.org aros.org]
*[http://web.archive.org/web/20110526115419/http://www.sasg.com/mui/autodocs/index.html MUI Autodocs] online at [http://www.sasg.com sasg.com]
*MUI (=Zune) reference guide &quot;MUIDev.guide&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*MUI Reference information from AmigaOS documentation can be found e.g. [http://utilitybase.com/forum/index.php?action=vtopic&amp;forum=13 utilitybase.com/forum/...] or at [http://utilitybase.com/ref/ utilitybase.com/ref], it has a section on MUI. (Note: Information at that site is a little outdated, but still very helpful.) (2011-10-31: utilitybase.com currently down.)

==Tools==

===MUIBuilder===

A [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool native build] and [http://sourceforge.net/projects/muibuilder/ sourceforge svn repository] has been started and [[Aros/Developer/ZuneFurther]] documentation can be read. v3 is W.I.P. so it is not recommended for now.

This [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=5578&amp;forum=1&amp;post_id=52900#forumpost52900 thread] discussed using the m68k build and [http://www.mazze-online.de/files/mbtest.zip diff] file which modifications were necessary to make it build-able under AROS.

Summary
* added &quot;#define MUI_OBSOLETE&quot; to get some deprecated but needed defines
* changed/added some #include
* changed variable name Object to obj because Object is a type
* changed the Hook for the callback function
* last not least: added main.c which calls the functions to open/close the GUI.

Just go ahead and create your GUIS under any version of AROS or under amiga 68k version and do some modifications (which would be necessary for MorphOS/AmigaOS3/AmigaOS4, too).

===ChocolateCastle===

The [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool binary] which makes creating MUI classes and applications easier. Programmers using this system often avoid writing custom classes, being discouraged by a lot of boring and schematical typing. A significant part of a typical custom class may be generated automatically. This is usually 2 to 5 kB of source code. Automating this work speeds programming up and helps avoiding simple typing errors.

==Errors==
&lt;pre&gt;
Message  
Solution SetAttrs() is vararg version of SetAttrsA() and expects a complete taglist so you must add TAG_DONE and not TAG_END. 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols ... KeyString
Solution finally replaced KeyString(0,256,'f') by MUIA_CreateObject(MUIO_String,&quot;f&quot;,256)
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols... GetAttr
Solution you need:  #include &lt;proto/intuition.h&gt;
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution  #define MUI_OBSOLETE
&lt;/pre&gt;

{{BookCat}}

[[ru:Zune]]</text>
      <sha1>oy8tpdppi9ybdezz6ybob987wk3c1gd</sha1>
    </revision>
    <revision>
      <id>4668975</id>
      <parentid>4668974</parentid>
      <timestamp>2026-09-05T18:01:00Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668975</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20595" sha1="cz14v9fgkd2urcrqfossnqbfkrk8bi3" xml:space="preserve">{{ArosNav}}

==Introduction==

&lt;pre&gt;
version muimaster.library is 19 for 3.8 
                          is 20 for 3.9
                          is    for 4.0  dynamic tabs simplification 
                          is    for 5.0  
&lt;/pre&gt;

Zune is an object-oriented GUI toolkit. It is nearly a clone (at both API and Look&amp;Feel level) of MUI, a well-known Amiga shareware product by Stefan Stuntz. Therefore, MUI developers will feel at home here, while others will discover the concepts and qualities that Zune shares with MUI.

The programmer has a much easier time to design its GUI: no need for hardcoded values, Zune is font-sensitive, and adapts to any window size due to its layout system. He/she mostly needs to only specify the semantic of its GUI to Zune, which will arrange the low-level details automatically.

Zune is based on the [https://library.morph.zone/Short_BOOPSI_Overview BOOPSI] system, the framework inherited from AmigaOS (TM) for object-oriented programming in C. Zune [[Aros/Developer/Zune/Classes|classes]] does not derive from existing BOOPSI gadget classes; instead, the Notify class (base class of the Zune hierarchy) derives from the BOOPSI root class.

* Many AROS GUI components (windows, requesters, gadgets, images) are now programmed in an object-oriented way, using the BOOPSI/Zune toolkit. 
* Every such component is created as an object, not as a pointer to a system structure. That means no more filling structures with data. 
* Objects are manipulated using methods and by passing tags via the SetAttrs() function.

Creating Prefs from scratch with using our Zune Prefs classes.

A good introduction to the BOOPSI system is the [http://amigadev.elowar.com/read/ADCD_2.1/Libraries_Manual_guide/node01FF.html Chapter 12, &quot;BOOPSI - Object-oriented Intuition&quot;]. Here BOOPSI NewObject() has been replaced by MUI_NewObject(), DisposeObject() becomes MUI_DisposeObject(), etc.

==Prerequisites==

Some knowledge of [http://wiki.answers.com/Q/What_are_the_concepts_of_object_oriented_programming OOP] {{w|object-oriented programming}} is more than welcome.

Knowing AROS APIs and concepts like [[Aros/Developer/Docs/Libraries/Intuition|taglists]] and BOOPSI is essential. As Zune is a MUI clone, all the documentation pertaining to MUI is applicable to Zune. In particular, the latest available MUI developer kit and MUI autodocs can be found at [http://main.aminet.net/dev/mui/mui38dev.lha here]. In this LHA archive, 2 documents are warmly recommended:

 '''MUIdev.guide''', the MUI programmer documentation 
 and
 '''PSI.c''' source code, demonstrating Zune practices like OOP and dynamic object creation

==Zune basics and conventions==

MUI (= Zune) sticks a prefix on the start to signify what is being access/changed:

* MUIA_ attribute 
* MUIM_ method 
* MUIV_ special values

==BOOPSI Primer/Concepts==

===Class===
A class is defined by its name, its parent class and a dispatcher.

'''name''': either a string for the public classes, so that they may be used by any program in the system, or none if its a private class used only by a single application.

'''parent class''': all BOOPSI classes are forming a hierarchy rooted at the class aptly named rootclass. It allows each subclass to implement its own version of specific parent operation, or to fall back on the one provided by its parent. Also known as base class or super class.

'''dispatcher''': it gives access to all operations (called methods) provided by this class, ensuring that each operation is handled by the proper code or passed to its super class.

BOOPSI type for a class is Class * also known as IClass.

===Object===
An object is an instance of class: each object has its specific data, but all objects of the same class share the same behavior. An object has several classes if we count the parents of its true class (the most derived one) up to the rootclass.

BOOPSI type for an object is Object *. It has no field you can directly access.

When a Zune object is created and destroyed several methods are called:
&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;
If the documentation says that something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

===Attribute===
An attribute is related to the instance data of each object: you can not access these data directly, you can only set or get the attributes provided by an object to modify its internal state. An attribute is implemented as a Tag (ULONG value or'ed with TAG_USER).

GetAttr() and SetAttrs() are used to modify an object's attributes.

Attributes can be one or more of the following:

Initialization-settable (I) : the attribute can be given as parameter at the object creation.

Settable (S) : You can set this attribute at any time (or at least, not only creation).

Gettable (G) : You can get the value of this attribute.

===Method===
A BOOPSI method is a function which receives as parameters an object, a class and a message:

object: the object you act on

class: the considered class for this object.

message: contains a method ID which determines the function to call within a dispatcher, and is followed by its parameters.

To send a message to an object, use DoMethod(). It will use the true class first. If the class implements this method, it will handle it. Else it will try its parent class, until the message is handled or the rootclass is reached (in this case, the unknown message is silently discarded).

Summary, before a method can act on an object, it needs a BOOPSI message 
&lt;pre&gt;
    Function                     BOOPSI Method

    NewObject()                  OM_NEW
    DisposeObject()              OM_DISPOSE
    SetAttrs()/SetGadgetAttrs()  OM_SET
    GetAttr()                    OM_GET
&lt;/pre&gt;

==BOOPSI Examples==
Let's see basic examples of this OOP framework:

Getting an attribute
We'll query a MUI String object for its content:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
void f(Object *string)
{
    IPTR result;
    
    GetAttr(string, MUIA_String_Contents, &amp;result);
    printf(&quot;String content is: %s\n&quot;, (STRPTR)result);
}
&lt;/syntaxhighlight&gt;

Object * is the type of BOOPSI objects. 
IPTR must be used for the type of the result, which can be an integer or a pointer. An IPTR is always written in memory, so using a smaller type would lead to memory corruption! 
Here we query a MUI String object for its content: MUIA_String_Contents, as any other attribute, is a ULONG (it's a Tag) 
Zune applications use more often the get() and XGET() macros instead:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
get(string, MUIA_String_Contents, &amp;result);

result = XGET(string, MUIA_String_Contents);
&lt;/syntaxhighlight&gt;
Setting an attribute
Let's change the content of our string:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;, TAG_DONE);
&lt;/syntaxhighlight&gt;
Pointers parameters must be casted to IPTR to avoid warnings. 
After the object parameter, a taglist is passed to SetAttrs and thus must end with TAG_DONE. 
You'll find the set() macro useful:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
set(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;);
&lt;/syntaxhighlight&gt;
But it's only with SetAttrs() that you can set several attributes at once:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string,
         MUIA_Disabled, TRUE,
         MUIA_String_Contents, (IPTR)&quot;hmmm...&quot;,
         TAG_DONE);
&lt;/syntaxhighlight&gt;
Calling a method
Let's see the most called method in a Zune program, the event processing method called in your main loop:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
result = DoMethod(obj, MUIM_Application_NewInput, (IPTR)&amp;sigs);
&lt;/syntaxhighlight&gt;
Parameters are not a taglist, and thus don't end with TAG_DONE. 
You have to cast pointers to IPTR to avoid warnings.

==&quot;Hello world&quot; example sourcecode==

[http://www.aros.org/documentation/developers/zune/images/hello.png Screenshot 'Hello World']

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
// gcc hello.c -lmui
#include &lt;exec/types.h&gt;
#include &lt;libraries/mui.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

int main(void)
{
    Object *wnd, *app, *but;

    // GUI creation
    app = ApplicationObject,
        SubWindow, wnd = WindowObject,
            MUIA_Window_Title, &quot;Hello world!&quot;,
            WindowContents, VGroup,
                Child, TextObject,
                    MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,
                    End,
                Child, but = SimpleButton(&quot;_Ok&quot;),
                End,
            End,
        End;

    if (app != NULL)
    {
        ULONG sigs = 0;

        // Click Close gadget or hit Escape to quit
        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Click the button to quit
        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Open the window
        set(wnd, MUIA_Window_Open, TRUE);

        // Check that the window opened
        if (XGET(wnd, MUIA_Window_Open))
        {
            // Main loop
            while((LONG)DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
                  != MUIV_Application_ReturnID_Quit)
            {
                if (sigs)
                {
                    sigs = Wait(sigs | SIGBREAKF_CTRL_C);
                    if (sigs &amp; SIGBREAKF_CTRL_C)
                        break;
                }
            }
        }
        // Destroy our application and all its objects
        MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

===Remarks/General===
We don't manually open libraries, it's done automatically for us.

===GUI creation===
We use a macro-based language to easily build our GUI. A Zune application has always 1 and only 1 Application object:

:   &lt;code&gt;app = ApplicationObject,&lt;/code&gt;

An application can have 0, 1 or more Window objects. Most often a single one:

:       &lt;code&gt;SubWindow, wnd = WindowObject,&lt;/code&gt;

Be nice, give a title to the window:

:           &lt;code&gt;MUIA_Window_Title, &quot;Hello world!&quot;,&lt;/code&gt;

A window must have 1 and only 1 child, usually a group. This one is vertical, that means that its children will be arranged vertically:

:           &lt;code&gt;WindowContents, VGroup,&lt;/code&gt;

A group must have at least 1 child, here it's just a text:

:              &lt;code&gt; Child, TextObject,&lt;/code&gt;

Zune accepts various escape codes (here, to center the text) and newlines:

:                  &lt;code&gt; MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,&lt;/code&gt;

An End macro must match every xxxObject macro (here, TextObject):

:                   &lt;code&gt;End,&lt;/code&gt;

Let's add a second child to our group, a button! With a keyboard shortcut o indicated by an underscore:

:               &lt;code&gt;Child, but = SimpleButton(&quot;_Ok&quot;),&lt;/code&gt;

Finish the group:

:               &lt;code&gt;End,&lt;/code&gt;

Finish the window:

:           &lt;code&gt;End,&lt;/code&gt;

Finish the application:

:       &lt;code&gt;End;&lt;/code&gt;

So, who still needs a GUI builder? :-)

===Error handling===

If any of the object in the application tree can't be created, Zune destroys all the objects already created and application creation fails. If not, you have a fully working application:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
   if (app != NULL)
   {
       ...&lt;/syntaxhighlight&gt;

When you're done, just call MUI_DisposeObject() on your application object to destroy all the objects currently in the application, and free all the resources:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;       ...
       MUI_DisposeObject(app);
   }&lt;/syntaxhighlight&gt;


===Notifications===

Notifications are the simplest way to react on events. The principle? We want to be notified when a certain attribute of a certain object is set to a certain value:

:        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,

Here we'll listen to the MUIA_Window_CloseRequest of our Window object and be notified whenever this attribute is set to TRUE. So what happens when a notification is triggered? A message is sent to an object, here we tell our Application to return MUIV_Application_ReturnID_Quit on the next event loop iteration:

:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

As we can specify anything we want here, we have to tell the number of extra parameters we are supplying to MUIM_Notify: here, 2 parameters.

For the button, we listen to its MUIA_Pressed attribute: it's set to FALSE whenever the button is being released (reacting when it's pressed is bad practice, you may want to release the mouse outside of the button to cancel your action - plus we want to see how it looks when it's pressed). The action is the same as the previous, send a message to the application:

:        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

===Opening the window===
Windows aren't open until you ask them to:

:        set(wnd, MUIA_Window_Open, TRUE);

If all goes well, your window should be displayed at this point. But it can fail! So don't forget to check by querying the attribute, which should be TRUE:

:        if (XGET(wnd, MUIA_Window_Open))

===Main loop===
Let me introduce you my lil' friend, the ideal Zune event loop:

:        ULONG sigs = 0;

Don't forget to initialize the signals to 0 ... The test of the loop is the MUIM_Application_NewInput method:

:        ...
:        while((LONG) DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
:              != MUIV_Application_ReturnID_Quit)

It takes as input the signals of the events it has to process (result from Wait(), or 0), will modify this value to place the signals Zune is waiting for (for the next Wait()) and will return a value. This return value mechanism was historically the only way to react on events, but it was ugly and has been deprecated in favor of custom classes and object-oriented design.

The body of the loop is quite empty, we only wait for signals and handle Ctrl-C to break out of the loop:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
    {
    if (sigs)
        {
        sigs = Wait(sigs | SIGBREAKF_CTRL_C);
        if (sigs &amp; SIGBREAKF_CTRL_C)
             break;
        }
    }
&lt;/syntaxhighlight&gt;

===Conclusion===

This program gets you started with Zune, and allows you to toy with GUI design, but not more.

==Notification actions==

Notification allows you to respond to events your application/gui or any other object might cause.  Due to the attribute and method based nature of Zune, and a few special attributes, most applications can be almost completely automated through the use of Notification(s).

As seen in hello.c, you use MUIM_Notify to call a method if a certain condition happens. If you want your application to react in a specific way to events, you can use one of these schemes:

* Set An attribute.  You can automate the passing of values from gadgets,
::etc to other gadgets.  Setting values may also trigger other notification
::events.
      
* Invoke a method, for example:    
::'''MUIM_Application_ReturnID:''' you can ask your application to return an
:: arbitrary ID on the next loop iteration, and check for the value in
:: the loop. This is the dirty old way of doing things.
      
:: '''MUIM_CallHook,''' to call a standard Amiga callback hook: this is an
::average choice, not object-oriented but not that ugly either.
      
::'''custom method:''' the method belongs to one of your custom class. It 
::is the best solution as it supports object-oriented design in
::applications. It needs you to create custom classes so it may not 
::the easiest for beginners or people in a hurry.

==Zune Examples/Tutorials==

*some [https://arosarchives.os4depot.net/?function=showfile&amp;file=development/example/mui_examples.i386-aros.zip c src examples]
*Being an AmigaOS3.x MUI clone, all AmigaOS3.x MUI code serves as example code for using AROS Zune.
*MUI example sourcecode &quot;PSI.c&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*[http://code.google.com/p/guidetoamigacompatibleprogramming/source/browse/#svn/trunk/english Shinkuro's] Cross-Platform Guide gives information about compatible programming on Amiga-related platforms (Amiga, AROS, MorphOS) and [http://guidetoamigacompatibleprogramming.googlecode.com/svn-history/r6/trunk/english/CAP_4.txt MUI]
*[http://archive.is/20121225201004/robertnegro.wordpress.com/2012/10/30/aros-zune-programming-tutorials-for-beginners/ Good examples of Zune Main Classes]
*AROS itself contains lots of Zune examples. Download AROS sources and AROS contrib sources archives, take a look at the sourcecode of Zune programs. A good starting point are the Zune test programs, located in the SYS:Tests/Zune folder of AROS' binary distributions (e.g. the nightly build) - their sources can be found in the &quot;test/Zune&quot; folder of the AROS source archive.
*[[Aros/Developer/Zune/Examples|Zune example code collection]]

Some other good examples are here:

*[http://www.liquido2.com/tutorial/ An Introduction to AMIGA Programming Using C]
*[http://www.pcguru.plus.com/tutorial/introduction.html Programming AmigaOS in C]
*[http://library.morphzone.org/Magic_User_Interface_Programming Magic User Interface Programming] at [http://www.morphzone.org morphzone.org]
*[https://github.com/emartisoft/AmigaOS3.X-MUI-Examples Examples]

==Zune Reference==

*[http://aros.sourceforge.net/documentation/developers/zune-dev/index.php AROS Zune Development Manual] at [http://www.aros.org aros.org]
*[http://web.archive.org/web/20110526115419/http://www.sasg.com/mui/autodocs/index.html MUI Autodocs] online at [http://www.sasg.com sasg.com]
*MUI (=Zune) reference guide &quot;MUIDev.guide&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*MUI Reference information from AmigaOS documentation can be found e.g. [http://utilitybase.com/forum/index.php?action=vtopic&amp;forum=13 utilitybase.com/forum/...] or at [http://utilitybase.com/ref/ utilitybase.com/ref], it has a section on MUI. (Note: Information at that site is a little outdated, but still very helpful.) (2011-10-31: utilitybase.com currently down.)

==Tools==

===MUIBuilder===

A [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool native build] and [http://sourceforge.net/projects/muibuilder/ sourceforge svn repository] has been started and [[Aros/Developer/ZuneFurther]] documentation can be read. v3 is W.I.P. so it is not recommended for now.

This [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=5578&amp;forum=1&amp;post_id=52900#forumpost52900 thread] discussed using the m68k build and [http://www.mazze-online.de/files/mbtest.zip diff] file which modifications were necessary to make it build-able under AROS.

Summary
* added &quot;#define MUI_OBSOLETE&quot; to get some deprecated but needed defines
* changed/added some #include
* changed variable name Object to obj because Object is a type
* changed the Hook for the callback function
* last not least: added main.c which calls the functions to open/close the GUI.

Just go ahead and create your GUIS under any version of AROS or under amiga 68k version and do some modifications (which would be necessary for MorphOS/AmigaOS3/AmigaOS4, too).

===ChocolateCastle===

The [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool binary] which makes creating MUI classes and applications easier. Programmers using this system often avoid writing custom classes, being discouraged by a lot of boring and schematical typing. A significant part of a typical custom class may be generated automatically. This is usually 2 to 5 kB of source code. Automating this work speeds programming up and helps avoiding simple typing errors.

==Errors==
&lt;pre&gt;
Message  
Solution SetAttrs() is vararg version of SetAttrsA() and expects a complete taglist so you must add TAG_DONE and not TAG_END. 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols ... KeyString
Solution finally replaced KeyString(0,256,'f') by MUIA_CreateObject(MUIO_String,&quot;f&quot;,256)
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols... GetAttr
Solution you need:  #include &lt;proto/intuition.h&gt;
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution  #define MUI_OBSOLETE
&lt;/pre&gt;

{{BookCat}}

[[ru:Zune]]</text>
      <sha1>cz14v9fgkd2urcrqfossnqbfkrk8bi3</sha1>
    </revision>
    <revision>
      <id>4668976</id>
      <parentid>4668975</parentid>
      <timestamp>2026-09-05T18:02:58Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668976</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20473" sha1="1re5nrvuji3k8mz6cev2f5pmzurudee" xml:space="preserve">{{ArosNav}}

==Introduction==

&lt;pre&gt;
version muimaster.library is 19 for 3.8 
                          is 20 for 3.9
                          is    for 4.0  dynamic tabs simplification 
                          is    for 5.0  
&lt;/pre&gt;

Zune is an object-oriented GUI toolkit. It is nearly a clone (at both API and Look&amp;Feel level) of MUI, a well-known Amiga shareware product by Stefan Stuntz. Therefore, MUI developers will feel at home here, while others will discover the concepts and qualities that Zune shares with MUI.

The programmer has a much easier time to design its GUI: no need for hardcoded values, Zune is font-sensitive, and adapts to any window size due to its layout system. He/she mostly needs to only specify the semantic of its GUI to Zune, which will arrange the low-level details automatically.

Zune is based on the [https://library.morph.zone/Short_BOOPSI_Overview BOOPSI] system, the framework inherited from AmigaOS (TM) for object-oriented programming in C. Zune [[Aros/Developer/Zune/Classes|classes]] does not derive from existing BOOPSI gadget classes; instead, the Notify class (base class of the Zune hierarchy) derives from the BOOPSI root class.

* Many AROS GUI components (windows, requesters, gadgets, images) are now programmed in an object-oriented way, using the BOOPSI/Zune toolkit. 
* Every such component is created as an object, not as a pointer to a system structure. That means no more filling structures with data. 
* Objects are manipulated using methods and by passing tags via the SetAttrs() function.

Creating Prefs from scratch with using our Zune Prefs classes.

A good introduction to the BOOPSI system is the [http://amigadev.elowar.com/read/ADCD_2.1/Libraries_Manual_guide/node01FF.html Chapter 12, &quot;BOOPSI - Object-oriented Intuition&quot;]. Here BOOPSI NewObject() has been replaced by MUI_NewObject(), DisposeObject() becomes MUI_DisposeObject(), etc.

==Prerequisites==

Some knowledge of [http://wiki.answers.com/Q/What_are_the_concepts_of_object_oriented_programming OOP] {{w|object-oriented programming}} is more than welcome.

Knowing AROS APIs and concepts like [[Aros/Developer/Docs/Libraries/Intuition|taglists]] and BOOPSI is essential. As Zune is a MUI clone, all the documentation pertaining to MUI is applicable to Zune. In particular, the latest available MUI developer kit and MUI autodocs can be found at [http://main.aminet.net/dev/mui/mui38dev.lha here]. In this LHA archive, 2 documents are warmly recommended:

 '''MUIdev.guide''', the MUI programmer documentation 
 and
 '''PSI.c''' source code, demonstrating Zune practices like OOP and dynamic object creation

==Zune basics and conventions==

MUI (= Zune) sticks a prefix on the start to signify what is being access/changed:

* MUIA_ attribute 
* MUIM_ method 
* MUIV_ special values

==BOOPSI Primer/Concepts==

===Class===
A class is defined by its name, its parent class and a dispatcher.

'''name''': either a string for the public classes, so that they may be used by any program in the system, or none if its a private class used only by a single application.

'''parent class''': all BOOPSI classes are forming a hierarchy rooted at the class aptly named rootclass. It allows each subclass to implement its own version of specific parent operation, or to fall back on the one provided by its parent. Also known as base class or super class.

'''dispatcher''': it gives access to all operations (called methods) provided by this class, ensuring that each operation is handled by the proper code or passed to its super class.

BOOPSI type for a class is Class * also known as IClass.

===Object===
An object is an instance of class: each object has its specific data, but all objects of the same class share the same behavior. An object has several classes if we count the parents of its true class (the most derived one) up to the rootclass.

BOOPSI type for an object is Object *. It has no field you can directly access.

When a Zune object is created and destroyed several methods are called:
&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;
If the documentation says that something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

===Attribute===
An attribute is related to the instance data of each object: you can not access these data directly, you can only set or get the attributes provided by an object to modify its internal state. An attribute is implemented as a Tag (ULONG value or'ed with TAG_USER).

GetAttr() and SetAttrs() are used to modify an object's attributes.

Attributes can be one or more of the following:

Initialization-settable (I) : the attribute can be given as parameter at the object creation.

Settable (S) : You can set this attribute at any time (or at least, not only creation).

Gettable (G) : You can get the value of this attribute.

===Method===
A BOOPSI method is a function which receives as parameters an object, a class and a message:

object: the object you act on

class: the considered class for this object.

message: contains a method ID which determines the function to call within a dispatcher, and is followed by its parameters.

To send a message to an object, use DoMethod(). It will use the true class first. If the class implements this method, it will handle it. Else it will try its parent class, until the message is handled or the rootclass is reached (in this case, the unknown message is silently discarded).

Summary, before a method can act on an object, it needs a BOOPSI message 
&lt;pre&gt;
    Function                     BOOPSI Method

    NewObject()                  OM_NEW
    DisposeObject()              OM_DISPOSE
    SetAttrs()/SetGadgetAttrs()  OM_SET
    GetAttr()                    OM_GET
&lt;/pre&gt;

==BOOPSI Examples==
Let's see basic examples of this OOP framework:

Getting an attribute
We'll query a MUI String object for its content:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
void f(Object *string)
{
    IPTR result;
    
    GetAttr(string, MUIA_String_Contents, &amp;result);
    printf(&quot;String content is: %s\n&quot;, (STRPTR)result);
}
&lt;/syntaxhighlight&gt;

Object * is the type of BOOPSI objects. 
IPTR must be used for the type of the result, which can be an integer or a pointer. An IPTR is always written in memory, so using a smaller type would lead to memory corruption! 
Here we query a MUI String object for its content: MUIA_String_Contents, as any other attribute, is a ULONG (it's a Tag) 
Zune applications use more often the get() and XGET() macros instead:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
get(string, MUIA_String_Contents, &amp;result);

result = XGET(string, MUIA_String_Contents);
&lt;/syntaxhighlight&gt;
Setting an attribute
Let's change the content of our string:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;, TAG_DONE);
&lt;/syntaxhighlight&gt;
Pointers parameters must be casted to IPTR to avoid warnings. 
After the object parameter, a taglist is passed to SetAttrs and thus must end with TAG_DONE. 
You'll find the set() macro useful:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
set(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;);
&lt;/syntaxhighlight&gt;
But it's only with SetAttrs() that you can set several attributes at once:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string,
         MUIA_Disabled, TRUE,
         MUIA_String_Contents, (IPTR)&quot;hmmm...&quot;,
         TAG_DONE);
&lt;/syntaxhighlight&gt;
Calling a method
Let's see the most called method in a Zune program, the event processing method called in your main loop:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
result = DoMethod(obj, MUIM_Application_NewInput, (IPTR)&amp;sigs);
&lt;/syntaxhighlight&gt;
Parameters are not a taglist, and thus don't end with TAG_DONE. 
You have to cast pointers to IPTR to avoid warnings.

==&quot;Hello world&quot; example sourcecode==

[http://www.aros.org/documentation/developers/zune/images/hello.png Screenshot 'Hello World']

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
// gcc hello.c -lmui
#include &lt;exec/types.h&gt;
#include &lt;libraries/mui.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

int main(void)
{
    Object *wnd, *app, *but;

    // GUI creation
    app = ApplicationObject,
        SubWindow, wnd = WindowObject,
            MUIA_Window_Title, &quot;Hello world!&quot;,
            WindowContents, VGroup,
                Child, TextObject,
                    MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,
                    End,
                Child, but = SimpleButton(&quot;_Ok&quot;),
                End,
            End,
        End;

    if (app != NULL)
    {
        ULONG sigs = 0;

        // Click Close gadget or hit Escape to quit
        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Click the button to quit
        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Open the window
        set(wnd, MUIA_Window_Open, TRUE);

        // Check that the window opened
        if (XGET(wnd, MUIA_Window_Open))
        {
            // Main loop
            while((LONG)DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
                  != MUIV_Application_ReturnID_Quit)
            {
                if (sigs)
                {
                    sigs = Wait(sigs | SIGBREAKF_CTRL_C);
                    if (sigs &amp; SIGBREAKF_CTRL_C)
                        break;
                }
            }
        }
        // Destroy our application and all its objects
        MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

===Remarks/General===
We don't manually open libraries, it's done automatically for us.

===GUI creation===
We use a macro-based language to easily build our GUI. A Zune application has always 1 and only 1 Application object:

:   &lt;code&gt;app = ApplicationObject,&lt;/code&gt;

An application can have 0, 1 or more Window objects. Most often a single one:

:       &lt;code&gt;SubWindow, wnd = WindowObject,&lt;/code&gt;

Be nice, give a title to the window:

:           &lt;code&gt;MUIA_Window_Title, &quot;Hello world!&quot;,&lt;/code&gt;

A window must have 1 and only 1 child, usually a group. This one is vertical, that means that its children will be arranged vertically:

:           &lt;code&gt;WindowContents, VGroup,&lt;/code&gt;

A group must have at least 1 child, here it's just a text:

:              &lt;code&gt; Child, TextObject,&lt;/code&gt;

Zune accepts various escape codes (here, to center the text) and newlines:

:                  &lt;code&gt; MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,&lt;/code&gt;

An End macro must match every xxxObject macro (here, TextObject):

:                   &lt;code&gt;End,&lt;/code&gt;

Let's add a second child to our group, a button! With a keyboard shortcut o indicated by an underscore:

:               &lt;code&gt;Child, but = SimpleButton(&quot;_Ok&quot;),&lt;/code&gt;

Finish the group:

:               &lt;code&gt;End,&lt;/code&gt;

Finish the window:

:           &lt;code&gt;End,&lt;/code&gt;

Finish the application:

:       &lt;code&gt;End;&lt;/code&gt;

So, who still needs a GUI builder? :-)

===Error handling===

If any of the object in the application tree can't be created, Zune destroys all the objects already created and application creation fails. If not, you have a fully working application:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
   if (app != NULL)
   {
       ...&lt;/syntaxhighlight&gt;

When you're done, just call MUI_DisposeObject() on your application object to destroy all the objects currently in the application, and free all the resources:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;       ...
       MUI_DisposeObject(app);
   }&lt;/syntaxhighlight&gt;


===Notifications===

Notifications are the simplest way to react on events. The principle? We want to be notified when a certain attribute of a certain object is set to a certain value:

:        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,

Here we'll listen to the MUIA_Window_CloseRequest of our Window object and be notified whenever this attribute is set to TRUE. So what happens when a notification is triggered? A message is sent to an object, here we tell our Application to return MUIV_Application_ReturnID_Quit on the next event loop iteration:

:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

As we can specify anything we want here, we have to tell the number of extra parameters we are supplying to MUIM_Notify: here, 2 parameters.

For the button, we listen to its MUIA_Pressed attribute: it's set to FALSE whenever the button is being released (reacting when it's pressed is bad practice, you may want to release the mouse outside of the button to cancel your action - plus we want to see how it looks when it's pressed). The action is the same as the previous, send a message to the application:

:        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

===Opening the window===
Windows aren't open until you ask them to:

:        set(wnd, MUIA_Window_Open, TRUE);

If all goes well, your window should be displayed at this point. But it can fail! So don't forget to check by querying the attribute, which should be TRUE:

:        if (XGET(wnd, MUIA_Window_Open))

===Main loop===
Let me introduce you my lil' friend, the ideal Zune event loop:

:        ULONG sigs = 0;

Don't forget to initialize the signals to 0 ... The test of the loop is the MUIM_Application_NewInput method:

:        ...
:        while((LONG) DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
:              != MUIV_Application_ReturnID_Quit)

It takes as input the signals of the events it has to process (result from Wait(), or 0), will modify this value to place the signals Zune is waiting for (for the next Wait()) and will return a value. This return value mechanism was historically the only way to react on events, but it was ugly and has been deprecated in favor of custom classes and object-oriented design.

The body of the loop is quite empty, we only wait for signals and handle Ctrl-C to break out of the loop:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
    {
    if (sigs)
        {
        sigs = Wait(sigs | SIGBREAKF_CTRL_C);
        if (sigs &amp; SIGBREAKF_CTRL_C)
             break;
        }
    }
&lt;/syntaxhighlight&gt;

===Conclusion===

This program gets you started with Zune, and allows you to toy with GUI design, but not more.

==Notification actions==

Notification allows you to respond to events your application/gui or any other object might cause.  Due to the attribute and method based nature of Zune, and a few special attributes, most applications can be almost completely automated through the use of Notification(s).

As seen in hello.c, you use MUIM_Notify to call a method if a certain condition happens. If you want your application to react in a specific way to events, you can use one of these schemes:

* Set An attribute.  You can automate the passing of values from gadgets,
::etc to other gadgets.  Setting values may also trigger other notification
::events.
      
* Invoke a method, for example:    
::'''MUIM_Application_ReturnID:''' you can ask your application to return an
:: arbitrary ID on the next loop iteration, and check for the value in
:: the loop. This is the dirty old way of doing things.
      
:: '''MUIM_CallHook,''' to call a standard Amiga callback hook: this is an
::average choice, not object-oriented but not that ugly either.
      
::'''custom method:''' the method belongs to one of your custom class. It 
::is the best solution as it supports object-oriented design in
::applications. It needs you to create custom classes so it may not 
::the easiest for beginners or people in a hurry.

==Zune Examples/Tutorials==

*some [https://arosarchives.os4depot.net/?function=showfile&amp;file=development/example/mui_examples.i386-aros.zip c src examples]
*Being an AmigaOS3.x MUI clone, all AmigaOS3.x MUI code serves as example code for using AROS Zune.
*MUI example sourcecode &quot;PSI.c&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*[http://archive.is/20121225201004/robertnegro.wordpress.com/2012/10/30/aros-zune-programming-tutorials-for-beginners/ Good examples of Zune Main Classes]
*AROS itself contains lots of Zune examples. Download AROS sources and AROS contrib sources archives, take a look at the sourcecode of Zune programs. A good starting point are the Zune test programs, located in the SYS:Tests/Zune folder of AROS' binary distributions (e.g. the nightly build) - their sources can be found in the &quot;test/Zune&quot; folder of the AROS source archive.
*[[Aros/Developer/Zune/Examples|Zune example code collection]]

Some other good examples are here:

*[http://www.liquido2.com/tutorial/ An Introduction to AMIGA Programming Using C]
*[http://www.pcguru.plus.com/tutorial/introduction.html Programming AmigaOS in C]
*[http://library.morphzone.org/Magic_User_Interface_Programming Magic User Interface Programming] at [http://www.morphzone.org morphzone.org]
*[https://github.com/emartisoft/AmigaOS3.X-MUI-Examples Examples]
*[http://code.google.com/p/guidetoamigacompatibleprogramming/source/browse/#svn/trunk/english Shinkuro's] Cross-Platform Guide about compatible programming on Amiga-related platforms (Amiga, AROS, MorphOS) 

==Zune Reference==

*[http://aros.sourceforge.net/documentation/developers/zune-dev/index.php AROS Zune Development Manual] at [http://www.aros.org aros.org]
*[http://web.archive.org/web/20110526115419/http://www.sasg.com/mui/autodocs/index.html MUI Autodocs] online at [http://www.sasg.com sasg.com]
*MUI (=Zune) reference guide &quot;MUIDev.guide&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*MUI Reference information from AmigaOS documentation can be found e.g. [http://utilitybase.com/forum/index.php?action=vtopic&amp;forum=13 utilitybase.com/forum/...] or at [http://utilitybase.com/ref/ utilitybase.com/ref], it has a section on MUI. (Note: Information at that site is a little outdated, but still very helpful.) (2011-10-31: utilitybase.com currently down.)

==Tools==

===MUIBuilder===

A [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool native build] and [http://sourceforge.net/projects/muibuilder/ sourceforge svn repository] has been started and [[Aros/Developer/ZuneFurther]] documentation can be read. v3 is W.I.P. so it is not recommended for now.

This [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=5578&amp;forum=1&amp;post_id=52900#forumpost52900 thread] discussed using the m68k build and [http://www.mazze-online.de/files/mbtest.zip diff] file which modifications were necessary to make it build-able under AROS.

Summary
* added &quot;#define MUI_OBSOLETE&quot; to get some deprecated but needed defines
* changed/added some #include
* changed variable name Object to obj because Object is a type
* changed the Hook for the callback function
* last not least: added main.c which calls the functions to open/close the GUI.

Just go ahead and create your GUIS under any version of AROS or under amiga 68k version and do some modifications (which would be necessary for MorphOS/AmigaOS3/AmigaOS4, too).

===ChocolateCastle===

The [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool binary] which makes creating MUI classes and applications easier. Programmers using this system often avoid writing custom classes, being discouraged by a lot of boring and schematical typing. A significant part of a typical custom class may be generated automatically. This is usually 2 to 5 kB of source code. Automating this work speeds programming up and helps avoiding simple typing errors.

==Errors==
&lt;pre&gt;
Message  
Solution SetAttrs() is vararg version of SetAttrsA() and expects a complete taglist so you must add TAG_DONE and not TAG_END. 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols ... KeyString
Solution finally replaced KeyString(0,256,'f') by MUIA_CreateObject(MUIO_String,&quot;f&quot;,256)
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols... GetAttr
Solution you need:  #include &lt;proto/intuition.h&gt;
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution  #define MUI_OBSOLETE
&lt;/pre&gt;

{{BookCat}}

[[ru:Zune]]</text>
      <sha1>1re5nrvuji3k8mz6cev2f5pmzurudee</sha1>
    </revision>
    <revision>
      <id>4668977</id>
      <parentid>4668976</parentid>
      <timestamp>2026-09-05T18:04:05Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668977</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20479" sha1="jtgwemt1bcd11yb26x4m9xatpghtlnk" xml:space="preserve">{{ArosNav}}

==Introduction==

&lt;pre&gt;
version muimaster.library is 19 for 3.8 
                          is 20 for 3.9
                          is    for 4.0  dynamic tabs simplification 
                          is    for 5.0  
&lt;/pre&gt;

Zune is an object-oriented GUI toolkit. It is nearly a clone (at both API and Look&amp;Feel level) of MUI, a well-known Amiga shareware product by Stefan Stuntz. Therefore, MUI developers will feel at home here, while others will discover the concepts and qualities that Zune shares with MUI.

The programmer has a much easier time to design its GUI: no need for hardcoded values, Zune is font-sensitive, and adapts to any window size due to its layout system. He/she mostly needs to only specify the semantic of its GUI to Zune, which will arrange the low-level details automatically.

Zune is based on the [https://library.morph.zone/Short_BOOPSI_Overview BOOPSI] system, the framework inherited from AmigaOS (TM) for object-oriented programming in C. Zune [[Aros/Developer/Zune/Classes|classes]] does not derive from existing BOOPSI gadget classes; instead, the Notify class (base class of the Zune hierarchy) derives from the BOOPSI root class.

* Many AROS GUI components (windows, requesters, gadgets, images) are now programmed in an object-oriented way, using the BOOPSI/Zune toolkit. 
* Every such component is created as an object, not as a pointer to a system structure. That means no more filling structures with data. 
* Objects are manipulated using methods and by passing tags via the SetAttrs() function.

Creating Prefs from scratch with using our Zune Prefs classes.

A good introduction to the BOOPSI system is the [http://amigadev.elowar.com/read/ADCD_2.1/Libraries_Manual_guide/node01FF.html Chapter 12, &quot;BOOPSI - Object-oriented Intuition&quot;]. Here BOOPSI NewObject() has been replaced by MUI_NewObject(), DisposeObject() becomes MUI_DisposeObject(), etc.

==Prerequisites==

Some knowledge of [http://wiki.answers.com/Q/What_are_the_concepts_of_object_oriented_programming OOP] {{w|object-oriented programming}} is more than welcome.

Knowing AROS APIs and concepts like [[Aros/Developer/Docs/Libraries/Intuition|taglists]] and BOOPSI is essential. As Zune is a MUI clone, all the documentation pertaining to MUI is applicable to Zune. In particular, the latest available MUI developer kit and MUI autodocs can be found at [http://main.aminet.net/dev/mui/mui38dev.lha here]. In this LHA archive, 2 documents are warmly recommended:

 '''MUIdev.guide''', the MUI programmer documentation 
 and
 '''PSI.c''' source code, demonstrating Zune practices like OOP and dynamic object creation

==Zune basics and conventions==

MUI (= Zune) sticks a prefix on the start to signify what is being access/changed:

* MUIA_ attribute 
* MUIM_ method 
* MUIV_ special values

==BOOPSI Primer/Concepts==

===Class===
A class is defined by its name, its parent class and a dispatcher.

'''name''': either a string for the public classes, so that they may be used by any program in the system, or none if its a private class used only by a single application.

'''parent class''': all BOOPSI classes are forming a hierarchy rooted at the class aptly named rootclass. It allows each subclass to implement its own version of specific parent operation, or to fall back on the one provided by its parent. Also known as base class or super class.

'''dispatcher''': it gives access to all operations (called methods) provided by this class, ensuring that each operation is handled by the proper code or passed to its super class.

BOOPSI type for a class is Class * also known as IClass.

===Object===
An object is an instance of class: each object has its specific data, but all objects of the same class share the same behavior. An object has several classes if we count the parents of its true class (the most derived one) up to the rootclass.

BOOPSI type for an object is Object *. It has no field you can directly access.

When a Zune object is created and destroyed several methods are called:
&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;
If the documentation says that something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

===Attribute===
An attribute is related to the instance data of each object: you can not access these data directly, you can only set or get the attributes provided by an object to modify its internal state. An attribute is implemented as a Tag (ULONG value or'ed with TAG_USER).

GetAttr() and SetAttrs() are used to modify an object's attributes.

Attributes can be one or more of the following:

Initialization-settable (I) : the attribute can be given as parameter at the object creation.

Settable (S) : You can set this attribute at any time (or at least, not only creation).

Gettable (G) : You can get the value of this attribute.

===Method===
A BOOPSI method is a function which receives as parameters an object, a class and a message:

object: the object you act on

class: the considered class for this object.

message: contains a method ID which determines the function to call within a dispatcher, and is followed by its parameters.

To send a message to an object, use DoMethod(). It will use the true class first. If the class implements this method, it will handle it. Else it will try its parent class, until the message is handled or the rootclass is reached (in this case, the unknown message is silently discarded).

Summary, before a method can act on an object, it needs a BOOPSI message 
&lt;pre&gt;
    Function                     BOOPSI Method

    NewObject()                  OM_NEW
    DisposeObject()              OM_DISPOSE
    SetAttrs()/SetGadgetAttrs()  OM_SET
    GetAttr()                    OM_GET
&lt;/pre&gt;

==BOOPSI Examples==
Let's see basic examples of this OOP framework:

Getting an attribute
We'll query a MUI String object for its content:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
void f(Object *string)
{
    IPTR result;
    
    GetAttr(string, MUIA_String_Contents, &amp;result);
    printf(&quot;String content is: %s\n&quot;, (STRPTR)result);
}
&lt;/syntaxhighlight&gt;

Object * is the type of BOOPSI objects. 
IPTR must be used for the type of the result, which can be an integer or a pointer. An IPTR is always written in memory, so using a smaller type would lead to memory corruption! 
Here we query a MUI String object for its content: MUIA_String_Contents, as any other attribute, is a ULONG (it's a Tag) 
Zune applications use more often the get() and XGET() macros instead:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
get(string, MUIA_String_Contents, &amp;result);

result = XGET(string, MUIA_String_Contents);
&lt;/syntaxhighlight&gt;
Setting an attribute
Let's change the content of our string:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;, TAG_DONE);
&lt;/syntaxhighlight&gt;
Pointers parameters must be casted to IPTR to avoid warnings. 
After the object parameter, a taglist is passed to SetAttrs and thus must end with TAG_DONE. 
You'll find the set() macro useful:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
set(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;);
&lt;/syntaxhighlight&gt;
But it's only with SetAttrs() that you can set several attributes at once:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string,
         MUIA_Disabled, TRUE,
         MUIA_String_Contents, (IPTR)&quot;hmmm...&quot;,
         TAG_DONE);
&lt;/syntaxhighlight&gt;
Calling a method
Let's see the most called method in a Zune program, the event processing method called in your main loop:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
result = DoMethod(obj, MUIM_Application_NewInput, (IPTR)&amp;sigs);
&lt;/syntaxhighlight&gt;
Parameters are not a taglist, and thus don't end with TAG_DONE. 
You have to cast pointers to IPTR to avoid warnings.

==&quot;Hello world&quot; example sourcecode==

[http://www.aros.org/documentation/developers/zune/images/hello.png Screenshot 'Hello World']

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
// gcc hello.c -lmui
#include &lt;exec/types.h&gt;
#include &lt;libraries/mui.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

int main(void)
{
    Object *wnd, *app, *but;

    // GUI creation
    app = ApplicationObject,
        SubWindow, wnd = WindowObject,
            MUIA_Window_Title, &quot;Hello world!&quot;,
            WindowContents, VGroup,
                Child, TextObject,
                    MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,
                    End,
                Child, but = SimpleButton(&quot;_Ok&quot;),
                End,
            End,
        End;

    if (app != NULL)
    {
        ULONG sigs = 0;

        // Click Close gadget or hit Escape to quit
        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Click the button to quit
        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Open the window
        set(wnd, MUIA_Window_Open, TRUE);

        // Check that the window opened
        if (XGET(wnd, MUIA_Window_Open))
        {
            // Main loop
            while((LONG)DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
                  != MUIV_Application_ReturnID_Quit)
            {
                if (sigs)
                {
                    sigs = Wait(sigs | SIGBREAKF_CTRL_C);
                    if (sigs &amp; SIGBREAKF_CTRL_C)
                        break;
                }
            }
        }
        // Destroy our application and all its objects
        MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

===Remarks/General===
We don't manually open libraries, it's done automatically for us.

===GUI creation===
We use a macro-based language to easily build our GUI. A Zune application has always 1 and only 1 Application object:

:   &lt;code&gt;app = ApplicationObject,&lt;/code&gt;

An application can have 0, 1 or more Window objects. Most often a single one:

:       &lt;code&gt;SubWindow, wnd = WindowObject,&lt;/code&gt;

Be nice, give a title to the window:

:           &lt;code&gt;MUIA_Window_Title, &quot;Hello world!&quot;,&lt;/code&gt;

A window must have 1 and only 1 child, usually a group. This one is vertical, that means that its children will be arranged vertically:

:           &lt;code&gt;WindowContents, VGroup,&lt;/code&gt;

A group must have at least 1 child, here it's just a text:

:              &lt;code&gt; Child, TextObject,&lt;/code&gt;

Zune accepts various escape codes (here, to center the text) and newlines:

:                  &lt;code&gt; MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,&lt;/code&gt;

An End macro must match every xxxObject macro (here, TextObject):

:                   &lt;code&gt;End,&lt;/code&gt;

Let's add a second child to our group, a button! With a keyboard shortcut o indicated by an underscore:

:               &lt;code&gt;Child, but = SimpleButton(&quot;_Ok&quot;),&lt;/code&gt;

Finish the group:

:               &lt;code&gt;End,&lt;/code&gt;

Finish the window:

:           &lt;code&gt;End,&lt;/code&gt;

Finish the application:

:       &lt;code&gt;End;&lt;/code&gt;

So, who still needs a GUI builder? :-)

===Error handling===

If any of the object in the application tree can't be created, Zune destroys all the objects already created and application creation fails. If not, you have a fully working application:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
   if (app != NULL)
   {
       ...&lt;/syntaxhighlight&gt;

When you're done, just call MUI_DisposeObject() on your application object to destroy all the objects currently in the application, and free all the resources:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;       ...
       MUI_DisposeObject(app);
   }&lt;/syntaxhighlight&gt;


===Notifications===

Notifications are the simplest way to react on events. The principle? We want to be notified when a certain attribute of a certain object is set to a certain value:

:        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,

Here we'll listen to the MUIA_Window_CloseRequest of our Window object and be notified whenever this attribute is set to TRUE. So what happens when a notification is triggered? A message is sent to an object, here we tell our Application to return MUIV_Application_ReturnID_Quit on the next event loop iteration:

:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

As we can specify anything we want here, we have to tell the number of extra parameters we are supplying to MUIM_Notify: here, 2 parameters.

For the button, we listen to its MUIA_Pressed attribute: it's set to FALSE whenever the button is being released (reacting when it's pressed is bad practice, you may want to release the mouse outside of the button to cancel your action - plus we want to see how it looks when it's pressed). The action is the same as the previous, send a message to the application:

:        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

===Opening the window===
Windows aren't open until you ask them to:

:        set(wnd, MUIA_Window_Open, TRUE);

If all goes well, your window should be displayed at this point. But it can fail! So don't forget to check by querying the attribute, which should be TRUE:

:        if (XGET(wnd, MUIA_Window_Open))

===Main loop===
Let me introduce you my lil' friend, the ideal Zune event loop:

:        ULONG sigs = 0;

Don't forget to initialize the signals to 0 ... The test of the loop is the MUIM_Application_NewInput method:

:        ...
:        while((LONG) DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
:              != MUIV_Application_ReturnID_Quit)

It takes as input the signals of the events it has to process (result from Wait(), or 0), will modify this value to place the signals Zune is waiting for (for the next Wait()) and will return a value. This return value mechanism was historically the only way to react on events, but it was ugly and has been deprecated in favor of custom classes and object-oriented design.

The body of the loop is quite empty, we only wait for signals and handle Ctrl-C to break out of the loop:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
    {
    if (sigs)
        {
        sigs = Wait(sigs | SIGBREAKF_CTRL_C);
        if (sigs &amp; SIGBREAKF_CTRL_C)
             break;
        }
    }
&lt;/syntaxhighlight&gt;

===Conclusion===

This program gets you started with Zune, and allows you to toy with GUI design, but not more.

==Notification actions==

Notification allows you to respond to events your application/gui or any other object might cause.  Due to the attribute and method based nature of Zune, and a few special attributes, most applications can be almost completely automated through the use of Notification(s).

As seen in hello.c, you use MUIM_Notify to call a method if a certain condition happens. If you want your application to react in a specific way to events, you can use one of these schemes:

* Set An attribute.  You can automate the passing of values from gadgets,
::etc to other gadgets.  Setting values may also trigger other notification
::events.
      
* Invoke a method, for example:    
::'''MUIM_Application_ReturnID:''' you can ask your application to return an
:: arbitrary ID on the next loop iteration, and check for the value in
:: the loop. This is the dirty old way of doing things.
      
:: '''MUIM_CallHook,''' to call a standard Amiga callback hook: this is an
::average choice, not object-oriented but not that ugly either.
      
::'''custom method:''' the method belongs to one of your custom class. It 
::is the best solution as it supports object-oriented design in
::applications. It needs you to create custom classes so it may not 
::the easiest for beginners or people in a hurry.

==Zune Examples/Tutorials==

*some [https://arosarchives.os4depot.net/?function=showfile&amp;file=development/example/mui_examples.i386-aros.zip c src examples]
*Being an AmigaOS3.x MUI clone, all AmigaOS3.x MUI code serves as example code for using AROS Zune.
*MUI example sourcecode &quot;PSI.c&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*[http://archive.is/20121225201004/robertnegro.wordpress.com/2012/10/30/aros-zune-programming-tutorials-for-beginners/ Good examples of Zune Main Classes]
*AROS itself contains lots of Zune examples. Download AROS sources and AROS contrib sources archives, take a look at the sourcecode of Zune programs. A good starting point are the Zune test programs, maybe located in the SYS:Demos/Zune folder of AROS' binary distributions (e.g. the nightly build) - their sources can be found in the &quot;test/Zune&quot; folder of the AROS source archive.
*[[Aros/Developer/Zune/Examples|Zune example code collection]]

Some other good examples are here:

*[http://www.liquido2.com/tutorial/ An Introduction to AMIGA Programming Using C]
*[http://www.pcguru.plus.com/tutorial/introduction.html Programming AmigaOS in C]
*[http://library.morphzone.org/Magic_User_Interface_Programming Magic User Interface Programming] at [http://www.morphzone.org morphzone.org]
*[https://github.com/emartisoft/AmigaOS3.X-MUI-Examples Examples]
*[http://code.google.com/p/guidetoamigacompatibleprogramming/source/browse/#svn/trunk/english Shinkuro's] Cross-Platform Guide about compatible programming on Amiga-related platforms (Amiga, AROS, MorphOS) 

==Zune Reference==

*[http://aros.sourceforge.net/documentation/developers/zune-dev/index.php AROS Zune Development Manual] at [http://www.aros.org aros.org]
*[http://web.archive.org/web/20110526115419/http://www.sasg.com/mui/autodocs/index.html MUI Autodocs] online at [http://www.sasg.com sasg.com]
*MUI (=Zune) reference guide &quot;MUIDev.guide&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*MUI Reference information from AmigaOS documentation can be found e.g. [http://utilitybase.com/forum/index.php?action=vtopic&amp;forum=13 utilitybase.com/forum/...] or at [http://utilitybase.com/ref/ utilitybase.com/ref], it has a section on MUI. (Note: Information at that site is a little outdated, but still very helpful.) (2011-10-31: utilitybase.com currently down.)

==Tools==

===MUIBuilder===

A [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool native build] and [http://sourceforge.net/projects/muibuilder/ sourceforge svn repository] has been started and [[Aros/Developer/ZuneFurther]] documentation can be read. v3 is W.I.P. so it is not recommended for now.

This [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=5578&amp;forum=1&amp;post_id=52900#forumpost52900 thread] discussed using the m68k build and [http://www.mazze-online.de/files/mbtest.zip diff] file which modifications were necessary to make it build-able under AROS.

Summary
* added &quot;#define MUI_OBSOLETE&quot; to get some deprecated but needed defines
* changed/added some #include
* changed variable name Object to obj because Object is a type
* changed the Hook for the callback function
* last not least: added main.c which calls the functions to open/close the GUI.

Just go ahead and create your GUIS under any version of AROS or under amiga 68k version and do some modifications (which would be necessary for MorphOS/AmigaOS3/AmigaOS4, too).

===ChocolateCastle===

The [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool binary] which makes creating MUI classes and applications easier. Programmers using this system often avoid writing custom classes, being discouraged by a lot of boring and schematical typing. A significant part of a typical custom class may be generated automatically. This is usually 2 to 5 kB of source code. Automating this work speeds programming up and helps avoiding simple typing errors.

==Errors==
&lt;pre&gt;
Message  
Solution SetAttrs() is vararg version of SetAttrsA() and expects a complete taglist so you must add TAG_DONE and not TAG_END. 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols ... KeyString
Solution finally replaced KeyString(0,256,'f') by MUIA_CreateObject(MUIO_String,&quot;f&quot;,256)
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols... GetAttr
Solution you need:  #include &lt;proto/intuition.h&gt;
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution  #define MUI_OBSOLETE
&lt;/pre&gt;

{{BookCat}}

[[ru:Zune]]</text>
      <sha1>jtgwemt1bcd11yb26x4m9xatpghtlnk</sha1>
    </revision>
    <revision>
      <id>4668978</id>
      <parentid>4668977</parentid>
      <timestamp>2026-09-05T18:05:08Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668978</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20337" sha1="m6o98vlorsg921lyfvtqwm00iru67tb" xml:space="preserve">{{ArosNav}}

==Introduction==

&lt;pre&gt;
version muimaster.library is 19 for 3.8 
                          is 20 for 3.9
                          is    for 4.0  dynamic tabs simplification 
                          is    for 5.0  
&lt;/pre&gt;

Zune is an object-oriented GUI toolkit. It is nearly a clone (at both API and Look&amp;Feel level) of MUI, a well-known Amiga shareware product by Stefan Stuntz. Therefore, MUI developers will feel at home here, while others will discover the concepts and qualities that Zune shares with MUI.

The programmer has a much easier time to design its GUI: no need for hardcoded values, Zune is font-sensitive, and adapts to any window size due to its layout system. He/she mostly needs to only specify the semantic of its GUI to Zune, which will arrange the low-level details automatically.

Zune is based on the [https://library.morph.zone/Short_BOOPSI_Overview BOOPSI] system, the framework inherited from AmigaOS (TM) for object-oriented programming in C. Zune [[Aros/Developer/Zune/Classes|classes]] does not derive from existing BOOPSI gadget classes; instead, the Notify class (base class of the Zune hierarchy) derives from the BOOPSI root class.

* Many AROS GUI components (windows, requesters, gadgets, images) are now programmed in an object-oriented way, using the BOOPSI/Zune toolkit. 
* Every such component is created as an object, not as a pointer to a system structure. That means no more filling structures with data. 
* Objects are manipulated using methods and by passing tags via the SetAttrs() function.

Creating Prefs from scratch with using our Zune Prefs classes.

A good introduction to the BOOPSI system is the [http://amigadev.elowar.com/read/ADCD_2.1/Libraries_Manual_guide/node01FF.html Chapter 12, &quot;BOOPSI - Object-oriented Intuition&quot;]. Here BOOPSI NewObject() has been replaced by MUI_NewObject(), DisposeObject() becomes MUI_DisposeObject(), etc.

==Prerequisites==

Some knowledge of [http://wiki.answers.com/Q/What_are_the_concepts_of_object_oriented_programming OOP] {{w|object-oriented programming}} is more than welcome.

Knowing AROS APIs and concepts like [[Aros/Developer/Docs/Libraries/Intuition|taglists]] and BOOPSI is essential. As Zune is a MUI clone, all the documentation pertaining to MUI is applicable to Zune. In particular, the latest available MUI developer kit and MUI autodocs can be found at [http://main.aminet.net/dev/mui/mui38dev.lha here]. In this LHA archive, 2 documents are warmly recommended:

 '''MUIdev.guide''', the MUI programmer documentation 
 and
 '''PSI.c''' source code, demonstrating Zune practices like OOP and dynamic object creation

==Zune basics and conventions==

MUI (= Zune) sticks a prefix on the start to signify what is being access/changed:

* MUIA_ attribute 
* MUIM_ method 
* MUIV_ special values

==BOOPSI Primer/Concepts==

===Class===
A class is defined by its name, its parent class and a dispatcher.

'''name''': either a string for the public classes, so that they may be used by any program in the system, or none if its a private class used only by a single application.

'''parent class''': all BOOPSI classes are forming a hierarchy rooted at the class aptly named rootclass. It allows each subclass to implement its own version of specific parent operation, or to fall back on the one provided by its parent. Also known as base class or super class.

'''dispatcher''': it gives access to all operations (called methods) provided by this class, ensuring that each operation is handled by the proper code or passed to its super class.

BOOPSI type for a class is Class * also known as IClass.

===Object===
An object is an instance of class: each object has its specific data, but all objects of the same class share the same behavior. An object has several classes if we count the parents of its true class (the most derived one) up to the rootclass.

BOOPSI type for an object is Object *. It has no field you can directly access.

When a Zune object is created and destroyed several methods are called:
&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;
If the documentation says that something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

===Attribute===
An attribute is related to the instance data of each object: you can not access these data directly, you can only set or get the attributes provided by an object to modify its internal state. An attribute is implemented as a Tag (ULONG value or'ed with TAG_USER).

GetAttr() and SetAttrs() are used to modify an object's attributes.

Attributes can be one or more of the following:

Initialization-settable (I) : the attribute can be given as parameter at the object creation.

Settable (S) : You can set this attribute at any time (or at least, not only creation).

Gettable (G) : You can get the value of this attribute.

===Method===
A BOOPSI method is a function which receives as parameters an object, a class and a message:

object: the object you act on

class: the considered class for this object.

message: contains a method ID which determines the function to call within a dispatcher, and is followed by its parameters.

To send a message to an object, use DoMethod(). It will use the true class first. If the class implements this method, it will handle it. Else it will try its parent class, until the message is handled or the rootclass is reached (in this case, the unknown message is silently discarded).

Summary, before a method can act on an object, it needs a BOOPSI message 
&lt;pre&gt;
    Function                     BOOPSI Method

    NewObject()                  OM_NEW
    DisposeObject()              OM_DISPOSE
    SetAttrs()/SetGadgetAttrs()  OM_SET
    GetAttr()                    OM_GET
&lt;/pre&gt;

==BOOPSI Examples==
Let's see basic examples of this OOP framework:

Getting an attribute
We'll query a MUI String object for its content:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
void f(Object *string)
{
    IPTR result;
    
    GetAttr(string, MUIA_String_Contents, &amp;result);
    printf(&quot;String content is: %s\n&quot;, (STRPTR)result);
}
&lt;/syntaxhighlight&gt;

Object * is the type of BOOPSI objects. 
IPTR must be used for the type of the result, which can be an integer or a pointer. An IPTR is always written in memory, so using a smaller type would lead to memory corruption! 
Here we query a MUI String object for its content: MUIA_String_Contents, as any other attribute, is a ULONG (it's a Tag) 
Zune applications use more often the get() and XGET() macros instead:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
get(string, MUIA_String_Contents, &amp;result);

result = XGET(string, MUIA_String_Contents);
&lt;/syntaxhighlight&gt;
Setting an attribute
Let's change the content of our string:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;, TAG_DONE);
&lt;/syntaxhighlight&gt;
Pointers parameters must be casted to IPTR to avoid warnings. 
After the object parameter, a taglist is passed to SetAttrs and thus must end with TAG_DONE. 
You'll find the set() macro useful:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
set(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;);
&lt;/syntaxhighlight&gt;
But it's only with SetAttrs() that you can set several attributes at once:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string,
         MUIA_Disabled, TRUE,
         MUIA_String_Contents, (IPTR)&quot;hmmm...&quot;,
         TAG_DONE);
&lt;/syntaxhighlight&gt;
Calling a method
Let's see the most called method in a Zune program, the event processing method called in your main loop:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
result = DoMethod(obj, MUIM_Application_NewInput, (IPTR)&amp;sigs);
&lt;/syntaxhighlight&gt;
Parameters are not a taglist, and thus don't end with TAG_DONE. 
You have to cast pointers to IPTR to avoid warnings.

==&quot;Hello world&quot; example sourcecode==

[http://www.aros.org/documentation/developers/zune/images/hello.png Screenshot 'Hello World']

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
// gcc hello.c -lmui
#include &lt;exec/types.h&gt;
#include &lt;libraries/mui.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

int main(void)
{
    Object *wnd, *app, *but;

    // GUI creation
    app = ApplicationObject,
        SubWindow, wnd = WindowObject,
            MUIA_Window_Title, &quot;Hello world!&quot;,
            WindowContents, VGroup,
                Child, TextObject,
                    MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,
                    End,
                Child, but = SimpleButton(&quot;_Ok&quot;),
                End,
            End,
        End;

    if (app != NULL)
    {
        ULONG sigs = 0;

        // Click Close gadget or hit Escape to quit
        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Click the button to quit
        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Open the window
        set(wnd, MUIA_Window_Open, TRUE);

        // Check that the window opened
        if (XGET(wnd, MUIA_Window_Open))
        {
            // Main loop
            while((LONG)DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
                  != MUIV_Application_ReturnID_Quit)
            {
                if (sigs)
                {
                    sigs = Wait(sigs | SIGBREAKF_CTRL_C);
                    if (sigs &amp; SIGBREAKF_CTRL_C)
                        break;
                }
            }
        }
        // Destroy our application and all its objects
        MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

===Remarks/General===
We don't manually open libraries, it's done automatically for us.

===GUI creation===
We use a macro-based language to easily build our GUI. A Zune application has always 1 and only 1 Application object:

:   &lt;code&gt;app = ApplicationObject,&lt;/code&gt;

An application can have 0, 1 or more Window objects. Most often a single one:

:       &lt;code&gt;SubWindow, wnd = WindowObject,&lt;/code&gt;

Be nice, give a title to the window:

:           &lt;code&gt;MUIA_Window_Title, &quot;Hello world!&quot;,&lt;/code&gt;

A window must have 1 and only 1 child, usually a group. This one is vertical, that means that its children will be arranged vertically:

:           &lt;code&gt;WindowContents, VGroup,&lt;/code&gt;

A group must have at least 1 child, here it's just a text:

:              &lt;code&gt; Child, TextObject,&lt;/code&gt;

Zune accepts various escape codes (here, to center the text) and newlines:

:                  &lt;code&gt; MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,&lt;/code&gt;

An End macro must match every xxxObject macro (here, TextObject):

:                   &lt;code&gt;End,&lt;/code&gt;

Let's add a second child to our group, a button! With a keyboard shortcut o indicated by an underscore:

:               &lt;code&gt;Child, but = SimpleButton(&quot;_Ok&quot;),&lt;/code&gt;

Finish the group:

:               &lt;code&gt;End,&lt;/code&gt;

Finish the window:

:           &lt;code&gt;End,&lt;/code&gt;

Finish the application:

:       &lt;code&gt;End;&lt;/code&gt;

So, who still needs a GUI builder? :-)

===Error handling===

If any of the object in the application tree can't be created, Zune destroys all the objects already created and application creation fails. If not, you have a fully working application:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
   if (app != NULL)
   {
       ...&lt;/syntaxhighlight&gt;

When you're done, just call MUI_DisposeObject() on your application object to destroy all the objects currently in the application, and free all the resources:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;       ...
       MUI_DisposeObject(app);
   }&lt;/syntaxhighlight&gt;


===Notifications===

Notifications are the simplest way to react on events. The principle? We want to be notified when a certain attribute of a certain object is set to a certain value:

:        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,

Here we'll listen to the MUIA_Window_CloseRequest of our Window object and be notified whenever this attribute is set to TRUE. So what happens when a notification is triggered? A message is sent to an object, here we tell our Application to return MUIV_Application_ReturnID_Quit on the next event loop iteration:

:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

As we can specify anything we want here, we have to tell the number of extra parameters we are supplying to MUIM_Notify: here, 2 parameters.

For the button, we listen to its MUIA_Pressed attribute: it's set to FALSE whenever the button is being released (reacting when it's pressed is bad practice, you may want to release the mouse outside of the button to cancel your action - plus we want to see how it looks when it's pressed). The action is the same as the previous, send a message to the application:

:        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

===Opening the window===
Windows aren't open until you ask them to:

:        set(wnd, MUIA_Window_Open, TRUE);

If all goes well, your window should be displayed at this point. But it can fail! So don't forget to check by querying the attribute, which should be TRUE:

:        if (XGET(wnd, MUIA_Window_Open))

===Main loop===
Let me introduce you my lil' friend, the ideal Zune event loop:

:        ULONG sigs = 0;

Don't forget to initialize the signals to 0 ... The test of the loop is the MUIM_Application_NewInput method:

:        ...
:        while((LONG) DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
:              != MUIV_Application_ReturnID_Quit)

It takes as input the signals of the events it has to process (result from Wait(), or 0), will modify this value to place the signals Zune is waiting for (for the next Wait()) and will return a value. This return value mechanism was historically the only way to react on events, but it was ugly and has been deprecated in favor of custom classes and object-oriented design.

The body of the loop is quite empty, we only wait for signals and handle Ctrl-C to break out of the loop:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
    {
    if (sigs)
        {
        sigs = Wait(sigs | SIGBREAKF_CTRL_C);
        if (sigs &amp; SIGBREAKF_CTRL_C)
             break;
        }
    }
&lt;/syntaxhighlight&gt;

===Conclusion===

This program gets you started with Zune, and allows you to toy with GUI design, but not more.

==Notification actions==

Notification allows you to respond to events your application/gui or any other object might cause.  Due to the attribute and method based nature of Zune, and a few special attributes, most applications can be almost completely automated through the use of Notification(s).

As seen in hello.c, you use MUIM_Notify to call a method if a certain condition happens. If you want your application to react in a specific way to events, you can use one of these schemes:

* Set An attribute.  You can automate the passing of values from gadgets,
::etc to other gadgets.  Setting values may also trigger other notification
::events.
      
* Invoke a method, for example:    
::'''MUIM_Application_ReturnID:''' you can ask your application to return an
:: arbitrary ID on the next loop iteration, and check for the value in
:: the loop. This is the dirty old way of doing things.
      
:: '''MUIM_CallHook,''' to call a standard Amiga callback hook: this is an
::average choice, not object-oriented but not that ugly either.
      
::'''custom method:''' the method belongs to one of your custom class. It 
::is the best solution as it supports object-oriented design in
::applications. It needs you to create custom classes so it may not 
::the easiest for beginners or people in a hurry.

==Zune Examples/Tutorials==

*some [https://arosarchives.os4depot.net/?function=showfile&amp;file=development/example/mui_examples.i386-aros.zip c src examples]
*Being an AmigaOS3.x MUI clone, all AmigaOS3.x MUI code serves as example code for using AROS Zune.
*MUI example sourcecode &quot;PSI.c&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*[http://archive.is/20121225201004/robertnegro.wordpress.com/2012/10/30/aros-zune-programming-tutorials-for-beginners/ Good examples of Zune Main Classes]
*AROS itself contains lots of Zune examples. Download AROS sources and AROS contrib sources archives, take a look at the sourcecode of Zune programs. A good starting point are the Zune test programs, maybe located in the SYS:Demos/Zune folder of AROS' binary distributions (e.g. the nightly build) - their sources can be found in the &quot;test/Zune&quot; folder of the AROS source archive.
*[[Aros/Developer/Zune/Examples|Zune example code collection]]

Some other good examples are here:

*[http://www.liquido2.com/tutorial/ An Introduction to AMIGA Programming Using C]
*[http://www.pcguru.plus.com/tutorial/introduction.html Programming AmigaOS in C]
*[https://github.com/emartisoft/AmigaOS3.X-MUI-Examples Examples]
*[http://code.google.com/p/guidetoamigacompatibleprogramming/source/browse/#svn/trunk/english Shinkuro's] Cross-Platform Guide about compatible programming on Amiga-related platforms (Amiga, AROS, MorphOS) 

==Zune Reference==

*[http://aros.sourceforge.net/documentation/developers/zune-dev/index.php AROS Zune Development Manual] at [http://www.aros.org aros.org]
*[http://web.archive.org/web/20110526115419/http://www.sasg.com/mui/autodocs/index.html MUI Autodocs] online at [http://www.sasg.com sasg.com]
*MUI (=Zune) reference guide &quot;MUIDev.guide&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*MUI Reference information from AmigaOS documentation can be found e.g. [http://utilitybase.com/forum/index.php?action=vtopic&amp;forum=13 utilitybase.com/forum/...] or at [http://utilitybase.com/ref/ utilitybase.com/ref], it has a section on MUI. (Note: Information at that site is a little outdated, but still very helpful.) (2011-10-31: utilitybase.com currently down.)

==Tools==

===MUIBuilder===

A [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool native build] and [http://sourceforge.net/projects/muibuilder/ sourceforge svn repository] has been started and [[Aros/Developer/ZuneFurther]] documentation can be read. v3 is W.I.P. so it is not recommended for now.

This [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=5578&amp;forum=1&amp;post_id=52900#forumpost52900 thread] discussed using the m68k build and [http://www.mazze-online.de/files/mbtest.zip diff] file which modifications were necessary to make it build-able under AROS.

Summary
* added &quot;#define MUI_OBSOLETE&quot; to get some deprecated but needed defines
* changed/added some #include
* changed variable name Object to obj because Object is a type
* changed the Hook for the callback function
* last not least: added main.c which calls the functions to open/close the GUI.

Just go ahead and create your GUIS under any version of AROS or under amiga 68k version and do some modifications (which would be necessary for MorphOS/AmigaOS3/AmigaOS4, too).

===ChocolateCastle===

The [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool binary] which makes creating MUI classes and applications easier. Programmers using this system often avoid writing custom classes, being discouraged by a lot of boring and schematical typing. A significant part of a typical custom class may be generated automatically. This is usually 2 to 5 kB of source code. Automating this work speeds programming up and helps avoiding simple typing errors.

==Errors==
&lt;pre&gt;
Message  
Solution SetAttrs() is vararg version of SetAttrsA() and expects a complete taglist so you must add TAG_DONE and not TAG_END. 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols ... KeyString
Solution finally replaced KeyString(0,256,'f') by MUIA_CreateObject(MUIO_String,&quot;f&quot;,256)
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols... GetAttr
Solution you need:  #include &lt;proto/intuition.h&gt;
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution  #define MUI_OBSOLETE
&lt;/pre&gt;

{{BookCat}}

[[ru:Zune]]</text>
      <sha1>m6o98vlorsg921lyfvtqwm00iru67tb</sha1>
    </revision>
    <revision>
      <id>4668979</id>
      <parentid>4668978</parentid>
      <timestamp>2026-09-05T18:07:16Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668979</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19886" sha1="qkqu3bedqpv5w9zaeq6tnhl36smj60s" xml:space="preserve">{{ArosNav}}

==Introduction==

&lt;pre&gt;
version muimaster.library is 19 for 3.8 
                          is 20 for 3.9
                          is    for 4.0  dynamic tabs simplification 
                          is    for 5.0  
&lt;/pre&gt;

Zune is an object-oriented GUI toolkit. It is nearly a clone (at both API and Look&amp;Feel level) of MUI, a well-known Amiga shareware product by Stefan Stuntz. Therefore, MUI developers will feel at home here, while others will discover the concepts and qualities that Zune shares with MUI.

The programmer has a much easier time to design its GUI: no need for hardcoded values, Zune is font-sensitive, and adapts to any window size due to its layout system. He/she mostly needs to only specify the semantic of its GUI to Zune, which will arrange the low-level details automatically.

Zune is based on the [https://library.morph.zone/Short_BOOPSI_Overview BOOPSI] system, the framework inherited from AmigaOS (TM) for object-oriented programming in C. Zune [[Aros/Developer/Zune/Classes|classes]] does not derive from existing BOOPSI gadget classes; instead, the Notify class (base class of the Zune hierarchy) derives from the BOOPSI root class.

* Many AROS GUI components (windows, requesters, gadgets, images) are now programmed in an object-oriented way, using the BOOPSI/Zune toolkit. 
* Every such component is created as an object, not as a pointer to a system structure. That means no more filling structures with data. 
* Objects are manipulated using methods and by passing tags via the SetAttrs() function.

Creating Prefs from scratch with using our Zune Prefs classes.

A good introduction to the BOOPSI system is the [http://amigadev.elowar.com/read/ADCD_2.1/Libraries_Manual_guide/node01FF.html Chapter 12, &quot;BOOPSI - Object-oriented Intuition&quot;]. Here BOOPSI NewObject() has been replaced by MUI_NewObject(), DisposeObject() becomes MUI_DisposeObject(), etc.

==Prerequisites==

Some knowledge of [http://wiki.answers.com/Q/What_are_the_concepts_of_object_oriented_programming OOP] {{w|object-oriented programming}} is more than welcome.

Knowing AROS APIs and concepts like [[Aros/Developer/Docs/Libraries/Intuition|taglists]] and BOOPSI is essential. As Zune is a MUI clone, all the documentation pertaining to MUI is applicable to Zune. In particular, the latest available MUI developer kit and MUI autodocs can be found at [http://main.aminet.net/dev/mui/mui38dev.lha here]. In this LHA archive, 2 documents are warmly recommended:

 '''MUIdev.guide''', the MUI programmer documentation 
 and
 '''PSI.c''' source code, demonstrating Zune practices like OOP and dynamic object creation

==Zune basics and conventions==

MUI (= Zune) sticks a prefix on the start to signify what is being access/changed:

* MUIA_ attribute 
* MUIM_ method 
* MUIV_ special values

==BOOPSI Primer/Concepts==

===Class===
A class is defined by its name, its parent class and a dispatcher.

'''name''': either a string for the public classes, so that they may be used by any program in the system, or none if its a private class used only by a single application.

'''parent class''': all BOOPSI classes are forming a hierarchy rooted at the class aptly named rootclass. It allows each subclass to implement its own version of specific parent operation, or to fall back on the one provided by its parent. Also known as base class or super class.

'''dispatcher''': it gives access to all operations (called methods) provided by this class, ensuring that each operation is handled by the proper code or passed to its super class.

BOOPSI type for a class is Class * also known as IClass.

===Object===
An object is an instance of class: each object has its specific data, but all objects of the same class share the same behavior. An object has several classes if we count the parents of its true class (the most derived one) up to the rootclass.

BOOPSI type for an object is Object *. It has no field you can directly access.

When a Zune object is created and destroyed several methods are called:
&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;
If the documentation says that something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

===Attribute===
An attribute is related to the instance data of each object: you can not access these data directly, you can only set or get the attributes provided by an object to modify its internal state. An attribute is implemented as a Tag (ULONG value or'ed with TAG_USER).

GetAttr() and SetAttrs() are used to modify an object's attributes.

Attributes can be one or more of the following:

Initialization-settable (I) : the attribute can be given as parameter at the object creation.

Settable (S) : You can set this attribute at any time (or at least, not only creation).

Gettable (G) : You can get the value of this attribute.

===Method===
A BOOPSI method is a function which receives as parameters an object, a class and a message:

object: the object you act on

class: the considered class for this object.

message: contains a method ID which determines the function to call within a dispatcher, and is followed by its parameters.

To send a message to an object, use DoMethod(). It will use the true class first. If the class implements this method, it will handle it. Else it will try its parent class, until the message is handled or the rootclass is reached (in this case, the unknown message is silently discarded).

Summary, before a method can act on an object, it needs a BOOPSI message 
&lt;pre&gt;
    Function                     BOOPSI Method

    NewObject()                  OM_NEW
    DisposeObject()              OM_DISPOSE
    SetAttrs()/SetGadgetAttrs()  OM_SET
    GetAttr()                    OM_GET
&lt;/pre&gt;

==BOOPSI Examples==
Let's see basic examples of this OOP framework:

Getting an attribute
We'll query a MUI String object for its content:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
void f(Object *string)
{
    IPTR result;
    
    GetAttr(string, MUIA_String_Contents, &amp;result);
    printf(&quot;String content is: %s\n&quot;, (STRPTR)result);
}
&lt;/syntaxhighlight&gt;

Object * is the type of BOOPSI objects. 
IPTR must be used for the type of the result, which can be an integer or a pointer. An IPTR is always written in memory, so using a smaller type would lead to memory corruption! 
Here we query a MUI String object for its content: MUIA_String_Contents, as any other attribute, is a ULONG (it's a Tag) 
Zune applications use more often the get() and XGET() macros instead:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
get(string, MUIA_String_Contents, &amp;result);

result = XGET(string, MUIA_String_Contents);
&lt;/syntaxhighlight&gt;
Setting an attribute
Let's change the content of our string:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;, TAG_DONE);
&lt;/syntaxhighlight&gt;
Pointers parameters must be casted to IPTR to avoid warnings. 
After the object parameter, a taglist is passed to SetAttrs and thus must end with TAG_DONE. 
You'll find the set() macro useful:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
set(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;);
&lt;/syntaxhighlight&gt;
But it's only with SetAttrs() that you can set several attributes at once:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string,
         MUIA_Disabled, TRUE,
         MUIA_String_Contents, (IPTR)&quot;hmmm...&quot;,
         TAG_DONE);
&lt;/syntaxhighlight&gt;
Calling a method
Let's see the most called method in a Zune program, the event processing method called in your main loop:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
result = DoMethod(obj, MUIM_Application_NewInput, (IPTR)&amp;sigs);
&lt;/syntaxhighlight&gt;
Parameters are not a taglist, and thus don't end with TAG_DONE. 
You have to cast pointers to IPTR to avoid warnings.

==&quot;Hello world&quot; example sourcecode==

[http://www.aros.org/documentation/developers/zune/images/hello.png Screenshot 'Hello World']

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
// gcc hello.c -lmui
#include &lt;exec/types.h&gt;
#include &lt;libraries/mui.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

int main(void)
{
    Object *wnd, *app, *but;

    // GUI creation
    app = ApplicationObject,
        SubWindow, wnd = WindowObject,
            MUIA_Window_Title, &quot;Hello world!&quot;,
            WindowContents, VGroup,
                Child, TextObject,
                    MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,
                    End,
                Child, but = SimpleButton(&quot;_Ok&quot;),
                End,
            End,
        End;

    if (app != NULL)
    {
        ULONG sigs = 0;

        // Click Close gadget or hit Escape to quit
        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Click the button to quit
        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Open the window
        set(wnd, MUIA_Window_Open, TRUE);

        // Check that the window opened
        if (XGET(wnd, MUIA_Window_Open))
        {
            // Main loop
            while((LONG)DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
                  != MUIV_Application_ReturnID_Quit)
            {
                if (sigs)
                {
                    sigs = Wait(sigs | SIGBREAKF_CTRL_C);
                    if (sigs &amp; SIGBREAKF_CTRL_C)
                        break;
                }
            }
        }
        // Destroy our application and all its objects
        MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

===Remarks/General===
We don't manually open libraries, it's done automatically for us.

===GUI creation===
We use a macro-based language to easily build our GUI. A Zune application has always 1 and only 1 Application object:

:   &lt;code&gt;app = ApplicationObject,&lt;/code&gt;

An application can have 0, 1 or more Window objects. Most often a single one:

:       &lt;code&gt;SubWindow, wnd = WindowObject,&lt;/code&gt;

Be nice, give a title to the window:

:           &lt;code&gt;MUIA_Window_Title, &quot;Hello world!&quot;,&lt;/code&gt;

A window must have 1 and only 1 child, usually a group. This one is vertical, that means that its children will be arranged vertically:

:           &lt;code&gt;WindowContents, VGroup,&lt;/code&gt;

A group must have at least 1 child, here it's just a text:

:              &lt;code&gt; Child, TextObject,&lt;/code&gt;

Zune accepts various escape codes (here, to center the text) and newlines:

:                  &lt;code&gt; MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,&lt;/code&gt;

An End macro must match every xxxObject macro (here, TextObject):

:                   &lt;code&gt;End,&lt;/code&gt;

Let's add a second child to our group, a button! With a keyboard shortcut o indicated by an underscore:

:               &lt;code&gt;Child, but = SimpleButton(&quot;_Ok&quot;),&lt;/code&gt;

Finish the group:

:               &lt;code&gt;End,&lt;/code&gt;

Finish the window:

:           &lt;code&gt;End,&lt;/code&gt;

Finish the application:

:       &lt;code&gt;End;&lt;/code&gt;

So, who still needs a GUI builder? :-)

===Error handling===

If any of the object in the application tree can't be created, Zune destroys all the objects already created and application creation fails. If not, you have a fully working application:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
   if (app != NULL)
   {
       ...&lt;/syntaxhighlight&gt;

When you're done, just call MUI_DisposeObject() on your application object to destroy all the objects currently in the application, and free all the resources:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;       ...
       MUI_DisposeObject(app);
   }&lt;/syntaxhighlight&gt;


===Notifications===

Notifications are the simplest way to react on events. The principle? We want to be notified when a certain attribute of a certain object is set to a certain value:

:        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,

Here we'll listen to the MUIA_Window_CloseRequest of our Window object and be notified whenever this attribute is set to TRUE. So what happens when a notification is triggered? A message is sent to an object, here we tell our Application to return MUIV_Application_ReturnID_Quit on the next event loop iteration:

:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

As we can specify anything we want here, we have to tell the number of extra parameters we are supplying to MUIM_Notify: here, 2 parameters.

For the button, we listen to its MUIA_Pressed attribute: it's set to FALSE whenever the button is being released (reacting when it's pressed is bad practice, you may want to release the mouse outside of the button to cancel your action - plus we want to see how it looks when it's pressed). The action is the same as the previous, send a message to the application:

:        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

===Opening the window===
Windows aren't open until you ask them to:

:        set(wnd, MUIA_Window_Open, TRUE);

If all goes well, your window should be displayed at this point. But it can fail! So don't forget to check by querying the attribute, which should be TRUE:

:        if (XGET(wnd, MUIA_Window_Open))

===Main loop===
Let me introduce you my lil' friend, the ideal Zune event loop:

:        ULONG sigs = 0;

Don't forget to initialize the signals to 0 ... The test of the loop is the MUIM_Application_NewInput method:

:        ...
:        while((LONG) DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
:              != MUIV_Application_ReturnID_Quit)

It takes as input the signals of the events it has to process (result from Wait(), or 0), will modify this value to place the signals Zune is waiting for (for the next Wait()) and will return a value. This return value mechanism was historically the only way to react on events, but it was ugly and has been deprecated in favor of custom classes and object-oriented design.

The body of the loop is quite empty, we only wait for signals and handle Ctrl-C to break out of the loop:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
    {
    if (sigs)
        {
        sigs = Wait(sigs | SIGBREAKF_CTRL_C);
        if (sigs &amp; SIGBREAKF_CTRL_C)
             break;
        }
    }
&lt;/syntaxhighlight&gt;

===Conclusion===

This program gets you started with Zune, and allows you to toy with GUI design, but not more.

==Notification actions==

Notification allows you to respond to events your application/gui or any other object might cause.  Due to the attribute and method based nature of Zune, and a few special attributes, most applications can be almost completely automated through the use of Notification(s).

As seen in hello.c, you use MUIM_Notify to call a method if a certain condition happens. If you want your application to react in a specific way to events, you can use one of these schemes:

* Set An attribute.  You can automate the passing of values from gadgets,
::etc to other gadgets.  Setting values may also trigger other notification
::events.
      
* Invoke a method, for example:    
::'''MUIM_Application_ReturnID:''' you can ask your application to return an
:: arbitrary ID on the next loop iteration, and check for the value in
:: the loop. This is the dirty old way of doing things.
      
:: '''MUIM_CallHook,''' to call a standard Amiga callback hook: this is an
::average choice, not object-oriented but not that ugly either.
      
::'''custom method:''' the method belongs to one of your custom class. It 
::is the best solution as it supports object-oriented design in
::applications. It needs you to create custom classes so it may not 
::the easiest for beginners or people in a hurry.

==Zune Examples/Tutorials==

*some [https://arosarchives.os4depot.net/?function=showfile&amp;file=development/example/mui_examples.i386-aros.zip c src examples]
*Being an AmigaOS3.x MUI clone, all AmigaOS3.x MUI code serves as example code for using AROS Zune.
*MUI example sourcecode &quot;PSI.c&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*[http://archive.is/20121225201004/robertnegro.wordpress.com/2012/10/30/aros-zune-programming-tutorials-for-beginners/ Good examples of Zune Main Classes]
*AROS itself contains lots of Zune examples. Download AROS sources and AROS contrib sources archives, take a look at the sourcecode of Zune programs. A good starting point are the Zune test programs, maybe located in the SYS:Demos/Zune folder of AROS' binary distributions (e.g. the nightly build) - their sources can be found in the &quot;test/Zune&quot; folder of the AROS source archive.
*[[Aros/Developer/Zune/Examples|Zune example code collection]]

Some other good examples are here:

*[https://github.com/emartisoft/AmigaOS3.X-MUI-Examples Examples]
*[http://code.google.com/p/guidetoamigacompatibleprogramming/source/browse/#svn/trunk/english Shinkuro's] Cross-Platform Guide about compatible programming on Amiga-related platforms (Amiga, AROS, MorphOS) 

==Zune Reference==

*[http://aros.sourceforge.net/documentation/developers/zune-dev/index.php AROS Zune Development Manual] at [http://www.aros.org aros.org]
*[http://web.archive.org/web/20110526115419/http://www.sasg.com/mui/autodocs/index.html MUI Autodocs] online at [http://www.sasg.com sasg.com]
*MUI (=Zune) reference guide &quot;MUIDev.guide&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*[http://www.liquido2.com/tutorial/ An Introduction to AMIGA Programming Using C]

==Tools==

===MUIBuilder===

A [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool native build] and [http://sourceforge.net/projects/muibuilder/ sourceforge svn repository] has been started and [[Aros/Developer/ZuneFurther]] documentation can be read. v3 is W.I.P. so it is not recommended for now.

This [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=5578&amp;forum=1&amp;post_id=52900#forumpost52900 thread] discussed using the m68k build and [http://www.mazze-online.de/files/mbtest.zip diff] file which modifications were necessary to make it build-able under AROS.

Summary
* added &quot;#define MUI_OBSOLETE&quot; to get some deprecated but needed defines
* changed/added some #include
* changed variable name Object to obj because Object is a type
* changed the Hook for the callback function
* last not least: added main.c which calls the functions to open/close the GUI.

Just go ahead and create your GUIS under any version of AROS or under amiga 68k version and do some modifications (which would be necessary for MorphOS/AmigaOS3/AmigaOS4, too).

===ChocolateCastle===

The [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool binary] which makes creating MUI classes and applications easier. Programmers using this system often avoid writing custom classes, being discouraged by a lot of boring and schematical typing. A significant part of a typical custom class may be generated automatically. This is usually 2 to 5 kB of source code. Automating this work speeds programming up and helps avoiding simple typing errors.

==Errors==
&lt;pre&gt;
Message  
Solution SetAttrs() is vararg version of SetAttrsA() and expects a complete taglist so you must add TAG_DONE and not TAG_END. 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols ... KeyString
Solution finally replaced KeyString(0,256,'f') by MUIA_CreateObject(MUIO_String,&quot;f&quot;,256)
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols... GetAttr
Solution you need:  #include &lt;proto/intuition.h&gt;
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution  #define MUI_OBSOLETE
&lt;/pre&gt;

{{BookCat}}

[[ru:Zune]]</text>
      <sha1>qkqu3bedqpv5w9zaeq6tnhl36smj60s</sha1>
    </revision>
    <revision>
      <id>4668980</id>
      <parentid>4668979</parentid>
      <timestamp>2026-09-05T18:08:02Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668980</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19806" sha1="5v4pxj8dsydueptb352rmso3aws2svj" xml:space="preserve">{{ArosNav}}

==Introduction==

&lt;pre&gt;
version muimaster.library is 19 for 3.8 
                          is 20 for 3.9
                          is    for 4.0  dynamic tabs simplification 
                          is    for 5.0  
&lt;/pre&gt;

Zune is an object-oriented GUI toolkit. It is nearly a clone (at both API and Look&amp;Feel level) of MUI, a well-known Amiga shareware product by Stefan Stuntz. Therefore, MUI developers will feel at home here, while others will discover the concepts and qualities that Zune shares with MUI.

The programmer has a much easier time to design its GUI: no need for hardcoded values, Zune is font-sensitive, and adapts to any window size due to its layout system. He/she mostly needs to only specify the semantic of its GUI to Zune, which will arrange the low-level details automatically.

Zune is based on the [https://library.morph.zone/Short_BOOPSI_Overview BOOPSI] system, the framework inherited from AmigaOS (TM) for object-oriented programming in C. Zune [[Aros/Developer/Zune/Classes|classes]] does not derive from existing BOOPSI gadget classes; instead, the Notify class (base class of the Zune hierarchy) derives from the BOOPSI root class.

* Many AROS GUI components (windows, requesters, gadgets, images) are now programmed in an object-oriented way, using the BOOPSI/Zune toolkit. 
* Every such component is created as an object, not as a pointer to a system structure. That means no more filling structures with data. 
* Objects are manipulated using methods and by passing tags via the SetAttrs() function.

Creating Prefs from scratch with using our Zune Prefs classes.

A good introduction to the BOOPSI system is the [http://amigadev.elowar.com/read/ADCD_2.1/Libraries_Manual_guide/node01FF.html Chapter 12, &quot;BOOPSI - Object-oriented Intuition&quot;]. Here BOOPSI NewObject() has been replaced by MUI_NewObject(), DisposeObject() becomes MUI_DisposeObject(), etc.

==Prerequisites==

Some knowledge of [http://wiki.answers.com/Q/What_are_the_concepts_of_object_oriented_programming OOP] {{w|object-oriented programming}} is more than welcome.

Knowing AROS APIs and concepts like [[Aros/Developer/Docs/Libraries/Intuition|taglists]] and BOOPSI is essential. As Zune is a MUI clone, all the documentation pertaining to MUI is applicable to Zune. In particular, the latest available MUI developer kit and MUI autodocs can be found at [http://main.aminet.net/dev/mui/mui38dev.lha here]. In this LHA archive, 2 documents are warmly recommended:

 '''MUIdev.guide''', the MUI programmer documentation 
 and
 '''PSI.c''' source code, demonstrating Zune practices like OOP and dynamic object creation

==Zune basics and conventions==

MUI (= Zune) sticks a prefix on the start to signify what is being access/changed:

* MUIA_ attribute 
* MUIM_ method 
* MUIV_ special values

==BOOPSI Primer/Concepts==

===Class===
A class is defined by its name, its parent class and a dispatcher.

'''name''': either a string for the public classes, so that they may be used by any program in the system, or none if its a private class used only by a single application.

'''parent class''': all BOOPSI classes are forming a hierarchy rooted at the class aptly named rootclass. It allows each subclass to implement its own version of specific parent operation, or to fall back on the one provided by its parent. Also known as base class or super class.

'''dispatcher''': it gives access to all operations (called methods) provided by this class, ensuring that each operation is handled by the proper code or passed to its super class.

BOOPSI type for a class is Class * also known as IClass.

===Object===
An object is an instance of class: each object has its specific data, but all objects of the same class share the same behavior. An object has several classes if we count the parents of its true class (the most derived one) up to the rootclass.

BOOPSI type for an object is Object *. It has no field you can directly access.

When a Zune object is created and destroyed several methods are called:
&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;
If the documentation says that something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

===Attribute===
An attribute is related to the instance data of each object: you can not access these data directly, you can only set or get the attributes provided by an object to modify its internal state. An attribute is implemented as a Tag (ULONG value or'ed with TAG_USER).

GetAttr() and SetAttrs() are used to modify an object's attributes.

Attributes can be one or more of the following:

Initialization-settable (I) : the attribute can be given as parameter at the object creation.

Settable (S) : You can set this attribute at any time (or at least, not only creation).

Gettable (G) : You can get the value of this attribute.

===Method===
A BOOPSI method is a function which receives as parameters an object, a class and a message:

object: the object you act on

class: the considered class for this object.

message: contains a method ID which determines the function to call within a dispatcher, and is followed by its parameters.

To send a message to an object, use DoMethod(). It will use the true class first. If the class implements this method, it will handle it. Else it will try its parent class, until the message is handled or the rootclass is reached (in this case, the unknown message is silently discarded).

Summary, before a method can act on an object, it needs a BOOPSI message 
&lt;pre&gt;
    Function                     BOOPSI Method

    NewObject()                  OM_NEW
    DisposeObject()              OM_DISPOSE
    SetAttrs()/SetGadgetAttrs()  OM_SET
    GetAttr()                    OM_GET
&lt;/pre&gt;

==BOOPSI Examples==
Let's see basic examples of this OOP framework:

Getting an attribute
We'll query a MUI String object for its content:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
void f(Object *string)
{
    IPTR result;
    
    GetAttr(string, MUIA_String_Contents, &amp;result);
    printf(&quot;String content is: %s\n&quot;, (STRPTR)result);
}
&lt;/syntaxhighlight&gt;

Object * is the type of BOOPSI objects. 
IPTR must be used for the type of the result, which can be an integer or a pointer. An IPTR is always written in memory, so using a smaller type would lead to memory corruption! 
Here we query a MUI String object for its content: MUIA_String_Contents, as any other attribute, is a ULONG (it's a Tag) 
Zune applications use more often the get() and XGET() macros instead:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
get(string, MUIA_String_Contents, &amp;result);

result = XGET(string, MUIA_String_Contents);
&lt;/syntaxhighlight&gt;
Setting an attribute
Let's change the content of our string:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;, TAG_DONE);
&lt;/syntaxhighlight&gt;
Pointers parameters must be casted to IPTR to avoid warnings. 
After the object parameter, a taglist is passed to SetAttrs and thus must end with TAG_DONE. 
You'll find the set() macro useful:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
set(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;);
&lt;/syntaxhighlight&gt;
But it's only with SetAttrs() that you can set several attributes at once:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string,
         MUIA_Disabled, TRUE,
         MUIA_String_Contents, (IPTR)&quot;hmmm...&quot;,
         TAG_DONE);
&lt;/syntaxhighlight&gt;
Calling a method
Let's see the most called method in a Zune program, the event processing method called in your main loop:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
result = DoMethod(obj, MUIM_Application_NewInput, (IPTR)&amp;sigs);
&lt;/syntaxhighlight&gt;
Parameters are not a taglist, and thus don't end with TAG_DONE. 
You have to cast pointers to IPTR to avoid warnings.

==&quot;Hello world&quot; example sourcecode==

[http://www.aros.org/documentation/developers/zune/images/hello.png Screenshot 'Hello World']

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
// gcc hello.c -lmui
#include &lt;exec/types.h&gt;
#include &lt;libraries/mui.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

int main(void)
{
    Object *wnd, *app, *but;

    // GUI creation
    app = ApplicationObject,
        SubWindow, wnd = WindowObject,
            MUIA_Window_Title, &quot;Hello world!&quot;,
            WindowContents, VGroup,
                Child, TextObject,
                    MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,
                    End,
                Child, but = SimpleButton(&quot;_Ok&quot;),
                End,
            End,
        End;

    if (app != NULL)
    {
        ULONG sigs = 0;

        // Click Close gadget or hit Escape to quit
        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Click the button to quit
        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Open the window
        set(wnd, MUIA_Window_Open, TRUE);

        // Check that the window opened
        if (XGET(wnd, MUIA_Window_Open))
        {
            // Main loop
            while((LONG)DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
                  != MUIV_Application_ReturnID_Quit)
            {
                if (sigs)
                {
                    sigs = Wait(sigs | SIGBREAKF_CTRL_C);
                    if (sigs &amp; SIGBREAKF_CTRL_C)
                        break;
                }
            }
        }
        // Destroy our application and all its objects
        MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

===Remarks/General===
We don't manually open libraries, it's done automatically for us.

===GUI creation===
We use a macro-based language to easily build our GUI. A Zune application has always 1 and only 1 Application object:

:   &lt;code&gt;app = ApplicationObject,&lt;/code&gt;

An application can have 0, 1 or more Window objects. Most often a single one:

:       &lt;code&gt;SubWindow, wnd = WindowObject,&lt;/code&gt;

Be nice, give a title to the window:

:           &lt;code&gt;MUIA_Window_Title, &quot;Hello world!&quot;,&lt;/code&gt;

A window must have 1 and only 1 child, usually a group. This one is vertical, that means that its children will be arranged vertically:

:           &lt;code&gt;WindowContents, VGroup,&lt;/code&gt;

A group must have at least 1 child, here it's just a text:

:              &lt;code&gt; Child, TextObject,&lt;/code&gt;

Zune accepts various escape codes (here, to center the text) and newlines:

:                  &lt;code&gt; MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,&lt;/code&gt;

An End macro must match every xxxObject macro (here, TextObject):

:                   &lt;code&gt;End,&lt;/code&gt;

Let's add a second child to our group, a button! With a keyboard shortcut o indicated by an underscore:

:               &lt;code&gt;Child, but = SimpleButton(&quot;_Ok&quot;),&lt;/code&gt;

Finish the group:

:               &lt;code&gt;End,&lt;/code&gt;

Finish the window:

:           &lt;code&gt;End,&lt;/code&gt;

Finish the application:

:       &lt;code&gt;End;&lt;/code&gt;

So, who still needs a GUI builder? :-)

===Error handling===

If any of the object in the application tree can't be created, Zune destroys all the objects already created and application creation fails. If not, you have a fully working application:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
   if (app != NULL)
   {
       ...&lt;/syntaxhighlight&gt;

When you're done, just call MUI_DisposeObject() on your application object to destroy all the objects currently in the application, and free all the resources:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;       ...
       MUI_DisposeObject(app);
   }&lt;/syntaxhighlight&gt;


===Notifications===

Notifications are the simplest way to react on events. The principle? We want to be notified when a certain attribute of a certain object is set to a certain value:

:        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,

Here we'll listen to the MUIA_Window_CloseRequest of our Window object and be notified whenever this attribute is set to TRUE. So what happens when a notification is triggered? A message is sent to an object, here we tell our Application to return MUIV_Application_ReturnID_Quit on the next event loop iteration:

:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

As we can specify anything we want here, we have to tell the number of extra parameters we are supplying to MUIM_Notify: here, 2 parameters.

For the button, we listen to its MUIA_Pressed attribute: it's set to FALSE whenever the button is being released (reacting when it's pressed is bad practice, you may want to release the mouse outside of the button to cancel your action - plus we want to see how it looks when it's pressed). The action is the same as the previous, send a message to the application:

:        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

===Opening the window===
Windows aren't open until you ask them to:

:        set(wnd, MUIA_Window_Open, TRUE);

If all goes well, your window should be displayed at this point. But it can fail! So don't forget to check by querying the attribute, which should be TRUE:

:        if (XGET(wnd, MUIA_Window_Open))

===Main loop===
Let me introduce you my lil' friend, the ideal Zune event loop:

:        ULONG sigs = 0;

Don't forget to initialize the signals to 0 ... The test of the loop is the MUIM_Application_NewInput method:

:        ...
:        while((LONG) DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
:              != MUIV_Application_ReturnID_Quit)

It takes as input the signals of the events it has to process (result from Wait(), or 0), will modify this value to place the signals Zune is waiting for (for the next Wait()) and will return a value. This return value mechanism was historically the only way to react on events, but it was ugly and has been deprecated in favor of custom classes and object-oriented design.

The body of the loop is quite empty, we only wait for signals and handle Ctrl-C to break out of the loop:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
    {
    if (sigs)
        {
        sigs = Wait(sigs | SIGBREAKF_CTRL_C);
        if (sigs &amp; SIGBREAKF_CTRL_C)
             break;
        }
    }
&lt;/syntaxhighlight&gt;

===Conclusion===

This program gets you started with Zune, and allows you to toy with GUI design, but not more.

==Notification actions==

Notification allows you to respond to events your application/gui or any other object might cause.  Due to the attribute and method based nature of Zune, and a few special attributes, most applications can be almost completely automated through the use of Notification(s).

As seen in hello.c, you use MUIM_Notify to call a method if a certain condition happens. If you want your application to react in a specific way to events, you can use one of these schemes:

* Set An attribute.  You can automate the passing of values from gadgets,
::etc to other gadgets.  Setting values may also trigger other notification
::events.
      
* Invoke a method, for example:    
::'''MUIM_Application_ReturnID:''' you can ask your application to return an
:: arbitrary ID on the next loop iteration, and check for the value in
:: the loop. This is the dirty old way of doing things.
      
:: '''MUIM_CallHook,''' to call a standard Amiga callback hook: this is an
::average choice, not object-oriented but not that ugly either.
      
::'''custom method:''' the method belongs to one of your custom class. It 
::is the best solution as it supports object-oriented design in
::applications. It needs you to create custom classes so it may not 
::the easiest for beginners or people in a hurry.

==Zune Examples/Tutorials==

*some [https://arosarchives.os4depot.net/?function=showfile&amp;file=development/example/mui_examples.i386-aros.zip c src examples]
*Being an AmigaOS3.x MUI clone, all AmigaOS3.x MUI code serves as example code for using AROS Zune.
*MUI example sourcecode &quot;PSI.c&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*[http://archive.is/20121225201004/robertnegro.wordpress.com/2012/10/30/aros-zune-programming-tutorials-for-beginners/ Good examples of Zune Main Classes]
*AROS itself contains lots of Zune examples. Download AROS sources and AROS contrib sources archives, take a look at the sourcecode of Zune programs. A good starting point are the Zune test programs, maybe located in the SYS:Demos/Zune folder of AROS' binary distributions (e.g. the nightly build) - their sources can be found in the &quot;test/Zune&quot; folder of the AROS source archive.
*[[Aros/Developer/Zune/Examples|Zune example code collection]]

Some other good examples are here:

*[https://github.com/emartisoft/AmigaOS3.X-MUI-Examples Examples]
*[http://code.google.com/p/guidetoamigacompatibleprogramming/source/browse/#svn/trunk/english Shinkuro's] Cross-Platform Guide about compatible programming on Amiga-related platforms (Amiga, AROS, MorphOS) 


==Zune Reference==

*[http://aros.sourceforge.net/documentation/developers/zune-dev/index.php AROS Zune Development Manual] at [http://www.aros.org aros.org]
*[http://web.archive.org/web/20110526115419/http://www.sasg.com/mui/autodocs/index.html MUI Autodocs] online at [http://www.sasg.com sasg.com]
*MUI (=Zune) reference guide &quot;MUIDev.guide&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]


==Tools==

===MUIBuilder===

A [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool native build] and [http://sourceforge.net/projects/muibuilder/ sourceforge svn repository] has been started and [[Aros/Developer/ZuneFurther]] documentation can be read. v3 is W.I.P. so it is not recommended for now.

This [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=5578&amp;forum=1&amp;post_id=52900#forumpost52900 thread] discussed using the m68k build and [http://www.mazze-online.de/files/mbtest.zip diff] file which modifications were necessary to make it build-able under AROS.

Summary
* added &quot;#define MUI_OBSOLETE&quot; to get some deprecated but needed defines
* changed/added some #include
* changed variable name Object to obj because Object is a type
* changed the Hook for the callback function
* last not least: added main.c which calls the functions to open/close the GUI.

Just go ahead and create your GUIS under any version of AROS or under amiga 68k version and do some modifications (which would be necessary for MorphOS/AmigaOS3/AmigaOS4, too).

===ChocolateCastle===

The [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/guitool binary] which makes creating MUI classes and applications easier. Programmers using this system often avoid writing custom classes, being discouraged by a lot of boring and schematical typing. A significant part of a typical custom class may be generated automatically. This is usually 2 to 5 kB of source code. Automating this work speeds programming up and helps avoiding simple typing errors.

==Errors==
&lt;pre&gt;
Message  
Solution SetAttrs() is vararg version of SetAttrsA() and expects a complete taglist so you must add TAG_DONE and not TAG_END. 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols ... KeyString
Solution finally replaced KeyString(0,256,'f') by MUIA_CreateObject(MUIO_String,&quot;f&quot;,256)
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols... GetAttr
Solution you need:  #include &lt;proto/intuition.h&gt;
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution  #define MUI_OBSOLETE
&lt;/pre&gt;

{{BookCat}}

[[ru:Zune]]</text>
      <sha1>5v4pxj8dsydueptb352rmso3aws2svj</sha1>
    </revision>
    <revision>
      <id>4668981</id>
      <parentid>4668980</parentid>
      <timestamp>2026-09-05T18:13:20Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668981</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19537" sha1="cjxsfems7vcqme1zfzaiyknu8kgg437" xml:space="preserve">{{ArosNav}}

==Introduction==

&lt;pre&gt;
version muimaster.library is 19 for 3.8 
                          is 20 for 3.9
                          is    for 4.0  dynamic tabs simplification 
                          is    for 5.0  
&lt;/pre&gt;

Zune is an object-oriented GUI toolkit. It is nearly a clone (at both API and Look&amp;Feel level) of MUI, a well-known Amiga shareware product by Stefan Stuntz. Therefore, MUI developers will feel at home here, while others will discover the concepts and qualities that Zune shares with MUI.

The programmer has a much easier time to design its GUI: no need for hardcoded values, Zune is font-sensitive, and adapts to any window size due to its layout system. He/she mostly needs to only specify the semantic of its GUI to Zune, which will arrange the low-level details automatically.

Zune is based on the [https://library.morph.zone/Short_BOOPSI_Overview BOOPSI] system, the framework inherited from AmigaOS (TM) for object-oriented programming in C. Zune [[Aros/Developer/Zune/Classes|classes]] does not derive from existing BOOPSI gadget classes; instead, the Notify class (base class of the Zune hierarchy) derives from the BOOPSI root class.

* Many AROS GUI components (windows, requesters, gadgets, images) are now programmed in an object-oriented way, using the BOOPSI/Zune toolkit. 
* Every such component is created as an object, not as a pointer to a system structure. That means no more filling structures with data. 
* Objects are manipulated using methods and by passing tags via the SetAttrs() function.

Creating Prefs from scratch with using our Zune Prefs classes.

A good introduction to the BOOPSI system is the [http://amigadev.elowar.com/read/ADCD_2.1/Libraries_Manual_guide/node01FF.html Chapter 12, &quot;BOOPSI - Object-oriented Intuition&quot;]. Here BOOPSI NewObject() has been replaced by MUI_NewObject(), DisposeObject() becomes MUI_DisposeObject(), etc.

==Prerequisites==

Some knowledge of [http://wiki.answers.com/Q/What_are_the_concepts_of_object_oriented_programming OOP] {{w|object-oriented programming}} is more than welcome.

Knowing AROS APIs and concepts like [[Aros/Developer/Docs/Libraries/Intuition|taglists]] and BOOPSI is essential. As Zune is a MUI clone, all the documentation pertaining to MUI is applicable to Zune. In particular, the latest available MUI developer kit and MUI autodocs can be found at [http://main.aminet.net/dev/mui/mui38dev.lha here]. In this LHA archive, 2 documents are warmly recommended:

 '''MUIdev.guide''', the MUI programmer documentation 
 and
 '''PSI.c''' source code, demonstrating Zune practices like OOP and dynamic object creation

==Zune basics and conventions==

MUI (= Zune) sticks a prefix on the start to signify what is being access/changed:

* MUIA_ attribute 
* MUIM_ method 
* MUIV_ special values

==BOOPSI Primer/Concepts==

===Class===
A class is defined by its name, its parent class and a dispatcher.

'''name''': either a string for the public classes, so that they may be used by any program in the system, or none if its a private class used only by a single application.

'''parent class''': all BOOPSI classes are forming a hierarchy rooted at the class aptly named rootclass. It allows each subclass to implement its own version of specific parent operation, or to fall back on the one provided by its parent. Also known as base class or super class.

'''dispatcher''': it gives access to all operations (called methods) provided by this class, ensuring that each operation is handled by the proper code or passed to its super class.

BOOPSI type for a class is Class * also known as IClass.

===Object===
An object is an instance of class: each object has its specific data, but all objects of the same class share the same behavior. An object has several classes if we count the parents of its true class (the most derived one) up to the rootclass.

BOOPSI type for an object is Object *. It has no field you can directly access.

When a Zune object is created and destroyed several methods are called:
&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;
If the documentation says that something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

===Attribute===
An attribute is related to the instance data of each object: you can not access these data directly, you can only set or get the attributes provided by an object to modify its internal state. An attribute is implemented as a Tag (ULONG value or'ed with TAG_USER).

GetAttr() and SetAttrs() are used to modify an object's attributes.

Attributes can be one or more of the following:

Initialization-settable (I) : the attribute can be given as parameter at the object creation.

Settable (S) : You can set this attribute at any time (or at least, not only creation).

Gettable (G) : You can get the value of this attribute.

===Method===
A BOOPSI method is a function which receives as parameters an object, a class and a message:

object: the object you act on

class: the considered class for this object.

message: contains a method ID which determines the function to call within a dispatcher, and is followed by its parameters.

To send a message to an object, use DoMethod(). It will use the true class first. If the class implements this method, it will handle it. Else it will try its parent class, until the message is handled or the rootclass is reached (in this case, the unknown message is silently discarded).

Summary, before a method can act on an object, it needs a BOOPSI message 
&lt;pre&gt;
    Function                     BOOPSI Method

    NewObject()                  OM_NEW
    DisposeObject()              OM_DISPOSE
    SetAttrs()/SetGadgetAttrs()  OM_SET
    GetAttr()                    OM_GET
&lt;/pre&gt;

==BOOPSI Examples==
Let's see basic examples of this OOP framework:

Getting an attribute
We'll query a MUI String object for its content:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
void f(Object *string)
{
    IPTR result;
    
    GetAttr(string, MUIA_String_Contents, &amp;result);
    printf(&quot;String content is: %s\n&quot;, (STRPTR)result);
}
&lt;/syntaxhighlight&gt;

Object * is the type of BOOPSI objects. 
IPTR must be used for the type of the result, which can be an integer or a pointer. An IPTR is always written in memory, so using a smaller type would lead to memory corruption! 
Here we query a MUI String object for its content: MUIA_String_Contents, as any other attribute, is a ULONG (it's a Tag) 
Zune applications use more often the get() and XGET() macros instead:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
get(string, MUIA_String_Contents, &amp;result);

result = XGET(string, MUIA_String_Contents);
&lt;/syntaxhighlight&gt;
Setting an attribute
Let's change the content of our string:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;, TAG_DONE);
&lt;/syntaxhighlight&gt;
Pointers parameters must be casted to IPTR to avoid warnings. 
After the object parameter, a taglist is passed to SetAttrs and thus must end with TAG_DONE. 
You'll find the set() macro useful:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
set(string, MUIA_String_Contents, (IPTR)&quot;hello&quot;);
&lt;/syntaxhighlight&gt;
But it's only with SetAttrs() that you can set several attributes at once:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
SetAttrs(string,
         MUIA_Disabled, TRUE,
         MUIA_String_Contents, (IPTR)&quot;hmmm...&quot;,
         TAG_DONE);
&lt;/syntaxhighlight&gt;
Calling a method
Let's see the most called method in a Zune program, the event processing method called in your main loop:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
result = DoMethod(obj, MUIM_Application_NewInput, (IPTR)&amp;sigs);
&lt;/syntaxhighlight&gt;
Parameters are not a taglist, and thus don't end with TAG_DONE. 
You have to cast pointers to IPTR to avoid warnings.

==&quot;Hello world&quot; example sourcecode==

[http://www.aros.org/documentation/developers/zune/images/hello.png Screenshot 'Hello World']

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
// gcc hello.c -lmui
#include &lt;exec/types.h&gt;
#include &lt;libraries/mui.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

int main(void)
{
    Object *wnd, *app, *but;

    // GUI creation
    app = ApplicationObject,
        SubWindow, wnd = WindowObject,
            MUIA_Window_Title, &quot;Hello world!&quot;,
            WindowContents, VGroup,
                Child, TextObject,
                    MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,
                    End,
                Child, but = SimpleButton(&quot;_Ok&quot;),
                End,
            End,
        End;

    if (app != NULL)
    {
        ULONG sigs = 0;

        // Click Close gadget or hit Escape to quit
        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Click the button to quit
        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
                 (IPTR)app, 2,
                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

        // Open the window
        set(wnd, MUIA_Window_Open, TRUE);

        // Check that the window opened
        if (XGET(wnd, MUIA_Window_Open))
        {
            // Main loop
            while((LONG)DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
                  != MUIV_Application_ReturnID_Quit)
            {
                if (sigs)
                {
                    sigs = Wait(sigs | SIGBREAKF_CTRL_C);
                    if (sigs &amp; SIGBREAKF_CTRL_C)
                        break;
                }
            }
        }
        // Destroy our application and all its objects
        MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

===Remarks/General===
We don't manually open libraries, it's done automatically for us.

===GUI creation===
We use a macro-based language to easily build our GUI. A Zune application has always 1 and only 1 Application object:

:   &lt;code&gt;app = ApplicationObject,&lt;/code&gt;

An application can have 0, 1 or more Window objects. Most often a single one:

:       &lt;code&gt;SubWindow, wnd = WindowObject,&lt;/code&gt;

Be nice, give a title to the window:

:           &lt;code&gt;MUIA_Window_Title, &quot;Hello world!&quot;,&lt;/code&gt;

A window must have 1 and only 1 child, usually a group. This one is vertical, that means that its children will be arranged vertically:

:           &lt;code&gt;WindowContents, VGroup,&lt;/code&gt;

A group must have at least 1 child, here it's just a text:

:              &lt;code&gt; Child, TextObject,&lt;/code&gt;

Zune accepts various escape codes (here, to center the text) and newlines:

:                  &lt;code&gt; MUIA_Text_Contents, &quot;\33cHello world!\nHow are you?&quot;,&lt;/code&gt;

An End macro must match every xxxObject macro (here, TextObject):

:                   &lt;code&gt;End,&lt;/code&gt;

Let's add a second child to our group, a button! With a keyboard shortcut o indicated by an underscore:

:               &lt;code&gt;Child, but = SimpleButton(&quot;_Ok&quot;),&lt;/code&gt;

Finish the group:

:               &lt;code&gt;End,&lt;/code&gt;

Finish the window:

:           &lt;code&gt;End,&lt;/code&gt;

Finish the application:

:       &lt;code&gt;End;&lt;/code&gt;

So, who still needs a GUI builder? :-)

===Error handling===

If any of the object in the application tree can't be created, Zune destroys all the objects already created and application creation fails. If not, you have a fully working application:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
   if (app != NULL)
   {
       ...&lt;/syntaxhighlight&gt;

When you're done, just call MUI_DisposeObject() on your application object to destroy all the objects currently in the application, and free all the resources:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;       ...
       MUI_DisposeObject(app);
   }&lt;/syntaxhighlight&gt;


===Notifications===

Notifications are the simplest way to react on events. The principle? We want to be notified when a certain attribute of a certain object is set to a certain value:

:        DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,

Here we'll listen to the MUIA_Window_CloseRequest of our Window object and be notified whenever this attribute is set to TRUE. So what happens when a notification is triggered? A message is sent to an object, here we tell our Application to return MUIV_Application_ReturnID_Quit on the next event loop iteration:

:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

As we can specify anything we want here, we have to tell the number of extra parameters we are supplying to MUIM_Notify: here, 2 parameters.

For the button, we listen to its MUIA_Pressed attribute: it's set to FALSE whenever the button is being released (reacting when it's pressed is bad practice, you may want to release the mouse outside of the button to cancel your action - plus we want to see how it looks when it's pressed). The action is the same as the previous, send a message to the application:

:        DoMethod(but, MUIM_Notify, MUIA_Pressed, FALSE,
:                 (IPTR)app, 2,
:                 MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

===Opening the window===
Windows aren't open until you ask them to:

:        set(wnd, MUIA_Window_Open, TRUE);

If all goes well, your window should be displayed at this point. But it can fail! So don't forget to check by querying the attribute, which should be TRUE:

:        if (XGET(wnd, MUIA_Window_Open))

===Main loop===
Let me introduce you my lil' friend, the ideal Zune event loop:

:        ULONG sigs = 0;

Don't forget to initialize the signals to 0 ... The test of the loop is the MUIM_Application_NewInput method:

:        ...
:        while((LONG) DoMethod(app, MUIM_Application_NewInput, (IPTR)&amp;sigs)
:              != MUIV_Application_ReturnID_Quit)

It takes as input the signals of the events it has to process (result from Wait(), or 0), will modify this value to place the signals Zune is waiting for (for the next Wait()) and will return a value. This return value mechanism was historically the only way to react on events, but it was ugly and has been deprecated in favor of custom classes and object-oriented design.

The body of the loop is quite empty, we only wait for signals and handle Ctrl-C to break out of the loop:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
    {
    if (sigs)
        {
        sigs = Wait(sigs | SIGBREAKF_CTRL_C);
        if (sigs &amp; SIGBREAKF_CTRL_C)
             break;
        }
    }
&lt;/syntaxhighlight&gt;

===Conclusion===

This program gets you started with Zune, and allows you to toy with GUI design, but not more.

==Notification actions==

Notification allows you to respond to events your application/gui or any other object might cause.  Due to the attribute and method based nature of Zune, and a few special attributes, most applications can be almost completely automated through the use of Notification(s).

As seen in hello.c, you use MUIM_Notify to call a method if a certain condition happens. If you want your application to react in a specific way to events, you can use one of these schemes:

* Set An attribute.  You can automate the passing of values from gadgets,
::etc to other gadgets.  Setting values may also trigger other notification
::events.
      
* Invoke a method, for example:    
::'''MUIM_Application_ReturnID:''' you can ask your application to return an
:: arbitrary ID on the next loop iteration, and check for the value in
:: the loop. This is the dirty old way of doing things.
      
:: '''MUIM_CallHook,''' to call a standard Amiga callback hook: this is an
::average choice, not object-oriented but not that ugly either.
      
::'''custom method:''' the method belongs to one of your custom class. It 
::is the best solution as it supports object-oriented design in
::applications. It needs you to create custom classes so it may not 
::the easiest for beginners or people in a hurry.

==Zune Examples/Tutorials==

*some [https://arosarchives.os4depot.net/?function=showfile&amp;file=development/example/mui_examples.i386-aros.zip c src examples]
*Being an AmigaOS3.x MUI clone, all AmigaOS3.x MUI code serves as example code for using AROS Zune.
*MUI example sourcecode &quot;PSI.c&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]
*[http://archive.is/20121225201004/robertnegro.wordpress.com/2012/10/30/aros-zune-programming-tutorials-for-beginners/ Good examples of Zune Main Classes]
*AROS itself contains lots of Zune examples. Download AROS sources and AROS contrib sources archives, take a look at the sourcecode of Zune programs. A good starting point are the Zune test programs, maybe located in the SYS:Demos/Zune folder of AROS' binary distributions (e.g. the nightly build) - their sources can be found in the &quot;test/Zune&quot; folder of the AROS source archive.
*[[Aros/Developer/Zune/Examples|Zune example code collection]]

Some other good examples are here:

*[https://github.com/emartisoft/AmigaOS3.X-MUI-Examples Examples]
*[http://code.google.com/p/guidetoamigacompatibleprogramming/source/browse/#svn/trunk/english Shinkuro's] Cross-Platform Guide about compatible programming on Amiga-related platforms (Amiga, AROS, MorphOS) 


==Zune Reference==

*[http://aros.sourceforge.net/documentation/developers/zune-dev/index.php AROS Zune Development Manual] at [http://www.aros.org aros.org]
*[http://web.archive.org/web/20110526115419/http://www.sasg.com/mui/autodocs/index.html MUI Autodocs] online at [http://www.sasg.com sasg.com]
*MUI (=Zune) reference guide &quot;MUIDev.guide&quot;, found in [http://ftp.sunet.se/pub/aminet/dev/mui/mui38dev.lha MUI3.8 developer archive]


==Tools==

===MUIBuilder===

[https://arosarchives.os4depot.net/index.php?function=browse&amp;cat=development/guitool Mui Builder] and [http://sourceforge.net/projects/muibuilder/ sourceforge svn repository] has been started and [[Aros/Developer/ZuneFurther]] documentation can be read. v3 is W.I.P. so it is not recommended for now.


Summary
* added &quot;#define MUI_OBSOLETE&quot; to get some deprecated but needed defines
* changed/added some #include
* changed variable name Object to obj because Object is a type
* changed the Hook for the callback function
* last not least: added main.c which calls the functions to open/close the GUI.

Just go ahead and create your GUIS under any version of AROS or under amiga 68k version and do some modifications (which would be necessary for MorphOS/AmigaOS3/AmigaOS4, too).

===ChocolateCastle===

The [https://arosarchives.os4depot.net/index.php?function=browse&amp;cat=development/guitool binary] which makes creating MUI classes and applications easier. Programmers using this system often avoid writing custom classes, being discouraged by a lot of boring and schematical typing. A significant part of a typical custom class may be generated automatically. This is usually 2 to 5 kB of source code. Automating this work speeds programming up and helps avoiding simple typing errors.

==Errors==
&lt;pre&gt;
Message  
Solution SetAttrs() is vararg version of SetAttrsA() and expects a complete taglist so you must add TAG_DONE and not TAG_END. 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols ... KeyString
Solution finally replaced KeyString(0,256,'f') by MUIA_CreateObject(MUIO_String,&quot;f&quot;,256)
&lt;/pre&gt;
&lt;pre&gt;
Message  undefined symbols... GetAttr
Solution you need:  #include &lt;proto/intuition.h&gt;
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution 
&lt;/pre&gt;
&lt;pre&gt;
Message  
Solution  #define MUI_OBSOLETE
&lt;/pre&gt;

{{BookCat}}

[[ru:Zune]]</text>
      <sha1>cjxsfems7vcqme1zfzaiyknu8kgg437</sha1>
    </revision>
  </page>
  <page>
    <title>User:MikeAssad~enwikibooks</title>
    <ns>2</ns>
    <id>22682</id>
    <revision>
      <id>4668927</id>
      <parentid>2872605</parentid>
      <timestamp>2026-09-05T12:31:14Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668927</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1141" sha1="6rix8rz18z9h1hmcvcenbx53bvxkdkd" xml:space="preserve">[http://en.wikipedia.org/wiki/User:MikeAssad My user page on Wikipedia]

{| cellspacing=&quot;1&quot; cellpadding=&quot;1&quot; style=&quot;background: #f7fff8;{{Text default color}}; border: 1px solid #88a; padding: 5px; font-size: 80%;&quot;
|- style=&quot;text-align: left;&quot;
| style=&quot;width: 88px; padding-left: 6px;&quot; | [[Image:Wikimedia.png|65px]]
|
{|
| style=&quot;background: #43a976;{{Text default color}}; text-align: center;&quot; |'''Licensing rights granted to Wikimedia Foundation'''
|- style=&quot;text-align: left;&quot;
| I grant non-exclusive permission for the [[Wikimedia|Wikimedia Foundation Inc.]] to relicense my text and media contributions, including any images, audio clips, or video clips, under any [[copyleft]] license that it chooses, provided it maintains the free and open spirit of the [[GFDL]].  This permission acknowledges that future licensing needs of the Wikimedia projects may need adapting in unforseen fashions to facilitate other uses, formats, and locations.  It is given for as long as this banner remains. '''Note: This banner is under construction, and is subject to major changes pending [[Template talk:WikimediaMediaLicensing|discussions]]'''
|}
|}</text>
      <sha1>6rix8rz18z9h1hmcvcenbx53bvxkdkd</sha1>
    </revision>
  </page>
  <page>
    <title>User:Snarius~enwikibooks</title>
    <ns>2</ns>
    <id>26811</id>
    <revision>
      <id>4668994</id>
      <parentid>2886505</parentid>
      <timestamp>2026-09-05T19:05:44Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668994</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1071" sha1="qecnr911bxpg9dn0cb148bptqx39gnz" xml:space="preserve">{{wikipediapar||User:Snargle}}

&lt;span style=&quot;border:1px solid black; background-color:#ddd;{{Text default color}}; padding-right:1em&quot;&gt; &lt;span style=&quot;-display:none&quot;&gt;&amp;dArr;&lt;/span&gt;&lt;span style=&quot;display:none; -display:inline&quot;&gt;V&lt;/span&gt; read the red box &lt;span style=&quot;-display:none&quot;&gt;&amp;dArr;&lt;/span&gt;&lt;span style=&quot;display:none; -display:inline&quot;&gt;V&lt;/span&gt;&lt;/span&gt;
{{userbox|#449944|#558855|blep|Formerly [[User:Snarius]]}}


I've helped out with a few books, namely:
*[[Super NES Programming]]--I'm the main contributor, check it out.
*[[Down'n'dirty Blacksmithing]], total splitting, gave it some pics.
*[[Knowing Knoppix]], total splitting again, some cleanup
*[[Digital Photography]], Split what needs to be splat
*[[The Way of the Program]], split it into smaller. barrel-sized pieces.  Cleaned it up a bit, too.
*[[Template:ArosNav]] made navbar (still dont want to know whar AROS is)
*[[The Legend of Zelda: The Wind Waker]] split, added template (update:it's deleted as a copyvio)
*[[Linux Guide]]--kinda split it
*[[N64 Programming]]--uploaded/wikified

And:
{{MultiLicensePD}}</text>
      <sha1>qecnr911bxpg9dn0cb148bptqx39gnz</sha1>
    </revision>
  </page>
  <page>
    <title>User:Yanka ronin</title>
    <ns>2</ns>
    <id>33909</id>
    <revision>
      <id>4668917</id>
      <parentid>992367</parentid>
      <timestamp>2026-09-05T12:06:43Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668917</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="881" sha1="isb0wq93uv0i7s92q1gpdl623ot5dg4" xml:space="preserve">{{{1|Welcome, {{PAGENAME}}!}}}
{| style=&quot;background:white;{{text default color}}border:1px solid #abd5f5;; padding:0px; border-spacing:0px;&quot;
 ! style=&quot;background:#d0e5f5;{{text default color}}&quot; | [[Wikibooks:Welcome, newcomers|Getting started]] with Wikibooks
 |-
 | style=&quot;padding:5px;&quot; |
* Wikibooks is a collection of open-source textbooks. Find out [[WB:WIW|what this means]].
* To sign your name (on talk pages), use four tildes, like this: &amp;#126;&amp;#126;&amp;#126;&amp;#126; 
* For help in using the wiki, see the [[Help:Editing|editing guide]].
* Explore, [[Wikibooks:Be bold|be bold]], and have fun!
 |}

Come introduce yourself at the [[WB:SLN|new users]] page.  If you have any questions, you can ask there or contact me personally. ''(''&lt;sub&gt;Donovan&lt;/sub&gt;|[[User:Geocachernemesis|Geocachernemesis]]|&lt;sup&gt;[[User_talk:Geocachernemesis|Interact]]&lt;/sup&gt;'')'' 01:46, 16 July 2005 (UTC)</text>
      <sha1>isb0wq93uv0i7s92q1gpdl623ot5dg4</sha1>
    </revision>
  </page>
  <page>
    <title>User:Mats.kirknes~enwikibooks</title>
    <ns>2</ns>
    <id>34202</id>
    <revision>
      <id>4669003</id>
      <parentid>2871435</parentid>
      <timestamp>2026-09-05T19:20:31Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669003</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="884" sha1="6o7xq01hoqavjkxq3fkteu2tfrohzb9" xml:space="preserve">{{{1|Welcome, {{PAGENAME}}!}}}
{| style=&quot;background:white;{{text default color}}; border:1px solid #abd5f5;; padding:0px; border-spacing:0px;&quot;
 ! style=&quot;background:#d0e5f5;{{text default color}};&quot; | [[Wikibooks:Welcome, newcomers|Getting started]] with Wikibooks
 |-
 | style=&quot;padding:5px;&quot; |
* Wikibooks is a collection of open-source textbooks. Find out [[WB:WIW|what this means]].
* To sign your name (on talk pages), use four tildes, like this: &amp;#126;&amp;#126;&amp;#126;&amp;#126; 
* For help in using the wiki, see the [[Help:Editing|editing guide]].
* Explore, [[Wikibooks:Be bold|be bold]], and have fun!
 |}

Come introduce yourself at the [[WB:SLN|new users]] page.  If you have any questions, you can ask there or contact me personally. ''(''&lt;sub&gt;Donovan&lt;/sub&gt;|[[User:Geocachernemesis|Geocachernemesis]]|&lt;sup&gt;[[User_talk:Geocachernemesis|Interact]]&lt;/sup&gt;'')'' 11:57, 19 July 2005 (UTC)</text>
      <sha1>6o7xq01hoqavjkxq3fkteu2tfrohzb9</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Magbatz~enwikibooks</title>
    <ns>3</ns>
    <id>35169</id>
    <revision>
      <id>4669051</id>
      <parentid>2923041</parentid>
      <timestamp>2026-09-06T06:35:41Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669051</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3087" sha1="2xfdcmsbbrutloqdn0iv96q75q9jnxr" xml:space="preserve">{{{1|Welcome, {{PAGENAME}}!}}}
{| style=&quot;background:white;{{text default color}}; border:1px solid #abd5f5;; padding:0px; border-spacing:0px;&quot;
 ! style=&quot;background:#d0e5f5;{{text default color}};&quot; | [[Wikibooks:Welcome, newcomers|Getting started]] with Wikibooks
 |-
 | style=&quot;padding:5px;&quot; |
* Wikibooks is a collection of open-source textbooks. Find out [[WB:WIW|what this means]].
* To sign your name (on talk pages), use four tildes, like this: &amp;#126;&amp;#126;&amp;#126;&amp;#126; 
* For help in using the wiki, see the [[Help:Editing|editing guide]].
* Explore, [[Wikibooks:Be bold|be bold]], and have fun!
 |}

Come introduce yourself at the [[WB:SLN|new users]] page.  If you have any questions, you can ask there or contact me personally.

Thanks for helping to fight vandalism on Wikibooks. We need more people like you, your contribution is greatly appreciated.:) ''(''&lt;sub&gt;Donovan&lt;/sub&gt;|[[User:Geocachernemesis|Geocachernemesis]]|&lt;sup&gt;[[User_talk:Geocachernemesis|Interact]]&lt;/sup&gt;'')'' 02:57, 29 July 2005 (UTC)

== Your account will be renamed ==

&lt;div class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See [[m:Special:MyLanguage/Single User Login finalisation announcement|the announcement]] for more information.

Unfortunately, your account clashes with another account also called Magbatz. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Magbatz~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can [[Special:GlobalRenameRequest|pick out a different name]].

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours,&lt;br /&gt;[[m:User:Keegan (WMF)|Keegan Peterzell]]&lt;br /&gt;Community Liaison, Wikimedia Foundation
&lt;/div&gt; 23:24, 17 March 2015 (UTC)
&lt;!-- SUL finalisation notification --&gt;

== Renamed ==

&lt;div class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;
This account has been renamed as part of [[m:Special:MyLanguage/Single User Login finalisation announcement|single-user login finalisation]]. If you own this account you can [[{{#special:userlogin}}|log in using your previous username and password]] for more information. If you do not like this account's new name, you can choose your own using this form after logging in: [[{{#special:GlobalRenameRequest}}]]. -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User talk:Keegan (WMF)|talk]])
&lt;/div&gt; 05:13, 19 April 2015 (UTC)
&lt;!-- SUL post-rename notification --&gt;</text>
      <sha1>2xfdcmsbbrutloqdn0iv96q75q9jnxr</sha1>
    </revision>
  </page>
  <page>
    <title>User:Xerol</title>
    <ns>2</ns>
    <id>45931</id>
    <revision>
      <id>4668988</id>
      <parentid>1891592</parentid>
      <timestamp>2026-09-05T19:00:24Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668988</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1260" sha1="q1j83iwg38l7td3gmks6ll2ppef5f21" xml:space="preserve">==Notices and other stuff==
&lt;div style=&quot;margin: 10px; background-color: #EEFFEE;{{Text default color}}; border: 1px solid #807070; padding: 5px;&quot;&gt;Somewhat active again, see Projects below for where I'll be working.&lt;/div&gt;

==Useful Links==
Mostly for my use, but also because some of these are hard to find:
*[[Wikibooks:Vandalism in progress]]
*[[Wikibooks:Deletion_policy]]

==Contact Me==
*AIM: XerolOplan
*ICQ: 125672905
*MSN: xeroloplan@hotmail.com
*Yahoo: xerol3
*My [[w:User:Xerol|Wikipedia userpage]]. Even when I'm inactive I still read wikipedia so if you post on my talk page, I'll get the notice.
I'm also on the Wikibooks IRC channel most of the time.
==Projects==
*[[User:Xerol/TemplateSandbox|Template Sandbox]]
===Diagrams and Illustrations===
I'll be making nice vector diagrams whereever helpful, probably putting them up on [[commons:User:Xerol|commons]].
===My Cleanup Tasks===
See [[User:Xerol/Cleanup]].
===Templates===
====General Template Cleanup====
*{{Tlx|AttentionTemplate}}
*{{Tlx|AttentionTemplateDoc}}
====SoftwareVersion templates and Manual of Style====
Working on templates for use in the SoftwareVersions project.

==Miscellaneous==
Feel free to comment in each section; feedback is always appreciated, especially if I'm wrong.</text>
      <sha1>q1j83iwg38l7td3gmks6ll2ppef5f21</sha1>
    </revision>
  </page>
  <page>
    <title>User:Kalden~enwikibooks</title>
    <ns>2</ns>
    <id>62807</id>
    <revision>
      <id>4669000</id>
      <parentid>2865823</parentid>
      <timestamp>2026-09-05T19:16:13Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669000</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="896" sha1="hwbe917rmmkd05ujpsvyjmvrb0ayka4" xml:space="preserve">&lt;div class=&quot;plainlinks&quot; style=&quot;font-size:90%; background-color:#FFFFFF;{{text default color}}; text-align:center; border-bottom: 2px solid #D8DAE7; border-top: 2px solid #D8DAE7;&quot;&gt;
[http://fr.wikipedia.org/wiki/Utilisateur:Kalden fr.wikipédia.org] - [http://fr.wikibooks.org/wiki/Utilisateur:Kalden fr.wikibooks.org] - [http://en.wikibooks.org/wiki/Utilisateur:Kalden en.wikibooks.org] - [http://oss.wikicities.com/wiki/User:Kalden wikicities.org] - [http://timebreach.free.fr/userinfo.php?uid=1 timebreach.sourceforge.net]
&lt;/div&gt;
&lt;br clear=&quot;all&quot; /&gt;

== Presentation ==
I'm student in computer science at [[w:École supérieure d'informatique|École supérieure d'informatique]], 
after i was in [[w:iut de montpellier|iut de montpellier]].

I like [[w:linux|linux]].
I use[[w:gentoo|gentoo]] and [[w:suse|suse]].

I've create [[Time Breach]]. 


If you have some discussion use my page. thanks.</text>
      <sha1>hwbe917rmmkd05ujpsvyjmvrb0ayka4</sha1>
    </revision>
  </page>
  <page>
    <title>User:Karl Wick/Test/Test 2</title>
    <ns>2</ns>
    <id>66072</id>
    <revision>
      <id>4669007</id>
      <parentid>402086</parentid>
      <timestamp>2026-09-05T19:22:40Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669007</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="605" sha1="qldcwqrehzjqrh3d1dbgucm41ewbcu1" xml:space="preserve">&lt;div class=&quot;noprint&quot; style=&quot;border:1px solid gold; background:cornsilk;{{text default color}}; padding: 4px; text-align: center; float: right;&quot;&gt;&lt;small&gt;
''On WP:'' &lt;br&gt; [[w:Octet rule|Octet rule]]
&lt;/small&gt;&lt;/div&gt;

If the article can be illustrated with pictures, find an appropriate place to position these images and get them from  [[w:Wikimedia Commons|Wikimedia Commons]]. For more information, see [[Wikipedia:Picture tutorial]] and [[Wikipedia:Images]]


left float, with caption:
&lt;div class=&quot;floatleft&quot;&gt;[[Image:NAME|Alt text]]&lt;br&gt;Caption&lt;/div&gt;


&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
[[Wikipedia:Extended image syntax]]</text>
      <sha1>qldcwqrehzjqrh3d1dbgucm41ewbcu1</sha1>
    </revision>
  </page>
  <page>
    <title>User:Rotemliss</title>
    <ns>2</ns>
    <id>90227</id>
    <revision>
      <id>4668924</id>
      <parentid>1554927</parentid>
      <timestamp>2026-09-05T12:23:39Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4668924</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2118" sha1="d09zz4ss46bgkt2tthf0cmmfzliu5kt" xml:space="preserve">{{userboxtop}} 
{{user language|he|N}} 
{{user language|en|3}}
 {{user language|ar|1}} 
{{userboxbottom}}
[[Image:Wikistress3D 1 v3.jpg|left|150px]]
I signed up to Wikibooks on 19 August 2006.

{{Userpage}}

== User map in Wikimedia Foundation ==
{| class=&quot;toccolours&quot; style=&quot;clear: both; direction: ltr; text-align: center; width: 100%;&quot;
|-
! Multilingual
| colspan=&quot;6&quot; |
{| style=&quot;background-color: transparent; color:inherit; width: 100%;&quot;
| [[Image:Commons-logo.svg|30px|Commons]]
[[commons:User:Rotemliss|Commons]]
| [[Image:Wikimedia Community Logo.svg|30px|Meta]]
[[m:User:Rotemliss|Meta]]
| [[Image:Mediawiki-logo.png|30px|MediaWiki]]
[[mw:User:Rotemliss|MediaWiki]]
| [[Image:Wikispecies-logo.svg|30px|Wikispecies]]
[[wikispecies:User:Rotemliss|Wikispecies]]
|}
|-
! English (en)
| [[Image:Wikipedia-logo-en.png|30px|Wikipedia]]
[[w:en:User:Rotemliss|Wikipedia]]
| [[Image:Wiktionary-logo-en.png|30px|Wiktionary]]
[[wikt:en:User:Rotemliss|Wiktionary]]
| [[Image:Wikiquote-logo-en.png|30px|Wikiquote]]
[[q:en:User:Rotemliss|Wikiquote]]
| [[Image:Wikibooks-logo-en.png|30px|Wikibooks]]
'''Wikibooks'''
|
|
|-
! Français (fr)
| [[Image:Wikipedia-logo-fr.png|30px|Wikipédia]]
[[w:fr:Utilisateur:Rotemliss|Wikipédia]]
|
|
|
|
|
|-
! עברית (he)
| [[Image:Wikipedia-logo-he.png|30px|ויקיפדיה]]
[[w:he:משתמש:Rotemliss|ויקיפדיה]] (sysop)
| [[Image:Wiktionary-logo-he.png|30px|ויקימילון]]
[[wikt:he:משתמש:Rotemliss|ויקימילון]]
| [[Image:Wikiquote-logo-he.png|30px|ויקיציטוט]]
[[q:he:משתמש:Rotemliss|ויקיציטוט]] (sysop)
| [[Image:Wikibooks-logo-he.png|30px|ויקיספר]]
[[:he:משתמש:Rotemliss|ויקיספר]] (sysop, bureaucrat)
| [[Image:Wikisource-logo-he.png|30px|ויקיטקסט]]
[[s:he:משתמש:Rotemliss|ויקיטקסט]] (sysop)
| [[Image:Wikinews-logo-he.png|30px|ויקיחדשות]]
[[n:he:משתמש:Rotemliss|ויקיחדשות]] (sysop)
|-
! ייִדיש (yi)
| [[Image:Wikipedia-logo-yi.png|30px|װיקיפּעדיע]]
[[w:yi:באַניצער:Rotemliss|װיקיפּעדיע]]
|
|
|
|
|
|}

[[he:משתמש:Rotemliss]]</text>
      <sha1>d09zz4ss46bgkt2tthf0cmmfzliu5kt</sha1>
    </revision>
  </page>
  <page>
    <title>User:Amrykid</title>
    <ns>2</ns>
    <id>96088</id>
    <revision>
      <id>4669001</id>
      <parentid>605496</parentid>
      <timestamp>2026-09-05T19:16:41Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669001</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="572" sha1="ld7yaobv81zm3w0eufmby0fmzaepi9z" xml:space="preserve">==Userboxes==

&lt;div style=&quot;float: left; border:solid red 1px; margin: 1px;&quot;&gt;
{| cellspacing=&quot;0&quot; style=&quot;width: 238px; background: blue;{{text default color}};&quot;
| style=&quot;width: 45px; height: 45px; background: red;{{text default color}};text-align: center; font-size: 14pt;&quot; | '''[[User:Amrykid|Amrykid]]'''
| style=&quot;font-size: 8pt; padding: 4pt; line-height: 1.25em;&quot; | this user has a account on wikipedia
|}
&lt;/div&gt;


==Links==

*[http://www.Wikipedia.org/wiki/User:Amrykid Wikipedia Account]
*[http://en.Wikiversity.org/wiki/User:Amrykid Wikiversity Account]

==Books==</text>
      <sha1>ld7yaobv81zm3w0eufmby0fmzaepi9z</sha1>
    </revision>
    <revision>
      <id>4669002</id>
      <parentid>4669001</parentid>
      <timestamp>2026-09-05T19:20:01Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4669002</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="561" sha1="sktyro84t6uhbkszksfgw9tgvsqfshx" xml:space="preserve">==Userboxes==

&lt;div style=&quot;float: left; border:solid red 1px; margin: 1px;&quot;&gt;
{| cellspacing=&quot;0&quot; style=&quot;width: 238px; background: blue;color:white;&quot;
| style=&quot;width: 45px; height: 45px; background: red;{{text default color}};text-align: center; font-size: 14pt;&quot; | '''[[User:Amrykid|Amrykid]]'''
| style=&quot;font-size: 8pt; padding: 4pt; line-height: 1.25em;&quot; | this user has a account on wikipedia
|}
&lt;/div&gt;


==Links==

*[http://www.Wikipedia.org/wiki/User:Amrykid Wikipedia Account]
*[http://en.Wikiversity.org/wiki/User:Amrykid Wikiversity Account]

==Books==</text>
      <sha1>sktyro84t6uhbkszksfgw9tgvsqfshx</sha1>
    </revision>
  </page>
  <page>
    <title>User:SBJohnny/Unused Redirect</title>
    <ns>2</ns>
    <id>97098</id>
    <revision>
      <id>4669016</id>
      <parentid>1662856</parentid>
      <timestamp>2026-09-05T19:31:22Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669016</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1532" sha1="083uebx3mw1wg6oq7brrtdclzbderke" xml:space="preserve">{| style=&quot;width:80%;border:solid #999 1px;background:#F8F8F8;{{Text default color}};margin:0.5em auto;clear:all&quot;
 | style=&quot;width: 52px; text-align: center;&quot; | [[Image:Warning_icon.png|Warning]]
 | style=&quot;vertical-align: middle;&quot; | This redirect '''will''' be deleted very soon. Please begin updating your bookmarks and webpages.&lt;br/&gt;The new location of this book or module is [[{{{1}}}]]
 |}
&lt;!-- time dependent inclusion of page into candidates for speedy deletion, until then categorize it in Unused Redirects --&gt;
&lt;includeonly&gt;
{{#ifexpr:({{CURRENTMONTH}} &gt;= {{REVISIONMONTH}}+1 or {{CURRENTYEAR}} &gt; {{REVISIONYEAR}}) and {{CURRENTDAY}} &gt;= {{REVISIONDAY}}|
[[Category:Candidates for speedy deletion]]|[[Category:Unused Redirects/{{#switch:&quot;{{REVISIONMONTH}}&quot;
| &quot;01&quot; = January
| &quot;02&quot; = Febrary
| &quot;03&quot; = March
| &quot;04&quot; = April
| &quot;05&quot; = May
| &quot;06&quot; = June
| &quot;07&quot; = July
| &quot;08&quot; = August
| &quot;09&quot; = September
| &quot;10&quot; = October
| &quot;11&quot; = November
| &quot;12&quot; = December
}} {{REVISIONYEAR}}]]}}&lt;/includeonly&gt;&lt;noinclude&gt;
This template marks a page as being an archived redirect, which will be maintained for a period of time in case external sites are linked to this page. 
*'''''Always''''' use the form &lt;nowiki&gt;{{Unused Redirect|NEWPAGENAME}}&lt;/nowiki&gt;
*Make sure to blank the page when adding this tag (including the redirect... this template will provide the redirect).
*Please do not subst. 

''This adds page to [[:Category:Candidates for speedy deletion]] after a month''

== See Also ==

*{{tl1|rfd|reason}}
*{{tl|Impending Doom}}
&lt;/noinclude&gt;</text>
      <sha1>083uebx3mw1wg6oq7brrtdclzbderke</sha1>
    </revision>
  </page>
  <page>
    <title>User:Herraotic/Intermediate Mathematics</title>
    <ns>2</ns>
    <id>107587</id>
    <revision>
      <id>4668996</id>
      <parentid>718559</parentid>
      <timestamp>2026-09-05T19:10:39Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668996</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1322" sha1="mm5hpskgptq8xa6nbs2flkh3wl6qkq5" xml:space="preserve">===Welcome to '''Intermediate Mathematics'''===
The objective of this book is to provide a thorough explanation of intermediate mathematics also referred to as GCSE Higher Mathematics, though it could also be used for any other course with similar requirements.

This book is currently not based on a specification as we are attempting to cover all topics, from all perspectives.

{| style=&quot;background-color: transparent;color:inherit;&quot;
| colspan=&quot;3&quot; | [[/Introduction/]] · [[/About/]] · [[/Q&amp;A|Ask a question!]]
|-
| style=&quot;vertical-align:top; width:25%&quot; | 
; Module 1 - Part 1
* Estimation
* Multiplying &amp; dividing with decimals
* Exact calculations
* Summary about numbers
* Factors &amp; multiples
* Prime numbers
* Tests of divisibility
* Prime factorisation
* HCF &amp; LCM
* Rules of indices
| style=&quot;vertical-align:top; width:25%&quot; | 
; Module 2 - Part 1
* ...
* ...
| style=&quot;vertical-align:top; width:25%&quot; | 
; Module 3 - Part 1
* ...
* ...
| style=&quot;vertical-align:top; width:25%&quot; | 
; Module 4 - Part 1
* ...
* ...
|-
| style=&quot;vertical-align:top; width:25%&quot; | 
; Module 1 - Part 2
* ...
* ...
| style=&quot;vertical-align:top; width:25%&quot;| 
; Module 2 - Part 2
* ...
* ...
| style=&quot;vertical-align:top; width:25%&quot; | 
; Module 3 - Part 2
* ...
* ...
| style=&quot;vertical-align:top; width:25%&quot; | 
; Module 4 - Part 2
* ...
* ...
|}</text>
      <sha1>mm5hpskgptq8xa6nbs2flkh3wl6qkq5</sha1>
    </revision>
  </page>
  <page>
    <title>User:Kijog/sandbox2</title>
    <ns>2</ns>
    <id>109288</id>
    <revision>
      <id>4669019</id>
      <parentid>4622029</parentid>
      <timestamp>2026-09-05T20:10:59Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669019</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="46460" sha1="qwuaurnw4nf7igvda5cr087up9l1krf" xml:space="preserve">{| style=&quot;text-align: center; background: #ffffff;{{Text default color}}; border: solid 10px #D3D3D3&quot; rules=&quot;all&quot;
! style=&quot;background-color: #D3D3D3;{{Text default color}};text-align: center&quot; colspan=&quot;3&quot;| The Colours [[Image:Flag of Wales (1959).svg|20px]] Yr Lliwiau
|- 
! Saesneg
! 
! Cymraeg
|-
| Red
| style=&quot;background-color:red;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Coch
|-
| Orange
| style=&quot;background-color:orange;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Oren
|-
| Yellow
| style=&quot;background-color:yellow;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Melyn
|-
| Green
| style=&quot;background-color:green;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Gwyrdd
|-
| Blue
| style=&quot;background-color:blue;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Glas
|-
| Purple
| style=&quot;background-color:purple;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Glasgoch
|-
| Brown
| style=&quot;background-color:brown;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Brown
|-
| Pink
| style=&quot;background-color:pink;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Pinc
|-
| White
| style=&quot;background-color:white;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Gwyn
|-
| Grey
| style=&quot;background-color:gray;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Llwyd
|-
| Black
| style=&quot;background-color:black;{{Text default color}};&quot; | &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
| Du
|}
{{Infobox Language
|name=Welsh
|nativename=Cymraeg
|familycolor=Indo-European
|pronunciation=[kəmˈrɑːɨɡ]
|states=[[United Kingdom]], [[Argentina]], [[United States]], [[Canada]], [[Australia]], [[New Zealand]]
|region=[[Wales]], [[Chubut]]
|speakers=700,000+:&lt;br&gt;— Wales: 611,000&lt;ref&gt;http://www.bwrdd-yr-iaith.org.uk/cynnwys.php?pID=109&amp;nID=2122&amp;langID=2&lt;/ref&gt;&lt;br&gt;— [[England]]: 133,000&lt;ref&gt;http://www.ibiblio.org/pub/archives/welsh-l/welsh-l/1993/Mar/More-Welsh-Speakers&lt;/ref&gt;&lt;br&gt;— [[Chubut Province|Chubut]], [[Argentina]]: 5,000&lt;ref&gt;http://www.bbc.co.uk/dna/h2g2/A1163503&lt;/ref&gt;&lt;br&gt;— [[Canada]]: 3,160&lt;ref&gt;http://www.ethnologue.com/show_country.asp?name=CA&lt;/ref&gt;&lt;br&gt;— [[United States|USA]]: 2,655&lt;ref&gt;http://www.usenglish.org/foundation/research/lia/languages_of_the_usa.pdf&lt;/ref&gt;
|fam2=[[Celtic languages|Celtic]]
|fam3=[[Insular Celtic languages|Insular Celtic]]
|fam4=[[Brythonic languages|Brythonic]]
|nation=[[Wales]]
|script=[[Latin alphabet]] ([[Welsh alphabet|Welsh variant]])
|map=[[Image:Siaradwyr y Gymraeg ym Mhrif Ardaloedd Cymru.png|center|thumb|300px|Percentage  of Welsh speakers by [[Subdivisions of Wales|principal area]]]]
|iso1=cy
|iso2b=wel|iso2t=cym
|iso3=cym}}

'''Welsh''' (''{{lang|cy|Cymraeg}}'' or ''{{lang|cy|y Gymraeg}}'', [[International Phonetic Alphabet|pronounced]] {{IPA|[kəmˈrɑːɨɡ]}}, {{IPA|[ə ɡəmˈrɑːɨɡ]}}), is a member of the [[Brythonic]] branch of [[Celtic languages|Celtic]] spoken natively in [[Wales]] (''Cymru''), in [[England]] by some along the Welsh border, and in the [[Welsh settlement in Argentina|Welsh immigrant colony]] in the [[Chubut Valley]], in [[Argentina|Argentine]] [[Patagonia]].

There are also speakers of Welsh throughout the world, most notably in the rest of [[Great Britain]], the [[United States]], [[Canada]] and [[Australia]].

Due to the increasing use of the [[English language]] the numbers of Welsh speakers had been declining for decades.  However, following a number of measures, including the introduction of the [[Welsh Language Act 1993]], Welsh has enjoyed a strong revival in recent years and has an equal status with English in the public sector in Wales.  It is the most spoken Celtic language.

See [[Welsh English]] for the [[English language]] as spoken in Wales.

==Status==

[[image:wales.cardiff.slow.arp.750pix.jpg|thumb|left|Bilingual road markings in Wales]]

The 2004 Welsh Language Use Survey shows 21.7% of the population of Wales are Welsh speakers. This is an increase from 20.5% in the [[Census 2001|2001 census]], and from 18.5% in 1991.  The 2001 census also shows that about 25% of Welsh residents were born outside Wales.  The number of Welsh speakers in the rest of Britain is unknown.   In [[1993]], [[S4C]], the Welsh-language TV channel published the results of a
survey into the numbers of people who speak or understand Welsh, and this estimated that there were some 133,000 Welsh-speakers living in [[England]], about 50,000 of them in the [[Greater London]] area and border towns and villages in the Welsh Marches such as [[Oswestry]].
&lt;ref&gt;[http://www.ibiblio.org/pub/archives/welsh-l/welsh-l/1993/Mar/More-Welsh-Speakers Summary of 1993 S4C survey]&lt;/ref&gt;

Historically, large numbers of Welsh people spoke only Welsh, but [[monoglot]] Welsh speakers are now virtually non-existent. Almost without exception, Welsh speakers also speak English (or, among those in [[Chubut Province]], [[Spanish language|Spanish]]).  However, a large number of Welsh speakers are more comfortable expressing themselves in Welsh than in English.  A speaker's choice of language can vary according to the subject domain and the social context (known in linguistics as [[code-switching]]).

Although Welsh is a minority language, support for the language grew during the second half of the [[20th century]], along with the rise of organisations such as the [[Welsh nationalism|nationalist]] political party [[Plaid Cymru]] and the Welsh Language Society, [[Cymdeithas yr Iaith Gymraeg]].

Welsh as a first language is largely concentrated in the less urban north and west of Wales, principally [[Gwynedd]], [[Denbighshire]] (''{{lang|cy|Sir Ddinbych}}''), [[Anglesey]] (''{{lang|cy|Ynys Môn}}''), [[Carmarthenshire]] (''{{lang|cy|Sir Gaerfyrddin}}''), north [[Pembrokeshire]] (''{{lang|cy|Sir Benfro}}''), [[Ceredigion]], parts of west [[Glamorgan]] (''{{lang|cy|Morgannwg}}''), north-west and extreme south-west [[Powys]], although first-language and other fluent speakers can be found throughout Wales.

[[Image:Callaghan_Square_sign_Cardiff_Caerdydd_200507.jpg|thumb|Bilingual road sign in [[Cardiff]].]]

Welsh is a [[living language]], used in conversation by thousands and seen throughout Wales. The [[Welsh Language Act 1993]] and the [[Government of Wales Act 1998]] provide that the Welsh and English languages should be treated equally.  Public bodies are required to prepare and implement a Welsh Language Scheme.  Local councils and the [[Welsh Assembly]] use Welsh  as an official language, issuing official literature and publicity in Welsh versions (e.g. letters to parents from schools, library information, and council information) and all road signs in Wales should be in English and Welsh, including the Welsh versions of place names.  The teaching of Welsh is now compulsory in all schools in Wales up to age 16, and this has had a major effect in stabilising and to some extent reversing the decline in the language.  It means, for example, that even the children of English monoglot migrants to Wales grow up with  a knowledge of the language.  However, the vast majority of people in the main population centres of South Wales do not use the language in daily life.

The UK government has ratified the [[European Charter for Regional or Minority Languages]] in respect to Welsh.

The language has greatly increased its prominence since the creation of the television channel [[S4C]] in November [[1982]], which broadcasts exclusively in Welsh during peak viewing hours. The main evening television news provided by the [[BBC]] in Welsh is  [http://www.bbc.co.uk/cymru/live/newyddion.ram available for download] (Real Media).

Since December [[2001]] the British Government has planned to ensure that all immigrants know [[English language|English]]. It remains to be seen if Welsh will be considered a separate case. At present, a knowledge of either Welsh, English or [[Scottish Gaelic]] is sufficient for [[naturalisation]] purposes and it is believed that this policy will be continued in any proposed changes to the law.

==History==
{| border=&quot;0&quot; cellpadding=&quot;5&quot; &lt;!--margin=&quot;1&quot;--&gt; style=&quot;text-align:right;background-color:#ffffd9;{{Text default color}};margin-left:10px&quot;
|style=&quot;background-color:#ffffd9;{{Text default color}};&quot;|&lt;timeline&gt;
ImageSize = width:240 height:700
PlotArea = right:40 top:10 left:40 bottom:10
DateFormat = yyyy
TimeAxis = orientation:vertical order:reverse
Period = from:500 till:2006
AlignBars = early
ScaleMajor = unit:year increment:200 start:500
Colors = 
 id:canvas value:rgb(1,1,0.85) 
BackgroundColors = canvas:canvas
PlotData =
 width:15 color:blue
 bar:test from:500 till:800 shift:(10,0) text:Early Welsh
PlotData = 
 width:15 color:black
 bar:test from:800 till:1050 shift:(10,0) text:[[Old Welsh language|Old Welsh]]
PlotData = 
 width:15 color:white
 bar:test from:1050 till:1250 shift:(10,0) text:[[Middle Welsh language|Middle Welsh]]
PlotData = 
 width:15 color:red
 bar:test from:1250 till:1588 shift:(10,0) text:Early Modern Welsh
PlotData = 
 width:15 color:green
 bar:test from:1588 till:2006 shift:(10,0) text:Late Modern Welsh 
PlotData = 
 bar:test at:1588 mark:(line,white)
 at:1588 shift:(10,0) text:1588 William Morgan's Welsh~Bible published
 bar:test at:1993 mark:(line,white)
 at:1983 shift:(10,0) text:1993 Welsh Language Act
 bar:test at:2001 mark:(line,white)
 at:2006 shift:(10,0) text:2001 Number of speakers increase~in the national Census
&lt;/timeline&gt;
|}
Like most languages, there are identifiable periods within the history of Welsh, although the boundaries between these are often indistinct. 

===Old Welsh===
The earliest extant sources of a language identifiable as Welsh go back to about the 6th century, and the language of this period is known as ''Early Welsh''. Very little of this language remains.  The next main period, somewhat better attested, is [[Old Welsh language|Old Welsh]] (''{{lang|cy|Hen Gymraeg}}'') ([[9th century|9th]] to [[11th century|11th]] centuries); [[poetry]] from both Wales and [[Scotland]] has been preserved in this form of the language.  As [[Anglo-Saxons|Germanic]] and [[Gaels|Gaelic]] colonisation of Great Britain proceeded, the Brythonic speakers in Wales were split off from those in northern England, speaking [[Cumbrian language|Cumbrian]], and those in the south-west, speaking what would become [[Cornish language|Cornish]], and so the languages diverged. Both ''Canu Aneirin'' and ''Canu Taliesin'' were in this era.

===Middle Welsh===
''[[Middle Welsh language|Middle Welsh]]'' (or ''{{lang|cy|Cymraeg Canol}}'') is the label attached to the Welsh of the [[12th century|12th]] to [[14th century|14th]] centuries, of which much more remains than for any earlier period. This is the language of nearly all surviving early manuscripts of the ''[[Mabinogion]]'', although the tales themselves are certainly much older. It is also the language of the existing [[Welsh law]] manuscripts.  Middle Welsh is reasonably intelligible, albeit with some work, to a modern-day Welsh speaker.

===Modern Welsh===
Modern Welsh can be divided into two periods. The first, ''Early Modern Welsh'' ran from the [[14th century]] to roughly the end of the [[16th century]] and was the language used by [[Dafydd ap Gwilym]]. 

====Late Modern Welsh====
''Late Modern Welsh'' began with the publication of [[William Morgan (Bible translator)|William Morgan]]'s [[Welsh Bible|translation of the Bible]] in [[1588]]. Like its English counterpart, the [[King James Version of the Bible|King James Version]], this proved to have a strong stabilising effect on the language, and indeed the language today still bears the same ''Late Modern'' label as Morgan's language. Of course, many minor changes have occurred since then.

====19th century====
The language enjoyed a further boost in the [[19th century]], with the publication of some of the first complete and concise Welsh [[dictionary|dictionaries]]. Early work by Welsh [[lexicography|lexicographic]] pioneers such as [[Daniel Silvan Evans]] ensured that the language was documented as accurately as possible, and modern dictionaries such as the ''{{lang|cy|[[Geiriadur Prifysgol Cymru]]}}'' (the [[University of Wales]] Dictionary), are direct descendants of these dictionaries.

However, the influx of English workers during the [[Industrial Revolution]] in Wales from about [[1800]] led to a substantial dilution of the Welsh-speaking population of Wales.  English migrants seldom learnt Welsh and their Welsh colleagues tended to speak English in mixed Welsh–English contexts, and bilingualism became almost universal. The legal status of Welsh was inferior to that of English, and so English gradually came to prevail, except in the most rural areas, particularly in north west and mid Wales.  An important exception, however, was in the [[non-conformist]] churches, which were strongly associated with the Welsh language.

====20th and 21st centuries====
By the twentieth century, the numbers of Welsh speakers were shrinking at a rate which suggested that it would be extinct within a few generations. The 10-yearly [[census]] first started to ask language questions in [[1891]], by which time 54% of the population still spoke Welsh. The percentage fell with every subsequent census, until reaching an all-time low in [[1981]] (19%). In [[1991]] the position was stable (19% as in 1981) and in the most recent census, [[as of 2001|2001]], it has risen to 21% able to speak Welsh. The [[Census 2001|2001 census]] also recorded that 20% could read Welsh, 18% could write Welsh, and 24% could understand Welsh. Furthermore, the highest proportion of Welsh speakers was among young people, which bodes well for the future of Welsh. In 2001, 39% of children aged 10 to 15 were able to speak, read and write Welsh (many of them having learned it in school), compared with 25% of 16 to 19 year olds. However, the percentage of Welsh speakers in areas where Welsh is spoken by the majority is still in decline.

It seems that the rise of [[Welsh nationalism]] rallied supporters of the language, and the establishment of Welsh television and radio found a mass audience which was encouraged in the retention of its Welsh. Perhaps most important of all, at the end of the twentieth century it became compulsory for all school children to learn Welsh up to age 16, and this both reinforced the language in Welsh-speaking areas and reintroduced at least an elementary knowledge of it in areas which had become more or less wholly Anglophone. The decline in the percentage of people in Wales who can speak Welsh has now been halted, and there are even signs of a modest recovery. However, although Welsh is the daily language in many parts of Wales, English is almost universally understood.

==Orthography==
{{main|Welsh alphabet}}

Welsh is written in a version of the [[Latin alphabet]] consisting of 28 letters, of which eight are [[digraph (orthography)|digraph]]s treated as single letters for [[collation]]:

: a, b, c, ch, d, dd, e, f, ff, g, ng, h, i, l, ll, m, n, o, p, ph, r, rh, s, t, th, u, w, y

The letters ''j'' and ''v'', although not originally used to write Welsh, have been borrowed from the [[English alphabet]], and are most commonly used only within names, although there are a few exceptions.

The most common [[diacritic]] is the [[circumflex]], which is used in some cases to mark a [[vowel length|long vowel]].

==Grammar==
===Phonology===
====Consonants====
Welsh has the following [[consonant]] [[phoneme]]s:
{| class=&quot;wikitable&quot;
|- style=&quot;background: #efefef;{{Text default color}};&quot;
| &amp;nbsp;
! scope=&quot;col&quot; | [[bilabial consonant|Bilabial]]
! scope=&quot;col&quot; | [[labiodental consonant|Labiodental]]
! scope=&quot;col&quot; | [[labiovelar consonant|Labiovelar]]
! scope=&quot;col&quot; | [[dental consonant|Dental]]
! scope=&quot;col&quot; | [[alveolar consonant|Alveolar]]
! scope=&quot;col&quot; | Alveolar&lt;br /&gt;[[lateral consonant|lateral]]
! scope=&quot;col&quot; | [[postalveolar consonant|Postalveolar]]
! scope=&quot;col&quot; | [[palatal consonant|Palatal]]
! scope=&quot;col&quot; | [[velar consonant|Velar]]
! scope=&quot;col&quot; | [[glottal consonant|Glottal]]
|-
! scope=&quot;row&quot; style=&quot;background: #efefef;{{Text default color}};&quot; | '''[[plosive consonant|Plosive]]'''
| style=&quot;text-align:center;&quot; | {{IPA|p&amp;nbsp;&amp;nbsp;b}}
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|t&amp;nbsp;&amp;nbsp;d}}
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|k&amp;nbsp;&amp;nbsp;g}}
| &amp;nbsp;
|-
! scope=&quot;row&quot; style=&quot;background: #efefef;{{Text default color}};&quot; | '''[[affricate consonant|Affricate]]'''
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|(tʃ)&amp;nbsp;&amp;nbsp;(dʒ)}}
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
|-
! scope=&quot;row&quot; style=&quot;background: #efefef;{{Text default color}};&quot; | '''[[nasal consonant|Nasal]]'''
| style=&quot;text-align:center;&quot; | {{IPA|(m̥)&amp;nbsp;&amp;nbsp;m}}
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|(n̥)&amp;nbsp;&amp;nbsp;n}}
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|(ŋ̊)&amp;nbsp;&amp;nbsp;ŋ}}
| &amp;nbsp;
|-
! scope=&quot;row&quot; style=&quot;background: #efefef;{{Text default color}};&quot; | '''[[fricative consonant|Fricative]]'''
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|f&amp;nbsp;&amp;nbsp;v}}
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|θ&amp;nbsp;&amp;nbsp;ð}}
| style=&quot;text-align:center;&quot; | {{IPA|s&amp;nbsp;&amp;nbsp;(z) }}
| style=&quot;text-align:center;&quot; | {{IPA|ɬ}}
| style=&quot;text-align:center;&quot; | {{IPA|ʃ}}
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|x}}
| style=&quot;text-align:center;&quot; | {{IPA|h}}
|-
! scope=&quot;row&quot; style=&quot;background: #efefef;{{Text default color}};&quot; | '''[[Trill consonant|Trill]]'''
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|r̥&amp;nbsp;&amp;nbsp;r}}
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
| &amp;nbsp;
|-
! scope=&quot;row&quot; style=&quot;background: #efefef;{{Text default color}};&quot; | '''[[Approximant]]'''
| &amp;nbsp;
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|w}}
| &amp;nbsp;
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|l}}
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|j}}
| &amp;nbsp;
| &amp;nbsp;
|}

{{IPA|/z/}} occurs only in unassimilated [[loanword]]s.  {{IPA|/tʃ/}} and {{IPA|/dʒ/}} occur mainly in loanwords, but also in some dialects as developments from {{IPA|/tj/}} and {{IPA|/dj/}}; the [[voiceless consonant|voiceless]] [[nasal consonant|nasals]] {{IPA|/m̥/}}, {{IPA|/n̥/}}, {{IPA|/ŋ̊/}} occur only as a consequence of [[Welsh morphology#Initial consonant mutation|nasal mutation]].

====Vowels====
[[Image:Welsh vowel chart.svg|thumb|300px|A chart plotting the vowel [[formant]]s of a Welsh speaker from [[Bangor, Wales|Bangor]].]]
{|class=&quot;wikitable&quot;
! [[Monophthong]]s
! [[Front vowel|Front]]
! [[Central vowel|Central]]
! [[Back vowel|Back]]
|-
| '''[[Close vowel|Close]]'''
| style=&quot;text-align:center;&quot; | {{IPA|iː}}
| style=&quot;text-align:center;&quot; | {{IPA|ɨː}}
| style=&quot;text-align:center;&quot; | {{IPA|uː}}
|-
| '''[[Near-close vowel|Near-close]]'''
| style=&quot;text-align:center;&quot; | {{IPA|ɪ}}
| style=&quot;text-align:center;&quot; | {{IPA|ɨ̞}}
| style=&quot;text-align:center;&quot; | {{IPA|ʊ}}
|-
| '''[[Close mid vowel|Close mid]]'''
| style=&quot;text-align:center;&quot; | {{IPA|eː}}
| rowspan=2 style=&quot;text-align:center;&quot; | {{IPA|ə}}
| style=&quot;text-align:center;&quot; | {{IPA|oː}}
|-
| '''[[Open mid vowel|Open mid]]'''
| style=&quot;text-align:center;&quot; | {{IPA|ɛ}}
| style=&quot;text-align:center;&quot; | {{IPA|ɔ}}
|-
| '''[[Open vowel|Open]]'''
| style=&quot;text-align:center;&quot; | {{IPA|a}}
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|ɑː}}
|}

The vowels {{IPA|/ɨ̞/}} and {{IPA|/ɨː/}} occur only in Northern dialects; in Southern dialects they are replaced by {{IPA|/ɪ/}} and {{IPA|/iː/}} respectively. In Southern dialects, the contrast between long and short vowels is found in stressed [[syllable]]s only; in Northern dialects, the contrast is found only in stressed ''word-final'' syllables (including monosyllabic words).

The vowel {{IPA|/ə/}} does not occur in the final syllable of words (except a few monosyllables).

{|class=&quot;wikitable&quot;
! [[Diphthong]]s
! Second component&lt;br /&gt;is front
! Second component&lt;br /&gt;is central
! Second component&lt;br /&gt;is back
|-
| '''First component is close'''
| &amp;nbsp;
| style=&quot;text-align:center;&quot; | {{IPA|ʊɨ}}
| style=&quot;text-align:center;&quot; | {{IPA|ɪu, ɨu}}
|-
| '''First component is mid'''
| style=&quot;text-align:center;&quot; | {{IPA|əi, ɔi}}
| style=&quot;text-align:center;&quot; | {{IPA|əɨ, ɔɨ}}
| style=&quot;text-align:center;&quot; | {{IPA|ɛu, əu}}
|-
| '''First component is open'''
| style=&quot;text-align:center;&quot; | {{IPA|ai}}
| style=&quot;text-align:center;&quot; | {{IPA|aɨ, ɑːɨ}}
| style=&quot;text-align:center;&quot; | {{IPA|au}}
|}

The diphthongs containing {{IPA|/ɨ/}} occur only in Northern dialects; in Southern dialects {{IPA|/ʊɨ/}} is replaced by {{IPA|/ʊi/}}, {{IPA|/ɨu, əɨ, ɔɨ/}} are merged with {{IPA|/ɪu, əi, ɔi/}}, and {{IPA|/aɨ, ɑːɨ/}} are merged with {{IPA|/ai/}}.

====Stress====
[[Stress (linguistics)|Stress]] in polysyllabic words occurs most commonly on the [[wikt:penultimate|penultimate]] [[syllable]], more rarely on the final syllable.

The positioning of the stress means that related words or concepts (or even [[plural]]s) can sound quite different, as syllables are added to the end of a word and the stress moves correspondingly, e.g.:
: ''{{lang|cy|ysgrif}}'' — {{IPA|/ˈəsgriv/}} — an article or essay
: ''{{lang|cy|ysgrifen}}'' — {{IPA|/əsˈgriven/}} — writing
: ''{{lang|cy|ysgrifennydd}}'' — {{IPA|/əsgriˈvenɨð/}} — a secretary
: ''{{lang|cy|ysgrifenyddes}}'' — {{IPA|/əsgriveˈnəðes/}} — a female secretary

(Note also how adding a syllable to ''{{lang|cy|ysgrifennydd}}'' to form ''{{lang|cy|ysgrifenyddes}}'' changes the pronunciation of the second &quot;y&quot;. This is because the pronunciation of &quot;y&quot; depends on whether or not it is in the final syllable.)

The connection between the Welsh word ''{{lang|cy|ysgrif}}'' and the [[Latin language|Latin]] ''{{lang|la|scribo}}'' &quot;I write&quot;, from which it is derived, is fairly clear, taking [[Historical linguistics|diachronic sound shifts]] into account.

===Morphology===
{{main|Welsh morphology}}

Welsh [[morphology (linguistics)|morphology]] has much in common with that of the other modern [[Insular Celtic languages]], such as the use of initial [[consonant mutation]]s, and the use of so-called &quot;conjugated prepositions&quot; ([[preposition]]s that fuse with the personal [[pronoun]]s that are their [[object (grammar)|object]]). Welsh [[noun]]s belong to one of two [[grammatical gender]]s, masculine and feminine, but are not inflected for [[declension|case]]. Welsh has a variety of different endings to indicate the [[plural]], and two endings to indicate the [[grammatical number|singular]] of some nouns. In spoken Welsh, [[verb]] inflection is indicated primarily by the use of [[auxiliary verb]]s, rather than by the inflection of the main verb. In literary Welsh, on the other hand, inflection of the main verb is usual.

=== Other features of Welsh grammar ===
====Possessives as object pronouns==== 
The Welsh for &quot;I like Rhodri&quot; is &quot;''{{lang|cy|Dw i'n hoffi Rhodri}}''&quot; (&quot;I am liking [of] Rhodri&quot;), but &quot;I like ''him''&quot; is &quot;''{{lang|cy|Dw i'n '''ei''' hoffi fe}}''&quot; — literally, &quot;I am ''his'' liking him&quot;; &quot;I like ''you''&quot; is &quot;''{{lang|cy|Dw i'n '''dy''' hoffi di}}''&quot; (&quot;I am ''your'' liking you&quot;), etc.

====Significant use of auxiliary verbs====
While English can either use verbs directly (e.g. &quot;I go&quot;) or with the aid of an [[auxiliary verb]] (&quot;I am going&quot;, here using &quot;to be&quot; as the auxiliary), non-literary Welsh inclines very strongly towards the latter use. In the [[present tense]], all verbs are used with the auxiliary &quot;''{{lang|cy|bod}}''&quot; (to be), so &quot;''{{lang|cy|dw i'n mynd}}''&quot; is literally &quot;I am going&quot;, but also means simply &quot;I go&quot;. In the [[past tense|past]] and [[future tense|future]] tenses, there are [[inflected language|inflected]] forms of all verbs (which are invariably used in the written language), but it is more common nowadays in speech to use the [[verbal noun]] (''{{lang|cy|berfenw}}'', loosely equal to the [[infinitive]] in English) together with the inflected form of &quot;''{{lang|cy|gwneud}}''&quot; (to do), so &quot;I went&quot; can be &quot;''{{lang|cy|mi es i}}''&quot; or &quot;''{{lang|cy|mi wnes i fynd}}''&quot; and &quot;I will go&quot; can be &quot;''{{lang|cy|mi a' i}}''&quot; or &quot;''{{lang|cy|mi wna i fynd}}''&quot;. There is also a future form using the auxiliary ''{{lang|cy|bod}}'', giving &quot;''{{lang|cy|fydda i'n mynd}}''&quot; (perhaps best translated as &quot;I will be going&quot;) and an [[imperfect tense]] (a continuous/habitual past tense) also using &quot;''{{lang|cy|bod}}''&quot;, with &quot;''{{lang|cy|roeddwn i'n mynd}}''&quot; meaning &quot;I used to go/I was going&quot;.

====Affirmative markers====
''{{lang|cy|Mi}}'' or  ''{{lang|cy|fe}}'' is often placed before inflected verbs to show that they are declarative. In the present and imperfect of the verb ''{{lang|cy|bod}}'' (to be), ''{{lang|cy|yr}}'' is used instead.  ''Mi'' is mainly restricted to colloquial Northern Welsh, with ''fe'' predominating in the South and in the formal or literary register.  Such marking of the declarative is, in any case, rather less common in higher registers.

== Counting system ==
The traditional counting system used by the Welsh language is [[vigesimal]], i.e. based on twenties, as in [[French language|French]] numbers 80-99, where numbers from 11–14 are &quot;''x'' on ten&quot;, 16–19 are &quot;''x'' on fifteen&quot; (though 18 is more usually &quot;two nines&quot;); numbers from 21–39 are &quot;1–19 on twenty&quot;, 40 is &quot;two twenties&quot;, 60 is &quot;three twenties&quot;, etc.

There is also a decimal counting system, favoured by younger people, more common in South Wales, and which appears to be commonly used in Patagonian Welsh, where numbers are &quot;''x'' tens ''y''&quot;, e.g. thirty-five in decimal is ''{{lang|cy|tri deg pump}}'' (three ten five) while in vigesimal it is ''{{lang|cy|pymtheg ar hugain}}'' (fifteen – itself &quot;five-ten&quot; – on twenty).

A further complication is that while there is only one word for &quot;one&quot; (''{{lang|cy|un}}'') there are masculine and feminine forms of the numbers &quot;two&quot; (''{{lang|cy|dau}}'' and ''{{lang|cy|dwy}}''), &quot;three&quot; (''{{lang|cy|tri}}'' and ''{{lang|cy|tair}}'') and &quot;four&quot; (''{{lang|cy|pedwar}}'' and ''{{lang|cy|pedair}}''), which must agree with the [[grammatical gender]] of the objects being counted, though this rule is less strictly observed with the decimal counting system.

{|class=&quot;wikitable&quot;
! Number
! Vigesimal system
! Decimal system
|-
| 1
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|un}}
|-
| 2
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|dau}} (m), {{lang|cy|dwy}} (f)
|-
| 3
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|tri}} (m), {{lang|cy|tair}} (f)
|-
| 4
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|pedwar}} (m), {{lang|cy|pedair}} (f)
|-
| 5
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|pump}}
|-
| 6
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|chwech}}
|-
| 7
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|saith}}
|-
| 8
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|wyth}}
|-
| 9
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|naw}}
|-
| 10
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|deg}}
|-
| 11
| {{lang|cy|un ar ddeg}}
| {{lang|cy|un deg un}}
|-
| 12
| {{lang|cy|deuddeg}}
| {{lang|cy|un deg dau}}
|-
| 13
| {{lang|cy|tri/tair ar ddeg}}
| {{lang|cy|un deg tri}}
|-
| 14
| {{lang|cy|pedwar/pedair ar ddeg}}
| {{lang|cy|un deg pedwar}}
|-
| 15
| {{lang|cy|pymtheg}}
| {{lang|cy|un deg pump}}
|-
| 16
| {{lang|cy|un ar bymtheg}}
| {{lang|cy|un deg chwech}}
|-
| 17
| {{lang|cy|dau/dwy ar bymtheg}}
| {{lang|cy|un deg saith}}
|-
| 18
| {{lang|cy|deunaw}} (&quot;two nines&quot;)
| {{lang|cy|un deg wyth}}
|-
| 19
| {{lang|cy|pedwar/pedair ar bymtheg}}
| {{lang|cy|un deg naw}}
|-
| 20
| {{lang|cy|ugain}}
| {{lang|cy|dau ddeg}}
|-
| 21
| {{lang|cy|un ar hugain}}
| {{lang|cy|dau ddeg un}}
|-
| 22
| {{lang|cy|dau/dwy ar hugain}}
| {{lang|cy|dau ddeg dau}}
|-
| 23
| {{lang|cy|tri/tair ar hugain}}
| {{lang|cy|dau ddeg tri}}
|-
| 24
| {{lang|cy|pedwar/pedair ar hugain}}
| {{lang|cy|dau ddeg pedwar}}
|-
| 25
| {{lang|cy|pump ar hugain}}
| {{lang|cy|dau ddeg pump}}
|-
| 26
| {{lang|cy|chwech ar hugain}}
| {{lang|cy|dau ddeg chwech}}
|-
| 27
| {{lang|cy|saith ar hugain}}
| {{lang|cy|dau ddeg saith}}
|-
| 28
| {{lang|cy|wyth ar hugain}}
| {{lang|cy|dau ddeg wyth}}
|-
| 29
| {{lang|cy|naw ar hugain }}
| {{lang|cy|dau ddeg naw}}
|-
| 30
| {{lang|cy|deg ar hugain}}
| {{lang|cy|tri deg}}
|-
| 31
| {{lang|cy|un ar ddeg ar hugain}}
| {{lang|cy|tri deg un}}
|-
| 32
| {{lang|cy|deuddeg ar hugain}}
| {{lang|cy|tri deg dau}}
|-
| etc.
|
|
|-
| 40
| {{lang|cy|deugain}} (&quot;two twenties&quot;)
| {{lang|cy|pedwar deg}}
|-
| 41
| {{lang|cy|deugain ac un}}
| {{lang|cy|pedwar deg un}}
|-
| 50
| {{lang|cy|hanner cant}} (&quot;half a hundred&quot;)
| {{lang|cy|pump deg}}
|-
| 51
| {{lang|cy|hanner cant ac un}}
| {{lang|cy|pum deg un}}
|-
| 60
| {{lang|cy|trigain}}
| {{lang|cy|chwe deg}}
|-
| 61
| {{lang|cy|trigain ac un}}
| {{lang|cy|chwe deg un}}
|-
| 70
| {{lang|cy|deg a thrigain}}
| saith deg
|-
| 71
| {{lang|cy|un ar ddeg a thrigain}}
| {{lang|cy|saith deg un}}
|-
| 80
| {{lang|cy|pedwar ugain}}
| {{lang|cy|wyth deg}}
|-
| 81
| {{lang|cy|pedwar ugain ac un}}
| {{lang|cy|wyth deg un}}
|-
| 90
| {{lang|cy|deg a phedwar ugain}}
| {{lang|cy|naw deg}}
|-
| 91
| {{lang|cy|un ar ddeg a phedwar ugain}}
| {{lang|cy|naw deg un}}
|-
| 100
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|cant}}
|-
| 200
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|dau gant}}
|-
| 300
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|tri chant}}
|-
| 400
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|pedwar cant}}
|-
| 500
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|pum cant}}
|-
| 600
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|chwe chant}}
|-
| 1000
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|mil}}
|-
| 2000
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|dwy fil}}
|-
| 1,000,000
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|miliwn}}
|-
| 1,000,000,000
| colspan=&quot;2&quot; style=&quot;text-align: center;&quot; | {{lang|cy|biliwn}}
|}

'''Notes''':

* The words ''{{lang|cy|deg}}'' (ten), ''{{lang|cy|deuddeg}}'' (twelve) and ''{{lang|cy|pymtheg}}'' (fifteen) often become ''{{lang|cy|deng}}'', ''{{lang|cy|deuddeng}}'' and ''{{lang|cy|pymtheng}}'' respectively when before a word beginning with &quot;m&quot;, e.g. ''{{lang|cy|deng munud}}'' (ten minutes), ''{{lang|cy|deuddeng milltir}}'' (twelve miles), ''{{lang|cy|pymtheng mlynedd}}'' (fifteen years).

* The numbers ''{{lang|cy|pump}}'' (five), ''{{lang|cy|chwech}}'' (six) and ''{{lang|cy|cant}}'' (hundred) drop the final consonant when they stand immediately in front of a noun, e.g. ''{{lang|cy|pum potel}}'' (five bottles), ''{{lang|cy|chwe llwy}}'' (six spoons), ''{{lang|cy|can punt}}'' (a hundred pounds).

* Larger numbers tend to use the decimal system, e.g. 1,965 ''{{lang|cy|mil, naw cant chwe deg pump}}''. An exception to this rule is when referring to years, where after the number of thousands, the individual digits are spoken, e.g. 1965 ''{{lang|cy|mil naw chwe(ch) pump}}''. This system appears to have broken down for years after 2000, e.g. 2005 is ''{{lang|cy|dwy fil a phump}}''.

* The number ''miliwn'' is feminine, and ''biliwn'' is masculine.  It is necessary for the gender of these to be different as they can both mutate to ''filiwn''.  Two million is therefore ''dwy filiwn'', and two billion is ''dau filiwn''.

==Dialects==
[[Dialect]]ical differences are very evident in the spoken, and to a lesser extent the written, language. A convenient, if slightly simplistic, classification is into ''North Walian'' and ''South Walian'' forms (or &quot;''{{lang|cy|Gog}}''&quot; and &quot;''{{lang|cy|Hwntw}}''&quot; based on the word for North, ''{{lang|cy|gogledd}}'', and the South Walian word for &quot;them over there&quot;). The differences between dialects encompass vocabulary, pronunciation and grammar, although particularly in the last regard the differences are in fact relatively minor. Much more fine-grained classifications exist beyond north and south: the book ''{{lang|cy|Cymraeg, Cymrâg, Cymrêg: cyflwyno'r tafodieithoedd}}'',&lt;ref&gt;Thomas, B. and Thomas, P. W. ''{{lang|cy|Cymraeg, Cymrâg, Cymrêg: cyflwyno'r tafodieithoedd}}'', published by Gwasg Taf, {{#isbn:0-948469-14-5}}. Out of print&lt;/ref&gt; about Welsh dialects was accompanied by a cassette containing recordings of fourteen different speakers demonstrating aspects of different dialects. The book refers to the earlier ''Linguistic Geography of Wales''&lt;ref&gt;Thomas, A. R. [[1973]] ''Linguistic Geography of Wales''&lt;/ref&gt; as describing six different regions which could be identified as having words specific to those regions.

Another dialect is [[Patagonian Welsh]], which has developed since the start of the [[Welsh settlement in Argentina]] in [[1865]]; it includes [[Spanish language|Spanish]] loanwords and terms for local features.

An example of the difference between North and South Walian usage would be the question &quot;Do you want a cup of tea?&quot; In the North this would typically be &quot;''{{lang|cy|Dach chi isio panad?}}''&quot;, while in the South the question &quot;''{{lang|cy|Dych chi moyn dishgled?}}''&quot; would be more likely. An example of a pronunciation difference between Northern and Southern Welsh is the tendency of Southern dialects to &quot;lisp&quot; the letter &quot;s&quot;, e.g. ''{{lang|cy|mis}}'' (month), would tend to be pronounced {{IPA|[miːs]}} in the north, and {{IPA|[miːʃ]}} in the south.

In fact, the difference between dialects of modern spoken Welsh pale into insignificance compared to the difference between the spoken and literary languages. The latter is significantly more formal and is the language of [[Welsh Bible|Welsh translations]] of the [[Bible]], amongst other things (although the ''{{lang|cy|Beibl Cymraeg Newydd}}'' — New Welsh Bible — is significantly less formal than the traditional [[1588]] [[Bible]]). Gareth King, author of a Welsh grammar, observes that &quot;The difference between these two is much greater than between the virtually identical colloquial and literary forms of English&quot; and goes so far as to state &quot;that there are good grounds for regarding them as separate languages&quot;.  He comments that whilst colloquial Welsh is a mother tongue requiring no special learning to acquire, literary Welsh is the mother tongue of no-one, and must be taught to people.&lt;ref&gt;King, G. ''Modern Welsh: a comprehensive grammar'', published by Routledge, {{#isbn:0-415-09269-8}} p3&lt;/ref&gt;

Although the question &quot;Do you want a cup of tea?&quot; is not likely to occur in literary Welsh usage, if it did it would be along the lines of &quot;''{{lang|cy|A oes arnoch eisiau cwpanaid o de?}}''&quot;

Amongst the characteristics of the literary, as against the spoken, language are a higher dependence on inflected verb forms, a shift in the usage of some of the tenses, a reduction in the explicit use of pronouns (since the information is usually conveyed in the verb/preposition inflections) and a greatly reduced tendency to substitute [[English language|English]] loanwords for native Welsh words.

==Diglossia: Literary vs. Colloquial Welsh==
Modern Welsh can be written in two varieties - '''Colloquial Welsh''' (''Cymraeg llafar'') or '''Literary Welsh''' (''Cymraeg llenyddol''). The grammar described on this page is that of Colloquial Welsh, which is used for speech and informal writing.  Literary Welsh is closer to the form of Welsh used in the 1588 translation of the Bible and is found in official documents and other formal [[Register (linguistics)|registers]], including much literature.  As a standardised form, literary Welsh shows little if any of the dialectal variation found in colloquial Welsh.

Some differences include

{| class=&quot;wikitable&quot;
|-
! Literary Welsh
! Colloquial Welsh
|-
| Can omit subject pronouns ([[Pro-drop language|pro-drop]])
| Subject pronouns rarely omitted
|-
| Extensive use of simple verb forms
| Extensive use of periphrastic verb forms
|-
| No distinction between simple present and future (e.g. ''gwelaf'' &quot;I see&quot;/&quot;I shall see&quot;)
| Simple form expresses only future (e.g. ''gwela i'' &quot;I'll see&quot;) 
|-
| Subjunctive verb forms
| Subjunctive in fixed idioms
|-
| 3rd.pl ending = ''–nt''
| 3rd.pl ending = ''–n''
|}

In addition, more archaic pronouns and forms of mutation may be observed in Literary Welsh. A complete grammar of Literary Welsh can be found in ''A Grammar of Welsh'' (1980) by Stephen J. Williams.

Currently, most Welsh writing, especially that found on the Internet or in magazines, is closer to the '''Colloquial''' form.  This is also becoming more common in artistic literature.

===Examples of sentences in literary and colloquial Welsh===

{| class=&quot;wikitable&quot;
|-
! English 
! Literary Welsh
! Colloquial Welsh
|-
| I get up early every day
| Codaf yn gynnar bob dydd 
| Dw i'n codi'n gynnar bob dydd
|-
| I'll get up early tomorrow
| Codaf yn gynnar yfory
| Coda i'n gynnar fory/wna i godi'n gynnar fory
|-
| S/he had not stood there long
| Ni safasai yno'n hir 
| Doedd hi/o ddim wedi sefyll yno'n hir
|-
| They'll sleep only when there's a need
| Ni chysgant ond pan fo angen
| Byddan nhw ddim ond yn cysgu pan fydd angen
|-
|}

==Welsh in education==
The decade around [[1840]] was a period of great social upheaval in Wales, manifested in the [[Chartism|Chartist]] movement, which culminated in 20,000 people marching on [[Newport]] in [[1839]] resulting in a [[riot]] when 20 people were killed by soldiers defending the Westgate Hotel, and the [[Rebecca Riots]] when [[tollbooth]]s on [[turnpikes]] were systematically destroyed. This unrest brought the state of education in Wales to the attention of the English establishment, as social reformers of the time considered education as a means of dealing with social ills. ''[[The Times]]'' newspaper was prominent among those who considered that the lack of education of the Welsh people was the root cause of most of the problems, although the population was generally literate in Welsh because of the activities of [[Sunday School]]s and the need to read the Bible. In July [[1846]], three commissioners, R. R. W. Lingen, Jellynger C. Symons and H. R. Vaughan Johnson, were appointed to inquire into the state of education in Wales; the Commissioners were all [[Anglican]]s, and hence unsympathetic to the Non-conformist majority in Wales, and were monoglot English-speakers.

The Commissioners presented their report to the Government on [[1 July]] [[1847]] in three large blue-bound volumes. This report quickly became known as ''{{lang|cy|Brad y Llyfrau Gleision}}'' (The [[Treachery of the Blue Books]]) as, apart from documenting the state of education in Wales, the Commissioners were also free with their comments disparaging the language, Non-conformity, and the morals of the Welsh people in general. An immediate effect of the report was for a belief to take root in the minds of ordinary people that the only way for Welsh people to get on in the world was through the medium of English, and an inferiority complex developed about the Welsh language whose effects have not yet been completely eradicated. The historian Professor [[Kenneth O. Morgan]] referred to the significance of the report and its consequences as &quot;the [[Massacre of Glencoe|Glencoe]] and the [[Amritsar massacre|Amritsar]] of Welsh history&quot;.

In the later [[19th century]] virtually all teaching in the schools of Wales was in English, even in areas where the pupils barely understood English. Some schools used the [[Welsh Not]], a piece of wood, often bearing the letters &quot;WN&quot;, which was hung around the neck of any pupil caught speaking Welsh. The pupil could pass it on to any schoolmate heard speaking Welsh, with the pupil wearing it at the end of the day being given a beating. Towards the beginning of the 20th century this policy slowly began to change, partly owing to the efforts of [[Owen Morgan Edwards]] when he became chief inspector of schools for Wales in [[1907]].

The [[Aberystwyth]] Welsh School (''{{lang|cy|Ysgol Gymraeg Aberystwyth}}'') was founded in [[1939]] by Sir Ifan ap Owen Edwards, the son of O.M. Edwards as the first Welsh Primary School. The headteacher was Norah Isaac. {{lang|cy|Ysgol Gymraeg}} is still a very successful school and now there are Welsh language primary schools all over the country. Ysgol Glan Clwyd was established in [[Rhyl]] in [[1955]] as the first Welsh language school to teach to a secondary level. 

Welsh is now widely used in [[education]].  All Welsh universities teach some courses in Welsh (most notably the [[University of Wales, Bangor]] and the [[University of Wales, Aberystwyth]]) but are primarily English language. Under the [[National Curriculum]], [[Education in Wales|schoolchildren in Wales]] must study Welsh up to the age of 16.  Over a quarter of children in Wales attend schools which teach predominantly through the medium of Welsh. &lt;ref&gt;Figures for 2002-03: [http://www.bwrdd-yr-iaith.org.uk/cynnwys.php?pID=219&amp;langID=2 ''Welsh medium or bilingual provision''], [[Welsh Language Board]]&lt;/ref&gt;. The remainder study Welsh as a second language in English-medium schools.  Specialist teachers of Welsh called ''{{lang|cy|Athrawon Bro}}'' support the teaching of Welsh in the National Curriculum.

==Welsh in information technology==
Welsh has a substantial presence on the Internet, ranging from formal lists of terminology in a variety of fields &lt;ref&gt;The [http://www.e-gymraeg.org/bwrdd-yr-iaith/termau/default.aspx?lang=en Welsh National Database of Standardised Terminology] was [http://www.bwrdd-yr-iaith.org.uk/cynnwys.php?pID=241&amp;langID=2&amp;nID=640 released in March 2006].&lt;/ref&gt; to Welsh language interfaces for parts of [[Microsoft Windows XP]], a variety of [[Linux distribution]]s, and some online services to [[blog]]s kept in Welsh.&lt;ref&gt;Selections of Welsh-language blogs are listed on the sites  [http://rhithfro.com Y Rhithfro] and [http://blogiadur.com Blogiadur].&lt;/ref&gt;

==Welsh in warfare==
Secure communications are often difficult to achieve in wartime.  [[Cryptography]] can be used to protect messages, but codes can be broken. Therefore, little-known languages are sometimes encoded, so that even if the code is broken, the message is still in a language few people know. For example, [[Navajo language|Navajo]] [[code talker]]s were used by the [[Military of the United States|United States military]] during [[World War II]]. Similarly, the [[Royal Welch Fusiliers]], a Welsh regiment serving in [[Bosnia and Herzegovina|Bosnia]], used Welsh for emergency communications that needed to be secure.&lt;ref&gt;{{cite news | last = Heath | first = Tony | title = Welsh speak up for their ancient tongue|work = [[The Independent]] | pages = 6 | date = 1996-08-26}}&lt;/ref&gt;

During the 1982 [[Falklands War]] between [[Argentina]] and the United Kingdom, there were stories of British soldiers speaking Welsh with captured Argentinian soldiers who were descendants of [[Welsh settlement in Argentina|Welsh immigrants to the Chubut Valley]] in [[Patagonia]].{{Fact|date=February 2007}}

==Welsh in popular culture==
In the summer of 2006, [[List of Big Brother 2006 housemates (UK)#Glyn|Glyn Wise]] and [[List of Big Brother 2006 housemates (UK)#Imogen|Imogen Thomas]] entered the [[Big Brother UK|Big Brother house]]. These were two fluent Welsh speakers and regularly spoke to each other through the Welsh language. This increased the awareness of the Welsh language dramatically in young people.

==See also==
{{portalpar|Wales}}
*[[Welsh Tract]]
*[[Welsh Bible]]
*[[List of Welsh principal areas by percentage Welsh language]]
*[[Languages in the United Kingdom]]
*[[Welsh Language Board]]
*[[List of Welsh people]]
*[[List of Welsh language authors]]
*[[List of Welsh language poets (6th century to c.1600)]]
*[[Association of Welsh Translators and Interpreters]]
*[[Honourable Society of Cymmrodorion]]
*[[Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch]]

==References==
&lt;references/&gt;

*J.W.Aitchison and H.Carter. ''Language,Economy and Society. The changing fortunes of the Welsh Language in the Twentieth Century''. Cardiff. University of Wales Press. 2000.
*J.W.Aitchison and H.Carter. ''Spreading the Word. The Welsh Language 2001''. Y Lolfa. 2004

==External links==
{{InterWiki|code=cy}}
{{Commonscat|Welsh language}}

===About the language===
*{{ethnologue|code=cym}}
*[http://users.comlab.ox.ac.uk/geraint.jones/about.welsh/ History and status of the Welsh language]
*[http://www.gwybodiadur.co.uk Gwybodiadur: a Welsh informationary]
*[http://www.bbc.co.uk/wales/storyofwelsh The Story of Welsh]: programme details for series from [[BBC Wales]]
*[http://www.cymru.ac.uk/newpages/external/e4106.asp The University of Wales Centre for Advanced Welsh and Celtic Studies]
*[http://www.llgc.org.uk/drych/drych_s088.htm The Blue Books of 1847] — [[National Library of Wales]] Digital Mirror.
*[http://www.summerlands.com/crossroads/celticlanguage/labara4.html A Taste of Welsh Verse]
* [http://www.welshlanguageact.org/ Welsh Language Act website]
* [http://www.deddfiaith.org/ Gwefan Deddf Iaith Newydd]
* [http://news.bbc.co.uk/1/hi/wales/4308262.stm Welsh Scrabble available (BBC News link)]

===Dictionaries===
{{wiktionarylang|code=cy}}
* [http://www.geiriadur.net/ Welsh–English &amp; English-Welsh Dictionary from the University of Wales, Lampeter]
* [http://www.cymru.ac.uk/geiriadur/ {{lang|cy|Geiriadur Prifysgol Cymru}}: University of Wales Dictionary of the Welsh Language], a historical dictionary of Welsh (with a [http://www.cymru.ac.uk/geiriadur/gpc_pdfs.htm second edition] in progress, including an embryonic on-line version)

===Learning the language===
* [http://www.bbc.co.uk/learnwelsh BBC Learn Welsh] 
* [http://www.cs.cf.ac.uk/fun/welsh/ A Welsh Course] by Mark Nodine
* [http://www.clwbmalucachu.co.uk Clwb malu cachu], a website for Welsh learners
* [http://www.learnons4c.co.uk/home.php Learn Welsh with S4C]
* [http://www.swan.ac.uk/dace/e-wlpan/ E-Wlpan, Swansea University]
* [http://www.bangor.ac.uk/ll/database/form_welsh4adults.php.en University of Wales, Bangor - a list of Welsh class venues throughout North West Wales]

{{Spoken Wikipedia|Welsh_language.ogg|2005-05-12}}{{Celtic languages}}

[[Category:Brythonic languages]]
[[Category:Languages of the United Kingdom]]
[[Category:Spoken articles]]
[[Category:Wales|Language]]
[[Category:Welsh culture]]
[[Category:Welsh language|Welsh language]]</text>
      <sha1>qwuaurnw4nf7igvda5cr087up9l1krf</sha1>
    </revision>
  </page>
  <page>
    <title>User:Dr. K~enwikibooks</title>
    <ns>2</ns>
    <id>118587</id>
    <revision>
      <id>4669010</id>
      <parentid>2855011</parentid>
      <timestamp>2026-09-05T19:24:38Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669010</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="990" sha1="djqt902esarfw63wyyy1pgcf898svmv" xml:space="preserve">I made this account after a student telling me about [[Prentice Hall Chemistry]], a book series I have found quite reliable in keeping up with new information.

== Things to do ==
*[[:Category:User templates]] - I have found quite an interest in these userboxes that I have heard about. Since this Wikiproject is fairly new is there another Wikiproject with more userboxes? I will check Wikipedia first it seems that is the main project.


This is a test userbox that I have written in html code to practice

&lt;div style=&quot;float: left; border:solid #FFFF00 1px; margin: 1px;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; style=&quot;width: 238px; background: #FFFF99;{{text default color}};&quot;&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 45px; height: 45px; background: #FFFF00;{{text default color}}; text-align: center; font-size: 14pt;&quot;&gt;
Chem
&lt;/td&gt;
&lt;td style=&quot;font-size: 8pt; padding: 4pt; line-height: 1.25em;&quot;&gt;This user works as a [[w:Chemist|Chemist]] for his [[:Category:Wikibookian chemists|profession]].&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;/div&gt;</text>
      <sha1>djqt902esarfw63wyyy1pgcf898svmv</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:West Brom 4ever~enwikibooks</title>
    <ns>3</ns>
    <id>121707</id>
    <revision>
      <id>4669063</id>
      <parentid>2945181</parentid>
      <timestamp>2026-09-06T06:41:39Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669063</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2981" sha1="e63qxo3qsqole1ifo0mn8zgwikv4hoy" xml:space="preserve">{{{1|Welcome, {{PAGENAME}}!}}}
{| style=&quot;background:white;{{text default color}}; border:1px solid #abd5f5;; padding:0px; border-spacing:0px;&quot;
 ! style=&quot;background:#d0e5f5;{{text default color}};&quot; | [[Wikibooks:Welcome, newcomers|Getting started]] with Wikibooks
 |-
 | style=&quot;padding:5px;&quot; |
* Wikibooks is a collection of open-source textbooks. Find out [[WB:WIW|what this means]].
* To sign your name (on talk pages), use four tildes, like this: &amp;#126;&amp;#126;&amp;#126;&amp;#126; 
* For help in using the wiki, see the [[Help:Editing|editing guide]].
* Explore, [[Wikibooks:Be bold|be bold]], and have fun!
 |}

Come introduce yourself at the [[WB:SLN|new users]] page.  If you have any questions, you can ask there or contact me personally. [[User:West Brom 4ever|West Brom 4ever]] 19:39, 13 May 2007 (UTC)

== Thanks for welcome :) ==

- :) --[[User:Millosh|Millosh]] 18:26, 18 June 2007 (UTC)

== Your account will be renamed ==

&lt;div class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See [[m:Special:MyLanguage/Single User Login finalisation announcement|the announcement]] for more information.

Unfortunately, your account clashes with another account also called West Brom 4ever. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name West Brom 4ever~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can [[Special:GlobalRenameRequest|pick out a different name]].

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours,&lt;br /&gt;[[m:User:Keegan (WMF)|Keegan Peterzell]]&lt;br /&gt;Community Liaison, Wikimedia Foundation
&lt;/div&gt; 23:51, 17 March 2015 (UTC)
&lt;!-- SUL finalisation notification --&gt;

== Renamed ==

&lt;div class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;
This account has been renamed as part of [[m:Special:MyLanguage/Single User Login finalisation announcement|single-user login finalisation]]. If you own this account you can [[{{#special:userlogin}}|log in using your previous username and password]] for more information. If you do not like this account's new name, you can choose your own using this form after logging in: [[{{#special:GlobalRenameRequest}}]]. -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User talk:Keegan (WMF)|talk]])
&lt;/div&gt; 05:38, 19 April 2015 (UTC)
&lt;!-- SUL post-rename notification --&gt;</text>
      <sha1>e63qxo3qsqole1ifo0mn8zgwikv4hoy</sha1>
    </revision>
  </page>
  <page>
    <title>Abstract Algebra/Quaternions</title>
    <ns>0</ns>
    <id>123378</id>
    <revision>
      <id>4669024</id>
      <parentid>4668488</parentid>
      <timestamp>2026-09-05T22:12:37Z</timestamp>
      <contributor>
        <username>Rgdboer</username>
        <id>1021217</id>
      </contributor>
      <minor />
      <comment>/* Historic instances */ copyedit</comment>
      <origin>4669024</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17595" sha1="1up5vsd5sg7b12xtvsaaj4n4eajbmqs" xml:space="preserve">{{TOC right}}
The algebra of '''Quaternions''' is a structure first studied by the Irish mathematician [[w:en:William Rowan Hamilton|William Rowan Hamilton]] which extends the two-dimensional complex numbers to four dimensions.  Multiplication is non-commutative in quaternions, a feature which enables its representation of three-dimensional rotation. Hamilton's provocative discovery of quaternions founded the field of [[Abstract Algebra/Hypercomplex numbers|hypercomplex numbers]]. Suggestive methods like dot products and cross products implicit in quaternion products enabled algebraic description of geometry now widely applied in science and engineering.

==Definitions==
[[File:Inscription on Broom Bridge (Dublin) regarding the discovery of Quaternions multiplication by Sir William Rowan Hamilton.jpg|right|thumb|Quaternion plaque on Broom Bridge, Dublin, which says: 
{{center/top}}
Here as he walked by&lt;br&gt;on the 16th of October 1843&lt;br&gt;Sir William Rowan Hamilton&lt;br&gt;in a flash of genius discovered&lt;br&gt;the fundamental formula for&lt;br&gt;quaternion multiplication 
{{math|1=''i''&lt;sup&gt;2&lt;/sup&gt; = ''j''&lt;sup&gt;2&lt;/sup&gt; = ''k''&lt;sup&gt;2&lt;/sup&gt; = ''ijk'' = −1}} &amp; cut it on a stone of this bridge
{{center/end}}
]]


A '''Quaternion''' corresponds to an ordered 4-tuple &lt;math&gt;q=(a,b,c,d)&lt;/math&gt;, where &lt;math&gt;a,b,c,d\in\mathbb{R}&lt;/math&gt;. A quaternion is denoted &lt;math&gt;q=a + b i + c j + d k&lt;/math&gt;. The sum &lt;math&gt; b i + c j + d k&lt;/math&gt; is called the '''vector part''' of ''q'', and ''a'' is the '''real part'''. Hamilton coined the term ''vector'' in this context. Subsequent developments have extended the usage of the term ''vector'' to any element of a linear space. The vectors in H form a 3-dimensional subspace ''V''.

The set of all quaternions is denoted by &lt;math&gt;\mathbb{H}&lt;/math&gt;. It is straightforward to define component-wise addition and scalar multiplication on &lt;math&gt;\mathbb{H}&lt;/math&gt;, making it a [[Abstract Algebra/Vector Spaces|real vector space]].

Multiplication follows the rules of the &quot;quaternion group&quot; Q&lt;sub&gt;8&lt;/sub&gt; = {1, -1, i, -i, j, -j, k, -k} that Hamilton carved into a stone of Broom Bridge, Dublin:

:&lt;math&gt;i^2 = j^2 = k^2 = ijk = -1&lt;/math&gt;

The rules for the pairwise multiplication of &lt;math&gt;i&lt;/math&gt;, &lt;math&gt;j&lt;/math&gt;, and &lt;math&gt;k&lt;/math&gt; are:

:&lt;math&gt; ij=k,\ \ jk=i,\ \ ki=j &lt;/math&gt; (positive cyclic products)

:&lt;math&gt;ji=-k,\ \ kj=-i,\ \ ik=-j&lt;/math&gt; (negative cyclic products).

Using these, one can define a general rule for multiplication of quaternions. Because quaternion multiplication is ''not'' commutative, &lt;math&gt;\mathbb{H}&lt;/math&gt; is a ''not'' a field. However, every nonzero quaternion has a multiplicative inverse (see below), so the quaternions are an example of a '''division ring'''. It is important to note that the non-commutative nature of quaternion multiplication makes it impossible to define the quotient &lt;math&gt;p/q&lt;/math&gt; of two quaternions ''p'' and ''q'' unambiguously, as the quantities &lt;math&gt;pq^{-1}&lt;/math&gt; and &lt;math&gt;q^{-1}p&lt;/math&gt; are generally different.

Like the more familiar complex numbers, the quaternions have a '''conjugation''', often denoted by a superscript star: &lt;math&gt;q^*&lt;/math&gt;. The conjugate of the quaternion &lt;math&gt;q=a+bi+cj+dk&lt;/math&gt; is &lt;math&gt;q^*=a-bi-cj-dk&lt;/math&gt;. As is the case for the complex numbers, the product &lt;math&gt;qq^*&lt;/math&gt; is always a positive real number equal to the sum of the squares of the quaternion's components. The '''norm ''' of a quaternion is the square root of  &lt;math&gt;qq^*&lt;/math&gt;.

If ''pq'' is the product of two quaternions, then &lt;math&gt;(pq)(pq)^* = (p p^*)(q q^*),&lt;/math&gt; implying that &lt;math&gt;\mathbb{H}&lt;/math&gt; forms a [[Associative Composition Algebra|composition algebra]].

The multiplicative inverse of a non-zero quaternion &lt;math&gt;q&lt;/math&gt; is given by
 
:&lt;math&gt;q^{-1}=\frac{q^*}{qq^*}&lt;/math&gt; where division is defined since &lt;math&gt;qq^* \ne 0.&lt;/math&gt; 

Unlike in the complex case, the conjugate &lt;math&gt;q^*&lt;/math&gt; of a quaternion &lt;math&gt;q&lt;/math&gt; can be computed algebraically:

:&lt;math&gt;q^*=-\frac{1}{2}(q+iqi+jqj+kqk)&lt;/math&gt;.

==Versors and elliptic space==
William Kingdon Clifford used Hamilton’s quaternions to explicate rotation geometry as an elliptic space with its own variety of lines, parallels, and surfaces. The ideas were reviewed in 1948 by Lemaitre and Coxeter and that sketch has these definitions:

A '''versor''' is a quaternion of norm one, thus it lies on a 3-dimensional sphere found in the 4-space of quaternions. The versors are given by Euler's formula for complex numbers where the imaginary unit is taken from the unit sphere in the 3-space of vector quaternions:
:&lt;math&gt;v = \cos c + s \sin c = e^{cs} , \ \ s^2 = -1 .&lt;/math&gt;

The '''distance''' between two versors ''u'' and ''v'' is &lt;math&gt;d(u,v) = \arccos (u v^* + v u^*)/2 .&lt;/math&gt;

A '''right parataxy''' on elliptic space is effected by multiplying on the right by a versor &lt;math&gt;v = e^{cs} .&lt;/math&gt; Similarly a '''left parataxy''' arises from left multiplication. In recognition of his contribution to elliptic geometry, a parataxy is called a ''Clifford translation''.

The '''general displacement''' of elliptic space is a combination of two parataxies, one left, one right:&lt;math&gt;x \mapsto u x v .&lt;/math&gt; Note that if &lt;math&gt;u = v^* ,&lt;/math&gt; then the real line in the quaternions is fixed and the displacement is a rotation of the 3-space of quaternion vectors.

The term '''line''' is appropriated for elliptic geometry. These lines are ''not'' straight, but they are parametrized by real numbers. Each line is associated with a '''right versor''' like ''s'' when ''c'' = &amp;pi;/2 in ''v''. Then &lt;math&gt;L = \{ e^{cs} : c \in R \}&lt;/math&gt; is a typical elliptic line. It corresponds to the axis of the rotation
:&lt;math&gt;x \mapsto e^{cs} x e^{-cx} .&lt;/math&gt;

Now for ''u'' not on ''L'', there are two '''Clifford parallels''' to ''L'' through ''u'': 
:&lt;math&gt;\{u e^{cs} : c \in R \}, \quad \{e^{cs} u : c \in R \} .&lt;/math&gt;
For fixed right versors ''r'' and ''s'', a Clifford surface can be formed as a union of Clifford parallels or as
:&lt;math&gt;\{ e^{cs} e^{dr} : b, c \in R \} .&lt;/math&gt;
To form elliptic space from versors, two versors ''u'' and ''v'' are equivalent if ''u'' + ''v'' = 0. Modulo this equivalence, the versors, their algebra and geometry, represent elliptic space.

==Linear viewpoint==
Quaternions may be represented by 2×2 matrices with complex number entries: the place of &lt;math&gt;i, j, k &lt;/math&gt; is taken by these arrays:
:&lt;math&gt;\begin{pmatrix} i &amp; 0 \\ 0 &amp; -i \end{pmatrix}, \quad \begin{pmatrix} 0 &amp; 1 \\ -1 &amp; 0 \end{pmatrix}, \quad \begin{pmatrix} 0 &amp; i \\ i &amp; 0 \end{pmatrix}.&lt;/math&gt;
One uses matrix multiplication to verify that these expressions obey the rules of presentation of Q&lt;sub&gt;8&lt;/sub&gt;. 

M(2,C) denotes the full algebra of 2×2 complex matrices, which has eight real dimensions, and sustains a representation of &lt;math&gt;\mathbb{H}&lt;/math&gt; as a four-dimensional subalgebra. The linear properties of &lt;math&gt;\mathbb{H}&lt;/math&gt; and M(2,C) assure the fidelity of the representation once the copy of Q&lt;sub&gt;8&lt;/sub&gt; has been identified.

Quaternions, like other associative hypercomplex systems of the 19th century, eventually were viewed as matrix algebras in the 20th century. However, in 1853 Hamilton included biquaternions in his book of ''Lectures on Quaternions''. 

'''Biquaternions''' are quaternions with complex number coefficients, sometimes called ''complex quaternions''. Biquaternions form an algebra isomorphic to M(2,C). If the rows or columns of a matrix are proportional, then the [[Linear Algebra/Definition of Determinant|determinant]] is zero, and there is no inverse. Nevertheless, such matrices have been used in physical science to represent events on a light-path from the origin. Authors Silberstein and Lanczos refer to this algebra as the biquaternions, but other writers have abandoned the label: Elie Cartan used M(2,C) extensively in ''The Theory of Spinors'' (1938), and Wolfgang Pauli, in his matrix mechanics of the atom, caused himself to be associated with M(2,C). 

===Pauli Spin Matrices===
Quaternions are closely related to the Pauli spin matrices of Quantum Mechanics. The Pauli matrices are often denoted as&lt;br /&gt;
:&lt;math&gt;\sigma_1=\begin{pmatrix}0 &amp; 1 \\ 1 &amp; 0\end{pmatrix}&lt;/math&gt; , &lt;math&gt;\sigma_2=\begin{pmatrix}0 &amp; -i \\ i &amp; 0\end{pmatrix}&lt;/math&gt; , &lt;math&gt;\sigma_3=\begin{pmatrix}1 &amp; 0 \\ 0 &amp; -1\end{pmatrix}&lt;/math&gt;

(Where &lt;math&gt;i&lt;/math&gt; is the well known quantity &lt;math&gt;\sqrt{-1}&lt;/math&gt; of complex numbers)

The 2×2 identity matrix is sometimes taken as &lt;math&gt;\sigma_0&lt;/math&gt;.

Thus &lt;math&gt;S&lt;/math&gt;, the real linear span of the matrices &lt;math&gt;\sigma_0&lt;/math&gt;, &lt;math&gt;i\sigma_1&lt;/math&gt;, &lt;math&gt;i\sigma_2&lt;/math&gt; and &lt;math&gt;i\sigma_3&lt;/math&gt;, is isomorphic to &lt;math&gt;\mathbb{H}&lt;/math&gt;. For example, take this matrix product:

:&lt;math&gt;\begin{pmatrix}i &amp; 0 \\ 0 &amp; -i\end{pmatrix} \begin{pmatrix}0 &amp; 1 \\ -1 &amp; 0\end{pmatrix} = \begin{pmatrix}0 &amp; i \\ i &amp; 0\end{pmatrix}&lt;/math&gt;

Or, equivalently, &amp;nbsp; &lt;math&gt;i\sigma_3 \ i\sigma_2 = i\sigma_1 .&lt;/math&gt;

All three of these matrices square to the negative of the identity matrix. If we take &lt;math&gt; 1=\sigma_0&lt;/math&gt;, &lt;math&gt;i=i\sigma_3&lt;/math&gt;, &lt;math&gt;j=i\sigma_2&lt;/math&gt;, and &lt;math&gt;k=i\sigma_1&lt;/math&gt;, it is easy to see that the span of the these four matrices is &quot;the same as&quot; (that is, isomorphic to) the set of quaternions &lt;math&gt;\mathbb{H}&lt;/math&gt;.

==Exercises==
# Using the presentation equations of Q&lt;sub&gt;8&lt;/sub&gt;, write out the full product of two quaternions. In other words, given &lt;math&gt;q_1=a_1+b_1i+c_1j+d_1k&lt;/math&gt; and &lt;math&gt;q_2=a_2+b_2i+c_2j+d_2k&lt;/math&gt;, find the components of their product &lt;math&gt;q=q_1q_2 .&lt;/math&gt;
# Show the composition algebra property &lt;math&gt;(pq)(pq)^* = (p p^*) (q q^*) .&lt;/math&gt; Hint: use [[w: Euler's four-square identity]].

==Axial pencils==
[[File:Sheaf_of_Planes.gif|thumb|right|250px|The axis of a pencil is the real axis in the 4-algebra]]
Hamilton's quaternions provide a picture of a pencil of complex number planes that fill out his hyperspace. Another pair of pencils provide alternative descriptions of 4-space as made up of planar algebras:
The hyperspace is &lt;math&gt;\reals^4&lt;/math&gt; with the first coordinate taken as the real line, and as the axis of the various pencils. The Hamilton case uses the sphere of imaginary units
:&lt;math&gt;S^2 = \{q \in H : q^2 = -1 \} = \{xi + yj + zk : x^2 + y^2 + z^2 = 1 \} .&lt;/math&gt;
Any pair of antipodal points on this sphere generates a plane isomorphic to the ordinary complex plane &lt;math&gt;\Complex .&lt;/math&gt;

The second and third pencils derive from the findings of James Cockle and Arthur Cayley. Cayley set up an arithmetic of matrix multiplication which has expedited modern science. For instance, the so-called imaginary units are represented by &lt;math&gt;\begin{pmatrix}0 &amp; -1 \\ 1 &amp; 0 \end{pmatrix}&lt;/math&gt; which has multiplicative square equal to the negative of the identity matrix. But then there is also by &lt;math&gt;\begin{pmatrix}0 &amp; 1 \\ 1 &amp; 0 \end{pmatrix}&lt;/math&gt; which generates an algebraic plane distinct from ordinary complex numbers. This algebra [[Associative Composition Algebra/Split-binarions|split-binarions]], has inverse proportion included as a structural feature, such as found in economics or spacetime. In fact, the Lorentz boost is exhibited by a split-binarion multiplication. The inherent relation was recognized in the 19th century by J. Cockle, W.K. Clifford, and A. Macfarlane in the English world and by some Serbians.

The second pencil is an imaginary one without linear representation. As Hamilton had a sphere of imaginary units, Macfarlane would have a sphere of hyperbolic units ''u'' with ''u''&lt;sup&gt;2&lt;/sup&gt; = +1. The full algebra of split-binarions is &lt;math&gt;A = \{ q = x + y u : x, y \in \reals \}&lt;/math&gt; Any pair of elements that are polar opposite on this sphere generate a plane isomorphic to the split-binarions A. The 4-algebra containing this pencil is the '''hyperbolic quaternion''' algebra. As Oliver Heaviside and Willard Gibbs advocated a positive dot product for vectors, they have been associated with hyperbolic quaternions. When this algebra drew attention in the 1890s a &quot;great vector debate&quot; ensued in various publications including ''Nature''. When the failure of the algebra to satisfy the associative law of multiplication was noted, it was realized that no matrix representation would be found. 

Each plane of the pencil can represent a Lorentz boost. However, rotations of the vector subspace, an operation within the reach of Hamilton's structure, is beyond the means of hyperbolic quaternions, hence the Lorentz group cannot be represented with Macfarlane's algebra.

The third pencil arises from both imaginary units and hyperbolic units as found in the ring of [[Abstract Algebra/2x2 real matrices|2x2 real matrices]]. In this figure there must be noted nilpotent matrices such as by 
&lt;math&gt;\begin{pmatrix}0 &amp; 1 \\ 0 &amp; 0 \end{pmatrix}&lt;/math&gt; which correspond to [[Abstract Algebra/Shear and Slope|dual numbers]] in the matrix algebra. Such planes separate the complex and split-binarion planes, and are included in the pencil. The axis of the pencil is the line of matrices that are real multiples of the identity matrix. Over an alternate basis this ring is known as [[Associative Composition Algebra/Split-quaternions|split-quaternions]], and the pencil has three types of planar subrings.

== Quaternion algebras ==
The real numbers are part of Hamilton's quaternions. An objective of abstract algebra is to show algebraic structures in their most general form. The real numbers satisfy the axioms of a field and they have other properties such as order and completeness. Given an arbitrary [[Abstract Algebra/Fields|field]] ''F'', it can be associated with an abstract algebra called a ''quaternion algebra'' as follows:

The elements of a quaternion algebra are in the four-dimensional space over ''F'' : &amp;nbsp;''V'' = ''F''&lt;sup&gt; 4&lt;/sup&gt;. As in ''F'', there is a multiplicative identity 1 in ''V'', and hence a one-dimensional subspace &lt;math&gt;F \cdot 1.&lt;/math&gt; The multiplication &lt;math&gt;\times&lt;/math&gt; on ''V'' has the feature that basis vectors of the orthogonal complement of &lt;math&gt;F \cdot 1&lt;/math&gt; in ''V'' are anticommutative.

More particularly, with i and j  perpendicular in this orthogonal complement of &lt;math&gt;F \cdot 1&lt;/math&gt;, i j = &amp;minus; j i. With k = i j, and perpendicular to the plane of i and j, associativity of multiplication implies jk  = j i j = &amp;minus; i j j = &amp;minus;k j, and k i = i j i = &amp;minus;i k, so k also anticommutes with i and j. 

The multiplication on ''V'' is determined by multiplication on its basis vectors. That multiplication is not commutative (due to anticommutivity) and includes the negative for each basis vector: &lt;math&gt;B = \{ 1, -1, i, -i, j, -j, k, -k \} \subset V .&lt;/math&gt;  There are only two non-commutative groups of order eight: the quaternion group Q&lt;sub&gt;8&lt;/sub&gt; and the dihedral group of symmetries of a square figure D&lt;sub&gt;4&lt;/sub&gt;. Thus, for any field ''F'', there are two quaternion algebras over ''F'' corresponding to the selection of multiplication on ''B'' according to Q&lt;sub&gt;8&lt;/sub&gt; or D&lt;sub&gt;4&lt;/sub&gt;.

=== Historic incidents ===
There was a glitch in an early presentation, with ''F'' being the field of real numbers, and the basis group confused. 
In 1878 [[w:W. K. Clifford]] nearly described representation of split-quaternions with matrices:&lt;ref&gt;[[w:W. K. Clifford]] (1878) [https://archive.org/details/elementsofdynami01clifiala/page/170/mode/2up ''Elements of Dynamic''], page 170 via Internet Archive&lt;/ref&gt; He used ''K'' to express the imaginary unit &lt;math&gt;\begin{pmatrix}0 &amp; 1 \\ -1 &amp; 0 \end{pmatrix}&lt;/math&gt;. The only flaw was a missing minus sign in the equation
:&lt;math&gt;J K  = \begin{pmatrix}0 &amp; 1 \\ 1 &amp; 0 \end{pmatrix} \begin{pmatrix}0 &amp; 1 \\ -1 &amp; 0 \end{pmatrix} = \begin{pmatrix}-1 &amp; 0 \\  0 &amp; 1 \end{pmatrix} = -I .&lt;/math&gt;

The inexplicable mistake in a case of a finite subgroup of the general linear group hindered understanding.
Some clarity followed from a letter to the editor from [[w:C. G. Knott]]&lt;ref&gt;{{cite journal |first=C.G. |last=Knott |title=Recent Innovations in Vector Theory |journal=Nature |volume=47 |issue=1225 |pages=590–3 |year=1893 |doi=10.1038/047590b0 |bibcode=1893Natur..47R.590. |doi-access=free }} read before the Royal Society of Edinburgh 19 December 1892 and published in ''Proceedings''&lt;/ref&gt; 1892) He reaffirmed Hamilton's products in this proposition:
:If a 4-algebra on basis &lt;math&gt;\{1,\,i,\,j,\,k\}&lt;/math&gt; is associative and off-diagonal products are given by Hamilton's rules, then &lt;math&gt;i^2=-\!1=j^2=k^2&lt;/math&gt;.
'''Proof:'''
:&lt;math&gt;j = ki = (-ji)i = -j(ii)&lt;/math&gt;, so &lt;math&gt;i^2 = -1&lt;/math&gt;. Cycle the letters &lt;math&gt;i&lt;/math&gt;, &lt;math&gt;j&lt;/math&gt;, &lt;math&gt;k&lt;/math&gt; to obtain &lt;math&gt;i^2=-1=j^2=k^2&lt;/math&gt;.

An other hitch is the notion of isomorphism of algebras, which should include preserving the field ''F''. Here [[w:Leonard Dickson]] ventured to nullify the difference between the complex algebras ( ''F'' = '''C''' ) over the two basis groups Q&lt;sub&gt;8&lt;/sub&gt; and D&lt;sub&gt;4&lt;/sub&gt;.
He wrote in ''Linear Algebras''&lt;ref&gt;Leonard Dickson (1915) [https://archive.org/details/cu31924001557515/page/n25/mode/2up?q=quaternion Equivalence of complex quaternion and matric algebras], ''Linear Algebras'', page 15&lt;/ref&gt; that the complex quaternion and matric algebras were equivalent. There is a real isomorphism between them, but that is not a complex isomorphism preserving the field. Nevertheless, Dickson was one of the first to acknowledge the existence of a four-dimensional, real subalgebra of M(2,'''C''') other than quaternions.

== References ==
{{Reflist}}


{{Subject|Abstract Algebra}}</text>
      <sha1>1up5vsd5sg7b12xtvsaaj4n4eajbmqs</sha1>
    </revision>
  </page>
  <page>
    <title>User:Jomegat/Sandbox/Knot</title>
    <ns>2</ns>
    <id>125983</id>
    <revision>
      <id>4669005</id>
      <parentid>904049</parentid>
      <timestamp>2026-09-05T19:21:30Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669005</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="771" sha1="5khd7kcm9t61udzt1jby7j7u7aeiq91" xml:space="preserve">{| style=&quot;position:relative; margin: 0 0 0.5em 1em; border-collapse: collapse; float:right; background:white;{{text default color}}; clear:right; width:100%;&quot; border=&quot;1&quot; cellpadding=&quot;2&quot;
|- style=&quot;text-align:center;&quot;
! style=&quot;background: tan;{{text default color}};&quot;|{{{name}}}
|-
| {{#if:{{{image|}}}|[[image:{{{image}}}|thumb|{{{image_width|250px}}}|{{{image_caption|}}}]]}}
{{#if:{{{image2|}}}|[[image:{{{image2}}}|thumb|{{{image2_width|250px}}}|{{{image2_caption|}}}]]}}
{{#if:{{{use|}}}|&lt;br&gt;&lt;div style=&quot;text-align:left&quot;&gt;'''Use:''' {{{use}}}&lt;/div&gt;}}
{{#if:{{{tying_instructions|}}}|&lt;br&gt;&lt;div style=&quot;text-align:left&quot;&gt;'''How to tie:'''
&lt;br&gt; 
{{{tying_instructions}}}&lt;/div&gt;}}
{{#if:{{{warnings|}}}|&lt;br&gt;&lt;div style=&quot;text-align:left&quot;&gt; '''WARNING:''' {{{warnings}}}&lt;/div&gt;}}
|}</text>
      <sha1>5khd7kcm9t61udzt1jby7j7u7aeiq91</sha1>
    </revision>
  </page>
  <page>
    <title>General Chemistry</title>
    <ns>0</ns>
    <id>129154</id>
    <revision>
      <id>4668987</id>
      <parentid>4666435</parentid>
      <timestamp>2026-09-05T18:53:25Z</timestamp>
      <contributor>
        <username>~2026-48412-47</username>
        <id>3625259</id>
      </contributor>
      <comment>Undid revision [[Special:Diff/4666435|4666435]] by [[Special:Contributions/~2026-47545-99|~2026-47545-99]] ([[User talk:~2026-47545-99|discuss]])</comment>
      <origin>4668987</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2031" sha1="o85png9wwz6zb2gofzae9vonckzkgdi" xml:space="preserve">{{DISPLAYTITLE:&lt;span style=&quot;display:block;text-align:center;font-size:250%;font-style:italic;line-height:1em;&quot;&gt;General Chemistry&lt;/span&gt;}}
Welcome to the '''''General Chemistry''''' wikibook. In this wikibook, you will be introduced to various aspects of general chemistry such as changes in matter and elements.
== Contents ==
[[File:F4M0.png|300px|thumb|A three-dimensional representation of a 4f orbital]]
{{Print version}}
{{PDF version|GeneralChemistry}}
{{Book Search|prefix=General Chemistry}}
[[/Introduction/]]
{{:General Chemistry/Properties of Matter}}
{{:General Chemistry/Atomic Structure}}
{{:General Chemistry/Compounds and Bonding}}
{{:General Chemistry/Chemical Reactions}}
{{:General Chemistry/Aqueous Solutions}}
{{:General Chemistry/Phases of Matter}}
{{:General Chemistry/Chemical Equilibria}}
{{:General Chemistry/Chemical Kinetics}}
{{:General Chemistry/Thermodynamics}}
{{:General Chemistry/Chemistries of Various Elements}}

=== Appendices ===
# [[File:100%.svg]] [[/Periodic Table/]]
# [[File:100%.svg]] [[/Units/]]
# [[Image:75%.svg]] [[/Constants/]]
# [[Image:50%.svg]] [[/Useful Equations/]]
# [[File:100%.svg]] [[/Standard Reduction Potentials/]]
# [[File:100%.svg]] [[/Table of the Chemical Elements and their Properties/]]
# [[Image:25%.svg]] [[/Review Questions/]]

== External Resources ==
*[http://www.chemmybear.com Chemmybear.com] Tons of info, pictures, and study flashcards.
*[http://micvac.dichi.unina.it Chemistry Problems 1.0] Free educational software for General Chemistry
*[http://www.freeuniv.com/lect/chempage.html Free University Project: General Chemistry]

== Wikibook Administration ==
# [[/Book Structure/]]
# [[/Book Cover/]]
# [[/Orphaned Pages/]]

__NOTOC__ __NOEDITSECTION__
{{Shelves|Chemistry}}
{{alphabetical|G}}
{{status|75%}}

[[de:Allgemeine und Anorganische Chemie]]
[[el:Γενική και Ανόργανη Χημεία]]
[[fr:Chimie générale]]
[[id:Kimia Dasar]]
[[it:Chimica generale]]
[[nl:Chemie Centraal]]
[[pl:Chemia dla liceum/Okładka]]
[[fi:Yleinen kemia]]</text>
      <sha1>o85png9wwz6zb2gofzae9vonckzkgdi</sha1>
    </revision>
  </page>
  <page>
    <title>User:MiszaBot</title>
    <ns>2</ns>
    <id>136191</id>
    <revision>
      <id>4669009</id>
      <parentid>3278453</parentid>
      <timestamp>2026-09-05T19:24:08Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669009</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="365" sha1="rutm4enou33vqzd6rh5tjlkna5lao82" xml:space="preserve">{{bot|Misza13|status=approved}}

{| style=&quot;text-align:center; background:yellowgreen;{{text default color}};border:1px solid gray; text-align:center; width:75%; font-size:150%; padding:5px;&quot;
 | [[w:en:User:MiszaBot/Archive HowTo|&lt;span style=&quot;color:darkslategray&quot;&gt;Click here to read how to set up automated archiving of a page. Takes you to enwikipedia.&lt;/span&gt;]]
 |}</text>
      <sha1>rutm4enou33vqzd6rh5tjlkna5lao82</sha1>
    </revision>
  </page>
  <page>
    <title>User:Kriswarry</title>
    <ns>2</ns>
    <id>136798</id>
    <revision>
      <id>4668992</id>
      <parentid>4644387</parentid>
      <timestamp>2026-09-05T19:04:34Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668992</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1006" sha1="j6k7glor2ozw5t4y9w4id4p1lgao2oj" xml:space="preserve">{{{1|Welcome, {{PAGENAME}}!}}}
{| style=&quot;background:white;{{Text default color}}; border:1px solid #abd5f5;; padding:0px; border-spacing:0px;&quot;
 ! style=&quot;background:#d0e5f5;{{Text default color}};&quot; | [[Wikibooks:Welcome, newcomers|Getting started]] with Wikibooks
 |-
 | style=&quot;padding:5px;&quot; |
* Wikibooks is a collection of open-source textbooks. Find out [[WB:WIW|what this means]].
* To sign your name (on talk pages), use four tildes, like this: &amp;#126;&amp;#126;&amp;#126;&amp;#126; 
* For help in using the wiki, see the [[Help:Editing|editing guide]].
* Explore, [[Wikibooks:Be bold|be bold]], and have fun!
 |}

Come introduce yourself at the [[WB:SLN|new users]] page.  If you have any questions, you can ask there or contact me personally. [[User:Urbane|&lt;span style=&quot;color: black;&quot;&gt;&lt;b&gt;Urbane&lt;/b&gt;&lt;/span&gt;]] [[User talk:Urbane|&lt;span style=&quot;color: green;&quot;&gt;&lt;small&gt;(Talk)&lt;/small&gt;&lt;/span&gt;]] [[Special:Contributions/Urbane|&lt;span style=&quot;color: green;&quot;&gt;&lt;small&gt;(Contributions)&lt;/small&gt;&lt;/span&gt;]] 20:30, 13 October 2007 (UTC)</text>
      <sha1>j6k7glor2ozw5t4y9w4id4p1lgao2oj</sha1>
    </revision>
  </page>
  <page>
    <title>User:Aquillyne</title>
    <ns>2</ns>
    <id>139604</id>
    <revision>
      <id>4669017</id>
      <parentid>1026759</parentid>
      <timestamp>2026-09-05T19:32:12Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669017</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="380" sha1="enptfhscc8y0dl4rsy98mezbpdbu2qt" xml:space="preserve">&lt;div style=&quot;border: 2px solid #49f; background: #eefcff;{{Text default color}}; margin: auto 0em 1em 0em; padding: 0.8em; font-family: Verdana, Tahoma, Sans-Serif; font-size: 98%&quot;&gt;'''[[wikipedia:User talk:Aquillyne|Please contact me via my talk page on the English Wikipedia]], where I usually contribute.&lt;br /&gt;Messages left here will go unanswered for some time. Thanks.'''&lt;/div&gt;</text>
      <sha1>enptfhscc8y0dl4rsy98mezbpdbu2qt</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Reading room/Administrative Assistance</title>
    <ns>4</ns>
    <id>140081</id>
    <revision>
      <id>4669059</id>
      <parentid>4668705</parentid>
      <timestamp>2026-09-06T06:39:58Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Reporting Reazulkarim545456</comment>
      <origin>4669059</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="11515" sha1="0rdrzyvpvffmga9jfbx6j43stvdglh0" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{shortcut|WB:AN|WB:AA}} {{TOC left}}
{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Administrative Assistance/Archives/%(year)d/%(monthname)s
|algo = old(14d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{ombox|type=content|text='''To request a rename or usurpation''', go to the global request page at Meta [[meta:SRUC|here]].&lt;br /&gt;''Please do not post those requests here!''}}
{{Clear}}
Welcome to the '''Administrative Assistance reading room'''.  You can request assistance from [[WB:ADMIN|administrators]] for handling a variety of problems here and alert them about problems which may require special actions not normally used during regular content editing. Please be patient as administrators are often quite busy with either their own projects or trying to perform general maintenance and cleanup.

You can deal with most vandalism yourself: [[Wikibooks:Dealing with vandalism|fix it]], then [[Wikibooks:Templates/User_notices|warn the user]]. If there is repeated vandalism by one user, lots of vandalism on a single page, or vandalism from many users, tell an admin here, or in [irc://irc.freenode.net/wikibooks #wikibooks] (say &lt;code&gt;!admin&lt;/code&gt; to get attention).

For more general questions and assistance that doesn't require an administrator, please use the [[WB:HELP|Assistance Reading Room]].
{{clear}}

[[Category:Reading room]]

== IntoAEC reported by MathXplore ==

* {{userlinks|IntoAEC}}

Spam &lt;!-- USERREPORTED:/IntoAEC/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:25, 19 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:27, 26 August 2026 (UTC)

== CaribbeanMedicalSchools reported by MathXplore ==

* {{userlinks|CaribbeanMedicalSchools}}

Spam &lt;!-- USERREPORTED:/CaribbeanMedicalSchools/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:16, 26 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:27, 26 August 2026 (UTC)
== Chzoraiz41 reported by MathXplore ==

* {{userlinks|Chzoraiz41}}

Link spam, [[Special:AbuseLog/315229]] &lt;!-- USERREPORTED:/Chzoraiz41/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:09, 27 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:17, 27 August 2026 (UTC)
== Gloriagulshan reported by MathXplore ==

* {{userlinks|Gloriagulshan}}

[[:w:Wikipedia:Sockpuppet investigations/Kagoz]] ([[Special:Contributions/Tikapara]], [[Wikibooks:Reading_room/Administrative_Assistance/Archives/2025/September#Tikapara_reported_by_MathXplore]]), created page [[Introduction to Filmmaking]] Contributed by Ali Zulfikar Zahedi ([[:w:Ali Zulfikar Zahedi]], [[:w:simple:Ali Zulfikar Zahedi]]) &lt;!-- USERREPORTED:/Gloriagulshan/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 03:56, 29 August 2026 (UTC)

:I believe this page is intended as instructional material for learning filmmaking rather than as an encyclopedic article. I will revise the page to focus on practical filmmaking concepts, methods, and processes in accordance with the purpose of Wikibooks. [[User:Gloriagulshan|Gloriagulshan]] ([[User talk:Gloriagulshan|discuss]] • [[Special:Contributions/Gloriagulshan|contribs]]) 04:20, 29 August 2026 (UTC)
: Cc: {{ping|SHB2000|MarcGarver}} [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 04:41, 29 August 2026 (UTC)
::I see the account is glocked, and there are no sleepers that aren't already locked, so nothing more to do. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 11:18, 3 September 2026 (UTC)

== Atlanticgym reported by MathXplore ==

* {{userlinks|Atlanticgym}}

Link spam, [[Special:AbuseLog/315249]] &lt;!-- USERREPORTED:/Atlanticgym/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:32, 29 August 2026 (UTC)

:{{done}} --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 12:35, 29 August 2026 (UTC)
== Makowe2026 reported by Veritas Sapientiae ==

* {{userlinks|Makowe2026}}

Spam &lt;!-- USERREPORTED:/Makowe2026/ --&gt; [[User:Veritas Sapientiae|Veritas Sapientiae]] ([[User talk:Veritas Sapientiae|discuss]] • [[Special:Contributions/Veritas Sapientiae|contribs]]) 13:53, 29 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:20, 29 August 2026 (UTC)
== Abir077 reported by MathXplore ==

* {{userlinks|Abir077}}

Link spam, [[Special:AbuseLog/315272]] &lt;!-- USERREPORTED:/Abir077/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:07, 31 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:46, 31 August 2026 (UTC)
== Jeevandan26 reported by MathXplore ==

* {{userlinks|Jeevandan26}}
Link spam, [[Special:AbuseLog/315288]] &lt;!-- USERREPORTED:/Jeevandan26/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:14, 1 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:20, 1 September 2026 (UTC)
== Mohansai00116 reported by MathXplore ==
* {{userlinks|Mohansai00116}}

Link spam, [[Special:AbuseLog/315335]] &lt;!-- USERREPORTED:/Mohansai00116/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:09, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:04, 3 September 2026 (UTC)

== Fatemai6 reported by MathXplore ==
* {{userlinks|Fatemai6}}

Link spam, [[Special:AbuseLog/315329]] &lt;!-- USERREPORTED:/Fatemai6/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:10, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Kamrulhasan147 reported by MathXplore ==
* {{userlinks|Kamrulhasan147}}

Link spam, [[Special:AbuseLog/315327]], [[Special:Contributions/Kamrulhasan142]] &lt;!-- USERREPORTED:/Kamrulhasan147/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:12, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Kamrulhasan142 reported by MathXplore ==
* {{userlinks|Kamrulhasan142}}

Link spam, [[Special:AbuseLog/315295]], [[Special:Contributions/Kamrulhasan147]] &lt;!-- USERREPORTED:/Kamrulhasan142/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:13, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Twenty7incgs reported by MathXplore ==
* {{userlinks|Twenty7incgs}}

Link spam, [[Special:AbuseLog/315323]] &lt;!-- USERREPORTED:/Twenty7incgs/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:14, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Tailleash reported by MathXplore ==
* {{userlinks|Tailleash}}

Link spam, [[Special:AbuseLog/315318]] &lt;!-- USERREPORTED:/Tailleash/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:15, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Md Akash Mia12 reported by MathXplore ==
* {{userlinks|Md Akash Mia12}}

Link spam, [[Special:AbuseLog/315299]], [[Special:AbuseLog/315298]] &lt;!-- USERREPORTED:/Md Akash Mia12/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:17, 2 September 2026 (UTC)
: {{done|Page deleted}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:03, 3 September 2026 (UTC)

== Vapesitefiftybar reported by MathXplore ==
* {{userlinks|Vapesitefiftybar}}

Link spam, [[Special:AbuseLog/315338]] &lt;!-- USERREPORTED:/Vapesitefiftybar/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:40, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)
== Myteethtime1 reported by MathXplore ==
* {{userlinks|Myteethtime1}}

Spam &lt;!-- USERREPORTED:/Myteethtime1/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:54, 4 September 2026 (UTC)
: {{Done}} by MarcGarver. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:28, 4 September 2026 (UTC)

== Rajstartupservices reported by MathXplore ==
* {{userlinks|Rajstartupservices}}

Link spam, [[Special:AbuseLog/315363]] &lt;!-- USERREPORTED:/Rajstartupservices/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 14:33, 4 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:28, 4 September 2026 (UTC)
== Reazulkarim545456 reported by MathXplore ==
* {{userlinks|Reazulkarim545456}}

Link spam, [[Special:AbuseLog/315377]] &lt;!-- USERREPORTED:/Reazulkarim545456/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 06:39, 6 September 2026 (UTC)</text>
      <sha1>0rdrzyvpvffmga9jfbx6j43stvdglh0</sha1>
    </revision>
    <revision>
      <id>4669061</id>
      <parentid>4669059</parentid>
      <timestamp>2026-09-06T06:40:58Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Reporting Fahmidafy</comment>
      <origin>4669061</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="11800" sha1="dto2sfehmexeb8jsach8tkz65jci25o" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{shortcut|WB:AN|WB:AA}} {{TOC left}}
{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Administrative Assistance/Archives/%(year)d/%(monthname)s
|algo = old(14d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{ombox|type=content|text='''To request a rename or usurpation''', go to the global request page at Meta [[meta:SRUC|here]].&lt;br /&gt;''Please do not post those requests here!''}}
{{Clear}}
Welcome to the '''Administrative Assistance reading room'''.  You can request assistance from [[WB:ADMIN|administrators]] for handling a variety of problems here and alert them about problems which may require special actions not normally used during regular content editing. Please be patient as administrators are often quite busy with either their own projects or trying to perform general maintenance and cleanup.

You can deal with most vandalism yourself: [[Wikibooks:Dealing with vandalism|fix it]], then [[Wikibooks:Templates/User_notices|warn the user]]. If there is repeated vandalism by one user, lots of vandalism on a single page, or vandalism from many users, tell an admin here, or in [irc://irc.freenode.net/wikibooks #wikibooks] (say &lt;code&gt;!admin&lt;/code&gt; to get attention).

For more general questions and assistance that doesn't require an administrator, please use the [[WB:HELP|Assistance Reading Room]].
{{clear}}

[[Category:Reading room]]

== IntoAEC reported by MathXplore ==

* {{userlinks|IntoAEC}}

Spam &lt;!-- USERREPORTED:/IntoAEC/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:25, 19 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:27, 26 August 2026 (UTC)

== CaribbeanMedicalSchools reported by MathXplore ==

* {{userlinks|CaribbeanMedicalSchools}}

Spam &lt;!-- USERREPORTED:/CaribbeanMedicalSchools/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:16, 26 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:27, 26 August 2026 (UTC)
== Chzoraiz41 reported by MathXplore ==

* {{userlinks|Chzoraiz41}}

Link spam, [[Special:AbuseLog/315229]] &lt;!-- USERREPORTED:/Chzoraiz41/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:09, 27 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:17, 27 August 2026 (UTC)
== Gloriagulshan reported by MathXplore ==

* {{userlinks|Gloriagulshan}}

[[:w:Wikipedia:Sockpuppet investigations/Kagoz]] ([[Special:Contributions/Tikapara]], [[Wikibooks:Reading_room/Administrative_Assistance/Archives/2025/September#Tikapara_reported_by_MathXplore]]), created page [[Introduction to Filmmaking]] Contributed by Ali Zulfikar Zahedi ([[:w:Ali Zulfikar Zahedi]], [[:w:simple:Ali Zulfikar Zahedi]]) &lt;!-- USERREPORTED:/Gloriagulshan/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 03:56, 29 August 2026 (UTC)

:I believe this page is intended as instructional material for learning filmmaking rather than as an encyclopedic article. I will revise the page to focus on practical filmmaking concepts, methods, and processes in accordance with the purpose of Wikibooks. [[User:Gloriagulshan|Gloriagulshan]] ([[User talk:Gloriagulshan|discuss]] • [[Special:Contributions/Gloriagulshan|contribs]]) 04:20, 29 August 2026 (UTC)
: Cc: {{ping|SHB2000|MarcGarver}} [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 04:41, 29 August 2026 (UTC)
::I see the account is glocked, and there are no sleepers that aren't already locked, so nothing more to do. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 11:18, 3 September 2026 (UTC)

== Atlanticgym reported by MathXplore ==

* {{userlinks|Atlanticgym}}

Link spam, [[Special:AbuseLog/315249]] &lt;!-- USERREPORTED:/Atlanticgym/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:32, 29 August 2026 (UTC)

:{{done}} --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 12:35, 29 August 2026 (UTC)
== Makowe2026 reported by Veritas Sapientiae ==

* {{userlinks|Makowe2026}}

Spam &lt;!-- USERREPORTED:/Makowe2026/ --&gt; [[User:Veritas Sapientiae|Veritas Sapientiae]] ([[User talk:Veritas Sapientiae|discuss]] • [[Special:Contributions/Veritas Sapientiae|contribs]]) 13:53, 29 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:20, 29 August 2026 (UTC)
== Abir077 reported by MathXplore ==

* {{userlinks|Abir077}}

Link spam, [[Special:AbuseLog/315272]] &lt;!-- USERREPORTED:/Abir077/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:07, 31 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:46, 31 August 2026 (UTC)
== Jeevandan26 reported by MathXplore ==

* {{userlinks|Jeevandan26}}
Link spam, [[Special:AbuseLog/315288]] &lt;!-- USERREPORTED:/Jeevandan26/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:14, 1 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:20, 1 September 2026 (UTC)
== Mohansai00116 reported by MathXplore ==
* {{userlinks|Mohansai00116}}

Link spam, [[Special:AbuseLog/315335]] &lt;!-- USERREPORTED:/Mohansai00116/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:09, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:04, 3 September 2026 (UTC)

== Fatemai6 reported by MathXplore ==
* {{userlinks|Fatemai6}}

Link spam, [[Special:AbuseLog/315329]] &lt;!-- USERREPORTED:/Fatemai6/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:10, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Kamrulhasan147 reported by MathXplore ==
* {{userlinks|Kamrulhasan147}}

Link spam, [[Special:AbuseLog/315327]], [[Special:Contributions/Kamrulhasan142]] &lt;!-- USERREPORTED:/Kamrulhasan147/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:12, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Kamrulhasan142 reported by MathXplore ==
* {{userlinks|Kamrulhasan142}}

Link spam, [[Special:AbuseLog/315295]], [[Special:Contributions/Kamrulhasan147]] &lt;!-- USERREPORTED:/Kamrulhasan142/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:13, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Twenty7incgs reported by MathXplore ==
* {{userlinks|Twenty7incgs}}

Link spam, [[Special:AbuseLog/315323]] &lt;!-- USERREPORTED:/Twenty7incgs/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:14, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Tailleash reported by MathXplore ==
* {{userlinks|Tailleash}}

Link spam, [[Special:AbuseLog/315318]] &lt;!-- USERREPORTED:/Tailleash/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:15, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Md Akash Mia12 reported by MathXplore ==
* {{userlinks|Md Akash Mia12}}

Link spam, [[Special:AbuseLog/315299]], [[Special:AbuseLog/315298]] &lt;!-- USERREPORTED:/Md Akash Mia12/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:17, 2 September 2026 (UTC)
: {{done|Page deleted}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:03, 3 September 2026 (UTC)

== Vapesitefiftybar reported by MathXplore ==
* {{userlinks|Vapesitefiftybar}}

Link spam, [[Special:AbuseLog/315338]] &lt;!-- USERREPORTED:/Vapesitefiftybar/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:40, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)
== Myteethtime1 reported by MathXplore ==
* {{userlinks|Myteethtime1}}

Spam &lt;!-- USERREPORTED:/Myteethtime1/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:54, 4 September 2026 (UTC)
: {{Done}} by MarcGarver. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:28, 4 September 2026 (UTC)

== Rajstartupservices reported by MathXplore ==
* {{userlinks|Rajstartupservices}}

Link spam, [[Special:AbuseLog/315363]] &lt;!-- USERREPORTED:/Rajstartupservices/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 14:33, 4 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:28, 4 September 2026 (UTC)
== Reazulkarim545456 reported by MathXplore ==
* {{userlinks|Reazulkarim545456}}

Link spam, [[Special:AbuseLog/315377]] &lt;!-- USERREPORTED:/Reazulkarim545456/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 06:39, 6 September 2026 (UTC)
== Fahmidafy reported by MathXplore ==
* {{userlinks|Fahmidafy}}

Link spam, [[Special:AbuseLog/315378]] &lt;!-- USERREPORTED:/Fahmidafy/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 06:40, 6 September 2026 (UTC)</text>
      <sha1>dto2sfehmexeb8jsach8tkz65jci25o</sha1>
    </revision>
    <revision>
      <id>4669064</id>
      <parentid>4669061</parentid>
      <timestamp>2026-09-06T06:42:07Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Reporting Grow spark digital</comment>
      <origin>4669064</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="12112" sha1="5j92ewrtt4xxnom7w8771e730coznju" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{shortcut|WB:AN|WB:AA}} {{TOC left}}
{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Administrative Assistance/Archives/%(year)d/%(monthname)s
|algo = old(14d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{ombox|type=content|text='''To request a rename or usurpation''', go to the global request page at Meta [[meta:SRUC|here]].&lt;br /&gt;''Please do not post those requests here!''}}
{{Clear}}
Welcome to the '''Administrative Assistance reading room'''.  You can request assistance from [[WB:ADMIN|administrators]] for handling a variety of problems here and alert them about problems which may require special actions not normally used during regular content editing. Please be patient as administrators are often quite busy with either their own projects or trying to perform general maintenance and cleanup.

You can deal with most vandalism yourself: [[Wikibooks:Dealing with vandalism|fix it]], then [[Wikibooks:Templates/User_notices|warn the user]]. If there is repeated vandalism by one user, lots of vandalism on a single page, or vandalism from many users, tell an admin here, or in [irc://irc.freenode.net/wikibooks #wikibooks] (say &lt;code&gt;!admin&lt;/code&gt; to get attention).

For more general questions and assistance that doesn't require an administrator, please use the [[WB:HELP|Assistance Reading Room]].
{{clear}}

[[Category:Reading room]]

== IntoAEC reported by MathXplore ==

* {{userlinks|IntoAEC}}

Spam &lt;!-- USERREPORTED:/IntoAEC/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:25, 19 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:27, 26 August 2026 (UTC)

== CaribbeanMedicalSchools reported by MathXplore ==

* {{userlinks|CaribbeanMedicalSchools}}

Spam &lt;!-- USERREPORTED:/CaribbeanMedicalSchools/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:16, 26 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:27, 26 August 2026 (UTC)
== Chzoraiz41 reported by MathXplore ==

* {{userlinks|Chzoraiz41}}

Link spam, [[Special:AbuseLog/315229]] &lt;!-- USERREPORTED:/Chzoraiz41/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:09, 27 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:17, 27 August 2026 (UTC)
== Gloriagulshan reported by MathXplore ==

* {{userlinks|Gloriagulshan}}

[[:w:Wikipedia:Sockpuppet investigations/Kagoz]] ([[Special:Contributions/Tikapara]], [[Wikibooks:Reading_room/Administrative_Assistance/Archives/2025/September#Tikapara_reported_by_MathXplore]]), created page [[Introduction to Filmmaking]] Contributed by Ali Zulfikar Zahedi ([[:w:Ali Zulfikar Zahedi]], [[:w:simple:Ali Zulfikar Zahedi]]) &lt;!-- USERREPORTED:/Gloriagulshan/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 03:56, 29 August 2026 (UTC)

:I believe this page is intended as instructional material for learning filmmaking rather than as an encyclopedic article. I will revise the page to focus on practical filmmaking concepts, methods, and processes in accordance with the purpose of Wikibooks. [[User:Gloriagulshan|Gloriagulshan]] ([[User talk:Gloriagulshan|discuss]] • [[Special:Contributions/Gloriagulshan|contribs]]) 04:20, 29 August 2026 (UTC)
: Cc: {{ping|SHB2000|MarcGarver}} [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 04:41, 29 August 2026 (UTC)
::I see the account is glocked, and there are no sleepers that aren't already locked, so nothing more to do. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 11:18, 3 September 2026 (UTC)

== Atlanticgym reported by MathXplore ==

* {{userlinks|Atlanticgym}}

Link spam, [[Special:AbuseLog/315249]] &lt;!-- USERREPORTED:/Atlanticgym/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:32, 29 August 2026 (UTC)

:{{done}} --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 12:35, 29 August 2026 (UTC)
== Makowe2026 reported by Veritas Sapientiae ==

* {{userlinks|Makowe2026}}

Spam &lt;!-- USERREPORTED:/Makowe2026/ --&gt; [[User:Veritas Sapientiae|Veritas Sapientiae]] ([[User talk:Veritas Sapientiae|discuss]] • [[Special:Contributions/Veritas Sapientiae|contribs]]) 13:53, 29 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:20, 29 August 2026 (UTC)
== Abir077 reported by MathXplore ==

* {{userlinks|Abir077}}

Link spam, [[Special:AbuseLog/315272]] &lt;!-- USERREPORTED:/Abir077/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:07, 31 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:46, 31 August 2026 (UTC)
== Jeevandan26 reported by MathXplore ==

* {{userlinks|Jeevandan26}}
Link spam, [[Special:AbuseLog/315288]] &lt;!-- USERREPORTED:/Jeevandan26/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:14, 1 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:20, 1 September 2026 (UTC)
== Mohansai00116 reported by MathXplore ==
* {{userlinks|Mohansai00116}}

Link spam, [[Special:AbuseLog/315335]] &lt;!-- USERREPORTED:/Mohansai00116/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:09, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:04, 3 September 2026 (UTC)

== Fatemai6 reported by MathXplore ==
* {{userlinks|Fatemai6}}

Link spam, [[Special:AbuseLog/315329]] &lt;!-- USERREPORTED:/Fatemai6/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:10, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Kamrulhasan147 reported by MathXplore ==
* {{userlinks|Kamrulhasan147}}

Link spam, [[Special:AbuseLog/315327]], [[Special:Contributions/Kamrulhasan142]] &lt;!-- USERREPORTED:/Kamrulhasan147/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:12, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Kamrulhasan142 reported by MathXplore ==
* {{userlinks|Kamrulhasan142}}

Link spam, [[Special:AbuseLog/315295]], [[Special:Contributions/Kamrulhasan147]] &lt;!-- USERREPORTED:/Kamrulhasan142/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:13, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Twenty7incgs reported by MathXplore ==
* {{userlinks|Twenty7incgs}}

Link spam, [[Special:AbuseLog/315323]] &lt;!-- USERREPORTED:/Twenty7incgs/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:14, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Tailleash reported by MathXplore ==
* {{userlinks|Tailleash}}

Link spam, [[Special:AbuseLog/315318]] &lt;!-- USERREPORTED:/Tailleash/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:15, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Md Akash Mia12 reported by MathXplore ==
* {{userlinks|Md Akash Mia12}}

Link spam, [[Special:AbuseLog/315299]], [[Special:AbuseLog/315298]] &lt;!-- USERREPORTED:/Md Akash Mia12/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:17, 2 September 2026 (UTC)
: {{done|Page deleted}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:03, 3 September 2026 (UTC)

== Vapesitefiftybar reported by MathXplore ==
* {{userlinks|Vapesitefiftybar}}

Link spam, [[Special:AbuseLog/315338]] &lt;!-- USERREPORTED:/Vapesitefiftybar/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:40, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)
== Myteethtime1 reported by MathXplore ==
* {{userlinks|Myteethtime1}}

Spam &lt;!-- USERREPORTED:/Myteethtime1/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:54, 4 September 2026 (UTC)
: {{Done}} by MarcGarver. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:28, 4 September 2026 (UTC)

== Rajstartupservices reported by MathXplore ==
* {{userlinks|Rajstartupservices}}

Link spam, [[Special:AbuseLog/315363]] &lt;!-- USERREPORTED:/Rajstartupservices/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 14:33, 4 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:28, 4 September 2026 (UTC)
== Reazulkarim545456 reported by MathXplore ==
* {{userlinks|Reazulkarim545456}}

Link spam, [[Special:AbuseLog/315377]] &lt;!-- USERREPORTED:/Reazulkarim545456/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 06:39, 6 September 2026 (UTC)
== Fahmidafy reported by MathXplore ==
* {{userlinks|Fahmidafy}}

Link spam, [[Special:AbuseLog/315378]] &lt;!-- USERREPORTED:/Fahmidafy/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 06:40, 6 September 2026 (UTC)
== Grow spark digital reported by MathXplore ==
* {{userlinks|Grow spark digital}}

Link spam, [[Special:AbuseLog/315381]] &lt;!-- USERREPORTED:/Grow spark digital/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 06:42, 6 September 2026 (UTC)</text>
      <sha1>5j92ewrtt4xxnom7w8771e730coznju</sha1>
    </revision>
    <revision>
      <id>4669095</id>
      <parentid>4669064</parentid>
      <timestamp>2026-09-06T10:32:04Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Reporting Korigosnacks</comment>
      <origin>4669095</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="12406" sha1="id1f7jbu6b3zlc1e9i292rxv84xfsno" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{shortcut|WB:AN|WB:AA}} {{TOC left}}
{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Administrative Assistance/Archives/%(year)d/%(monthname)s
|algo = old(14d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{ombox|type=content|text='''To request a rename or usurpation''', go to the global request page at Meta [[meta:SRUC|here]].&lt;br /&gt;''Please do not post those requests here!''}}
{{Clear}}
Welcome to the '''Administrative Assistance reading room'''.  You can request assistance from [[WB:ADMIN|administrators]] for handling a variety of problems here and alert them about problems which may require special actions not normally used during regular content editing. Please be patient as administrators are often quite busy with either their own projects or trying to perform general maintenance and cleanup.

You can deal with most vandalism yourself: [[Wikibooks:Dealing with vandalism|fix it]], then [[Wikibooks:Templates/User_notices|warn the user]]. If there is repeated vandalism by one user, lots of vandalism on a single page, or vandalism from many users, tell an admin here, or in [irc://irc.freenode.net/wikibooks #wikibooks] (say &lt;code&gt;!admin&lt;/code&gt; to get attention).

For more general questions and assistance that doesn't require an administrator, please use the [[WB:HELP|Assistance Reading Room]].
{{clear}}

[[Category:Reading room]]

== IntoAEC reported by MathXplore ==

* {{userlinks|IntoAEC}}

Spam &lt;!-- USERREPORTED:/IntoAEC/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:25, 19 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:27, 26 August 2026 (UTC)

== CaribbeanMedicalSchools reported by MathXplore ==

* {{userlinks|CaribbeanMedicalSchools}}

Spam &lt;!-- USERREPORTED:/CaribbeanMedicalSchools/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:16, 26 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:27, 26 August 2026 (UTC)
== Chzoraiz41 reported by MathXplore ==

* {{userlinks|Chzoraiz41}}

Link spam, [[Special:AbuseLog/315229]] &lt;!-- USERREPORTED:/Chzoraiz41/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:09, 27 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:17, 27 August 2026 (UTC)
== Gloriagulshan reported by MathXplore ==

* {{userlinks|Gloriagulshan}}

[[:w:Wikipedia:Sockpuppet investigations/Kagoz]] ([[Special:Contributions/Tikapara]], [[Wikibooks:Reading_room/Administrative_Assistance/Archives/2025/September#Tikapara_reported_by_MathXplore]]), created page [[Introduction to Filmmaking]] Contributed by Ali Zulfikar Zahedi ([[:w:Ali Zulfikar Zahedi]], [[:w:simple:Ali Zulfikar Zahedi]]) &lt;!-- USERREPORTED:/Gloriagulshan/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 03:56, 29 August 2026 (UTC)

:I believe this page is intended as instructional material for learning filmmaking rather than as an encyclopedic article. I will revise the page to focus on practical filmmaking concepts, methods, and processes in accordance with the purpose of Wikibooks. [[User:Gloriagulshan|Gloriagulshan]] ([[User talk:Gloriagulshan|discuss]] • [[Special:Contributions/Gloriagulshan|contribs]]) 04:20, 29 August 2026 (UTC)
: Cc: {{ping|SHB2000|MarcGarver}} [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 04:41, 29 August 2026 (UTC)
::I see the account is glocked, and there are no sleepers that aren't already locked, so nothing more to do. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 11:18, 3 September 2026 (UTC)

== Atlanticgym reported by MathXplore ==

* {{userlinks|Atlanticgym}}

Link spam, [[Special:AbuseLog/315249]] &lt;!-- USERREPORTED:/Atlanticgym/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:32, 29 August 2026 (UTC)

:{{done}} --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 12:35, 29 August 2026 (UTC)
== Makowe2026 reported by Veritas Sapientiae ==

* {{userlinks|Makowe2026}}

Spam &lt;!-- USERREPORTED:/Makowe2026/ --&gt; [[User:Veritas Sapientiae|Veritas Sapientiae]] ([[User talk:Veritas Sapientiae|discuss]] • [[Special:Contributions/Veritas Sapientiae|contribs]]) 13:53, 29 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:20, 29 August 2026 (UTC)
== Abir077 reported by MathXplore ==

* {{userlinks|Abir077}}

Link spam, [[Special:AbuseLog/315272]] &lt;!-- USERREPORTED:/Abir077/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:07, 31 August 2026 (UTC)

:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 12:46, 31 August 2026 (UTC)
== Jeevandan26 reported by MathXplore ==

* {{userlinks|Jeevandan26}}
Link spam, [[Special:AbuseLog/315288]] &lt;!-- USERREPORTED:/Jeevandan26/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:14, 1 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:20, 1 September 2026 (UTC)
== Mohansai00116 reported by MathXplore ==
* {{userlinks|Mohansai00116}}

Link spam, [[Special:AbuseLog/315335]] &lt;!-- USERREPORTED:/Mohansai00116/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:09, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:04, 3 September 2026 (UTC)

== Fatemai6 reported by MathXplore ==
* {{userlinks|Fatemai6}}

Link spam, [[Special:AbuseLog/315329]] &lt;!-- USERREPORTED:/Fatemai6/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:10, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Kamrulhasan147 reported by MathXplore ==
* {{userlinks|Kamrulhasan147}}

Link spam, [[Special:AbuseLog/315327]], [[Special:Contributions/Kamrulhasan142]] &lt;!-- USERREPORTED:/Kamrulhasan147/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:12, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Kamrulhasan142 reported by MathXplore ==
* {{userlinks|Kamrulhasan142}}

Link spam, [[Special:AbuseLog/315295]], [[Special:Contributions/Kamrulhasan147]] &lt;!-- USERREPORTED:/Kamrulhasan142/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:13, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Twenty7incgs reported by MathXplore ==
* {{userlinks|Twenty7incgs}}

Link spam, [[Special:AbuseLog/315323]] &lt;!-- USERREPORTED:/Twenty7incgs/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:14, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Tailleash reported by MathXplore ==
* {{userlinks|Tailleash}}

Link spam, [[Special:AbuseLog/315318]] &lt;!-- USERREPORTED:/Tailleash/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:15, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)

== Md Akash Mia12 reported by MathXplore ==
* {{userlinks|Md Akash Mia12}}

Link spam, [[Special:AbuseLog/315299]], [[Special:AbuseLog/315298]] &lt;!-- USERREPORTED:/Md Akash Mia12/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:17, 2 September 2026 (UTC)
: {{done|Page deleted}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:03, 3 September 2026 (UTC)

== Vapesitefiftybar reported by MathXplore ==
* {{userlinks|Vapesitefiftybar}}

Link spam, [[Special:AbuseLog/315338]] &lt;!-- USERREPORTED:/Vapesitefiftybar/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:40, 2 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:05, 3 September 2026 (UTC)
== Myteethtime1 reported by MathXplore ==
* {{userlinks|Myteethtime1}}

Spam &lt;!-- USERREPORTED:/Myteethtime1/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:54, 4 September 2026 (UTC)
: {{Done}} by MarcGarver. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:28, 4 September 2026 (UTC)

== Rajstartupservices reported by MathXplore ==
* {{userlinks|Rajstartupservices}}

Link spam, [[Special:AbuseLog/315363]] &lt;!-- USERREPORTED:/Rajstartupservices/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 14:33, 4 September 2026 (UTC)
: {{done}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:28, 4 September 2026 (UTC)
== Reazulkarim545456 reported by MathXplore ==
* {{userlinks|Reazulkarim545456}}

Link spam, [[Special:AbuseLog/315377]] &lt;!-- USERREPORTED:/Reazulkarim545456/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 06:39, 6 September 2026 (UTC)
== Fahmidafy reported by MathXplore ==
* {{userlinks|Fahmidafy}}

Link spam, [[Special:AbuseLog/315378]] &lt;!-- USERREPORTED:/Fahmidafy/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 06:40, 6 September 2026 (UTC)
== Grow spark digital reported by MathXplore ==
* {{userlinks|Grow spark digital}}

Link spam, [[Special:AbuseLog/315381]] &lt;!-- USERREPORTED:/Grow spark digital/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 06:42, 6 September 2026 (UTC)
== Korigosnacks reported by MathXplore ==
* {{userlinks|Korigosnacks}}

Link spam, [[Special:AbuseLog/315383]] &lt;!-- USERREPORTED:/Korigosnacks/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 10:32, 6 September 2026 (UTC)</text>
      <sha1>id1f7jbu6b3zlc1e9i292rxv84xfsno</sha1>
    </revision>
  </page>
  <page>
    <title>User:Soul windsurfer</title>
    <ns>2</ns>
    <id>146738</id>
    <revision>
      <id>4668923</id>
      <parentid>4647736</parentid>
      <timestamp>2026-09-05T12:21:39Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668923</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="178766" sha1="qq5zip0a5bffwsvazgffvcmz8ygksgu" xml:space="preserve"> This isn't what OP is asking for. 

 In my opinion, the &quot;best&quot; solution is the one that can be read by another programmer (or the original programmer two years later) without copious comments. You may well want the fastest or cleverest solution which some have  already provided but I prefer readability over cleverness any time.In my opinion, the &quot;best&quot; solution is the one that can be read by another programmer (or the original programmer two years later) without copious comments. You may well want the fastest or cleverest solution which some have already provided but I prefer readability over cleverness any time.&lt;ref&gt;[https://stackoverflow.com/questions/109023/count-the-number-of-set-bits-in-a-32-bit-integer?rq=1 stackoverflow question : count-the-number-of-set-bits-in-a-32-bit-integer]&lt;/ref&gt;

 it was so easy that I am ashamed of having asked.
 
 [https://petapixel.com/2018/09/19/8-12-14-vs-16-bit-depth-what-do-you-really-need/ I’m not a big fan of speculating, so I’ve done a lot of testing. It is always important to validate your assumptions. I have heard many experts claim something to be true (in theory), only to find that real-world factors make the theory essentially irrelevant. A Ferrari is theoretically faster than a Ford truck, but maybe not on a dirt road. GREG BENZ]
 

 Sorry, I don't really understand this. I like mathematics but my knowledge is very limited.
 

  It is a great idea! Mindboggling, but I don't know how it would be done.
 

  faces two separate but interconnected problems.
 

  Benefits and drawbacks of each method = pros and cons = pro et contra ( latin)
 

  Julia Programming For Nervous Beginners   


  The rabbit hole is deep with many paths to explore. ( 3DickUlus )

    I don't think that this answers the OP's question in any way. ( Here OP's means probably Other People's )

 &quot;The answer is no, although it doesn't seem so easy to give a rigorous counter-example.&quot;  Glougloubarbaki&lt;ref&gt;[https://math.stackexchange.com/questions/3546649/is-the-basin-of-attraction-of-a-p-starshaped-wrt-to-p math SE question: is-the-basin-of-attraction-of-a-p-starshaped-wrt-to-p]&lt;/ref&gt;
 

 &quot; Mathematics takes place at different time-scales. If you can solve a problem in 55 minutes that others need an hour to solve, you can probably get a good job. If you can solve a problem in a month that others might need a year to solve, you will probably do well as a graduate student. But if you can solve a problem in 10 years that nobody else can solve in a lifetime, you could be a great mathematician.&quot; Robert Israel


   &quot; anyone who wishes to study this topic should earn a Ph.D. in number theory and spend several years researching the relevant topics in depth, with the guidance of a world class expert.&quot; Alon Amit, PhD in Mathematics; Mathcircler.


   &quot;The author apologises wholeheartedly to those who dare read the source code.&quot; Freddie R. Exall

   A BELIEF IS NOT A PROOF.

   &quot;Category theory is ... the most, abstract fields of mathematics&quot; Robb Seaton&lt;ref&gt;[http://rs.io/why-category-theory-matters/ Why Category Theory Matters by Robb Seaton]&lt;/ref&gt;

   For the sake of completeness, here is the entire code I used:&quot;

    &quot;That's quite a comprehensive analysis: It'll take me probably a week (or better a month) to understand it. &quot; marcm200&lt;ref&gt;[https://fractalforums.org/fractal-mathematics-and-new-theories/28/line-segments-intersecting-msets-how-often/3181/msg17563 fractalforums.org : line-segments-intersecting-msets-how-often]&lt;/ref&gt;

     I feel this is a very basic question, but I seem to be unable to find an answer for (neither by myself nor searching)  marcm200
&lt;gallery&gt;
Animated-GIFs-davidope-11.gif
Artificial dendrites growth.gif
Branchedgifsm.gif
Fortunes-algorithm.gif
&lt;/gallery&gt;


[http://fraktal.republika.pl My home page] - dead (:-(

[[Image:Wikipedia-logo.png|20px]] Wikipedia - [[w:User:Adam majewski|Adam majewski]]

[[Image:Commons-logo.svg|20px]] Commons - [[commons:User:Adam majewski|Adam majewski]]

[https://www.dropbox.com/sh/o0txhw0ui3rbyam/oXlVzMWlJ6 My Dropbox public folders]

[http://math.stackexchange.com/users/44654/adam Mathematics Stack Exchange]

[https://gitlab.com/u/adammajewski gitlab repo]

='''wiki''' =
&lt;pre&gt; 
== c source code==
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
&lt;/syntaxhighlight&gt;

== bash source code==
&lt;syntaxhighlight lang=&quot;bash&quot;&gt;
&lt;/syntaxhighlight&gt;


==make==
&lt;syntaxhighlight lang=makefile&gt;
all: 
	chmod +x d.sh
	./d.sh
&lt;/syntaxhighlight&gt;


Tu run the program simply 

  make


==text output==
&lt;pre&gt;

==references==
&lt;references/&gt;

== References ==
{{Reflist}}

&lt;syntaxhighlight lang=&quot;python&quot;&gt; &lt;/syntaxhighlight&gt; 

==== Sections ====
Sections included inside a hidden block result in broken anchors in the table of contents at the top of the page.
{{hidden begin|title=example}}
===== You can't get here from the table of contents =====
{{hidden end}}


&lt;/pre&gt;


* [[:w:Special:SiteMatrix|SiteMatrix : List of Wikimedia wikis]]
* [[:w:Wikipedia:Tools|Wikipedia tools]]
* [[Template:Multiple_image|Multiple_image]]
* [[Template:Gallery]]
* [http://:m:Help:Images_and_other_uploaded_files#Gallery Help:Images_and_other_uploaded_files#Gallery]
* [https://www.mathjax.org/ mathjax live demo ( mathjax render)]
* [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight]
* [[http://alexgorbatchev.com/SyntaxHighlighter/ SyntaxHighlighter]]
* [[https://www.mediawiki.org/wiki/Extension:SyntaxHighlighter source]]
* [[http://detectlanguage.com/ detect spoken language]]
* [[Help:Variables]]
* [[Help:Editing]]
* [[Help:Editing#Inserting_references]]
* {{Ping|username}} 
* [http://meta.wikimedia.org/wiki/List_of_Wikibooks List_of_Wikibooks languages]
* [https://en.wikibooks.org/wiki/Help:Formulas formula ]
* [[Special:SpecialPages | WIKIBOOKS SPECIAL]]
* [https://www.mediawiki.org/wiki/Extension:RSS rss]
* [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Hidden_text | &lt;code&gt;&lt;nowiki&gt;&lt;!-- Comment --&gt;&lt;/nowiki&gt;&lt;/code&gt;] 
* http://meta.math.stackexchange.com/questions/5020/mathjax-basic-tutorial-and-quick-reference
* https://en.wikibooks.org/wiki/Template:ISBN
&lt;pre&gt;

{{displaytitle|title=&amp;nbsp;|tab=Print version}}
{{print version notice}}
{{print version cover}}
{{PDF version}} 
{{Book title|{{BOOKNAME}}|A guide for the popular online role-playing game ''[[w:EverQuest II|EverQuest II]]''.}}
== Table of Contents ==
{{Book search}}
{{Print version}}
{{wikipedia|Everquest II}}
== How to write this book ==
Anyone who wishes to improve on this book is/are [[w:Wikipedia:Be bold in updating pages|highly encouraged to do so]]. Before you do, make sure you've read the [[Help:Editing|MediaWiki editing help page]].
{{status|0%}}
{{Alphabetical|E}}
{{shelves|Strategy guides}}

&lt;/pre&gt;


If you want the stable and official version of Fractal zoomer documentation you can make pdf from wikibooks and put it in wikibooks or your repos. Then you will have full control of it's content
==table==
Wikibooks help
* [[Help:Tables]]
* [[Editing_Wikitext/Tables]]
* [[Editing_Wikitext/Tables_Ready_to_Use]]


wikipedia help
* [[:w:Wikipedia:Manual_of_Style/Tables]]
* [[:w:Wikipedia:Table dos and don'ts]], a summary of the key points in this guideline
* [[:w:Help:Table]], extensive help
* [[:w:Help:Table/Introduction to tables]], a quick guide to using tables
* [[:w:Help:Collapsing]] (show/hide button)
* [[:w:Wikipedia:Conditional tables]]

=Triangle groups=
The triangle can be:
* an ordinary Euclidean triangle
* a triangle on the sphere
* a hyperbolic triangle

== Hyperbolic groups in H2==
{{Further|Uniform tilings in hyperbolic plane}}

Two-dimensional hyperbolic triangle groups exist as rank 3 Coxeter diagrams, defined by triangle (p q r) for:
:&lt;math&gt;\frac{1}{p}+\frac{1}{q}+\frac{1}{r}&lt;1.&lt;/math&gt;


{| class=&quot;wikitable&quot; style=&quot;float:center;&quot;
|+ [[:w:Poincaré disk model|Poincaré disk model]] of fundamental domain [[:w:Triangle group|triangles]]
|-
!colspan=5|Example right triangles [p,q]
|- align=center
|[[File:H2checkers 237.png|80px]]&lt;br&gt;[3,7]
|[[File:H2checkers 238.png|80px]]&lt;br&gt;[3,8]
|[[File:Hyperbolic domains 932 black.png|80px]]&lt;br&gt;[3,9]
|[[File:H2checkers 23i.png|80px]]&lt;br&gt;[3,&amp;infin;]
|- align=center
|[[File:H2checkers 245.png|80px]]&lt;br&gt;[4,5]
|[[File:H2checkers 246.png|80px]]&lt;br&gt;[4,6]
|[[File:H2checkers 247.png|80px]]&lt;br&gt;[4,7]
|[[File:H2checkers 248.png|80px]]&lt;br&gt;[4,8]
|[[File:H2checkers 24i.png|80px]]&lt;br&gt;[&amp;infin;,4]
|- align=center
|[[File:H2checkers 255.png|80px]]&lt;br&gt;[5,5]
|[[File:H2checkers 256.png|80px]]&lt;br&gt;[5,6]
|[[File:H2checkers 257.png|80px]]&lt;br&gt;[5,7]
|[[File:H2checkers 266.png|80px]]&lt;br&gt;[6,6]
|[[File:H2checkers 2ii.png|80px]]&lt;br&gt;[&amp;infin;,&amp;infin;]
|- align=center
!colspan=5|Example general triangles [(p,q,r)]
|- align=center
|[[File:H2checkers 334.png|80px]]&lt;br&gt;[(3,3,4)]
|[[File:H2checkers 335.png|80px]]&lt;br&gt;[(3,3,5)]
|[[File:H2checkers 336.png|80px]]&lt;br&gt;[(3,3,6)]
|[[File:H2checkers 337.png|80px]]&lt;br&gt;[(3,3,7)]
|[[File:H2checkers 33i.png|80px]]&lt;br&gt;[(3,3,&amp;infin;)]
|- align=center
|[[File:H2checkers 344.png|80px]]&lt;br&gt;[(3,4,4)]
|[[File:H2checkers 366.png|80px]]&lt;br&gt;[(3,6,6)]
|[[File:H2checkers 3ii.png|80px]]&lt;br&gt;[(3,&amp;infin;,&amp;infin;)]
|[[File:H2checkers 666.png|80px]]&lt;br&gt;[(6,6,6)]
|[[File:Infinite-order triangular tiling.svg|80px]]&lt;br&gt;[(&amp;infin;,&amp;infin;,&amp;infin;)]
|}
==hyperbolic tilings==
Shown in the [[:en:Poincaré disk model|conformal ('stereographic') disc model]].
In each, the origin is equidistant from the three defining mirrors.

Made by [[User:Tamfang/programs|crude little Python programs]].
Full size is 2520 pixels (least common multiple of 1,2,3,4,5,6,7,8,9,10).

Ranked by the area of the fundamental triangle.

You will notice that many of the duals are missing; because, where an odd number of facets meet at a vertex, I have not thought of an algorithm to color them.  (The black-and-white figures are made by counting mirror-flips from the pixel to the interior of the triangle that contains the centre.)

{| class=&quot;wikitable&quot;
! p q r !! xxx !! xox !! oox !! oxx !! oxo !! xxo !! xoo !! snub
|- align=center
| width=60|2 3 7 &lt;br&gt; area &amp;pi;/42
|[[File:H2 tiling 237-7.png|90px]]  [[File:H2checkers 237.png|90px]]
|[[File:H2 tiling 237-5.png|90px]] 
|[[File:H2 tiling 237-1.png|90px]] 
|[[File:H2 tiling 237-3.png|90px]] 
|[[File:H2 tiling 237-2.png|90px]] 
|[[File:H2 tiling 237-6.png|90px]] 
|[[File:H2 tiling 237-4.png|90px]] 
|[[File:H2 snub 237a.png|90px]] [[File:H2 snub 237b.png|90px]]
|- align=center
| 2 4 5 &lt;br&gt; area &amp;pi;/20
|[[File:H2 tiling 245-7.png|90px]]  [[File:H2checkers 245.png|90px]]
|[[File:H2 tiling 245-5.png|90px]] 
|[[File:H2 tiling 245-1.png|90px]] 
|[[File:H2 tiling 245-3.png|90px]]  [[File:H2chess 245f.png|90px]]
|[[File:H2 tiling 245-2.png|90px]] 
|[[File:H2 tiling 245-6.png|90px]] 
|[[File:H2 tiling 245-4.png|90px]]  [[File:H2chess 245c.png|90px]]
|[[File:H2 snub 245a.png|90px]] [[File:H2 snub 245b.png|90px]]
|- align=center
| 3 3 4 &lt;br&gt; area &amp;pi;/12
|[[File:H2 tiling 334-7.png|90px]]  [[File:H2checkers 334.png|90px]]
|[[File:H2 tiling 334-5.png|90px]] 
|[[File:H2 tiling 334-1.png|90px]] 
|[[File:H2 tiling 334-3.png|90px]] 
|[[File:H2 tiling 334-2.png|90px]] 
|[[File:H2 tiling 334-6.png|90px]] 
|[[File:H2 tiling 334-4.png|90px]] 
|[[File:H2 snub 334a.png|90px]] [[File:H2 snub 334b.png|90px]]
|- align=center
| 2 3 &amp;infin; &lt;br&gt; area &amp;pi;/6
|[[File:H2 tiling 23i-7.png|90px]]  [[File:H2checkers 23i.png|90px]]
|[[File:H2 tiling 23i-5.png|90px]]  
|[[File:H2 tiling 23i-1.png|90px]]  [[File:H2chess 23ib.png|90px]]
|[[File:H2 tiling 23i-3.png|90px]]  
|[[File:H2 tiling 23i-2.png|90px]]  
|[[File:H2 tiling 23i-6.png|90px]]  [[File:H2chess 23ie.png|90px]]
|[[File:H2 tiling 23i-4.png|90px]]  
|[[File:H2 snub 23ia.png|90px]] [[File:H2 snub 23ib.png|90px]]
|- align=center
| 2 &amp;infin; &amp;infin; &lt;br&gt; area &amp;pi;/2
|[[File:H2 tiling 2ii-7.png|90px]]  [[File:H2checkers 2ii.png|90px]]
|[[File:H2 tiling 2ii-5.png|90px]]  [[File:H2chess 2iid.png|90px]]
|[[File:H2 tiling 2ii-1.png|90px]]  [[File:H2chess 2iib.png|90px]]
|[[File:H2 tiling 2ii-3.png|90px]]  [[File:H2chess 2iif.png|90px]]
|[[File:H2 tiling 2ii-2.png|90px]]  [[File:H2chess 2iia.png|90px]]
|[[File:H2 tiling 2ii-6.png|90px]]  [[File:H2chess 2iie.png|90px]]
|[[File:H2 tiling 2ii-4.png|90px]]  [[File:H2chess 2iic.png|90px]]
|[[File:H2 snub 2iia.png|90px]] [[File:H2 snub 2iib.png|90px]]
|- align=center
| &amp;infin; &amp;infin; &amp;infin; &lt;br&gt; area &amp;pi;
|[[File:H2 tiling iii-7.png|90px]]  [[File:H2checkers iii.png|90px]]
|[[File:H2 tiling iii-5.png|90px]]  [[File:H2chess iiid.png|90px]]
|[[File:H2 tiling iii-1.png|90px]]  [[File:H2chess iiib.png|90px]]
|[[File:H2 tiling iii-3.png|90px]]  [[File:H2chess iiif.png|90px]]
|[[File:H2 tiling iii-2.png|90px]]  [[File:H2chess iiia.png|90px]]
|[[File:H2 tiling iii-6.png|90px]]  [[File:H2chess iiie.png|90px]]
|[[File:H2 tiling iii-4.png|90px]]  [[File:H2chess iiic.png|90px]]
|[[File:H2 snub iiia.png|90px]] [[File:H2 snub iiib.png|90px]]
|}

The difference between the two snubs in each row is whether or not the central triangle contains a vertex.

In my opinion the above six rows abundantly illustrate the principles; but, by popular demand, [[User:Tamfang/H2|I made a hundred more]].  (And it appears that each row now has at least one article in Wikipedia.  I lament my role as enabler.)
==uniformn==
{| class=wikitable align=right width=300
|+ Examples of uniform tilings
|-
!Spherical
!Euclidean 
!colspan=4|Hyperbolic
|- align=center
|[[File:Uniform tiling 532-t0.png|100px]]&lt;BR&gt;[[dodecahedron|{5,3}]]&lt;BR&gt;5.5.5&lt;BR&gt;{{CDD|node_1|5|node|3|node}}
|[[File:Uniform tiling 63-t0.png|100px]]&lt;BR&gt;[[hexagonal tiling|{6,3}]]&lt;BR&gt;6.6.6&lt;BR&gt;{{CDD|node_1|6|node|3|node}}
|[[File:Heptagonal tiling.svg|100px]]&lt;BR&gt;[[heptagonal tiling|{7,3}]]&lt;BR&gt;7.7.7&lt;BR&gt;{{CDD|node_1|7|node|3|node}}
|[[File:H2-I-3-dual.svg|100px]]&lt;BR&gt;[[Order-3 apeirogonal tiling|{∞,3}]]&lt;BR&gt;∞.∞.∞&lt;BR&gt;{{CDD|node_1|infin|node|3|node}}
|-
|colspan=4|''[[Regular tiling]]s'' {p,q} of the sphere, Euclidean plane, and hyperbolic plane using regular pentagonal, hexagonal and heptagonal and apeirogonal faces.
|- align=center
|[[File:Uniform tiling 532-t01.png|100px]]&lt;BR&gt;[[truncated dodecahedron|t{5,3}]]&lt;BR&gt;10.10.3&lt;BR&gt;{{CDD|node_1|5|node_1|3|node}}
|[[File:Uniform tiling 63-t01.png|100px]]&lt;BR&gt;[[truncated hexagonal tiling|t{6,3}]]&lt;BR&gt;12.12.3&lt;BR&gt;{{CDD|node_1|6|node_1|3|node}}
|[[File:Truncated heptagonal tiling.svg|100px]]&lt;BR&gt;[[Truncated heptagonal tiling|t{7,3}]]&lt;BR&gt;14.14.3&lt;BR&gt;{{CDD|node_1|7|node_1|3|node}}
|[[File:H2 tiling 23i-3.png|100px]]&lt;BR&gt;[[Truncated apeirogonal tiling|t{∞,3}]]&lt;BR&gt;∞.∞.3&lt;BR&gt;{{CDD|node_1|infin|node_1|3|node}}
|-
|colspan=4|[[Truncation (geometry)|Truncated tilings]] have 2p.2p.q vertex figures from regular {p,q}.
|- align=center
|[[File:Uniform tiling 532-t1.png|100px]]&lt;BR&gt;[[icosidodecahedron|r{5,3}]]&lt;BR&gt;3.5.3.5&lt;BR&gt;{{CDD|node|5|node_1|3|node}}
|[[File:Uniform tiling 63-t1.svg|100px]]&lt;BR&gt;[[trihexagonal tiling|r{6,3}]]&lt;BR&gt;3.6.3.6&lt;BR&gt;{{CDD|node|6|node_1|3|node}}
|[[File:Triheptagonal tiling.svg|100px]]&lt;BR&gt;[[triheptagonal tiling|r{7,3}]]&lt;BR&gt;3.7.3.7&lt;BR&gt;{{CDD|node|7|node_1|3|node}}
|[[File:H2 tiling 23i-2.png|100px]]&lt;BR&gt;[[triapeirogonal tiling|r{∞,3}]]&lt;BR&gt;3.∞.3.∞&lt;BR&gt;{{CDD|node|infin|node_1|3|node}}
|-
|colspan=4|''[[Quasiregular tiling]]s'' are similar to regular tilings but alternate two types of regular polygon around each vertex.
|- align=center
|[[File:Uniform tiling 532-t02.png|100px]]&lt;BR&gt;[[rhombicosidodecahedron|rr{5,3}]]&lt;BR&gt;3.4.5.4&lt;BR&gt;{{CDD|node_1|5|node|3|node_1}}
|[[File:Uniform tiling 63-t02.png|100px]]&lt;BR&gt;[[Rhombitrihexagonal tiling|rr{6,3}]]&lt;BR&gt;3.4.6.4&lt;BR&gt;{{CDD|node_1|6|node|3|node_1}}
|[[File:Rhombitriheptagonal tiling.svg|100px]]&lt;BR&gt;[[Rhombitriheptagonal tiling|rr{7,3}]]&lt;BR&gt;3.4.7.4&lt;BR&gt;{{CDD|node_1|7|node|3|node_1}}
|[[File:H2 tiling 23i-5.png|100px]]&lt;BR&gt;[[Rhombitriapeirogonal tiling|rr{∞,3}]]&lt;BR&gt;3.4.∞.4&lt;BR&gt;{{CDD|node_1|infin|node|3|node_1}}
|-
|colspan=4|''[[Semiregular tiling]]s'' have more than one type of regular polygon.
|- align=center
|[[File:Uniform tiling 532-t012.png|100px]]&lt;BR&gt;[[truncated icosidodecahedron|tr{5,3}]]&lt;BR&gt;4.6.10&lt;BR&gt;{{CDD|node_1|5|node_1|3|node_1}}
|[[File:Uniform tiling 63-t012.svg|100px]]&lt;BR&gt;[[truncated trihexagonal tiling|tr{6,3}]]&lt;BR&gt;4.6.12&lt;BR&gt;{{CDD|node_1|6|node_1|3|node_1}}
|[[File:Truncated triheptagonal tiling.svg|100px]]&lt;BR&gt;[[truncated triheptagonal tiling|tr{7,3}]]&lt;BR&gt;4.6.14&lt;BR&gt;{{CDD|node_1|7|node_1|3|node_1}}
|[[File:H2 tiling 23i-7.png|100px]]&lt;BR&gt;[[truncated triapeirogonal tiling|tr{∞,3}]]&lt;BR&gt;4.6.∞&lt;BR&gt;{{CDD|node_1|infin|node_1|3|node_1}}
|-
|colspan=4|''[[Omnitruncated tiling]]s'' have three or more even-sided regular polygons.
|}&lt;div style=&quot;font-size:75%;display:inline-block;float:right;clear:right;&quot;&gt;
{| class=&quot;wikitable collapsible collapsed&quot; align=right
|+ Construction of Archimedean Solids and Tessellations
!colspan=2|Symmetry
!colspan=2|[[Dihedral symmetry in three dimensions|Triangular dihedral symmetry]]&lt;br /&gt;[[File:Sphere symmetry group d3h.png|100px]]
![[Tetrahedral symmetry|Tetrahedral]]&lt;br /&gt;[[File:Tetrahedral reflection domains.png|100px]]
!colspan=2|[[Octahedral symmetry|Octahedral]]&lt;br /&gt;[[File:Octahedral reflection domains.png|100px]]
!colspan=2|[[Icosahedral symmetry|Icosahedral]]&lt;br /&gt;[[File:Icosahedral reflection domains.png|100px]]
!colspan=2|[[p6m symmetry]]&lt;br /&gt;[[File:Tiling Dual Semiregular V4-6-12 Bisected Hexagonal.svg|100px]]
!colspan=2|[[Coxeter–Dynkin diagram#Hyperbolic groups in H2|[3,7] symmetry]]&lt;br /&gt;[[File:H2checkers 237.png|100px]]
!colspan=2|[[Coxeter–Dynkin diagram#Hyperbolic groups in H2|[3,8] symmetry]]&lt;br /&gt;[[File:H2checkers 238.png|100px]]
|-
! Starting solid&lt;br /&gt;Operation||Symbol&lt;br /&gt;{p,q}&lt;br /&gt;{{CDD|node_1|p|node|q|node}}
! [[Hosohedron|Triangular hosohedron]]&lt;br /&gt;{2,3}&lt;br /&gt;[[File:Spherical trigonal hosohedron.svg|50px]] || [[Dihedron|Triangular dihedron]]&lt;br /&gt;{3,2}&lt;br /&gt;[[File:Trigonal dihedron.svg|50px]] || [[Tetrahedron]]&lt;br /&gt;{3,3}&lt;br /&gt;[[File:Uniform polyhedron-33-t0.png|50px]] || [[Cube]]&lt;br /&gt;{4,3}&lt;br /&gt;[[File:Uniform polyhedron-43-t0.svg|50px]] || [[Octahedron]]&lt;br /&gt;{3,4}&lt;br /&gt;[[File:Uniform polyhedron-43-t2.svg|50px]] || [[Dodecahedron]]&lt;br /&gt;{5,3}&lt;br /&gt;[[File:Uniform polyhedron-53-t0.svg|50px]] || [[Regular icosahedron|Icosahedron]]&lt;br /&gt;{3,5}&lt;br /&gt;[[File:Uniform polyhedron-53-t2.svg|50px]] || [[Hexagonal tiling]]&lt;br /&gt;{6,3}&lt;br /&gt;[[File:Uniform tiling 63-t0.svg|50px]] || [[Triangular tiling]]&lt;br /&gt;{3,6}&lt;br /&gt;[[File:Uniform tiling 63-t2.svg|50px]] || [[Heptagonal tiling]]&lt;br /&gt;{7,3}&lt;br /&gt;[[File:Heptagonal tiling.svg|50px]] || [[Order-7 triangular tiling]]&lt;br /&gt;{3,7}&lt;br /&gt;[[File:Order-7 triangular tiling.svg|50px]] || [[Octagonal tiling]]&lt;br /&gt;{8,3}&lt;br /&gt;[[File:H2 tiling 238-1.png|50px]] || [[Order-8 triangular tiling]]&lt;br /&gt;{3,8}&lt;br /&gt;[[File:H2 tiling 238-4.png|50px]]
|- align=center
! [[truncation (geometry)|Truncation]] (t)||t{p,q}&lt;br /&gt;{{CDD|node_1|p|node_1|q|node}}
| [[triangular prism]]&lt;br /&gt;[[File:Spherical triangular prism.svg|50px]] || [[truncated triangular dihedron]]&lt;br /&gt;[[File:Hexagonal_dihedron.svg|50px]]&lt;span style=&quot;font-size:70%&quot;&gt;(Half of the &quot;edges&quot; count as degenerate [[digon|digon faces]]. The other half are normal edges.)&lt;/span&gt; || [[truncated tetrahedron]]&lt;br /&gt;[[File:Uniform polyhedron-33-t01.png|50px]] || [[truncated cube]]&lt;br /&gt;[[File:Uniform polyhedron-43-t01.svg|50px]] || [[truncated octahedron]]&lt;br /&gt;[[File:Uniform polyhedron-43-t12.svg|50px]] || [[truncated dodecahedron]]&lt;br /&gt;[[File:Uniform polyhedron-53-t01.svg|50px]] || [[truncated icosahedron]]&lt;br /&gt;[[File:Uniform polyhedron-53-t12.svg|50px]] || [[Truncated hexagonal tiling]]&lt;br /&gt;[[File:Uniform tiling 63-t01.svg|50px]] || [[Hexagonal_tiling|Truncated triangular tiling]]&lt;br /&gt;[[File:Uniform tiling 63-t12.svg|50px]] || [[Truncated heptagonal tiling]]&lt;br /&gt;[[File:Truncated heptagonal tiling.svg|50px]] || [[Truncated order-7 triangular tiling]]&lt;br /&gt;[[File:Truncated order-7 triangular tiling.svg|50px]]  || [[Truncated octagonal tiling]]&lt;br /&gt;[[File:H2 tiling 238-3.png|50px]] || [[Truncated order-8 triangular tiling]]&lt;br /&gt;[[File:H2 tiling 238-6.png|50px]]
|- align=center
! [[Rectification (geometry)|Rectification]] (r)&lt;br /&gt;Ambo (a)||r{p,q}&lt;br /&gt;{{CDD|node|p|node_1|q|node}}
|colspan=2|  [[tridihedron]]&lt;br /&gt;[[File:Trigonal_dihedron.svg|50px]]&lt;span style=&quot;font-size:70%&quot;&gt;(All of the &quot;edges&quot; count as degenerate [[digon|digon faces]].)&lt;/span&gt; ||[[tetratetrahedron]]&lt;br /&gt;[[File:Uniform polyhedron-33-t1.png|50px]] ||colspan=2| [[cuboctahedron]]&lt;br /&gt;[[File:Uniform polyhedron-43-t1.svg|50px]] ||colspan=2| [[icosidodecahedron]]&lt;br /&gt;[[File:Uniform polyhedron-53-t1.svg|50px]] ||colspan=2| [[Trihexagonal tiling]]&lt;br /&gt;[[File:Uniform polyhedron-63-t1.png|50px]] ||colspan=2| [[Triheptagonal tiling]]&lt;br /&gt;[[File:Triheptagonal tiling.svg|50px]] ||colspan=2| [[Trioctagonal tiling]]&lt;br /&gt;[[File:H2 tiling 238-2.png|50px]]
|- align=center
! [[Bitruncation]] (2t)&lt;br /&gt;Dual kis (dk)||2t{p,q}&lt;br /&gt;{{CDD|node|p|node_1|q|node_1}}
| truncated triangular dihedron&lt;br /&gt;[[File:Hexagonal_dihedron.svg|50px]]&lt;span style=&quot;font-size:70%&quot;&gt;(Half of the &quot;edges&quot; count as degenerate [[digon|digon faces]]. The other half are normal edges.)&lt;/span&gt; || triangular prism&lt;br /&gt;[[File:Spherical triangular prism.svg|50px]] || truncated tetrahedron&lt;br /&gt;[[File:Uniform polyhedron-33-t12.png|50px]] || truncated octahedron&lt;br /&gt;[[File:Uniform polyhedron-43-t12.svg|50px]] || truncated cube&lt;br /&gt;[[File:Uniform polyhedron-43-t01.svg|50px]] || truncated icosahedron&lt;br /&gt;[[File:Uniform polyhedron-53-t12.svg|50px]] || truncated dodecahedron&lt;br /&gt;[[File:Uniform polyhedron-53-t01.svg|50px]] || truncated triangular tiling&lt;br /&gt;[[File:Uniform tiling 63-t12.png|50px]] || truncated hexagonal tiling&lt;br /&gt;[[File:Uniform tiling 63-t01.png|50px]] || Truncated order-7 triangular tiling&lt;br /&gt;[[File:Truncated order-7 triangular tiling.svg|50px]] || Truncated heptagonal tiling&lt;br /&gt;[[File:Truncated heptagonal tiling.svg|50px]] || Truncated order-8 triangular tiling&lt;br /&gt;[[File:H2 tiling 238-6.png|50px]] || Truncated octagonal tiling&lt;br /&gt;[[File:H2 tiling 238-3.png|50px]]
|- align=center
! [[Birectification]] (2r)&lt;br /&gt;[[Dual polyhedron|Dual]] (d)||2r{p,q}&lt;br /&gt;{{CDD|node|p|node|q|node_1}}
| triangular dihedron&lt;br /&gt;{3,2}&lt;br /&gt;[[File:Trigonal dihedron.svg|50px]] || triangular hosohedron&lt;br /&gt;{2,3}&lt;br /&gt;[[File:Spherical trigonal hosohedron.svg|50px]] || tetrahedron&lt;br /&gt;[[File:Uniform polyhedron-33-t2.png|50px]]|| octahedron&lt;br /&gt;[[File:Uniform polyhedron-43-t2.svg|50px]] || cube&lt;br /&gt;[[File:Uniform polyhedron-43-t0.svg|50px]] || icosahedron&lt;br /&gt;[[File:Uniform polyhedron-53-t2.svg|50px]] || dodecahedron&lt;br /&gt;[[File:Uniform polyhedron-53-t0.svg|50px]] || triangular tiling&lt;br /&gt;[[File:Uniform tiling 63-t2.svg|50px]] || hexagonal tiling&lt;br /&gt;[[File:Uniform tiling 63-t0.svg|50px]] || Order-7 triangular tiling&lt;br /&gt;[[File:Order-7 triangular tiling.svg|50px]] || Heptagonal tiling&lt;br /&gt;[[File:Heptagonal tiling.svg|50px]] || Order-8 triangular tiling&lt;br /&gt;[[File:H2 tiling 238-4.png|50px]] || Octagonal tiling&lt;br /&gt;[[File:H2 tiling 238-1.png|50px]]
|- align=center
! [[Cantellation]] (rr)&lt;br /&gt;[[expansion (geometry)|Expansion]] (e)||rr{p,q}&lt;br /&gt;{{CDD|node_1|p|node|q|node_1}}
| colspan=2|[[triangular prism]]&lt;br /&gt;[[File:Spherical triangular prism.svg|50px]]&lt;span style=&quot;font-size:70%&quot;&gt;(The &quot;edge&quot; between each pair of tetragons counts as a degenerate [[digon|digon face]]. The other edges (the ones between a trigon and a tetragon) are normal edges.)&lt;/span&gt; || [[rhombitetratetrahedron]]&lt;br /&gt;[[File:Uniform polyhedron-33-t02.png|50px]] ||colspan=2| [[rhombicuboctahedron]]&lt;br /&gt;[[File:Uniform polyhedron-43-t02.png|50px]] || colspan=2|[[rhombicosidodecahedron]] &lt;br /&gt;[[File:Uniform polyhedron-53-t02.png|50px]] || colspan=2|[[rhombitrihexagonal tiling]]&lt;br /&gt;[[File:Uniform tiling 63-t02.svg|50px]] || colspan=2|[[Rhombitriheptagonal tiling]] &lt;br /&gt;[[File:H2 tiling 237-5.png|50px]] || colspan=2|[[Rhombitrioctagonal tiling]] &lt;br /&gt;[[File:H2 tiling 238-5.png|50px]]
|- align=center
! Snub rectified (sr)&lt;br /&gt;[[Snub (geometry)|Snub]] (s)||sr{p,q}&lt;br /&gt;{{CDD|node_h|p|node_h|q|node_h}}
|colspan=2| [[triangular antiprism]]&lt;br /&gt;[[File:Trigonal antiprism.png|50px]]&lt;span style=&quot;font-size:70%&quot;&gt;(Three yellow-yellow &quot;edges&quot;, no two of which share any vertices, count as degenerate [[digon|digon faces]]. The other edges are normal edges.)&lt;/span&gt; || [[snub tetratetrahedron]]&lt;br /&gt;[[File:Uniform polyhedron-33-s012.svg|50px]] ||colspan=2| [[snub cuboctahedron]]&lt;br /&gt;[[File:Uniform polyhedron-43-s012.png|50px]] ||colspan=2| [[snub icosidodecahedron]]&lt;br /&gt;[[File:Uniform polyhedron-53-s012.png|50px]] ||colspan=2| [[snub trihexagonal tiling]]&lt;br /&gt;[[File:Uniform tiling 63-snub.svg|50px]] ||colspan=2| [[Snub triheptagonal tiling]]&lt;br /&gt;[[File:Uniform tiling 73-snub.png|50px]] ||colspan=2| [[Snub trioctagonal tiling]]&lt;br /&gt;[[File:Uniform tiling 83-snub.png|50px]]
|- align=center
! [[Cantitruncation]] (tr)&lt;br /&gt;Bevel (b)||tr{p,q}&lt;br /&gt;{{CDD|node_1|p|node_1|q|node_1}}
|colspan=2| [[hexagonal prism]]&lt;br /&gt;[[File:Truncated triangle prism.png|50px]] || [[truncated tetratetrahedron]]&lt;br /&gt;[[File:Uniform polyhedron-33-t012.png|50px]] ||colspan=2| [[truncated cuboctahedron]]&lt;br /&gt;[[File:Uniform polyhedron-43-t012.png|50px]] ||colspan=2| [[truncated icosidodecahedron]]&lt;br /&gt;[[File:Uniform polyhedron-53-t012.png|50px]] ||colspan=2| [[truncated trihexagonal tiling]]&lt;br /&gt;[[File:Uniform tiling 63-t012.svg|50px]] ||colspan=2| [[Truncated triheptagonal tiling]]&lt;br /&gt;[[File:H2 tiling 237-7.png|50px]] ||colspan=2| [[Truncated trioctagonal tiling]]&lt;br /&gt;[[File:H2 tiling 238-7.png|50px]]
|}&lt;/div&gt;
In [[Hyperbolic geometry|hyperbolic]] [[geometry]], a '''uniform hyperbolic tiling''' (or regular, quasiregular or semiregular hyperbolic tiling) is an edge-to-edge filling of the hyperbolic plane which has [[regular polygon]]s as [[Face (geometry)|faces]] and is [[vertex-transitive]] ([[Transitive group action|transitive]] on its [[vertex (geometry)|vertices]], isogonal, i.e. there is an [[isometry]] mapping any vertex onto any other). It follows that all vertices are [[Congruence (geometry)|congruent]], and the [[tessellation|tiling]] has a high degree of rotational and translational [[symmetry]].

Uniform tilings can be identified by their [[vertex configuration]], a sequence of numbers representing the number of sides of the polygons around each vertex. For example, 7.7.7 represents the [[heptagonal tiling]] which has 3 [[heptagon]]s around each vertex. It is also regular since all the polygons are the same size, so it can also be given the [[Schläfli symbol]] {7,3}.

Uniform tilings may be [[Regular polyhedron|regular]] (if also face- and edge-transitive), quasi-regular (if edge-transitive but not face-transitive) or [[Semiregular polyhedron|semi-regular]] (if neither edge- nor face-transitive). For right triangles (''p''&amp;nbsp;''q''&amp;nbsp;2), there are two regular tilings, represented by [[Schläfli symbol]] {''p'',''q''} and {''q'',''p''}.

==see also==
* [[:w:User:Tomruen/List of hyperbolic symmetry groups]]
* [[:commons:User:Tomruen/gallery]]
* [[:commons:User:Tamfang|User:Tamfang]]

=github=
* [https://github.com/nschloe/xhub nschloe: xhub ( Extend GitHub pages with support for LaTeX, graphs, etc.) math]
* https://github.blog/2022-05-19-math-support-in-markdown/ 
* https://nschloe.github.io/2022/05/20/math-on-github.html
* https://github.blog/2022-02-14-include-diagrams-markdown-files-mermaid/
* 


=table=
[[Fractals/mandel#Misiurewicz_point|Misiurewicz_point]]

{| class=&quot;wikitable&quot;
|+ Misiurewicz point of wake 1/q = &lt;math&gt;M_{q,1}&lt;/math&gt;
|-
! period !! p/q !! prep,period !! c !!  [[Fractals/Iterations_in_the_complex_plane/wake|e_angles_of_the_wake]] !! [[Fractals/Iterations_in_the_complex_plane/p_misiurewicz|e_engles_of_Misiurewicz]]
|-
|  2 || 1/2 || 2,1 || -1.543689012692076 +0.000000000000000i || ( 1/3 = p01, 2/3 = p10 ) || 
|-
|  3 || 1/3 || 3,1 || -0.101096363845622 +0.956286510809142i || ( 1/7 = p001, 2/7 = p010 ) || 9/56, 11/56, 15/56
|-
|  4 || 1/4 || 4,1 ||  0.366362983422764 +0.591533773261445i || Treść komórki ||
|-
|  5 || 1/5 || 5,1 ||  0.437924241359463 +0.341892084338116i || Treść komórki ||
|-
|  6 || 1/6 || 6,1 ||  0.424512719050040 +0.207530228166745i ||  ||
|-
|  7 || 1/7 || 7,1 ||  0.397391822296541 +0.133511204871878i || ||
|-
|  8 || 1/8 || 8,1 ||  0.372137705449577 +0.090398233158173i || ||
|-
|  9 || 1/9 || 9,1 ||  0.351423759052522 +0.063866559813293i  || (1/511 = p000000001, 2/511 = p000000010 ) || 
|-
| 10|| 1/10 || 10,1 || 0.334957506651529  +0.046732666062027i || (1/1023 = p0000000001, 2/1023 = p0000000010 )||
|-
| 11|| || || || ||
|-
| 12|| || || || ||
|-
| 13|| || || || ||
|-
| 14|| || || || ||
|-
| 15|| || || || ||
|-
| 16|| || || || ||
|-
| 17|| || || || ||
|-
| 18|| || || || ||
|-
| 19|| || || || ||
|-
| 20|| || || || ||
|-
| 21|| || || || ||
|-
| 22|| || || || ||
|-
| 23|| || || || ||
|-
| 24|| || || || ||
|-
| 25|| || || || ||
|-
| 26|| || || || ||
|-
| 27|| || || || ||
|-
| 28|| || || || ||
|-
| 29|| || || || ||
|-
| 30|| || || || ||
|-
| q || 1/q || q,1 ||  ||&lt;math&gt;0.(0^{q-1}1,) , \  0.(0^{q-2}10,) &lt;/math&gt; ||
|}

=comparison=

{| cellspacing=&quot;0&quot; cellpadding=&quot;15&quot; style=&quot;width:100%; vertical-align:top; margin:0.8em 0; border: 1px solid SlateBlue; background:#F7F7FF;{{Text default color}};&quot;
|style=&quot;vertical-align:top; border-right:1px dashed SlateBlue&quot;|

&lt;syntaxhighlight lang=txt&gt;
 Math notation
&lt;/syntaxhighlight&gt;
&lt;math&gt;square : \mathbb{C} \to  \mathbb{C}&lt;/math&gt;

&lt;math&gt;c_e \leftarrow e^c+c_0&lt;/math&gt;


|style=&quot;vertical-align:top; border-right:1px dashed SlateBlue&quot;|

&lt;syntaxhighlight lang=c&gt;
// c without complex type
cx_e = exp(creal(c)) * cos(cimag(c)) + realpart(c0); // real part of c_e
cy_e = exp(creal(c)) * sin(cimag(c)) + imagpart(c0); // imag part of c_e

&lt;/syntaxhighlight&gt;
|style=&quot;vertical-align:top; border-right:1px dashed SlateBlue&quot;|
&lt;syntaxhighlight lang=c&gt;
// c with complex type
complex double map(complex double c) {
return c = cexp(c) + c0; }

&lt;/syntaxhighlight&gt;


|}

=Sources of informations=
* printed:
** books
** journals
* (mostly) not printed ( online, but some online can also be printed)
** wikipedia 
** google search
** [https://github.com/gleitz/howdoi CLI search: howdoi]
** OpenChet GPT
** [https://iq.opengenus.org/ iq.opengenus.org]


See also
* synthetic data generation (SDG) for AI training
** Computer-generated imagery (CGI) = technology or application of computer graphics for creating or improving images

=AI=
* [https://vanceai.com/image-enhancer/ vanceai image-enhancer]
* [https://openai.com/dall-e-2 dall-e-2 = DALL-E image generation ]
* midjourney
** [https://midjourney.gitbook.io/docs/ midjourney doc]
** [https://www.midjourney.com/home/?callbackUrl=%2Fapp%2F midjourney app]
** [https://www.aiphotomaker.art/home aiphotomaker]
* [https://lexica.art/ lexica]
* [https://playgroundai.com/ playground ai ]
* [http://get3dfrom2d.com/ 3D from 2D]


AI art engines: Midjourney (good control through text), Lexica (great at generating stylized beauty), PlaygroundAi (based on Stable Diffusion).

Image-to-text engines (describe images in words): Midjourney's &quot;describe&quot; command, CLIP, Replicate.

Visual libraries of artists: Midlibrary.

Prompt marketplaces: Promptbase.

Stock images: Unsplash.

=SE=
* [https://math.stackexchange.com/editing-help math.stackexchange : editing]
* [https://math.meta.stackexchange.com/questions/1773/do-we-have-an-equation-editing-howto math.meta.SE question: do-we-have-an-equation-editing-howto ?]
* [https://math.meta.stackexchange.com/questions/5020/mathjax-basic-tutorial-and-quick-reference math.meta.SE question: mathjax-basic-tutorial-and-quick-reference ]
* [https://meta.stackexchange.com/questions/8231/are-answers-that-just-contain-links-elsewhere-really-good-answers/8259 meta.stackexchange question: are-answers-that-just-contain-links-elsewhere-really-good-answers ?]


console
* [https://meta.stackoverflow.com/questions/273049/stack-snippets-console-output stack-snippets-console-output]
* [https://meta.stackoverflow.com/questions/358992/ive-been-told-to-create-a-runnable-example-with-stack-snippets-how-do-i-do runnable-example-with-stack-snippets]
* [https://meta.stackexchange.com/questions/239706/add-a-console-to-stack-snippets add-a-console-to-stack-snippets]

=mapping=
 three methods for making a conformal mapping:
* Using complicated Schwarz-Christoffel. See the work of Driscoll and Trefethen, for example, https://pdfs.semanticscholar.org/ec28/b851707a35630faf58fdb5690f31cc814b15.pdf , references thereto, and their subsequent work, e.g., https://arxiv.org/abs/1911.03696 .
*  Use Stephenson's circle packing method, for example, http://www.cs.jhu.edu/~misha/Fall09/Stephenson97.pdf , and references thereto.
*  Use Marshall's &quot;ZIPPER&quot; algorithm. Examples are visible here: http://sites.math.washington.edu/~marshall/zipper.html . More recent work on ZIPPER: https://arxiv.org/abs/math/0605532 .


==mandelbrot==

https://www.youtube.com/watch?v=TJXwEIzyoq8


I use this formular:  Z ← Zⁿ + F(C)  where  F(C) is a complex function of the screen coordinate C.

If F does not depend on Z, it means that F(C) can be calculated before the starting of the iteration process. Which makes calculations faster.  In this video F(C) = [Rot(C, u∙sin(v))]ᵐ

Rot( ) is a complex function that rotates a complex number ( C ) by an angle (  u∙sin(v) ). v is the angle of the C vector with the x-axis. m, u and n are real numbers that I can change during the video.

I make the following morphing:
(n, m, u) = (2, 1, -10) → (2, 1, 0) → (3, 1, 10) → (3, 1, 0) → (4, 1, -10) → (4, 1, 0) → (5, 1, 5) → 
(5, 1, 0) → (6, 1, -5) → (6, 1, 0) → (6, 1, 5) → (2, -5, 0) → (2, -4, 10) → (2, -4, 0) → (2, -3, -10) →
(2, -3, 0) → (2, -2, 6) → (2, -2, 0) → (2, -1, -6) → (2, -1, 0) → (2, 1, 6) → (2, 1, 0) → (2, 1, -10)


==viewer==
* [https://www.falstad.com/complexviewer/ falstad : complex viewer] JS
* [http://davidbau.com/conformal/ david bau : conformal/#z]
==examples==
* [https://www.geogebra.org/m/mugcuvk7 Mappings of the circle to the upper/lower half plane] &lt;math&gt;z \to e^{i*3.14} \frac{z - z_0}{z - \bar{z_0}} &lt;/math&gt; where &lt;math&gt; z_0 = 1*i&lt;/math&gt; and &lt;math&gt; \bar{z_0} = -1*i&lt;/math&gt;
* [https://www.geogebra.org/m/xtueknna  geometry of some complex functions Author:Walter Füchte]
* [https://www.geogebra.org/m/kCxvMbHb Moebiusebene Author:Walter Füchte]
* The map  &lt;math&gt;t \to e^{it}&lt;/math&gt;   wraps the real axis around the unit circle (inf  many times)
* [https://www.geogebra.org/m/DgmYHpsy Complex mappings Author:Juan Carlos Ponce Campuzano] f(z) = u(x,y) + i v(x,y).
* [https://mabotkin.github.io/complex/ complex mapper]
* Images of a square grid of size [-pi,pi]x[-pi,pi]  under the (conformal) map  &lt;math&gt;z \to \cot(z)&lt;/math&gt;. The image of the lines of constant real part accumuate round the points +-i. https://functions.wolfram.com/ElementaryFunctions/Cot/visualizations/4/
* You know that there is a conformal mapping from the unit disk to the upper half plane given by: &lt;math&gt;z \mapsto -i\frac{z-i}{z+i}&lt;/math&gt;. But then you know that the transformation &lt;math&gt;z \mapsto \sqrt z&lt;/math&gt; taking the principal value sends the upper half plane to the region you are desiring. Reversing these mappings gives: &lt;math&gt;w \mapsto \frac{iw^2+1}{-w^2-i}&lt;/math&gt; Which you will see is a conformal mapping sending the first quadrant to the unit disk. &lt;ref&gt;[https://math.stackexchange.com/questions/298075/find-conformal-mapping-from-sector-to-unit-disc math.stackexchange question: find-conformal-mapping-from-sector-to-unit-disc]&lt;/ref&gt;
** https://i.stack.imgur.com/r0Lno.jpg
** https://i.stack.imgur.com/YsIHj.jpg
** https://i.stack.imgur.com/a08mS.jpg

==area==
https://math.stackexchange.com/questions/2063137/series-related-to-the-mandelbrot-set

Despite expanding finite iterations, there's a series maps the exterior of a unit disk to the exterior of the $M$ set.

&lt;math&gt;
 \begin{align}
   \psi(z) &amp;= z+\sum_{m=0}^{\infty} \frac{\beta_{0,m+1}}{z^m} \\
   z_{n} &amp;= \sum_{m=0}^{\infty} \beta_{n,m} z^{2^n-m} \\
   &amp;= z^{2^{n}}+o(1)
 \end{align}
&lt;/math&gt;


[http://gdz.sub.uni-goettingen.de/dms/load/img/?PID=GDZPPN001185500 John H. Ewing, Glenn Schober, The area of the Mandelbrot Set]

Strictly speaking, we won't say the iteration converges when the final states are oscillating. Hence, **not all** the points on the Mandelbrot set converge to a limit.  All points in $n$-periodic cycles $(n&gt;1)$ or chaotic bands are **bounded**, so they belong to the Mandelbrot set but **do not converge**.

If you insist for how interior of M is mapped to its final states.  Please see derivation about period 1 cycle and its final state below:


In conclusion,
&lt;math&gt;c=\frac{re^{i\phi}}{2}-\frac{r^2e^{2i\phi}}{4}&lt;/math&gt; maps to &lt;math&gt;z=\frac{re^{i\phi}}{2}&lt;/math&gt; 

where 
* &lt;math&gt;(r,\phi) \in [0,1] \times [0,2\pi)&lt;/math&gt;

For period one cycle, z and c can be expressed in quadratic:
&lt;math&gt;z^2-z+c=0&lt;/math&gt;

Taking the branch enclosing the super-attractive point c=0,

&lt;math&gt;\begin{align}
    z &amp;= \frac{1-\sqrt{1-4c}}{2} \\
    &amp;= \sum_{k=1}^{\infty} \frac{(-1)^{n-1}c^{n}}{2^{2n-1}}
       \binom{\frac{1}{2}}{n} \\
    &amp;= c+c^2+2c^4+5c^6+14c^8+42c^{10}+\ldots
  \end{align}
&lt;/math&gt;

which has the radius convergence of &lt;math&gt;\dfrac{1}{4}&lt;/math&gt;.

The boundary of the mapping:

$c=\frac{e^{i\theta}}{4} \mapsto
   z=\frac{1-\sqrt{|\sin \frac{\theta}{2}|+|\sin \frac{\theta}{2}|^2}}{2}-
     \frac{i\operatorname{sgn} (\sin \theta) \sqrt{|\sin \frac{\theta}{2}|-|\sin \frac{\theta}{2}|^2}}{2}$$

 - The iteration and series agree only when $|c| \le \dfrac{1}{4}$.

 &gt; Below is the comparison between the exact iterations (blue) and the series summation (red):

 [![enter image description here][6]][6]

 &gt; The green boundaries refer pre-image and image enclosed for period two cycle.

 [![enter image description here][7]][7]

 - Animation of successive iterations of the Mandelbrot Set:

 [![enter image description here][8]][8]


  [1]: https://i.stack.imgur.com/cORV2.jpg
  [2]: 
  [3]: https://i.stack.imgur.com/aZbQV.jpg
  [4]: https://i.stack.imgur.com/jE7kl.jpg
  [5]: https://i.stack.imgur.com/kBhwg.jpg
  [6]: https://i.stack.imgur.com/mgRaQ.jpg
  [7]: https://i.stack.imgur.com/ojdZL.jpg
  [8]: https://i.stack.imgur.com/5SsqA.gif

==Riemann mapping ==
* Construction of the Riemann mapping by steepest descent along Green's function


===ChatGPT===
Computing the Riemann mapping of a hyperbolic component of the Mandelbrot set can be a challenging task, as it involves solving a number of complex analytic problems. However, there are a few general steps that can be followed to compute a Riemann mapping of a given hyperbolic component:

Identify the hyperbolic component: The first step is to identify the hyperbolic component that you wish to map. This typically involves finding the boundary of the component and determining its connectivity.

Find a conformal map from the component to the unit disk: The next step is to find a conformal map from the hyperbolic component to the unit disk. A conformal map is a holomorphic function that preserves angles, which is necessary to maintain the topological properties of the component. There are various methods to find such a conformal map, like the method of the kernel function, or the method of the half-plane.

Compute the Riemann mapping: Once a conformal map from the hyperbolic component to the unit disk has been found, the Riemann mapping can be computed by composing the conformal map with a suitable automorphism of the unit disk.

Verify the Riemann mapping: The final step is to verify that the computed Riemann mapping is a bijection and that it preserves the topological properties of the hyperbolic component.

It's worth noting that the above steps are very simplified and the actual process of finding the Riemann mapping can be quite involved and require a deep understanding of complex analysis. Also, in the case of the Mandelbrot set, the boundary of the hyperbolic component is fractal in nature and it's not clear cut, so it's not easy to identify it.

It is also important to note that this process is generally not an explicit one, meaning that it may not be possible to write down an explicit formula for the Riemann mapping in closed form, it is usually obtained via numerical methods.
------------------------------------------------------

The method of the kernel function is a technique for finding a conformal map from a simply connected region in the complex plane to the unit disk. The method is based on the idea of finding a special function called the kernel function, which can be used to construct the desired conformal map.

The basic idea behind the method is to find a function f(z) that satisfies the following conditions:

f(z) is holomorphic and non-constant on the region of interest
f(z) maps the region to the unit disk
f(z) maps the boundary of the region to the unit circle
The function that satisfies these conditions is called the kernel function. The conformal map from the region to the unit disk is then given by the function g(z) = f(z) / f'(z0), where z0 is an arbitrary point in the region.

To find the kernel function, one typically starts by assuming that it has a certain form, such as f(z) = (z - z0)^k g(z) where k is a positive integer and g(z) is a holomorphic function on the region. Then one can use complex analysis techniques, such as the Schwarz reflection principle, to find the appropriate value of k and the function g(z) that make f(z) a kernel function.

It's worth noting that this method can be quite involved and requires a deep understanding of complex analysis. Also, finding the kernel function may not be possible in all cases, and finding a good approximation of it may be challenging.

------------------
The method of the half-plane is another technique for finding a conformal map from a simply connected region in the complex plane to the unit disk. This method is based on the idea of mapping the region to a half-plane and then mapping the half-plane to the unit disk.

The basic idea behind the method is to find a function f(z) that maps the region of interest to the upper half-plane and that satisfies the following properties:

f(z) is holomorphic and non-constant on the region of interest
f(z) maps the region to the upper half-plane
f(z) maps the boundary of the region to the real axis
Once we have this function, we can then use the well-known Moebius transformation that maps the upper half-plane to the unit disk, given by g(z) = (z-i)/(z+i)

The final conformal map from the region of interest to the unit disk is the composition of f(z) and g(z) which is g(f(z))

As with the kernel function method, finding a good approximation of f(z) may be challenging and it may not be possible to find it in all cases.

It's also worth noting that this method can be quite involved and requires a deep understanding of complex analysis. The method of the half-plane is often used to find conformal maps of regions that have some special symmetry, such as regions that are symmetric with respect to the real axis.
===basilica===
https://arxiv.org/abs/1201.4225 A Thompson Group for the Basilica by James Belk, Bradley Forrest
A Riemann map on the central component.


Basically, the answer is that I used inverse images to compute a very large number of points with known Bottcher coordinates, and then drew curves through the right sequences of points.

Here is a summary of the procedure I used for drawing equipotentials and external rays for a quadratic Julia set:

1.  Start with a large number (say 3 * 2^13) of equally spaced sample points on a circle of large radius (say R = 2^16) centered at the origin.  Note that this circle is basically an equipotential for the Julia set, since the radius is so large.

2.  Compute an equal number of points on the inverse image of this circle (which is again basically an equipotential whose radius is the square root of R).  Note that each of the original points has two preimages, so it must be worked out in each case which preimage to use.

3.  Iterate step 2 to produce sample points on a large number (say 50) of equipotentials that converge to the Julia set.

This lets you draw '''the equipotentials''' with ease.  


If you want to draw '''the external rays''', it works to draw a piecewise-linear path  between corresponding points on different equipotentials.  Of course, the resulting external rays will be straight between the sample points, but you can fix this by using more than one orbit of equipotentials.

'''The Riemann map for the central component for the Basilica''' was drawn in essentially the same way, except that instead of starting with points on a big circle, I started with sample points on a circle of small radius (e.g. 0.00001) around the origin.

=analysis=

Problem solving
* brute-force analysis
* Trial and error


=2D computer graphic =
* [https://www.falstad.com/matrix/ matrix viewer 2D transformatikon by Paul Falstad]
* [[:w:Glossary_of_computer_graphics|Glossary_of_computer_graphics in wikipedia]]
* [https://www.youtube.com/watch?v=HEFaRqI8TQw&amp;t=869s Transformations of Functions  MathWithMrsGA]
* [https://itmedia.pl/kategoria-produktu/sprzet/komputery-i-laptopy/przeznaczenie-komputery-i-laptopy/ IT media]
* tablica ( matrix) 2d i uzycie [[:en:w:Kernel_(image_processing)|kernel]]


==rendering==
* raytracing
* raymarching
* rasterization 


==csfml==
&lt;pre&gt;
sudo apt-get install libsfml-dev
sudo apt-get install libcsfml-dev
&lt;/pre&gt;

==hdr==
[[User:Soul_windsurfer#HDR_2|HDR description]]

== printing==

'''Poster'''
* color mode = CMYK. Work in CMYK rather than RGB or convert to CMYK, icc profile : [https://color.org/fogra39.xalter Coated FOGRA 39]
* Your poster should be easy to read from at least 5 feet (7.5 meters) away
* The resolution: typical dpi for posters is 300 dpi ( at least 300 dpi for best results). 2400 dpi or more for large posters.
* Standard poster sizes in inches are 11x17, 18x24, and 24x36. Big range is between 18 inches by 24 inches.
* You have two choices for poster printing: digital or litho. 


Links
* [[:w:Category:Quality issues in printing|Category:Quality issues in printing in wikipedia]]
* [https://graphicdesign.stackexchange.com/questions/16512/how-to-prepare-a-design-for-cmyk-printing graphicdesign.stackexchange questions: how-to-prepare-a-design-for-cmyk-printing]
* [https://graphicdesign.stackexchange.com/questions/2984/what-kind-of-black-should-i-use-when-designing-for-cmyk-print graphicdesign.stackexchange  question: what-kind-of-black-should-i-use-when-designing-for-cmyk-print]
* [https://graphicdesign.stackexchange.com/questions/24648/identifying-printing-quality-issues graphicdesign.stackexchange  question: identifying-printing-quality-issues]
* [https://fractalforums.org/discuss-fractalforums/5/printing-big-fractals/1731 fractalforums.org : printing-big-fractals]
* [https://www.youtube.com/watch?v=PpmZjPljPvw printing big fractals  by peter]: a rendered  170mb file I received  to produce am image at 200 dpi 57 x 33 inches. The printer is an HP designjet 4500ps I rebuilt and its printing onto 180gsm coated paper. It will print up to 1067 mm x any length.

===poradnik===
https://forum.dobreprogramy.pl/t/inkscape-kolory-cmyk/510928/7

Teoretycznie się da ale ani to wygodne ani szybkie. Zakładam że w Inkscapie przygotowujesz rysunek wektorowy i tym wektorom chcesz nadać kolory cmykowe. Po pierwsze zainstaluj w systemie profile CMYK, oczywiście najlepiej te które dostaniesz od drukarni ale praktyka mówi że drukarnia nigdy nie wie jaki profil użyć więc jeśli jeszcze nie masz żadnych profili cmykowych to zainstaluj te z http://www.eci.org. 326

Ja używam ISOcoated_v2_eci.icc to jest profil o zafarbieniu 340 (o ile dobrze pamiętam), gdybyś ich tam nie znalazł to tutaj masz linka bezpośredniego z mojego serwera: ftp://ttmath.org/pub/color_management/profile_cmyk_dla_programow/

Taki profil instalujesz sobie w systemie, w moim przypadku kopiuje je do odpowiedniego katalogu:

/home/tomek$ ls -1 .local/share/color/icc

27MP65.icm

ISOcoated_v2_300_eci.icc

ISOcoated_v2_eci.icc

PSO_Uncoated_ISO12647_eci.icc

eciRGB_v2.icc

eciRGB_v2_ICCv4.icc
Teraz konfigurujesz inkscape aby używał odpowiedniego profilu, screenshot: 

 
Następnie we właściwościach dokumentu Inkscepa w zakładce ‘kolor’ dodajesz odpowiedni profil:


Teraz w Inkscapie przy ustawianiu kolorów dla obiektów uaktywni się zakładka CMS (nie CMYK), na zakładce CMS z listy rozwijanej wybierzesz nasz profil i wtedy pojawią się cztery suwaczki którymi ustawiasz jaki kolor ma być w wyeksportowanym pliku. Jak zauważysz będziesz mógł zmieniać także kolor przy pomocy zakładki RGB albo CMYK ale te ustawienia będą tylko poglądowe na ekranie to co ma się wyeksportować to ustawiamy na zakładce CMS. Zrobiłem prosty dokument w którym na górze są cztery kwadraty w pełnych cmykowych kolorach oraz na dole tekst w 100 procentowym czarnym: 

 
Nie ma jednak tak dobrze, to jeszcze nie koniec. Inkscape będzie używał naszego cmyka ale tylko w dokumentach SVG, w tej chwili nie potrafi jeszcze wyeksportować cmykowego dokumentu PDF. Z pomocą przyjdzie nam Scribus. W Inkscapie zapisujemy dokument *.svg, najlepiej wybrać opcję ‘czysty dokument svg’ aby Inkscape nie dodawał zbędnych atrybutów a następnie w Scribusie importujemy dokument SVG i eksportujemy cmykowego PDFa. Oczywiście na początku wstępna konfiguracja dokumentu: 

 
I po konfiguracji wybieramy opcję Plik -&gt; Importuj -&gt; Pobierz plik wektorowy… Tu jednak nastąpi problem, Scribus nie potrafi wczytać wszystkich właściwości obiektów (pędzle, wypełnienia itp) które ustawi Inkscape. Możemy to obejść otwierając dokument svg w edytorze tekstu bo to przecież jest zwykły xml i usuwając pare nadmiarowych styli które wstawił Inkscape: 

 
A tak wygląda dokument po usunięciu styli: 

Teraz ponownie próbujesz zaimportować plik do Scribusa i tym razem się udaje: 

 
I już możesz wyeksportować plik pdf: 

 
Zauważ że eksportuję jako PDFX, dlaczego to zakładam że wiesz. I tutaj końcowy efekt naszych prac: http://tmp.ttmath.org/inkscape_cmyk/rysunek_cmyk.pdf 123

Możesz ten plik otworzyć w programie graficznym obsługującym cmyka (przy imporcie uważaj aby była zaznaczona konwersja z cmyka) i po imporcie sprawdzić kolory, kwadraty będą miały czyste kolory cmykowe,  odpowiednio pierwszy z lewej od góry: (100, 0, 0, 0), w środu u góry (0, 100, 0, 0) i tak dalej a tekst będzie miał tylko setke czarnego.

Jeśli w swojej pracy masz bitmapy to je umieszczasz w Scribusie, Inkscape chyba nie da rady wyeksportować bitmapy cmykowej.

Sam widzisz  że dać się da ale ani to wygodne a i możliwość popełnienia błędu duża szczególnie przy poprawkach pliku w edytorze tekstu.
===dpi===
DPI
* 300 dpi does the trick
* 600 dpi looks great with graphics
* 1200 dpi is ready to be sent to the company executives
* 1440+ dpi is professional-level photographic print quality

=== Printing method===
* '''a litho print''' involves the printer making a set of 'plates' that are used to press the image to the paper. Creating these plates comes at a cost and doesn’t offer the immediacy of digital poster printing. The initial outlay can be expensive, but if you’re doing a large print run and want to output up to A1, it’s the process that offers a higher quality print and finish than digital printing.
* '''Digital printing''' with inkjet or laser printers is the cheaper and quicker of the two and good for smaller print runs. If budget is an issue and you’re not being too exacting over the quality, go with digital printing. This is also fine if you're not going above A3.


Links
* [https://www.lifewire.com/4-6-8-color-process-printing-1077448 lifewire : 4-6-8-color-process-printing by Jacci Howard Bear   Updated on November 25, 2019]

=== base ===
There are three main '''types of large posters''':
* Paper posters are the most common type of large poster. They are usually printed on high-quality paper and are a great way to make a statement. you can print it out onto some paper and laminate it.
* Vinyl posters are made of durable vinyl and are perfect for outdoor use.
* Fabric posters are made of lightweight fabric and are perfect for indoor use.


Paper 
* GSM stands for grams per square meter and determines how heavy the paper stock is

Different paper types for posters include:
* Gloss ( Gloss Art FSC or 150gsm ) – As the name suggests, this paper offers a glossy sheen to any poster. The shiny finish encourages an eye-catching look for your poster designs and is available in six different paper weights.
* Bond – 100% recycled and high-quality, bond paper is an environmentally-friendly poster option. It’s durable and available in two different weights at Solopress.
* Day Glo – For a fluorescent colour scheme, day glo posters are the go-to. With a luminous effect, this paper is perfect for making a huge impression.
* Light Box – When you’re using a back light to illuminate a poster advert, print it on light box paper. It’s the ideal method for use in cinemas, theatres and on the street.
* 170gsm Silk

=== size ===
There are five A poster sizes to choose from, each suiting a different purpose:
* A4 – Small, but with enough room to make an impact, A4 posters are a great option. Available in a huge selection of paper types and weights, they’re a versatile choice.
* A3 – If you’re looking for a little more room to play with, A3 can get your message across. It’s commonly seen indoors in bars or shop windows – the right mix of detail and white space make it especially eye-catching.
* A2 – This is the perfect size for gig and event posters. A2 posters can display snippets of information and leave enough room for impressive artwork and imagery.
* A1 – Our most popular choice at Solopress, A1 posters can super-size your message. Large fonts and grand designs are ideal for posters hanging in exhibition halls or museums.
* A0 – Over one metre in width, A0 posters can make a big impression on viewers. This size allows for large, eye-catching artwork and has space for lots of information.

A sizes (1.413 ratio):
* A4 Paper Poster Size: 8.5” x 11” = (21 x 29.7 cm) = 2 550 x 3 300 points ( at 300 dpi ) = 
* A3  = 420 x 297 mm = 42 x 29.7 cm = 16.54 x 11.69 in = 4 962 x 3 507 points ( at 300 dpi)
* A2 = 594 x 420 mm = 59.4 x 42 cm = 23.39 x 16.54 in = 7 017 x 4 962 points ( at 300 dpi ) 
* A1 = 841 x 594 mm = 84.1 x 59.4 cm = 33.11 x 23.39 in = 9 933 x 7 017 points ( at 300 dpi)
* A0 = 1189 x 841 mm = 118.9 x 84.1 cm = 46.81 x 33.11 in = 14 043 x 9 933 points ( at 300 dpi)

B sizes ( 1.4 ratio)
* B2 = 707 x 500 mm = 70.7 x 50 cm = 27.83 x 19.69 in = 8 349 x 5 907 point ( at 300 dpi)
* B1 = 1000 x 707 mm = 100 x 70.7 cm = 39.37 x 27.83 in = 
* B0 = 1400 x 1000 mm 140 x 100 cm = 55.12 x 39.37 in = 


https://www.canva.com/sizes/poster/

SIZE	DIMENSION
Smallest	 8.5×11 in = 21.59 × 27.94 cm
Small	    11 × 17 in = 27.94 × 43.18 cm
Medium	    18 × 24 in = 45.72 × 60.96 cm 
Large	    24 × 36 in = 60.96 × 91.44 cm
Movie	    27 × 40 in = 68.58 × 101.6 cm
Bus Stop	40 × 60 in = 101.6 × 152.4 cm

=== unit system===
* The United States uses the Imperial system, which comes from the old British Imperial System. 
* The rest of the world uses the Metric system, developed in the late 18th century to unify all confusing measurements systems
===file===
* format pdf ver. 1.3. 
* https://profesjonalnydruk.pl/pliki-do-druku/
* https://wydrukujemy.to/pliki-do-druku/
* https://www.printworld.com/pl/plakat-a2-pion-1s.pdf
* https://drukarniakursor.pl/przygotowanie-do-druku/
* https://www.walstead-ce.com/wp-content/uploads/2019/05/SPIN01_Przygotowanie-materia%C5%82%C3%B3w-do-druku.pdf
* https://coloursfactory.pl/app/uploads/2021/04/cf-specyfikacja-techniczna-PL-A4_www.pdf
* https://graphicdesign.stackexchange.com/questions/143024/how-to-check-if-a-pdf-file-is-in-rgb-or-cmyk

Ubuntu: 
* GIMP - no CMYK
* Krita ( CMYK)
* Krita nie ma możliwości eksportu PDF, ani nie jest taka planowana. Aby utworzyć plik PDF z obrazami z Krity, należy użyć Scribus.
* Scribus supports professional publishing features, such as CMYK colors, spot colors, ICC color management and versatile PDF creation
** [https://wiki.scribus.net/canvas/Your%20first%20PDF%20form%20with%20Scribus Your first PDF form with Scribus]
** [https://wiki.scribus.net/canvas/Color%20Management%20setup scribus: Color Management setup]

===TAC or TIC or TIL===
* https://www.prepressure.com/design/basics/tic
* https://www.cummingsprinting.com/technotes/total-area-coverage/
* https://graphicdesign.stackexchange.com/questions/73233/total-ink-coverage-on-cmyk-digital-printing
* https://callingcardbooks.com/whats-total-area-coverage-tac-and-why-does-ingramspark-care/
* https://creativepro.com/reducing-the-total-ink-limit-cmyk-images-using-photoshop/
* https://stackoverflow.com/questions/3092356/calculate-cmyk-coverage-on-pdf
* https://stackoverflow.com/questions/6241282/converting-pdf-to-cmyk-with-identify-recognizing-cmyk?rq=1
* nafarbienie : https://grafmag.pl/artykuly/cmyk-i-rgb-roznice-w-wydruku
When several colors are printed on top of each other, there is a limit to the amount of ink or toner that can be put on paper. This maximum total dot percentage is referred to as either
* TIC (Total Ink Coverage) 
* TAC (ang. Total Area Coverage, pl. Suma wartości tonalnych) 
* [https://aldertech.com/what-is-the-right-total-ink-limit-setting/ TIL ( TOTAL INK LIMIT )]
When a designer ignores this technical limitation, the ink that gets laid down last won’t attach properly to the previous layers, leading to muddy browns in neutral areas. The ink also won’t dry properly on the press sheets. This can cause set-off where the ink of a still wet sheet rubs off on whatever is stacked on top of it.

technique
* Under Color Removal (UCR) does indeed reduce the amount of ink used to print grayish colors. 
* Gray Component Replacement (GCR) that replaces equal portions of cyan, magenta and yellow by black in all colors. It can lead to even bigger ink savings.


SWOP = [[:w:Specifications_for_Web_Offset_Publications|Specifications for Web Offset Publications]]

===color ===
* color separation = split color to 4 ( or more) inks
* https://www.castleprint.co.uk/spot-and-process-colours-explained/
* RGB -&gt; CMYK : 
* Color in printing
** spot color = colour chosen from a colour swatch, like standard Pantone© colours swatch
** Process Colour ( CMYK):  
*** Pantone 032 colour split to CMYK: Cyan = 0% – Magenta = 90% – Yellow = 86% – Black = 0%
*** Pantone 247 is made up of 36% Cyan &amp; 100% Magenta, with no yellow or black (K).


industry standards in the classification of spot color systems
* [[Pantone]], the dominant spot color printing system in the [[United States]] and [[Europe]]. PMS = Pantone Matching System
* [[Toyo Ink|Toyo]], a common spot color system in [[Japan]].
* [[Dainippon Ink &amp; Chemicals|DIC]] Color System Guide, another spot color system common in Japan – it is based on [[Munsell color system|Munsell color theory]].&lt;ref&gt;[http://www.theinformedillustrator.com/2012/09/process-versus-spot-color.html The Informed Illustrator: Digital Spot Color Systems]&lt;/ref&gt;
* [[ANPA color palette|ANPA]], a palette of 300 colors specified by the [[Newspaper Association of America|American Newspaper Publishers Association]] for spot color usage in [[newspapers]].
* [[GCMI]], a standard for color used in package printing developed by the Glass Packaging Institute (formerly known as the Glass Container Manufacturers Institute, hence the abbreviation).
* [[HKS (colour system)|HKS]] is a color system which contains 120 spot colors and 3,250 tones for coated and uncoated paper. HKS is an abbreviation of three German color manufacturers: Hostmann-Steinberg Druckfarben, Kast + Ehinger Druckfarben and H. Schmincke &amp; Co.
* [[RAL (color space system)|RAL]] is a color matching system used in Europe. The so-called RAL CLASSIC system is mainly used for varnish and powder coating.
Because each color system creates their own colors from scratch, spot colors from one system may be impossible to find within the library of another.


[https://www.lifewire.com/use-spot-or-process-colors-1077446 When to Use]:
* Spot Colors (Such as PMS Colors)
* Process Colors (CMYK)
* Process and Spot Colors Together
* 6-Color or 8-Color Process Printing


Black in cmyk
* https://graphicdesign.stackexchange.com/questions/130388/where-does-black-come-from-in-cmyk-color-mode
* https://graphicdesign.stackexchange.com/questions/2984/what-kind-of-black-should-i-use-when-designing-for-cmyk-print
* https://graphicdesign.stackexchange.com/questions/668/whats-the-difference-between-cmyk-black-and-rgb-black?noredirect=1&amp;lq=1
* https://graphicdesign.stackexchange.com/questions/12860/when-should-i-use-rich-black
====problems====
* https://www.clearprint.com/cmyk-printing-problems-solved/

==color==
* a '''web‑safe colors''': The web‑safe colors are the 216 colors used by browsers regardless of the platform. The browser changes all colors in the image to these colors when displaying the image on an 8‑bit screen. The 216 colors are a subset of the Mac OS 8‑bit color palettes. By working only with these colors, you can be sure that art you prepare for the web will not dither on a system set to display 256 colors.&lt;ref&gt;[https://helpx.adobe.com/photoshop/using/choosing-colors.html helpx.adobe photoshop:  using/choosing-colors]&lt;/ref&gt;
* a '''non-printable color''': Some colors in the RGB, HSB, and Lab color models cannot be printed because they are out-of-gamut and have no equivalents in the CMYK model.
* a '''spot color''': 

===spot color libraries===
The Adobe Color Picker supports the following color systems ( libraries):
* ANPA-COLOR: Commonly used for newspaper applications. The ANPA-COLOR ROP Newspaper Color Ink Book contains samples of the ANPA colors.
* DIC Color Guide: Commonly used for printing projects in Japan. For more information, contact Dainippon Ink &amp; Chemicals, Inc., in Tokyo, Japan.
* FOCOLTONE: Consists of 763 CMYK colors. Focoltone colors help avoid prepress trapping and registration problems by showing the overprints that make up the colors. A swatch book with specifications for process and spot colors, overprint charts, and a chip book for marking up layouts are available from Focoltone. For more information, contact Focoltone International, Ltd., in Stafford, United Kingdom.
* HKS swatches: Used for printing projects in Europe. Each color has a specified CMYK equivalent. You can select from HKS E (for continuous stationery), HKS K (for gloss art paper), HKS N (for natural paper), and HKS Z (for newsprint). Color samplers for each scale are available. HKS Process books and swatches have been added to the color system menu.
* TRUMATCH: Provides predictable CMYK color matching with more than 2,000 achievable, computer-generated colors. Trumatch colors cover the visible spectrum of the CMYK gamut in even steps. The Trumatch Color displays up to 40 tints and shades of each hue, each originally created in four-color process and each reproducible in four colors on electronic imagesetters. In addition, four-color grays using different hues are included. For more information, contact Trumatch Inc., in New York City, New York.


===contrast ratio===
* https://github.com/adobe/leonardo

===black===
* czernią 100K ( ang. black), a tzw. bogatą czernią ( ang. rich black). Efekt jest taki, że w druku zwykła czerń (100K) jest ciemnoszara zamiast czarna. Po to właśnie używa się rich blacka.
=== profile kolorów ===
* [http://www.eci.org/doku.php?id=en:downloads European Color Initiative (ECI)]
* https://www.colormanagement.org/index_en.html
*  print : Cmyku Coated FOGRA 39 dla profilu Print 
* RGB
** sRGB dla profilu Web ( został stworzony do wyświetlania kolorów m.in. w internecie i posiada najwęższy zakres możliwych barw, dzięki czemu kolory są wyświetlane w całej gamie bez względu na klasę monitora i karty graficznej użytkownika. Jeżeli przygotowujesz jakąkolwiek grafikę czy zdjęcie, które umieścisz w internecie — chcesz przypisać profil sRGB )
** Adobe RGB (1998) został stworzony jako większy brat sRGB, a jego zakres kolorów jest szerszy i służy głównie do opisywania kolorów na fotografiach (ogólnie mówiąc wszelkich skomplikowanych obrazach rastrowych, które mają być drukowane i obrabiane).
** jest Lab (właściwie CIELAB D50). Posiada najszerszy gamut spośród wszystkich przestrzeni jakie istnieją. Opisywanie kolorów w tej przestrzeni oparte jest na postrzeganiu koloru przez ludzkie oko. I chociaż traktowany jest jako niezależny od urządzenia, można powiedzieć, że jest zależny od oka ludzkiego. Lab jest najtrudniejszy do zrozumienia, ponieważ nie posiada tradycyjnych kanałów z pojedynczymi kolorami. Skrót Lab to trzy kanały — luminancja (Lightness), a (tinta) i b (temperatura). Lightness zawiera informację jedynie o luminancji obrazu (jego naświetlenia, jasności i jaskrawości). Kanał ten przypomina z grubsza czarno białą wersję obrazu i przyjmuje wartości od zera (czerń) do 100 (biel). Kanał “a” to oś zieleń — czerwień (a właściwie karmazyn), natomiast kanał “b” to oś żółcień — ciemny niebieski (zbliżony do fioletu). Na pierwszy rzut oka te osie barw nie mają większego sensu, ale w rzeczywistości są odzwierciedleniem realnych barw powstających przy padaniu światła słonecznego na rzeczywiste obiekty. Z tego też powodu regulacja balansu bieli w module wywoływania negatywów cyfrowych w Photoshopie oparta jest na osiach Lab. Oś “b” odzwierciedla temperaturę barwową światła (od żółtej czyli ciepłej, do niebieskiej czyli zimnej), natomiast oś “a” to tinta, która reguluje zabarwianie sceny w zależności od światła odbitego od obiektów (np. ciasne podwórko wśród kamienic wydaje się być niebieskawo-fioletowe). Tryb Lab jest niezmiernie użyteczny, jeśli chcemy korygować jedynie tonację naszego zdjęcia, ponieważ pracujemy wtedy na kanale Lightness, podczas gdy w RGB proces ten jest niemożliwy, gdyż tony są połączone z informacją o barwie w poszczególnych kanałach. Wykonując np. polecenie poziomy (levels) w trybie RGB, zmieniamy także kolory. Lab znakomicie nadaje się też do nasycania kolorów — pracujemy przecież na odseparowanych kanałach barw. Kolory w Lab są żywsze i bardziej klarowne niż podczas obróbki w RGB. Niestety Lab nie jest trybem powszechnym, nie można zapisać pliku jpeg w trybie Lab i ogólnie mówiąc bardzo mało aplikacji obsługuje ten tryb. Jest to środowisko stricte edycyjne. Po dokonaniu potrzebnych korekt w Lab, musimy przekonwertować nasz plik z powrotem do RGB czy innego trybu.
** profilem jest ProPhoto RGB, który ma najszerszy zakres gamutu i potrafi opisać całe bogactwo barw jakie tylko może zarejestrować matryca aparatu (nie do końca), przez co jest doskonałym wyborem jeśli chodzi o profesjonalną postprodukcję zdjęć i ich wydruk na wysokiej klasy drukarkach fotograficznych. Zarówno Adobe RGB jak i ProPhoto lepiej nadają się do obróbki zdjęć niż sRGB. Szczerze mówiąc różnica nie jest kolosalna, ale jeśli zależy nam na najwyższej możliwej jakości i elastyczności, lepiej obrabiać zdjęcia z powyższymi profilami, na samym końcu zamieniając go ewentualnie na sRGB.


[https://blog.psboy.pl/2009/05/wielka-trojka-rgb-cmyk-lab/ Wielka trójka — RGB, CMYK, Lab. Sebastian Kończak ]

===gray scale===
In computing image pixels are usually quantized to store them as unsigned integers, to reduce the required storage and computation. 

Some early grayscale monitors can only display up to sixteen different shades, which would be stored in binary form using '''4 bits'''.

But today grayscale images intended for visual display are commonly stored with '''8 bits per sampled pixel'''. This pixel depth allows 256 different intensities (i.e., shades of gray) to be recorded, and also simplifies computation as each pixel sample can be accessed individually as one full byte. 

However, if these intensities were spaced equally in proportion to the amount of physical light they represent at that pixel (called a '''linear encoding or scale'''), the differences between adjacent dark shades could be quite noticeable as banding artifacts, while many of the lighter shades would be &quot;wasted&quot; by encoding a lot of perceptually-indistinguishable increments. 

Therefore, the shades are instead typically spread out evenly on a '''gamma-compressed nonlinear scale''', which better approximates uniform perceptual increments for both dark and light shades, usually making these 256 shades enough to avoid noticeable increments.

==transformation==
* 2D
* 3D
** OpneGL


===notation===

In [[linear algebra]], a '''column vector''' with m elements is an &lt;math&gt;m \times 1&lt;/math&gt; [[Matrix_(mathematics)|matrix]] consisting of a single column of m entries, for example,
&lt;math display=&quot;block&quot;&gt;\boldsymbol{x} = \begin{bmatrix} x_1 \\ x_2 \\ \vdots \\ x_m \end{bmatrix}.&lt;/math&gt;

Similarly, a '''row vector''' is a &lt;math&gt;1 \times n&lt;/math&gt; matrix for some n, consisting of a single row of n entries,
&lt;math display=&quot;block&quot;&gt;\boldsymbol a = \begin{bmatrix} a_1 &amp; a_2 &amp; \dots &amp; a_n \end{bmatrix}. &lt;/math&gt;

{| class=&quot;wikitable&quot;
|-
! !! Row vector !! Column vector
|-
| '''Standard matrix notation'''&lt;br/&gt;(array spaces, no commas, transpose signs)
| align=center| &lt;math&gt; \begin{bmatrix} x_1 \; x_2 \; \dots \; x_m \end{bmatrix} &lt;/math&gt; 
| align=center| &lt;math&gt; \begin{bmatrix} x_1 \\ x_2 \\ \vdots \\ x_m \end{bmatrix} \text{ or } \begin{bmatrix} x_1 \; x_2 \; \dots \; x_m \end{bmatrix}^{\rm T} &lt;/math&gt; 
|}

&lt;gallery&gt;
Row_and_column_major_order.svg|Illustration of difference between row- and column-major ordering
&lt;/gallery&gt;


===gallery===
&lt;gallery&gt;
Lambert draw.png
Gnomonic draw.png
Scaled angle projection draw.png
Fisheye-view projection.png
Orthographic draw.png
Stereographic draw.png
Variable center projection draw.png
&lt;/gallery&gt;

===scaling or resizing===
* Resize a plane figure's linear dimensions by a scale factor s 
* When the size is changed, the object may also move
* If the scaling factor S is less than 1, then we reduce the size of the object ( contraction or reduction). If the scaling factor S is greater than 1, then we increase size of the object ( dilation or enlargement )
* [https://www.geogebra.org/m/JhaRDXZP Geogebra : Enlarging to a Scale Factor and Centre by Jonathan Robinson]
* [https://www.geogebra.org/m/hMNc4eES geogebra : Transformations  by DavidA]
* [[:w:Scaling_(geometry)|Scaling in geometry ( wikipedia)]]

Scaling of object by by a scale factor s = sx+ sy*i
 x’ = x * sx 
 y’ = y * sy.

Scaling
* Uniform (maintains the object’s proportions as it scales): sx = sy
* non-uniform: sx != sy


Resizing objects while maintaining a fixed centre point = Scaling object about their own center
* width' = width * sx
* height' = height * sy
* compute coordinate of corners from the center

===rotation===
When we rotate a shape one should know: 
* a centre of rotation
* the angle and units of the rotation
* the direction of rotation


====point====
* a rotation about the origin O by an angle θ 
* a 2D clockwise theta degrees rotation of point (x, y) around point (a, b) 


About origin:

 float s = sin(angle); // angle is in radians
 float c = cos(angle); // angle is in radians

For clockwise rotation :

 float xnew = p.x * c + p.y * s;
 float ynew = -p.x * s + p.y * c;

For counter clockwise rotation :

 float xnew = p.x * c - p.y * s;
 float ynew = p.x * s + p.y * c;


[https://gamedev.stackexchange.com/questions/111343/get-local-coords-from-global-coords Code in Java]
* global coordinate ( before rotation)
* local coordinate ( after rotation)
* origin = (pointX, pointY)
* 

&lt;syntaxhighlight lang=&quot;java&quot;&gt; 
public static double[] getLocalFromGlobal(int pointX, int pointY, int localX, int localY, float angle) {
    float px = pointX - localX;
    float py = pointY - localY;

    double cos = Math.cos((Math.PI / 180) * angle);
    double sin = Math.sin((Math.PI / 180) * angle);

    double finalX = (px * cos) + (py * sin);
    double finalY = -(px * sin) + (py * cos);
    return new double[]{finalX, finalY};
}
&lt;/syntaxhighlight&gt; 

[https://stackoverflow.com/questions/2259476/rotating-a-point-about-another-point-2d First subtract the pivot point (cx,cy), then rotate it (counter clock-wise), then add the point again.]

&lt;syntaxhighlight lang=&quot;c&quot;&gt; 
 POINT rotate_point(float cx,float cy, float angle, POINT p)
{
  float s = sin(angle);
  float c = cos(angle);

  // translate point back to origin:
  p.x -= cx;
  p.y -= cy;

  // rotate point
  float xnew = p.x * c - p.y * s;
  float ynew = p.x * s + p.y * c;

  // translate point back:
  p.x = xnew + cx;
  p.y = ynew + cy;
  return p;
}
&lt;/syntaxhighlight&gt;


&lt;syntaxhighlight lang=&quot;python&quot;&gt; 
def rotate(origin, point, angle):
    &quot;&quot;&quot;
    Rotate a point counter-clockwise by a given angle around a given origin.
    &quot;&quot;&quot;
    # Convert negative angles to positive
    angle = normalise_angle(angle)

    # Convert to radians
    angle = math.radians(angle)

    # Convert to radians
    ox, oy = origin
    px, py = point

    # Move point 'p' to origin (0,0)
    _px = px - ox
    _py = py - oy

    # Rotate the point 'p' 
    qx = (math.cos(angle) * _px) - (math.sin(angle) * _py)
    qy = (math.sin(angle) * _px) + (math.cos(angle) * _py)

    # Move point 'p' back to origin (ox, oy)
    qx = ox + qx
    qy = oy + qy

    return [qx, qy]


def normalise_angle(angle):
    &quot;&quot;&quot; If angle is negative then convert it to positive. &quot;&quot;&quot;
    if (angle != 0) &amp; (abs(angle) == (angle * -1)):
        angle = 360 + angle
    return angle
&lt;/syntaxhighlight&gt;

====object====
* [https://www.geeksforgeeks.org/2d-transformation-rotation-objects/ geeksforgeeks : 2d-transformation-rotation-objects]
* [https://stackoverflow.com/questions/20023209/function-for-rotating-2d-objects stackoverflow question: function-for-rotating-2d-objects]
* [https://gamedev.stackexchange.com/questions/178555/why-are-rotations-in-2d-game-engines-often-counter-clockwise-positive-systems gamedev.stackexchange question: why-are-rotations-in-2d-game-engines-often-counter-clockwise-positive-systems]

First, we need a function to rotate a point around origin.

When we rotate a point (x,y) around origin by theta degrees, we get the coordinates:

&lt;math&gt; (x*cos(\theta)-y*sin(\theta), x*sin(\theta)+y*cos(\theta))&lt;/math&gt;

If we want to rotate it around a point other than the origin, we just need to shift it so the center point becomes the origin.
Now, we can write the following function:

    from math import sin, cos, radians
    
    def rotate_point(point, angle, center_point=(0, 0)):
        &quot;&quot;&quot;Rotates a point around center_point(origin by default)
        Angle is in degrees.
        Rotation is counter-clockwise
        &quot;&quot;&quot;
        angle_rad = radians(angle % 360)
        # Shift the point so that center_point becomes the origin
        new_point = (point[0] - center_point[0], point[1] - center_point[1])
        new_point = (new_point[0] * cos(angle_rad) - new_point[1] * sin(angle_rad),
                     new_point[0] * sin(angle_rad) + new_point[1] * cos(angle_rad))
        # Reverse the shifting we have done
        new_point = (new_point[0] + center_point[0], new_point[1] + center_point[1])
        return new_point

Some outputs:

    print(rotate_point((1, 1), 90, (2, 1)))
    # This prints (2.0, 0.0)
    print(rotate_point((1, 1), -90, (2, 1)))
    # This prints (2.0, 2.0)
    print(rotate_point((2, 2), 45, (1, 1)))
    # This prints (1.0, 2.4142) which is equal to (1,1+sqrt(2))

Now, we just need to rotate every corner of the polygon using our previous function:

    def rotate_polygon(polygon, angle, center_point=(0, 0)):
        &quot;&quot;&quot;Rotates the given polygon which consists of corners represented as (x,y)
        around center_point (origin by default)
        Rotation is counter-clockwise
        Angle is in degrees
        &quot;&quot;&quot;
        rotated_polygon = []
        for corner in polygon:
            rotated_corner = rotate_point(corner, angle, center_point)
            rotated_polygon.append(rotated_corner)
        return rotated_polygon

Example output:

    my_polygon = [(0, 0), (1, 0), (0, 1)]
    print(rotate_polygon(my_polygon, 90))
    # This gives [(0.0, 0.0), (0.0, 1.0), (-1.0, 0.0)]
    

[https://gamedev.stackexchange.com/questions/86755/how-to-calculate-corner-positions-marks-of-a-rotated-tilted-rectangle In C by Aholio] 

 X = x*cos(θ) - y*sin(θ)
 Y = x*sin(θ) + y*cos(θ)
 
This will give you the location of a point rotated θ degrees around the origin. Since the corners of the square are rotated around the center of the square and not the origin, a couple of steps need to be added to be able to use this formula. First you need to set the point relative to the origin. Then you can use the rotation formula. After the rotation you need to move it back relative to the center of the square.


 &lt;syntaxhighlight lang=&quot;c&quot;&gt; 
// cx, cy - center of square coordinates
// x, y - coordinates of a corner point of the square
// theta is the angle of rotation

// translate point to origin
float tempX = x - cx;
float tempY = y - cy;

// now apply rotation
float rotatedX = tempX*cos(theta) - tempY*sin(theta);
float rotatedY = tempX*sin(theta) + tempY*cos(theta);

// translate back
x = rotatedX + cx;
y = rotatedY + cy;
&lt;/syntaxhighlight&gt;

===warp===
 &quot;A square is warped into a quarter-slice of a disk. The same transformation is again applied to the quarter-slice, and again to the resulting shape, repeatedly. A strange shape is created, with three spindly legs that appear to walk from corner to corner. This is the attractor of this particular transformation. [code]&quot; matthen

https://blog.matthen.com/
===composition===
A sequence of transformations can be combined into single one (composition, concatenation). The resulting matrix is called as composite matrix.

Advantage of composition :
* It transformations become compact.
* The number of operations is reduced.
* Rules used for defining transformation in form of equations are complex as compared to matrix.


the order in which the transforms are applied:
* is important 
* transforms are applied to objects in the reverse of the order in which they are given in the code (because the first transform in the code is applied to an object that has already been affected by the second transform).

== 2D normalized homogenous coordinate ==
Coordinate
* finite point &lt;math&gt;z&lt;/math&gt; on the complex plane &lt;math&gt;z \in \hat{\mathbb{C}}&lt;/math&gt; with [[:w:Cartesian coordinate system|Cartesian coordinate]] &lt;math&gt;z = x + y * i&lt;/math&gt;
* point r on the extended complex plane (= [[:w:Riemann sphere|Riemann sphere]] ) 
** 2D [[:w:homogenous coordinate|homogenous coordinate]]  &lt;math&gt;r = [s,t,u] &lt;/math&gt;
** normalized 2D homogenous coordinate &lt;math&gt;n = [v,w] &lt;/math&gt;


Special points
* [[:w:Origin (mathematics)|origin]] &lt;math&gt;z = 0&lt;/math&gt;
* [[:w:point at infinity|point at infinity]] 
** in homogenous coordinate : when last coordinate u is 1 &lt;math&gt; [s,t, 1] &lt;/math&gt; then it is a point at infinity 
** in normalized homogenous coordinate &lt;math&gt;[v, 1] &lt;/math&gt;


===Conversions===
* from [[:w:Cartesian coordinate system|Cartesian coordinate]] to [[:w:homogenous coordinate|homogenous coordinate]]
* from [[:w:homogenous coordinate|homogenous coordinate]] to normalized homogenous coordinate

* from normalized homogenous coordinate to [[:w:homogenous coordinate|homogenous coordinate]]

==== from homogenous to Cartesian coordinate ====
The original Cartesian coordinates are recovered by dividing the first two positions by the third. Thus unlike Cartesian coordinates, a single point can be represented by infinitely many homogeneous coordinates. Note that here not u  ( typical) but 1-u is used

The mapping from the sphere to the finite plane is 

If &lt;math&gt; u &lt; 1 &lt;/math&gt;
  &lt;math&gt;x = \frac{s}{1 - u}&lt;/math&gt;
  &lt;math&gt;y = \frac{t}{1 - u}&lt;/math&gt;
  &lt;math&gt;z = \frac{x + y*i}{1 - u}&lt;/math&gt;

If &lt;math&gt; u =  1 &lt;/math&gt; then z is  [[:w:point at infinity|point at infinity]]  &lt;math&gt; z = \infty &lt;/math&gt;

=deep=
* deep” pixels – those containing multiple samples per pixel (and a potentially differing number of them in each pixel)
* deep image = image with deep pixels
* [[:w:Color_depth#Deep_color_(30-bit)|Deep color in wikipedia]] = 30-bit color depth and more

=HDR=
High dynamic range (HDR) is a dynamic range higher than usual, synonyms are wide dynamic range, extended dynamic range, expanded dynamic range.


Types: 
* HDR TV / HDR Video 
** HD 
*** UHD = 4K = Ultra High Definition = ultra HD
** HDR-TV = Wider color gamut and contrast range than Standard Dynamic Range (SDR). Minimum 10-bit color depth and output at least 540 nits of peak brightness
*** four primary HDR formats are HDR10/10+, Dolby Vision, HLG, and Technicolor HDR
*** one need compatible equipment down the line ( from source, cables and all devices)  An internet speed of 15 to 25mbps is required for stable viewing.
* HDR photo
* HDR image


[https://www.w3.org/Graphics/Color/Workshop/slides/talk/kunkel SDR is a retronym that was established over the past 15 years to identify traditional content that uses:]
* gamma encoding
* more limited luminance ranges 
* WCG = Wider color gamut = color gamuts such as Rec. 709 or sRGB.


https://www.flatpanelshd.com/focus.php?subaction=showfull&amp;id=1559638820

https://www.lenovo.com/in/en/faqs/monitors-faqs/hdr-displays/
What is HDR? Without getting too deep into the technical details, an HDR display produces greater luminance and color depth than screens built to meet older standards. Here are some HDR basics:

HDR display luminance
Display luminance describes the amount of light it emits, which in turn determines the gap between the brightest and darkest pixels on the screen. The increased light produced by an HDR display makes its brightest pixels far brighter than before, further differentiating them from the darkest ones. This increased contrast ratio enables more subtle pixel-to-pixel changes and better image reproduction.

Luminance is measured in candelas/m2 or &quot;nits&quot; -- a term that's increasingly common in the technical specifications for both professional and consumer monitors and laptop displays. Several different standards have been published to define what can qualify as an HDR display, generally starting at 400 nits for laptops and rising to 1000 or even 10,000 nits for high-end professional monitors.

HDR display color depth
Color depth refers to how many bits of data each pixel of a display can utilize to produce the colors in an image or video. Before HDR, most displays topped out at 8-bit color. But the new HDR formats can process 10-bit (or even 12-bit) color, increasing the potential on-screen color variations exponentially.

It's all in the math. Whether directly or through what's called dithering, 8-bit color depth allows for 256 different shades of each primary color, making it possible to generate about 16.5 million color variations. 10-bit color bumps the number of shade options from 256 to 1024 -- increasing the maximum color variations to more than 1 billion!


[https://www.eizo.com/library/basics/pixel%20density%204k/ 4K resolution]
* DCI 4K is twice the 2048 x 1080 pixel resolution of projectors (4096 x 2160/approx. 17:9) and is the 4K resolution of the film industry. 
* UHD 4K (also called UHDTV 4K), on the other hand, is the 4K resolution of the television industry defined by the International Telecommunication Union (ITU). It has twice the horizontal resolution of 1920 x 1080 pixel full HD (3840 x 2160/16:9).


==hdr video==

HDR TV formats
* HDR10: Most widely used open standard for HDR with 10-bit color and generalized meta data
* Dolby Vision: Proprietary Dolby HDR technology promising 12-bit equivalent color and scene-by-scene meta data
* HDR10+: A new, proprietary HDR format being developed reportedly with frame-by-frame meta data
*  HLG (Hybrid Log Gamma, from BBC and NHK)
* Advanced HDR from Technicolor


HDR monitor : VESA's HDR standards for monitors: 
* VESA DisplayHDR 400 
* VESA DisplayHDR 1400


===game===
You need four things to enable HDR on your PC:
* A GPU that supports HDR
* A display that supports HDR
* A DisplayPort 1.4 or HDMI 2.0a (or newer) connection
* HDR content, such as a game or streaming service


https://displayhdr.org/

HDR on a PC.
* A monitor that’s DisplayHDR 1000 certified or a quality HDR television.
* A video card from the AMD RX 400, Nvidia GTX 900 series, or Intel integrated graphics found in Intel 7th-gen Core, or newer.
* An HDMI 2.0a, DisplayPort 1.4, or Thunderbolt 4 connection, or newer.
* Microsoft’s HEVC Extensions, which are sold on the Microsoft Store.
* HDR content, such as an HDR-compatible game or streaming service.

https://www.pcworld.com/article/394712/everything-you-need-to-know-about-hdr-on-your-pc.html


==image==
HDRI stands for High Dynamic Range Imaging, and is basically an image format that contains from the deepest shadow up to the brightest highlight information. 
* the LDR  an 'ordinary' digital image contains only 8 bits of information per color (red, green, blue) which gives you 256 gradations per color ( '''integers''' from 0 to 255 )  
* the HDR image format stores the 3 colors with '''floating point accuracy'''. Thus the 'depth' from dark to light per color is virtually unlimited. Using HDR images in a 3D environment will result in very realistic and convincing shadows, highlights and reflections. This is very important for realistic emulation of chrome for example.


High Dynamic Range (HDR) image was created by 
* merging LDR images ( photos) at different exposure ( multi-exposure HDR capture) = HDRI = High-dynamic-range imaging. In photography and videography,  is a technique that creates extended or high dynamic range (HDR) images by taking and combining multiple exposures of the same subject matter at different exposure levels. Combining multiple images in this way results in an image with a greater dynamic range than what would be possible by taking one single imagage ( photo)
* inverse tone mapping (ITM) a single exposure LDR image ( photo)
* High-dynamic-range rendering (HDRR or HDR rendering), also known as high-dynamic-range lighting, is the rendering of computer graphics scenes by using lighting calculations done in high dynamic range (HDR) =computer graphic


Image types
* photography = photo
* computer graphic 


HDR (high dynamic range) można krótko zdefiniować jako łączenie kilku zdjęć tej samej sceny, ale o różnym naświetleniu, w celu otrzymania jednego obrazu o powiększonym zakresie tonalnym (najciemniejszy punkt odpowiada takiemu punktowi na zdjęciu najciemniejszym, najjaśniejszy punkt odpowiada takiemu punktowi na zdjęciu najjaśniejszym). [https://blog.psboy.pl/2010/01/hdr-czy-tylko-tandetny-efekt/ hdr-czy-tylko-tandetny-efekt. Sebastian Kończak]


głębia bitowa urządzeń
* które obecnie używamy to osiem bitów na kanał, czyli 256 gradacji tonów. 
* Tymczasem HDR to 32 bity na kanał (ta wartość jest różna dla poszczególnych algorytmów i formatów zapisu) 


Urządzenia:
* nasze oko widzi w HDR, czyli szerokim zakresie tonów
* tymczasem aparaty fotograficzne (cyfrowe oczywiście też) „widzą” w mocno zawężonym zakresie LDR (low dynamic range)

Etapy:
* wykonać zdjęcia jednej sceny, najlepiej trzy i więcej klatek. 
* Przy fotografowaniu sceny korzystamy z opcji bracketingu w aparacie. Standardowe podejście to –2EV, 0 (domyślna ekspozycja zmierzona przez aparat), +2EV. Zatem mamy zdjęcie niedoświetlone, naświetlone prawidłowo i prześwietlone. Połączenie ich razem da nam zakres tonalny od najciemniejszych wartości zdjęcia niedoświetlonego, aż do najjaśniejszych obszarów zdjęcia prześwietlonego. 
* Proponuję także fotografować w formacie RAW, ponieważ dodatkowo zachowujemy potężny zakres tonów (16 bitowy) w porównaniu do 8 bitów w pliku JPEG, nie wspominając o braku kompresji stratnej i innych obróbek dokonywanych przez aparat.
* wybrać 16 bits/channel, co pozwoli nam przekonwertować HDR’a na głębię 16 bitową, korzystając z którejś z dostępnych metod, a także przywrócić użyteczność wszystkich narzędzi i opcji Photoshopa.

HDR Conversion, w którym mamy do wyboru cztery metody konwersji:
* Exposure &amp; Gamma (Ekspozycja i Kontrast Tonów Średnich) – pozwala na wybranie konkretnej ekspozycji (czyli po prostu jasności sceny) oraz jej kontrastu. Jest to metoda domyślna i produkuje najlepsze efekty, jeżeli naszym celem jest tylko poszerzony zakres tonalny, bez agresywnych efektów wizualnych, które możemy spotkać w internecie.
* Highlight Compression (Kompresja Świateł) – jest metodą automatyczną, gdzie zakres tonalny zostaje skompresowany do 16 bitów od strony tonów jasnych. Pozwala to uniknąć prześwietleń w najjaśniejszych partiach sceny.
* Equalize Histogram (Wyrównanie Histogramu) – metoda automatyczna, powoduje skompresowanie histogramu od strony cieni i świateł, zachowując przy tym średni, domyślny kontrast sceny.
* Local Adaptation (Lokalne Dopasowanie) – jest to metoda produkująca tzw. „efekt” HDR, czyli charakterystyczne rozjaśnienia wokół konturów przedmiotów. Mamy tutaj dwa suwaki – Radius (Promień), w którym ustalamy wielkość lokalnego rozświetlenia, oraz Threshold (Próg) – w którym ustalamy jak bardzo mają się tonalnie różnić sąsiadujące piksele, by zakwalifikować je do jednego obszaru rozświetlenia. W tej metodzie mamy też do dyspozycji krzywą tonalną i histogram, dzięki którym możemy dopasować jasność i kontrast ogólny sceny. Ta metoda produkuje dobre „efekty” HDR, szczególnie w połączeniu z poleceniem Image – Adjustments – Shadow/Highlights (Obraz – Dopasowania – Cień/Światła).


Tone mapping
https://blog.psboy.pl/2016/11/photoshop-w-godzine-cz-4-gra-w-rawy/


===photo===
https://www.adobe.com/creativecloud/photography/discover/hdr.html

==cgi==
Computer-generated imagery, computer-graphic effects in films, television programs, and other visual media

These images are 
* static (i.e. still images) 
* dynamic (i.e. moving images). The application of CGI for creating/improving animations is called computer animation, or CGI animation.

CGI both refers to:
* 2D computer graphics and (more frequently) 
* 3D computer graphics with the purpose of designing characters, virtual worlds, or scenes and special effects (in films, television programs, commercials, etc.).

=RAW=
* [[Python_Programming/Errors|raw_input in python]]
* raw graphic image formats
* raw disc image format : format is a plain binary image of the disc image, and is very portable. See [[QEMU/Images|QEMU Image formats]]
* [[Haskell/Libraries/Data_structures_primer|in Haskell]]
** raw primitive values
** raw bytes
** raw performance with arrays
* [[R Programming/Estimation utilities|in R programming language: raw function option]]
* datbase : [[Oracle_and_DB2,_Comparison_and_Compatibility/Storage_Model/Data_Types/Oracle|Oracle RAW Data Types]]: Both RAW and LONG RAW are used for data that is not interpreted by the database binary data and byte strings, LONG RAW is (or rather was) for large binary objects – for the storage of Audio, Video.
* C++
** [[C++ Language/Preprocessing/PreprocessingStrings|raw-string-literal]]
** [[C++ Language/Indirection/SmartPointers/RiskFromRawPointers|Raw Pointers]]

=PBURF=

  git clone https://github.com/luisjavierhernandez/PBURF.jl.git
  cd PBURF.jl
  cd src
  

&lt;syntaxhighlight lang=&quot;julia&quot;&gt;
julia

              _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type &quot;?&quot; for help, &quot;]?&quot; for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.5.3
 _/ |\__'_|_|_|\__'_|  |  Ubuntu ⛬  julia/1.5.3+dfsg-3
|__/                   |


julia&gt; pwd()
&quot;/home/a/PBURF.jl/src&quot;


julia&gt; readdir()
1-element Array{String,1}:
 &quot;PBURF.jl&quot;

julia&gt; include(&quot;PBURF.jl&quot;)

julia&gt; import Pkg; Pkg.add(&quot;Polynomials&quot;)
julia&gt;import Pkg; Pkg.add(&quot;Polynomials&quot;)
julia&gt;import Pkg; Pkg.add(&quot;Colors&quot;)

&lt;/syntaxhighlight&gt;

= function calculators =
* [https://www.symbolab.com/solver/functions-calculator symbolab ]
* [https://www.mathway.com/Algebra mathway - function algebra]
* [https://wims.univ-cotedazur.fr/wims/en_tool~analysis~function.en.html  Gang XIAO]
* [https://www.emathhelp.net/calculators/calculus-1/function-calculator/  emathhelp]
* [https://www.desmos.com/calculator/zzxbryrahc?lang=pl desmos]
* [https://www.wolframalpha.com/calculators/domain-range-calculator/ wolframalpha:  domain-range-calculator]
* [https://www.mathworks.com/help/symbolic/find-asymptotes-critical-and-inflection-points.html mathworks:ind-asymptotes-critical-and-inflection-points ( online) ]

=critical point =
https://math.stackexchange.com/questions/502750/when-is-infty-a-critical-point-of-a-rational-function-on-the-sphere


Just choose an appropriate pair of charts. Write &lt;math&gt;f(z) = p(z) / q(z)&lt;/math&gt;, where &lt;math&gt;p&lt;/math&gt; and &lt;math&gt;q&lt;/math&gt; are polynomial functions with no common zeros. We may assume &lt;math&gt;f&lt;/math&gt; is not a constant function – the constant case is trivial. There are a few cases:

==first case==

* &lt;math&gt;f(\infty) = \infty&lt;/math&gt; – look at the function &lt;math&gt;w \mapsto \frac{1}{f(1 / w)}&lt;/math&gt;. The derivative is given by
&lt;math&gt;\frac{f' (1/w)}{w^2 f(1/w)^2} = \frac{p'(1/w) q(1/w) - p(1/w) q'(1/w)}{w^2 p(1/w)^2}&lt;/math&gt;
but it's not immediate how to extract anything useful from this expression. Instead, suppose the leading term of &lt;math&gt;p(z)&lt;/math&gt; is &lt;math&gt;a z^n&lt;/math&gt; while the leading term of &lt;math&gt;q(z)&lt;/math&gt; is &lt;math&gt;b z^m&lt;/math&gt;. We must have &lt;math&gt;n &gt; m&lt;/math&gt; if &lt;math&gt;f(\infty) = \infty&lt;math&gt;, and the numerator is of degree &lt;math&gt;n + m - 1&lt;/math&gt; (in terms of &lt;math&gt;1/w&lt;/math&gt;) and the denominator is of degree &lt;math&gt;2 n - 2&lt;/math&gt;. 


Now there are two subcases:
* &lt;math&gt;m = n - 1&lt;/math&gt; – then the value of the expression at &lt;math&gt;w = 0&lt;/math&gt; is &lt;math&gt;\frac{b}{a}&lt;/math&gt;; in particular, &lt;math&gt;\infty&lt;/math&gt; is not a critical point of &lt;math&gt;f&lt;/math&gt;.
* &lt;math&gt;m &lt; n - 1&lt;/math&gt; – then the value of the expression at &lt;math&gt;w = 0&lt;/math&gt; is &lt;math&gt;0&lt;/math&gt;, so &lt;math&gt;\infty&lt;/math&gt; is a critical point of &lt;math&gt;f&lt;/math&gt;.


==second case==
  &lt;math&gt;f(\infty) \ne \infty&lt;/math&gt; 

look at the function 

  &lt;math&gt;w \mapsto f(1 / w)&lt;/math&gt;. 
  
The derivative is given by 

  &lt;math&gt;-\frac{f' (1/w)}{w^2} = -\frac{p'(1/w) q(1/w) - p(1/w) q'(1/w)}{w^2 q(1/w)^2}&lt;/math&gt;

but again it's not clear what we can say from this. 


Let &lt;math&gt;a z^n&lt;/math&gt; be the leading term of &lt;math&gt;p(z)&lt;/math&gt; and let &lt;math&gt;b z^m&lt;/math&gt; be the leading term of &lt;math&gt;q(z)&lt;/math&gt;. 

We must have &lt;math&gt;n \le m&lt;/math&gt; if &lt;math&gt;f(\infty) \ne \infty&lt;/math&gt;, and the numerator is of degree &lt;math&gt;n + m - 1&lt;math&gt; (if &lt;math&gt;n \ne m&lt;/math&gt;) or &lt;math&gt;&lt; n + m - 1&lt;/math&gt; (if &lt;math&gt;n = m&lt;/math&gt;) and the denominator is of degree &lt;math&gt;2 m - 2&lt;/math&gt;. 

Now there are four subcases:
* &lt;math&gt;n = m = 1&lt;/math&gt; – then &lt;math&gt;f&lt;/math&gt; is a Möbius transformation and the value of the expression is non-zero; in particular, &lt;math&gt;\infty&lt;/math&gt; is not a critical point of &lt;math&gt;f&lt;/math&gt;.
* &lt;math&gt;n = m &gt; 1&lt;/math&gt; – if the numerator is of degree &lt;math&gt;2 m - 2&lt;/math&gt; as well, then the value of the expression is non-zero; if the numerator is of degree &lt;math&gt;&lt; 2 m - 2&lt;/math&gt;, then the value of the expression is zero. (Both sub-subcases are possible, of course.)
* &lt;math&gt;n = m - 1&lt;/math&gt; – then the value of the expression at &lt;math&gt;w = 0&lt;/math&gt; is &lt;math&gt;-\frac{a}{b}&lt;/math&gt;; in particular, &lt;math&gt;\infty&lt;/math&gt; is not a critical point of &lt;math&gt;f&lt;/math&gt;.
* &lt;math&gt;n &lt; m - 1&lt;/math&gt; – then the value of the expression at &lt;math&gt;w = 0&lt;/math&gt; is &lt;math&gt;0&lt;/math&gt;, so &lt;math&gt;\infty&lt;/math&gt; is a critical point of &lt;math&gt;f&lt;/math&gt;.

At any rate, the point is that there is no _easy_ criterion purely in terms of the values of &lt;math&gt;f&lt;/math&gt; and &lt;math&gt;f'&lt;/math&gt;.

=rigorous studies of nonlinear systems =
* computing enclosures of trajectories
* finding and proving the existence of symbolic dynamics 
* obtaining rigorous bounds for the topological entropy
* methods for finding accurate enclosures of chaotic attractor
* interval operators for proving the existence of fixed points and periodic orbits
* methods for finding all short cycles 
https://rd.springer.com/chapter/10.1007/978-3-540-95972-4_2

==methods==
* [[:w:Trial_and_error|Trial_and_error in wiki]]
* [[:w:Brute-force_search|Brute-force_search in wiki]]

==graphic software==
* https://www.generic-mapping-tools.org/documentation/
* http://gwyddion.net/documentation/user-guide-en/color-map.html#color-gradient-editor* 


==text color==
* [[Template:Color|wikitext]]
* [[Help:Tables#Color|tble]]
* [[Help:Formulas#Color|math formula]]

==some notes==
Some notes from [http://ca.wikipedia.org/wiki/Fractal | wikipedia ]


&lt;MATH&gt; Z^2 &lt;/MATH&gt; 
* &lt;MATH&gt; \operatorname{Re} = x^2 - y^2 &lt;/MATH&gt;  
* &lt;MATH&gt; \operatorname{Im} = 2 * x * y  &lt;/MATH&gt;

&lt;MATH&gt; Z^3 &lt;/MATH&gt;  
* &lt;MATH&gt; \operatorname{Re} = x^3 - 3* y^2 * x  &lt;/MATH&gt;  
* &lt;MATH&gt; \operatorname{Im} = 3 * x^2 * y  - y^3 &lt;/MATH&gt;

&lt;MATH&gt; Z^4 &lt;/MATH&gt;
* &lt;MATH&gt; \operatorname{Re} = x^4  - 6 * x^2 * y^2 + y^4  &lt;/MATH&gt; 
* &lt;MATH&gt; \operatorname{Im} = 4*x^3 * y - 4 * x * y^3  &lt;/MATH&gt;

&lt;MATH&gt; Z^5 &lt;/MATH&gt; 
* &lt;MATH&gt; \operatorname{Re} = x^5  - 10 * x^3 * y^2 + 5 * x * y^4  &lt;/MATH&gt;
* &lt;MATH&gt; \operatorname{Im} = 5*x^4 * y - 10 * x^2 * y^3 + y^5  &lt;/MATH&gt;

&lt;MATH&gt; Z^6 &lt;/MATH&gt; 
* &lt;MATH&gt; \operatorname{Re} = x^6  - 15 * x^4 * y^2 +15 * x^2 * y^4 - y^6 &lt;/MATH&gt;  
* &lt;MATH&gt; \operatorname{Im} = 6*x^5 * y - 20 * x^4 * y^2 + 6* x * y^5  &lt;/MATH&gt;

&lt;MATH&gt; Z^7 &lt;/MATH&gt;
* &lt;MATH&gt; \operatorname{Re} = x^7  - 21 * x^5 * y^2 + 35 * x^3 * y^4 -  7 * x * y^6 &lt;/MATH&gt;
* &lt;MATH&gt; \operatorname{Im} = 7*x^6 * y - 35 * x^4 * y^3 + 21* x^2 * y^5 - y^7  &lt;/MATH&gt;,

&lt;MATH&gt; \exp(Z) &lt;/MATH&gt;
* &lt;MATH&gt; \operatorname{Re} =  \exp(x) *  \cos(y) &lt;/MATH&gt; 
* &lt;MATH&gt; \operatorname{Im} = \exp(x) * \sin(y) &lt;/MATH&gt;

&lt;MATH&gt; \ln(Z) &lt;/MATH&gt; 
* &lt;MATH&gt; \operatorname{Re} =  0.5 *  \ln(x^2 + y^2) &lt;/MATH&gt;
* &lt;MATH&gt; \operatorname{Im} =  \arctan(y/x)&lt;/MATH&gt;

&lt;MATH&gt; \sin(Z) &lt;/MATH&gt;  
* &lt;MATH&gt; \operatorname{Re} =  \sin(x) *  ((\exp(y) + \exp(-y))/2) &lt;/MATH&gt; &amp;nbsp;  
* &lt;MATH&gt; \operatorname{Im} = \cos(x) *  ((\exp(y) - \exp(-y))/2) &lt;/MATH&gt;

&lt;MATH&gt; \cos(Z) &lt;/MATH&gt;  
* &lt;MATH&gt; \operatorname{Re} =  \cos(x) *  ((\exp(y) + \exp(-y))/2) &lt;/MATH&gt; 
* &lt;MATH&gt; \operatorname{Im} = -\sin(x) *  ((\exp(y) - \exp(-y))/2) &lt;/MATH&gt;

&lt;MATH&gt; \sinh(Z) &lt;/MATH&gt;  
* &lt;MATH&gt; \operatorname{Re} =  \cos(y) *  ((\exp(x) - \exp(-x))/2) &lt;/MATH&gt; 
* &lt;MATH&gt; \operatorname{Im} = \sin(y) *  ((\exp(x) + \exp(-x))/2) &lt;/MATH&gt;

&lt;MATH&gt; CosH(Z) &lt;/MATH&gt;  
* &lt;MATH&gt; \operatorname{Re} =  \cos(y) *  ((\exp(x) + \exp(-x))/2) &lt;/MATH&gt; 
* &lt;MATH&gt; \operatorname{Im} = \sin(y) *  ((\exp(x) - \exp(-x))/2) &lt;/MATH&gt;


[https://people.math.carleton.ca/~kcheung/math/books/giam-ON/html/ A Gentle Introduction to the Art of Mathematics by Joe Fields,]

=parabolic/hyperbolic/elliptic=

The meaning of the terms &quot;elliptic, hyperbolic, parabolic&quot; in different disciplines in mathematics&lt;ref&gt;[https://www.quora.com/Where-is-the-best-summary-on-the-meaning-of-the-terms-elliptic-hyperbolic-parabolic-as-used-in-different-disciplines-in-mathematics quora : Where-is-the-best-summary-on-the-meaning-of-the-terms-elliptic-hyperbolic-parabolic-as-used-in-different-disciplines-in-mathematics]&lt;/ref&gt;
* PDE ( Linear Second Order PDE’s in two Independent Variables) : https://en.wikipedia.org/wiki/Partial_differential_equation
* Moebius transformations  = Classification of Isometries ( https://www.mathi.uni-heidelberg.de/~alessandrini/Arith_Reports/1-hyperbolic%20geometry.pdf)
* dicrete local complex dynamics 
* Conic section 
* Quadratic form
* probability distributions.
&lt;gallery caption=&quot;coordinate&quot;&gt;
Elliptical coordinates grid.svg|elliptical
&lt;/gallery&gt;


===hyperbolic===
* hyperbolic&quot;. usually) means that |f′(t)|≠1| , https://math.stackexchange.com/questions/2172002/is-indeterminate-a-better-name-than-indifferent-for-neutral-fixed-points
* http://www.scholarpedia.org/article/Hyperbolic_dynamics

===Moebius transformations===

Shadertoy
* [https://www.shadertoy.com/view/msdGRj Elliptic Mobius Transform Created by Borthralla in 2023-02-28]
* [https://www.shadertoy.com/view/Ddd3z2 Parabolic Mobius Transform Created by Borthralla in 2023-02-28]

=curves=


==alg==
* trace a curve
* curve sampling = collect a list of points from curve
* simplify curve
* edge detection = ridge detection = line detection algorithm = Curve extraction
* curve fitting
===sampling===
* uniform sampling of the function ( curve)
* adaptive sampling of the function ( curve)

===simplify curve ===
* Polyline Simplification
* to Reduce the Number of Nodes in Curve Object
* reduce-the-number-of-points-in-a-curve-while-preserving-its-overall-shape
* given a curve composed of line segments (= polyline ) find a similar curve with fewer points
*  decimate a curve composed of line segments to a similar curve with fewer points
** [https://stackoverflow.com/questions/7980586/how-to-reduce-the-number-of-points-in-a-curve-while-preserving-its-overall-shape stackoverflow question: how-to-reduce-the-number-of-points-in-a-curve-while-preserving-its-overall-shape]
** [http://Https://www.geometrictools.com/Documentation/PolylineReduction.pdf geometrictools : PolylineReduction]
** &quot;removing the point whose angle between neighboring points is closest to 180 degrees, until some threshold, or until you've reached a desired number of points.&quot; aioobe
** https://en.wikipedia.org/wiki/Ramer%E2%80%93Douglas%E2%80%93Peucker_algorithm


===smooth curve from points===
&quot;curve fitting is a set of techniques used to fit a curve to data points &quot;
* https://www.quora.com/Whats-the-difference-between-curve-fitting-and-regression
* https://www.codeproject.com/Articles/31859/Draw-a-Smooth-Curve-through-a-Set-of-2D-Points-wit
* https://www.codeproject.com/Articles/25237/Bezier-Curves-Made-Simple
* https://mycurvefit.com/
* https://www.particleincell.com/2012/bezier-splines/
* http://www.mvps.org/directx/articles/catmull/
* https://stackoverflow.com/questions/tagged/curve-fitting?sort=votes&amp;pageSize=50
* https://web.cs.wpi.edu/~matt/courses/cs563/talks/curves.html
* http://pages.mtu.edu/~shene/COURSES/cs3621/NOTES/INT-APP/CURVE-INT-global.html
* https://web.cs.wpi.edu/~matt/courses/cs563/talks/curves.html
* https://gis.stackexchange.com/questions/138881/finding-the-center-line-from-a-set-of-3d-points

Fit method
* linear
** join points with segments = concatenated linear segments
** straight line using linear regression
* nonlinear
** polynomial
** cubic spline
*** Smooth Bézier Spline Through Prescribed Points

===trace a curve===
* To trace the curve we evaluate successive points on the curve 
* https://stackoverflow.com/questions/31464345/fitting-a-closed-curve-to-a-set-of-points
* https://stackoverflow.com/questions/14631776/calculate-turning-points-pivot-points-in-trajectory-path
* https://www.quora.com/Whats-the-difference-between-curve-fitting-and-regression
* http://user.engineering.uiowa.edu/~dip/lecture/Segmentation2.html
* http://alice.loria.fr/publications/papers/2014/STREAM/RobustStreamlines.pdf
* https://link.springer.com/article/10.1007/s40819-015-0067-1
** https://repository.kulib.kyoto-u.ac.jp/dspace/bitstream/2433/82596/1/0787-12.pdf
** ADAPTIVE MULTIPRECISION PATH TRACKING: https://www.semanticscholar.org/paper/Adaptive-Multiprecision-Path-Tracking-Bates-Hauenstein/6517744e4b68d3e648166448a88bda63e6a597e3
** http://www.math.colostate.edu/~bates/preprints/BHS_ODE_21apr10.pdf
===sketch a curve===
* http://xaktly.com/DerivativesIII.html
*

===boundary trace===
* http://paulbourke.net/papers/conrec/
* http://user.engineering.uiowa.edu/~dip/lecture/Segmentation2.html
* http://sijoo.tistory.com/251
* http://www.imageprocessingplace.com/downloads_V3/root_downloads/tutorials/contour_tracing_Abeer_George_Ghuneim/moore.html
* https://www.ibiblio.org/e-notes/MSet/big_m.htm
*

==types==
* [[:w:Biarc|Biarc]]
* folium
** [https://digilander.libero.it/roberto20129/matematica/curve2.html#Foliumd folium]
** [http://www.mathcurve.com/courbes2d/foliumsimple/foliumsimple.shtml folium simple]
** [http://www.mathcurve.com/courbes2d.gb/clairaut/clairaut.shtml clairaut curve]
* trifolium
** [https://www.mathcurve.com/courbes2d.gb/trifoliumregulier/trifoliumregulier.shtml regular]

https://www.mathcurve.com/courbes2d.gb/rosace/rosace.shtml
rose curve = n-folium: The curve is composed of a n base patterns. The pattern is called :  the petal or branch / leaf / lobe - symmetrical about Ox obtained for angle between -pi/(2n) and pi/(2n)


osculating circle of a sufficiently smooth plane curve
* https://www.geogebra.org/m/eemfktww
===level sets===
* https://scicomp.stackexchange.com/questions/1348/given-values-on-a-mesh-what-algorithm-can-i-use-to-construct-efficiently-level?rq=1


==curve properities==
===curvature===
Interesting curves involning the curvature concept by [http://xahlee.info/SpecialPlaneCurves_dir/Curvature_dir/curvature.html Xah Lee]:
* Evolute curve (the centers of osculating circles)
* Radial curve (locus of osculating circle normals)
* circle = curve with constant curvature everywhere
* line = curve with curvature of 0 everywhere)
* Clothoid  = spiral cirve of linearly increasing curvature)

=geometry=
* https://www.ics.uci.edu/~eppstein/161/syl.html
* https://www.cs.cmu.edu/~kmcrane/
* http://blancosilva.github.io/post/2014/10/28/Computational-Geometry-in-Python.html
* digital
** https://dgtal.org/tools/
** https://github.com/DGtal-team

=== Moore-Neighbor Tracing  ===
* https://en.wikipedia.org/wiki/Moore_neighborhood
* http://www.imageprocessingplace.com/downloads_V3/root_downloads/tutorials/contour_tracing_Abeer_George_Ghuneim/mmain.html
* https://www.codeproject.com/Articles/1105045/Tracing-Boundary-in-D-Image-Using-Moore-Neighborho
* https://stackoverflow.com/questions/26830697/moore-neighbourhood-in-python
* https://py.checkio.org/en/mission/count-neighbours/


see also:
* https://en.wikipedia.org/wiki/User:TerribleTadpole/sandbox
* https://cs.wikibooks.org/wiki/Geometrie/Vypl%C5%88ov%C3%A1n%C3%AD
* https://commons.wikimedia.org/wiki/Category:Pathfinding
* https://en.wikipedia.org/wiki/Pathfinding

==chain code==
* http://islab.ulsan.ac.kr/files/announcement/301/20091132.pdf
* https://stackoverflow.com/questions/12885055/chain-code-infinite-loop?rq=1
* https://stackoverflow.com/questions/47001899/freeman-chain-code-infinite-loop-4-adjacency?rq=1
* https://stackoverflow.com/questions/6718525/understanding-freeman-chain-codes-for-ocr?rq=1
* https://www.e-olymp.com/en/problems/1803
* http://airccse.org/journal/ijcga/papers/4214ijcga02.pdf
* http://appliedmaths.sun.ac.za/TW793/slides/slides_11_1.pdf
* http://www.aass.oru.se/Research/Learning/courses/dip/2011/lectures/DIP_2011_L14.pdf

==test==

&lt;math&gt;1 / 237142198758023568227473377297792835283496928595231875152809132048206089502588927 \approx 4.21687917729220928973942962050800760308398455294740302003110521004325771638790385468222014406044810316697454753662... *10^-81&lt;/math&gt;
&lt;math&gt; \frac{1}{2^{267}-1}= \frac{1}{237142198758023568227473377297792835283496928595231875152809132048206089502588927}   \approx 4.216879177292209*10^{-81} &lt;/math&gt;( land on the root point of period 267 component : c267 = 0.250137369683480-0.000003221184145 i    with angled internal adress : &lt;math&gt;1 \xrightarrow{1/267} 267&lt;/math&gt;


( land on the root point of period 268 component c268 = 0.250137369683480-0.000003221184145i    period = 10000 i with angled internal adress : &lt;math&gt;1 \xrightarrow{267/268} 268&lt;/math&gt;

==mandelbrot set ==
the Mandelbrot set for the function 1/z - z∙(1 + 0.001∙z)/(1 - 0.002∙z + 0.001∙z2) = &quot;1 -0.002 - 0.999 -0.001   0 1 -0.002 0.001&quot;:

  &lt;math&gt;f(z) = \frac{1}{z} - \frac{z*(1 + 0.001*z)}{(1 - 0.002*z + 0.001*z^2)}&lt;/math&gt;
http://www.juliasets.dk/UFP.htm
==video==
* https://www.college-de-france.fr/site/en-pierre-louis-lions/symposium-2017-05-30-15h30.htm
* https://www.college-de-france.fr/site/en-pierre-louis-lions/symposium-2017-05-29-11h30.htm
* https://www.math.stonybrook.edu/jackfest/Talks/
* http://www.math.vt.edu/netmaps/index.php

==programs==
* http://jsxgraph.uni-bayreuth.de/wp/index.html
* http://www.singsurf.org/index.php
* http://www.javaview.de/index.html

=gradient line of the 2D scalar field=
* http://hplgit.github.io/
* https://www.khanacademy.org/math/multivariable-calculus/multivariable-derivatives/gradient-and-directional-derivatives/v/gradient
* https://stackoverflow.com/questions/25342072/computing-and-drawing-vector-fields
* https://stackoverflow.com/questions/33059710/how-to-plot-gradfx-y?noredirect=1&amp;lq=1
* https://math.stackexchange.com/questions/462592/trouble-with-gradient-intuition
* https://metacademy.org/graphs/concepts/finite_difference_approximations_to_derivatives
* https://ocw.mit.edu/courses/mathematics/18-02sc-multivariable-calculus-fall-2010/2.-partial-derivatives/part-b-chain-rule-gradient-and-directional-derivatives/session-35-gradient-definition-perpendicular-to-level-curves/
* https://ocw.mit.edu/courses/mathematics/18-02sc-multivariable-calculus-fall-2010/2.-partial-derivatives/part-b-chain-rule-gradient-and-directional-derivatives/session-35-gradient-definition-perpendicular-to-level-curves/MIT18_02SC_notes_18.pdf
* https://metacademy.org/browse
* https://www.desmos.com/calculator/el5syd7ugj
* http://freymanart.com/VectorFields/index.htm

Key words:
* &quot;gradient line&quot; 2d &quot;scalar field&quot;

[http://people.reed.edu/~ormsbyk/projectproject/posts/level-sets.html flow] :
*  level curves and gradient vector
*  flow across continuously-spaced level curves
* The flow’s derivative is the gradient – the flow will follow the gradient vectors
* gradient is the direction of steepest ascent in the zz-direction, the reverse of the flow is the path of an object as it rolls on the surface, starting from a high place and rolling down to a lower place (in the exact opposite direction as the gradient vectors point).
* def from [http://bora.uib.no/bitstream/handle/1956/1638/Masteroppgave-haegland.pdf?sequence=1&amp;isAllowed=y Streamline Tracing on Irregular Grids by H˚akon Hægland]
** &quot;The instantaneous curves that are at every point tangent to the direction of the velocity at that point are called '''streamlines''' of the flow&quot;
** &quot;A '''pathline''' of a fluid particle is the locus of its position in space as time passes. It is thus the trajectory of a particle of fixed identity&quot;

==Khan==
[https://www.khanacademy.org/math/multivariable-calculus/multivariable-derivatives/partial-derivative-and-gradient-articles/a/the-gradient the gradient] points in the direction which increases the value of f most quickly. 
There are two ways to think about this direction:
* Choose a fixed step size, and find the direction such that a step of that size increases fff the most. Given steps of a constant size away from a particular point, the gradient is the one which increases f the most.
* Choose a fixed increase in fff, and find the direction such that it takes the shortest step to increase fff by that amount. Given steps which increase f by a given size, the gradient direction is the shortest among these.

Either way, you're trying to :
* maximize the rise over run, 
* either by maximizing the rise, or minimizing the run.

==MathWorks==

[https://uk.mathworks.com/help/matlab/ref/gradient.html Numerical Gradient]
The numerical gradient of a function is a way to estimate the values of the partial derivatives in each dimension using the known values of the function at certain points.

For a function of two variables, F(x,y), the gradient is

∇F=∂F/ ∂x ˆi + ∂F ∂y ˆ j  . 

The gradient can be thought of as a collection of vectors pointing in the direction of increasing values of F. In MATLAB®, you can compute numerical gradients for functions with any number of variables. 

Tips
Use diff or a custom algorithm to compute multiple numerical derivatives, rather than calling gradient multiple times.

Algorithms
gradient calculates the central difference for interior data points. For example, consider a matrix with unit-spaced data, A, that has horizontal gradient G = gradient(A). The interior gradient values, G(:,j), are

G(:,j) = 0.5*(A(:,j+1) - A(:,j-1));
The subscript j varies between 2 and N-1, with N = size(A,2).

gradient calculates values along the edges of the matrix with single-sided differences:

G(:,1) = A(:,2) - A(:,1);
G(:,N) = A(:,N) - A(:,N-1);
If you specify the point spacing, then gradient scales the differences appropriately. If you specify two or more outputs, then the function also calculates differences along other dimensions in a similar manner. Unlike the diff function, gradient returns an array with the same number of elements as the input.

== so==

https://stackoverflow.com/questions/263305/drawing-a-topographical-map

The gradient is a mathematical operator that may help you.

If you can turn your interpolation into a differentiable function, the gradient of the height will always point in the direction of steepest ascent.  All curves of equal height are perpendicular to the gradient of height evaluated at that point.

Your idea about starting from the highest point is sensible, but might miss features if there is more than one local maximum.

I'd suggest

1. pick height values at which you will draw lines
2. create a bunch of points on a fine, regularly spaced grid, then walk each point in small steps in the gradient direction towards the nearest height at which you want to draw a line
3. create curves by stepping each point perpendicular to the gradient; eliminate excess points by killing a point when another curve comes too close to it-- but to avoid destroying the center of hourglass like figures, you might need to check the angle between the oriented vector perpendicular to the gradient for both of the points.  (When I say oriented, I mean make sure that the angle between the gradient and the perpendicular value you calculate is always 90 degrees in the same direction.)


In response to your comment to @erickson and to answer the point about calculating the gradient of your function. Instead of calculating the derivatives of your 300 term function you could do a numeric differentiation as follows.

Given a point [x,y] in your image you could calculate the gradient (direction of steepest decent)

    g={  ( f(x+dx,y)-f(x-dx,y) )/(2*dx),   ( f(x,y+dy)-f(x,y-dy) )/(2*dy) }

where dx and dy could be the spacing in your grid.  

The contour line will run perpendicular to the gradient.  So, to get the contour direction, c, we can multiply g=[v,w] by matrix, A=[0 -1, 1 0] giving 

    c = [-w,v]
    
    
https://stackoverflow.com/questions/68491888/how-tensorflow-knows-how-to-calculate-the-derivative 

numeric differentiation (aka finite differences)
https://www.unioviedo.es/compnum/labs/lab07_der_int/lab07_der_int.html

&lt;pre&gt;
def numerical_derivative_2d(func, epsilon):
    def grad_func(x):
        return (func(x + np.array([epsilon, 0])) - func(x)) / epsilon, (func(x + np.array([0, epsilon])) - func(x)) / epsilon
    return grad_func
&lt;/pre&gt;

=potential flow=
* https://gregjavens.com/2016/03/12/laplace-equation-finite-element-method-3/
[[File:Construction of a potential flow.svg|thumb|right|Construction of a potential flow.svg]]

=spiral=
* https://math.stackexchange.com/questions/2254493/logarithmic-spiral-transform-function
* https://math.stackexchange.com/questions/1232346/find-gradient-of-a-equi-angular-spiral-log-spiral
* [https://www.ibiblio.org/e-notes/MSet/spiral.htm  spiral in Julia set]
* [https://www.geogebra.org/m/c982z9uw  Pursuit Paths via Complex Numbers Author:Steve Phelps]
==The Golden Ratio and the Golden Angle==

In disc [[phyllotaxis]], as in the [[sunflower]] and daisy, the mesh of spirals occurs in [[Fibonacci number]]s because divergence (angle of succession in a single spiral arrangement) approaches the [[golden ratio]].  The shape of the spirals depends on the growth of the elements generated sequentially.  In mature-disc [[phyllotaxis]], when all the elements are the same size, the shape of the spirals is that of Fermat spirals&amp;mdash;ideally.  That is because Fermat's spiral traverses equal [[annulus (mathematics)|annuli]] in equal turns. The full model proposed by H Vogel in 1979&lt;ref&gt;
{{Cite journal
  | last =Vogel
  | first =H
  | title =A better way to construct the sunflower head
  | journal =Mathematical Biosciences
  | issue =44
  | pages =179–189
  | year =1979
  | doi =10.1016/0025-5564(79)90080-4
  | volume =44
  | postscript =&lt;!--None--&gt;
}}&lt;/ref&gt; is

:&lt;math&gt;r = c \sqrt{n},&lt;/math&gt;

:&lt;math&gt;\theta = n \times 137.508^\circ,&lt;/math&gt;

where ''θ'' is the angle, ''r'' is the radius or distance from the center, and ''n'' is the index number of the floret and ''c'' is a constant scaling factor. The angle 137.508° is the [[golden angle]] which is approximated by ratios of [[Fibonacci number]]s.&lt;ref&gt;{{cite book
  | last =Prusinkiewicz
  | first =Przemyslaw
  | authorlink =Przemyslaw Prusinkiewicz
  |author2=Lindenmayer, Aristid |authorlink2=Aristid Lindenmayer 
  | title =The Algorithmic Beauty of Plants
  | publisher =Springer-Verlag
  | date =1990
  | location =
  | pages =101&amp;ndash;107
  | url =http://algorithmicbotany.org/papers/#webdocs
  | doi =
  | isbn = 978-0-387-97297-8 }}&lt;/ref&gt;

&lt;gallery&gt;
Sunflower spiral.png|The pattern of florets produced by Vogel's model (central image). The other two images show the patterns for slightly different values of the angle.
Dotswirl.gif
Logarithmic floret simulation.svg
&lt;/gallery&gt;


Illustration of Vogel's formula of the pattern of sunflower florets (see [[:en:Sunflower#Mathematical model of floret arrangement|article]]) for ''n'' from 1 to 500, using the polar coordinates equations &lt;math&gt;r = c \sqrt{n}&lt;/math&gt; and &lt;math&gt;\theta = n \times \frac{2 \pi}{\phi + 1}&lt;/math&gt;. Can be produced using the following MATLAB code:
 n=1:500;
 r=sqrt(n);
 t=2*pi/((sqrt(5)+1)/2+1)*n;
 plot(r.*cos(t),-r.*sin(t),'o')

===Links===
* [https://www.youtube.com/watch?v=EK32jo7i5LQ&amp;list=PL53AB2CAE70F31F2A&amp;index=34 Why do prime numbers make these spirals? | Dirichlet’s theorem, pi approximations, and more  by 3Blue1Brown]
* [https://www.shadertoy.com/view/4lGfDd best scrambling offset Created by FabriceNeyret2]   pretends golden ratio gives the best Sunflower because it's the &quot;most irrational&quot; number. I find the argument a lot less convincing with linear offsets rather than circular.
* [https://www.youtube.com/watch?v=sj8Sg8qnjOg The Golden Ratio (why it is so irrational) - Numberphile ]
* [https://www.youtube.com/watch?v=OFI1FJcGLeM The Art of John Edmark Talk by Paul Dancstep from Exploratorium]
* https://blog.matthen.com/tagged/fibonacci

 &quot; Is it possible to find a pattern in the prime numbers? If you arrange them in what is called the Ulam spiral, you can see some clear patterns emerging. There are other spiral shapes which give nice patterns, such as stacking them into a triangle.... Is it possible to find a pattern in the prime numbers?  If you arrange them in what is called the Ulam spiral, you can see some clear patterns emerging. There are other spiral shapes which give nice patterns, such as stacking them into a triangle.  Here I have tried wrapping them into a Fibonacci spiral, where each dot is slightly further out than the last- and is rotated by a Golden ratio of a full turn (about 0.618034 * 360 = 222.49224 degrees). The red dots are the primes, the blacks the non-primes (composites). Unfortunately, there doesn’t seem to be any pattern. Does there? [code]&quot; matthen

 &quot; This spiral is rotated by the golden angle every frame. Though it looks like the circles are growing and changing colour, they are actually unchanging and the whole image is just rotating. [inspired by these amazing sculptures] [code] [related]&quot; matthen

===Vogel's mode===
A model for the pattern of [[floret]]s in the head of a [[sunflower]] was proposed by [[:de:Helmut Vogel (Physiker)|Helmut Vogel]] in 1979.&lt;ref&gt;{{Citation | last =Vogel | first =Helmut | title =A better way to construct the sunflower head | journal = Mathematical Biosciences | issue =3–4 | pages = 179–89 | year = 1979 | doi = 10.1016/0025-5564(79)90080-4 | volume = 44}}&lt;/ref&gt;  This has the form

  &lt;math&gt; \theta = \frac{2\pi}{\varphi^2} n&lt;/math&gt;
  &lt;math&gt;r = c \sqrt{n} &lt;/math&gt;
  &lt;math&gt;z = r(\cos \theta + i\sin \theta ) &lt;/math&gt;

where:
* {{math|''n''}} is the index number of the floret 
* {{math|''c''}} is a constant scaling factor

The florets thus lie on [[Fermat's spiral]]. The divergence angle, approximately 137.51°, is the [[golden angle]], dividing the circle in the golden ratio.  Because this ratio is irrational, no floret has a neighbor at exactly the same angle from the center, so the florets pack efficiently.  Because the rational approximations to the golden ratio are of the form {{math|''F''(''j''):''F''(''j'' + 1)}}, the nearest neighbors of floret number {{math|''n''}} are those at {{math|''n'' ± ''F''(''j'')}} for some index {{math|''j''}}, which depends on {{math|''r''}}, the distance from the center.  Sunflowers and similar flowers most commonly have spirals of florets in clockwise and counter-clockwise directions in the amount of adjacent Fibonacci numbers,{{sfn|Livio|2003|p=112}} typically counted by the outermost range of radii.&lt;ref&gt;{{Citation | last1 = Prusinkiewicz | first1 = Przemyslaw | author1-link = Przemyslaw Prusinkiewicz | author2-link = Aristid Lindenmayer | last2 = Lindenmayer | first2 = Aristid | title = The Algorithmic Beauty of Plants | publisher = Springer-Verlag | year = 1990 | pages = [https://archive.org/details/algorithmicbeaut0000prus/page/101 101–107] | chapter = 4 | chapter-url = http://algorithmicbotany.org/papers/#webdocs | isbn = 978-0-387-97297-8 | url = https://archive.org/details/algorithmicbeaut0000prus/page/101 }}&lt;/ref&gt;

==Algorithm==
* http://algorithmicbotany.org/papers/abop/abop-ch4.pdf
* http://blog.marmakoide.org/?p=1
* https://www.codeproject.com/Articles/650821/Fractals-in-theory-and-practice
* http://www.mathrecreation.com/2015/08/simple-fun-with-r.html
* http://www.maths.surrey.ac.uk/hosted-sites/R.Knott/Fibonacci/fibnat2.html
* http://demonstrations.wolfram.com/SpiralExplorer/
* http://demonstrations.wolfram.com/PhyllotaxisSpirals/
* http://demonstrations.wolfram.com/PhyllotaxisExplained/
* http://demonstrations.wolfram.com/NumericalFlowers/
* https://www.codeproject.com/Articles/1221341/The-Vogel-Spiral-Phenomenon
* https://calculus7.org/2016/01/17/irrational-sunflowers/
* http://physics.nyu.edu/grierlab/fibonacci3b/node2.html
* http://www.maths.surrey.ac.uk/hosted-sites/R.Knott/Fibonacci/fibnat2.html
* http://www.mi.sanu.ac.rs/vismath/bridges2005/krawczyk/index.html
* [https://maa.tandfonline.com/doi/abs/10.1080/0025570X.2002.11953126#.WuioS59fifY Golden, , and π Flowers: A Spiral Story Michael Naylor]

====code====
* https://www.desmos.com/calculator/risuha09iw

R code 

&lt;syntaxhighlight lang=&quot;R&quot;&gt;
#http://www.mathrecreation.com/2015/08/simple-fun-with-r.html
# https://github.com/dmackinnon1/r_examples/blob/master/simple/example2.r

#example 2b phyllotaxis spiral
t &lt;- 1:500
p &lt;- (1 + sqrt(5))*pi
plot(sqrt(t)*cos(p*t), sqrt(t)*sin(p*t), type=&quot;p&quot;, axes=FALSE)

&lt;/syntaxhighlight&gt;

Maple code
&lt;syntaxhighlight lang=&quot;Maple&quot;&gt;
# code from : http://personal.maths.surrey.ac.uk/ext/R.Knott/Fibonacci/seedPlotMaple.txt
# by Ron Knott

&gt; with(plots):

#Growpts shows a single picture (plot) of n seeds (points) distributed at 
#TurnperSeed (a numberbetween 0 and 1) which is the fraction of 1 turn between 
#one seed and the next,

&gt; 
growpts:=(n,TpS)-&gt;growpts1(n,TpS,POINT):
growpts1:=proc(n,TurnperSeed,symb) local i,a,r,s,phi2pi;
   s:=null;
   phi2pi:=TurnperSeed*2*Pi;
   listplot([seq([sqrt(n-i)*cos(phi2pi*i),sqrt(n-i)*sin(phi2pi*i)],i=1..n)],
      style=POINT,axes=NONE,scaling=CONSTRAINED,symbol=symb)
end;


#Here is a seed-head with Pi turns between each seed.  
#Since Pi=3.14159&gt;1, it is the same as 0.14159 turns per seed.  
#Note how there are 7 radial arms (corresponding to 22/7 for Pi) near the centre 
#and the next set of radial arms are 113 arms with seeds placed 16 arms apart 
#(since the next best approximation to Pi is 3+16/113=355/113).

&gt; growpts(1000,Pi);

#Here we take a single Turns-per-seed value and keep adding a new seed 
#(at the centre) showing the seed head growing up to n seeds finally.  
#The plots are animated to show the growing process:


&gt;
seedplot := proc(n, ratio)
  display([seq(growpts1(i, ratio, CIRCLE), i = (1 .. n))], insequence = true, 
  style = point, scaling = constrained, axes = NONE)
end proc;

#Here is 100 seeds at Phi =1.618.. turns per seed (which is the same as 
#Phi-1=0.618..=phi turns per seed):

&gt; seedplot(100,(sqrt(5)-1)/2);

&lt;/syntaxhighlight&gt;

=intersection of polar curves=
* https://math.stackexchange.com/questions/1221260/intersecting-polar-curves-r-1cos%CE%B8-and-r-1-cos%CE%B8
* https://math.stackexchange.com/questions/1064268/suppose-that-two-polar-curves-are-given-by-r-1-cos2-theta-and-r-2-si
* https://math.stackexchange.com/questions/851190/finding-self-intersections-on-a-polar-curve
* https://math.stackexchange.com/questions/2038456/intersection-points-of-two-polar-curves?rq=1
* https://math.stackexchange.com/questions/1281068/intersection-of-polar-curve-with-line?rq=1
* https://math.stackexchange.com/questions/2358269/points-of-intersection-for-two-logarithmic-spirals?rq=1

=iteration=
* https://math.stackexchange.com/questions/2571345/iterating-quadratic-polynomials/2571349#2571349
* https://math.stackexchange.com/questions/140819/general-mandelbrot-iteration-formulas?rq=1

=atan2=

[[File:Atan2 circle.svg|thumb|right]]
* https://stackoverflow.com/questions/17574424/how-to-use-atan2-in-combination-with-other-radian-angle-systems
* http://patrikstas.com/2015/11/05/what-is-difference-between-atan-and-atan2/
* https://mrl.nyu.edu/~perlin/courses/spring2012/texture.html
* https://www.youtube.com/watch?v=mGEtMc20eeE
* https://www.youtube.com/watch?v=Zh6cmQcT1YI
* https://www.youtube.com/watch?v=LHzgW9aQUV8
* https://www.youtube.com/watch?v=Idxeo49szW0


=conformal=
* &quot; Conformal transformation: 	One can find solutions to the Dirichlet problem for a wider class of regions by conformal transformations. These are transformations which preserve the angles and have the property that the transplanted function is harmonic if the original function is harmonic. One can obtain conformal transformations using complex function (x,y) -&gt; (u,v): if z=x+iy and F(z) is a polynomial in z and F(z)=u+i v, then the map is conformal. For example, to solve the Dirichlet problem outside a wing, one can transform the circle into the wing using a conformal transformation. Such methods are relevant in engeneering.&quot; http://www.math.harvard.edu/archive/21b_fall_03/laplace/index.html
* https://www3.cs.stonybrook.edu/~gu/tutorial/RiemannMapping.html
* https://www.chebfun.org/docs/guide/guide16.html
* https://www.cs.cmu.edu/~kmcrane/Projects/Other/OverviewConformalGeometryProcessing.pdf
* http://www-users.math.umn.edu/~olver/ln_/cml.pdf
* The Euler conformal map, a special case of the M¨obius transformation, maps circles to circles
* https://gregjavens.com/2016/05/11/conformal-map/
* https://gregjavens.com/2016/03/12/laplace-equation-finite-element-method-3/
* http://mathfaculty.fullerton.edu/mathews/c2003/ConformalMapDictionary.2.html
* https://www3.cs.stonybrook.edu/~gu/
* https://arxiv.org/abs/1306.1162
* http://www.eng.biu.ac.il/weberof/publications/
* http://wwwf.imperial.ac.uk/~dgcrowdy/GuTalk.pdf
==numerical conformal mapping===

=Orthogonal=
[[File:Apollonius hyperbolic.svg|thumb|right|Ancillary figure for van Roomen's solution to the problem of Apollonius.]]
* https://www.mathcurve.com/courbes2d.gb/orthogonale/orthogonale.shtml
* https://en.wikipedia.org/wiki/Orthogonal_trajectory
* http://www.emathhelp.net/calculators/calculus-1/tangent-line-calculator/
* https://www.whitman.edu/mathematics/calculus_online/section10.02.html
* http://tutorial.math.lamar.edu/Classes/CalcII/ParaTangent.aspx
* http://www.emathhelp.net/calculators/calculus-1/online-graphing-calculator/
* https://www.math24.net/tangent-normal-lines/
* https://emathhelp.net/calculators/calculus-1/online-graphing-calculator/?uid=nwd4ldjtge
* https://emathhelp.net/plot/nwd4ldjtge.png
* https://math.stackexchange.com/questions/1919319/how-do-i-get-the-tangent-of-a-curve?rq=1
* https://math.stackexchange.com/questions/992847/finding-the-equation-of-a-tangent-line-to-a-polar-curve?rq=1
* 
tangent to circle in the polar form 

  z= r(t)

[http://www.emathhelp.net/calculators/calculus-1/online-graphing-calculator/ is line] : 

  y = x*tan(t)
&lt;gallery&gt;
Kardioide.svg|Creating a cardioid by rolling a circle on a circle of the same radius
File:Cardiod animation.gif|animation
&lt;/gallery&gt;

Tangent to cardioid in polar form : 

  z = 2a( 1 - cos(t))

is line : 

  // y = (x*(-1+2*cos(t))*sin(t)+(-3+3*cos(t))*sin(t))/(-1+2*cos(t)^2-cos(t))
  y = (x*(-1+2*cos(t))*sin(t)+(-2a+2a*cos(t))*sin(t))/(-1-cos(t)+2*cos(t)^2)

where t is changing from 0 to 2*pi

Compare : 
* [http://www.criced.tsukuba.ac.jp/grapes/image/fukuso1.html circle to cardioid mapping ( w = z^2)]
* [http://www.criced.tsukuba.ac.jp/grapes/image/fukuso2.html  The objects shown here are the inverse images of the map w = z4 where the point w is on the cricle and on the line in the complex plane.]


==ellipse==

&lt;math&gt;(x,y)=(a \cos t, b \sin t),\ 0\le t&lt;2\pi\ .&lt;/math&gt;

slope m 


&lt;math&gt; m = -\frac{b}{a}\cot t\quad &lt;/math&gt;


The equation of the tangent at point &lt;math&gt;\vec c_\pm(m)&lt;/math&gt; has the form &lt;math&gt;y=mx+n&lt;/math&gt;

&lt;math&gt;y = m x \pm\sqrt{m^2a^2+b^2}\; .&lt;/math&gt;


https://www.math24.net/tangent-normal-lines-page-2/#example11
https://www.math24.net/implicit-differentiation/


Implicit
* function
* implicit differentiation = differentiation of the implicit function

=sqare root=
* http://mathlets.org/mathlets/complex-roots/
* https://flothesof.github.io/branch-cuts-with-square-roots.html
* http://phantomgraphs.weebly.com/
* https://math.stackexchange.com/questions/1797223/graphically-solving-for-complex-roots-how-to-visualize?noredirect=1&amp;lq=1
* Reciprocal Function as a Mapping
** http://functions.wolfram.com/ElementaryFunctions/Sqrt/visualizations/4/
** http://functions.wolfram.com/ElementaryFunctions/Sqrt/visualizations/7/
** http://mathfaculty.fullerton.edu/mathews/c2003/ComplexFunPowerRootMod.html
** https://sites.oxy.edu/ron/math/312/16/ws/08.pdf
** https://usamo.wordpress.com/2017/02/16/holomorphic-logarithms-and-roots/
** http://laussy.org/wiki/MMII/Complex_functions_of_complex_numbers
** https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/_24769_figure12567.gif
* branch cuts
** https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node129.html
** sqrt : The branch cut for square root lies along the negative real axis, continuous with quadrant II. The range consists of the right half-plane, including the non-negative imaginary axis and excluding the negative imaginary axis.
** https://math.stackexchange.com/questions/923931/problem-identifying-branch-cuts-of-a-square-root-function?noredirect=1&amp;lq=1
==repeated ==
* https://math.stackexchange.com/questions/3283/why-do-i-always-get-1-when-i-keep-hitting-the-square-root-button-on-my-calculat
* https://www.geeksforgeeks.org/sqrt-square-root-decomposition-technique-set-1-introduction/
* http://edspi31415.blogspot.com/2015/08/repeated-presses-of-square-root-button.html
*


=tree=
* https://www.youtube.com/watch?v=BEz-vGJvaik

=People=
[http://www.danca.rist.ro/index.htm Marius-F. Danca]
[[pl:User:Adam_majewski]]
=petal=
&quot;An attracting petal, P + ,
for a map M at zero is an open simply connected forward invariant region with
0 ∈ ∂P + , that shrinks down to the origin under iteration of M . More precisely, P +
is an attracting petal if M (P + ) ⊂ P + ∪ {0} and n≥0 M n (P + ) = {0}.
&quot;&lt;ref&gt;NEWTON’S METHOD ON
THE COMPLEX EXPONENTIAL FUNCTION
MAKO E. HARUTA&lt;/ref&gt;


==example==
http://mathoverflow.net/questions/104482/parabolic-immediate-basins-always-simply-connected?rq=1
&quot;An example is f(z)=z+1−1/zf(z)=z+1−1/z. There is one petal for the neutral point at infinity. Let AA be the dmain of attraction of ∞∞. Critical points are ±i±i. Everything is symmetric with respect to the real line, because the function is real. One critical point is in AA, so by symmetry the other one is also in AA. The map f:A→Af:A→A is 2-to-1 (because ff is of degree 22), so Riemann and Hurwitz tell us that AA is infinitely connected.&quot;

shareciteeditflag
answered Aug 12 '12 at 13:38

Alexandre Eremenko

==cylinder==
What is the difference between the cylinder &lt;math&gt;\mathbb C \setminus 0&lt;/math&gt;  and cylinder &lt;math&gt;\mathbb C / \mathbb Z&lt;/math&gt; ?
=topology=

* Topology is a branch of mathematics that deals with qualitative geometric information. This includes the classification of loops and higher-dimensional surfaces.
* Topological data analysis and computational topology deal with the study of topology using a computer.
* Persistent homology is an algebraic method for discerning topological features of data.
* Connected component (or connected cluster of points) is a 0-dimensional feature and cycle (or loop) is a 1-dimensional feature.
* Simplicial complex is a set composed of points, line segments, triangles, and their n-dimensional counterparts.
* Filtration is the sequence of simplicial complexes, with an inclusion map from each simplicial complex to the next.
* Barcode is a visual representation of the persistence of the topological features. Longer bars represent significant features of the data. Shorter bars are due to irregularities or noise.


&quot;A topologist is someone who doesn't know the difference between a cup of coffee and a donut.&quot;
* [https://docs.gempy.org/tutorials/ch4-Topology/ch4-1-Topology.html Gempy]
* [http://ronny.rest/tutorials/module/seg_01/segmentation_01_intro/ semantic segmentation]
==computational topology==
* [https://www.youtube.com/@utahsoccomputationaltopolo4135  Utah SoC Computational Topology]
* [https://markolalovic.github.io/blog/tda-digits tda-digits]

==set==
* [[:w:dense set|dense set]] a subset A of a topological space X is said to be dense in X if every point of X either belongs to A or else is arbitrarily &quot;close&quot; to a member of A 
* [[:w:countable set|countable set]]: a set is countable if either it is finite or it can be made in one to one correspondence with the set of natural numbers.

= ???=

''' El método de Mandelbrot ''': este método para desarrollar &quot;objetos fractales&quot; fue creado por [[Benoît Mandelbrot]] en la década de los años 70, mientras trabajaba en IBM. Consiste en construir, para cada punto '''c''' del plano complejo, una sucesión de números complejos '''z&lt;sub&gt;n&lt;/sub&gt;'''. Partiendo del punto '''z&lt;sub&gt;0&lt;/sub&gt; = 0''', se calcula la sucesión de forma iterativa mediante la fórmula '''z&lt;sub&gt;n+1&lt;/sub&gt;=F(z&lt;sub&gt;n&lt;/sub&gt;)+c''', donde '''F''' es una función arbitraria previamente elegida. Cuando la sucesión iterativa está acotada, se asigna al punto '''c''' del plano complejo un color sólido (por ejemplo, el color negro). Si la sucesión diverge entonces se asigna al punto '''c''' un color progresivamente distinto, dependiendo de cuántas iteraciones hayan sido necesarias para detectar la divergencia de la sucesión.

El fractal derivado por este método cuando se toma la función '''F(z)=z&lt;sup&gt;2&lt;/sup&gt;''' se llama [[conjunto de Mandelbrot]].

En lo que sigue, en lugar de '''z&lt;sub&gt;n+1&lt;/sub&gt;=F(z&lt;sub&gt;n&lt;/sub&gt;)+c''' se utilizará la notación '''Z=F(Z)+C''', como si se tratara de una asignación en algún lenguaje de programación.

== Z = Z&lt;sup&gt;m&lt;/sup&gt; + C ==
A continuación se muestra una serie de fractales iterando las diferentes potencias de '''Z = Z&lt;sup&gt;m&lt;/sup&gt; + C''', según el método de '''Mandelbrot'''. &lt;br&gt;&lt;br&gt;
'''Ejemplos de fractales del tipo Mandelbrot: Z = Z&lt;sup&gt;m&lt;/sup&gt; + C'''
&lt;gallery&gt;
MANDEL_Z2%2BC.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C'''&lt;/div&gt;Conjunto de Mandelbrot
Archivo:MANDEL_Z3%2BC.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z4%2BC.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;4&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z5%2BC.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;5&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z6%2BC.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;6&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z7%2BC.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;7&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z8%2BC_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;8&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z9%2BC_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;9&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z10%2BC_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;10&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z11%2BC_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;11&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z12%2BC_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;12&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z12%2BC_detall.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;12&lt;/sup&gt; + C&lt;br&gt;x 8'''&lt;/div&gt;
Archivo:MANDEL_Z20%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;20&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z20%2BC_detall.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;20&lt;/sup&gt; + C&lt;br&gt;x 10'''&lt;/div&gt;
Archivo:MANDEL_Z48%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;48&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z48%2BC_detall.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;48&lt;/sup&gt; + C&lt;br&gt;x 20'''&lt;/div&gt;
Archivo:MANDEL_Z96%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;96&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z96%2BC_detall.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;96&lt;/sup&gt; + C&lt;br&gt;x 40'''&lt;/div&gt;
&lt;/gallery&gt;
Tal y como se puede ver en los ejemplos representados, el número de lóbulos es '''L = m - 1''' &lt;br&gt;
=== Un breve viaje a las profundidades del fractal de Mandelbrot Z = Z&lt;sup&gt;2&lt;/sup&gt; + C ===
A continuación vamos a adentrarnos en el fractal clásico de Mandelbrot, utilizando el [[microscopio]] de altísima resolución que nos proporciona el [[cálculo iterativo]]. Todas las ampliaciones vienen precedidas de una imagen del fractal a escala 1:1 en donde podemos apreciar la zona ampliada.&lt;ref&gt;Barnsley, M. Fractals everywhere.Academic Press Inc, 1988. {{#isbn:0-12-079062-9}}. (Cap 5)
&lt;/ref&gt;
==== Ampliación zona 1 ====
Centro de coordenadas : '''Cx = 0.291811 , Cy = 0.0144686'''
&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2_X1_001.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;''' x 1'''&lt;/div&gt;
Archivo:MANDEL_Z2_X732_0,291811_0,0144686.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;''' x 732'''&lt;/div&gt;
&lt;/gallery&gt;
==== Ampliación zona 2 ====
Centro de coordenadas : '''Cx = -0.165643411 , Cy = 0.656685704 ''' 
&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2_X1_002.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;''' x 1'''&lt;/div&gt;
Archivo:MANDEL_Z2_X3855_-0,165643411_0,656685704.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;''' x 3855'''&lt;/div&gt;
&lt;/gallery&gt;
==== Ampliación zona 3 ====
Centro de coordenadas : '''Cx = -0.755625 , Cy = 0.06328125 ''' 
&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2_X1_003.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;''' x 1'''&lt;/div&gt;
Archivo:MANDEL_Z2_X180_-0,755625_0,06328125.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;''' x 180'''&lt;/div&gt;
&lt;/gallery&gt;
==== Ampliación zona 4 ====
Centro de coordenadas : '''Cx = -0,1758752481899, Cy = 1,075392007''' 
&lt;br&gt;
A continuación bajaremos a gran profundidad, con una ampliación de más de 2 millones y con un número máximo de 6000 iteraciones por pixel !&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2_X1_004.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;''' x 1'''&lt;/div&gt;
Archivo:MANDEL_Z2_X2369369_-0,1758752481899_1,075392007.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;''' x 2,369,369'''&lt;/div&gt;
&lt;/gallery&gt;
==== Ampliación zona XX ====
Centro de coordenadas : '''Cx = 0,02816835288421, Cy = 0,63790834667330 '''
&lt;br&gt;
Ahora nos adentraremos en un sitio con extrañas formas y colores, pero donde pueden apreciarse perfectamente las formas del fractal de Mandelbrot...
&lt;br&gt;
&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2_X5598_0,02816835288421_0,63790834667330.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;''' x 5,598'''&lt;/div&gt;
&lt;/gallery&gt;

== Z = Z&lt;sup&gt;-m&lt;/sup&gt; + C ==
'''Ejemplos de fractales del tipo Mandelbrot, con potencias negativas de Z.'''
&lt;gallery&gt;
Archivo:MANDEL_Z-2%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z &lt;sup&gt;-2&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z-3%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z &lt;sup&gt;-3&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z-4%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z &lt;sup&gt;-4&lt;/sup&gt; + C'''&lt;/div&gt;
Archivo:MANDEL_Z-5%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z &lt;sup&gt;-5&lt;/sup&gt; + C'''&lt;/div&gt;
&lt;/gallery&gt;
== Z = Z&lt;sup&gt;p&lt;/sup&gt; / (1 + Z&lt;sup&gt;q&lt;/sup&gt;) + C ==
&lt;gallery&gt;
Archivo:MANDEL_Z2_(1+Z)+C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; / (1 + Z) + C''' &lt;br&gt;&lt;/div&gt;
Archivo:MANDEL_Z3_(1%2BZ2)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; / (1 + Z&lt;sup&gt;2&lt;/sup&gt;) + C''' &lt;br&gt;&lt;/div&gt;
Archivo:MANDEL_Z3_(1%2BZ)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; / (1 + Z) + C''' &lt;br&gt;&lt;/div&gt;
Archivo:MANDEL_Z3_(1%2BZ%2BZ2)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; / (1 + Z + Z&lt;sup&gt;2&lt;/sup&gt;) + C''' &lt;br&gt;&lt;/div&gt;
Archivo:MANDEL_(1%2B2xZ)_Z2%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = [(1 + Z) / Z&lt;sup&gt;2&lt;/sup&gt;] + C''' &lt;br&gt;&lt;/div&gt;
&lt;/gallery&gt;

== Z = Z&lt;sup&gt;m&lt;/sup&gt; + C&lt;sup&gt;p&lt;/sup&gt; ==
Pero, ¿ qué pasa cuando hacemos '''Z = Z&lt;sup&gt;m&lt;/sup&gt; + C&lt;sup&gt;p&lt;/sup&gt;''' ?. Tal y como se puede ver en los siguientes ejemplos, el número de lóbulos es '''L = (m - 1) * p''' &lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2_C2.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;L = (2 - 1)* 2 = '''2'''&lt;/div&gt;
Archivo:MANDEL_Z2_C3.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C&lt;sup&gt;3&lt;/sup&gt;''' &lt;br&gt;L = (2 - 1)* 3 = '''3'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC6-1.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt;+C&lt;sup&gt;6&lt;/sup&gt; - 1 ''' &lt;br&gt; L = (2 - 1)* 6 = '''6'''&lt;/div&gt;
Archivo:MANDEL_Z3_C2.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; + C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;L = (3 - 1)* 2 = '''4'''&lt;/div&gt;
Archivo:MANDEL_Z3_C3.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; + C&lt;sup&gt;3&lt;/sup&gt;''' &lt;br&gt;L = (3 - 1)* 3 = '''6'''&lt;/div&gt;
Archivo:MANDEL_Z4_C4.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;4&lt;/sup&gt; + C&lt;sup&gt;4&lt;/sup&gt;''' &lt;br&gt;L = (4 - 1)* 4 = '''12'''&lt;/div&gt;
&lt;/gallery&gt;

== Z = Z&lt;sup&gt;m&lt;/sup&gt; + Z + C ==
A continuación se muestra una serie de fractales iterando las diferentes potencias de '''Z = Z&lt;sup&gt;m&lt;/sup&gt; + Z + C''', según el método de '''Mandelbrot'''. &lt;br&gt;&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BZ%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + Z + C'''&lt;/div&gt;
Archivo:MANDEL_Z3%2BZ%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; + Z + C'''&lt;/div&gt;
Archivo:MANDEL_Z4%2BZ%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;4&lt;/sup&gt; + Z + C'''&lt;/div&gt;
Archivo:MANDEL_Z9%2BZ%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;9&lt;/sup&gt; + Z + C'''&lt;/div&gt;
&lt;/gallery&gt;

== Z = Z&lt;sup&gt;m&lt;/sup&gt; - Z + C ==
A continuación se muestra una serie de fractales iterando las diferentes potencias de '''Z = Z&lt;sup&gt;m&lt;/sup&gt; - Z + C''', según el método de '''Mandelbrot'''. &lt;br&gt;&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z3-Z%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; - Z + C'''&lt;/div&gt;
 Archivo:MANDEL_Z4-Z%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;4&lt;/sup&gt; - Z + C'''&lt;/div&gt;
Archivo:MANDEL_Z5-Z%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;5&lt;/sup&gt; - Z + C'''&lt;/div&gt;
Archivo:MANDEL_Z9-Z%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;9&lt;/sup&gt; - Z + C'''&lt;/div&gt;
&lt;/gallery&gt;

== Z = Z&lt;sup&gt;m&lt;/sup&gt; + 1 / C&lt;sup&gt;p&lt;/sup&gt; ==
También se puede transformar cada punto del plano complejo, de acuerdo a una función arbitraria, antes de ser sumado a la función iterativa, según la siguiente ecuación '''Z = Z&lt;sup&gt;m&lt;/sup&gt; + F(C) '''. Veamos que pasa cuando la transformación es del tipo:'''F(C) = 1 / C'''&lt;br&gt;&lt;br&gt;
'''Ejemplos de fractales del tipo Mandelbrot: Z = Z&lt;sup&gt;m&lt;/sup&gt; + 1/C''', donde cada punto C del plano complejo se transforma en 1 / C, antes de entrar en la iteración de la potencia de Z. &lt;br&gt;Zo = (0,0i). El número de vértices es '''V = (m - 1)''' 
&lt;gallery&gt;
Archivo:MANDEL_Z2_1_C.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + 1/C'''&lt;/div&gt;
Archivo:MANDEL_Z3%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; + 1/C'''&lt;/div&gt;
Archivo:MANDEL_Z4%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;4&lt;/sup&gt; + 1/C'''&lt;/div&gt;
Archivo:MANDEL_Z5%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;5&lt;/sup&gt; + 1/C'''&lt;/div&gt;
Archivo:MANDEL_Z6%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;6&lt;/sup&gt; + 1/C'''&lt;/div&gt;
Archivo:MANDEL_Z7%2B1_C_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;7&lt;/sup&gt; + 1/C'''&lt;/div&gt;
&lt;/gallery&gt;
&lt;br&gt;
Pero, qué pasa cuándo '''Z = Z&lt;sup&gt;m&lt;/sup&gt; + (1 / C&lt;sup&gt;2&lt;/sup&gt;)''' ?.
Pues algo muy parecido a lo que veíamos antes, ahora el número de vértices es '''V = (m - 1) * p''' &lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2_iC2.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + 1 / C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;V = (2 - 1)* 2 = '''2'''&lt;/div&gt;
Archivo:MANDEL_Z3_iC2.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; + 1 / C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;V = (3 - 1)* 2 = '''4'''&lt;/div&gt;
Archivo:MANDEL_Z4_iC2.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;4&lt;/sup&gt; + 1 / C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;V = (4 - 1)* 2 = '''6'''&lt;/div&gt;
Archivo:MANDEL_Z5_iC2.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;5&lt;/sup&gt; + 1 / C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;V = (5 - 1)* 2 = '''8'''&lt;/div&gt;
Archivo:MANDEL_Z6_iC2.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;6&lt;/sup&gt; + 1 / C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;V = (6 - 1)* 2 = '''10'''&lt;/div&gt;
Archivo:MANDEL_Z7_iC2.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;7&lt;/sup&gt; + 1 / C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;V = (7 - 1)* 2 = '''12'''&lt;/div&gt;
&lt;/gallery&gt; 
&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2_iC3.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + 1 / C&lt;sup&gt;3&lt;/sup&gt;''' &lt;br&gt;V = (2 - 1)* 3 = '''3'''&lt;/div&gt;
Archivo:MANDEL_Z2_iC3+1.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + 1 / (C&lt;sup&gt;3&lt;/sup&gt;+1)''' &lt;br&gt;V = (2 - 1)* 3 = '''3'''&lt;/div&gt;
&lt;/gallery&gt; 
&lt;br&gt;


=== Integrando en el mismo fractal una función de C y su inversa Z = Z&lt;sup&gt;m&lt;/sup&gt; + C i Z = Z&lt;sup&gt;m&lt;/sup&gt; + 1/C ===
La zona en color BLANCO intenso es el área de la intersección de los 2 sets.&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BC--Z2%2B1_C_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;Z = Z&lt;sup&gt;2&lt;/sup&gt; + 1 / C &lt;br&gt;Z = Z&lt;sup&gt;2&lt;/sup&gt; + C&lt;/div&gt;
Archivo:MANDEL_Z3%2BC--Z2%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;Z = Z&lt;sup&gt;2&lt;/sup&gt; + 1 / C &lt;br&gt;Z = Z&lt;sup&gt;3&lt;/sup&gt; + C&lt;/div&gt;
Archivo:MANDEL_Z2%2BC--Z3%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;Z = Z&lt;sup&gt;3&lt;/sup&gt; + 1 / C &lt;br&gt;Z = Z&lt;sup&gt;2&lt;/sup&gt; + C&lt;/div&gt;
Archivo:MANDEL_Z3%2BC--Z3%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;Z = Z&lt;sup&gt;3&lt;/sup&gt; + 1 / C &lt;br&gt;Z = Z&lt;sup&gt;3&lt;/sup&gt; + C&lt;/div&gt;
Archivo:MANDEL_Z4%2BC--Z4%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;Z = Z&lt;sup&gt;4&lt;/sup&gt; + 1 / C &lt;br&gt;Z = Z&lt;sup&gt;4&lt;/sup&gt; + C&lt;/div&gt;
Archivo:MANDEL_Z3%2BC--Z4%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;Z = Z&lt;sup&gt;4&lt;/sup&gt; + 1 / C &lt;br&gt;Z = Z&lt;sup&gt;3&lt;/sup&gt; + C&lt;/div&gt;
&lt;/gallery&gt;

== Z = ( Z&lt;sup&gt;m&lt;/sup&gt; / C&lt;sup&gt;m&lt;/sup&gt; ) + C ==
&lt;gallery&gt;
Archivo:MANDEL_(Z4_C4)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = (Z&lt;sup&gt;4&lt;/sup&gt; / C&lt;sup&gt;4&lt;/sup&gt;) + C'''&lt;/div&gt;
Archivo:MANDEL_(Z8_C8)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = (Z&lt;sup&gt;8&lt;/sup&gt; / C&lt;sup&gt;8&lt;/sup&gt;) + C'''&lt;/div&gt;
&lt;/gallery&gt;

== Z = Z&lt;sup&gt;m&lt;/sup&gt; + C + C&lt;sup&gt;p&lt;/sup&gt; + 1/ C + 1/ C&lt;sup&gt;q&lt;/sup&gt; ==
También podemos añadir más sumandos a la función Z&lt;sup&gt;m&lt;/sup&gt;, combinando C, C&lt;SUP&gt;p&lt;/SUP&gt;, 1/C y 1/C&lt;SUP&gt;q&lt;/SUP&gt; en grupos de 2, 3 o 4, veamos que sucede si agrupamos C&lt;SUP&gt;2&lt;/SUP&gt;, 1/C y 1/C&lt;SUP&gt;2&lt;/SUP&gt; de 2,3 o 4 formas ..: 
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BC%2BC2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C + C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;&lt;/div&gt;
Archivo:MANDEL_Z2%2BC%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C + 1/C''' &lt;br&gt;&lt;/div&gt;
Archivo:MANDEL_Z2%2BC%2B1_C2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C + 1/C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;&lt;/div&gt;
Archivo:MANDEL_Z2%2BC2%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C&lt;sup&gt;2&lt;/sup&gt;+ 1/C'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC2%2B1_C2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C&lt;sup&gt;2&lt;/sup&gt; + 1/C&lt;sup&gt;2&lt;/sup&gt;''' &lt;br&gt;&lt;/div&gt;
Archivo:MANDEL_Z2%2B1_C%2B1_C2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + 1/C + 1/ C&lt;sup&gt;2&lt;/sup&gt; ''' &lt;br&gt;&lt;/div&gt;
&lt;/gallery&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BC%2BC2%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C + C&lt;SUP&gt;2&lt;/SUP&gt; + 1/C'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC%2BC2%2B1_C2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C + C&lt;SUP&gt;2&lt;/SUP&gt; + 1/C&lt;sup&gt;2&lt;/sup&gt;'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC%2B1_C%2B1_C2_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C + 1/C + 1/C&lt;sup&gt;2&lt;/sup&gt;'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC2%2B1_C%2B1_C2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C&lt;SUP&gt;2&lt;/SUP&gt; + 1/C + 1/C&lt;sup&gt;2&lt;/sup&gt;'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC%2BC2%2B1_C%2B1_C2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C + C&lt;sup&gt;2&lt;/sup&gt; + 1/C + 1/C&lt;sup&gt;2&lt;/sup&gt;'''&lt;/div&gt;
&lt;/gallery&gt;
&lt;br&gt;
A continuación más combinaciones con otros exponentes:
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BC%2B1_C3_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + C + 1/ C&lt;sup&gt;3&lt;/sup&gt;'''&lt;/div&gt;
&lt;/gallery&gt;

== Z = Z&lt;sup&gt;m&lt;/sup&gt; + polinomios de C ==
Podemos combinar diferentes potencias de C y/o Z sumándolas a Z&lt;sup&gt;m&lt;/sup&gt; , veamos qué sucede:
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BC_(C2%2B1)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C /(C&lt;sup&gt;2&lt;/sup&gt;+1) + C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2BC_(C2-1)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C /(C&lt;sup&gt;2&lt;/sup&gt;-1)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Z2_%2B_C2_(C4%2B_0,1).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C&lt;sup&gt;2&lt;/sup&gt; /(C&lt;sup&gt;4&lt;/sup&gt; + 0.1)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Z2_%2B_C2_(C4-0,25).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C&lt;sup&gt;2&lt;/sup&gt; / (C&lt;sup&gt;4&lt;/sup&gt; - 0.25)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
=== El caso de la función: Z=Z&lt;sup&gt;2&lt;/sup&gt; + 1 /(C&lt;sup&gt;m&lt;/sup&gt;-1) ===
&lt;gallery&gt;
Archivo:MANDEL_Z2%2B1_(C2-1)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + 1 /(C&lt;sup&gt;2&lt;/sup&gt;-1)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2B1_(C3-1)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + 1 /(C&lt;sup&gt;3&lt;/sup&gt;-1)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2B1_(C4-1)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;Z'''=Z&lt;sup&gt;2&lt;/sup&gt; + 1 /(C&lt;sup&gt;4&lt;/sup&gt;-1)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

== Z = Z&lt;sup&gt;m&lt;/sup&gt; + polinomios mixtos de C i Z ==
Podemos sumar a Z&lt;sup&gt;m&lt;/sup&gt; polinomios mixtos de C i Z , veamos qué sucede:
=== Z = Z&lt;sup&gt;2&lt;/sup&gt; + C/ (Z&lt;sup&gt;2&lt;/sup&gt; + k) ===
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BC_(Z2-0,001)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C / (Z&lt;sup&gt;2&lt;/sup&gt;- 0.001)'''&lt;br&gt; Zo = (0,0i)''' x 1000'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC_(Z2-0,01)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C / (Z&lt;sup&gt;2&lt;/sup&gt;- 0.01)'''&lt;br&gt; Zo = (0,0i)''' x 100'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC_(Z2-0,1)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C / (Z&lt;sup&gt;2&lt;/sup&gt;- 0.1)'''&lt;br&gt; Zo = (0,0i)''' x 10'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC_(Z2%2B0,1)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C / (Z&lt;sup&gt;2&lt;/sup&gt;+ 0.1)'''&lt;br&gt; Zo = (0,0i)''' x 10'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC_(Z2%2B0,01)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C / (Z&lt;sup&gt;2&lt;/sup&gt;+ 0.01)'''&lt;br&gt; Zo = (0,0i)''' x 100'''&lt;/div&gt;
Archivo:MANDEL_Z2%2BC_(Z2%2B0,001)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C / (Z&lt;sup&gt;2&lt;/sup&gt;+ 0.001)'''&lt;br&gt; Zo = (0,0i)''' x 24,900'''&lt;/div&gt;
&lt;/gallery&gt;
=== Z = Z&lt;sup&gt;m&lt;/sup&gt; + C&lt;sup&gt;p&lt;/sup&gt;/Z&lt;sup&gt;q&lt;/sup&gt; + C ===
&lt;gallery&gt;
Archivo:Mandel_Z2%2BC2_Z2%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + (C&lt;sup&gt;2&lt;/sup&gt; /Z&lt;sup&gt;2&lt;/sup&gt;) + C '''&lt;br&gt; Zo = (0,0i) m=2, p=2,q=2&lt;/div&gt;
Archivo:MANDEL_Z2+C4_Z2+C.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + (C&lt;sup&gt;4&lt;/sup&gt; /Z&lt;sup&gt;2&lt;/sup&gt;) + C '''&lt;br&gt; Zo = (0,0i) m=2,p=4,q=2&lt;/div&gt;
Archivo:Mandel_Z2%2BC4_Z4%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + (C&lt;sup&gt;4&lt;/sup&gt; /Z&lt;sup&gt;4&lt;/sup&gt;) + C '''&lt;br&gt; Zo = (0,0i) m=2, p=4,q=4&lt;/div&gt;
Archivo:Mandel_Z2%2BC6_Z6%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + (C&lt;sup&gt;6&lt;/sup&gt; /Z&lt;sup&gt;6&lt;/sup&gt;) + C '''&lt;br&gt; Zo = (0,0i) m=2, p=6,q=6&lt;/div&gt;
Archivo:Mandel_Z4%2BC2_Z4%2BC.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;4&lt;/sup&gt; + (C&lt;sup&gt;2&lt;/sup&gt; /Z&lt;sup&gt;4&lt;/sup&gt;) + C '''&lt;br&gt; Zo = (0,0i) m=4, p=2,q=4&lt;/div&gt;
&lt;/gallery&gt;

=== Z= [(Z&lt;sup&gt;m&lt;/sup&gt;+C-1) / (m*Z&lt;sup&gt;m-1&lt;/sup&gt;+C- m)]&lt;sup&gt;2&lt;/sup&gt; ===
&lt;gallery&gt;
Archivo:MANDEL_MAGNET_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z&lt;sup&gt;2&lt;/sup&gt;+C-1) / (2*Z+C-2)]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i) '''MAGNET'''&lt;/div&gt;
Archivo:MANDEL_((Z2%2BC2-1)_(2XZ%2BC2-2))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z&lt;sup&gt;2&lt;/sup&gt;+C&lt;sup&gt;2&lt;/sup&gt;-1) / (2*Z+C&lt;sup&gt;2&lt;/sup&gt; -2)]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z2%2BC3-1)_(2XZ%2BC3-2))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z&lt;sup&gt;2&lt;/sup&gt;+C&lt;sup&gt;3&lt;/sup&gt;-1) / (2*Z+C&lt;sup&gt;3&lt;/sup&gt; -2)]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z3%2BC-1)_(3XZ2%2BC-3))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z&lt;sup&gt;3&lt;/sup&gt;+C-1) / (3*Z&lt;sup&gt;2&lt;/sup&gt;+C-3)]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z4%2BC-1)_(4XZ3%2BC-4))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z&lt;sup&gt;4&lt;/sup&gt;+C-1) / (4*Z&lt;sup&gt;3&lt;/sup&gt;+C-4)]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

=== Z= [(Z + C&lt;sup&gt;m&lt;/sup&gt;-1) / C&lt;sup&gt;m&lt;/sup&gt;]&lt;sup&gt;2&lt;/sup&gt; ===
&lt;gallery&gt;
Archivo:MANDEL_((Z%2BC-1)_(C%2B0))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C -1) / C]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC2-1)_(C2%2B0))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;2&lt;/sup&gt;-1) / C&lt;sup&gt;2&lt;/sup&gt;]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC3-1)_(C3%2B0))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;3&lt;/sup&gt;-1) / C&lt;sup&gt;3&lt;/sup&gt;]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC4-1)_(C4%2B0))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;4&lt;/sup&gt;-1) / C&lt;sup&gt;4&lt;/sup&gt;]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC5-1)_(C5))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;5&lt;/sup&gt;-1) / C&lt;sup&gt;5&lt;/sup&gt;]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
=== Z= [(Z + C&lt;sup&gt;m&lt;/sup&gt;-1) / C&lt;sup&gt;m&lt;/sup&gt;]&lt;sup&gt;3&lt;/sup&gt; ===
&lt;gallery&gt;
Archivo:MANDEL_((Z%2BC-1)_(C))3_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C-1) / C]&lt;sup&gt;3&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC2-1)_(C2))3_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;2&lt;/sup&gt;-1) / C&lt;sup&gt;2&lt;/sup&gt;]&lt;sup&gt;3&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC3-1)_(C3))3_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;3&lt;/sup&gt;-1) / C&lt;sup&gt;3&lt;/sup&gt;]&lt;sup&gt;3&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

=== Z= [(Z + C&lt;sup&gt;m&lt;/sup&gt;+1) / (C&lt;sup&gt;m&lt;/sup&gt; - 1)]&lt;sup&gt;2&lt;/sup&gt; ===
&lt;gallery&gt;
Archivo:MANDEL_((Z%2BC%2B1)_(C-1))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C +1) / (C -1]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC2%2B1)_(C2-1))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;2&lt;/sup&gt; +1) / (C&lt;sup&gt;2&lt;/sup&gt; -1]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC3%2B1)_(C3-1))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;3&lt;/sup&gt; +1) / (C&lt;sup&gt;3&lt;/sup&gt; -1]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC4%2B1)_(C4-1))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;4&lt;/sup&gt; +1) / (C&lt;sup&gt;4&lt;/sup&gt; -1)]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC5%2B1)_(C5-1))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;5&lt;/sup&gt; +1) / (C&lt;sup&gt;5&lt;/sup&gt; -1)]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
=== Z= [(Z + C&lt;sup&gt;m&lt;/sup&gt;-1) / (C&lt;sup&gt;m&lt;/sup&gt; + 1)]&lt;sup&gt;2&lt;/sup&gt; ===
&lt;gallery&gt;
Archivo:MANDEL_((Z%2BC-1)_(C%2B1))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C -1) / (C +1]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC2-1)_(C2%2B1))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;2&lt;/sup&gt; -1) / (C&lt;sup&gt;2&lt;/sup&gt; +1]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC3-1)_(C3%2B1))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;3&lt;/sup&gt; -1) / (C&lt;sup&gt;3&lt;/sup&gt; +1]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC4-1)_(C4%2B1))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;4&lt;/sup&gt; -1) / (C&lt;sup&gt;4&lt;/sup&gt; +1)]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_((Z%2BC5-1)_(C5%2B1))2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= [(Z + C&lt;sup&gt;5&lt;/sup&gt; -1) / (C&lt;sup&gt;5&lt;/sup&gt; +1)]&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

=== Otras combinaciones de Z y C ===
&lt;gallery&gt;
Archivo:mandel.jmb_001.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + C&lt;sup&gt;2&lt;/sup&gt; /(Z&lt;sup&gt;2&lt;/sup&gt;+C) + C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

== Más funciones de variable compleja ==
Pero existe una amplia variedad de funciones, en el dominio de los [[Número complejo|números complejos]], que pueden ser iteradas según el método de Mandelbrot. &lt;br&gt;
Voy a citar aquí algunos ejemplos, explicitando la parte real y la imaginaria:&lt;br&gt;&lt;br&gt;
''' Exp(Z)''' = [ Exp(x) * Cos(x), Exp(x) * Sin(y)i ] &lt;br&gt;
''' Sin(Z)''' = [ Sin(x) * ((Exp(y) + Exp(-y)) / 2), Cos(x) * ((Exp(y) - Exp(-y)) / 2)i ] &lt;br&gt;
''' Cos(Z)''' = [ Cos(x) * ((Exp(y) + Exp(-y)) / 2) , -Sin(x) * ((Exp(y) - Exp(-y)) / 2)i ] &lt;br&gt;
''' SinH(Z)''' = [ Cos(y) * ((Exp(x) - Exp(-x)) / 2) , Sin(Y) * ((Exp(x) + Exp(-x)) / 2)i ] &lt;br&gt;
''' CosH(Z)''' = [ Cos(y) * ((Exp(x) + Exp(-x)) / 2) , Sin(y) * ((Exp(x) - Exp(-x)) / 2)i ] &lt;br&gt;
''' LN(Z)''' = [ 0.5 * Log(x * x + y * y) , Atn(y / x)i ] &lt;br&gt;
''' SQR(Z)''' = [ (x * x + y * y)^0.25 * Cos(0.5 * Atn(y/x)) , (x * x + y * y)^0.25 * Sin(0.5 * Atn(y/x)) i ] &lt;br&gt;
''' ATN(Z)''' = [PI / 4 - (1 / 2) * Atn((1 - x^2 - y^2) / (2 * x)), -(1 / 4) * Log((1 - x^2 - y^2) ^2 + 4 * x^2) + (1 / 2) * Log((1 + y) ^2 + x^2) i]&lt;br&gt;

&lt;br&gt;
=== Z = Z&lt;sup&gt;m&lt;/sup&gt; + F(C) ===
A continuación algunos ejemplos de fractales por iteración de '''Z&lt;sup&gt;2&lt;/SUP&gt;''', pero transformando C según las funciones descritas anteriormente:
&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2+SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + Sin(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2B1_SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + 1/Sin(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2+SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + Cos(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2B1_SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + 1/Cos(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2+SINH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + SinH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2B1_SINH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + 1/SinH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2+COSH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + CosH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2B1_COSH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + 1/CosH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BTAN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + Tan(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2BCOTAN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + CoTan(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2BTANH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + TanH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2BTANH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + CoTanH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BSIN(C)_COSH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + Sin(C)/CosH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2BCOSH(C)_SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + CosH(C)/Sin(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2BCOS(C)_SINH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + Cos(C)/SinH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2BSINH(C)_COS(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + SinH(C)/Cos(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

&lt;gallery&gt;
Archivo:MANDEL_Z2%2BSIN(C)_SINH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + Sin(C)/SinH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2BSINH(C)_SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + SinH(C)/Sin(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2BSIN(C)_SINH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + Cos(C)/CosH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z2%2BSINH(C)_SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z=Z&lt;sup&gt;2&lt;/sup&gt; + CosH(C)/Cos(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BATN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= Z&lt;sup&gt;2&lt;/sup&gt; + ATan(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_-0,5XZ2%2BSQR(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= -0.5*Z&lt;sup&gt;2&lt;/sup&gt; + Sqr(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_-0,5XZ3%2BSQR(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z= -0.5*Z&lt;sup&gt;3&lt;/sup&gt; + Sqr(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

== Fractales por iteración de Exp(Z) ==
Esta función se descompone en una parte real y otra imaginaria: ''' Exp(Z)''' = [ Exp(x) * Cos(y), Exp(x) * Sin(y)i ] &lt;br&gt;
Puede ser utilizada como función iterativa o como función transformadora de C = (Cx,Cyi), o simultáneamente:
=== Como función iterativa ===
&lt;gallery&gt;
Archivo:MANDEL_EXP(Z)%2BC.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z)+ C '''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_ZxExp(Z)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z * Exp(Z)+ C '''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

=== Como función transformadora de C ===
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BEXP(C).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + Exp(C) '''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
=== Como función iterativa i transformadora de C, simultáneamente ===
&lt;gallery&gt;
Archivo:EXP(C3_Z3).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(C&lt;sup&gt;3&lt;/sup&gt;/Z&lt;sup&gt;3&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Mandel_Exp(_(Z%5E2%2Bk3xZ)_SQR(C%5E3)).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp[(Z&lt;sup&gt;2&lt;/sup&gt;-1.00001*Z)/Sqr(C&lt;sup&gt;3&lt;/sup&gt;)]'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Mandel_Exp(_(Z%5E2%2Bk3xZ)_C%5E3)_.jmb.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp[(Z&lt;sup&gt;2&lt;/sup&gt;- 1.00001*Z)/C&lt;sup&gt;3&lt;/sup&gt;]'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
==== El caso de la función Z = Exp[(Z&lt;sup&gt;2&lt;/sup&gt; + k * Z) / F(C&lt;sup&gt;m&lt;/sup&gt;)] ====
Esta función es muy sensible a Zo, y también al coeficiente ('''k''') que multiplica a Z. Veamos algunos ejemplos interesantes:
&lt;gallery&gt;
Archivo:Mandel Exp( (Z^2+k3xZ) Sqr(C^3) ).jmb.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp[(Z&lt;sup&gt;2&lt;/sup&gt;+ k*Z)/ Sqr(C&lt;sup&gt;3&lt;/sup&gt;)]'''&lt;br&gt; Zo = (1,1i) ''' k = 1'''&lt;/div&gt;
Archivo:Mandel_Exp((Z2-0,8Z)_Sqr(C3))_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp[(Z&lt;sup&gt;2&lt;/sup&gt;+ k*Z)/ Sqr(C&lt;sup&gt;3&lt;/sup&gt;)]'''&lt;br&gt; Zo = (1,1i) ''' k = -0.8 '''&lt;/div&gt;
Archivo:MANDEL_EXP(Z2_SQR(C7))_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp[(Z&lt;sup&gt;2&lt;/sup&gt;+ k*Z)/ Sqr(C&lt;sup&gt;7&lt;/sup&gt;)]'''&lt;br&gt; Zo = (1,1i) ''' k = 0.0 '''&lt;/div&gt;
Archivo:MANDEL_EXP((Z2-0,8Z)_SQR(C7))_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp[(Z&lt;sup&gt;2&lt;/sup&gt;+ k*Z)/ Sqr(C&lt;sup&gt;7&lt;/sup&gt;)]'''&lt;br&gt; Zo = (1,1i) ''' k = -0.8 '''&lt;/div&gt;
Archivo:MANDEL_EXP((Z2%2B3Z)_LN(C9))_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp[(Z&lt;sup&gt;2&lt;/sup&gt;+ k*Z)/ LN(C&lt;sup&gt;9&lt;/sup&gt;)]'''&lt;br&gt; Zo = (1,1i) ''' k = 3.0 '''&lt;/div&gt;
&lt;/gallery&gt;

==== El caso de la función Z&lt;sub&gt;n+1&lt;/sub&gt; = Exp(Z&lt;sub&gt;n&lt;/sub&gt; / C &lt;sup&gt;m&lt;/sup&gt;) ====
&lt;gallery&gt;
Archivo:MANDEL_EXP(Z_C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z /C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_EXP(Z_C2)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z /C&lt;sup&gt;2&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_EXP(Z_C3)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z /C&lt;sup&gt;3&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_EXP(Z_C4)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z /C&lt;sup&gt;4&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_EXP(Z_C5)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z /C&lt;sup&gt;5&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_EXP(Z_C6)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z /C&lt;sup&gt;6&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt; 
&lt;br&gt;
==== El caso de la función Z&lt;sub&gt;n+1&lt;/sub&gt; = Exp(Z&lt;sub&gt;n&lt;/sub&gt; / C &lt;sup&gt;m&lt;/sup&gt;) + C &lt;sup&gt;p&lt;/sup&gt; ====
&lt;gallery&gt;
Archivo:MANDEL_EXP(Z_C6)%2BC3_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z /C&lt;sup&gt;6&lt;/sup&gt;) + C &lt;sup&gt;3&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_EXP(Z_C8)%2BC4_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z /C&lt;sup&gt;8&lt;/sup&gt;) + C &lt;sup&gt;4&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_EXP(Z_C8)%2BC2_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z /C&lt;sup&gt;8&lt;/sup&gt;) + C &lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

==== El caso de la función Z&lt;sub&gt;n+1&lt;/sub&gt; = Exp(Z&lt;sub&gt;n&lt;/sub&gt;&lt;sup&gt;p&lt;/sup&gt; / C &lt;sup&gt;p&lt;/sup&gt;) ====
&lt;gallery&gt;
Archivo:Mandel_EXP(Z3_C3).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z&lt;sup&gt;3&lt;/sup&gt;/C&lt;sup&gt;3&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_EXP(Z4_C4).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z&lt;sup&gt;4&lt;/sup&gt;/C&lt;sup&gt;4&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
&lt;br&gt;
==== El caso de la función Z&lt;sub&gt;n+1&lt;/sub&gt; = Z&lt;sub&gt;n&lt;/sub&gt;&lt;sup&gt;q&lt;/sup&gt; * Exp(Z&lt;sub&gt;n&lt;/sub&gt; / C &lt;sup&gt;p&lt;/sup&gt;) + C ====
&lt;gallery&gt;
Archivo:Mandel_Z2xEXP(Z_C)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; * Exp(Z/C)+ C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Mandel_Z3xEXP(Z_C)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt; * Exp(Z/C)+ C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Mandel_Z4xEXP(Z_C)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;4&lt;/sup&gt; * Exp(Z/C)+ C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Mandel_Z5xEXP(Z_C)%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;5&lt;/sup&gt; * Exp(Z/C)+ C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

==== El caso de la función Z&lt;sub&gt;n+1&lt;/sub&gt; = Exp[ Z&lt;sub&gt;n&lt;/sub&gt;&lt;sup&gt;2&lt;/sup&gt; / (C &lt;sup&gt;m&lt;/sup&gt; + C &lt;sup&gt;p&lt;/sup&gt;) ] ====
Aparece un número de lóbulos centrales = '''m''', y un número de aristas exteriores = '''p''', siendo '''m&lt;p'''.
&lt;gallery&gt;
Archivo:Exp(Z2 (C5 + C)).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp[Z&lt;sup&gt;2&lt;/sup&gt; / ( C&lt;sup&gt;5&lt;/sup&gt; + C )]'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Mandel_EXP(_Z2_(C6%2BC3)).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp[Z&lt;sup&gt;2&lt;/sup&gt; / ( C&lt;sup&gt;6&lt;/sup&gt; + C&lt;sup&gt;3&lt;/sup&gt; )]'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Mandel_EXP(_Z2_(C8%2BC4)).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp[Z&lt;sup&gt;2&lt;/sup&gt; / ( C&lt;sup&gt;8&lt;/sup&gt; + C&lt;sup&gt;4&lt;/sup&gt; )]'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
&lt;br&gt;
==== El caso de la función Z&lt;sub&gt;n+1&lt;/sub&gt; = Z&lt;sub&gt;n&lt;/sub&gt;&lt;sup&gt;m&lt;/sup&gt; * Exp[ Cos(Z&lt;sub&gt;n&lt;/sub&gt;)] + 1/C ====
Aparecen un número de aristas = '''m'''.
&lt;gallery&gt;
Archivo:MANDEL_Z2xExp(Cos(Z))%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt;* Exp[ Cos(Z)] + 1/C '''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z3xExp(Cos(Z))%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt;* Exp[ Cos(Z)] + 1/C '''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z4xExp(Cos(Z))%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;4&lt;/sup&gt;* Exp[ Cos(Z)] + 1/C '''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
== Fractales per iteración de Sin(Z) ==
Esta función se descompone en una parte real y otra imaginaria: ''' Sin(Z)''' = [ Sin(x) * ((Exp(y) + Exp(-y)) / 2), Cos(x) * ((Exp(y) - Exp(-y)) / 2)i ] &lt;br&gt;
Puede ser utilizada como función iterativa o como función transformadora de los puntos C = (Cx,Cyi), simultáneamente:
=== Como función iterativa ===


=== Como función transformadora de C ===
&lt;gallery&gt;
Archivo:MANDEL_Z2+SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt;+Sin(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z3+SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt;+Sin(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z4+SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;4&lt;/sup&gt;+Sin(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z5+SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;5&lt;/sup&gt;+Sin(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z6+SIN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;6&lt;/sup&gt;+Sin(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
&lt;br&gt;
&lt;gallery&gt;
Archivo:MANDEL_Z2+SIN(C2)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt;+Sin(C&lt;sup&gt;2&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z3+SIN(C2)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;3&lt;/sup&gt;+Sin(C&lt;sup&gt;2&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_Z4+SIN(C2)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;4&lt;/sup&gt;+Sin(C&lt;sup&gt;2&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

=== Como función iterativa y transformadora de C, simultáneamente ===
&lt;gallery&gt;
Archivo:MANDEL_SIN(COSH(Z)xC3)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(CosH(Z)*C&lt;sup&gt;3&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

==== El caso de la función Z&lt;sub&gt;n+1&lt;/sub&gt; = Sin(Z&lt;sub&gt;n&lt;/sub&gt; * C &lt;sup&gt;m&lt;/sup&gt;) ====
&lt;gallery&gt;
Archivo:MANDEL_SIN(ZxSQR(C))_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z*C&lt;sup&gt;0.5&lt;/sup&gt;)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
Archivo:MANDEL_SIN(ZxC)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z*C)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
Archivo:MANDEL_SIN(ZxC2).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z*C&lt;sup&gt;2&lt;/sup&gt;)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
Archivo:MANDEL_SIN(ZxC3).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z*C&lt;sup&gt;3&lt;/sup&gt;)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
Archivo:MANDEL_SIN(ZxC10)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z*C&lt;sup&gt;10&lt;/sup&gt;)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
Archivo:MANDEL_SIN(SQR(Z)xC3)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z&lt;sup&gt;0.5&lt;/sup&gt;*C&lt;sup&gt;3&lt;/sup&gt;)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
&lt;/gallery&gt;

==== El caso de la función Z&lt;sub&gt;n+1&lt;/sub&gt; = Sin(Z&lt;sub&gt;n&lt;/sub&gt; / C &lt;sup&gt;m&lt;/sup&gt;) ====
&lt;gallery&gt;
Archivo:MANDEL_SIN(Z_SQR(C))_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z/C&lt;sup&gt;0.5&lt;/sup&gt;)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
Archivo:MANDEL_SIN(Z_C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z/C)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
Archivo:MANDEL_SIN(Z_C2)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z/C&lt;sup&gt;2&lt;/sup&gt;)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
Archivo:MANDEL_SIN(Z_C3)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z/C&lt;sup&gt;3&lt;/sup&gt;)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
Archivo:MANDEL_SIN(Z_C10)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Sin(Z/C&lt;sup&gt;10&lt;/sup&gt;)'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
&lt;/gallery&gt;

== Fractales por iteración de Cos(Z) ==
Esta función se descompone en una parte real y otra imaginaria: ''' ' Cos(Z)''' = [ Cos(x)*((Exp(y)+Exp(-y)) / 2), -Sin(x)*((Exp(y)-Exp(-y))/2)i ] &lt;br&gt;
Puede ser utilizada como función iterativa o como función transformadora de C = (Cx,Cyi), o simultáneamente
=== Como función iterativa ===
&lt;gallery&gt;
Archivo:MANDEL_COS(Z)%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z)+ 1/C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_COS(Z)%2BLN(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z)+ LN(C) '''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_COS(Z3)%2B1_C.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z&lt;SUP&gt;3&lt;/SUP&gt;)+ 1/C'''&lt;br&gt; Zo = (0.2,0.3i)&lt;/div&gt;
&lt;/gallery&gt;

=== Como función transformadora de C ===
&lt;gallery&gt;
Archivo:MANDEL_Z2%2BCOS(Z).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + Cos( C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
=== Como función iterativa y transformadora de C, simultáneamente ===
&lt;gallery&gt;
Archivo:MANDEL_COS(Z)%2BCOS(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z) + Cos(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_COS(C_Z)_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(C/Z)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
==== El caso de la función Z&lt;sub&gt;n+1&lt;/sub&gt; = Cos(Z&lt;sub&gt;n&lt;/sub&gt; * C &lt;sup&gt;m&lt;/sup&gt;) ====
&lt;gallery&gt;
Archivo:MANDEL_COS(ZxSQR(C))_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z*C&lt;sup&gt;0.5&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Mandel_Cos(ZxC).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z*C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Mandel_Cos(ZxC2).jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z*C&lt;sup&gt;2&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:Mandel_Cos(ZxC3).jmb.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z*C&lt;sup&gt;3&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
&lt;br&gt;

==== El caso de la función Z&lt;sub&gt;n+1&lt;/sub&gt; = Cos(Z&lt;sub&gt;n&lt;/sub&gt;/C &lt;sup&gt;m&lt;/sup&gt;) ====
&lt;gallery&gt;
Archivo:MANDEL_COS(Z_SQR(C))_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z/C&lt;SUP&gt;0.5&lt;/SUP&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_COS(Z_C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z/C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_COS(Z_C2)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z/C&lt;SUP&gt;2&lt;/SUP&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_COS(Z_C3)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z/C&lt;SUP&gt;3&lt;/SUP&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
Archivo:MANDEL_COS(Z_C4)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Cos(Z/C&lt;SUP&gt;4&lt;/SUP&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
&lt;br&gt;

== Fractales por iteración de SinH(Z) ==
Esta función se descompone en una parte real y otra imaginaria: ''' SinH(Z)''' = [ Cos(y) * ((Exp(x) - Exp(-x)) / 2) , Sin(Y) * ((Exp(x) + Exp(-x)) / 2)i ] &lt;br&gt;
Puede ser utilizada como función iterativa o como función transformadora de C = (Cx,Cyi), o simultáneamente:
=== Como función iterativa ===
&lt;gallery&gt;
MANDEL_SinH(Z)%2B1_C_BIG.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = SinH(Z) + 1/C'''&lt;br&gt; Zo = (0.91, -0.08i)&lt;/div&gt;
MANDEL_SinH(Z)%2B1_C_BIG2.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = SinH(Z) + 1/C'''&lt;br&gt; Zo = (0.90, -0.05i)&lt;/div&gt;
MANDEL_SinH(Z)%2B1_C2_BIG.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = SinH(Z) + 1/C&lt;sup&gt;2&lt;/sup&gt;'''&lt;br&gt; Zo = (1, 0.1i)&lt;/div&gt;
MANDEL_SinH(Z2)%2B1_C_BIG.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = SinH(Z&lt;sup&gt;2&lt;/sup&gt;) + 1/C'''&lt;br&gt; Zo = (1, -1i)&lt;/div&gt;
&lt;/gallery&gt;

=== Como función transformadora de C ===
&lt;gallery&gt;
MANDEL_Z2%2BSINH(C)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + SinH(C)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
MANDEL_Z2%2BSINH(1_C3)_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Z&lt;sup&gt;2&lt;/sup&gt; + SinH(1/ C&lt;sup&gt;3&lt;/sup&gt;)'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;
&lt;br&gt;

=== Como función iterativa i transformadora de C, simultáneamente ===
&lt;gallery&gt;
MANDEL_SinH(Z_C)_BIG.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = SinH(Z / C )'''&lt;br&gt; Zo = (0,1i)&lt;/div&gt;
MANDEL_SINH(Z)_C_mediumB.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = SinH(Z)/ C'''&lt;br&gt; Zo = (1,0i)&lt;/div&gt;
&lt;/gallery&gt; 
&lt;br&gt;&lt;br&gt;

== Fractales por iteración de CosH(Z) ==
Esta función se descompone en una parte real y otra imaginaria: ''' CosH(Z)''' = [ Cos(y) * ((Exp(x) + Exp(-x)) / 2) , Sin(y) * ((Exp(x) - Exp(-x)) / 2)i ] &lt;br&gt;
Puede ser utilizada como función iterativa o como función transformadora de C = (Cx,Cyi), o simultáneamente:
=== Como función iterativa ===
&lt;gallery&gt;
MANDEL_COSH(Z)%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = CosH(Z) + 1/C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
MANDEL_COSH(Z2)%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = CosH(Z&lt;sup&gt;2&lt;/sup&gt;) + 1/C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
MANDEL_COSH(Z3)%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = CosH(Z&lt;sup&gt;3&lt;/sup&gt;) + 1/C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
MANDEL_COSH(Z4)%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = CosH(Z&lt;sup&gt;4&lt;/sup&gt;) + 1/C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
MANDEL_COSH(Z5)%2B1_C_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = CosH(Z&lt;sup&gt;5&lt;/sup&gt;) + 1/C'''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

== Fractales por iteración de combinaciones de diferentes funciones de Z ==
&lt;gallery&gt;
MANDEL_SinH(Z)xSin(Z)%2BC_BIG.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = SinH(Z) * Sin(Z) + C '''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
MANDEL_CosH(Exp(Z2))%2BC_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = CosH[Exp(Z&lt;sup&gt;2&lt;/sup&gt;)]+ C '''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
MANDEL_EXP(Z_C5)%2BLN(Z)%2BZ_medium.jpg|&lt;div style=&quot;text-align: center;&quot;&gt;'''Z = Exp(Z/C&lt;sup&gt;5&lt;/sup&gt;)+ Ln(Z) + Z '''&lt;br&gt; Zo = (0,0i)&lt;/div&gt;
&lt;/gallery&gt;

== Más fractales según el método de Mandelbrot ==
Aquí se muestra un ejemplo de iteración de dos funciones F(X) y F(Y), por adición de cada uno de los puntos del plano C(X,Y), y la introducción de una tercera función F(Z) que desequilibra el punto de convergencia.&lt;br&gt;
'''Xn+1 = Xn - Sin(Yn) + C(X) .. Yn+1 = Yn - Sin( Xn) + C(Y) .. Zn+1 = Zn - Cos( Xn + Yn) '''
&lt;br&gt;
&lt;gallery&gt;
MANDEL_JMB01a_medium.jpg
MANDEL_JMB01_medium.jpg
&lt;/gallery&gt;

=references=
*Computer Methods and Borel Summability Applied to Feigenbaum's Equation By Jean Pierre Eckmann
Format Hardback | 297 pages, Publication date 01 May 1985, Publisher Springer , Publication City/Country United States , ISBN10 0387152156, ISBN13 9780387152158
* http://mathoverflow.net/questions/157309/power-series-expansion-of-the-koenigs-function?rq=1
* T. M. CHERRY, A singular case of iteration of analytic functions: A contribution to the small divisor problem. In: Nonlinear Problems of Engineering, W. F. AMES (Ed.), New York, 1964, 29–50.
* Cherry, T. M., &quot;A Singular Case of Iteration of Analytic Functions: A Contribution to the Small-Divisor Problem,&quot; in Nonlinear Problems of Engineering (edited by W. F. Ames), Academic Press, New York, 1964, 29-50.
* MR178125 30.40 (57.48) Cherry, T. M. A singular case of iteration of analytic functions: A contribution to the small-divisor problem. 1964 Nonlinear Problems of Engineering pp. 29–50 Academic Press, New York

{{user language|pl|N}}
{{user language|en|2}}.</text>
      <sha1>qq5zip0a5bffwsvazgffvcmz8ygksgu</sha1>
    </revision>
  </page>
  <page>
    <title>Chess Opening Theory/1. d4/1...c6</title>
    <ns>0</ns>
    <id>148548</id>
    <revision>
      <id>4668938</id>
      <parentid>4668883</parentid>
      <timestamp>2026-09-05T13:32:15Z</timestamp>
      <contributor>
        <username>~2026-48234-29</username>
        <id>3625228</id>
      </contributor>
      <comment>/* Theory table london is bad! */</comment>
      <origin>4668938</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1876" sha1="9apxefvi6b6hbrqlo7bx105hymp7f27" xml:space="preserve">{{Chess Opening Theory/Position
|Queen's Pawn opening
|moves=1.d4 c6
|eco=[[Chess/ECOA|A40]]
|parent=[[../|Queens Pawn Opening]]
}}
== 1...c6 ==

'''1...c6''' is a transpositional tool. Black gives White the option of changing their mind and playing an e4 opening instead.

After [[/2. c4|'''2. c4''']], Black can play 2...d5 and transpose into a [[Chess Opening Theory/1. d4/1...d5/2. c4/2...c6|Slav defence]], as if they had played 1. d4 d5 2. c4 c6. 

With this move order, White has the option of [[/2. e4|'''2. e4''']], where 2...d4 will transpose into a [[Chess Opening Theory/1. e4/1...c6/2. d4/2...d5|Caro-Kann]], as if they had played 1. e4 c6 2. d4 d5. 

However, if White plays something else, like '''2. Bf4''', going for a [[Chess Opening Theory/1. d4/1...d5/2. Bf4|Accelerated London]]-style set-up where Black might like to play ...c5 at some point, they may regret having given up a tempo on ...c6 now. miguel funk london is trash i love tomboy and femboy 

==Theory table ==
{{Chess Opening Theory/Table}}

'''1. d4 c6 '''
&lt;table border=&quot;0&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot;&gt;
	&lt;tr&gt;
		&lt;th&gt;&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;2&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;3&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;4&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;5&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;6&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;7&lt;/th&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;right&quot;&gt;[[Chess/Slav Defence|Slav Defence]]&lt;/th&gt;
		&lt;td&gt;[[/2. c4|c4]]&lt;br&gt;d5&lt;/td&gt;
		&lt;td&gt;Nf3&lt;br&gt;Nf6&lt;/td&gt;
		&lt;td&gt;Nc3&lt;br&gt;dxc4&lt;/td&gt;
		&lt;td&gt;a4&lt;br&gt;Bf5&lt;/td&gt;
		&lt;td&gt;e3&lt;br&gt;e6&lt;/td&gt;
		&lt;td&gt;Bxc4&lt;br&gt;Bb4&lt;/td&gt;
		&lt;td&gt;=&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;right&quot;&gt;[[Chess/Caro-Kann Defence|Caro-Kann Defence]]&lt;/th&gt;
		&lt;td&gt;[[/2. e4|e4]]&lt;br&gt;d5&lt;/td&gt;
		&lt;td&gt;Nc3&lt;br&gt;dxe4&lt;/td&gt;
		&lt;td&gt;Nxe4&lt;br&gt;Bf5&lt;/td&gt;
		&lt;td&gt;Ng3&lt;br&gt;Bg6&lt;/td&gt;
		&lt;td&gt;Nf3&lt;br&gt;Nd7&lt;/td&gt;
		&lt;td&gt;h4&lt;br&gt;h6&lt;/td&gt;
		&lt;td&gt;=&lt;/td&gt;
	&lt;/tr&gt;
&lt;/table&gt;
{{ChessMid}}
{{wikipedia|Queen's Pawn}}
==References==
{{reflist}}
===See also===
{{BCO2}}
{{NCO}}
{{Chess Opening Theory/Footer}}</text>
      <sha1>9apxefvi6b6hbrqlo7bx105hymp7f27</sha1>
    </revision>
    <revision>
      <id>4668939</id>
      <parentid>4668938</parentid>
      <timestamp>2026-09-05T13:35:39Z</timestamp>
      <contributor>
        <username>~2026-48234-29</username>
        <id>3625228</id>
      </contributor>
      <comment>deleated the troll</comment>
      <origin>4668939</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1823" sha1="2ijw960vu406j4ulury012q2jy56sku" xml:space="preserve">{{Chess Opening Theory/Position
|Queen's Pawn opening
|moves=1.d4 c6
|eco=[[Chess/ECOA|A40]]
|parent=[[../|Queens Pawn Opening]]
}}
== 1...c6 ==

'''1...c6''' is a transpositional tool. Black gives White the option of changing their mind and playing an e4 opening instead.

After [[/2. c4|'''2. c4''']], Black can play 2...d5 and transpose into a [[Chess Opening Theory/1. d4/1...d5/2. c4/2...c6|Slav defence]], as if they had played 1. d4 d5 2. c4 c6. 

With this move order, White has the option of [[/2. e4|'''2. e4''']], where 2...d4 will transpose into a [[Chess Opening Theory/1. e4/1...c6/2. d4/2...d5|Caro-Kann]], as if they had played 1. e4 c6 2. d4 d5. 

However, if White plays something else, like '''2. Bf4''', going for a [[Chess Opening Theory/1. d4/1...d5/2. Bf4|Accelerated London]]-style set-up where Black might like to play ...c5 at some point, they may regret having given up a tempo on ...c6 now. 

==Theory table ==
{{Chess Opening Theory/Table}}

'''1. d4 c6 '''
&lt;table border=&quot;0&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot;&gt;
	&lt;tr&gt;
		&lt;th&gt;&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;2&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;3&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;4&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;5&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;6&lt;/th&gt;
		&lt;th align=&quot;left&quot;&gt;7&lt;/th&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;right&quot;&gt;[[Chess/Slav Defence|Slav Defence]]&lt;/th&gt;
		&lt;td&gt;[[/2. c4|c4]]&lt;br&gt;d5&lt;/td&gt;
		&lt;td&gt;Nf3&lt;br&gt;Nf6&lt;/td&gt;
		&lt;td&gt;Nc3&lt;br&gt;dxc4&lt;/td&gt;
		&lt;td&gt;a4&lt;br&gt;Bf5&lt;/td&gt;
		&lt;td&gt;e3&lt;br&gt;e6&lt;/td&gt;
		&lt;td&gt;Bxc4&lt;br&gt;Bb4&lt;/td&gt;
		&lt;td&gt;=&lt;/td&gt;
	&lt;/tr&gt;
	&lt;tr&gt;
		&lt;th align=&quot;right&quot;&gt;[[Chess/Caro-Kann Defence|Caro-Kann Defence]]&lt;/th&gt;
		&lt;td&gt;[[/2. e4|e4]]&lt;br&gt;d5&lt;/td&gt;
		&lt;td&gt;Nc3&lt;br&gt;dxe4&lt;/td&gt;
		&lt;td&gt;Nxe4&lt;br&gt;Bf5&lt;/td&gt;
		&lt;td&gt;Ng3&lt;br&gt;Bg6&lt;/td&gt;
		&lt;td&gt;Nf3&lt;br&gt;Nd7&lt;/td&gt;
		&lt;td&gt;h4&lt;br&gt;h6&lt;/td&gt;
		&lt;td&gt;=&lt;/td&gt;
	&lt;/tr&gt;
&lt;/table&gt;
{{ChessMid}}
{{wikipedia|Queen's Pawn}}
==References==
{{reflist}}
===See also===
{{BCO2}}
{{NCO}}
{{Chess Opening Theory/Footer}}</text>
      <sha1>2ijw960vu406j4ulury012q2jy56sku</sha1>
    </revision>
  </page>
  <page>
    <title>User:Neoptolemus/Reading list</title>
    <ns>2</ns>
    <id>151245</id>
    <revision>
      <id>4668929</id>
      <parentid>3279564</parentid>
      <timestamp>2026-09-05T12:33:52Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668929</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1916" sha1="j8ojhw4ngilw2q9vk67miyxd6nfbhuc" xml:space="preserve">The following is a list of existing books on topics I find interesting, created for my own use so that I can quickly find something fascinating to read and/or edit. [[User:Neoptolemus|'''Νεοπτόλεμος''']] ( [[User talk:Neoptolemus|talk]] &amp;#124; [[Special:Emailuser/Neoptolemus|email]] &amp;#124; [[Special:Contributions/Neoptolemus|contribs]] ) 01:13, 6 March 2008 (UTC)


{|width=&quot;100%&quot; align=&quot;center&quot; cellpadding=&quot;4&quot; style=&quot;text-align:left; background-color: transparent;color:inherit;&quot;
| style=&quot;text-align:center&quot; | 
|style=&quot;width:33%&quot; | 
*[[Chess]]
*[[Chess Opening Theory]]
*[[Astronomy]]
*[[International Relations]]
*[[American Politics]]
*[[Introduction to Latin American Studies]]
*[[Comparative Politics]]
*[[Political Theory]]
**[[Politicaltheory]]
*[[United States Government]]
*[[Introduction to Sociology]]
*[[Mythology]]
*[[Greek Mythology]]
*[[Indian Mythology]]
*[[Conlang]]
*[[Buddhist Philosophy]]
*[[Marxism, Communism, and Socialism]]
| style=&quot;text-align:center&quot; | 
|style=&quot;width:33%&quot; | 
*[[Utopia]]
*[[Political Philosophy: Ancient to Renaissance|Political Philosophy]]
*[[Theology 1: Philosophy of Religion]]
*[[Theology 2: Comparative Religion]]
*[[Theology 3: Descriptive Religion]]
*[[History of Islamic Civilization]]
*[[History of Islam]]
*[[Hinduism]]
*[[Bahá'í Faith]]
*[[Buddhism]]
*[[Sikhism]]
*[[Sufism]]
*[[Islam]]
*[[Ancient History]]
*[[Modern History]]
*[[World History]]
*[[European History]]
| style=&quot;text-align:center&quot; | 
|style=&quot;width:33%&quot; | 
*[[Latin-American History]]
*[[The Seven Wonders of the World]]
*[[New Zealand History]]
*[[Australian History]]
*[[Canadian History]]
*[[English History]]
*[[Ethiopian History]]
*[[History of Greece]]
*[[History of the United Kingdom]]
*[[US History]]
*[[Israeli History]]
*[[Japanese History]]
*[[Korean History]]
*[[Iranian History]]
*[[History of the Soviet Union]]
*[[The Holocaust]]
*[[COSTP World History Project]]
|}</text>
      <sha1>j8ojhw4ngilw2q9vk67miyxd6nfbhuc</sha1>
    </revision>
  </page>
  <page>
    <title>User:Robbiemuffin/Templates/DT main/doc</title>
    <ns>2</ns>
    <id>158199</id>
    <revision>
      <id>4668998</id>
      <parentid>1186274</parentid>
      <timestamp>2026-09-05T19:12:25Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668998</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4160" sha1="f7aldy8thfabxd3emiy4sd6v93n020s" xml:space="preserve">{{Documentation subpage}}
&lt;!-- PLEASE ADD CATEGORIES AND INTERWIKIS AT THE BOTTOM OF THIS PAGE. --&gt;
&lt;div style=&quot;background-color:#abc;{{text default color}}; padding: 2px; border-top-right-radius: 2em; border-top-left-radius: 2em; -webkit-border-top-left-radius: 2em; -webkit-border-top-right-radius: 2em; -moz-border-radius-topleft: 2em; -moz-border-radius-topright: 2em;&quot;&gt;

&lt;div style=&quot;font-size: 5px; line-height: 5px&quot;&gt;&amp;nbsp;&lt;/div&gt;
&lt;span style=&quot;margin-left: 1.1em; font-size: 1.5em; font-weight: bold; font-variant: small-caps&quot;&gt;&lt;nowiki&gt;{{&lt;/nowiki&gt;&lt;span style=&quot;font-size: 0.8em&quot;&gt;User:Robbiemuffin/Templates/DT main&lt;/span&gt;&lt;nowiki&gt;}}&lt;/nowiki&gt; — Documentation Template&lt;/span&gt;

 &lt;div style=&quot;margin-left: 5%; margin-right: 5%;&quot;&gt;

{|
| __TOC__
|}
&lt;br /&gt;

&lt;!-- Add sections here --&gt;
== Purpose ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;
The purpose of the documentation template is to make creating template or other documentation speedy and efficient.
&lt;/div&gt;

== Specification ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;

&lt;pre&gt;&lt;div style=&quot;
  background-color:#abc; 
  padding: 2px; 
  border-top-right-radius: 2em; border-top-left-radius: 2em; 
  -webkit-border-top-left-radius: 2em; -webkit-border-top-right-radius: 2em; 
  -moz-border-radius-topleft: 2em; -moz-border-radius-topright: 2em;&quot;&gt;

&lt;div style=&quot;font-size: 5px; line-height: 5px&quot;&gt;&amp;nbsp;&lt;/div&gt;
{{{title|}}}

 &lt;div style=&quot;margin-left: 5%; margin-right: 5%;&quot;&gt;

{|
| __TOC__
|}
&lt;br /&gt;

&lt;!-- Add sections here --&gt;
{{{content|}}}

&lt;!-- end document --&gt;
 &lt;/div&gt;

&lt;div style=&quot;font-size:3em&quot;&gt;&amp;nbsp;&lt;/div&gt;
[[Image:Ajax-hacker.full.png|100px|center|]]
&lt;div style=&quot;
  margin-left: auto; margin-right: auto; 
  text-align: center; 
  font-size:0.85em&quot;&gt;
    ''this page was brought to you by an Ajax hacker''
&lt;/div&gt;

&lt;/div&gt;&lt;/pre&gt;

&lt;/div&gt;

== Usage ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;

&lt;p&gt;
&lt;span style=&quot;margin-left: 1.1em; font-size: 1.2em; font-weight: bold;&quot;&gt;
 &lt;nowiki&gt;{{&lt;/nowiki&gt;
 &lt;span style=&quot;font-variant: none&quot;&gt;subst:&lt;/span&gt;&amp;nbsp;
 &lt;span style=&quot;font-size: 0.8em; font-variant: small-caps&quot;&gt;User:Robbiemuffin/Templates/DT main&lt;nowiki&gt; | &lt;/nowiki&gt;title=&lt;/span&gt;&lt;span style=&quot;font-size: 0.8em;&quot;&gt;'''''doc_title'''''&lt;/span&gt;&lt;span style=&quot;font-size: 0.8em; font-variant: small-caps&quot;&gt;&lt;nowiki&gt; | &lt;/nowiki&gt;content=&lt;/span&gt;&lt;span style=&quot;font-size: 0.8em;&quot;&gt;'''''doc_preinsertion_content'''''&lt;/span&gt;&lt;nowiki&gt; }}&lt;/nowiki&gt;
&lt;/span&gt;
&lt;/p&gt;

&lt;div style=&quot;margin-left: 2%;&quot;&gt;
{| style=&quot;padding: 0.25em; background-color: rgba(255, 255, 255, 0.25);{{text default color}};&quot;
|&lt;span style=&quot;font-size: 1.8em; line-height: 2em&quot;&gt;title&lt;/span&gt;
|Title text for the Documentation.
|-
|&lt;span style=&quot;font-size: 1.8em; line-height: 2em&quot;&gt;contents&lt;/span&gt;
|Convenience method, puts contents at the insertion point.
|}
&lt;/div&gt;

&lt;/div&gt;

== Example ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;

Replacing the two sections that default with a new documentation page with:

&lt;pre&gt;{{subst:User:Robbiemuffin/Templates/DT main|title=Some documentation|content=

{{subst:User:Robbiemuffin/Templates/DT section|title=Purpose}}
{{subst:User:Robbiemuffin/Templates/DT section|title=Specification}}
{{subst:User:Robbiemuffin/Templates/DT section|title=Usage}}
{{subst:User:Robbiemuffin/Templates/DT section|title=Example}}
{{subst:User:Robbiemuffin/Templates/DT section|title=See Also}}

}}&lt;/pre&gt;

-- generated this page.  (Save and load the page, then come back and edit the documentation to fill it.)

&lt;/div&gt;

== See Also ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;

[[User:Robbiemuffin/Templates/DT section]]

&lt;/div&gt;


&lt;!-- end document --&gt;
 &lt;/div&gt;

&lt;div style=&quot;font-size:3em&quot;&gt;&amp;nbsp;&lt;/div&gt;
[[Image:Ajax-hacker.full.png|100px|center|]]
&lt;div style=&quot;margin-left: auto; margin-right: auto; text-align: center; font-size:0.85em&quot;&gt;''this page was brought to you by an Ajax hacker''&lt;/div&gt;

&lt;/div&gt;

&lt;includeonly&gt;&lt;!--
++++ PLEASE ADD CATEGORIES AND INTERWIKIS BELOW THIS LINE, THANK YOU. --&gt;
&lt;/includeonly&gt;</text>
      <sha1>f7aldy8thfabxd3emiy4sd6v93n020s</sha1>
    </revision>
  </page>
  <page>
    <title>User:Robbiemuffin/Templates/DT section/doc</title>
    <ns>2</ns>
    <id>158200</id>
    <revision>
      <id>4669014</id>
      <parentid>1186256</parentid>
      <timestamp>2026-09-05T19:30:37Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669014</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4121" sha1="bphxb34081pkhc5m81ezzq8eul7uozl" xml:space="preserve">{{Documentation subpage}}
&lt;!-- PLEASE ADD CATEGORIES AND INTERWIKIS AT THE BOTTOM OF THIS PAGE. --&gt;
&lt;div style=&quot;background-color:#abc;{{Text default color}}; padding: 2px; border-top-right-radius: 2em; border-top-left-radius: 2em; -webkit-border-top-left-radius: 2em; -webkit-border-top-right-radius: 2em; -moz-border-radius-topleft: 2em; -moz-border-radius-topright: 2em;&quot;&gt;

&lt;div style=&quot;font-size: 5px; line-height: 5px&quot;&gt;&amp;nbsp;&lt;/div&gt;
&lt;span style=&quot;margin-left: 1.1em; font-size: 1.5em; font-weight: bold; font-variant: small-caps&quot;&gt;&lt;nowiki&gt;{{&lt;/nowiki&gt;&lt;span style=&quot;font-size: 0.8em&quot;&gt;User:Robbiemuffin/Templates/DT main&lt;/span&gt;&lt;nowiki&gt;}}&lt;/nowiki&gt; — sections for Documentation Template&lt;/span&gt;

 &lt;div style=&quot;margin-left: 5%; margin-right: 5%;&quot;&gt;

{|
| __TOC__
|}
&lt;br /&gt;

&lt;!-- Add sections here --&gt;
== Purpose ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;

Convenience method for adding sections to a DT main-styled documentation page

&lt;/div&gt;

== Specification ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;

&lt;pre&gt;== {{{title|}}} ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;

{{{content|}}}

&lt;/div&gt;&lt;/pre&gt;

&lt;/div&gt;

== Usage ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;

&lt;p&gt;
&lt;span style=&quot;margin-left: 1.1em; font-size: 1.2em; font-weight: bold;&quot;&gt;
 &lt;nowiki&gt;{{&lt;/nowiki&gt;
 &lt;span style=&quot;font-variant: none&quot;&gt;subst:&lt;/span&gt;&amp;nbsp;
 &lt;span style=&quot;font-size: 0.8em; font-variant: small-caps&quot;&gt;User:Robbiemuffin/Templates/DT section&lt;nowiki&gt; | &lt;/nowiki&gt;title=&lt;/span&gt;&lt;span style=&quot;font-size: 0.8em;&quot;&gt;'''''section_title'''''&lt;/span&gt;&lt;span style=&quot;font-size: 0.8em; font-variant: small-caps&quot;&gt;&lt;nowiki&gt; | &lt;/nowiki&gt;content=&lt;/span&gt;&lt;span style=&quot;font-size: 0.8em;&quot;&gt;'''''section_preinsertion_content'''''&lt;/span&gt;&lt;nowiki&gt; }}&lt;/nowiki&gt;
&lt;/span&gt;
&lt;/p&gt;

&lt;div style=&quot;margin-left: 2%;&quot;&gt;
{| style=&quot;padding: 0.25em; background-color: rgba(255, 255, 255, 0.25);{{Text default color}};&quot;
|&lt;span style=&quot;font-size: 1.8em; line-height: 2em&quot;&gt;title&lt;/span&gt;
|Title text for the Section.
|-
|&lt;span style=&quot;font-size: 1.8em; line-height: 2em&quot;&gt;contents&lt;/span&gt;
|Convenience method, puts contents at the insertion point.
|}
&lt;/div&gt;

&lt;/div&gt;

== Example ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;

Replacing the two sections that default with a new documentation page with:

&lt;pre&gt;{{subst:User:Robbiemuffin/Templates/DT main|title=Some documentation|content=

{{subst:User:Robbiemuffin/Templates/DT section|title=Purpose}}
{{subst:User:Robbiemuffin/Templates/DT section|title=Specification}}
{{subst:User:Robbiemuffin/Templates/DT section|title=Usage}}
{{subst:User:Robbiemuffin/Templates/DT section|title=Example}}
{{subst:User:Robbiemuffin/Templates/DT section|title=See Also}}

}}&lt;/pre&gt;

-- generated this page.  (Save and load the page, then come back and edit the documentation to fill it.)

Since this works through substitution, you can use this method at any time to add new sections: If, later on, I want to add a new section after Usage, I could edit the USage section and add this code:
&lt;pre&gt;{{subst:User:Robbiemuffin/Templates/DT section|title=My New Section}}&lt;/pre&gt;

Calling this template without substitutions (and preferably without options) gives a quick short hand to edit the actual template ... '''''which you should never do unless you will revert the changes afterwards.'''''  This is a convenience method so you can tune your sections in a one-time-only fashion.

&lt;/div&gt;

== See Also ==
&lt;div style=&quot;margin-left: 2%; margin-right: 2%; text-align: justify; text-justify: newspaper&quot;&gt;

[[User:Robbiemuffin/Templates/DT main]]

&lt;/div&gt;

&lt;!-- end document --&gt;
 &lt;/div&gt;

&lt;div style=&quot;font-size:3em&quot;&gt;&amp;nbsp;&lt;/div&gt;
[[Image:Ajax-hacker.full.png|100px|center|]]
&lt;div style=&quot;margin-left: auto; margin-right: auto; text-align: center; font-size:0.85em&quot;&gt;''this page was brought to you by an Ajax hacker''&lt;/div&gt;

&lt;/div&gt;


&lt;includeonly&gt;&lt;!--
++++ PLEASE ADD CATEGORIES AND INTERWIKIS BELOW THIS LINE, THANK YOU. --&gt;
&lt;/includeonly&gt;</text>
      <sha1>bphxb34081pkhc5m81ezzq8eul7uozl</sha1>
    </revision>
  </page>
  <page>
    <title>User:PMarmottant/Physics at smaller scales</title>
    <ns>2</ns>
    <id>158236</id>
    <revision>
      <id>4669004</id>
      <parentid>1191516</parentid>
      <timestamp>2026-09-05T19:21:02Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669004</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4176" sha1="lju6wle6d2yl173exytt8gyrgjipmrq" xml:space="preserve">== Microscopic scales found in fluids ==
* Distance between molecules in a liquid:  
&lt;math&gt; d \sim 0.1  \;\mathrm{nm}&lt;/math&gt;
* Distance between molecules in a gas: 
&lt;math&gt; d \sim (1/\rho)^{1/3}\sim(kT/P)^{1/3}\sim 3 \;\mathrm{nm}&lt;/math&gt;
* Free mean path between collisition in a gas, air at ambient pressure:     
&lt;math&gt; \lambda = k T/\sqrt{2}\pi \delta^2 P\simeq 61 \; \mathrm{nm}&lt;/math&gt;, with &lt;math&gt;\pi\delta^2&lt;/math&gt; the effective collision cross-section.

== Size of objects of interest embedded in a liquids, example of biological elements ==
* Protein, lipid molecule of the membrane: 1 nm
* Virus: 10 nm
* Cell: 1-10 μm

== Hierarchy of forces  ==
* Size of the object: &lt;math&gt;l^1&lt;/math&gt;
* Surface: &lt;math&gt;l^2&lt;/math&gt;
* Volume and mass: &lt;math&gt;l^3&lt;/math&gt;
The surface to volume ratio increases when the size decreases.

Importance of forces, as a function of distance &lt;math&gt;d&lt;/math&gt; or object size &lt;math&gt;l&lt;/math&gt;
{| border=&quot;2&quot; cellpadding=&quot;4&quot; cellspacing=&quot;0&quot; style=&quot;margin: 1em 1em 1em 0; background: #f9f9f9;{{text default color}}; border: 1px #aaa solid; border-collapse: collapse;&quot;
|-
|-
| Van des Waals between molecules
| &lt;math&gt;d^{-7}\,&lt;/math&gt;
|-
| Van des Waals between surfaces
| &lt;math&gt;d^{-3}\,&lt;/math&gt;
|-
| Capillary force 
| &lt;math&gt;l^1\,&lt;/math&gt;
|-
| Capillary force 
| &lt;math&gt;l^1\,&lt;/math&gt;
|-
| Muscular force
| &lt;math&gt;l^2\,&lt;/math&gt;
|-
| Gravity force
| &lt;math&gt;l^3\,&lt;/math&gt;
|-
| Magnetic force
| &lt;math&gt;l^3\,&lt;/math&gt;
|-
| Dielectrophoretic force
| &lt;math&gt;l^3\,&lt;/math&gt;
|}
The effects at the beginning of the table become increasingly present when down-sizing.

== Examples in Nature of the hierarchy of forces ==

=== Insects can walk on water ===
[[Image:WaterstriderEnWiki.jpg|thumb|200px|left|The [[w:water strider|Water strider]] uses surface tension to walk]]
[[Image:PatteInsecte.svg|thumb|200px|right|Surface tension acts on the perimeter of legs]]
A contact line occurs on the legs of these insects. The leg surface is hydrophobic, and therefore the surfaced is curved downwards, which creates an upward tension force. 

The typical leg diameter  is l, and we can estimate the intensity of the forces:

* Capillary force scales like &lt;math&gt; \sigma \pi l&lt;/math&gt;, with &lt;math&gt;\sigma&lt;/math&gt; the surface tension, a force per unit length whose value is &lt;math&gt;\sigma=70.10^{-3} \mathrm{N/m}&lt;/math&gt;
* Weight scales like &lt;math&gt; \rho g l^3&lt;/math&gt;

Therefore weight is comparable to the capillary force at the characteristic leghtscale:

:&lt;math&gt;l^*=\sqrt{\frac{\sigma}{\rho g}}\simeq 3 \, \mathrm{mm}&lt;/math&gt;
Below this length capillary forces are preponderant. 

=== Smaller but stronger ===
How many times can you lift people of your size?

The structure of muscles is universal in the animal kingdom, with similar fibers of diameter &lt;math&gt;l_0&lt;/math&gt;. 
Each fiber can exert a maximum force &lt;math&gt;f&lt;/math&gt;. 
The number of fibers is &lt;math&gt;\scriptstyle l^2/l_0^2&lt;/math&gt;
* Muscular force exerted by a muscle therefore scales like 
:&lt;math&gt;F\sim P l^2\,&lt;/math&gt;

with &lt;math&gt;\scriptstyle P=f/l_0^2&lt;/math&gt; the maximum stress exerted by a fiber. It is a &quot;Natural&quot; constant, independent of the size. It can be evaluated for human beings as &lt;math&gt;\scriptstyle P\sim F/l^2=100\; \mathrm{N}/10\;\mathrm{cm}^2\simeq 10^4 \;\mathrm{N}&lt;/math&gt;, where we computed the typical force exerted by a muscle divided by its typical section area.
* The weight scales like 
:&lt;math&gt;W \sim \rho g l^3\,&lt;/math&gt;

The number of people you can lift is therefore 
:&lt;math&gt;N=\frac{F}{W}=\frac{P}{\rho g l}=\frac{H}{l}&lt;/math&gt;

with &lt;math&gt;H\simeq 1 \; \mathrm{m}&lt;/math&gt; a constant independent of size.

Humans (l~1m) can lift 1 people
Small ants (l~1mm) can lift 1000 people!

Note, that this force is used by a particuliar species of ants to jump.  These ants  strike their mandibules on the ground with a force that is 300 times its own weight, and propell themselves up to 10cm in height
&lt;ref&gt; Patek, S. N. and Baio, J. E. and Fisher, B. L. and Suarez, A. V.  (2006)  [http://www.pnas.org/cgi/content/abstract/103/34/12787 Multifunctionality and mechanical origins: Ballistic jaw propulsion in trap-jaw ants], Proceedings of the National Academy of Sciences, vol 103, page 12787 &lt;/ref&gt;.

==References==
{{reflist}}</text>
      <sha1>lju6wle6d2yl173exytt8gyrgjipmrq</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Mafutrct</title>
    <ns>3</ns>
    <id>162342</id>
    <revision>
      <id>4669070</id>
      <parentid>4668021</parentid>
      <timestamp>2026-09-06T06:46:08Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669070</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4250" sha1="t8ip1ii7yl0gdmdfvw8upj00m1kf8rr" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Mafutrct!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything &amp; it is really easy. Come say [[WB:HELP|hello]] to everyone!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can always get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* If something you wrote was tagged with {{tlx|query}}, and you think this was done in error, just remove it &amp; explain why on the talk page.
* If your upload was tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] &amp; source are always required; fair use images require a {{tlx|fair use rationale}}.
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;{{!}}&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 22:03, 25 June 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}</text>
      <sha1>t8ip1ii7yl0gdmdfvw8upj00m1kf8rr</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Kpaul003</title>
    <ns>3</ns>
    <id>168378</id>
    <revision>
      <id>4669074</id>
      <parentid>4668064</parentid>
      <timestamp>2026-09-06T07:13:46Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669074</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8606" sha1="p6mstm714hyeqfo0opgusflijgos2x5" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Kpaul003!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything &amp; it is really easy. Come say [[WB:HELP|hello]] to everyone!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can always get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* If something you wrote was tagged with {{tlx|query}}, and you think this was done in error, just remove it &amp; explain why on the talk page.
* If your upload was tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] &amp; source are always required; fair use images require a {{tlx|fair use rationale}}.&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 03:19, 10 September 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}


==Hi==
Katelyn,

You have some really good points. I agree with you on your teaching philosophy. I also think that students should be active in their own learning. Students should be able to say things that they want to learn about too. Also, who said the teacher was the only one who could activate a learning environment. The students can also encourage learning to their fellow students. Good luck with your future 1st graders. I'm sure you will be a great teacher. You sound very passionate.

Krista    [[User:Kruss018|Kruss018]] ([[User talk:Kruss018|talk]]) 00:54, 15 September 2008 (UTC)


Hi Katelyn,

I really enjoyed reading your educational philosophy, and I believe we share a lot of the same ideas.  I agree that too much pressure is put on standardized testing.  I think teachers are having to rush through content and not have enough time for meaningful discussions with their students.  I also feel that technology is very important to use in the classroom, and I definetly believe students need to take typing class at a much younger age.  I thought that was a great point! Lastly, I agree that students of all abilities should be in one classroom.  It sounds like you have some really great ideas about what you want to incorporate in your curriculum.  

Kelly Shepherd
[[User:Kshep009|Kshep009]] ([[User talk:Kshep009|talk]]) 19:22, 13 September 2008 (UTC)


Hey Katelyn!  Thanks for commenting on my page!  I also enjoyed reading your philosophy, and I agree with what you have written - especially the bit about group work and utilizing technology to the best advantage of the students and teacher.  I also agree with your statement about students being exposed to other students with disabilities.  When I was in middle school, I was taken to St. Mary's in downtown Norfolk (School for the handicapped) and it definitely had a positive impact on my life.  Everyone, not just students, could benefit from stepping outside their world and seeing how people different from them live and persevere.  Best wishes!  [[User:Dbrod001|Dbrod001]] ([[User talk:Dbrod001|talk]]) 22:06, 13 September 2008 (UTC)

[[User:Vlane02|Vlane02]] ([[User talk:Vlane02|talk]]) 00:11, 14 September 2008 (UTC) Katelyn, I agree with your idea about Teacher philosophies, but Standars of Learning testing is essential for the govermment, school boards, and the parents to find about how the students are doing in school, the knowledge they absorbed, and for the govermment to see the students standars. It is a great way to see how our education in the United States is doing.
Students from others countries already come to compete in spelling Bees with the American students. Education is the foundation in any society and country; when we educate our children, we are educating the leaders of tomorrow.

Hello Katelyn:
Like many other teaching philosophies I have read there really appears to be an interest in helping to provide well rounded education to students.  You brought up both technlogy and exposure to sports and the arts.  I know that in my own adolesence the opportunity to play sports and to join a band were key steps in my youth.  Many a happy moment were spent on the soccer field and in band concerts.  I think your interest in very young children like first graders will be an excellent opportunity to teach children to accept challenges and to great opportunites for just that, opportunities.  As you say, it is also important for children to be exposed to other's, especially their own age, who have conditions different then their own.  Learning to cope with and overcome deficits such as physical, speech, mental or even emotional problems is something we all must face sometime in our lives.  As a teacher, you will be in a position to demonstrate a true spirit of acceptance.  One more thing.  I really admire your spirit of nationalism.  The rights our forefathers (and mothers) fought for and framed in the constitution are often taken for granted and insisting on saying the pledge of allegiance each day puts the focus or our civil responsibilities.  By the way, I vote for a moment of prayer as well!  God is our sovereign Lord and we would not even be alive save His providence. God bless you and these United States!    [[User:Efari002|Ed Farinholt (efari002)]] ([[User talk:Efari002|talk]]) 13:55, 28 October 2008 (UTC)</text>
      <sha1>p6mstm714hyeqfo0opgusflijgos2x5</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Hgibb005</title>
    <ns>3</ns>
    <id>168768</id>
    <revision>
      <id>4669073</id>
      <parentid>4668232</parentid>
      <timestamp>2026-09-06T07:13:09Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669073</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5960" sha1="tpoiqtqvhlm4yc0zmxr9f1jmtuoksg5" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Hgibb005!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything &amp; it is really easy. Come say [[WB:HELP|hello]] to everyone!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can always get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* If something you wrote was tagged with {{tlx|query}}, and you think this was done in error, just remove it &amp; explain why on the talk page.
* If your upload was tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] &amp; source are always required; fair use images require a {{tlx|fair use rationale}}.&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 03:26, 10 September 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}


==Teaching philosophy==
I enjoyed seeing your comment about spending time with students and finding out more about them.  That would definitely go far with a student and help us when we are giving them positive feedback to reinforce and keep them on track toward our teaching goals.  Finding time in a limited classroom period to effectively individualize education with each student is going to be a challenge for us.  We often have so many students and so little time with them for individual communication in today's school environment.  [[User:Phura001|Phura001]] ([[User talk:Phura001|talk]]) 18:29, 9 September 2008 (UTC)

The concept of being able to have a one on one time with each student would be idle.
    [[User:Tfrat001|Tfrat001]] ([[User talk:Tfrat001|talk]]) 01:36, 12 September 2008 (UTC)


First I want to say Congratulations on the new marriage! And I am very glad to hear you mother is better now! That is very impressive that you took a few years off of school to take care of her. I agree with your teaching philosophy. It is very important to have an environment where the student feels comfortable. I remember when I had a class where the teacher wasn't very welcoming, I never felt like going to that class and it made me not want to learn the subject. If a student doesn't feel comfortable in a class, they won't ask questions and that means they will most likely get lost or not learn the material. And even though it is very difficult for teachers to get to know each student on an individual basis, I agree that it is very important to have a positive relationship with all students.  
[[User:Cbrow103|Cbrow103]] ([[User talk:Cbrow103|talk]]) 18:19, 13 September 2008 (UTC)</text>
      <sha1>tpoiqtqvhlm4yc0zmxr9f1jmtuoksg5</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Lpaul006</title>
    <ns>3</ns>
    <id>168811</id>
    <revision>
      <id>4669075</id>
      <parentid>4668034</parentid>
      <timestamp>2026-09-06T07:14:24Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>A</comment>
      <origin>4669075</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4256" sha1="kmsuz6quh9nfs8bbtm2s1tciihs36y0" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Lpaul006!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything &amp; it is really easy. Come say [[WB:HELP|hello]] to everyone!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can always get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* If something you wrote was tagged with {{tlx|query}}, and you think this was done in error, just remove it &amp; explain why on the talk page.
* If your upload was tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] &amp; source are always required; fair use images require a {{tlx|fair use rationale}}.
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 02:48, 10 September 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}</text>
      <sha1>kmsuz6quh9nfs8bbtm2s1tciihs36y0</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Bzeig001</title>
    <ns>3</ns>
    <id>168823</id>
    <revision>
      <id>4669068</id>
      <parentid>4668462</parentid>
      <timestamp>2026-09-06T06:44:50Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4669068</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8313" sha1="hp8tqeapnqjjpvcwxf01s0vlv8ilp98" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Bzeig001!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything &amp; it is really easy. Come say [[WB:HELP|hello]] to everyone!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can always get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* If something you wrote was tagged with {{tlx|query}}, and you think this was done in error, just remove it &amp; explain why on the talk page.
* If your upload was tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] &amp; source are always required; fair use images require a {{tlx|fair use rationale}}.&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 02:55, 10 September 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}


Well Bethany, welcome to the area. Hope your enjoying your move so far. And i see that you work for the YMCA; thats pretty cool, i did some comunity service at the mount trashmore location a little while back. I like your personal philosophy, &quot;prepare for the worst and hope for the best&quot;, i'd say its a pretty good motto to have. You never know what this worlds going to throw atcha, best to be prepared! I also think you have a pretty good Educational Philosophy as well. Teaching is one of those things that deffinetly can influence the world. Hopefully you use your influence to arouse positive change and growth in your students! Good luck to you!! Gage[[Special:Contributions/70.161.55.43|70.161.55.43]] ([[User talk:70.161.55.43|talk]]) 15:22, 13 September 2008 (UTC)[[User:Gkapp001|Gkapp001]] ([[User talk:Gkapp001|talk]]) 15:27, 13 September 2008 (UTC)

Hello Bethany. I was interested in your comment on how you prepare for the worst and hope for the best. I remember I used to think that way but have since revised my point of view. Now I hope for the best and realized that when life gives you lemons you simply make lemonade. Life has a lot to offer and I am sure depending on what type of YMCA you work for you see a wide variety of children and families. As teachers we will have many roles to play, Good luck on your journey and do not forget to stop and smell the roses sometime.
[[User:Vguti001|Vguti001]] ([[User talk:Vguti001|talk]]) 22:43, 14 September 2008 (UTC)

Hey Bethany.  I have heard of Ben Lee, but can't say I'm a fan.  Some of my favorite movies are A River Runs Through it, Garden State, Elizabethtown, and Into the Wild; movies that inspire.  I love authentic mexican food, but I love taco bell as well.  Your philosophy sounds like you'll make a good teacher someday. [[User:Pleex010|Pleex010]] ([[User talk:Pleex010|talk]]) 01:07, 15 September 2008 (UTC)

    
== Copyright problems with [[:Image:Sidebar 2.jpg|Image:Sidebar 2.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Sidebar 2.jpg|Image:Sidebar 2.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Sidebar 2.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 03:08, 9 October 2008 (UTC)}}


== Copyright problems with [[:Image:Me And Ma.jpg|Image:Me And Ma.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Me And Ma.jpg|Image:Me And Ma.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Me And Ma.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 03:21, 9 October 2008 (UTC)}}</text>
      <sha1>hp8tqeapnqjjpvcwxf01s0vlv8ilp98</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Cwill122</title>
    <ns>3</ns>
    <id>168824</id>
    <revision>
      <id>4669067</id>
      <parentid>4668661</parentid>
      <timestamp>2026-09-06T06:44:25Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669067</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4549" sha1="ltw382g8y8azzybvxkb4nnykb909wor" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Cwill122!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything &amp; it is really easy. Come say [[WB:HELP|hello]] to everyone!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can always get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* If something you wrote was tagged with {{tlx|query}}, and you think this was done in error, just remove it &amp; explain why on the talk page.
* If your upload was tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] &amp; source are always required; fair use images require a {{tlx|fair use rationale}}.
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 02:55, 10 September 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align=right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}


Hello, you posted your wiki article on a page for which you did not correctly sign up.  This page is already taken, so I have removed your content.  Please contact me so that we can work out a solution.

[[User:PbakerODU|Pete]] ([[User talk:PbakerODU|talk]]) 14:24, 25 September 2008 (UTC)</text>
      <sha1>ltw382g8y8azzybvxkb4nnykb909wor</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Abake023</title>
    <ns>3</ns>
    <id>168846</id>
    <revision>
      <id>4669072</id>
      <parentid>4668254</parentid>
      <timestamp>2026-09-06T07:12:41Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669072</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4468" sha1="kican00kb2y5rpva4tvnquxly8e47le" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Abake023!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything &amp; it is really easy. Come say [[WB:HELP|hello]] to everyone!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can always get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* If something you wrote was tagged with {{tlx|query}}, and you think this was done in error, just remove it &amp; explain why on the talk page.
* If your upload was tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] &amp; source are always required; fair use images require a {{tlx|fair use rationale}}.&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 03:06, 10 September 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}


Hello Amy! I just wanted to say hi since I am the OTHER Amy Baker in the class...ABake028! Who knew I had a name double!! [[User:Abake028|Abake028]] ([[User talk:Abake028|talk]]) 14:45, 12 September 2008 (UTC)</text>
      <sha1>kican00kb2y5rpva4tvnquxly8e47le</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Bookaneer</title>
    <ns>3</ns>
    <id>168879</id>
    <revision>
      <id>4669069</id>
      <parentid>4668461</parentid>
      <timestamp>2026-09-06T06:45:14Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4669069</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4256" sha1="nivq82hxyliw20kflgzwhunywwd2j8l" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Bookaneer!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything &amp; it is really easy. Come say [[WB:HELP|hello]] to everyone!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can always get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* If something you wrote was tagged with {{tlx|query}}, and you think this was done in error, just remove it &amp; explain why on the talk page.
* If your upload was tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] &amp; source are always required; fair use images require a {{tlx|fair use rationale}}.&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{Text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{Text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 03:30, 10 September 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}</text>
      <sha1>nivq82hxyliw20kflgzwhunywwd2j8l</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Kolah001</title>
    <ns>3</ns>
    <id>168880</id>
    <revision>
      <id>4669082</id>
      <parentid>4667949</parentid>
      <timestamp>2026-09-06T07:20:06Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669082</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4256" sha1="bw3n3x56skvh48f50efcqxjezpzswgp" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Kolah001!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything &amp; it is really easy. Come say [[WB:HELP|hello]] to everyone!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can always get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* If something you wrote was tagged with {{tlx|query}}, and you think this was done in error, just remove it &amp; explain why on the talk page.
* If your upload was tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] &amp; source are always required; fair use images require a {{tlx|fair use rationale}}.
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 03:32, 10 September 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}</text>
      <sha1>bw3n3x56skvh48f50efcqxjezpzswgp</sha1>
    </revision>
  </page>
  <page>
    <title>User:PoizonMyst/Australian Esoterica</title>
    <ns>2</ns>
    <id>169132</id>
    <revision>
      <id>4668920</id>
      <parentid>4409489</parentid>
      <timestamp>2026-09-05T12:12:27Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668920</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19533" sha1="eu6kdw5gnnjiac271b3v70kk3lskuhg" xml:space="preserve">'''&lt;small&gt;[[Australian Esoterica]] • [[Talk:Australian_Esoterica|Discussion]] • [[Australian Esoterica/MOS|Manual of Style]] • [[User:PoizonMyst/Australian Esoterica Research|Resource Sandbox]]&lt;/small&gt;'''&lt;br /&gt;
This is my personal sandbox for the ''Australian Esoterica'' wikibook.

==Table of Contents==
*[[Australian Esoterica|Introduction]]
*[[Australian Esoterica/TOC|Table of Contents]]
*[[Australian Esoterica/What is Neopaganism?|What is Neopaganism?]]
*[[Australian Esoterica/World Nature Traditions|Nature Traditions of the World]]
*[[Australian Esoterica/Neopaganism in Australia|Neopaganism in Australia]]
*[[Australian Esoterica/Observances and Symmetries|Observances and Symmetries]]
**[[Australian Esoterica/Seasonal Festivals|Seasonal Festivals]]
**[[Australian Esoterica/Lunar Observances|Lunar Observances]]
**[[Australian Esoterica/Elements|Elements]]
**[[Australian Esoterica/Correspondence Tables|Correspondence Tables]]
*[[Australian Esoterica/Botánica|Botánica]]
**[[Australian Esoterica/Australian Herbs|Herbs]]
**[[Australian Esoterica/Australian Essential Oils|Essential Oils]]
**[[Australian Esoterica/Australian Carrier Oils|Carrier Oils]]
*[[Australian Esoterica/Divination|Divination]]
**[[Australian Esoterica/Astrology|Astrology]]
**[[Australian Esoterica/Numerology|Numerology]]
*[[Australian Esoterica/Glossary|Glossary of Terms]]
*[[Australian Esoterica/Bibliography|Bibliography and Further Resources]]
*[[Australian Esoterica/Authors|Contributing Authors]]
*[[Australian Esoterica/MOS|Australian Esoterica Manual of Style]]
*[[Australian Esoterica/Print Version|Print Version]] &lt;small&gt;''([[Australian Esoterica/Print Version|edit it]])''&lt;/small&gt;

===Aboriginal Australian Culture===
These should be demonstrated by incorporation throughout the book chappters/pages.
*[[Australian Esoterica/Aboriginal Australian Culture|Aboriginal Australian Culture]]
**[[Australian Esoterica/Aboriginal Australian Mythology and Symbology|Mythology and Symbology]]
**[[Australian Esoterica/Aboriginal Australian Spirit Guides|Spirit Guides]]
**[[Australian Esoterica/Aboriginal Australian Ceremonies|Ceremonies]]
**[[Australian Esoterica/Bush Tucker|Bush Tucker]]
**[[Australian Esoterica/Bush Medicine|Bush Medicine]]
**[[Australian Esoterica/Bush Craft|Bush Craft]]

===Equipment and Arts need to be changed around and sections better clarified===
*[[Australian Esoterica/Sacred Space|Sacred Space]]
*[[Australian Esoterica/Equipment|Equipment]]
**[[Australian Esoterica/Mystical Books|Mystical Books]]
**[[Australian Esoterica/Lapidary|Lapidary]]
**[[Australian Esoterica/Australian Symbology|Symbology]]

&lt;br&gt;{{toplink}}

==Introduction==
:&lt;small&gt;''Main article: [[Australian Esoterica|Introduction]]''&lt;/small&gt;
{{drop|F}}or Australian followers of Neopagan philosophies and customs, the traditional seasonal festivals, rituals, and practises taught by the European based disciplines, make it difficult for Australian witches to correctly synchronise with mother nature in the Southern Hemisphere. The '''Australian Esoterica''' aims to realign the traditional Northern Hemisphere Neopagan seasonal customs in accordance with Southern Hemisphere seasonal changes, while at the same time offering a comprehensive guide to Neopagan philosophies for Australian followers of the faith. Nevertheless, this book is not just a rehash of European spiritual practises turned upside down, but also aspires to become an internet [[Australian Esoterica/Mystical Books|Book of Shadows]] for all [[Australian Esoterica/Neopaganism in Australia|Australian Neopagans]] by describing culturally relevant mythologies, philosophies, and practises.
 
&lt;br&gt;{{toplink}}

==What is Neopaganism?==
:&lt;small&gt;''Main article: [[Australian Esoterica/What is Neopaganism?|What is Neopaganism?]]''&lt;/small&gt;
{{drop|A}}derivative of ''neo-'' (from the Ancient Greek prefix ''νεο-'', meaning &quot;new&quot;) and ''pagan'' (from the Latin ''pāgānus'', meaning &quot;country dweller, rustic&quot;), '''Neopaganism''' is a broad term used to describe several modern spiritual movements that are influenced by ancient philosophies and cultures, in particular traditional nature-based customs and polytheistic or pantheistic beliefs of pre-Christian Europe. Neopaganism is distinguished as the modern revival or reconstruction of classical Paganism, although both terms are often used interchangeably.

While early Christian missionaries first focused their efforts on establishing the Christian Church in major urban centres of the Roman Empire, people of the outlying rural regions continued to revere the cycles of nature and their associated spiritual deities.  As such, &quot;country dweller&quot;, or &quot;pagan&quot;, soon pertained to someone who was simply &quot;not a Christian.&quot; Ultimately, Christian political propaganda presented &quot;paganism&quot; as a derogatory expression pertaining to sinful hedonistic practises (from the Ancient Greek ''hēdonē'', meaning &quot;pleasure&quot;). Similarly, the Old Norse and Germanic Pagans, known as ''heathens'' (Old English translation of the Old High German ''heide'', meaning &quot;heath, heathland&quot;), became yet another term eventually distorted to be regarded as unfavourable. 

Today Neopagans worldwide are proudly reclaiming the original definitions of &quot;Pagan&quot; and &quot;Heathen&quot; to identify their nature-based spiritual practises and beliefs.


*References for this page are located in the [[Australian_Esoterica/Bibliography#What_is_Neopaganism?|''Bibliography and Further Resources'']].
&lt;br&gt;{{toplink}}

==Nature Traditions of the World==
:&lt;small&gt;''Main article: [[Australian Esoterica/World Nature Traditions|Nature Traditions of the World]]''&lt;/small&gt;


*References for this page are located in the [[Australian_Esoterica/Bibliography#Nature_Traditions_of_the_World|''Bibliography and Further Resources'']].
&lt;br&gt;{{toplink}}

==Neopaganism in Australia==
:&lt;small&gt;''Main article: [[Australian Esoterica/Neopaganism in Australia|Neopaganism in Australia]]''&lt;/small&gt;
{{drop|S}}o how can a philosophical belief system originating in the Northern Hemisphere be relevant to a multicultural nation situated south of the equator?

In answering this, the Australian Esoterica is not prepared to classify a cultural identity for Australian followers of Neopagan philosophies however there are a number of factors that southern followers of the craft may wish to contemplate.

Modern Neopagan spiritual movements of the Northern Hemisphere describe themselves as influenced by ancient nature-based cultures and their philosophies.  Seasonal festivals throughout the year commemorate these occasions.  Certainly the dates of such observances can be adjusted in accordance with the southern seasons, yet Australian Neopagans may find it difficult to culturally relate to the relevant historical stories. 
But does that really matter?  We are all of the same biological genus and reside on the same home planet.  Ultimately, such narratives belong to all of us - they are the chronicles of human spirituality.  Neopaganism is as much about what feels right for the individual as it is about traditional folklore and customs.  With all this is mind Australian Neopagans might consider:

*The traditional cultural practises and myths of Aboriginal Australians.
*Other traditional cultures of the Southern Hemisphere such as the [[w:en:Austronesian peoples|Austronesian peoples]] of Oceania and Southeast Asia.
*The [[w:en:Anglo-Celtic Australian|Anglo-Celtic]] colonial history of Australia.
*The traditional nature-based practises of [[w:en:Eastern religion|Asiatic]] and [[w:en:Abrahamic religions|Abrahamic]] philosophies and customs who have prominent populations within Australia (such as ''[[w:en:Feng Shui|Feng Shui]]'' of China, the Islamic ''[[Koranic Law of Nature]]'', or ''[[Ayurveda]]'' of India).
*Personal ancestry/geneology.
*The natural landscape and local history of an Australian region with which they closely identify (such as their place of birth or residence).
*The legality of Neopagan practises in Australia.
*Their personal views on the cultural identity that is an [[w:en:Australian|Australian]] [[w:en:Neopagan|Neopagan]].


*References for this page are located in the [[Australian_Esoterica/Bibliography#Neopaganism_in_Australia|''Bibliography and Further Resources'']].
&lt;br&gt;{{toplink}}

==Seasonal Festivals==
:&lt;small&gt;''Main article: [[Australian Esoterica/Seasonal Festivals|Seasonal Festivals]]''&lt;/small&gt;

{{drop|A}}s seasons in the Southern Hemisphere are reversed to those of the North, so too is the Neopagan festival calendar known as the Wheel of the Year. In Australia and New Zealand the long familiar &quot;Christmas in July&quot;, though not an official holiday, is a popular celebration and compelling evidence of efforts to suitably inverse the Pagan festival of &quot;Yule&quot; for the Southern regions.

===Sabbat Festivals===
Neopagans and Wiccans observe eight festivals each year, known as '''Sabbats''', which commemorate the annual cycle of seasons or phases of the sun and moon. This cycle is referred to as the ''Wheel of the Year'', with festivities spaced at approximately even intervals throughout the calendar. Traditionally the festivals mark the solstices and equinoxes, and the times for planting and harvest of crops.

The Wheel of the Year is a modern development of Wicca and Neopaganism originating from traditional holidays observed by Pagan cultures of ancient Europe. No pre-Christian European cultures celebrated all eight Sabbats of the calendar, so the Wheel of the Year comprises a modern merging of traditional festivals from all over ancient Europe, with similarities to the ancient rituals often ending at their shared names alone.

Modern interpretations of ancient practices vary widely, as such different groups may conceptualize and celebrate the Sabbats in very different ways, but the themes and meanings are generally similar. For some, the Wheel of the Year not only describes the continuous cycles of nature and time, but also the human progression through birth, life, decline and death. For many Wiccans, it represents the cycle of life, death, and rebirth of the Horned God and fertility of the Goddess.

Inspired by Gaelic fire festivals, the ''Cross-Quater Days'' (or ''Greater Sabbats'') mark the beginning of each [[w:en:Season#Traditional_season_divisions|traditional season]] (as opposed to [[w:en:Season#Astronomical|astronomical seasons]]) and fall approximately half-way between a solstice and an equinox. Generally, and mostly for convenience, the Greater Sabbats are celebrated on the first day of the season.

In British and Irish traditions of the Middle Ages, ''Quarter Days'' (or ''Lesser Sabbats'') fell close to the two solstice and two equinox holidays. These were dates on which servants were hired, rents or rates were due, and magistrates would determine debts and resolve conflicts in outlying rural regions. In England today, leasehold payments and rents for business premises are often still due on the old English Quarter Days.  The timing of these Lesser Sabbats are determined by the relationship of the Sun to the Earth so their dates deviate slightly each year.

The Celtics recognised that a new day began in the darkness, so too the start of a new year. Thus Samhain, the Celtic Feast of the Dead and beginning of Winter, is generally recognised as the first Sabbat of the year.

===Southern Hemisphere Wheel of the Year===
Below, are the eight festivals and their dates, conveniently inversed for Southern Hemisphere practitioners of the craft.

&lt;br&gt;
{| style=&quot;width:100%&quot; class=&quot;wikitable&quot; 
|-

  ! style=&quot;width:20%; font-weight:bold; text-align:center;&quot;|Season
  ! style=&quot;width:40%; font-weight:bold; text-align:center;&quot;|Greater Sabbat
  ! style=&quot;width:40%; font-weight:bold; text-align:center;&quot;|Lesser Sabbat

|-

  | style=&quot;text-align:center; background-color:#F8F8FF;color:white;&quot;|&lt;big&gt;Winter&lt;/big&gt;
Start: 1st June&lt;br /&gt;
(SH Astronomical)

  | style=&quot;vertical-align:top; background-color:#F8F8FF;color:white;&quot;|'''Samhain'''
*'''1st May''' (alt. 4-10 May)
*First day of ancient Winter.
*Greater Sabbat.  Lunar Festival. 
*A Cross Quarter celebration.
*''Also known as Halloween.''
*Northern Hemisphere: 31 Oct/1 Nov

  | style=&quot;vertical-align:top; background-color:#F8F8FF;color:white;&quot;|'''Yule'''
*'''21st or 22nd June'''
*June Solstice - Winter solstice. Shortest day of the year.
*Lesser Sabbat. Solar Festival.
*A Quarter Day celebration.
*''Also known as Yuletide.''
*Northern Hemisphere: 21/22 Dec

|-

  | style=&quot; text-align:center; background-color:#E7FEFF;color:white;&quot;|&lt;big&gt;Spring&lt;/big&gt;
1st September&lt;br /&gt;
(SH Astronomical)

  | style=&quot;vertical-align:top; background-color:#E7FEFF;color:white;&quot;|'''Imbolc'''
*'''1st August''' (alt. 3-10 August)
*First day of ancient Spring.
*Greater Sabbat. Lunar Festival.
*A Cross Quarter celebration.
*''Also known as Imbolg or Candlemas.''
*Northern Hemisphere: 1 Feb

  | style=&quot;vertical-align:top; background-color:#E7FEFF;color:white;&quot;|'''Ostara'''
*'''22nd or 23rd September'''
*September Equinox - Spring (Vernal) Equinox. Equal day and night.
*Lesser Sabbat. Solar Festival.
*A Quarter Day celebration.
*''Also known as Easter.''
*Northern Hemisphere: 21/22 Mar

|-

  | style=&quot;text-align:center;background-color:#FFFFED;color:white;&quot;|&lt;big&gt;Summer&lt;/big&gt;
1st December&lt;br /&gt;
(SH Astronomical)

  | style=&quot;vertical-align:top; background-color:#FFFFED;color:white;&quot;|'''Beltane'''
*'''1st November''' (alt. 5-10 Nov)
*First day of ancient Summer.
*Greater Sabbat. Lunar Festival.
*A Cross Quarter celebration.
*''Also known as Beltaine or May Day.''
*Northern Hemisphere: 1 May

  | style=&quot;vertical-align:top; background-color:#FFFFED;color:white;&quot;|'''Litha'''
*'''21st or 22nd December'''
*December Solstice - Summer solstice. Longest day of the year.
*Lesser Sabbat. Solar Festival.
*A Quarter Day celebration.
*''Also known as Midsummer.''
*Northern Hemisphere: 21/22 June

|-

  | style=&quot; text-align:center;background-color:#FAF0BE;color:white;&quot;|&lt;big&gt;Autumn&lt;/big&gt;
1st March&lt;br /&gt;
(SH Astronomical)

  | style=&quot;vertical-align:top; background-color:#FAF0BE;color:white;&quot;|'''Lughnasadh'''
*'''1st February''' (alt. 2-7 Feb)
*First day of ancient Autumn.
*Greater Sabbat. Lunar Festival.
*A Cross Quarter celebration.
*''Also known as Lammas.''
*Northern Hemisphere: 1 Aug

  | style=&quot;vertical-align:top; background-color:#FAF0BE;color:white;&quot;|'''Mabon'''
*'''21st or 22nd March'''
*March Equinox - Autumn Equinox. Equal day and night.
*Lesser Sabbat. Solar Festival.
*A Quarter Day celebration.
*''Also known as the Autumnal Equinox.''
*Northern Hemisphere: 22/23 Sep

|}

===Weather Observances of Australian Aboriginals===
Resource: http://en.wikipedia.org/wiki/Indigenous_Australian_seasons
#
{|style=&quot;border:1px solid gray;&quot;

| style=&quot;width:100% &quot;|And more ... ''copied from:'' http://en.wikipedia.org/wiki/Season#Australia
In Australia, the traditional Aboriginal people defined the seasons by what was happening to the plants, animals and weather around them. This led to each separate tribal group having different seasons, some with up to eight seasons each year. However, most modern Aboriginal Australians follow either four or six meteorological seasons, as do non-Aboriginal Australians.
The commonly followed dates are as follows: 1st day of March, June, September and December for the start of Autumn, Winter, Spring and Summer, respectively.

|}
#

===Seasonal Observances around the world===
Interestingly, the Sabbats fall closely to, or on the same dates, as eight points of the [[w:en:Solar_term|24 Solar Terms]] in traditional lunisolar calendars that were developed independently in East Asia. 


*References for this page are located in the [[Australian_Esoterica/Bibliography#Seasonal_Festivals|''Bibliography and Further Resources'']].
&lt;br&gt;{{toplink}}

==Lunar Observances==
:&lt;small&gt;''Main article: [[Australian Esoterica/Lunar Observances|Lunar Observances]]''&lt;/small&gt;


*References for this page are located in the [[Australian_Esoterica/Bibliography#Lunar_Observances|''Bibliography and Further Resources'']].
&lt;br&gt;{{toplink}}

==Glossary of Terms==
:&lt;small&gt;''Main article: [[Australian Esoterica/Glossary|Glossary of Terms]]''&lt;/small&gt;

'''Neopaganism:''' Describes several modern spiritual movements that are influenced by ancient philosophies and cultures, in particular traditional nature-based customs and polytheistic or pantheistic beliefs of pre-Christian Europe. Neopaganism is distinguished as the modern revival or reconstruction of classical Paganism.

'''Paganism:''' The traditional nature-based philosophies and polytheistic or pantheistic religions of classical pre-Christian Europe.

'''Pantheisim:''' The belief that God and the universe are one and the same.

'''Polytheistic:''' A belief in the existence of more than one god.

&lt;br&gt;{{toplink}}

==Bibliography and Further Resources==
:&lt;small&gt;''Main article: [[Australian Esoterica/Bibliography|Bibliography and Further Resources]]''&lt;/small&gt;
===What is Neopaganism?===
* [[wikt:neo-|Wiktionary: Neo-]]
* [[wikt:paganus|Wiktionary: Paganus]]
* [http://www.websters-online-dictionary.org/definition/pagan Webster's Online Dictionary: Pagan]
* [http://www.neopagan.net/PaganDefs.html neopagan.net: Defining Paganism]
* [[w:en:Neopaganism|Wikipedia: Neopaganism]]
* [[w:en:Paganism|Wikipedia: Paganism]]
* [[wikt:hedonism|Wiktionary: Hedonism]]
* [[wikt:Heide|Wiktionary: Heide]]
* [[wikt:polytheism|Wiktionary: Polytheism]]

===Neopaganism in Australia===
* [http://www.abc.net.au/religion/stories/s796571.htm Paganism - Australian Broadcasting Corporation Religion and Ethics Library]
* [http://resources.education.tas.gov.au/item/edres/87e0c394-5ef6-7cc8-376d-4d8d294f5cf3/1/ReligionAustralia.zip/index_religionsaus.htm Religious Identity of Australia - 2001 Census Results] ''(Tasmanian Government Educational Resource)''
* [http://www.paganawareness.net.au/laws.html Australian Witchcraft Laws - Pagan Awareness Network]
* [http://www.abc.net.au/queensland/stories/s1097056.htm Ritual, magic and witchcraft in old Queensland houses]
* [http://www.geocities.com/athens/2962/media/sunmail4_5_97.html Australian Media on Paganism]
* [http://www.austlii.edu.au/au/legis/sa/consol_act/soa1953189/s40.html Summary Offences Act Section 40 - Austlii SA]
* ''&quot;Lost Worlds: The Rise of Man&quot;'' documentary broadcast March 2009 on [[w:en:Special_Broadcasting_Service|SBS]]
* [[w:en:Aboriginal_stone_arrangement|Wikipedia: Aboriginal stone arrangement]]

===Observances and Symmetries===
====Seasonal Festivals====
* [[w:en:Archaeoastronomy|Wikipedia: Archaeoastronomy]]
* [[w:en:Wheel of the Year|Wikipedia: Wheel of the Year]]
* [[w:en:Sabbath|Wikipedia: Sabbath]]
* [[w:en:Cross-quarter_day|Wikipedia: Cross-quarter day]]
* [[w:en:Quarter_days|Wikipedia: Quarter days]]
* [[w:en:Solar_term|Wikipedia: Solar Term]]
* [[w:en:Season|Wikipedia: Season]]
* [[w:en:Lunisolar_calendar|Wikipedia: Lunisolar Calendar]]
* [http://paganwiccan.about.com/od/holidaysandcelebrations/u/Celebrations.htm Sabbats and Other Rituals - about.com]
* [http://atheism.about.com/library/FAQs/religion/blrel_hol_equinox.htm Equinoxes, Solstices, and Calendars - about.com]
* [http://www.unitedpaganchurch.org.au/sabbats.php Sabbats - United Pagan Church of Australia]
* [http://www.shadowsofoz.net/calendar/wheel_of_the_year.html Southern Hemisphere Wheel of the Year - Shadows of Oz]
* [http://www.magickaschool.com/forum/viewtopic.php?t=5018 The Wheel of the Year - Southern Hemisphere - Magic School Forum]


&lt;br&gt;{{toplink}}
&lt;br&gt;{{Userpage}}</text>
      <sha1>eu6kdw5gnnjiac271b3v70kk3lskuhg</sha1>
    </revision>
  </page>
  <page>
    <title>User:PoizonMyst/Template:MystBox</title>
    <ns>2</ns>
    <id>169531</id>
    <revision>
      <id>4668999</id>
      <parentid>1278776</parentid>
      <timestamp>2026-09-05T19:14:56Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668999</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="827" sha1="j4ycrqh6el4ifjyd5ixdlhgcz97r3b7" xml:space="preserve">&lt;table style=&quot;background: {{{background|#DFE8FF}}}; color: {{{color|#000000}}}; border: {{{border|1px solid #1e90ff}}}; text-align: center; width:{{{width|80%}}}; margin:{{{margin|4px 10%}}};&quot; align=&quot;{{{align|center}}}&quot;&gt;&lt;tr&gt;&lt;td width=&quot;{{{imagewidth|50px}}};&quot;&gt; {{{1}}} &lt;/td&gt;&lt;td&gt;{{{2}}}&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;noinclude&gt;[[User:PoizonMyst/Templates]]&lt;/noinclude&gt;


{|border=&quot;0&quot; style=&quot;width:80%; text-align:center; background-color: #DFE8FF;{{text default color}}; border:1px solid #1e90ff;&quot;
|-
|style=&quot;width:30%&quot;|'''«'''
|style=&quot;text-align:center&quot; rowspan=&quot;2&quot;|&lt;big&gt;'''''Australian Esoterica'''''&lt;/big&gt;&lt;br&gt;''{{{CurrentPage}}}''
|style=&quot;width:30%; text-align:right&quot; | '''»'''
|-
|{{{PrevPage}}}&lt;br&gt;&lt;small&gt;&lt; [[/TOC|Table of Contents]]&lt;/small&gt;
|style=&quot;text-align:right&quot; | {{{NextPage}}}&lt;br&gt;&lt;small&gt;[[/Glossary|Glossary]] &gt;&lt;/small&gt;
|-
|}</text>
      <sha1>j4ycrqh6el4ifjyd5ixdlhgcz97r3b7</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:15lanea~enwikibooks</title>
    <ns>3</ns>
    <id>173443</id>
    <revision>
      <id>4669076</id>
      <parentid>4667958</parentid>
      <timestamp>2026-09-06T07:15:32Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669076</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6554" sha1="irnhelddvpu6f5184xfxj78ke7xhzkk" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, 15lanea!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything, and changes can be made easily. Come [[WB:HELP|introduce yourself]] to everyone, and let us know what interests you.
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* We tag pages with various [[WB:TM|message templates]], such as {{tlx|query}}, to let editors know what needs to be improved. To learn more about these, ask at [[WB:PROJECTS|the projects reading room]].
* You cannot upload an image until you have been a member for at least '''4 days'''. If your upload is tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] and source citation are always required; fair use images require a {{tlx|fair use rationale}}. Get help in the [[WB:HELP|user assistance room]].
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 01:49, 15 October 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}

== Your account will be renamed ==

&lt;div class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See [[m:Special:MyLanguage/Single User Login finalisation announcement|the announcement]] for more information.

Unfortunately, your account clashes with another account also called 15lanea. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name 15lanea~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can [[Special:GlobalRenameRequest|pick out a different name]].

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours,&lt;br /&gt;[[m:User:Keegan (WMF)|Keegan Peterzell]]&lt;br /&gt;Community Liaison, Wikimedia Foundation
&lt;/div&gt; 22:54, 17 March 2015 (UTC)
&lt;!-- SUL finalisation notification --&gt;

== Renamed ==

&lt;div class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;
This account has been renamed as part of [[m:Special:MyLanguage/Single User Login finalisation announcement|single-user login finalisation]]. If you own this account you can [[{{#special:userlogin}}|log in using your previous username and password]] for more information. If you do not like this account's new name, you can choose your own using this form after logging in: [[{{#special:GlobalRenameRequest}}]]. -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User talk:Keegan (WMF)|talk]])
&lt;/div&gt; 04:27, 19 April 2015 (UTC)
&lt;!-- SUL post-rename notification --&gt;</text>
      <sha1>irnhelddvpu6f5184xfxj78ke7xhzkk</sha1>
    </revision>
    <revision>
      <id>4669077</id>
      <parentid>4669076</parentid>
      <timestamp>2026-09-06T07:15:56Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669077</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6577" sha1="a5xo0hvghvfffc5xmr94jgq6xwmt81u" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, 15lanea!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything, and changes can be made easily. Come [[WB:HELP|introduce yourself]] to everyone, and let us know what interests you.
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* We tag pages with various [[WB:TM|message templates]], such as {{tlx|query}}, to let editors know what needs to be improved. To learn more about these, ask at [[WB:PROJECTS|the projects reading room]].
* You cannot upload an image until you have been a member for at least '''4 days'''. If your upload is tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] and source citation are always required; fair use images require a {{tlx|fair use rationale}}. Get help in the [[WB:HELP|user assistance room]].
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 01:49, 15 October 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}

== Your account will be renamed ==

&lt;div class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See [[m:Special:MyLanguage/Single User Login finalisation announcement|the announcement]] for more information.

Unfortunately, your account clashes with another account also called 15lanea. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name 15lanea~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can [[Special:GlobalRenameRequest|pick out a different name]].

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours,&lt;br /&gt;[[m:User:Keegan (WMF)|Keegan Peterzell]]&lt;br /&gt;Community Liaison, Wikimedia Foundation
&lt;/div&gt; 22:54, 17 March 2015 (UTC)
&lt;!-- SUL finalisation notification --&gt;

== Renamed ==

&lt;div class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;
This account has been renamed as part of [[m:Special:MyLanguage/Single User Login finalisation announcement|single-user login finalisation]]. If you own this account you can [[{{#special:userlogin}}|log in using your previous username and password]] for more information. If you do not like this account's new name, you can choose your own using this form after logging in: [[{{#special:GlobalRenameRequest}}]]. -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User talk:Keegan (WMF)|talk]])
&lt;/div&gt; 04:27, 19 April 2015 (UTC)
&lt;!-- SUL post-rename notification --&gt;</text>
      <sha1>a5xo0hvghvfffc5xmr94jgq6xwmt81u</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Poseurtech</title>
    <ns>3</ns>
    <id>175127</id>
    <revision>
      <id>4669083</id>
      <parentid>4667819</parentid>
      <timestamp>2026-09-06T07:21:18Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669083</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4917" sha1="7bpfk4xe5toyzpfjjcmclfqzit5yo5c" xml:space="preserve">
&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Poseurtech!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything, and changes can be made easily. Come [[WB:HELP|introduce yourself]] to everyone, and let us know what interests you.
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* We tag pages with various [[WB:TM|message templates]], such as {{tlx|query}}, to let editors know what needs to be improved. To learn more about these, ask at [[WB:PROJECTS|the projects reading room]].
* You cannot upload an image until you have been a member for at least '''4 days'''. If your upload is tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] and source citation are always required; fair use images require a {{tlx|fair use rationale}}. Get help in the [[WB:HELP|user assistance room]].
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 04:00, 7 November 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text=align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}
:Please note that Wikibooks is not for promotion, and neither are our other wikis. You're welcome to contribute constructively, however linking in the manner you have done cross-wiki is unwelcome. &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 04:00, 7 November 2008 (UTC)</text>
      <sha1>7bpfk4xe5toyzpfjjcmclfqzit5yo5c</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Kk.gnogi</title>
    <ns>3</ns>
    <id>175250</id>
    <revision>
      <id>4669079</id>
      <parentid>4667952</parentid>
      <timestamp>2026-09-06T07:17:57Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669079</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5278" sha1="lgo2kqf9sviq7b1hy46ofiryegc8yoo" xml:space="preserve">
&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Kk.gnogi!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything, and changes can be made easily. Come [[WB:HELP|introduce yourself]] to everyone, and let us know what interests you.
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* We tag pages with various [[WB:TM|message templates]], such as {{tlx|query}}, to let editors know what needs to be improved. To learn more about these, ask at [[WB:PROJECTS|the projects reading room]].
* You cannot upload an image until you have been a member for at least '''4 days'''. If your upload is tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] and source citation are always required; fair use images require a {{tlx|fair use rationale}}. Get help in the [[WB:HELP|user assistance room]].
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 23:00, 8 November 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}
==[[:Orca manual]]==
{{mbox|type=notice|msg=
[[:Orca manual|This page]] appears to have been created in error (due to a test, or some kind of [[Help:Editing|misplaced edit]]). It might be a [[Help:Stub|stub]], if so, please use [[Talk:Orca manual|the discussion page]] as to explain what this page is about. If it evolves into a [[WB:WIW|legitimate Wikibooks module]], you may remove the tag. If not fixed, explained, or improved, it will automatically be considered a candidate for [[Wikibooks:Deletion policy#Speedy deletions|speedy deletion]] in 7 days. &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 22:59, 8 November 2008 (UTC)
}}</text>
      <sha1>lgo2kqf9sviq7b1hy46ofiryegc8yoo</sha1>
    </revision>
    <revision>
      <id>4669080</id>
      <parentid>4669079</parentid>
      <timestamp>2026-09-06T07:18:09Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>/* Orca manual */</comment>
      <origin>4669080</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5279" sha1="62vg6amrocuvow55gf4u46ecmbccnck" xml:space="preserve">
&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Kk.gnogi!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything, and changes can be made easily. Come [[WB:HELP|introduce yourself]] to everyone, and let us know what interests you.
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* We tag pages with various [[WB:TM|message templates]], such as {{tlx|query}}, to let editors know what needs to be improved. To learn more about these, ask at [[WB:PROJECTS|the projects reading room]].
* You cannot upload an image until you have been a member for at least '''4 days'''. If your upload is tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] and source citation are always required; fair use images require a {{tlx|fair use rationale}}. Get help in the [[WB:HELP|user assistance room]].
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 23:00, 8 November 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}
==[[:Orca manual]]==
{{mbox|type=notice|text=
[[:Orca manual|This page]] appears to have been created in error (due to a test, or some kind of [[Help:Editing|misplaced edit]]). It might be a [[Help:Stub|stub]], if so, please use [[Talk:Orca manual|the discussion page]] as to explain what this page is about. If it evolves into a [[WB:WIW|legitimate Wikibooks module]], you may remove the tag. If not fixed, explained, or improved, it will automatically be considered a candidate for [[Wikibooks:Deletion policy#Speedy deletions|speedy deletion]] in 7 days. &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 22:59, 8 November 2008 (UTC)
}}</text>
      <sha1>62vg6amrocuvow55gf4u46ecmbccnck</sha1>
    </revision>
  </page>
  <page>
    <title>User:Retropunk/Japanese Curriculum/Outline</title>
    <ns>2</ns>
    <id>176097</id>
    <revision>
      <id>4668926</id>
      <parentid>1354364</parentid>
      <timestamp>2026-09-05T12:30:35Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668926</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3288" sha1="8kjyuj4956qv2xrtgnnv5qy8sd53upy" xml:space="preserve">__NOTOC__

&lt;table style=&quot;width: 100%;&quot;&gt;
&lt;tr&gt;
&lt;td style=&quot;border: 3px solid #BB3E0C; background-color: #FAF4E6;{{Text default color}}; margin: .2em; padding: .5em&quot; colspan=&quot;2&quot;&gt;

{{wikiversity|Japanese}}
* [[/Introduction/About|Introduction]] &amp;mdash; About this wikibook
* [[/Introduction/|The Japanese language]]
* [[/Study methods/]]
* [[/Using_This_Book | How to use this book ]]
== Lesson plans ==
* [[/Beginner Lessons/]]
* [[/Lower Intermediate Lessons/]]
* [[/Upper Intermediate Lessons/]]
* [[/Advanced Lessons/]]
* [[/Near Native Lessons/]]
* [[User:Retropunk/Japanese Curriculum]]&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;border: 1px solid #8B2500; background-color: #FAF4E6;{{Text default color}}; margin: .2em; padding: .5em; width: 50%; vertical-align: top&quot;&gt;

== Reading and writing ==
[[Image:KanjiPractice.jpg|right|180px]]
* [[/Kana Chart/]]
* [[/Japanese writing system|Japanese scripts]]
** [[/Kana/]]
** [[/Kanji/]]
* [[/Reader|Reading practice]]
* [[/Writing Styles/ | Writing Styles]]
&lt;/td&gt;
&lt;td style=&quot;border: 1px solid #8B2500; background-color: #FAF4E6;{{Text default color}}; margin: .2em; padding: .5em; width: 50%; vertical-align: top&quot;&gt;

== Linguistics ==
[[Image:Ja_da_ya.png|right|160px]]
* [[/Pronunciation/]]
* [[/Pitch accent/]]
* [[/Dialects/]]
* [[/Other Linguistics/ | Slang and other variations]]
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;border: 1px solid #8B2500; background-color: #FAF4E6;{{Text default color}}; margin: .2em; padding: .5em; vertical-align: top&quot;&gt;

== Grammar ==
[[Image:Nihongo Bunpou b.100x400.svg|right]]
:''Here will end the grammar points from the [[/Contents/]] once they develop into something solid.''
* [[/Nouns Reference/]]
* [[/Adjectival Reference/]]
* [[/Verb Reference/]]
* [[/Particles/]]
* [[/Expressions/]]
* [[/Verb conjugation table/]]
* http://www.guidetojapanese.org/
&lt;/td&gt;
&lt;td style=&quot;border: 1px solid #8B2500; background-color: #FAF4E6;{{Text default color}}; margin: .2em; padding: .5em; vertical-align: top&quot;&gt;

== Vocabulary ==
[[Image:言-red.png|right|160px]]
:''See also the vocabulary [[/Vocabulary/|list]] and [[:Category:Japanese vocabulary|category]] for a more extensive list of available contents.''

* [[/Vocabulary/Academic Subjects/|Academic subjects]]
* [[/Vocabulary/Animals/|Animals]]
* [[/Vocabulary/Banking/|Banking]]
* [[/Vocabulary/Body parts/|Body parts]]
* [[/Vocabulary/Colors/|Colours]]
* [[/Vocabulary/Computing/|Computing]]
* [[/Vocabulary/Clothes and accessories/|Clothes and accessories]]
* [[/Vocabulary/Country Names/|Countries and languages]]
* [[/Vocabulary/Direction|Directions]]
* [[/Vocabulary/Family and people/|Family and people]]
* [[/Vocabulary/Food and Drink/|Food and drink]]
* [[/Vocabulary/Health/|Health]]
* [[/Vocabulary/Numbers/|Numbers]]
* [[/Vocabulary/Time/|Time]] and [[/Vocabulary/Dates/|dates]]
* [[/Vocabulary/Weather|Weather and seasons]]

* The basic 1000 Japanese [[wikt:Appendix:1000_Japanese_basic_words|words]]
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;border: 3px solid #A5A77F; background-color: #FAF4F4;{{Text default color}};margin: .2em; padding: .5em&quot; colspan=&quot;2&quot;&gt;

== Related Wikibooks ==
{{Wikipedia|Japanese proverbs}}
* [[East Asian Orthography]]
* [[Japanese Phrasebook]]
* [[JLPT Guide]]
* [[Living in Japan]]
* [[Cookbook:Cuisine of Japan]]
* [[Japanese History]]
&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;</text>
      <sha1>8kjyuj4956qv2xrtgnnv5qy8sd53upy</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Kmatusik</title>
    <ns>3</ns>
    <id>176191</id>
    <revision>
      <id>4669081</id>
      <parentid>4667951</parentid>
      <timestamp>2026-09-06T07:19:09Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669081</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8632" sha1="5op9dgjeitjdzm1x70w8eb6oe393o4x" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Kmatusik!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything, and changes can be made easily. Come [[WB:HELP|introduce yourself]] to everyone, and let us know what interests you.
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* We tag pages with various [[WB:TM|message templates]], such as {{tlx|query}}, to let editors know what needs to be improved. To learn more about these, ask at [[WB:PROJECTS|the projects reading room]], or insert &lt;nowiki&gt;{{helpme|your reason here}}&lt;/nowiki&gt;
* You cannot upload an image until you have been a member for at least '''4 days'''. If your upload is tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] and source citation are always required; fair use images require a {{tlx|fair use rationale}}. Get help in the [[WB:HELP|user assistance room]].
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 21:08, 17 November 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}


== Copyright problems with [[:Image:Transition-state analogs.png|Image:Transition-state analogs.png]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Transition-state analogs.png|Image:Transition-state analogs.png]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Transition-state analogs.png|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. [[User:Abigor|Abigor]] ([[User talk:Abigor|talk]]) 13:37, 11 January 2009 (UTC)}}


== Copyright problems with [[:Image:Pyrrole 2-carboxylic acid.png|Image:Pyrrole 2-carboxylic acid.png]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Pyrrole 2-carboxylic acid.png|Image:Pyrrole 2-carboxylic acid.png]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Pyrrole 2-carboxylic acid.png|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. [[User:Abigor|Abigor]] ([[User talk:Abigor|talk]]) 13:37, 11 January 2009 (UTC)}}


== Copyright problems with [[:Image:N-methylprotoporphyrin.png|Image:N-methylprotoporphyrin.png]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:N-methylprotoporphyrin.png|Image:N-methylprotoporphyrin.png]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:N-methylprotoporphyrin.png|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. [[User:Abigor|Abigor]] ([[User talk:Abigor|talk]]) 13:38, 11 January 2009 (UTC)}}


== Copyright problems with [[:Image:Racemization of Proline.png|Image:Racemization of Proline.png]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Racemization of Proline.png|Image:Racemization of Proline.png]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Racemization of Proline.png|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. [[User:Abigor|Abigor]] ([[User talk:Abigor|talk]]) 13:38, 11 January 2009 (UTC)}}</text>
      <sha1>5op9dgjeitjdzm1x70w8eb6oe393o4x</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:KinkyBootBeast231</title>
    <ns>3</ns>
    <id>176192</id>
    <revision>
      <id>4669078</id>
      <parentid>4667953</parentid>
      <timestamp>2026-09-06T07:16:57Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669078</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="14091" sha1="70m4qzi9kw2tbkn4weu0k2en4ymtnwh" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, KinkyBootBeast231!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything, and changes can be made easily. Come [[WB:HELP|introduce yourself]] to everyone, and let us know what interests you.
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* We tag pages with various [[WB:TM|message templates]], such as {{tlx|query}}, to let editors know what needs to be improved. To learn more about these, ask at [[WB:PROJECTS|the projects reading room]], or insert &lt;nowiki&gt;{{helpme|your reason here}}&lt;/nowiki&gt;
* You cannot upload an image until you have been a member for at least '''4 days'''. If your upload is tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] and source citation are always required; fair use images require a {{tlx|fair use rationale}}. Get help in the [[WB:HELP|user assistance room]].
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 21:08, 17 November 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}


== Copyright problems with [[:Image:Proteinsequencingchart.jpg|Image:Proteinsequencingchart.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Proteinsequencingchart.jpg|Image:Proteinsequencingchart.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Proteinsequencingchart.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 20:04, 26 November 2008 (UTC)}}


== Copyright problems with [[:Image:Proteinsequencingexample.jpg|Image:Proteinsequencingexample.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Proteinsequencingexample.jpg|Image:Proteinsequencingexample.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Proteinsequencingexample.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 20:04, 26 November 2008 (UTC)}}


== Copyright problems with [[:Image:Proteinsequencing.jpg|Image:Proteinsequencing.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Proteinsequencing.jpg|Image:Proteinsequencing.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Proteinsequencing.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 20:04, 26 November 2008 (UTC)}}


== Copyright problems with [[:File:Proteinsequencingexample.jpg|File:Proteinsequencingexample.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:File:Proteinsequencingexample.jpg|File:Proteinsequencingexample.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:File:Proteinsequencingexample.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 04:05, 22 December 2008 (UTC)}}


== Copyright problems with [[:Proteinsequencingchart.jpg|Proteinsequencingchart.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Proteinsequencingchart.jpg|Proteinsequencingchart.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Proteinsequencingchart.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. }}
[[User:Abigor|Abigor]] ([[User talk:Abigor|talk]]) 20:34, 10 January 2009 (UTC)


== Copyright problems with [[:Image:Free energy diagram.jpg|Image:Free energy diagram.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Free energy diagram.jpg|Image:Free energy diagram.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Free energy diagram.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. [[User:Abigor|Abigor]] ([[User talk:Abigor|talk]]) 13:40, 11 January 2009 (UTC)}}


== Copyright problems with [[:Image:Ping pong reaction.jpg|Image:Ping pong reaction.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Ping pong reaction.jpg|Image:Ping pong reaction.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Ping pong reaction.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. [[User:Abigor|Abigor]] ([[User talk:Abigor|talk]]) 13:41, 11 January 2009 (UTC)}}


== Copyright problems with [[:Image:Blood clotting.jpg|Image:Blood clotting.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Blood clotting.jpg|Image:Blood clotting.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Blood clotting.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. [[User:Abigor|Abigor]] ([[User talk:Abigor|talk]]) 13:41, 11 January 2009 (UTC)}}


== Copyright problems with [[:Image:Blood clot final path.jpg|Image:Blood clot final path.jpg]] ==
{{mbox|type=warning|msg=
Thank you for uploading [[:Image:Blood clot final path.jpg|Image:Blood clot final path.jpg]]. However it is missing information needed for compliance with [[w:copyright|copyright law]] and Wikibooks' [[WB:MEDIA|media policy]]. This and other files you have uploaded may soon be deleted unless the '''copyright permissions''' and '''source''' can be determined. If you know this information, then please add the correct [[WB:ICT|templates]] to the [[:Image:Image:Blood clot final path.jpg|description page]] with the copyright and source information included; there is no need to upload it again. If you have any questions, feel free to contact me, or ask in the [[WB:HELP|assistance reading room]].

See {{UserImages}} for a complete list of your uploads which may get deleted soon.&lt;br/&gt;Thank you. [[User:Abigor|Abigor]] ([[User talk:Abigor|talk]]) 13:42, 11 January 2009 (UTC)}}</text>
      <sha1>70m4qzi9kw2tbkn4weu0k2en4ymtnwh</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Kimberleelee</title>
    <ns>3</ns>
    <id>176213</id>
    <revision>
      <id>4669084</id>
      <parentid>4667948</parentid>
      <timestamp>2026-09-06T07:22:28Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669084</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4562" sha1="oczakriu1h2uoywdkftec06ljb3lnmx" xml:space="preserve">&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Kimberleelee!&lt;/div&gt;
{| cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;margin:0em 0em 1em 0em; width:100%&quot;
| style=&quot;width:45%; vertical-align:top; border:1px solid #fad67d; background-color:#faf6ed;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing here and ''[[WB:AGF|assume good faith]]'' for the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything, and changes can be made easily. Come [[WB:HELP|introduce yourself]] to everyone, and let us know what interests you.
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #fad67d; background-color:#faecc8;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* We tag pages with various [[WB:TM|message templates]], such as {{tlx|query}}, to let editors know what needs to be improved. To learn more about these, ask at [[WB:PROJECTS|the projects reading room]], or insert &lt;nowiki&gt;{{helpme|your reason here}}&lt;/nowiki&gt;
* You cannot upload an image until you have been a member for at least '''4 days'''. If your upload is tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] and source citation are always required; fair use images require a {{tlx|fair use rationale}}. Get help in the [[WB:HELP|user assistance room]].
&lt;/div&gt;
| style=&quot;padding:0em 0.5em 0em 0.5em;&quot; |

| style=&quot;width:55%; vertical-align:top; border:1px solid #abd5f5; background-color:#f1f5fc;{{text default color}};&quot; |
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please [[:w:Wikipedia:Sign your posts on talk pages|sign your name]] on discussion pages by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* If you're coming here from Wikipedia, you should read [[WB:WFW|our primer for Wikipedians]] to get up-to-speed quickly.
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; background-color:#d0e5f5;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #abd5f5; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]].
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks &amp;nbsp;'''&amp;mdash;&amp;nbsp;[[User:Mike.lifeguard|&lt;b style=&quot;color:#309;&quot;&gt;Mike.lifeguard&lt;/b&gt;]]'''&amp;nbsp;&amp;#124;&amp;nbsp;&lt;sup&gt;[[User talk:Mike.lifeguard|&lt;span style=&quot;color:#309;&quot;&gt;talk&lt;/span&gt;]]&lt;/sup&gt; 23:26, 17 November 2008 (UTC)&lt;/div&gt;
|-
|style=&quot;text-align:right&quot; colspan=3|&lt;small&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/small&gt;
|}</text>
      <sha1>oczakriu1h2uoywdkftec06ljb3lnmx</sha1>
    </revision>
  </page>
  <page>
    <title>User:Renamed user wZdBmxEPfs/InkscapeTemplate</title>
    <ns>2</ns>
    <id>177128</id>
    <revision>
      <id>4668930</id>
      <parentid>3478772</parentid>
      <timestamp>2026-09-05T12:35:23Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668930</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="503" sha1="m7l1uf5twiub7cdet22n7js0x18sssg" xml:space="preserve">{| style=&quot;align: center; float: bottom; border-spacing:8px; margin:0px -8px; width: 100%; border: 3px solid #cbcb98; background-color: #ffffcb; {{Text default color}}; vertical-align: center;  -moz-border-radius:10px&quot;
|style=&quot;text-align: center&quot;|[[Inkscape/About|About]] - [[Inkscape/Introduction|Introduction]] - [[Inkscape/Shape_Tools|Shape Tools]] - [[Inkscape/Path_Drawing_Tools|Path Drawing Tools]] - [[Inkscape/Other_Tools|Other Tools]]
|style=&quot;text-align: right&quot;| back to [[Inkscape|contents]]
|}</text>
      <sha1>m7l1uf5twiub7cdet22n7js0x18sssg</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/Developer/Porting software</title>
    <ns>0</ns>
    <id>179093</id>
    <revision>
      <id>4668969</id>
      <parentid>4492790</parentid>
      <timestamp>2026-09-05T17:35:26Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668969</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="49250" sha1="euv6lzqz41mmnynx12kz0rh2gon6sla" xml:space="preserve">{{ArosNav}}


==Introduction==

Before you attempt to port a program, make sure it's API dependencies are met on AROS.
(AmigaOS (TM) 3.x C API is considered AROS native)

* Acceptable: ANSI-C/C++, [ SDL v1 but v2 wip], GTK via [http://sourceforge.net/projects/gtk-mui/ gtk-mui], [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/library Cairo] (old port), OpenGL via Gallium3D acceleration, ...
* Very difficult: PyGame, Boost, Allegro, no SDL, Gnome, KDE and/or QT4, Godot, etc.
* Impossible: Java, C#, any Windows-only source, etc.

==Compilers and tools==

Open shell - its a menu option at the top left of Wanderer (desktop). Or by using the right Win key and w (or F12 and w) within the directory with the makefile. Type in  
 sh 
to change the amiga shell into a unix shell. You can then type in ls (unix equivalent to amiga dir). Take a look [http://en.wikibooks.org/wiki/Linux_commands here] for commands.

For a single file program-name.c or program-name.cpp
 gcc -o program-name program-name.c  
or 
 g++ -o program-name program-name.cpp

To close the shell, click on the top left-hand corner to close (twice).

Other missing symbols are due to linker libraries being necessary for linking in functions that aren't in the standard C libraries. For example some source code would need added 
 -lz -lm -lpng 
to compile or even -lmui switch to link a program with a MUI gui.

use this in unix line command mode to search for 'search-item' in many .c files (*.cpp for c++, etc.)
 grep -l 'search-item' *.c

==Using CONFIGURE to create a Makefile==

Open shell - its a menu option at the top left of Wanderer (desktop). Or by using the right Win key and w within the directory with the configure and make files. Type in  
 sh 
to change the amiga shell into a unix shell.

 configure—help

to see the available options. You'll need time to examine the options and choose the right ones. 
Hints are available later on. When you configure GCC using the `configure' script, it will construct the file `Makefile' from the template file `Makefile.in'. When it does this, it will incorporate makefile fragment files from the `config' directory, named `t-TARGET'  and `x-HOST'. If these files do not exist, it means nothing needs to be added for a given target or host.

Examples...
&lt;pre&gt;
 configure prefix=/PROGDIR --build=i686 --host=i686 --disable-nls

 configure prefix=/PROGDIR --build=i386 --host=i386 --disable-nls --without-opengl --without-star --disable-sdltest

 configure LDFLAGS=&quot;-nix&quot; --prefix=/PROGDIR --build=i386 --disable-nls --without-x --without-pic 
--disable-shared GREP=bin: --enable-client=sdl --disable-server --disable-sdltest
--with-sdl-prefix=development:include/SDL
&lt;/pre&gt;

to create a Makefile but if it does not work, look at the Hints section below 

==EDITING CONFIGURE to suit AROS==

Take a look at Fishy's tutorial [http://web.archive.org/web/20111107002757/http://fishys-house-of-aros-fun.webs.com/apps/blog/show/2651598-aros-porting-guide first]

dir ../   unix moving back a directory or two

dir /    amiga equivalent

When the Makefile is created, whilst in the unix shell, type in

 make -f Makefile

to create the program...

===CREATING MAKEFILE from a blank text file===


====Generic template makefile (not to be used)====

which requires multiple copies of .c .o files


&lt;pre&gt;
CC = gcc
#CC = g++
#AS = nasm -f coff
#AR = ar
LDFLAGS = -s
FLAGS = -I. -Icpu -Iaros -Wall -march=pentium -fomit-frame-pointer
LIBS =	-lz -lm -LDevelopment:lib
#LIBS =	-lSDL_net lSDL_ttf -lSDL_mixer -lSDL_image -lpng -ljpeg -lz -lvorbisfile -logg -lSDL
#LIBS =	-lz -lm -LDevelopment:lib -lglu -lglut -lgl -lSDL_mixer -lSDL_image -lpng -ljpeg -lz -lSDL
EXE =   name
OPTS =	-O2

#

@echo &quot;Building source files...&quot;
$(CC) $(FLAGS) $(OPTS) -c src/.c -o obj/.o
$(CC) $(FLAGS) $(OPTS) -c src/.c -o obj/.o
#$(CC) $(FLAGS) $(OPTS) -c src/.cpp -o obj/.o
#$(CC) $(FLAGS) $(OPTS) -c src/.cpp -o obj/.o

@echo &quot;Making executable...&quot;
$(CC) $(LDFLAGS) $(FLAGS) -o $(EXE) obj/.o $(LIBS)

@echo &quot;Done!&quot;
&lt;/pre&gt;


Remove # from CC = g++, if g++ compiler needed. Remember to put # it in front of CC = gcc. # at the start acts as a comment line and are not processed. Similarly, remove/add # in the LIBS part to activate simple command line compiling, simple SDL compiling or openGL compiling respectively.

Replace name with the program title in EXE part.

Then add various .c (compiling with gcc) or .cpp (compiling with g++) source code you want to compile and .o also 
&lt;pre&gt;
$(CC) $(FLAGS) $(OPTS) -c src/main.c -o obj/main.o 
&lt;/pre&gt;

Finally, collect all the .o for the final line
&lt;pre&gt;
$(CC) $(LDFLAGS) $(FLAGS) -o $(EXE) obj/main.o main2.o etc.o $(LIBS)
&lt;/pre&gt;


[http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/utility MakeTools] should be looked at also.

&lt;pre&gt;
CC = gcc
CFLAGS = -O
LDFLAGS = -lSDL_image -lpng -ljpeg -lSDL_ttf -lfreetype2 -lSDL_mixer -lvorbisfile -lvorbis -logg -lSDL -lgl -lglu -lz -lstdc++ -lm

OBJS = part1.o part2.o main.o

# $(OBJS) will look above for list of .o and then use the statements below to see what to do with them

myprogram: ${OBJS}
	${CC} -o myprogram ${CFLAGS} ${OBJS} $(LDFLAGS)

#--------------------------------------------------------

part1.o: part1.c part1.h header.h
	${CC} ${CFLAGS} -c part1.c

part2.o: part2.c header.h
	${CC} ${CFLAGS} -c part2.c

main.o: main.c header.h
	${CC} ${CFLAGS} -c main.c

clean:
	rm -f myprogram ${OBJS}
        @echo &quot;all cleaned up!&quot;

&lt;/pre&gt;

====Better Makefiles====

Just use the one that suits you.

&lt;pre&gt;
#Simpler version suffices for most small-scale projects 
#DEPS is needed to recompile hellomake.c with changed hellomake.h

CC=gcc
CFLAGS=-I.
DEPS = hellomake.h

# gcc, $(CC) and rm need to be TABbed to work with make

# macro DEPS, which is the set of .h files on which the .c files depend
%.o: %.c $(DEPS)
# -o $@ compiler output into file named on the left side of hellomake: below ie hellomake 
# the $&lt; is the first item in the dependencies list #DEPS
	$(CC) -c -o $@ $&lt; $(CFLAGS)

#putting the object files--hellomake.o and hellofunc.o in dependency list
#make knows it must first compile the .c versions individually, and then build the executable hellomake

hellomake: hellomake.o hellofunc.o 
	gcc -o hellomake hellomake.o hellofunc.o -I

&lt;/pre&gt;

&lt;pre&gt;
CC = gcc
CFLAGS = -O2 -I/include 
LDFLAGS = -lSDL_image -lpng -ljpeg -lSDL_ttf -lfreetype2 -lSDL_mixer -lvorbisfile -lvorbis -logg -lSDL -lgl -lglu -lz -lstdc++ -lm

#-----------------------------------------------------------------------------

OBJS = part1.o main.o

program: $(OBJS)
	$(CC) $(OBJS) -o $@ $(LDFLAGS) 
	$(STRIP) --strip-unneeded --remove-section=.comment $@

#-----------------------------------------------------------------------------

part1.o:   part1.c part1.h 
	@echo &quot;  Compiling $*...&quot;
	@$(CC) $(CFLAGS) $*.c

main.o: main.c header.h
	@echo &quot;  Compiling $*...&quot;
        @${CC} ${CFLAGS} $*.c

clean:
      rm -f myprogram ${OBJS}
      @echo &quot;all cleaned up!&quot;

&lt;/pre&gt;

&lt;pre&gt;

# Template for a simple generic Makefile
#
CC = i386-aros-gcc
# CPP = i386-aros-gcc -E
# CXX =
# CPPFLAGS =
# CXXFLAGS =
CFLAGS = (cflags)
LDFLAGS = (ldflags)
TARGET = (final-file-name)
OBJECTS = file1.o file2.o file3.o
LINKS = file1.c file2.c file3.c
# XTRAOBJ =
#
# rules
#
all: $(TARGET)

$(TARGET): $(OBJECTS) $(XTRAOBJ)
$(CC) $(OBJECTS) $(XTRAOBJ) $(LDFLAGS) -o $(TARGET)

%.o: %.c
$(CC) $(CFLAGS) -c $&lt; -o $@
#
# eof
# Cycloid Makefile Example
# OBJ = window2.o
#
# w.exe: $(OBJ)
# $(CC) $(CFLAGS) -o $@ $^ $(ARCHIVE) $(LIB)
#
# window.o: window2.c
#
# $(CC) $(INCL) -c window2.c

&lt;/pre&gt;

&lt;pre&gt;
# .h files in an include directory 
IDIR =../include

CC=gcc
CFLAGS=-I$(IDIR)

# .o files into a obj subdirectory and some local libraries in lib directory
ODIR=obj
LDIR =../lib

macro defined for any libraries you want to include, like mui library -lMUI
LIBS=-lMUI

_DEPS = hellomake.h
DEPS = $(patsubst %,$(IDIR)/%,$(_DEPS))

_OBJ = hellomake.o hellofunc.o 
OBJ = $(patsubst %,$(ODIR)/%,$(_OBJ))

$(ODIR)/%.o: %.c $(DEPS)
	$(CC) -c -o $@ $&lt; $(CFLAGS)

hellomake: $(OBJ)
	gcc -o $@ $^ $(CFLAGS) $(LIBS)

# .PHONY rule keeps make from doing something with a file named clean 
.PHONY: clean

# cleaning up your source and object directories 
clean:
	rm -f $(ODIR)/*.o *~ core $(INCDIR)/*~

&lt;/pre&gt;

&lt;pre&gt;
#simple makefile
CC=gcc
CFLAGS=-O2 -s -DNO_INLINE_STDARG -I./api/ -I../api/ -I../modules/api/ -I../amide/modules/api/amide/
LDFLAGS=$(CFLAGS) -nostartfiles -nodefaultlibs -lamiga -lstdc.static -lgcc
EXE=plugins/test.plugin

# Objects
OBJS =	StartUp.o \
	LibInit.o \
	sasc_module.o

all: $(EXE)

clean:
	rm -f *.o $(EXE)

$(EXE): $(OBJS)
	echo Making $@..
	$(CC) -o $(EXE) $(OBJS) $(LDFLAGS)
&lt;/pre&gt;

==Hints for correcting errors==

*undefs about std:: and operators mean that you need to use or g++ , or if you use gcc, then add to -lstdc++ 
*undefs about sdl_wav mean -lsdl_mixer, 
*undefs about AROSMesa mean -lgl, 

Link order is important, so you can't for example firstly do -lgl, and then -lsdl. As sdl wants gl, you will need to do -lsdl -lgl, and the same for all the other libs : include one after another when undefs happens.

 -lSDL_image -lpng -ljpeg -lSDL_ttf -lfreetype2 -lSDL_mixer -lvorbisfile -lvorbis -logg -lSDL -lgl -lglu -lz -lstdc++ -lm

There are undefined symbols in 'sasc.module':
__PROGRAM_ENTRIES__symbol_set_handler_missing
__LIBS__symbol_set_handler_missing

remove the -nostartfiles argument from command line 
the missing symbols are part of AROS automatic startup handling. Possibly manually adding -llibinit could fix the missing symbols.


add -nodefaultlibs like this:

LINK := $(OPTIMIZE) -s -nostartfiles -nodefaultlibs


should remove all automatically added libraries and now you will have to add them manually 

$(CC) $(LINK) -o $@ $(O_FILES) -lamiga -lstdc.static -lgcc

&lt;pre&gt;
#simple makefile
CC=gcc
CFLAGS=-O2 -s -DNO_INLINE_STDARG -I./api/ -I../api/ -I../modules/api/ -I../amide/modules/api/amide/
LDFLAGS=$(CFLAGS) -nostartfiles -nodefaultlibs -lamiga -lstdc.static -lgcc
EXE=plugins/test.plugin

# Objects
OBJS =	StartUp.o \
	LibInit.o \
	sasc_module.o

all: $(EXE)

clean:
	rm -f *.o $(EXE)

$(EXE): $(OBJS)
	echo Making $@..
	$(CC) -o $(EXE) $(OBJS) $(LDFLAGS)
&lt;/pre&gt;


and LoadModules function calls that function from main.c, case of AROS it is best to use portable macros to make these calls 

&lt;pre&gt;
mod_class =AROS_LC0(void *, AmIDE_API_GetClass,
        struct Library *, (AmIDE_API_Base), 5, AmIDE_API    );
&lt;/pre&gt;

#include &lt;aros/libcall.h&gt;


Additionally, most AROS code depends on the library bases being opened automatically so you may need to add a link library, libauto (-lauto). Some systems (so it's down to the compiler to provide it) don't have working libauto in which case you need to open the library bases manually.

AROS OS 64Bit GCC 10+ enforces strict checks on void variables so gcc output-&gt; error: variable or field __ret declared void.
AROS_LC0NR variant of macros to handle void return type (NR stands for No-Return) with more [http://www.aros.org/es/documentation/developers/app-dev/portable.html here] 

[http://aros.sourceforge.net/documentation/developers/porting.php Hints can be found here] 
Be warned that these links apply to using Linux to compile code and not native but may be useful.


&lt;pre&gt;
CONFIGURE ERRORS

Error    : no acceptable C compiler found in $PATH
Solution : add CC=gcc or CC=g++ after configure

Error    : no acceptable grep could be found in /Development/bin:
Solution : add GREP=bin: to configure line

Error    : gtk-mui library sequence
Solution : gcc -o test addbutton.c\ -lglib-2.0 -lgtlayout -lgthread-2.0 -lgmodule-2.0 -lgobject-2.0 -lgtk-mui -lglib-2.o -liconv -lmui -lthread

Error    : VARIABLE not within scope
Solution : add headers like...  #include &lt;libraries/mui.h&gt; #include &lt;proto/muimaster.h&gt; or #include &lt;string.h&gt; etc

Error    : malloc.h no such file or directory 
Solution : malloc is contained within &lt;aros/stdlib.h&gt;

Error    : SDL.h no such file or directory
Solution : #include SDL/SDL.h needed at top of .c file or -IDevelopment:include/SDL to the command line

Error    : 
Solution :

Error    : IMG_Load in -lSDL_image ... cannot find libSDL_image
Solution : ??

Error    : pow in -lm - 'case' unmatched - math.library (-lm) appears broken
Solution : ??

Error    : 
Solution :

Error    : 
Solution :

MAKE ERRORS

Error    : *** missing separator.  Stop. 
Solution : Make commands like gcc $(CC) or rm need to be TABbed in and not use spaces

Error    : 
Solution :

Error    : 
Solution :

Error    : 
Solution :

COMPILING ERRORS

Error    : expected '=' ';' &quot;asm&quot; or '__attribute__' before '{'
Solution : look at previous lines for missing/extra ; (like in defines) or missing } or forgot to #include something.h. Use gcc -E to check

Error    : request for member 'something' in function not a structure or union
Solution : using b.x = 12 (usually arrays); when it should be b-&gt;x (usually structs) or (*b).x, .h needed,

Error    : 'something' undeclared (first use in this function)
Solution : 'something' been declared at start of function, .h needed or link library needed -lmui etc.,

Error    : there are undefined symbols in program 
Solution : /* around these symbols' */ until you work out if they are needed or can be deleted

Error    : there are undefined symbols in &lt;program-name&gt; or memcpy strndup first 
Solution : linker library not included -lz -lSDL or -lGL etc or &lt;string.h&gt;

Error    : expected specifier-qualifier list before 'USHORT'
Solution : change all references of USHORT into UWORD (SHORT into WORD)

Error    : expected declaration specifiers or '...' before 'USHORT' 
Solution : replace USHORT with UWORD (SHORT into WORD)

Error    : field 'name' has incomplete type 
Solution :

Error    : expected ')' before 'type' 
Solution :

Error    : invalid conversion from 'ULONG*' to 'IPTR*'
Solution : most amiga like OS's return ULONG values or use ULONG TAGS but 64bit AROS needs IPTR used for compatibility

Error    : dereferencing pointer to incomplete type 
Solution :

Error    : If crackly break-up noise found in SDL sound 
Solution : try to find where the number of samples for the buffer is set in the source and increase it (double it at least). This solves many sound issues with SDL programs. The buffer was set to 1024, now set it to 4096.

Error    : initializer element is not constant around TAG_DONE);
Solution : header(s) &lt;utility.h&gt; and &lt;proto/utility.h&gt; need to be added

Error    : no i386-sdl-config
Solution : use --build=i686 instead of --build=i386

Error    : functions not found at final linking: SDL_CondWait, SDL_CondSignal, SDL_CreateCond
Solution : find them in the SDL_cond_aros.c file in the cdxlplay-sdl source http://www.a500.org/downloads/video/

Error    : crash glutGet((GLenum)GLUT_ELAPSED_TIME);
Solution : The glutInit function is needed, replace with by SDL_GetTicks()

Error    : undefined symbols: recv, connect, inet_pton, socket, select, send, inet_ntoa
Solution : LDFLAGS : -lSDL_net -lSDL with #include &lt;proto/bsdsocket.h&gt; (or &lt;proto/socket.h&gt;) in all files using SDL_net

Error    : SDL is not built with CDROM support.
Solution : Look for SDL_INIT. It can look something like this:
             if( SDL_Init( SDL_INIT_EVERYTHING ) == -1 )
             change it to:
             if ( SDL_Init(SDL_INIT_VIDEO|SDL_INIT_TIMER|SDL_INIT_AUDIO|SDL_INIT_JOYSTICK ) == -1 )
           That includes all the init routines available in SDL, minus the CD one.

Error    : Video mode set failed: OpenGL support not configured
Solution : 'sdl-config --libs' is fine for most SDL uses, but with GL it needs to be replaced with &quot;-lgl&quot;

Error    : 
Solution :

Error    : 
Solution :

RUN TIME ERRORS

Error    : 
Solution :

Error    : 
Solution :

Error    : 
Solution :

Error    : 
Solution :

Error    : 
Solution :

Delinting (removing warning messages)

64bit compatibility 
-        MUIA_Application_Copyright, _(MSG_AppCopyright),
+        MUIA_Application_Copyright, (IPTR)_(MSG_AppCopyright),

-        io-&gt;io_Unit   = (struct Unit *)unitnum;
+        io-&gt;io_Unit   = (struct Unit *)(IPTR)unitnum;


Clean up
-    ULONG signals;
+    ULONG signals = 0;

-    while((t = LibNextTagItem(&amp;tagList)))
+    while((t = LibNextTagItem((struct TagItem **)&amp;tagList)))

-       while ((tag = LibNextTagItem(&amp;msg)))
+       while ((tag = LibNextTagItem((struct TagItem **)&amp;msg)))

-    const struct TagItem *tstate = msg-&gt;ops_AttrList;
-    struct TagItem *tag;
+    struct TagItem *tag, *tstate = msg-&gt;ops_AttrList;

-        sprintf(buf, &quot;SYS/printer%d.prefs&quot;, unit);
+        sprintf(buf, &quot;SYS/printer%d.prefs&quot;, (int)unit);

-    STRPTR _return = NULL;
+    CONST_STRPTR _return = NULL;

-    return (CONST_STRPTR)_return;
+    return _return;

&lt;/pre&gt;

==Hints: Porting software from...==


===AmigaOS===

The right form of the main() function is
&lt;pre&gt;
int main(void)
{
...
return retval;
}

or

int main(int argc, char **argv)
{
...
return retval;
}
&lt;/pre&gt;

(Old code has often &quot;void main()&quot; or no return type at all)

For retval you can either use 0, EXIT_SUCCESS or EXIT_FAILURE (ANSI-C) or ADOS return codes which I don't know off-hand.

First turn anything that ending in _proto.h 
&lt;pre&gt;
#include &lt;dos/dos_proto.h&gt;
to
#include &lt;proto/dos.h&gt;
&lt;/pre&gt;
and if you want it more portable, then try
&lt;pre&gt;
#ifdef AROS
#include &lt;proto/dos.h&gt;
#else
#include &lt;dos/dos_proto.h&gt;
#endif
&lt;/pre&gt;

Include function prototypes for shared libraries from proto
e.g. #include &lt;proto/graphics.h&gt; instead of #include &lt;clib/graphics_protos.h&gt;

If the compiler complains about wrong type in a line like
 struct Library *GfxBase
you have to look up the right type in the header, e.g. in includes/proto/graphics.h

 #include &lt;proto/library_name.h&gt;

(replacing with correct name) should pull in the necessary info for automatic opening/closing of CORE libraries to work with basic applications which are written as DOS and Workbench/Wanderer launched processes. Others like mui have to be specified (-lmui in the gcc command line).

It looks like you are still including from clib. You either have to include from proto or you have to link with -lexec -lgadtools, etc.

There are undefined symbols in 'inctst':
U AllocMem
U FreeMem

Adding -lexec removed the errors.

&lt;pre&gt;
There are undefined symbols in 'a.out':
SetFont
CloseFont
OpenFont 
&lt;/pre&gt;

try -lgraphics or #include &lt;proto/graphics.h&gt; or #include &lt;defines/graphics.h&gt; or #include &lt;clib/graphics_protos.h&gt;

&lt;pre&gt;
Include sys/types.h before netinet/ip.h
Include &lt;netdb.h&gt; first before rest of your network includes 
&lt;/pre&gt;

Most AROS C/C++ Compilers can open and close the libraries for you as part of the startup code. As long as you have the protos included in the headers and the appropriate compiler options specified, the compiler will take care of opening any used libraries for you.

The library header source is in principle like AOS 68k too, with Resident struct, functable and so on. Except AROS has its own set of macros for functions which get parameters in registers. The AROS_LH#? and AROS_UFH#? stuff. You should be able to use contrib/mui/classes/nlist/commonaros/mccheader.c from AROS contrib sources as a hint.

But always remember, that coding for AROS is not coding for m68k Amiga. Much is different here and coding AROS in C means searching hundreds of include files for macros. And AROS source code is partly useless for an external newbie developer, as AROS has a deeply integrated build system which hides important parts from the implementing developers, e.g. a shared library consists only of its methods, the rest (Romtag, Jumptable etc.) is hidden in the AROS build system.


wbstart.library isn't ported indeed but its usage is depreciated and you are advised to convert its calls to use workbench.library/OpenWorkbenchObject() (which should be easy).

A temporary quick trick is to use CLI callings on C:Open which will launch programs using Workbench (using this very function). It can even be used with arguments which are passed as workbench arguments (ie like multi-clicked files).

====Programming languages====

As long as no assembler code is being used in the program, compiling a C program written for plain AmigaOS up to version 3.1 should be possible on AROS without any changes to the source code. (That presumes your AROS is using a 32bit big-endian CPU, like the original Amiga computer.) (Please note that '''AROS is still beta and incomplete''', and might lack some functions from AmigaOS API. See [[Aros/Developer/Docs#Status of AROS implementation|Status of AROS implementation]] for more on this.)

====Data types and sizes / little endian / big endian====

Some of the first things to consider is the actual size of your C data types, and in your uses of binary files (IFF for example) paying attention to reading and writing with portability to 64bit and little-endian CPUs as well as the classic mc680x0 or powerpc cpus used by Amiga OS.

* Warning signs is casting between char * and WORD/LONG/short/int etc., or any kind of pointer arithmetic, as well as any functions that read/write binary file formats (if they read character by character and/or does things similar to what I mentioned above, they are likely to be ok, if they read a chunk of memory in and treat it as a struct immediately then it will almost certainly fail).
* Endianness issues need to be fixed and there are a lot of them (reading/writing binary files, writing data into graphics frame buffers). Also network stack, file system, hardware. Pretty much any time you have to deal with external data, you have to worry about endianness. There are C #define macros to handle writing/reading the correct endianness and flipping the ordering when necessary.
* all LONG/ULONG/APTRs need to be checked if they need to be replaced by IPTR (e.g. relying on TagLists)

[we should probably have a chart showing sizes/endian used by Manx/sas/dice C on a mc68000/68030 vs today's PPC/i386/x86_64 AROS options here along with some GCC source code to show how to read/write binary files correctly under AROS running on differing endian CPUs]

====Screens====

Amiga chipset-graphics-based screens were generally done in a planar format 16/32-colors max for ECS hires/lores modes respectively and 256-colors for AGA.

[a chart of common amiga screen modes should go here]

Methods that worked well for the relatively low-resolution planar Amiga displays may be suboptimal for chunky and true color screens that are common today.

[pointer to examples should go here]

Amiga screens could be of differing resolution, which could be dragged up and down to reveal another, so some applications were written with differing resolution screens, say for a control panel at one resolution and another for the &quot;display&quot; visible at the same time stacked vertically. This may not make sense with today's chip sets or wide-screen displays. Opening multiple screens that vary in scan rate can confuse displays (monitors or projectors) that might take several seconds &quot;calibrating&quot; every time the user decides to change which public or private application screen they want to view. Defaulting to the user's preference for Wanderer (workbench) for screen mode is probably better than having a predefined mode hard-coded into your application.

====Fonts====

AmigaOS 3.1 also shipped with some nice disk fonts that are not currently available under AROS, so you should be careful about having any diskfont hard-coded as a default into your program. The ROM font &quot;topaz&quot; should be ok.

AROS fonts (as of 2010-03-10):
*arial.font
*dejavusansbold.font
*dejavusansboldoblique.font
*dejavusansbook.font
*dejavusanscondensedbold.font
*dejavusanscondensedboldobl.font
*dejavusanscondensedcondens.font
*dejavusanscondensedoblique.font
*dejavusansextralight.font
*dejavusansmonobold.font
*dejavusansmonoboldoblique.font
*dejavusansmonobook.font
*dejavusansmonooblique.font
*dejavusansoblique.font
*dejavuserifbold.font
*dejavuserifboldoblique.font
*dejavuserifbook.font
*dejavuserifcondensedbold.font
*dejavuserifcondensedboldob.font
*dejavuserifcondensedconden.font
*dejavuserifcondensedobliqu.font
*dejavuserifoblique.font
*fixed.font
*stop.font
*ttcourier.font
*Vera Mono Bold.font
*Vera Mono Bold Italic.font
*Vera Mono.font
*Vera Mono Italic.font
*Vera Sans Bold.font
*Vera Sans Bold Italic.font
*Vera Sans.font
*Vera Sans Italic.font
*Vera Serif Bold.font
*Vera Serif.font
*XEN.font

====GUI Toolkits====

=====Gadtools=====

The order of the fields in struct Node which is currently different than on AOS (will be changed in ABI V1).

struct Node has currently the following order:

&lt;pre&gt;
struct Node
{
    struct Node * ln_Succ,
        * ln_Pred;
    char    * ln_Name;
    UBYTE      ln_Type;
    BYTE      ln_Pri;
}; 
&lt;/pre&gt;

=====MUI=====

'''MUI''' - AROS' preferred GUI toolkit is Zune, a reimplementation of MUI 3.x, thus MUI 3.x code will work unchanged under AROS. MUI 4.x will need adapting or wait for the following [http://www.power2people.org/projects/profile/54 bounty] to be started.

=====ClassAct=====

'''ReAction/ClassAct''', a GUI toolkit for AmigaOS, is not available for AROS. It has been made part of AmigaOS 3.5 and higher. Programs that use ReAction might need considerable rework, preferably to use Zune (or: MUI), AROS' GUI toolkit.

=====BGui=====

'''bgui''' is available as part of the &quot;contrib&quot; archive, thus included in all current AROS binary distributions.

[We could use a chart comparing gui options for developers here.]

====C/C++ Compilers====

GCC/G++ is the primary C compiler supplied with AROS. Amiga programs making use of other compilers' (SAS/C, Maxon C, ...) specific functionality might need some rework.
You'll probably want to write makefiles that can run either hosted or native, so any AROS user can get them compiled and running on their machine. In a hosted environment the shell will most likely use UNIX semantics like cp==COPY ../==parent directory, and all file names will be case sensitive for your makefile and inside your C source code files (example: #include &quot;myFile.h&quot; != #include &quot;MyFile.H&quot;). Under AROS the makefile may use Amiga shell command semantics (copy #? progdir:prefs)or it may be using a UNIX shell ported to AROS, and the AROS environment, and like AmigaOS 3.1 may not care about case sensitivity of file names.

We can't use the SLOWSTACKTAGS macros for getting ULONG values from a variadic list.

===== SAS Lattice C Compiler=====

SAS/C was one of the more popular compiler packages back when AmigaOS 3.1 was released, it supported various keywords such as __chip for using chipram, and CPU-related register arguments that the current AROS GCC does not.

The makefiles will have to be translated from SMAKE to GNU Make and some of the headers will have to be translated from SC to GCC.

Pragmas were used on ancient C compilers like SASC. Include from &quot;proto&quot;, e.g. #include &lt;proto/workbench.h&gt;. Look if there are headers which include from &quot;clib&quot;. Change them to &quot;proto&quot;, too.

You can ignore warnings like &quot;suggested parentheses...&quot; or incompatible pointer types.

Some types and names of defines have changed (SHORT/USHORT -&gt; WORD/UWORD).

 -linput -lutility -lintuition -lrexxsyslib -lconsole -lgraphics -ldos -lexec

strmfp, stcgfe, stcgfp, stcgfn and stci_d are SAS/C / Lattice function that do not exist under gcc. They have to be reimplemented.

tolower and toupper was found once I've included ctype.h in the source code.
Sometimes missing symbols come from missing include files. Those are macros like toupper—not real functions, and the C preprocessor needs the include definition for the macro.

If you want your characters to be unsigned you need to put unsigned into the variable type. If you want them to be signed, put signed in the variable type. If you don't put either, you may get unexpected results.

Sometimes you need wrappers for functions which aren't part of ANSI C.

SAS/C allowed to use a type before it was defined =&gt; change the order or use forward declaration.

Use AROS macros for Hook functions as explained here:
http://aros.sourceforge.net/documentation/developers/app-dev/portable.php#hooks

There might be more if you are porting system software (libraries, interrupts etc.)
Just start and try to find the reason for warnings and errors.

Generally when porting sources, if a header doesn't exist in AROS, wrap it with an #if or #ifndef statement and see what symbols, structure definitions, etc. aren't found. Then you can look through the AROS includes to see if the missing symbols, etc. are implemented in another place, or if you have to make your own compatible include file with those defined.

For libraries you might want to look at the AROS source-tree to see how others have done it using things like [http://aminet.net/package/dev/gcc/sfdc sfdc], genmodule, etc.

* SAS/C included a ton of non-standard functions in its C library. Alternative versions of these can generally be found online, and for example YAM includes some of them in their sources, depending on license working around this is easy (none of these functions are big/difficult to re-implement if needed).
* SAS/C is very liberal in some of the things it accepts. This causes problems particularly for vbcc (not so relevant for AROS) but some things also for gcc, particularly in terms of type coercion and (lack) of forward declarations.
* SAS/C has a multitude of extensions targeting AmigaOS, such as non-standard 68k focused register declarations. These must either be removed or worked around by defining preprocessor macros that expand to nothing or a suitable replacement.
* The SAS/C smakefiles are a totally non-standard syntax.
* The general caveats of AmigaOS vs. AROS include files apply - many paths can be expected to be different.
* there might be endian issues
* you'll get a lot of compiler warnings. Some of them are harmless (e.g. &quot;parenthesis suggested ...&quot;). Others are dangerous (e.g. &quot;variable xxx may be undefined&quot;)
* for some specials like callback hooks you'll have to use AROS macros.


* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.
* Fix (change IPTR/SIPTR back to ULONG/LONG) the few places which really rely on ULONG/LONG being exactly 32 bit. That's for things like pixel (ARGB) buffers, structs written/read to disk, colormaps, but probably little else.


This is the [http://aros-exec.org/modules/newbb/viewtopic.php?start=30&amp;topic_id=5705&amp;viewmode=flat&amp;order=ASC&amp;type=&amp;mode=0 code] that I use in diskimage.device for converting a BSTR to a CSTR 
&lt;pre&gt;
LONG CopyStringBSTRToC (BSTR src, STRPTR dst, ULONG dst_size) {
#ifdef __AROS__
    STRPTR ptr = AROS_BSTR_ADDR(src);
    ULONG ln = AROS_BSTR_strlen(src);
#else
    UBYTE *ptr = BADDR(src);
    ULONG ln = *ptr++;
#endif
    if (ln &gt; (dst_size-1)) ln = dst_size-1;
    memcpy(dst, ptr, ln);
    dst[ln] = 0;
    return ln;
}
&lt;/pre&gt;

Some blankers{{typo help inline|reason=similar to blinkers|date=October 2022}} are missing the symbol &quot;custom&quot;. They have (as documented in the OS3.9 RKM) &quot;extern struct Custom custom;&quot;. 
'Custom' is a struct that maps the m68k Amiga AGA/OCS/ECS registers. Only build those for amiga-m68k, and you'll be fine.

=====Maxon Hisoft C=====

=====Dice C=====

=====North C=====

* RAWKEY: replaced with IDCMP_RAWKEY: 
* ModifyIDCMP(win,FLAGSON) replace with ?

===MorphOS===

====Assemblers/ Disassemblers====

ADis, which reads binaries into memory hunk by hunk to disassemble them, and then just treats it as an array of short. The &quot;right&quot; way would be to treat it as a char *, and do (arr[0] &lt;&lt; 8) + arr[1]. I wanted to use it to cross-disassemble M68k programs, but gave up and went with Ira instead because it was so pervasive.

===Linux Console Apps===

On AmigaOS this is done by libc on every I/O operation. Just AROS libs lacks this. 
Resources allocated by libc (malloc()ed memory, fopen() ed files, etc.) are safely reclaimed at exit(). libc tracks this internally. If your program additionally uses some AmigaOS API, it usually installs exit handler (I don't remebmer how), or disables Ctrl-C checking by redefining __chkabort() function.

You have to explicitly check for it on AROS (and AmigaOS). The reason for this is that there's no safe way for the OS to kill an app and reclaim all resources on AmigaOS and derivatives (since an app can have &quot;handed off&quot; memory and other resources to other tasks).

This is an example from the autodocs for SetSignal:

&lt;pre&gt;
#include &lt;libraries/dos.h&gt;

/* Check &amp; clear CTRL_C signal */
if(SetSignal(0L,SIGBREAKF_CTRL_C) &amp; SIGBREAKF_CTRL_C)
{ 
printf(&quot;CTRL-C pressed!n&quot;);
}
&lt;/pre&gt;

It is compiler dependent. It's safer to just do the SetSignal()-based check.


If you want a shared library, recommend getting linux-hosted aros building (use the gimmearos.sh script) and then look at the other library sources found in AROS/workbench/libs for examples of how its done.

If it were just a linker library, you can just compile the .c files with -fno-stack-protector (needed under aros-sdk cross compiler under linux, native aros gcc might not need that), etc. and join the .o files into a lib-yournamehere.a file with ar and ranlib them.

===SDL===

SDL_image may need -ljpeg -lpng -lz

SDL_mixer needs -lSDL_mixer -lvorbisfile -lvorbis -logg (in this order)


First thing to test with SDL sound under AROS is to increase the buffer. In all applications had needed this to obtain good sound output.

In most cases it would certainly mean that you have to increase the value of SYSSND_MIXSAMPLES. Usually multiplying this value by 2 or 4 gives good results.

You should also check the value of the obtained structure. It is not sure that AROS supports AUDIO_U8 and you might have reverted to AUDIO_U16. In this case sound will of course be distorted.

from [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=2533&amp;forum=2&amp;post_id=45301#forumpost45301 here]

Further tests with buffers using code from [http://www.kekkai.org/roger/sdl/mixer/ here], and this is the result I've noted:

&quot;a quick test compiling with 1024, 2048 or 4096 gave interesting results: 1024 - sounds are more responsive to key-events but if you quickly move the &quot;game-window&quot; around the screen you can hear sound glitches. 2048 - No big difference noticed in responsiveness and now no glitches moving the window around, anyway the fx-sound sample plays with some hiss-click glitches. 4096 - No hiss-click and no glitches moving the window BUT you can see that the responsiveness is decreased.

Trying this code then with original xRick 8bit samples gives good sound results, and even using 1024 bytes buffer the sound doesn't glitch when moving window&quot;

Seems to me that buffer depends a lot on responsiveness you need, overall game load and also what kind of sound samples you're using (of course the lower is the bit-encoding and frequency, the smaller you can use as buffer).


SDL_GetTicks just disable

 m_fLastTime = float(SDL_GetTicks())/1000;

in 2 places of sdlapp.cpp and add your own code at the end:

&lt;pre&gt;
    Ellapsed_Time = SDL_GetTicks() - Last_Time;
    if (Ellapsed_Time &lt; 20) /* 20 ms target =&gt; 50FPS */
    {
    SDL_Delay(20 - Ellapsed_Time);
    }
&lt;/pre&gt;

Maybe SDL_GetTicks works a bit wrong by some reasons in aros's SDL, right ? (because if the same code works fast on os4/mos/win32/anything-else), then it mean that something wrong with SDL_GetTicks then .. 
PS : SDL_GetTicks() isn't causing any trouble, its a basic SDL function that is used in almost all SDL applications.

 int CSDLApplication::Run() in sdlapp.cpp
and
 bool CMySDLApplication::FrameMove() in Armygaem.cpp

In initial-code Render3DEnvironment is called continuously and only FrameMove is updated at 50fps, Render() and SDL_GL_SwapBuffers() are called even if nothing has moved.
Calling the render() functions and SDL_GL_SwapBuffers(), too often is for me the root cause. A correction to OpenGL implementation would only be a safeguard to prevent stupid application from crashing or slowing down the system.

crash on exit is certainly due to the application not freeing any resources before exiting.

===Writing ROM-able code===

Code in AROS modules should be written in a way that makes it suitable for embedding into a ROM, FlashRAM or other kinds read-only memory. The following coding style rules are meant to make it possible. Of course they apply to all Kickstart modules and to code that may be made resident, shared or linked to other modules.
	 
ROM modules must have no .data and .bss sections. Basically, we need to get rid of all non-const global data. The real Amiga Kickstart proves that it's both possible and easy to achieve this. If you encounter an external variable (static or not) that is modified by the code, try to get rid of it or move it into the base of the library/device (or in the device node of your handler or in the userdata of your class).
	 
The above applies to library bases as well. If you are writing a library, put the bases of other libraries into your own library base structure. Boopsi classes can store library bases in their class private data.
	 
Try to set the static and const attributes to all your global data. You can also use the CONST_STRPTR and CONST_APTR types defined in &lt;exec/types.h&gt;. Using static const allows the compiler to move data into the .text (AKA code) segment. If you need to pass these globals to another function, try to change its prototype to use const too.

===Hooks and SDI===


A hook is a custom function you write in order to be able to handle a specific situation that arises from intercepting the main code (like processing a message). The function must be designed to accept three arguments, whose order and type is given.

* the first parameter (A0) contains the pointer to your hook, not to your window
* the 2nd Parameter points to the Object which causes this action, this isn´t your window but it´s the Object which was pressed (it´s always the Object which was connected to the Hook (=1st Parameter of DoMethod) 
* then give 5 as number of Parameters for MUIM_CallHook, but´s 4 (=number of all Parameters in DoMethod after the Count Parameter)

&lt;pre&gt;
AROS_UFH3S
(
void,
MyHookFunction,
AROS_UFHA(struct Hook * , hook, A0),
AROS_UFHA(Object * , obj, A2),
AROS_UFHA(ULONG * , params, A1)
)
&lt;/pre&gt;

params is an array but IPTR should be correct. Then you can access your parameters...

&lt;pre&gt;
app = (Object *) *params++;
window2 = (Object *) params++;
&lt;/pre&gt;


&lt;pre&gt;
The important thing about hook functions is that the parameters must be given in the order A0, A2, A1.
And not to leave out parameters even if they are unused by the hook function.

For initial quick&amp;dirty ports one can even simply defines things like
&quot;__saveds&quot;, &quot;__asm&quot;, &quot;__regargs&quot;, &quot;__stdargs&quot;, &quot;register ...&quot; to nothing.

For library functions it's the same (with library base as last param).

InitLib: libbase(d0), seglist(a0), sysbase(a6)
OpenLib: version(d0), libbase(a6)
CloseLib: libbase(a6)
ExpungeLib: libbase(d0), libbase(a6)

OpenDev: ioreq(A1), unitnum(d0), flags(d1), devbase(a6)
CloseDev: ioreq(a1), devbase(a6)
&lt;/pre&gt;

see [http://utilitybase.com/forum/index.php?action=vthread&amp;forum=3&amp;topic=1495 here]

The AROS asm call and lib call macros require param type (like &quot;struct Hook *&quot;) and param (like &quot;myhook&quot;) to be passed in two different arguments. Not in a single one.

Converting is easy. Adding some &quot;AROS_&quot; prefix plus some commas. Additionally in the hook functions and dispatcher functions &quot;HOOK_INIT&quot; / &quot;HOOK_EXIT&quot; / &quot;DISPATCHER_INIT&quot; / &quot;DISPATCHER_EXIT&quot; must be used (in case of AROS mapping to AROS_USERFUNC_INIT/AROS_USERFUNC_EXIT).

To force procedure parameters to use registers (like a0) in GCC

Since C calling convention on some machines (like 68k or x86) means params are passed on stack your C function must have params in correct order (Hook, object, msg) and not leave out params if they are unused by the function especially if it's the middle param (object).

 ULONG hook_function(REG(a0, struct Hook *hook), REG(a2, APTR object), REG(a1, APTR message))

In short when using HookEntry you initialize hooks like this:

&lt;pre&gt;
STATIC ULONG hookfunc(struct Hook *hook, APTR obj, APTR msg) 
{ 
/* ... *// 
}

#if defined(__amigaos4__) 
hook-&gt;h_Entry = hookfunc; 
#else 
hook-&gt;h_Entry = &amp;HookEntry; 
hook-&gt;h_SubEntry = hookfunc 
#endif 
&lt;/pre&gt;

If you are not using SDI headers this is the most universal method which works on OS3, OS4, AROS and MorphOS with every compiler and architecture.

Those dispatchers are usually taken as argument for MUI_CreateCustomClass(), which has:

&lt;pre&gt;
#if defined(__MAXON__) || defined(__amigaos4__)
    cl-&gt;cl_Dispatcher.h_Entry    = (HOOKFUNC)dispatcher;
#else
    cl-&gt;cl_Dispatcher.h_Entry    = (HOOKFUNC)metaDispatcher;
    cl-&gt;cl_Dispatcher.h_SubEntry = (HOOKFUNC)dispatcher;
#endif
&lt;/pre&gt;

metaDispatcher:

&lt;pre&gt;
#ifdef __AROS__
AROS_UFH3(IPTR, metaDispatcher,
    AROS_UFHA(struct IClass  *, cl,  A0),
    AROS_UFHA(Object *, obj, A2),
    AROS_UFHA(Msg     , msg, A1))
{
    AROS_USERFUNC_INIT
   
    return AROS_UFC4(IPTR, cl-&gt;cl_Dispatcher.h_SubEntry,
        AROS_UFPA(Class  *, cl,  A0),
        AROS_UFPA(Object *, obj, A2),
        AROS_UFPA(Msg     , msg, A1),
        AROS_UFPA(APTR    , cl-&gt;cl_Dispatcher.h_Data, A6)
    );

    AROS_USERFUNC_EXIT
}
&lt;/pre&gt;

What confuses me is that our own macros have registers:

&lt;pre&gt;
#define BOOPSI_DISPATCHER(rettype,name,cl,obj,msg) \
    AROS_UFH3(SAVEDS rettype, name,\
        AROS_UFHA(Class  *, cl,  A0),\
        AROS_UFHA(Object *, obj, A2),\
        AROS_UFHA(Msg     , msg, A1)) {AROS_USERFUNC_INIT
&lt;/pre&gt;

Maybe there is a difference between MUI and BOOPSI when it comes to dispatchers and SDI DISPATCHER can only be used for MUI.

AROS's MUI_CreateCustomClass() moves the dispatcher to h_SubEntry and uses something like HookEntry for h_Entry. There we don't have to care about registers.

BTW: SDI's hook macros *are* wrong for AROS.

&lt;pre&gt;
HOOKPROTONHNO(TestFunc, void, int *param)
{
    puts(&quot;Foobar&quot;);
}

MakeHook(TestHook, TestFunc);
&lt;/pre&gt;
expands to:
&lt;pre&gt;
static void TestFunc(__attribute__((unused)) struct Hook *_hook,
__attribute__((unused)) APTR _obj, int *param)
{
    puts(&quot;Foobar&quot;);
}

struct Hook TestHook = {{0L, 0L}, (HOOKFUNC)TestFunc, NULL, 0L};
&lt;/pre&gt;

That works only by accident on i386-AROS (because of stack parameters).
But there I *know* how to fix it and will soon send an update to you.

&lt;pre&gt;
#elif __AROS__

  #define MakeHook(hookname, funcname) struct Hook hookname = {{NULL, NULL}, \
    (HOOKFUNC)HookEntry, (HOOKFUNC)funcname, NULL}
  #define MakeHookWithData(hookname, funcname, data) struct Hook hookname =  \
    {{NULL, NULL}, (HOOKFUNC)HookEntry, (HOOKFUNC)funcname, (APTR)data}
  #define MakeStaticHook(hookname, funcname) static struct Hook hookname =   \
    {{NULL, NULL}, (HOOKFUNC)HookEntry, (HOOKFUNC)funcname, NULL}
  #define ENTRY(func) (APTR)func
  #define DISPATCHERPROTO(name) SAVEDS ASM IPTR name(REG(a0,                 \
    struct IClass * cl), REG(a2, Object * obj), REG(a1, Msg msg))
  #define DISPATCHER(name) DISPATCHERPROTO(name)
  #define SDISPATCHER(name) static DISPATCHERPROTO(name)
&lt;/pre&gt;

Difference is that funcname is moved to h_SubEntry.
Problem are the dispatcher macros. They'll currently only work with MUI_CreateCustomClass(). If I define them like our BOOPSI macros I have a new problem: what happens if I define a function with register macros
*AND* use HookEntry in h_Entry and the function in h_SubEntry?

BTW: in SDI_compiler.h there is:
&lt;pre&gt;
  /* we have to distinguish between AmigaOS4 and MorphOS */
  #if defined(_M68000) || defined(__M68000) || defined(__mc68000)
    #define REG(reg,arg) arg __asm(#reg)
    #define LREG(reg,arg) register REG(reg,arg)
  #else
    #define REG(reg,arg) arg
    #define SAVEDS
&lt;/pre&gt;

C++ is much more strict on types than C, this is the root of the problem. Absolutely everything should be casted, implicit conversions are not allowed at all. P.S. And casting is considered an extremely bad coding style IIRC...

Those who want to develop AROS API in C++ should update their headers from a current SDK.

HOOKFUNC looks now like this in include/utility/hooks.h:
 typedef IPTR (*HOOKFUNC)();

The prototypes have been included in &quot;extern C&quot; blocks, so that problems like this should be [http://aros-exec.org/modules/newbb/viewtopic.php?post_id=37123#forumpost37123 gone]

===Casts===

Casts simply put... casting through pointers, bad... casting through a union, [http://cellperformance.beyond3d.com/articles/2006/06/understanding-strict-aliasing.html good]*. (*exceptions apply) Hopefully someone can correct me if I'm wrong, but the main rule of thumb for avoiding these problems seems to be to not have two pointer variables in the same function that point to the same memory, but are of different type.

It's actually a little more subtle than this. They can point to different types, but not when the types do not contain sub-sets of the others.

i.e.

&lt;pre&gt;

struct Foo {
struct MinNode Node;
};
&lt;/pre&gt;

- any cast from struct Foo * to struct MinNode * is ok ...
but:
&lt;pre&gt;
struct Foo {
struct Foo *next;
struct Foo *prev;
};
&lt;/pre&gt;

- now casts from 'foo' to 'minnode' are not ok ... and worse, can be silently discarded (how that is considered polite behaviour I do not know). (and by extension, casting from List to Node are right out).

I would argue that this is actually a different language - it is no longer 'C', as such, and although the spec (as far as I have been able to ascertain) actually specifies this it has never been implemented in such a way until now. It is there to provide additional optimisation opportunities ... although the whole 'we'll just silently drop code that is otherwise quite obvious' thing is rather nasty.

The CellPerformance stuff really nails it all. Although I find it somewhat absurd you can cast pretty much anything through a union and it's 'ok', but using the language 'cast' exactly the same physical operation becomes 'illegal'.

NEVER EVER touch buffers passed in by the user as an &quot;input&quot; parameter. The concept of input parameters is often implicit in the function description. For instance, the filename passed to Open() is clearly an input variable and Open() must not mess with it, even if it is going to fix it back later. Keep in mind that the buffer might be in read-only memory or shared among several instances of a resident or multithreaded program.

Try to avoid host-OS calls such as malloc() and free() if you can do with AllocMem() and FreeMem(). This is because the pointer checking debug macros rely on finding the pointer within the Exec memory blocks with TypeOfMem().

 SA_BackFill, (ULONG) &amp;sbackfillhook,

Please do not use ULONG's to store/cast pointers in your code. use APTR/IPTR where appropriate.

==Compiling small parts of AROS source without using Build system==

[http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=3475&amp;forum=2&amp;post_id=29123#forumpost29123 from]

make stub
make
make install

and need genmodule from [http://pagesperso-orange.fr/franck.charlet/temp/radeon.zip inside] here.


Trying to build the support modules of [http://svn.berlios.de/wsvn/ignition/trunk/libs/scroller/ Ignition] with a normal Makefile:

How can I get rid of these linker warnings? 
U __includelibrarieshandling and U __this_program_requires_symbol_sets_handling


Is there something I have to care about when I create a module this way? 
(I have always used the build system in the past) Is there a function which must be the first in the generated module?

Are you using ld directly? If so, don't do that, use the compiler's driver instead (gcc, that is) to do all the steps, final linking included. The problem arises because the linker needs to be invoked through a wrapper, which in our case is called collect-aros (it would be collect2 on other systems). You can either call collect-aros in place of ld (I
wouldn't do that) or the compiler's driver (gcc, do that) as said above. Mh, hadn't noticed the makefile when I first replied and I had forgotten these symbols are actually produced by collect-aros itself.

The problem arises because you are using -nostartfiles, which avoids linking with the startup file, but the startup file contains code that handles the automatic libraries opening/closing and the generic symbol sets handling. By using DFLAGS=-lgraphics -lintuition -lutility you are actually linking with stub libraries that require the automatic handling of shared libraries to be implemented. Either you avoid using these stubs or you implement the needed code yourself. You can take inspiration from the normal startup code.

After re-enabling lines like
 #define UtilityBase cb-&gt;UtilityBase
I was able to build the module without the stub libraries.

==Tutorials==

See here for a [http://web.archive.org/web/20111107002757/http://fishys-house-of-aros-fun.webs.com/apps/blog/show/2651598-aros-porting-guide tutorial]

SDL/MesaGL/OpenGL game frameworks. [http://msm.grumpybumpers.com/?p=64 Jumpcore Minimal]

[http://lazyfoo.net/SDL_tutorials/index.php Tutorial]

[http://www.monkeyfighter.com/tetris.html Amiga Tetris]

[http://irrlicht.sourceforge.net/downloads.html Irrlicht 3D engine]

{{BookCat}}</text>
      <sha1>euv6lzqz41mmnynx12kz0rh2gon6sla</sha1>
    </revision>
    <revision>
      <id>4668970</id>
      <parentid>4668969</parentid>
      <timestamp>2026-09-05T17:38:05Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668970</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="49296" sha1="bzg2nl2i7y1y693v8zkwuvsuojos3eo" xml:space="preserve">{{ArosNav}}


==Introduction==

Before you attempt to port a program, make sure it's API dependencies are met on AROS.
(AmigaOS (TM) 3.x C API is considered AROS native)

* Acceptable: ANSI-C/C++, [ SDL v1 but v2 wip], GTK via [http://sourceforge.net/projects/gtk-mui/ gtk-mui], [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/library Cairo] (old port), OpenGL via Gallium3D acceleration, ...
* Abit of work:  Dice C, SAS C, Aztec C, etc 
* Very difficult: PyGame, Boost, Allegro, no SDL, Gnome, KDE and/or QT4, Godot, etc.
* Impossible: Java, C#, any Windows-only source, etc.

==Compilers and tools==

Open shell - its a menu option at the top left of Wanderer (desktop). Or by using the right Win key and w (or F12 and w) within the directory with the makefile. Type in  
 sh 
to change the amiga shell into a unix shell. You can then type in ls (unix equivalent to amiga dir). Take a look [http://en.wikibooks.org/wiki/Linux_commands here] for commands.

For a single file program-name.c or program-name.cpp
 gcc -o program-name program-name.c  
or 
 g++ -o program-name program-name.cpp

To close the shell, click on the top left-hand corner to close (twice).

Other missing symbols are due to linker libraries being necessary for linking in functions that aren't in the standard C libraries. For example some source code would need added 
 -lz -lm -lpng 
to compile or even -lmui switch to link a program with a MUI gui.

use this in unix line command mode to search for 'search-item' in many .c files (*.cpp for c++, etc.)
 grep -l 'search-item' *.c

==Using CONFIGURE to create a Makefile==

Open shell - its a menu option at the top left of Wanderer (desktop). Or by using the right Win key and w within the directory with the configure and make files. Type in  
 sh 
to change the amiga shell into a unix shell.

 configure—help

to see the available options. You'll need time to examine the options and choose the right ones. 
Hints are available later on. When you configure GCC using the `configure' script, it will construct the file `Makefile' from the template file `Makefile.in'. When it does this, it will incorporate makefile fragment files from the `config' directory, named `t-TARGET'  and `x-HOST'. If these files do not exist, it means nothing needs to be added for a given target or host.

Examples...
&lt;pre&gt;
 configure prefix=/PROGDIR --build=i686 --host=i686 --disable-nls

 configure prefix=/PROGDIR --build=i386 --host=i386 --disable-nls --without-opengl --without-star --disable-sdltest

 configure LDFLAGS=&quot;-nix&quot; --prefix=/PROGDIR --build=i386 --disable-nls --without-x --without-pic 
--disable-shared GREP=bin: --enable-client=sdl --disable-server --disable-sdltest
--with-sdl-prefix=development:include/SDL
&lt;/pre&gt;

to create a Makefile but if it does not work, look at the Hints section below 

==EDITING CONFIGURE to suit AROS==

Take a look at Fishy's tutorial [http://web.archive.org/web/20111107002757/http://fishys-house-of-aros-fun.webs.com/apps/blog/show/2651598-aros-porting-guide first]

dir ../   unix moving back a directory or two

dir /    amiga equivalent

When the Makefile is created, whilst in the unix shell, type in

 make -f Makefile

to create the program...

===CREATING MAKEFILE from a blank text file===


====Generic template makefile (not to be used)====

which requires multiple copies of .c .o files


&lt;pre&gt;
CC = gcc
#CC = g++
#AS = nasm -f coff
#AR = ar
LDFLAGS = -s
FLAGS = -I. -Icpu -Iaros -Wall -march=pentium -fomit-frame-pointer
LIBS =	-lz -lm -LDevelopment:lib
#LIBS =	-lSDL_net lSDL_ttf -lSDL_mixer -lSDL_image -lpng -ljpeg -lz -lvorbisfile -logg -lSDL
#LIBS =	-lz -lm -LDevelopment:lib -lglu -lglut -lgl -lSDL_mixer -lSDL_image -lpng -ljpeg -lz -lSDL
EXE =   name
OPTS =	-O2

#

@echo &quot;Building source files...&quot;
$(CC) $(FLAGS) $(OPTS) -c src/.c -o obj/.o
$(CC) $(FLAGS) $(OPTS) -c src/.c -o obj/.o
#$(CC) $(FLAGS) $(OPTS) -c src/.cpp -o obj/.o
#$(CC) $(FLAGS) $(OPTS) -c src/.cpp -o obj/.o

@echo &quot;Making executable...&quot;
$(CC) $(LDFLAGS) $(FLAGS) -o $(EXE) obj/.o $(LIBS)

@echo &quot;Done!&quot;
&lt;/pre&gt;


Remove # from CC = g++, if g++ compiler needed. Remember to put # it in front of CC = gcc. # at the start acts as a comment line and are not processed. Similarly, remove/add # in the LIBS part to activate simple command line compiling, simple SDL compiling or openGL compiling respectively.

Replace name with the program title in EXE part.

Then add various .c (compiling with gcc) or .cpp (compiling with g++) source code you want to compile and .o also 
&lt;pre&gt;
$(CC) $(FLAGS) $(OPTS) -c src/main.c -o obj/main.o 
&lt;/pre&gt;

Finally, collect all the .o for the final line
&lt;pre&gt;
$(CC) $(LDFLAGS) $(FLAGS) -o $(EXE) obj/main.o main2.o etc.o $(LIBS)
&lt;/pre&gt;


[http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/utility MakeTools] should be looked at also.

&lt;pre&gt;
CC = gcc
CFLAGS = -O
LDFLAGS = -lSDL_image -lpng -ljpeg -lSDL_ttf -lfreetype2 -lSDL_mixer -lvorbisfile -lvorbis -logg -lSDL -lgl -lglu -lz -lstdc++ -lm

OBJS = part1.o part2.o main.o

# $(OBJS) will look above for list of .o and then use the statements below to see what to do with them

myprogram: ${OBJS}
	${CC} -o myprogram ${CFLAGS} ${OBJS} $(LDFLAGS)

#--------------------------------------------------------

part1.o: part1.c part1.h header.h
	${CC} ${CFLAGS} -c part1.c

part2.o: part2.c header.h
	${CC} ${CFLAGS} -c part2.c

main.o: main.c header.h
	${CC} ${CFLAGS} -c main.c

clean:
	rm -f myprogram ${OBJS}
        @echo &quot;all cleaned up!&quot;

&lt;/pre&gt;

====Better Makefiles====

Just use the one that suits you.

&lt;pre&gt;
#Simpler version suffices for most small-scale projects 
#DEPS is needed to recompile hellomake.c with changed hellomake.h

CC=gcc
CFLAGS=-I.
DEPS = hellomake.h

# gcc, $(CC) and rm need to be TABbed to work with make

# macro DEPS, which is the set of .h files on which the .c files depend
%.o: %.c $(DEPS)
# -o $@ compiler output into file named on the left side of hellomake: below ie hellomake 
# the $&lt; is the first item in the dependencies list #DEPS
	$(CC) -c -o $@ $&lt; $(CFLAGS)

#putting the object files--hellomake.o and hellofunc.o in dependency list
#make knows it must first compile the .c versions individually, and then build the executable hellomake

hellomake: hellomake.o hellofunc.o 
	gcc -o hellomake hellomake.o hellofunc.o -I

&lt;/pre&gt;

&lt;pre&gt;
CC = gcc
CFLAGS = -O2 -I/include 
LDFLAGS = -lSDL_image -lpng -ljpeg -lSDL_ttf -lfreetype2 -lSDL_mixer -lvorbisfile -lvorbis -logg -lSDL -lgl -lglu -lz -lstdc++ -lm

#-----------------------------------------------------------------------------

OBJS = part1.o main.o

program: $(OBJS)
	$(CC) $(OBJS) -o $@ $(LDFLAGS) 
	$(STRIP) --strip-unneeded --remove-section=.comment $@

#-----------------------------------------------------------------------------

part1.o:   part1.c part1.h 
	@echo &quot;  Compiling $*...&quot;
	@$(CC) $(CFLAGS) $*.c

main.o: main.c header.h
	@echo &quot;  Compiling $*...&quot;
        @${CC} ${CFLAGS} $*.c

clean:
      rm -f myprogram ${OBJS}
      @echo &quot;all cleaned up!&quot;

&lt;/pre&gt;

&lt;pre&gt;

# Template for a simple generic Makefile
#
CC = i386-aros-gcc
# CPP = i386-aros-gcc -E
# CXX =
# CPPFLAGS =
# CXXFLAGS =
CFLAGS = (cflags)
LDFLAGS = (ldflags)
TARGET = (final-file-name)
OBJECTS = file1.o file2.o file3.o
LINKS = file1.c file2.c file3.c
# XTRAOBJ =
#
# rules
#
all: $(TARGET)

$(TARGET): $(OBJECTS) $(XTRAOBJ)
$(CC) $(OBJECTS) $(XTRAOBJ) $(LDFLAGS) -o $(TARGET)

%.o: %.c
$(CC) $(CFLAGS) -c $&lt; -o $@
#
# eof
# Cycloid Makefile Example
# OBJ = window2.o
#
# w.exe: $(OBJ)
# $(CC) $(CFLAGS) -o $@ $^ $(ARCHIVE) $(LIB)
#
# window.o: window2.c
#
# $(CC) $(INCL) -c window2.c

&lt;/pre&gt;

&lt;pre&gt;
# .h files in an include directory 
IDIR =../include

CC=gcc
CFLAGS=-I$(IDIR)

# .o files into a obj subdirectory and some local libraries in lib directory
ODIR=obj
LDIR =../lib

macro defined for any libraries you want to include, like mui library -lMUI
LIBS=-lMUI

_DEPS = hellomake.h
DEPS = $(patsubst %,$(IDIR)/%,$(_DEPS))

_OBJ = hellomake.o hellofunc.o 
OBJ = $(patsubst %,$(ODIR)/%,$(_OBJ))

$(ODIR)/%.o: %.c $(DEPS)
	$(CC) -c -o $@ $&lt; $(CFLAGS)

hellomake: $(OBJ)
	gcc -o $@ $^ $(CFLAGS) $(LIBS)

# .PHONY rule keeps make from doing something with a file named clean 
.PHONY: clean

# cleaning up your source and object directories 
clean:
	rm -f $(ODIR)/*.o *~ core $(INCDIR)/*~

&lt;/pre&gt;

&lt;pre&gt;
#simple makefile
CC=gcc
CFLAGS=-O2 -s -DNO_INLINE_STDARG -I./api/ -I../api/ -I../modules/api/ -I../amide/modules/api/amide/
LDFLAGS=$(CFLAGS) -nostartfiles -nodefaultlibs -lamiga -lstdc.static -lgcc
EXE=plugins/test.plugin

# Objects
OBJS =	StartUp.o \
	LibInit.o \
	sasc_module.o

all: $(EXE)

clean:
	rm -f *.o $(EXE)

$(EXE): $(OBJS)
	echo Making $@..
	$(CC) -o $(EXE) $(OBJS) $(LDFLAGS)
&lt;/pre&gt;

==Hints for correcting errors==

*undefs about std:: and operators mean that you need to use or g++ , or if you use gcc, then add to -lstdc++ 
*undefs about sdl_wav mean -lsdl_mixer, 
*undefs about AROSMesa mean -lgl, 

Link order is important, so you can't for example firstly do -lgl, and then -lsdl. As sdl wants gl, you will need to do -lsdl -lgl, and the same for all the other libs : include one after another when undefs happens.

 -lSDL_image -lpng -ljpeg -lSDL_ttf -lfreetype2 -lSDL_mixer -lvorbisfile -lvorbis -logg -lSDL -lgl -lglu -lz -lstdc++ -lm

There are undefined symbols in 'sasc.module':
__PROGRAM_ENTRIES__symbol_set_handler_missing
__LIBS__symbol_set_handler_missing

remove the -nostartfiles argument from command line 
the missing symbols are part of AROS automatic startup handling. Possibly manually adding -llibinit could fix the missing symbols.


add -nodefaultlibs like this:

LINK := $(OPTIMIZE) -s -nostartfiles -nodefaultlibs


should remove all automatically added libraries and now you will have to add them manually 

$(CC) $(LINK) -o $@ $(O_FILES) -lamiga -lstdc.static -lgcc

&lt;pre&gt;
#simple makefile
CC=gcc
CFLAGS=-O2 -s -DNO_INLINE_STDARG -I./api/ -I../api/ -I../modules/api/ -I../amide/modules/api/amide/
LDFLAGS=$(CFLAGS) -nostartfiles -nodefaultlibs -lamiga -lstdc.static -lgcc
EXE=plugins/test.plugin

# Objects
OBJS =	StartUp.o \
	LibInit.o \
	sasc_module.o

all: $(EXE)

clean:
	rm -f *.o $(EXE)

$(EXE): $(OBJS)
	echo Making $@..
	$(CC) -o $(EXE) $(OBJS) $(LDFLAGS)
&lt;/pre&gt;


and LoadModules function calls that function from main.c, case of AROS it is best to use portable macros to make these calls 

&lt;pre&gt;
mod_class =AROS_LC0(void *, AmIDE_API_GetClass,
        struct Library *, (AmIDE_API_Base), 5, AmIDE_API    );
&lt;/pre&gt;

#include &lt;aros/libcall.h&gt;


Additionally, most AROS code depends on the library bases being opened automatically so you may need to add a link library, libauto (-lauto). Some systems (so it's down to the compiler to provide it) don't have working libauto in which case you need to open the library bases manually.

AROS OS 64Bit GCC 10+ enforces strict checks on void variables so gcc output-&gt; error: variable or field __ret declared void.
AROS_LC0NR variant of macros to handle void return type (NR stands for No-Return) with more [http://www.aros.org/es/documentation/developers/app-dev/portable.html here] 

[http://aros.sourceforge.net/documentation/developers/porting.php Hints can be found here] 
Be warned that these links apply to using Linux to compile code and not native but may be useful.


&lt;pre&gt;
CONFIGURE ERRORS

Error    : no acceptable C compiler found in $PATH
Solution : add CC=gcc or CC=g++ after configure

Error    : no acceptable grep could be found in /Development/bin:
Solution : add GREP=bin: to configure line

Error    : gtk-mui library sequence
Solution : gcc -o test addbutton.c\ -lglib-2.0 -lgtlayout -lgthread-2.0 -lgmodule-2.0 -lgobject-2.0 -lgtk-mui -lglib-2.o -liconv -lmui -lthread

Error    : VARIABLE not within scope
Solution : add headers like...  #include &lt;libraries/mui.h&gt; #include &lt;proto/muimaster.h&gt; or #include &lt;string.h&gt; etc

Error    : malloc.h no such file or directory 
Solution : malloc is contained within &lt;aros/stdlib.h&gt;

Error    : SDL.h no such file or directory
Solution : #include SDL/SDL.h needed at top of .c file or -IDevelopment:include/SDL to the command line

Error    : 
Solution :

Error    : IMG_Load in -lSDL_image ... cannot find libSDL_image
Solution : ??

Error    : pow in -lm - 'case' unmatched - math.library (-lm) appears broken
Solution : ??

Error    : 
Solution :

Error    : 
Solution :

MAKE ERRORS

Error    : *** missing separator.  Stop. 
Solution : Make commands like gcc $(CC) or rm need to be TABbed in and not use spaces

Error    : 
Solution :

Error    : 
Solution :

Error    : 
Solution :

COMPILING ERRORS

Error    : expected '=' ';' &quot;asm&quot; or '__attribute__' before '{'
Solution : look at previous lines for missing/extra ; (like in defines) or missing } or forgot to #include something.h. Use gcc -E to check

Error    : request for member 'something' in function not a structure or union
Solution : using b.x = 12 (usually arrays); when it should be b-&gt;x (usually structs) or (*b).x, .h needed,

Error    : 'something' undeclared (first use in this function)
Solution : 'something' been declared at start of function, .h needed or link library needed -lmui etc.,

Error    : there are undefined symbols in program 
Solution : /* around these symbols' */ until you work out if they are needed or can be deleted

Error    : there are undefined symbols in &lt;program-name&gt; or memcpy strndup first 
Solution : linker library not included -lz -lSDL or -lGL etc or &lt;string.h&gt;

Error    : expected specifier-qualifier list before 'USHORT'
Solution : change all references of USHORT into UWORD (SHORT into WORD)

Error    : expected declaration specifiers or '...' before 'USHORT' 
Solution : replace USHORT with UWORD (SHORT into WORD)

Error    : field 'name' has incomplete type 
Solution :

Error    : expected ')' before 'type' 
Solution :

Error    : invalid conversion from 'ULONG*' to 'IPTR*'
Solution : most amiga like OS's return ULONG values or use ULONG TAGS but 64bit AROS needs IPTR used for compatibility

Error    : dereferencing pointer to incomplete type 
Solution :

Error    : If crackly break-up noise found in SDL sound 
Solution : try to find where the number of samples for the buffer is set in the source and increase it (double it at least). This solves many sound issues with SDL programs. The buffer was set to 1024, now set it to 4096.

Error    : initializer element is not constant around TAG_DONE);
Solution : header(s) &lt;utility.h&gt; and &lt;proto/utility.h&gt; need to be added

Error    : no i386-sdl-config
Solution : use --build=i686 instead of --build=i386

Error    : functions not found at final linking: SDL_CondWait, SDL_CondSignal, SDL_CreateCond
Solution : find them in the SDL_cond_aros.c file in the cdxlplay-sdl source http://www.a500.org/downloads/video/

Error    : crash glutGet((GLenum)GLUT_ELAPSED_TIME);
Solution : The glutInit function is needed, replace with by SDL_GetTicks()

Error    : undefined symbols: recv, connect, inet_pton, socket, select, send, inet_ntoa
Solution : LDFLAGS : -lSDL_net -lSDL with #include &lt;proto/bsdsocket.h&gt; (or &lt;proto/socket.h&gt;) in all files using SDL_net

Error    : SDL is not built with CDROM support.
Solution : Look for SDL_INIT. It can look something like this:
             if( SDL_Init( SDL_INIT_EVERYTHING ) == -1 )
             change it to:
             if ( SDL_Init(SDL_INIT_VIDEO|SDL_INIT_TIMER|SDL_INIT_AUDIO|SDL_INIT_JOYSTICK ) == -1 )
           That includes all the init routines available in SDL, minus the CD one.

Error    : Video mode set failed: OpenGL support not configured
Solution : 'sdl-config --libs' is fine for most SDL uses, but with GL it needs to be replaced with &quot;-lgl&quot;

Error    : 
Solution :

Error    : 
Solution :

RUN TIME ERRORS

Error    : 
Solution :

Error    : 
Solution :

Error    : 
Solution :

Error    : 
Solution :

Error    : 
Solution :

Delinting (removing warning messages)

64bit compatibility 
-        MUIA_Application_Copyright, _(MSG_AppCopyright),
+        MUIA_Application_Copyright, (IPTR)_(MSG_AppCopyright),

-        io-&gt;io_Unit   = (struct Unit *)unitnum;
+        io-&gt;io_Unit   = (struct Unit *)(IPTR)unitnum;


Clean up
-    ULONG signals;
+    ULONG signals = 0;

-    while((t = LibNextTagItem(&amp;tagList)))
+    while((t = LibNextTagItem((struct TagItem **)&amp;tagList)))

-       while ((tag = LibNextTagItem(&amp;msg)))
+       while ((tag = LibNextTagItem((struct TagItem **)&amp;msg)))

-    const struct TagItem *tstate = msg-&gt;ops_AttrList;
-    struct TagItem *tag;
+    struct TagItem *tag, *tstate = msg-&gt;ops_AttrList;

-        sprintf(buf, &quot;SYS/printer%d.prefs&quot;, unit);
+        sprintf(buf, &quot;SYS/printer%d.prefs&quot;, (int)unit);

-    STRPTR _return = NULL;
+    CONST_STRPTR _return = NULL;

-    return (CONST_STRPTR)_return;
+    return _return;

&lt;/pre&gt;

==Hints: Porting software from...==


===AmigaOS===

The right form of the main() function is
&lt;pre&gt;
int main(void)
{
...
return retval;
}

or

int main(int argc, char **argv)
{
...
return retval;
}
&lt;/pre&gt;

(Old code has often &quot;void main()&quot; or no return type at all)

For retval you can either use 0, EXIT_SUCCESS or EXIT_FAILURE (ANSI-C) or ADOS return codes which I don't know off-hand.

First turn anything that ending in _proto.h 
&lt;pre&gt;
#include &lt;dos/dos_proto.h&gt;
to
#include &lt;proto/dos.h&gt;
&lt;/pre&gt;
and if you want it more portable, then try
&lt;pre&gt;
#ifdef AROS
#include &lt;proto/dos.h&gt;
#else
#include &lt;dos/dos_proto.h&gt;
#endif
&lt;/pre&gt;

Include function prototypes for shared libraries from proto
e.g. #include &lt;proto/graphics.h&gt; instead of #include &lt;clib/graphics_protos.h&gt;

If the compiler complains about wrong type in a line like
 struct Library *GfxBase
you have to look up the right type in the header, e.g. in includes/proto/graphics.h

 #include &lt;proto/library_name.h&gt;

(replacing with correct name) should pull in the necessary info for automatic opening/closing of CORE libraries to work with basic applications which are written as DOS and Workbench/Wanderer launched processes. Others like mui have to be specified (-lmui in the gcc command line).

It looks like you are still including from clib. You either have to include from proto or you have to link with -lexec -lgadtools, etc.

There are undefined symbols in 'inctst':
U AllocMem
U FreeMem

Adding -lexec removed the errors.

&lt;pre&gt;
There are undefined symbols in 'a.out':
SetFont
CloseFont
OpenFont 
&lt;/pre&gt;

try -lgraphics or #include &lt;proto/graphics.h&gt; or #include &lt;defines/graphics.h&gt; or #include &lt;clib/graphics_protos.h&gt;

&lt;pre&gt;
Include sys/types.h before netinet/ip.h
Include &lt;netdb.h&gt; first before rest of your network includes 
&lt;/pre&gt;

Most AROS C/C++ Compilers can open and close the libraries for you as part of the startup code. As long as you have the protos included in the headers and the appropriate compiler options specified, the compiler will take care of opening any used libraries for you.

The library header source is in principle like AOS 68k too, with Resident struct, functable and so on. Except AROS has its own set of macros for functions which get parameters in registers. The AROS_LH#? and AROS_UFH#? stuff. You should be able to use contrib/mui/classes/nlist/commonaros/mccheader.c from AROS contrib sources as a hint.

But always remember, that coding for AROS is not coding for m68k Amiga. Much is different here and coding AROS in C means searching hundreds of include files for macros. And AROS source code is partly useless for an external newbie developer, as AROS has a deeply integrated build system which hides important parts from the implementing developers, e.g. a shared library consists only of its methods, the rest (Romtag, Jumptable etc.) is hidden in the AROS build system.


wbstart.library isn't ported indeed but its usage is depreciated and you are advised to convert its calls to use workbench.library/OpenWorkbenchObject() (which should be easy).

A temporary quick trick is to use CLI callings on C:Open which will launch programs using Workbench (using this very function). It can even be used with arguments which are passed as workbench arguments (ie like multi-clicked files).

====Programming languages====

As long as no assembler code is being used in the program, compiling a C program written for plain AmigaOS up to version 3.1 should be possible on AROS without any changes to the source code. (That presumes your AROS is using a 32bit big-endian CPU, like the original Amiga computer.) (Please note that '''AROS is still beta and incomplete''', and might lack some functions from AmigaOS API. See [[Aros/Developer/Docs#Status of AROS implementation|Status of AROS implementation]] for more on this.)

====Data types and sizes / little endian / big endian====

Some of the first things to consider is the actual size of your C data types, and in your uses of binary files (IFF for example) paying attention to reading and writing with portability to 64bit and little-endian CPUs as well as the classic mc680x0 or powerpc cpus used by Amiga OS.

* Warning signs is casting between char * and WORD/LONG/short/int etc., or any kind of pointer arithmetic, as well as any functions that read/write binary file formats (if they read character by character and/or does things similar to what I mentioned above, they are likely to be ok, if they read a chunk of memory in and treat it as a struct immediately then it will almost certainly fail).
* Endianness issues need to be fixed and there are a lot of them (reading/writing binary files, writing data into graphics frame buffers). Also network stack, file system, hardware. Pretty much any time you have to deal with external data, you have to worry about endianness. There are C #define macros to handle writing/reading the correct endianness and flipping the ordering when necessary.
* all LONG/ULONG/APTRs need to be checked if they need to be replaced by IPTR (e.g. relying on TagLists)

[we should probably have a chart showing sizes/endian used by Manx/sas/dice C on a mc68000/68030 vs today's PPC/i386/x86_64 AROS options here along with some GCC source code to show how to read/write binary files correctly under AROS running on differing endian CPUs]

====Screens====

Amiga chipset-graphics-based screens were generally done in a planar format 16/32-colors max for ECS hires/lores modes respectively and 256-colors for AGA.

[a chart of common amiga screen modes should go here]

Methods that worked well for the relatively low-resolution planar Amiga displays may be suboptimal for chunky and true color screens that are common today.

[pointer to examples should go here]

Amiga screens could be of differing resolution, which could be dragged up and down to reveal another, so some applications were written with differing resolution screens, say for a control panel at one resolution and another for the &quot;display&quot; visible at the same time stacked vertically. This may not make sense with today's chip sets or wide-screen displays. Opening multiple screens that vary in scan rate can confuse displays (monitors or projectors) that might take several seconds &quot;calibrating&quot; every time the user decides to change which public or private application screen they want to view. Defaulting to the user's preference for Wanderer (workbench) for screen mode is probably better than having a predefined mode hard-coded into your application.

====Fonts====

AmigaOS 3.1 also shipped with some nice disk fonts that are not currently available under AROS, so you should be careful about having any diskfont hard-coded as a default into your program. The ROM font &quot;topaz&quot; should be ok.

AROS fonts (as of 2010-03-10):
*arial.font
*dejavusansbold.font
*dejavusansboldoblique.font
*dejavusansbook.font
*dejavusanscondensedbold.font
*dejavusanscondensedboldobl.font
*dejavusanscondensedcondens.font
*dejavusanscondensedoblique.font
*dejavusansextralight.font
*dejavusansmonobold.font
*dejavusansmonoboldoblique.font
*dejavusansmonobook.font
*dejavusansmonooblique.font
*dejavusansoblique.font
*dejavuserifbold.font
*dejavuserifboldoblique.font
*dejavuserifbook.font
*dejavuserifcondensedbold.font
*dejavuserifcondensedboldob.font
*dejavuserifcondensedconden.font
*dejavuserifcondensedobliqu.font
*dejavuserifoblique.font
*fixed.font
*stop.font
*ttcourier.font
*Vera Mono Bold.font
*Vera Mono Bold Italic.font
*Vera Mono.font
*Vera Mono Italic.font
*Vera Sans Bold.font
*Vera Sans Bold Italic.font
*Vera Sans.font
*Vera Sans Italic.font
*Vera Serif Bold.font
*Vera Serif.font
*XEN.font

====GUI Toolkits====

=====Gadtools=====

The order of the fields in struct Node which is currently different than on AOS (will be changed in ABI V1).

struct Node has currently the following order:

&lt;pre&gt;
struct Node
{
    struct Node * ln_Succ,
        * ln_Pred;
    char    * ln_Name;
    UBYTE      ln_Type;
    BYTE      ln_Pri;
}; 
&lt;/pre&gt;

=====MUI=====

'''MUI''' - AROS' preferred GUI toolkit is Zune, a reimplementation of MUI 3.x, thus MUI 3.x code will work unchanged under AROS. MUI 4.x will need adapting or wait for the following [http://www.power2people.org/projects/profile/54 bounty] to be started.

=====ClassAct=====

'''ReAction/ClassAct''', a GUI toolkit for AmigaOS, is not available for AROS. It has been made part of AmigaOS 3.5 and higher. Programs that use ReAction might need considerable rework, preferably to use Zune (or: MUI), AROS' GUI toolkit.

=====BGui=====

'''bgui''' is available as part of the &quot;contrib&quot; archive, thus included in all current AROS binary distributions.

[We could use a chart comparing gui options for developers here.]

====C/C++ Compilers====

GCC/G++ is the primary C compiler supplied with AROS. Amiga programs making use of other compilers' (SAS/C, Maxon C, ...) specific functionality might need some rework.
You'll probably want to write makefiles that can run either hosted or native, so any AROS user can get them compiled and running on their machine. In a hosted environment the shell will most likely use UNIX semantics like cp==COPY ../==parent directory, and all file names will be case sensitive for your makefile and inside your C source code files (example: #include &quot;myFile.h&quot; != #include &quot;MyFile.H&quot;). Under AROS the makefile may use Amiga shell command semantics (copy #? progdir:prefs)or it may be using a UNIX shell ported to AROS, and the AROS environment, and like AmigaOS 3.1 may not care about case sensitivity of file names.

We can't use the SLOWSTACKTAGS macros for getting ULONG values from a variadic list.

===== SAS Lattice C Compiler=====

SAS/C was one of the more popular compiler packages back when AmigaOS 3.1 was released, it supported various keywords such as __chip for using chipram, and CPU-related register arguments that the current AROS GCC does not.

The makefiles will have to be translated from SMAKE to GNU Make and some of the headers will have to be translated from SC to GCC.

Pragmas were used on ancient C compilers like SASC. Include from &quot;proto&quot;, e.g. #include &lt;proto/workbench.h&gt;. Look if there are headers which include from &quot;clib&quot;. Change them to &quot;proto&quot;, too.

You can ignore warnings like &quot;suggested parentheses...&quot; or incompatible pointer types.

Some types and names of defines have changed (SHORT/USHORT -&gt; WORD/UWORD).

 -linput -lutility -lintuition -lrexxsyslib -lconsole -lgraphics -ldos -lexec

strmfp, stcgfe, stcgfp, stcgfn and stci_d are SAS/C / Lattice function that do not exist under gcc. They have to be reimplemented.

tolower and toupper was found once I've included ctype.h in the source code.
Sometimes missing symbols come from missing include files. Those are macros like toupper—not real functions, and the C preprocessor needs the include definition for the macro.

If you want your characters to be unsigned you need to put unsigned into the variable type. If you want them to be signed, put signed in the variable type. If you don't put either, you may get unexpected results.

Sometimes you need wrappers for functions which aren't part of ANSI C.

SAS/C allowed to use a type before it was defined =&gt; change the order or use forward declaration.

Use AROS macros for Hook functions as explained here:
http://aros.sourceforge.net/documentation/developers/app-dev/portable.php#hooks

There might be more if you are porting system software (libraries, interrupts etc.)
Just start and try to find the reason for warnings and errors.

Generally when porting sources, if a header doesn't exist in AROS, wrap it with an #if or #ifndef statement and see what symbols, structure definitions, etc. aren't found. Then you can look through the AROS includes to see if the missing symbols, etc. are implemented in another place, or if you have to make your own compatible include file with those defined.

For libraries you might want to look at the AROS source-tree to see how others have done it using things like [http://aminet.net/package/dev/gcc/sfdc sfdc], genmodule, etc.

* SAS/C included a ton of non-standard functions in its C library. Alternative versions of these can generally be found online, and for example YAM includes some of them in their sources, depending on license working around this is easy (none of these functions are big/difficult to re-implement if needed).
* SAS/C is very liberal in some of the things it accepts. This causes problems particularly for vbcc (not so relevant for AROS) but some things also for gcc, particularly in terms of type coercion and (lack) of forward declarations.
* SAS/C has a multitude of extensions targeting AmigaOS, such as non-standard 68k focused register declarations. These must either be removed or worked around by defining preprocessor macros that expand to nothing or a suitable replacement.
* The SAS/C smakefiles are a totally non-standard syntax.
* The general caveats of AmigaOS vs. AROS include files apply - many paths can be expected to be different.
* there might be endian issues
* you'll get a lot of compiler warnings. Some of them are harmless (e.g. &quot;parenthesis suggested ...&quot;). Others are dangerous (e.g. &quot;variable xxx may be undefined&quot;)
* for some specials like callback hooks you'll have to use AROS macros.


* Use texteditor or some tool to replace all &quot;ULONG&quot; with &quot;IPTR&quot; and &quot;LONG&quot; with &quot;SIPTR&quot; in the sources.
* Fix (change IPTR/SIPTR back to ULONG/LONG) the few places which really rely on ULONG/LONG being exactly 32 bit. That's for things like pixel (ARGB) buffers, structs written/read to disk, colormaps, but probably little else.


This is the [http://aros-exec.org/modules/newbb/viewtopic.php?start=30&amp;topic_id=5705&amp;viewmode=flat&amp;order=ASC&amp;type=&amp;mode=0 code] that I use in diskimage.device for converting a BSTR to a CSTR 
&lt;pre&gt;
LONG CopyStringBSTRToC (BSTR src, STRPTR dst, ULONG dst_size) {
#ifdef __AROS__
    STRPTR ptr = AROS_BSTR_ADDR(src);
    ULONG ln = AROS_BSTR_strlen(src);
#else
    UBYTE *ptr = BADDR(src);
    ULONG ln = *ptr++;
#endif
    if (ln &gt; (dst_size-1)) ln = dst_size-1;
    memcpy(dst, ptr, ln);
    dst[ln] = 0;
    return ln;
}
&lt;/pre&gt;

Some blankers{{typo help inline|reason=similar to blinkers|date=October 2022}} are missing the symbol &quot;custom&quot;. They have (as documented in the OS3.9 RKM) &quot;extern struct Custom custom;&quot;. 
'Custom' is a struct that maps the m68k Amiga AGA/OCS/ECS registers. Only build those for amiga-m68k, and you'll be fine.

=====Maxon Hisoft C=====

=====Dice C=====

=====North C=====

* RAWKEY: replaced with IDCMP_RAWKEY: 
* ModifyIDCMP(win,FLAGSON) replace with ?

===MorphOS===

====Assemblers/ Disassemblers====

ADis, which reads binaries into memory hunk by hunk to disassemble them, and then just treats it as an array of short. The &quot;right&quot; way would be to treat it as a char *, and do (arr[0] &lt;&lt; 8) + arr[1]. I wanted to use it to cross-disassemble M68k programs, but gave up and went with Ira instead because it was so pervasive.

===Linux Console Apps===

On AmigaOS this is done by libc on every I/O operation. Just AROS libs lacks this. 
Resources allocated by libc (malloc()ed memory, fopen() ed files, etc.) are safely reclaimed at exit(). libc tracks this internally. If your program additionally uses some AmigaOS API, it usually installs exit handler (I don't remebmer how), or disables Ctrl-C checking by redefining __chkabort() function.

You have to explicitly check for it on AROS (and AmigaOS). The reason for this is that there's no safe way for the OS to kill an app and reclaim all resources on AmigaOS and derivatives (since an app can have &quot;handed off&quot; memory and other resources to other tasks).

This is an example from the autodocs for SetSignal:

&lt;pre&gt;
#include &lt;libraries/dos.h&gt;

/* Check &amp; clear CTRL_C signal */
if(SetSignal(0L,SIGBREAKF_CTRL_C) &amp; SIGBREAKF_CTRL_C)
{ 
printf(&quot;CTRL-C pressed!n&quot;);
}
&lt;/pre&gt;

It is compiler dependent. It's safer to just do the SetSignal()-based check.


If you want a shared library, recommend getting linux-hosted aros building (use the gimmearos.sh script) and then look at the other library sources found in AROS/workbench/libs for examples of how its done.

If it were just a linker library, you can just compile the .c files with -fno-stack-protector (needed under aros-sdk cross compiler under linux, native aros gcc might not need that), etc. and join the .o files into a lib-yournamehere.a file with ar and ranlib them.

===SDL===

SDL_image may need -ljpeg -lpng -lz

SDL_mixer needs -lSDL_mixer -lvorbisfile -lvorbis -logg (in this order)


First thing to test with SDL sound under AROS is to increase the buffer. In all applications had needed this to obtain good sound output.

In most cases it would certainly mean that you have to increase the value of SYSSND_MIXSAMPLES. Usually multiplying this value by 2 or 4 gives good results.

You should also check the value of the obtained structure. It is not sure that AROS supports AUDIO_U8 and you might have reverted to AUDIO_U16. In this case sound will of course be distorted.

from [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=2533&amp;forum=2&amp;post_id=45301#forumpost45301 here]

Further tests with buffers using code from [http://www.kekkai.org/roger/sdl/mixer/ here], and this is the result I've noted:

&quot;a quick test compiling with 1024, 2048 or 4096 gave interesting results: 1024 - sounds are more responsive to key-events but if you quickly move the &quot;game-window&quot; around the screen you can hear sound glitches. 2048 - No big difference noticed in responsiveness and now no glitches moving the window around, anyway the fx-sound sample plays with some hiss-click glitches. 4096 - No hiss-click and no glitches moving the window BUT you can see that the responsiveness is decreased.

Trying this code then with original xRick 8bit samples gives good sound results, and even using 1024 bytes buffer the sound doesn't glitch when moving window&quot;

Seems to me that buffer depends a lot on responsiveness you need, overall game load and also what kind of sound samples you're using (of course the lower is the bit-encoding and frequency, the smaller you can use as buffer).


SDL_GetTicks just disable

 m_fLastTime = float(SDL_GetTicks())/1000;

in 2 places of sdlapp.cpp and add your own code at the end:

&lt;pre&gt;
    Ellapsed_Time = SDL_GetTicks() - Last_Time;
    if (Ellapsed_Time &lt; 20) /* 20 ms target =&gt; 50FPS */
    {
    SDL_Delay(20 - Ellapsed_Time);
    }
&lt;/pre&gt;

Maybe SDL_GetTicks works a bit wrong by some reasons in aros's SDL, right ? (because if the same code works fast on os4/mos/win32/anything-else), then it mean that something wrong with SDL_GetTicks then .. 
PS : SDL_GetTicks() isn't causing any trouble, its a basic SDL function that is used in almost all SDL applications.

 int CSDLApplication::Run() in sdlapp.cpp
and
 bool CMySDLApplication::FrameMove() in Armygaem.cpp

In initial-code Render3DEnvironment is called continuously and only FrameMove is updated at 50fps, Render() and SDL_GL_SwapBuffers() are called even if nothing has moved.
Calling the render() functions and SDL_GL_SwapBuffers(), too often is for me the root cause. A correction to OpenGL implementation would only be a safeguard to prevent stupid application from crashing or slowing down the system.

crash on exit is certainly due to the application not freeing any resources before exiting.

===Writing ROM-able code===

Code in AROS modules should be written in a way that makes it suitable for embedding into a ROM, FlashRAM or other kinds read-only memory. The following coding style rules are meant to make it possible. Of course they apply to all Kickstart modules and to code that may be made resident, shared or linked to other modules.
	 
ROM modules must have no .data and .bss sections. Basically, we need to get rid of all non-const global data. The real Amiga Kickstart proves that it's both possible and easy to achieve this. If you encounter an external variable (static or not) that is modified by the code, try to get rid of it or move it into the base of the library/device (or in the device node of your handler or in the userdata of your class).
	 
The above applies to library bases as well. If you are writing a library, put the bases of other libraries into your own library base structure. Boopsi classes can store library bases in their class private data.
	 
Try to set the static and const attributes to all your global data. You can also use the CONST_STRPTR and CONST_APTR types defined in &lt;exec/types.h&gt;. Using static const allows the compiler to move data into the .text (AKA code) segment. If you need to pass these globals to another function, try to change its prototype to use const too.

===Hooks and SDI===


A hook is a custom function you write in order to be able to handle a specific situation that arises from intercepting the main code (like processing a message). The function must be designed to accept three arguments, whose order and type is given.

* the first parameter (A0) contains the pointer to your hook, not to your window
* the 2nd Parameter points to the Object which causes this action, this isn´t your window but it´s the Object which was pressed (it´s always the Object which was connected to the Hook (=1st Parameter of DoMethod) 
* then give 5 as number of Parameters for MUIM_CallHook, but´s 4 (=number of all Parameters in DoMethod after the Count Parameter)

&lt;pre&gt;
AROS_UFH3S
(
void,
MyHookFunction,
AROS_UFHA(struct Hook * , hook, A0),
AROS_UFHA(Object * , obj, A2),
AROS_UFHA(ULONG * , params, A1)
)
&lt;/pre&gt;

params is an array but IPTR should be correct. Then you can access your parameters...

&lt;pre&gt;
app = (Object *) *params++;
window2 = (Object *) params++;
&lt;/pre&gt;


&lt;pre&gt;
The important thing about hook functions is that the parameters must be given in the order A0, A2, A1.
And not to leave out parameters even if they are unused by the hook function.

For initial quick&amp;dirty ports one can even simply defines things like
&quot;__saveds&quot;, &quot;__asm&quot;, &quot;__regargs&quot;, &quot;__stdargs&quot;, &quot;register ...&quot; to nothing.

For library functions it's the same (with library base as last param).

InitLib: libbase(d0), seglist(a0), sysbase(a6)
OpenLib: version(d0), libbase(a6)
CloseLib: libbase(a6)
ExpungeLib: libbase(d0), libbase(a6)

OpenDev: ioreq(A1), unitnum(d0), flags(d1), devbase(a6)
CloseDev: ioreq(a1), devbase(a6)
&lt;/pre&gt;

see [http://utilitybase.com/forum/index.php?action=vthread&amp;forum=3&amp;topic=1495 here]

The AROS asm call and lib call macros require param type (like &quot;struct Hook *&quot;) and param (like &quot;myhook&quot;) to be passed in two different arguments. Not in a single one.

Converting is easy. Adding some &quot;AROS_&quot; prefix plus some commas. Additionally in the hook functions and dispatcher functions &quot;HOOK_INIT&quot; / &quot;HOOK_EXIT&quot; / &quot;DISPATCHER_INIT&quot; / &quot;DISPATCHER_EXIT&quot; must be used (in case of AROS mapping to AROS_USERFUNC_INIT/AROS_USERFUNC_EXIT).

To force procedure parameters to use registers (like a0) in GCC

Since C calling convention on some machines (like 68k or x86) means params are passed on stack your C function must have params in correct order (Hook, object, msg) and not leave out params if they are unused by the function especially if it's the middle param (object).

 ULONG hook_function(REG(a0, struct Hook *hook), REG(a2, APTR object), REG(a1, APTR message))

In short when using HookEntry you initialize hooks like this:

&lt;pre&gt;
STATIC ULONG hookfunc(struct Hook *hook, APTR obj, APTR msg) 
{ 
/* ... *// 
}

#if defined(__amigaos4__) 
hook-&gt;h_Entry = hookfunc; 
#else 
hook-&gt;h_Entry = &amp;HookEntry; 
hook-&gt;h_SubEntry = hookfunc 
#endif 
&lt;/pre&gt;

If you are not using SDI headers this is the most universal method which works on OS3, OS4, AROS and MorphOS with every compiler and architecture.

Those dispatchers are usually taken as argument for MUI_CreateCustomClass(), which has:

&lt;pre&gt;
#if defined(__MAXON__) || defined(__amigaos4__)
    cl-&gt;cl_Dispatcher.h_Entry    = (HOOKFUNC)dispatcher;
#else
    cl-&gt;cl_Dispatcher.h_Entry    = (HOOKFUNC)metaDispatcher;
    cl-&gt;cl_Dispatcher.h_SubEntry = (HOOKFUNC)dispatcher;
#endif
&lt;/pre&gt;

metaDispatcher:

&lt;pre&gt;
#ifdef __AROS__
AROS_UFH3(IPTR, metaDispatcher,
    AROS_UFHA(struct IClass  *, cl,  A0),
    AROS_UFHA(Object *, obj, A2),
    AROS_UFHA(Msg     , msg, A1))
{
    AROS_USERFUNC_INIT
   
    return AROS_UFC4(IPTR, cl-&gt;cl_Dispatcher.h_SubEntry,
        AROS_UFPA(Class  *, cl,  A0),
        AROS_UFPA(Object *, obj, A2),
        AROS_UFPA(Msg     , msg, A1),
        AROS_UFPA(APTR    , cl-&gt;cl_Dispatcher.h_Data, A6)
    );

    AROS_USERFUNC_EXIT
}
&lt;/pre&gt;

What confuses me is that our own macros have registers:

&lt;pre&gt;
#define BOOPSI_DISPATCHER(rettype,name,cl,obj,msg) \
    AROS_UFH3(SAVEDS rettype, name,\
        AROS_UFHA(Class  *, cl,  A0),\
        AROS_UFHA(Object *, obj, A2),\
        AROS_UFHA(Msg     , msg, A1)) {AROS_USERFUNC_INIT
&lt;/pre&gt;

Maybe there is a difference between MUI and BOOPSI when it comes to dispatchers and SDI DISPATCHER can only be used for MUI.

AROS's MUI_CreateCustomClass() moves the dispatcher to h_SubEntry and uses something like HookEntry for h_Entry. There we don't have to care about registers.

BTW: SDI's hook macros *are* wrong for AROS.

&lt;pre&gt;
HOOKPROTONHNO(TestFunc, void, int *param)
{
    puts(&quot;Foobar&quot;);
}

MakeHook(TestHook, TestFunc);
&lt;/pre&gt;
expands to:
&lt;pre&gt;
static void TestFunc(__attribute__((unused)) struct Hook *_hook,
__attribute__((unused)) APTR _obj, int *param)
{
    puts(&quot;Foobar&quot;);
}

struct Hook TestHook = {{0L, 0L}, (HOOKFUNC)TestFunc, NULL, 0L};
&lt;/pre&gt;

That works only by accident on i386-AROS (because of stack parameters).
But there I *know* how to fix it and will soon send an update to you.

&lt;pre&gt;
#elif __AROS__

  #define MakeHook(hookname, funcname) struct Hook hookname = {{NULL, NULL}, \
    (HOOKFUNC)HookEntry, (HOOKFUNC)funcname, NULL}
  #define MakeHookWithData(hookname, funcname, data) struct Hook hookname =  \
    {{NULL, NULL}, (HOOKFUNC)HookEntry, (HOOKFUNC)funcname, (APTR)data}
  #define MakeStaticHook(hookname, funcname) static struct Hook hookname =   \
    {{NULL, NULL}, (HOOKFUNC)HookEntry, (HOOKFUNC)funcname, NULL}
  #define ENTRY(func) (APTR)func
  #define DISPATCHERPROTO(name) SAVEDS ASM IPTR name(REG(a0,                 \
    struct IClass * cl), REG(a2, Object * obj), REG(a1, Msg msg))
  #define DISPATCHER(name) DISPATCHERPROTO(name)
  #define SDISPATCHER(name) static DISPATCHERPROTO(name)
&lt;/pre&gt;

Difference is that funcname is moved to h_SubEntry.
Problem are the dispatcher macros. They'll currently only work with MUI_CreateCustomClass(). If I define them like our BOOPSI macros I have a new problem: what happens if I define a function with register macros
*AND* use HookEntry in h_Entry and the function in h_SubEntry?

BTW: in SDI_compiler.h there is:
&lt;pre&gt;
  /* we have to distinguish between AmigaOS4 and MorphOS */
  #if defined(_M68000) || defined(__M68000) || defined(__mc68000)
    #define REG(reg,arg) arg __asm(#reg)
    #define LREG(reg,arg) register REG(reg,arg)
  #else
    #define REG(reg,arg) arg
    #define SAVEDS
&lt;/pre&gt;

C++ is much more strict on types than C, this is the root of the problem. Absolutely everything should be casted, implicit conversions are not allowed at all. P.S. And casting is considered an extremely bad coding style IIRC...

Those who want to develop AROS API in C++ should update their headers from a current SDK.

HOOKFUNC looks now like this in include/utility/hooks.h:
 typedef IPTR (*HOOKFUNC)();

The prototypes have been included in &quot;extern C&quot; blocks, so that problems like this should be [http://aros-exec.org/modules/newbb/viewtopic.php?post_id=37123#forumpost37123 gone]

===Casts===

Casts simply put... casting through pointers, bad... casting through a union, [http://cellperformance.beyond3d.com/articles/2006/06/understanding-strict-aliasing.html good]*. (*exceptions apply) Hopefully someone can correct me if I'm wrong, but the main rule of thumb for avoiding these problems seems to be to not have two pointer variables in the same function that point to the same memory, but are of different type.

It's actually a little more subtle than this. They can point to different types, but not when the types do not contain sub-sets of the others.

i.e.

&lt;pre&gt;

struct Foo {
struct MinNode Node;
};
&lt;/pre&gt;

- any cast from struct Foo * to struct MinNode * is ok ...
but:
&lt;pre&gt;
struct Foo {
struct Foo *next;
struct Foo *prev;
};
&lt;/pre&gt;

- now casts from 'foo' to 'minnode' are not ok ... and worse, can be silently discarded (how that is considered polite behaviour I do not know). (and by extension, casting from List to Node are right out).

I would argue that this is actually a different language - it is no longer 'C', as such, and although the spec (as far as I have been able to ascertain) actually specifies this it has never been implemented in such a way until now. It is there to provide additional optimisation opportunities ... although the whole 'we'll just silently drop code that is otherwise quite obvious' thing is rather nasty.

The CellPerformance stuff really nails it all. Although I find it somewhat absurd you can cast pretty much anything through a union and it's 'ok', but using the language 'cast' exactly the same physical operation becomes 'illegal'.

NEVER EVER touch buffers passed in by the user as an &quot;input&quot; parameter. The concept of input parameters is often implicit in the function description. For instance, the filename passed to Open() is clearly an input variable and Open() must not mess with it, even if it is going to fix it back later. Keep in mind that the buffer might be in read-only memory or shared among several instances of a resident or multithreaded program.

Try to avoid host-OS calls such as malloc() and free() if you can do with AllocMem() and FreeMem(). This is because the pointer checking debug macros rely on finding the pointer within the Exec memory blocks with TypeOfMem().

 SA_BackFill, (ULONG) &amp;sbackfillhook,

Please do not use ULONG's to store/cast pointers in your code. use APTR/IPTR where appropriate.

==Compiling small parts of AROS source without using Build system==

[http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=3475&amp;forum=2&amp;post_id=29123#forumpost29123 from]

make stub
make
make install

and need genmodule from [http://pagesperso-orange.fr/franck.charlet/temp/radeon.zip inside] here.


Trying to build the support modules of [http://svn.berlios.de/wsvn/ignition/trunk/libs/scroller/ Ignition] with a normal Makefile:

How can I get rid of these linker warnings? 
U __includelibrarieshandling and U __this_program_requires_symbol_sets_handling


Is there something I have to care about when I create a module this way? 
(I have always used the build system in the past) Is there a function which must be the first in the generated module?

Are you using ld directly? If so, don't do that, use the compiler's driver instead (gcc, that is) to do all the steps, final linking included. The problem arises because the linker needs to be invoked through a wrapper, which in our case is called collect-aros (it would be collect2 on other systems). You can either call collect-aros in place of ld (I
wouldn't do that) or the compiler's driver (gcc, do that) as said above. Mh, hadn't noticed the makefile when I first replied and I had forgotten these symbols are actually produced by collect-aros itself.

The problem arises because you are using -nostartfiles, which avoids linking with the startup file, but the startup file contains code that handles the automatic libraries opening/closing and the generic symbol sets handling. By using DFLAGS=-lgraphics -lintuition -lutility you are actually linking with stub libraries that require the automatic handling of shared libraries to be implemented. Either you avoid using these stubs or you implement the needed code yourself. You can take inspiration from the normal startup code.

After re-enabling lines like
 #define UtilityBase cb-&gt;UtilityBase
I was able to build the module without the stub libraries.

==Tutorials==

See here for a [http://web.archive.org/web/20111107002757/http://fishys-house-of-aros-fun.webs.com/apps/blog/show/2651598-aros-porting-guide tutorial]

SDL/MesaGL/OpenGL game frameworks. [http://msm.grumpybumpers.com/?p=64 Jumpcore Minimal]

[http://lazyfoo.net/SDL_tutorials/index.php Tutorial]

[http://www.monkeyfighter.com/tetris.html Amiga Tetris]

[http://irrlicht.sourceforge.net/downloads.html Irrlicht 3D engine]

{{BookCat}}</text>
      <sha1>bzg2nl2i7y1y693v8zkwuvsuojos3eo</sha1>
    </revision>
  </page>
  <page>
    <title>User:Sjorskingma</title>
    <ns>2</ns>
    <id>200244</id>
    <revision>
      <id>4668997</id>
      <parentid>4586173</parentid>
      <timestamp>2026-09-05T19:11:46Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668997</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1859" sha1="r89w1lczw1fa7kc7c1w37ghwhdmeafd" xml:space="preserve">&lt;div style=&quot;background-color:#aaffff;{{text default color}}; line-height:1.5; border-width : 6px; border-style:solid;border-color:#88CCFF;&quot;&gt;
&lt;div style=&quot;background-color:#aaffff;{{text default color}}; line-height:1.5; border-width : 5px; border-style:solid;border-color:#00CCCC;&quot;&gt;
&lt;div style=&quot;background-color:#eeffff;{{text default color}}; line-height:1.5; border-width : 2px; border-style:solid;border-color:#3399AA;&quot;&gt;
&lt;div style=&quot;background-color:#eeffff;{{text default color}}; line-height:1.5; border-width : 2px; border-style:solid;border-color:#666677;&quot;&gt;
&lt;div style=&quot;background-color:#eeffff;{{text default color}}; line-height:1.5; border-width : 5px; border-style:solid;border-color:#BBBBBB;&quot;&gt;
&lt;div style=&quot;background-color:#eeffff;{{text default color}}; line-height:1.5; border-width : 5px; border-style:solid;border-color:#BBDDBB;&quot;&gt;
&lt;div style=&quot;background-color:#aaffff;{{text default color}}; line-height:1.5; border-width : 6px; border-style:solid;border-color:#88CCFF;&quot;&gt;
&lt;div style=&quot;background-color:#aaffff;{{text default color}}; line-height:1.5; border-width : 5px; border-style:solid;border-color:#00CCCC;&quot;&gt;
&lt;div style=&quot;background-color:#eeffff;{{text default color}}; line-height:1.5; border-width : 2px; border-style:solid;border-color:#3399AA;&quot;&gt;
&lt;div style=&quot;background-color:#eeffff;{{text default color}}; line-height:1.5; border-width : 2px; border-style:solid;border-color:#666677;&quot;&gt;
&lt;div style=&quot;background-color:#eeffff;{{text default color}}; line-height:1.5; border-width : 5px; border-style:solid;border-color:#BBBBBB;&quot;&gt;
&lt;div style=&quot;background-color:#eeffff;{{text default color}}; line-height:1.5; border-width : 5px; border-style:solid;border-color:#BBDDBB;&quot;&gt;
Link to my Dutch wikipedia userpage ---&gt; [http://nl.wikipedia.org/wiki/Gebruiker:Sjorskingma]
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</text>
      <sha1>r89w1lczw1fa7kc7c1w37ghwhdmeafd</sha1>
    </revision>
  </page>
  <page>
    <title>USMLE Step 1 Review/Pathology</title>
    <ns>0</ns>
    <id>203476</id>
    <revision>
      <id>4669071</id>
      <parentid>3328983</parentid>
      <timestamp>2026-09-06T06:48:56Z</timestamp>
      <contributor>
        <username>~2026-48319-29</username>
        <id>3625295</id>
      </contributor>
      <origin>4669071</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1375" sha1="npxtx6467zu0xfloz8zosqf8fonfh4r" xml:space="preserve">===5 SIGNS OF INFLAMMATION (as described by Celsus)===
*Redness/Erythema (''Rubor'')
*Raised temperature (''Calor'')
*Swelling (''Tumor'')
*Pain (''Dolor'')
*Loss of Function (''Functio Laesa'')

====HYPERSENSITIVITY REACTIONS====
Goombs classification:
&quot;'''A'''nna '''C'''ycled '''I'''mmediately '''D'''ownhill--Gell &amp; Goombs&quot; or &quot;'''ACID'''&quot;.
* Type I   '''A'''naphylaxis
* Type II Cytotoxic-mediated
* Type III '''I'''mmune-complex
* Type IV  '''D'''elayed hypersensitivity


Coal workers pneumoconiosis is due to the presence of anthracosis. Basically a carbon pigment from coal mining accumulates in macrophages along the pleural lymphatics and interstitium. Usually advances through various stages. 
Clinical stages (Anthracosis)
1.	Asymptomatic
2.	Simple CWP(Coal workers pneumoconiosis. Cx(characterized) by coal-dust macules and nodules in upper lobes that produce little pulmonary dysfunction. 
3.	Complicated CWP. Cx progressive massive fibrosis accompanied by increasing respiratory distress, secondary pulmonary hypertension, and cor pulmonale. 
4.	Caplan syndrome is CWP accompanied by rheumatoid arthritis. 

Terms: Pneumoconiosis, anthracosis, macrophages, pleural lymphatics, interstitium, asymptomatic, pulmonary dysfunction, fibrosis, Secondary pulmonary hypertension, cor pulmonale, rheumatoid arthritis, caplan syndrome. 


{{BookCat}}</text>
      <sha1>npxtx6467zu0xfloz8zosqf8fonfh4r</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Malosh</title>
    <ns>3</ns>
    <id>204488</id>
    <revision>
      <id>4669065</id>
      <parentid>4594366</parentid>
      <timestamp>2026-09-06T06:42:32Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669065</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5016" sha1="byyugaeikqr809ncl5kqss8bvdl0isk" xml:space="preserve">== Welcome! ==

&lt;div style=&quot;font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Malosh!&lt;/div&gt;
&lt;div style=&quot;width:55%; float:left; margin: .2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#15304f;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold; color:#f4eed7;&quot;&gt;[[Image:Crystal Clear app korganizer.png|20px]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for freely-licensed collaboratively-developed [[WB:WIW|textbooks]].'''&lt;br/&gt;
You don't need technical skills in order to contribute here. '''[[WB:BOLD|Be bold]]''' contributing and ''[[WB:AGF|assume good faith]]'' about the intentions of others. Remember, this is a ''[[w:wiki|wiki]]'', so you're allowed to change just about anything, and changes can be made easily. Come [[Wikibooks:Reading room/General|introduce yourself]] to everyone, and let us know what [[Wikibooks:Reading room/Projects|interests you]].

If you're coming here from other Wikimedia projects, you should read [[Help:Wikibooks for Wikimedians|our primer for Wikimedians]] to get quickly up-to-speed.
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#2a62a1;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold; color:#e9deaf;&quot;&gt;[[Image:Icon apps query.svg|20px]] '''Getting help'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* See the '''Wikibooks [[Help:Contents|help pages]]''' for common issues.
* Remember, every edit is saved, so if you make mistakes, you can [[Wikibooks:Reverting|revert]] to an earlier version if needed.
* Get help from the community in the [[Wikibooks:Reading room|Reading room]] or in our [[irc:wikibooks|IRC channel]].
* You cannot upload an image until you have been a member for at least '''4 days'''. If your upload is tagged with {{tlx|nld}}, {{tlx|bfu}}, or {{tlx|nfur}}, please read the template message as it explains the violation of [[WB:MEDIA|our media policy]]. Please be sure to provide the required {{tlx|information}}: a [[WB:ICT|license tag]] and source citation are always required; fair use images require a {{tlx|fair use rationale}}. Get help in the [[WB:HELP|user assistance room]].
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;width:43%; float:left; margin: .2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#5f96d3;{{text default color}}; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold; color:#15304f;&quot;&gt;[[Image:Transmission icon.png|20px]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[:w:Help:Edit summary|the edit summary]] and [[Help:Show preview|preview]] your edits before saving.
* Sign your name on [[Help:Talk page|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#5f96d3; padding:0.2em 0.5em 0.2em 0.5em; font-size:110%; font-weight:bold; color:#15304f;&quot;&gt;[[Image:Nuvola filesystems trashcan full.png|20px]] '''Made a mistake?'''&lt;/div&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; padding:0.4em 1em 0.3em 1em;&quot;&gt;
* '''Please make sure you follow our [[WB:NP|naming policy]]''' - modules should be named like &lt;code&gt;Book Title/Chapter Title&lt;/code&gt;.
* Need to rename a page? Use the ''move'' tab (only become available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To get a page deleted, add {{tlx|delete|''your reason for requesting deletion''}} to the top of the page.
* If something you wrote was deleted, please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:VFD|VFD]] archives if applicable. You can request undeletion at [[WB:VFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;div style=&quot;background-color:#transparent;color:inherit; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks, --[[User:Adrignola|Adrignola]] &lt;sup&gt;[[User talk:Adrignola|talk]] [[Special:Contributions/Adrignola|contribs]]&lt;/sup&gt; 13:17, 21 July 2009 (UTC)&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear: both; text-align:right; font-size:smaller&quot;&gt;(P.S. Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;

==Just a tip==
When you create new pages, please place {{tlx|BookCat}} at the bottom of them so they will be added to the category that contains all of the book's pages. That will save us time categorizing in the future. Thanks! Happy editing. -- [[User:Adrignola|Adrignola]] &lt;sup&gt;[[User talk:Adrignola|talk]] [[Special:Contributions/Adrignola|contribs]]&lt;/sup&gt; 13:19, 21 July 2009 (UTC)</text>
      <sha1>byyugaeikqr809ncl5kqss8bvdl0isk</sha1>
    </revision>
  </page>
  <page>
    <title>User:Tiicoo:AFSKRB/KrbInstall</title>
    <ns>2</ns>
    <id>210660</id>
    <revision>
      <id>4669008</id>
      <parentid>4104606</parentid>
      <timestamp>2026-09-05T19:23:25Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669008</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3299" sha1="6aigdgxj5lddcsnlo4io4n1yax8itw8" xml:space="preserve">{{:User:Tiicoo:AFSKRB/Draft:Nav | User:Tiicoo:AFSKRB/Overview | Overview on OpenAFS and Kerberos | User:Tiicoo:AFSKRB/AFSInstall | Installation Of OpenAFS}}

__TOC__

==What is Kerberos?==
[[w:Kerberos|Kerberos]] is a Software developed at the [[w:MIT|MIT]] which can be used for network authentication. It uses a trusted third party (which we will call [[w:Key_distribution_center|key distribution center]] or KDC) in case two entities are trying to communicate safely. That third party consists of an authentication server one one side and on the other side of a Ticket Granting Server. For each entity the third party knows the secret key. In case two entities try secret communication the [[w:Key_distribution_center|key distribution center]] the KDC generates a session key.

The tickets you get from the KDC, specifically the AFS tokens you can make from those tickets will be the passport in the AFS network.

==Where to get?==
===Installing packages provided by your distribution===
Most distributions provide an OpenAFS/Kerberos environment themselves. For Gentoo an ebuild is provided. In case you are using Slackware64 you may get packages from http://ossy86.bplaced.net/dev/afskrb/

===Building it from source===
You can download Kerberos packages from http://web.mit.edu/kerberos/www/ or download a current development release via

 svn co svn://anonsvn.mit.edu/krb5/trunk/ .

into the your current working directory.

After you have got the sources we will do a
 
 util/reconf

in order to update the necessary configuration files. After we have done that we tell the build system to compile modules we are relying on via

 ./configure \
  --prefix=/usr \
  --enable-dns-for-realm \
  --enable-athena \
  --enable-kdc-replay-cache \
  --with-ldap \
  --libdir=/usr/lib64

The following table describes necessary options.
{| class=&quot;prettytable&quot; 
! style=&quot;background:#FFDEAD;{{text default color}};&quot; colspan=7 | Description of configuration parameters
|-
! style=&quot;background:#efefef;{{text default color}};&quot; | Switch
! style=&quot;background:#efefef;{{text default color}};&quot; | Description
|-
| style=&quot;text-align:center;&quot; | --prefix=/usr
| style=&quot;text-align:center;&quot; | We are going to install Kerberos into the directory /usr
|-
| style=&quot;text-align:center;&quot; | --enable-dns-for-realm
| style=&quot;text-align:center;&quot; | If this option is enabled we can use the Domain Name System for finding Kerberos Servers
|-
| style=&quot;text-align:center;&quot; | --enable-athena
| style=&quot;text-align:center;&quot; | Enable if you wish support for athena-like systems (distributed administration of thin clients and/or small computers with training software)
|-
| style=&quot;text-align:center;&quot; | --enable-kdc-replay-cache
| style=&quot;text-align:center;&quot; | Enable detection of retransmitted and/or replayed requests to the [[w:Key_distribution_center|key distribution center]]
|-
| style=&quot;text-align:center;&quot; | --with-ldap
| style=&quot;text-align:center;&quot; | Enable the [[w:LDAP|LDAP]] Backend
|-
| style=&quot;text-align:center;&quot; | --libdir=/usr/lib64
| style=&quot;text-align:center;&quot; | We would like to install libraries into this directory in case we are running on a x86_64 machine.
|}

{{:User:Tiicoo:AFSKRB/Draft:Nav | User:Tiicoo:AFSKRB/Overview | Overview on OpenAFS and Kerberos | User:Tiicoo:AFSKRB/AFSInstall | Installation Of OpenAFS}}</text>
      <sha1>6aigdgxj5lddcsnlo4io4n1yax8itw8</sha1>
    </revision>
  </page>
  <page>
    <title>User:RussellNash</title>
    <ns>2</ns>
    <id>211630</id>
    <revision>
      <id>4668928</id>
      <parentid>1634447</parentid>
      <timestamp>2026-09-05T12:32:15Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668928</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="607" sha1="n0kskc7al252l34fu5thpsaf8fu5mbb" xml:space="preserve">== About Russell Nash ==
{| align=&quot;right&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; width=&quot;350px&quot;
! style=&quot;background:#efefef;{{Text default color}};text-align:right; vertical-align:top&quot;| Name:
| Russell Nash


|}


I am an Applied Economics Major at the University of Minnesota. My interests range from water polo and soccer to learning to bartend, cook, and play pool.  For the first five months of 2009 I studied in Barcelona, Spain.  This was one of the greatest experiences of my life. My interests beyond school are unknown. I have looked into furthering my education in either economics or law.</text>
      <sha1>n0kskc7al252l34fu5thpsaf8fu5mbb</sha1>
    </revision>
  </page>
  <page>
    <title>User:Karmine2010</title>
    <ns>2</ns>
    <id>219879</id>
    <revision>
      <id>4669013</id>
      <parentid>1707971</parentid>
      <timestamp>2026-09-05T19:29:44Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669013</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2500" sha1="io42lxqz50zjdans83dxo058h9g04pt" xml:space="preserve">=About Karmine2010=
{| style=&quot;text-align:right;width:350px&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; 
! style=&quot;background:#efefef;{{Text default color}}; text-align:right; vertical-align:top&quot;| Name:
| Karmine2010

|-
! style=&quot;background:#efefef;{{Text default color}}; text-align:right; vertical-align:top&quot;| Current Home:
| Minneapolis, MN


|}
I am currently a multifaceted student studying many topics in the medical field.  I am a part of writing the online Wiki book for the ''U of M'' course '''Writ 3562W''' with my colleagues.  I enjoy many activities including playing lacrosse, playing in my band, and reading books which are relevant to my professional goals.

==Goals as a Student==
I plan on applying to medical school and specializing in cardiology. Currently I am pursuing a B.S. in Nutrition, where I plan on becoming a Registered Dietitian (RD) after graduation. I also enjoy networking with like-mined individuals to discover and create solutions to current dietary and medical problems that our present in today's world.

==Favorite Music==
I enjoy most types of music, but I prefer artists such as John Mayer, Dave Matthews Band, and bands with similar musical styles. I also enjoy some alternative rock music from bands such as Blink 182, Third Eye Blind, Goo Goo Dolls, Eve 6, '''The Strokes are by far my favorite band.'''  http://www.blink182.com/

==Favorite TV Shows==
My favorite TV shows include The Office, 30 Rock, Entourage, Arrested Development, Friday Night Stand Up, Weeds, Flight of the Conchords, The First 48, Family Guy, Family Matters, Full House, Home Improvement, Best Week Ever, Anything on ESPN

==Favorite Movies==
My favorite movies include '''Baseketball, Super Bad, Pineapple Express, The Dark Knight, Rudy, A Lot Like Love, Remember The Titans, The Sting, Oceans 11, 12, 13, Knocked Up, Heavyweights, Wedding Crashers, Dazed And Confused, The Professional, The Pelican Brief, Goldeneye, The Truman Show, Liar Liar, We Are Marshall, Dead Poets Society, Rules Of Attraction, American History X, American Psycho, American Gangster, American Pie, Boondock Saints, Billy Madison, Happy Gilmore, Big Daddy'''

==Favorite Books==

My favorite books ''American Psycho, Less than Zero, The Pelican Brief, Harry Potter, Pitching the Black, Heart of a Champion, The Rookie, Scar Tissue, I Hope They Serve Beer In Hell, Soldier Boys, Runaway Jury, The Thief, Lord of the Rings, Hamlet, Midsummer's Night Dream, Lunar Park, The Informers, A Million Little Pieces''</text>
      <sha1>io42lxqz50zjdans83dxo058h9g04pt</sha1>
    </revision>
  </page>
  <page>
    <title>User:Zoomdesign</title>
    <ns>2</ns>
    <id>219891</id>
    <revision>
      <id>4669011</id>
      <parentid>1771011</parentid>
      <timestamp>2026-09-05T19:26:03Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669011</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2733" sha1="56edmfewdhjfwfq46oe740kat2dwrm0" xml:space="preserve">=About zoomdesign=
{| align=&quot;right&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; width=&quot;350px&quot;
! style=&quot;background:#efefef;{{text default color}};text-align:right;vertical-align:top&quot;| Nickname:
| Calor

|-
! style=&quot;background:#efefef;{{text default color}};text-align:right;vertical-align:top&quot;| Hometown:
| Wisconsin

|-
! style=&quot;background:#efefef;{{text default color}};text-align:right;vertical-align:top&quot;| Current Home:
| Minneapolis, MN

|-
! style=&quot;background:#efefef;{{text default color}};text-align:right;vertical-align:top&quot;| Education:
| College of Design&lt;br&gt;University of Minnesota&lt;br&gt;
 

|-
! style=&quot;background:#efefef;{{text default color}};text-align:right;vertical-align:top&quot;| Websites:
| [http://www.sporcle.com/ Mentally Stimulating Diversions]&lt;br&gt;
[http://www.tetris.com/ Tetris Game]&lt;br&gt;

|}
I am a student at the '''University of Minnesota''', taking the Professional and Technical Writing Class 3562W.  I enjoy every second I spend in the '''University of Minnesota Marching Band'''.  I love watching old cartoons like ''Darkwig Duck'', ''Talespin'', and ''Ducktales''.  In my downtime I love to watch movies, listen to music, and create art.  Buying movies is my Achilles heal, almost every time I go into Target I end up with a new movie.

=Professional=
I am in my Junior year at the '''U of M''' and will be graduating next spring 2011.  I have very little professional experience in my graduating field, but am very determined to not move back home once I have graduated.  My hope is to get involved in Housing Development or Historic Preservation.  I am also considering Graduate School in a variety of places, but have not decided anything yet.

=Favorites=
My all time favorite movie is ''The Sound of Music''.  I have loved it ever since I was young and watched it with my grandmother.  Currently, my favorite music comes from ''The Fray'', ''Cascada'', ''Kelly Clarkson'', ''Paramore'', and ''Jason Derulo''.  When I find time to read non-school books, I find the ''Harry Potter'' Series, ''The Voyage of the Jerlie Shannara'' Series, and ''The Chronicles of Narnia'' Series to be some of my favorites.  Fantasy books are probably my favorite genre for books because they stimulate your imagination and really make you picture the places they have created.

=Interests=
Being from '''Wisconsin''', I have to love '''Packer''' Football.  It is the one sports team from '''Wisconsin''' that I will never let my allegiance change.  I also enjoy going shopping with my friends and spending money that I shouldn't, it's always a good time.  Photographing every fun and exciting event is both awesome and a curse.  A lot of times I end up missing things because I'm off somewhere taking pictures of everything.</text>
      <sha1>56edmfewdhjfwfq46oe740kat2dwrm0</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/Developer/Zune/Classes</title>
    <ns>0</ns>
    <id>223648</id>
    <revision>
      <id>4668971</id>
      <parentid>4603745</parentid>
      <timestamp>2026-09-05T17:47:47Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668971</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="143557" sha1="1sfcwbr8t5d2kk8l950mk2dxcjy2bck" xml:space="preserve">{{ArosNav}}

==Introduction==

Mui original classes are identified by the trailing .mui like List, String, etc

MUI (Zune) replacement classes MCCs came later which include Nlist, BetterString, etc which some developers frown upon.

Please read autodocs/MUI_Application.doc/MUIM_Application_NewInput it has a proper example for a '''complete''' main loop. A MUI program has a main loop, but in an ideal application the loop is empty. Main loops as well as hooks are a thing of the past but backwards compatibility is still there.

'''New method'''
So nowadays, in order to handle notifications from buttons, sliders, etc. - you [http://guidetoamigacompatibleprogramming.googlecode.com/svn-history/r4/trunk/english/CAP_4.txt subclass Application.mui], Window.mui or &lt;one of the groups&gt;.mui of your choice, define your own private methods there and set up notifications on your buttons to call these methods. This lets you keep a neat internal structure rather than having everything in a one huge switch statement of return ids.

Methods have no TRUE or FALSE states nor anything other defined states, they are just function calls (well, sort of). The only approach is subclassing technique and overload the method. You can then do anything you wish. The custom class is your way.

To define your own private method and attribute ids you could start with TAG_USER.
;Read more [https://github.com/chfhhd/guidetoamigacompatibleprogramming here]

'''Old Method'''
With MUI you can also call hooks to avoid creating subclasses, but only the change of an attribute can cause an action.

* First set Application and Window classes information. 
* Use Horizontal Groups (HGroup) or Vertical Groups (VGroup) to stuff objects (buttons, sliders, directory listers, etc) into them. Objects are not placed directly to some fixed locations but are instead grouped in special containers which are then dynamically displayed and positioned. 
* Use [http://www.pcguru.plus.com/tutorial/mui_methods.html Notification] to do something when object changes (pressed, slide, etc) 
* Release them when finished or when ending app

Macros play a part in programming Zune interfaces. Get and Xget can replace GetAttrs and Set and Xset similarly with SetAttrs.

When you read the mui autodocs there is a field after the function name with [ISG] and sometimes also [ISGN]

And that indicates what to can do with the tag.
&lt;pre&gt;
I = Init
S = SetAttr can be used
G = GetAttr can be used
N = Supports Notify
&lt;/pre&gt;

So if you see [I.G] that means that you can use the Tag at Init and use GetAttr on it.

==MUI Zune Base Classes==

{| class=&quot;wikitable&quot;
|-
|+ BOOPSI rootclass connected to Zune NOTIFY.mui class
! [http://amiga.sourceforge.net/amigadevhelp/MUI_Application.html Application.mui]      
! [http://amiga.sourceforge.net/amigadevhelp/MUI_Window.html Window.mui]          
! [http://amiga.sourceforge.net/amigadevhelp/MUI_Family.html Family.mui]     
! [http://amiga.sourceforge.net/amigadevhelp/MUI_Area.html Area.mui] 
|-
| 
| Aboutmui
| Menustrip
| Rectangle
|-
| 
| 
| Menu
| Balance
|-
| 
| 
| Menulist
| Image
|-
| 
| 
| 
| Menubar
|-
| 
| 
| 
| Bitmap
|-
| 
| 
| 
| Text
|-
| 
| 
| 
| Gadget
|-
| 
| 
| 
| Gauge
|-
| 
| 
| 
| Scale
|-
| 
| 
| 
| Colorfield
|-
| 
| 
| 
| List
|-
| 
| 
| 
| Numeric
|-
| 
| 
| 
| Pendisplay
|-
| 
| 
| 
| Group
|-
|}

encapsulation is what you have with all the MUI classes. For example to use a listview you have a well defined interface for this gadget, and all implementation details are encapsulated into the class (like private variables etc.)

You would do similar with an advanced application. Locate all sub-systems and implement these as &quot;isolated&quot; modules with interfaces and implementation details encapsulated into the modules, not visible from the outside.

inheritance via subclassing

polymorphism

===Subclasses===

;[http://library.morphzone.org/General_Rules_and_Purpose_of_Subclassing Subclassing Classes]

Good source examples [http://www.onyxsoft.se/snakee.html Snakee], [http://www.bluemind.org/amiga-lister-dopus-magellan-lister-system-amigaos/ List],

====Application====

; [http://www.pcguru.plus.com/tutorial/mui_howitworks.html Read more here] and [http://library.morphzone.org/Subclassing_Application_Class Application Class here]

Instead of MUI_NewObject(MUIC_Application, ,etc) is often replaced by the macro ApplicationObject, etc, etc...

When subclassing window or application class there aren't MUIM_Setup/Cleanup methods at all.

If you want to make a gui where everything is made of custom classes (at least the outer stuff, ie application and windows), you define all your classes as usual, and then instantiate your application with a single newobject() call. It's no problem to add elements to a group/window/application when it is being allocated (inside OM_NEW).

====Window====

; [http://library.morphzone.org/MUI_Subclassing_Tutorial:_SciMark2_Port#GUI_Design Gui Design]

Instead of MUI_NewObject(MUIC_Window, ,etc) is often shortened to the macro WindowObject,etc,etc but can be still used in Child Windows...

The way to do this would be to implement a method in one of your subclasses (MUIC_Window or the window's Root MUIC_Group are always safe picks) and have a MUIA_Window_? notification call it.

For the positions to be remembered, you have to close the windows (set MUIA_Window_Open to false) before disposing the Zune Application object

====Classes====

;[http://library.morphzone.org/Subclassing_List_Class Morphos List SubClass]

Instead of MUI_NewObject(MUIC_Group, ,etc) is often rewritten as the macro &lt;Group&gt;GroupObject,etc,etc...

Then class creation:

 TheClass = MUI_CreateCustomClass (NULL, supername, NULL, sizeof (MyObjectData), dispatcher);

&lt;pre&gt;
  if (!(mcc = MUI_CreateCustomClass(NULL,MUIC_Area,NULL,sizeof(struct NewClass_Data),NewClass_Dispatcher)))
  {
    printf(&quot;Cannot create custom class.\n&quot;);
    return(0);
  }
&lt;/pre&gt;

Is it ok to inherit from other types of object? Yes, to subclass slider class to overload MUIM_Numeric_Stringify method.

How to check for a minimum version of a MUI MCC when building a GUI? [...] 
Your best chance is that the custom class writer has overloaded MUIA_Version/Revision.

===Doing Stuff===

And here is a way to access this inside a method:

&lt;pre&gt;
LONG AnyMethod (Class *cl, Object *obj, Msg msg)
{
struct MyObjectData *data = INST_DATA(cl,obj);

/*...*/

if (!strcmp (&quot;Amiga&quot;, data-&gt;Pointer)) DoSomething();

/*...*/
}
&lt;/pre&gt;

Memory allocated for object data structure is freed automatically by MUI in object destructor, you have to do nothing.

 struct MyObjectData *data = (MyObjectData *)INST_DATA(cl, obj);

====Dispatcher====

Then, in your dispatcher subprogram, you write something like case MUIM_NList_ContextMenuBuild then MyOwnContextMenuBuild(cl,obj,msg); then you write a subprogram MyOwnContextMenuBuild that does what you want your class to do when this method is called.

Every object in your subclass gets its own data area added to the object &quot;structure&quot;. Also known as a data instantation. It is your own var area privately for the object with the given size in the MUI_CreateCustomClass() call but do not use the obsolete MUI_GetClass() and MakeClass() pairing. See the [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=2765 Class2.c] example in the MUI:Developer/C/Examples dir.

====Overloading====

'''Overloading''' class methods is the main and best design to use when you need to add some class features or use some specials behaviours. In MUI C version this is done by creating a new MCC (MUI Custom Class) and a dispatcher routine catching incoming BOOPSI messages when DoMethod() is called on instance of this MCC.

To find out when a superclass's attribute changes without using a Notify? Yes, just overload OM_SET. 
Most (if not all) calls to OM_SET are done with a temporary tag list allocated on the stack, so it'll be lost anyway...

If you need this pointer separate for every object, you should place it in object data structure.

&lt;pre&gt;
struct MyObjectData
{
char *Pointer;
};
&lt;/pre&gt;

Tag list or method structures should be untouched in any way if it's not documented. If MUI or 3rd party mcc's do this they're broken... Example of documented method structures touched by MUI are MUIM_Draw and MUIM_AskMinMax...

MUI will call MUIM_Hide, MUIM_Show on your object if the dimension change. So no need to check this in MUIM_Draw. MUIM_Draw is btw always called for a reason, so see no reason for you to omit a redraw here.

&lt;pre&gt;
ULONG NewList_New(struct IClass *cl , Object *obj, Msg msg)
{
    return 0;
}

ULONG NewList_Set(struct IClass *cl , Object *obj, Msg msg)
{

    return(DoSuperMethodA(cl, obj, msg));
}

ULONG NewList_Get(struct IClass *cl, Object *obj, Msg msg)
{

    return(DoSuperMethodA(cl, obj, msg));
}

&lt;/pre&gt;

===Application and Window===

How can you get a pointer to an active window object at any time?
Normally you should search for MUIA_Window_Active in Application window list. 
Can create MUIC_Window subclass and intercept MUIA_Window_Active, and create your API for this. 
On the other hand, you can set up notification on this tag and if window receives it you will know about it and set some field in memory to window pointer or so.

MUIA_Window_Screen for your own screen and trying to have window size completely under control. 
Setting MUIA_Window_Width and MUIA_Window_Height always works when you don't specify window ID (MUIA_Window_ID) for WindowObject.
In case you specify this ID, height and width are set automatically by system and are remembered for next time you run application.

&lt;pre&gt;
     app = ApplicationObject,
         MUIA_Application_Title, (IPTR)&quot;KeyShow&quot;,
         MUIA_Application_Version, (IPTR)&quot;$VER: KeyShow 1.0 (24.02.2012)&quot;,
         MUIA_Application_Copyright, (IPTR)_(MSG_AppCopyright),
         MUIA_Application_Author, (IPTR)&quot;The AROS Development Team&quot;,
         MUIA_Application_Description, (IPTR)_(MSG_AppDescription),
         MUIA_Application_Base, (IPTR)&quot;KEYSHOW&quot;,
 
         SubWindow, (IPTR)(win = WindowObject,
             MUIA_Window_Title, (IPTR)_(MSG_WI_TITLE),
             MUIA_Window_ID, MAKE_ID('K','S','W','N'),
             WindowContents, (IPTR)KeyboardGroupObject,
             End,
         End),
     End;
 
     if (app == NULL)
&lt;/pre&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/*
    Copyright © 2002, The AROS Development Team.
    All rights reserved.

    $Id: dtpic.c 30792 2009-03-07 22:40:04Z neil $
*/

#include &lt;dos/dos.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;

#include &lt;libraries/mui.h&gt;

struct Library *MUIMasterBase;

Object *app;

int main(void)
{
    Object *wnd;
    
    MUIMasterBase = (struct Library*)OpenLibrary(&quot;muimaster.library&quot;,0);

    app = ApplicationObject,
   	SubWindow, wnd = WindowObject,
    	    MUIA_Window_Title, &quot;dtpic test&quot;,
	    MUIA_Window_Activate, TRUE,

    	    WindowContents, VGroup,
    	    	Child, MUI_NewObject(&quot;Dtpic.mui&quot;,MUIA_Dtpic_Name,&quot;SYS:System/Images/AROS.png&quot;,TAG_DONE),
		End,
	    End,
	End;

    if (app)
    {
	ULONG sigs = 0;

	DoMethod
        (
            wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE, (IPTR) app, 
            2, MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit
        );

	set(wnd,MUIA_Window_Open,TRUE);

	while (DoMethod(app, MUIM_Application_NewInput, (IPTR) &amp;sigs) != MUIV_Application_ReturnID_Quit)
	{
	    if (sigs)
	    {
		sigs = Wait(sigs | SIGBREAKF_CTRL_C | SIGBREAKF_CTRL_D);
		if (sigs &amp; SIGBREAKF_CTRL_C) break;
		if (sigs &amp; SIGBREAKF_CTRL_D) break;
	    }
	}

	MUI_Object(app);
    }

    CloseLibrary(MUIMasterBase);
    
    return 0;
}
&lt;/syntaxhighlight&gt;

You must OM_ADDMEMBER a window to an application before opening it and you must OM_ADDMEMBER an area object to a group object (in a MUIM_Group_InitChange/ExitCHange pair) if you want to show it in a window (be part of your GUI). Mui Dev docs have a section on  Dynamic Windows (Dynamic Object Linking/Windows) which are detailed documentation for dynamic window creation.

But you can create a custom class and get notified just by looking for incoming methods. Overloading MUIM_Setup is probably the best idea. You can subclass your window and put screen change detection in MUIM_Setup. E.g. in every MUIM_Setup you can remember screen pointer somewhere in object data, compare it with the previous value and do some things if screen has changed. use _app(obj) after MUIM_Setup.

You could have subclass of MUIC_Group where the all objects are placed... When you detect in MUIM_Setup that _screen() changed, you set MUIA_Window_CloseRequest to TRUE...  If you app runs on WB screen user can change WB screen resolution/depth at any time. User can change your screen from the custom screen database at any time. Other thing to consider is iconify from the Exchange or ARexx. You _must_ react for screen changes.

Then you should place MUIM_Application_Save after your main loop.

Overloading MUIM_Window_Snapshot with some code which saves the prefs would do a save whenever the user selects the Snapshot icon on the window border, it would not do that only at program end. If you really want to save on Snapshot, you have to create a new class with CreateCustomClass() which must be a subclass of MUIC_Window. In the dispatcher of this sub class you have to call your own code whenever the dispatcher receives the MUIM_Window_Snapshot method. Then you have to change the application creation code: You have to replace every window creation with creation of an object of your window sub class (Intuition.NewObject()).

There seems to be a general problem when disposing windows: You must *not* reference the application object in a windows dispose method! Why? Because before disposing a window, you unlink it from the application (OM_REMMEMBER). After that, the window does no longer belong to an application and using _app(obj) is illegal. You don't have _app(obj) available during OM_NEW, the same is true for OM_DISPOSE.

Using _app(obj) anywhere in setup/cleanup methods (either before or after the DoSuperMethod) is fine. In fact, there is another layer between new/dispose and setup/cleanup where an object learns about its application context. However, this layer has not been made publically available through methods yet.

MUIA_Window_IsSubWindow does exactly this (skipping OM_REMMEMBER and OM_DISPOSE). However, this is not the solution to all problems which arise from the &quot;global&quot; window list in the application object. Window class should probably be able to have more window children itself.

How do we get the actual Window from my MUI-object ???

&lt;pre&gt;
struct Window *win;
DoMethod(obj,MUIA_Window,&amp;win);
&lt;/pre&gt;

MUIA_Window is an attribute. You can read attributes by calling GetAttr() from Intuition:

GetAttr(MUIA_Window, obj, &amp;x);

And few warnings:

* MUIA_Window is only valid when the window is opened
* MUIA_Window is an area class tag. Use MUIA_Window_Window for window objects.

To call ChangeWindowBox on MUI windows. Just take care that the window is currently open (MUIA_Window_Window!=NULL) need the screen, you can always get MUIA_Window_Window and use window-&gt;WScreen etc. like with other intuition windows.

'''MUIM_Application_PushMethod'''

So you want to get out of the object context first, and this is easily done with MUIM_Application_PushMethod.

&lt;pre&gt;
/* From your mail window */
DoMethod(_app(obj), MUIM_Application_PushMethod, _app(obj), 2,
MUIM_MyApplication_RemoveObject, obj);

/* From your application subclass */
case MUIM_MyApplication_RemoveObject:
{
DoMethod(obj, OM_REMMEMBER, msg-&gt;Obj);
MUI_DisposeObject(msg-&gt;Obj);
}
break;
&lt;/pre&gt;

Basically have a rendering task that does a heap of computation and renders into an offscreen rastport. When it's finished a frame, it sets a flag (Drawn) to FALSE, releases a semaphore, and does a PushMethod.

The main program, waiting patiently in its event loop, at some point will be awakened by the PushMethod, which triggers the custom class to do a MUI_Redraw() internally, which in turn obtains the semaphore, copies the offscreen bitmap to the window, sets Drawn to TRUE, and releases the semaphore. Then it goes back to sleep.

The rendering subtask, in the meantime, has done an ObtainSemaphore. When it gets it, it checks to see if Drawn is TRUE. If so, it can continue because it means the main task successfully copied the bitmap. Otherwise it releases it, does a little Delay, and tries again, to try and give the main task time to snatch the semaphore and do its work.

So, the semaphore is, in effect, protecting the offscreen rastport (and the Drawn flag) - neither task can access or change it without obtaining the semaphore first, and the flag is used to tell the draw task whether the main task has had a chance to do its job or not. Most of the time (i.e. almost always) the main task does, in fact, manage to grab the semaphore immediately so the draw task doesn't manage to steal it back again too quickly. If the main task finishes quickly, then when the draw task tries to obtain the semaphore it succeeds immediately, so there's no penalty.

PushMethod should not be too heavily overloaded, however, for inter-process communication recommends using private messageports for more intensive stuff. Use it as a signalling mechanism to wake up the main task and get it to send a MUI_Redraw to the custom class, and only ever send one at once (although there are 30-60 of them per second). Never had any problems with it in those circumstances.

&lt;pre&gt;
struct SignalSemaphore lock_AddEntry_Sem;
...
InitSemaphore(&amp;lock_AddEntry_Sem);
...
while(something){
...
   ObtainSemaphore(lock_AddEntry_Sem);     // Grab the semaphore
   while (lock_AddEntry){                  // Main task completed its job?
      ReleaseSemaphore(lock_AddEntry_Sem); // No, release semaphore
      Delay(1);                            // Wait a bit
      ObtainSemaphore(lock_AddEntry_Sem);  // Try again
   }
...
   lock_AddEntry = TRUE;                   // Set flag
   ReleaseSemaphore(lock_AddEntry_Sem);    // Give CPU back to main task
...
}
&lt;/pre&gt;

MsgPorts are slower. Semaphores are better to use under any AmigaOS like.

MUIM_HandleEvent is called for each event handler node unless MUI_EventHandlerRC_Eat is returned. MUIM_HandleInput is called for an active object if it was not eaten by MUIM_HandleEvent.

Should use EventHandler and not request? To avoid getting events even if my object is not the active one ?
Yes - eventhandlers respect properties such as the active and default object, priorites etc. 
HotkeyString is a subclass of BetterString. It adds a new eventhandler with a higher priority, thus get the events before its superclass, which wouldn't be the case for the other approach (one could override MUIM_HandleInput, but this was just *one* example...)

Eventhandlers also allow you to swallow input, another thing which isn't possible with IDCMP-requesting. This means many objects (which use the old way) will only interpret input when they are the active or default object, which is bad e.g. in IProbe where I want HTMLview to react on arrow up/down, even when the URL-string is active - and this is AFAIK only possible with eventhandlers.

the proper way to know the current active window (IDCMP_ACTIVEWINDOW/IDCMP_INACTIVEWINDOW was what I tracked before). What is the proper MUI way to know a window has become active? You can attempt a setup dispatcher that add the required actions to the event handler.

&lt;pre&gt;
struct your_data
{
struct MUI_EventHandlerNode ehnode;
};

ULONG yoursetup(struct IClass *cl, Object *obj, Msg msg)
{
struct your_data *data = (struct your_data *)INST_DATA(cl, obj);

if (!DoSuperMethodA(cl, obj, msg))
return(FALSE);

data-&gt;ehnode.ehn_Object = obj;
data-&gt;ehnode.ehn_Class = cl;
data-&gt;ehnode.ehn_Events = IDCMP_ACTIVEWINDOW | IDCMP_INACTIVEWINDOW;

DoMethod(_win(obj), MUIM_Window_AddEventHandler, &amp;data-&gt;ehnode);

return(TRUE);
}
&lt;/pre&gt;

add a cleanup dispatcher that looks like :

&lt;pre&gt;
ULONG yourcleanup(struct IClass *cl, Object *obj, struct MUIP_HandleInput *msg)
{
struct your_data *data = (struct your_data *)INST_DATA(cl, obj);

DoMethod(_win(obj), MUIM_Window_RemEventHandler, &amp;data-&gt;ehnode);
return(DoSuperMethodA(cl,obj,msg));
}
&lt;/pre&gt;

Add a dispatcher for MUIM_HandleEvent and take care of your wanted event like :

&lt;pre&gt;
ULONG yourhandler(struct IClass *cl, Object *obj, struct MUIP_HandleInput *msg)
{
struct your_data *data = (struct your_data *)INST_DATA(cl, obj);

if (msg-&gt;imsg)
{
case IDCMP_ACTIVEWINDOW:
// Do what you want here
break;

case IDCMP_INACTIVEWINDOW:
// Do what you want...
break;
}

return(DoSuperMethodA(cl, obj, (Msg)msg));

}
&lt;/pre&gt;

or You could try to install an event listener that triggers every time MUIA_Window_Activate gets changed.

Be able to receive mouse co-ordinates and keypresses into my application, even when the window is not active. 
You can poll intuition base and read mouse coords at any time. An interrupt routine would be the best solution if your app wants keep an eye on it all the time... (might be possible with other libraries)

Everything is single threaded unless you specifically use MUIM_Application_InputBuffered. No functions are interrupted in order to handle a signal. Would a better method be to offload the MUI interface handling onto a
separate task, and communicate with the network task through signals? This would at least solve the problem mentioned above. STRICQ uses MUI and is setup to handle any number of simultaneous sockets, both TCP and UDP. 
First create another window, then call MUIM_Application_InputBuffered (even though you should really try to avoid this) and then do the PushMethod. What should I do if the InputBuffered had to be used to handle other actions? Come up with a design pattern that avoids this nasty input probing in the middle of your program 
Creating a subclass of application class for this purpose where you could call one method with the object to be deleted as an argument and the application sub-class then stored a pointer to this object and deleted it after MUIM_Application_Input returned (and a nested counter tells me that there is no other recursive call to MUIM_Application_Method). Remember that the MUIM_PushMethod is not safe in the sense that it can fail (e.g. out of memory) and then your object doesn't get deleted (i.e. memory leak). The solution using a sub class of application class is safe as there is no need to allocate memory for the pointer to the object by adding it to an 'internal' Group class.

====Iconify====

&lt;pre&gt;
#ifdef __amigaos4__
    MUIA_Application_DiskObject , diskobject = GetDiskObject(_ProgramName),
    #endif
&lt;/pre&gt;

MUIA_Application_DiskObject,GetDiskObject(&quot;PROGDIR:mp3player&quot;),

where PROGDIR:mp3player is the name of your app. Be aware, that you are leaking the disk object this way. Be sure to assign it to pointer and FreeDiskObject after your application has ended..

&lt;pre&gt;
struct DiskObject *my_app_icon;
MUIA_Application_DiskObject,my_app_icon=GetDiskObject(&quot;PROGDIR:zamp&quot;),

ULONG iconified=0;
get(application, MUIA_Application_Iconified, &amp;iconified);
if( !iconified)
&lt;/pre&gt;

How to execute an arexx script from your own program as though it was run from your program's arexx port.
An application subclass that adds one method called MUIM_Application_RunScript, just call this method with the scriptname and its arguments then it will be launched with your (MUI) port as host and it will make sure your program doesn't quit before the script has completed.

&lt;pre&gt;
ULONG ListWindows( Object *application )
{
ULONG windows = 0;
struct MinList *windowlist;
windowlist = (struct MinList *) xget( application,
MUIA_Application_WindowList );
if( windowlist &amp;&amp; !IsListEmpty( (struct List *) windowlist ) )
{
Object *object, *objectstate = (Object *) windowlist-&gt;mlh_Head;
while( object = NextObject( &amp;objectstate ) )
{
Printf( &quot;Object 0x%08lx is %swindow.\n&quot;,
object,
IsWindow( object ) ? &quot;&quot; : &quot;not &quot; );
windows++;
}
}
return( windows );
}
&lt;/pre&gt;

You can check whether object class is class or subclass of MUIC_Window, using similar code to below:

&lt;pre&gt;
BOOL IsWindow( Object *object )
{
struct IClass *windowclass = MUI_GetClass( MUIC_Window );
struct IClass *class;
for( class = OCLASS( object ); class; class = class-&gt;cl_Super )
if( class == windowclass )
return( TRUE );
return( FALSE );
}
&lt;/pre&gt;

====External input====

 MUIM_Application_AddInputHandler(struct( MUI_InputHandlerNode ) in the MUIM_Setup and MUIM_Cleanup methods of your class (not subclass?).

Remove with MUIM_Application_RemInputHandler

'''Obsolete Hooks''' Is it safe to call the MUI_DisposeObject() inside a hook which is called by a notification if it frees the object the notification is attached to? This is not safe. The hook contents are not freed because after returning from the hook, there is still some return code from the calling class which has to be executed.

&lt;pre&gt;
MUIM_Application_AboutMUI 
MUIM_Application_AddInputHandler 
MUIM_Application_CheckRefresh 
MUIM_Application_InputBuffered 
MUIM_Application_Load 
MUIM_Application_NewInput (replaces old Input) 
MUIM_Application_OpenConfigWindow 
MUIM_Application_PushMethod 
MUIM_Application_RemInputHandler 
MUIM_Application_ReturnID 
MUIM_Application_Save 
MUIM_Application_SetConfigItem  
MUIM_Application_ShowHelp        
&lt;/pre&gt;

&lt;pre&gt;
MUIA_Application_Active 
MUIA_Application_Author 
MUIA_Application_Base 
MUIA_Application_Broker 
MUIA_Application_BrokerHook 
MUIA_Application_BrokerPort 
MUIA_Application_BrokerPri 
MUIA_Application_Commands 
MUIA_Application_Copyright 
MUIA_Application_Description 
MUIA_Application_DiskObject 
MUIA_Application_DoubleStart 
MUIA_Application_DropObject 
MUIA_Application_ForceQuit 
MUIA_Application_HelpFile 
MUIA_Application_Iconified 
MUIA_Application_MenuAction 
MUIA_Application_MenuHelp 
MUIA_Application_Menustrip 
MUIA_Application_RexxHook 
MUIA_Application_RexxMsg 
MUIA_Application_RexxString 
MUIA_Application_SingleTask 
MUIA_Application_Sleep 
MUIA_Application_Title 
MUIA_Application_UseCommodities 
MUIA_Application_UsedClasses 
MUIA_Application_UseRexx 
MUIA_Application_Version 
MUIA_Application_Window 
MUIA_Application_WindowList 
&lt;/pre&gt;

&lt;pre&gt;
MUIM_Window_AddEventHandler 
MUIM_Window_Cleanup 
MUIM_Window_RemEventHandler 
MUIM_Window_ScreenToBack 
MUIM_Window_ScreenToFront   
MUIM_Window_Setup 
MUIM_Window_Snapshot 
MUIM_Window_ToBack 
MUIM_Window_ToFront 
&lt;/pre&gt;

&lt;pre&gt;
MUIA_Window_Activate 
MUIA_Window_ActiveObject 
MUIA_Window_AltHeight 
MUIA_Window_AltLeftEdge 
MUIA_Window_AltTopEdge 
MUIA_Window_AltWidth 
MUIA_Window_AppWindow 
MUIA_Window_Backdrop 
MUIA_Window_Borderless 
MUIA_Window_CloseGadget 
MUIA_Window_CloseRequest 
MUIA_Window_DefaultObject 
MUIA_Window_DepthGadget 
MUIA_Window_DisableKeys 
MUIA_Window_DragBar 
MUIA_Window_FancyDrawing 
MUIA_Window_Height 
MUIA_Window_ID 
MUIA_Window_InputEvent 
MUIA_Window_IsSubWindow 
MUIA_Window_LeftEdge 
MUIA_Window_MenuAction 
MUIA_Window_Menustrip 
MUIA_Window_MouseObject 
MUIA_Window_NeedsMouseObject 
MUIA_Window_NoMenus 
MUIA_Window_Open 
MUIA_Window_PublicScreen 
MUIA_Window_RefWindow 
MUIA_Window_RootObject 
MUIA_Window_Screen 
MUIA_Window_ScreenTitle 
MUIA_Window_SizeGadget 
MUIA_Window_SizeRight 
MUIA_Window_Sleep 
MUIA_Window_Title 
MUIA_Window_TopEdge 
MUIA_Window_UseBottomBorderScroller 
MUIA_Window_UseLeftBorderScroller 
MUIA_Window_UseRightBorderScroller 
MUIA_Window_Width 
MUIA_Window_Window 
&lt;/pre&gt;

===Objects===

DoMethod( object1, method, attribute, value, object2, parameter_number, method2, attribute2, value2 [,...])

* MUIM_Application_NewInput 
* MUIM_Window_
* MUIM_CallHook MUIM_FindUData MUIM_GetUData MUIM_SetUData 
* MUIM_KillNotify MUIM_NoNotifySet MUIM_Notify 
* MUIM_Set MUIM_MultiSet  MUIM_SetAsString 
* MUIM_List_InsertSingle

When a Zune object is created and destroyed several methods are called:

&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;

If something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

If you want to manage a set of invisible objects the class MUIC_Family may be of help.

Need to know size of object while program is between MUIM_GroupInitChange and MUIM_GroupExitChange. Simple asking about MUIA_Width a MUIA_Height returns 0. Anyone have any idea? 
Width/height is not valid until you call ExitChange again. But if you need to know object dimensions subclassing is probably the best way to do so. You can get object dimensions by using _width()/_height() macros.

The object can't tell the difference of whether OM_SET was invoked through SetAttr() or through MUIM_MultiSet. 
Some standard MUI classes do indeed modify the taglist passed to them. A good example is Group class; it sets certain tags to TAG_IGNORE, because they either cannot be forwarded to the children, or shouldn't be handled by its superclass (Area).

How do you add a selected image to an app to use a different image for normal and selected states ?
Most people are using a Group with PageMode set, so that the group simply toggle the displayed page, when pressed, and each page has the desired image shown on it.

====Notifications====

;[http://library.morphzone.org/Event_Driven_Programming,_Notifications Morphos Notify]

Basically, MUI doesn't use BOOPSI's notification system. Notification happens transparently; the only thing you need to do is pass the method up to your superclass, and you should be doing that anyway—you don't need to use the approach that non-MUI BOOPSI classes use.

You can put notification on every attribute of your custom class. That's assuming your class is derived from MUIC_Notify. Then MUI will automagically execute the notification whenever you set an attribute.

You can place a notification on any (public) attribute of any class (or its ancestors) using the MUIM_Notify method. These notifications can be placed at any time from anywhere.

All you have to do is only change attributes of your object using set(), and in your set method handler add
  return (DoSuperMethodA(cl, obj, msg)); 
at the end. This will pass on the OM_SET up the class hierarchy to Notify.mui, which will then perform the notifications. The other thing, of course, is to always use set() whenever you want to change a value, rather than just assigning it directly. Only within the OM_SET method should you assign it directly.

When some other class puts a notification on one of your attributes, and your attribute gets changed using set() (or OM_SET), then when it does the DoSuperMethod() call the OM_SET will eventually reach the root class of all MUI classes—Notify.mui. This keeps a list of notifications to be performed.

&lt;pre&gt;
    /* This is setting up a notification on the MUIA_Robot_FrameRate * attribute */ 
    DoMethod(MyObj,
            MUIM_Notify, MUIA_Robot_FrameRate, MUIV_EveryTime,
            FrameCntObj,
            4,
            MUIM_SetAsString, MUIA_Text_Contents, MUIX_R&quot;%ld&quot;, MUIV_TriggerValue
    );

...

    /* This is setting the frame rate (actually done within the class
     * itself -- ie. I use set() rather than just changing the value
     * directly in case there are notifications on it. */
    set(obj, MUIA_Robot_FrameRate, data-&gt;framecnt - data-&gt;lastframecnt);

...

/* This is the relevant part of my custom class's OM_SET method
 * handler. */
static ULONG mSet(struct IClass * cl, Object * obj, Msg msg)
{
    struct MyData *data = INST_DATA(cl, obj);
    struct TagItem *tags, *tag;

    for (tags = ((struct opSet *) msg)-&gt;ops_AttrList; tag = NextTagItem(&amp;tags);)
    {
        switch (tag-&gt;ti_Tag) {
...
          case MUIA_Robot_FrameRate:    data-&gt;framerate = (ULONG) tag-&gt;ti_Data;
                                        break;
...
        }
    }

    return(DoSuperMethodA(cl, obj, msg));
}
&lt;/pre&gt;

If you have an attribute MUIA_Xxx_Yyy that is readable and notifiable, and recognized by mGet() (your OM_GET method). Internally it reads from data-&gt;Yyy. Further, let's say you have a private attribute MUIA_Xxx_YyyP (probably best to give it a numeric value quite different to the rest in your class) that is recognized by mSet() and writes to data-&gt;Yyy. mSet(), however, does *not* recognize MUIA_Xxx_Yyy. The code in the mSet() switch statement that recognizes MUIA_Xxx_YyyP, in addition to writing to data-&gt;Yyy, changes tag-&gt;ti_Tag to MUIA_Xxx_Yyy. Then, when the DoSuperMethodA() call is made, Notify class recognizes the attribute that was changed as MUIA_Xxx_Yyy and correctly performs the notification.

Suppose your class use the custom attribute MUIA_HHH_MyAttr. Other objects can ask MUI to be notified whenever this attribute is set()ted to a given value,for example you can have something like this:

 DoMethod(obj1,MUIM_Notify,MUIA_HHH_MyAttr,32,obj2,1,MUIM_MyObj_Changed);

Here object obj2 asks to be notified with method MUIM_MyObj_Changed whenever the attribute MUIA_HHH_MyAttr of obj1 is set()ted to 32.

Child, Label2(&quot;Allow duplicates:&quot;),
Child, ck6 = CheckMark(TRUE),

DoMethod(ck6, MUIM_Notify, MUIA_Selected, MUIV_EveryTime, app, 2, MUIM_Application_ReturnID, ACT_CK6);

The confusing thing about this bug is that it only affects CheckMark(TRUE) objects (or if you use MUIM_Application_Load to restore the state of checkmarks then those that become set to TRUE will exhibit the same problem).

The autodocs state you 'simply' add your checkmarks and strings (paired together) even in 'invisible' space. You need the string because the autostring for a checkmark is only place-able at the left side (which would be unintuitive).

&lt;pre&gt;
Object *MakeCheck(BYTE state, char *label)
{
  return ImageObject,
           ImageButtonFrame,
           MUIA_Text_Contents, label,
           MUIA_InputMode   , MUIV_InputMode_Toggle,
           MUIA_Image_Spec  , MUII_CheckMark,
           MUIA_Background  , MUII_ButtonBack,
           MUIA_ShowSelState, state,
           MUIA_CycleChain  , TRUE,
         End;
}
&lt;/pre&gt;

 DoMethod(timerobj,MUIM_Notify,MA_Timer_Seconds,MUIV_EveryTime,obj,2,MM_Clock_Seconds,MUIV_TriggerValue);

This should call MM_Clock_Seconds everytime MA_Timer_Seconds changes.

&lt;pre&gt;
WaitIO(data-&gt;req);
CurrentTime(&amp;raw,&amp;micros);
today = raw%86400;
SetAttrs(obj,MA_Timer_Seconds,today%60,TAG_DONE);
&lt;/pre&gt;

Notify does not happen

&lt;pre&gt;
data-&gt;seconds = today%60+30;
data-&gt;minutes = (today%3600)/60;
data-&gt;hours = today/3600;
data-&gt;req-&gt;tr_node.io_Command = TR_ADDREQUEST;
data-&gt;req-&gt;tr_time.tv_secs = 1;
data-&gt;req-&gt;tr_time.tv_micro = 0;
SendIO((struct IORequest *)data-&gt;req); 
&lt;/pre&gt;

timerobj's OM_GET:

&lt;pre&gt;
case MA_Timer_Seconds:
 *msg-&gt;opg_Storage = data-&gt;seconds;
return TRUE; 
&lt;/pre&gt;

Class has no OM_SET but you '''must implement OM_SET''' to notify. I would not use MUI notifications for this kind of events because due to BOOPSI latency. The timer does work (tested by getting MA_Timer_Seconds in every MUIM_Draw for the clock class, but MM_Clock_Seconds never gets called.

SetAttrs(NULL, ...
In theory you do not have to because SetAttrsA() is only a wrapper call to DoMethodA() which accepts NULL object pointer but this is not documented behaviour either in SetAttrsA() nor DoMethodA(). So do not rely on it but use macro instead to save you from typing if statements.

Restore a button frame - D&amp;D lately but it seems it clashes with MUI's own D&amp;D drawing. You could look into Ambient D&amp;D for ideas. It uses its own dropmarks.

&lt;pre&gt;
MUI_DISPATCH(NewList_Dispatcher)
{
    switch (msg-&gt;MethodID)
    {
        case OM_NEW              : return(NewList_New  (cl,obj,(APTR)msg));
        case OM_SET              : return(NewList_Set  (cl,obj,(APTR)msg));
        case OM_GET              : return(NewList_Get  (cl,obj,(APTR)msg));
        
        case MUIM_DragQuery : return(NewList_DragQuery(cl,obj,(APTR)msg));
        case MUIM_DragDrop   : return(MyList_DragDrop (cl,obj,(APTR)msg));
        case MUIM_ExternDrop :return(MyList_ExternDrop(obj,(APTR)msg));
    }
    return(DoSuperMethodA(cl,obj,msg));
}
&lt;/pre&gt;

added an internal notification method to each checkmark (checkbox) and added the method to the dispatcher,

&lt;pre&gt;
DISPATCHERPROTO(MCC_BIA_dispatcher)
{
struct mydata *mydata = INST_DATA(cl,obj);

switch (msg-&gt;MethodID)
{
case OM_NEW: return( MCC_BIA_New (cl, obj, (APTR) msg));
case OM_SET: return( MCC_BIA_Set (cl, obj, (APTR) msg));
case OM_GET: return( MCC_BIA_Get (cl, obj, (APTR) msg));
case OM_DISPOSE: return( MCC_BIA_Dispose (cl, obj, (APTR) msg));
case MUIM_AskMinMax: return( MCC_BIA_AskMinMax (cl, obj, (APTR) msg));
case MUIM_BIA_Changed: return( MCC_BIA_Changed (cl, obj, (APTR) msg));
default: return( DoSuperMethodA (cl, obj, msg)); 
}
}
&lt;/pre&gt;

Each time click on one of the checkboxes you get an MUIM_BIA_changed and the function get's called. Within the function readout the checkboxes and rebuild the bit array which can be read and set by using the MUIA_BIA_Array tag.

Now a notification for MUIA_BIA_Array is required. Do I need to call the class itself by using set(MUIA_BIA_Array) to cause a notification to take place, or is there a more simple way. Calling the class from inside would cause the checkboxes to change and this would result in another MUIM_BIA_changed and we have an endless loop.

The problem is that setting would cause an update of the class internal gadgets. These would cause a notify and the notify would cause another set().

&lt;pre&gt;
//The best way to handle it is to filter out tag list..
struct TagItem *tagitem;
tagitem = FindTagItem( MUIA_xxx_name, taglist );
if( tagitem != NULL )
{
tagitem-&gt;ti_Tag = TAG_IGNORE;
}
&lt;/pre&gt;

do-notify set might still causing infinite loop in some circumstances that vary on super class attributes implementation, and therefore in one class version working fine, in second crashing system...

&lt;pre&gt;
MUIA_ApplicationObject 
MUIA_AppMessage	
MUIA_HelpLine 
MUIA_HelpNode 
MUIA_NoNotify 
MUIA_ObjectID 
MUIA_Parent 
MUIA_Revision 
MUIA_UserData 
MUIA_Version

MUIM_CallHook 
MUIM_Export 
MUIM_FindUData 
MUIM_GetConfigItem 
MUIM_GetUData 
MUIM_Import 
MUIM_KillNotify 
MUIM_KillNotifyObj 
MUIM_MultiSet 
MUIM_NoNotifySet 
MUIM_Notify 
MUIM_Set 
MUIM_SetAsString 
MUIM_SetUData 
MUIM_SetUDataOnce	
MUIM_WriteLong 
MUIM_WriteString 
&lt;/pre&gt;

====Layouts====

&lt;pre&gt;
// Create your GUI 
 app = ApplicationObject,
 SubWindow, wnd = WindowObject,
 MUIA_Window_Title, (IPTR) &quot;Title&quot;,
 MUIA_Window_CloseGadget, FALSE,

 WindowContents, (IPTR) VGroup,
  MUIA_Group_SameWidth, TRUE,

  Child, (IPTR) HGroup,

   Child, (IPTR) VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText1&quot;,
    End,

    [...]

   End,

   Child, VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText2&quot;,
    End,

    [...]

   End,

   Child, VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText3&quot;,
    End,

    [...]

   End,

   Child, VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText4&quot;,
    End,

    [...]

   End,

   Child, VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText5&quot;,
    End,

    [...]

   End,

   Child, VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText6&quot;,
    End,

    [...]

   End,
  End,

  Child, HGroup,

   Child, Scan_button = SimpleButton(&quot;Button&quot;),
   Child, Quit_button = SimpleButton(&quot;Quit&quot;),
  End,
 End,
 End,
 End;
&lt;/pre&gt;

&lt;pre&gt;
 Object *exampleWinObj, *exampleVirtGObj, *exampleContainerObj;

Object *exampleChildObj;

exampleWinObj = (Object *)WindowObject,
                    MUIA_Window_CloseGadget, FALSE,
                    MUIA_Window_Title, (IPTR)&quot;Example Window&quot;,
                    WindowContents, (IPTR) (exampleVirtGObj= (Object *)GroupObject,
                        MUIA_Group_Virtual, TRUE,
                        Child, (exampleContainerObj = (Object *)VGroup,
                        End),
                    End),
                End;

if (exampleWinObj)
{
    int i;
    for (i = 0; i &lt; 10; i++)
    {
        exampleChildObj = HVSpace;

        if (DoMethod(exampleContainerObj, MUIM_Group_InitChange))
        {
            DoMethod(exampleContainerObj, OM_ADDMEMBER, exampleChildObj);
            DoMethod(exampleContainerObj, MUIM_Group_ExitChange);
        }
    }
}
&lt;/pre&gt;

Change the HVSpace for whatever object (group, etc) you want to add..

'''Obsolete Hooks.'''

MUI does not allow own position of Components, only automatic positions available (group concept) but by setting and Layout Hook and add and Left, Top, Width and Height to every Object, you can disable this behaviour

Your notify should preferably invoke a method on the class responsible for the action you want to have executed. Tend to gather more general stuff in window or application subclasses. If there's really no place it belongs then you can have it call a hook instead.

You must add your own layout hook which reports the size. Then simply invoke MUIM_Group_Init/ExitChange on your virtgroup object, as that will cause a re-layout == invocation of your layout hook, which can report new sizes for the contents. If your family tree needs any layout (before rendering) then the layout hook is also the ideal place for this. Take a look at 2b_VRastPort sources on Aminet.

&lt;pre&gt;
/* gcc syntax */
ULONG __attribute__((regparm(3))) Genealo_Layout(struct Hook *hook, struct
MUI_LayoutMsg *lmsg, Object *obj )
{
ULONG result = 0;
int longueur=500, haut=500;

switch(lmsg-&gt;lm_Type)
{
case MUILM_MINMAX:
{
printf(&quot;MinMax\n&quot;);
lmsg-&gt;lm_MinMax.MinWidth = 500;
lmsg-&gt;lm_MinMax.MinHeight = 500;
lmsg-&gt;lm_MinMax.MaxWidth = 500;
lmsg-&gt;lm_MinMax.MaxHeight = 500;
lmsg-&gt;lm_MinMax.DefWidth = 500;
lmsg-&gt;lm_MinMax.DefHeight = 500;
}
break;

case MUILM_LAYOUT:
{
printf(&quot;Layout...\n&quot;);

lmsg-&gt;lm_Layout.Width = longueur;
lmsg-&gt;lm_Layout.Height = haut;
result = TRUE;
}
break;
}
return result;
}
&lt;/pre&gt;

&lt;pre&gt;
ULONG __attribute__((regparm(3))) Genealo_Dispatcher(struct IClass *cl ,
void *msg,Object *obj )
{
Msg msg2 = ( Msg ) msg;
struct Genealo_Data *data;
ULONG result;

switch (msg2-&gt;MethodID)
{
case OM_NEW:
{
result = DoSuperMethodA(cl,obj,msg);
if(obj = (Object *)(result))
{
data = (struct Genealo_Data *)INST_DATA(cl,obj);

data-&gt;LayoutHook.h_Entry = (ULONG(*) ())Genealo_Layout;
data-&gt;LayoutHook.h_Data = data;
SetAttrs(obj,MUIA_Group_LayoutHook, &amp;data-&gt;LayoutHook,TAG_DONE);
}
printf(&quot;%p\n&quot;,result);
return( result );
}
break;
/* ..... */
&lt;/pre&gt;

How to do multithreading in MUI, where the same thread to be running several times simultaneously? Your application tree may only be accessed by one task, as no MUI object is re-entrant nor thread-safe (the
classes are, not the objects). Using 
 DoMethod(app,MUIM_CallHook,&amp;hook)
works fine for running different threads at the same time but when calling the same hook a second time, the first one pauses. 
It is because both threads are running on the same OS task. If you want to have them running simultaneously, you have to create a separate task for each thread, e.g. by CreateProc() from dos.library. 
That method is the same as CallHookA(&amp;hook, app, NULL) which again is the same as just calling the hook-function directly, with 'app' and '&amp;hook' as parameters. Not sure why you think this equals 'multi-threading'. 
If the second event then terminates, the first one continues, but it seems all the local variables have been altered by the second event. Because your code is not reentrant.

====Finding====

there is also a user field in IClass and you can access to this through MUI_CreateCustomClass() as in the Dispatcher. 
&lt;pre&gt;
mcc = MUI_CreateCust..()
mcc-&gt;mcc_Class-&gt;cl_UserData = data;
&lt;/pre&gt;
in the Dispatcher:
&lt;pre&gt;
data = cl-&gt;cl_UserData;
&lt;/pre&gt;

[http://library.morphzone.org/Locating_Objects_in_the_Object_Tree Locating objects in a tree using MUIA_UserData and MUIM_FindUData]

use MUIA_UserData, to store a pointer to a private struct where IT store information that object/related code might need ... e.g pointers to paths/filenames, whatever you like really.

the MUIA_UserData of the object contains the given udata\  and returns the object pointer in this case.

====Area (dragging, RMB etc)====

Let the program know if the user clicks anywhere on the map, the answer is yes: Group class is a child of area class, thus you
can use any attribute of area class, for example MUIA_Pressed.

Let the program know, if and where the user clicked on the map, the answer is no. That's exactly what custom classes are for. 
If any drawing will be manipulated by the user (e.g. an area for painting with the mouse), you write a subclass of Area class. 
Bitmap is just for displaying rastered images. If you want to have a (resizeable) area for application specific drawings, sub-classing Area is still the right thing to do.

If you want to create a bitmap of them tiled, which would then be displayed inside the application. 
For this application it is certainly simpler to use a Column group with Bitmap objects as children, or even a group with a custom LayoutHook that adapts the number of columns to the size of the area.

&lt;pre&gt;
// want the image to be the same size as the picture or if the object has to be bigger then the picture,
// it should be centered (horiz and vertically). 
TextAttr ta = { &quot;topaz&quot;, 8, 0, 0 };
TextFont *Topaz8Font = OpenFont(&amp;ta);

Object *guiobject = ImageObject,
MUIA_Image_Spec, &quot;5:&lt;path&gt;&quot;,
MUIA_Image_FreeHoriz, FALSE,
MUIA_Image_FreeVert, FALSE,
MUIA_Image_FontMatch, TRUE,
MUIA_Font, Topaz8Font,
End;
&lt;/pre&gt;

the Image class is a subclass of Area class, and the Area class can handle input, thus it should be possible to create an Image object that behaves like an ordinary button. Simply try to create an Image object, init the attribute MUIA_Image_Spec as &quot;5:picture_filename&quot; (to load the image via datatypes) and try to init the Area class attribute MUIA_InputMode as MUIV_InputMode_RelVerify.

Then set up a notification for that object, so you will hear from it, open the window...

It might help to have a look at the &quot;default macros&quot; for images and buttons in mui.h to initialize the other attributes (frame type etc.) properly.

# Call MUIM_Group_InitChange on a parent group of your object.
# OM_REMMEMBER it from the group.
# Change the size ie you should modify the data used in MUIM_AskMinMax to fill the structure.
# OM_ADDMEMBER it back.
# Call MUIM_Group_ExitChange on the group.

=====MUIM_DRAW=====

If you want to code yourself what your class will display (eg the wireframe drawing with the mui class1 demoprogram), you implement this overriding the MUIM_Draw method. (have a look at the three examples of custom classes class1 (ok), class2 (ok), class3 (obsolete).

Is it possible to draw on objects outside of MUIM_Draw? MUIM_Draw adds some overhead compared to direct draw (like in gadtools) but overhead is very minimal and you can't notice any slow down either...

Is there a safe way to do draw into a window/MUI-object outside a Draw-event? 
You can draw only inside MUIM_Draw because:
* your object may belong to virtual group and needs clipping (MUI installs this automatically for MUIM_Draw)
* your application can be hidden (in the iconified state) at anytime and thus _rp(obj) is not always valid.
* your object could be hidden for some reason (page and register groups)

If you just want draw new parts of your objects without full redraw? Then you could do something like this:

&lt;pre&gt;
data-&gt;DrawCommand = MY_OWN_DRAW_COMMAND;
MUI_Redraw(obj, MADF_DRAWUPDATE);
&lt;/pre&gt;

And then in your MUIM_Draw method:

&lt;pre&gt;
MyDraw()
{
DoSuperMethod();

if (msg-&gt;flags &amp; MADF_DRAWUPDATE)
{
switch (data-&gt;DrawCommand)
{
/* UPDATE PARTS YOU WANT TO */
}
}
else
{
/* FULL REDRAW */
}
}
&lt;/pre&gt;

In MUIM_Draw simply call BltBitMapRastPort() to display stuff in screen:

 BltBitMapRastPort(data-&gt;RastPort.BitMap, 0, 0, rp, mleft, mtop , mwidth, mheight, 0xc0);

create a bitmap, embed it in a rastport and set this rastport in your MUI renderinfo - then simply call MUIM_DrawBackground, and the background is drawn into your off-screen bitmap. Remember to set back the rastport

within your objects area you ae absolutely free to render whatever you want. And about the rastport: You *should* attach an own rastport to the object, if you use any graphics.library functions: Mui expects to find the objects own rastport in the same state after MUIM_Draw is executed.

If MUIM_Draw not being called (blank area with a frame) then check that you are not calling DoSuperMethodA() first in your MUIM_Draw method and that the MUIM_Draw Method only checks for msg-&gt;flags == MADF_DRAWOBJECT.

&lt;pre&gt;
switch( msg-&gt;MethodID )
{
[...]
case MUIM_Draw: return( draw( class, object, msg ) );
[...]
}
&lt;/pre&gt;

solved the problem, replaced them in the draw method

&lt;pre&gt;
if(!DoSuperMethodA(cl,obj,(APTR)msg)) 
    DoSuperMethodA(cl,obj,(APTR)msg);
&lt;/pre&gt;

Typically your object should have an internal buffer where you store the objects state after the last MUIM_Draw. This allows you to draw only those parts of your map, that need to be updated.

Stuff the parameters into you instance data and call MUI_Redraw() with MADF_DRAWUPDATE. That's what it is for. 
Basically, all rendering is done inside MUIM_Draw. If another method wants to render, it sets up parameters and calls MUI_Redraw().
MUI_Redraw() will then call MUIM_Draw for you.

However, you must be aware that MUIM_Draw might _not_ be called, e.g. when your object is currently hidden. So, MUIM_Draw should only draw; your other methods should do all the other stuff (if you draw an ellipse, you have to store that information somewhere in case a refresh comes in, the application is iconified etc. So, you MUIM_xxx_DrawEllipse will store all that information somewhere (adding the ellipse to a list or drawing it into an offscreen bitmap), then it will call MUI_Redraw(TheObject,MADF_DRAWUPDATE) to update the display).

What about a 3ds viewer with mui buttons ? Titler display opengl and mui on the same window, so what class/methods can use to display/redirect opengl output onto mui win? 
You need an area subclass to display your GL stuff in MUI window. You only need an offscreen bitmap which is blitted to the window in your MUIM_Draw method.

InitRastPort(&amp;data-&gt;RastPort) is done in other part of code! Once opengl context is initialized you can render to your offscreen bitmap using GL calls.

Have a look to aminet/wazp3d in soft3d_opengl.c. Inside there is code to start mesa for aros
(seek ifdef aros...) But aros mesa cant render in a bitmap: You will need to use your mui window + glscissor

[http://aminet.net/package/dev/mui/GLArea_src AreaGL] may be helpful.

&lt;pre&gt;
MUIA_Image_FontMatch
MUIA_Image_FontMatchHeight
MUIA_Image_FontMatchWidth
MUIA_Image_FreeHoriz
MUIA_Image_FreeVert
MUIA_Image_OldImage
MUIA_Image_Spec
MUIA_Image_State
&lt;/pre&gt;

=====MUI_Redraw=====

With MUI_Redraw(), an object tells itself to refresh, e.g. when some internal attributes were changed. Calling MUI_Redraw() is only legal within a custom class dispatcher, &quot;using this function within an applications main part is invalid!&quot;. To solve the same problem with my GUI for the UAE port of AROS, and simply wrapped the MUI_Redraw inside a custom method.

&lt;pre&gt;
MUIM_UAEDisplay_Update, struct MUIP_UAEDisplay_Update *,
({

if (message-&gt;top &gt;= data-&gt;height || message-&gt;bottom &lt;= 0)
return TRUE;

if (message-&gt;top &lt;= 0)
message-&gt;top = 0;

data-&gt;update_top = message-&gt;top;
data-&gt;update_bottom = message-&gt;bottom;

MUI_Redraw(self, MADF_DRAWUPDATE);

return TRUE;
})

case OM_SET:
{
struct TagItem *tagitem, *tagstate = msg-&gt;ops_AttrList;
while( tagitem = NextTagItem( &amp;tagstate ) )
{
case MUIA_[classname]_Update:
{
MUI_Redraw( obj, MADF_DRAWUPDATE);
break;
}
}
return( DoSuperMethodA( cl, obj, msg ) );
}
&lt;/pre&gt;

But better might be making just attribute to passing array of vectors.. When it's passed redraw is called.. or custom method:

&lt;pre&gt;
case MUIM_[classname]_Update:
{
MUI_Redraw( obj, MADF_DRAWUPDATE);
return( 0 );
}
&lt;/pre&gt;

You must not completely intercept OM_SET. Program sub-class some MUI class like Area.mui or Group.mui and they have their own attributes that might be set during program running.. Intercepting them or redrawing window might cause illegal actions..

=====Groups=====

The group class was designed to contain other groups and gadgets not to be a gadget by self. It's a side effect because it's a subclass of area class (making it a subclass of notify class and copying part of methods would be senseless). Well... if you want create an image button (button with text and gfx), apart from the group class it could be done by creating subclass of MUIC_Area which in MUIM_Setup load necessary picture(s) using datatypes.library, draw it in MUIM_Draw and dispose in MUIM_Cleanup. 
Btw. the group class isn't a subclass of area class by mistake.

Only group objects can have children. To get children there's MUIA_Group_ChildList. Walking through list is done with NextObject(). Example:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
	Object *obj1;
	struct List *children	= (struct List *)XGET(_maingrp, MUIA_Group_ChildList);
	APTR pObj               = GetHead(children);

	// Parse the children
	while(NULL != (obj1 = NextObject((Object **)&amp;pObj)))
	{
		printf(&quot;ID is: %ld\n&quot;, XGET(obj1,MUIA_ObjectID));
	}
&lt;/syntaxhighlight&gt;

To get parent there's MUIA_Parent.

If you don't know number of children or it's variable you would have to alloc some memory for the method struct (
sizeof(struct MUIP_Group_Sort) + sizeof(Object *) * num_children) and then call it with DoMethodA(obj, alloc'd_method). Then free the method struct again.

num_children = number of successful NextObject() calls on child list.

There's MUIM_Group_Sort method allowing you to tell the group object the exact order of the childs. NListview.mcc uses this and the group_initchange/group_exitchange stuff to dynamically show/hide scrollbars.

Almost all attributes you set on a group will be forwarded to its children. You can set MUIA_Group_Forward to FALSE to prevent this (while setting the tag in question).

a MUIM_Group_Insert method for inserting a child into a group in specified place, just like MUIM_Family_Insert. Currently move the child list from the group to my private family, insert the new child into my family with MUIM_Family_Insert and move all children from the family to the group again. on groups just like MUIM_Family_Sort on families.

&lt;pre&gt;
#define MUIM_Group_Sort 0x80427417 /* V4 */
DoMethod(parent, MUIM_Group_InitChange);
    DoMethod(parent, REMMEMBER, obj);
    set(obj, MUIA_FixWidth, 100);  // just some changing beyond the object borders
    DoMethod(parent, ADDMEMBER, obj);
DoMethod(parent, MUIM_Group_ExitChange);
&lt;/pre&gt;

InitChange/ExitChange during setup/cleanup is not a good idea. You should add your childs in MUIM_Setup *before* the DoSuperMethod() and remove your childs in MUIM_Cleanup *after* the DoSuperMethod().

should not disable groups anyway just to disable its children. Better disable each child for itself, since this will indeed look nicer. You can do this with one DoMethod, e.g. MUIM_MultiSet or MUIM_SetUData

Group is intended for objects having visual representation. For a text editor, if you group Buffer and Display objects it will be a bit tricky since Buffer isn't really a gadget. Editor should be a subclass of Display, and Buffer should be attached via pointer in object data structure. It better shows relations between Buffer and Display, they are not just a gadgets in a group.

Basically you have to call MUIM_InitChange before removing or adding objects and then call MUIM_ExitChange:

&lt;pre&gt;
DoMethod(yourgroup,MUIM_InitChange)
DoMethod(OM_ADDMEMBER,newobject)
DoMethod(yourgroup,MUIM_ExitChange)
&lt;/pre&gt;

to trigger a relayout by doing a MUIM_Group̠InitChange and MUIM_Group_Exitchange on the _parent(obj)

Every object should be responsible for passing the new settings on to its children. Like when you have a subclass of group that contains a numeric and a string gadget, it will have some attribute that holds a structure of the gadgets' respective values, and the group object has to know which value goes to which of its children and set them accordingly when itself it receives an OM_SET. Then you'd ideally do a set(mywindow,PREFS_ATTRIBUTE,&amp;some_structure) and the object tree would handle the rest by itself. 
Then there's no other way than to remember each object that needs to be updated in some structure and set() it &quot;by hand&quot;.

virtgroup.mui are internal part of MUI (they're &quot;inside&quot; muimaster.library).

The virtual group it's like a container that can scroll if the content exceeds its boundaries. A Virtual group makes sense inside a ScrollGroup.

you should not use MUIA_Pressed for notifying toggle gadgets (only for RelVerify ones like buttons). Use MUIA_Selected.

&lt;pre&gt;
window
---&gt; group (&lt;--- set MaxWidth/MaxHeight here, works)
------&gt; scrollgroup
---------&gt; virtgroup
------------&gt; text
------&gt; rectangle (&lt;--- or here, works, too)
&lt;/pre&gt;

How to get a virtgroup which is only in the horiz direction virtual w/o using scrollgroup (use MUIA_Scrollgroup_FreeVert, FALSE) or is there a way to have the scrollbar hidden all the time?

You need a [http://morphosambient.cvs.sourceforge.net/morphosambient/ambient/virtgroupclass.c?revision=1.5&amp;view=markup custom class] which uses fixed height or width thus locking virtgroup vertically or horizontally.

Adding objects to a group on the fly. First you have to '''init''' the changes you want to do, then '''perform''' them and then declare you have '''finished'''. Example of code to add or remove a group from another group:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
        Object *_maingrp = .... // the container
        Object *_subgrp = .... // the content

	// add the subgroup
	if(DoMethod(_maingrp, MUIM_Group_InitChange))
	{
           DoMethod(_maingrp, OM_ADDMEMBER, _subgrp);
           DoMethod(_maingrp, MUIM_Group_ExitChange);
	}

	// remove the subgroup
	if(DoMethod(_maingrp, MUIM_Group_InitChange))
	{
           DoMethod(_maingrp, OM_REMMEMBER, _subgrp);
           DoMethod(_maingrp, MUIM_Group_ExitChange);
	}
&lt;/syntaxhighlight&gt;

&lt;pre&gt;
LONG sigs;
DoMethod(app,MUIM_Application_NewInput,&amp;sigs);
&lt;/pre&gt;
This seems to be a general pitfall for MUI programmers, but 'sigs' really has to be initialized to zero! 
It's worse: sigs is the result of Wait(), i.e. the signals received by the process. So if you give a random value, MUI will think random signals were received, and act on these. Normally the effect of this is not noticeable, as a message-port signal will just cause a &quot;while(GetMsg(port))&quot;, which will immediately terminate, but in theory serious problems could arise

Want to reproduce the Workbench way of dealing with icons. Want to be able to move images from a point to another. Derive a Group (virtual or otherwise) with its own custom layout hook and make the objects of that group Draggable; when you get a drop event, re-layout the group (force this using MUIM_Group_InitChange = followed by ExitChange)

[http://www.henning-thielemann.de/ProgramsE.html TableGroup]

&lt;pre&gt;
MUIM_Group_ExitChange
MUIM_Group_InitChange
MUIM_Group_Sort

MUIA_Group_ActivePage
MUIA_Group_Child
MUIA_Group_ChildList
MUIA_Group_Columns
MUIA_Group_Horiz
MUIA_Group_HorizSpacing
MUIA_Group_LayoutHook
MUIA_Group_PageMode
MUIA_Group_Rows
MUIA_Group_SameHeight
MUIA_Group_SameSize
MUIA_Group_SameWidth
MUIA_Group_Spacing
MUIA_Group_VertSpacing
&lt;/pre&gt;

=====RMB and LMB=====

RMB menus to gadgets. Context menus are a feature of the Area class, and can be set with MUIA_ContextMenu, or dynamically created by overloading MUIM_ContextMenuBuild. 
Is it possible to use rmb as lmb in MUI? Yes, you should override MUIM_ContextMenuBuild for your object. Create fake Menu object (just with one menu and no items), give it to MUIA_ContextMenu attribute and do your job in MUIM_ContextMenuBuild, returning NULL from there (it means no context menu will be drawn). 
Well, its not easy, because there is no simple method to get informed about RMB _release_. You have to sub-class Text class and write own MUIM_HandleInput, which is mentioned in docs as obsolete. But unfortunately MUI event handlers don't react to RMB (bug in MUI?). can look at the MUIMine source (on Aminet). It does something like that and mentions problems with the RMB. It's also using MUIM_HandleInput.

=====Dragging=====

&lt;pre&gt;
ULONG MyList_DragQuery(struct IClass *cl,Object *obj,struct MUIP_DragDrop *msg)
{
    if (msg-&gt;obj==obj)
    {   //return(MUIV_DragQuery_Accept);
        return(DoSuperMethodA(cl,obj,(Msg)msg));
    }
    else
    {
        if (msg-&gt;obj==(Object *)muiUserData(obj))
            return(MUIV_DragQuery_Accept);

        else
            return(MUIV_DragQuery_Refuse);
    }

}
&lt;/pre&gt;

Whenever there are no conflicting inputs, MUI starts the drag operation immediately. If the LMB is needed for anything else (ie on a button), MUI starts dragging like specified in the prefs. set MUI_Draggable, TRUE to an object of a MUI_Area subclass

&lt;pre&gt;
get(obj,MUIA_List_DropMark,&amp;dropmark);
DoMethod(obj,MUIM_List_InsertSingle,entry,dropmark);
&lt;/pre&gt;

Note that you must get the dropmark from the destination object, *not* from the source.

One mode allows you to enter the data in the string gadget. The other allows dragging.  In the dragging mode you make the StringObject a TextObject.  That way you have no problems dragging the objects around.  You could also try making a Custom string class.

How to get MUI to report the dropped position relative to the object that is accepting the drop?  Also is there some way to get mui to report based on the top, left of the object that was grabbed and not report from where you grabbed the object at? If the position is screen based, just substract from it _mleft(obj) and _window(obj)-&gt;LeftEdge, _mtop(obj and _window(obj)-&gt;TopEdge.

Is there a way to react to a dragging of a workbench icon into an appwindow created with MUI.
The desktop manager sends message to an application only when user stopped dragging so it is not possible.

MUI has its way to handle d&amp;d with MUIM_DragBegin/DragFinish for its MUI object.... 
MUIM_DragBegin/Finish are for internal MUI D&amp;D. AppWindow messages are externally generated and MUI can not control it.

This is typically a method that you usually won't call yourself (like the drag'n'drop methods of area.mui)

&lt;pre&gt;
MUIM_AskMinMax
MUIM_Cleanup
MUIM_ContextMenuBuild
MUIM_ContextMenuChoice
MUIM_CreateBubble
MUIM_CreateShortHelp
MUIM_DeleteBubble
MUIM_DeleteShortHelp
MUIM_DragBegin
MUIM_DragDrop
MUIM_DragFinish
MUIM_DragQuery
MUIM_DragReport
MUIM_Draw
MUIM_DrawBackground
MUIM_HandleEvent
MUIM_HandleInput
MUIM_Hide
MUIM_Setup
MUIM_Show

MUIA_Background
MUIA_BottomEdge
MUIA_ContextMenu
MUIA_ContextMenuTrigger
MUIA_ControlChar
MUIA_CycleChain
MUIA_Disabled
MUIA_Draggable
MUIA_Dropable
MUIA_ExportID
MUIA_FillArea
MUIA_FixHeight
MUIA_FixHeightTxt
MUIA_FixWidth
MUIA_FixWidthTxt
MUIA_Font
MUIA_Frame
MUIA_FramePhantomHoriz
MUIA_FrameTitle
MUIA_Height
MUIA_HorizDisappear
MUIA_HorizWeight
MUIA_InnerBottom
MUIA_InnerLeft
MUIA_InnerRight
MUIA_InnerTop
MUIA_InputMode
MUIA_LeftEdge
MUIA_MaxHeight
MUIA_MaxWidth
MUIA_Pressed
MUIA_RightEdge
MUIA_Selected
MUIA_ShortHelp
MUIA_ShowMe
MUIA_ShowSelState
MUIA_Timer
MUIA_TopEdge
MUIA_VertDisappear
MUIA_VertWeight
MUIA_Weight
MUIA_Width
MUIA_Window
MUIA_WindowObject
&lt;/pre&gt;

====register (TABS)====

how can a child (a tab) of a register (Tab) know that he is currently visible w/o knowing in which tab it is? 
Have a .mcc which is a subclass of group and creates a row of cycletitle-objects (like cycle gadget, but with a fixed title string within the cyclegadget) where each button represents a window. The group gets notified (by notifyintuition.library) when a new window is opened or one win gets closed. 
or create a subclass of group which has a new attribute of something like MUIA_XGroup_PageIndex. You could then compare this to the &quot;main groups&quot; objects active page. You should know the &quot;main group&quot; object as it gets this from reading MUIA_Parent of the &quot;tab page&quot;.

 if tabpage.pageindex = tabpage.parent.activepage then (simple pseudo code)

Or create a subclass of register which as well as MUIA_Group_ActivePage has say MUIA_Group_ActivePageObj which is set on a change of MUA_Group_ActivePage. You could then compare this to the &quot;tab page&quot;.

 if tabpage = tabpage.parent.activepageobj then (simple pseudo code)

Or create a new method of register that returns the current obj (similar to your above idea) but as a method it will be usable for all your register groups.

&lt;pre&gt;
MUIA_Register_Frame
MUIA_Register_Titles
&lt;/pre&gt;

====Lists====

;[http://library.morphzone.org/Subclassing_List_Class good examples of lists]

* The list class is a class which can hold and manipulate (to some extent) a linked list of data. 
* The listview class is a group subclass which handles the layout and interconnection of a list and the required sliders.

Listtree which uses images for the branches, but afaik doesn't allow you to change the image.

At startup the list is empty and add entries with MUIM_List_InsertSingle.

MUIA_List_SourceArray to assign an strarray then use the MUIA_List_Active result as the index for that array.

MUIM_List_Remove

listview to have the width of the text inside and no more and no less.

 MUIA_List_Format - MAXWIDTH/MINWIDTH

 MUIA_List_AdjustWidth, TRUE

to insert strings in a ListView:

 DoMethod(projectfiles,MUIM_List_InsertSingle,(long unsigned int)TXT.sfilename.c_str(),(IPTR)MUIV_List_Insert_Bottom);

COPYING you will need to define Construct &amp; Destruct hooks as List object does NOT copy your string (just takes a pointer) until you order otherwise. If you got simple one column list and you will be satisfied storing just strings in it, MUI offers builtin construct hooks for this. Refer autodocs for construct &amp; destructs (must set both!).

 MUIA_List_ConstructHook, MUIV_List_ConstructHook_String

 MUIA_List_DestructHook, MUIV_List_DestructHook_String

MUIV_List_Remove_Selected

You can call MUIM_List_CreateImage as soon as the list class completed its setup method. You must call MUIM_List_DeleteImage before the list completes its cleanup method.

MUIM_Insert_xyz inserts an Object to a List, this meant that the List class can handle any Object and so you can not add only Strings to it. only a Pointer is stored and not the content of it. Note the List is not responsible for Displaying its' content, this was done by the Listview and by default it´s Displayhook expects pointers to a Text in the list.

how to add a small image next to a string in the list? game/think/MUIMastermind.lha might have a simple approach without CreateImage() and so on.

Reading MUIA_List_Active gives me the entry number, but if the order's changed, it doesn't mean anything? 
GetEntry returns pointer to your entry and you can access any column you wish. It's your private pointer anyway.

If you want a page background for an app, simply use MUIA_Background, MUII_PageBack for your group object.

'''Obsolete Hooks.''' If hooks are being used, multicolumn List object to display the result but want to add title to columns

&lt;pre&gt;
HOOKPROTO(ResultList_Display, ULONG, char **array, struct ReqData *reqdata)
{
if (reqdata) {

int n;
for (n=0; n&lt;reqdata-&gt;nb ; n++) {
*array++ = reqdata-&gt;columns[n];
}
} else {
reqdata = (struct ReqData *)hook-&gt;h_Data; // list titles

int n;

for (n=0; n&lt;reqdata-&gt;nb ; n++) {
*array++ = reqdata-&gt;columns[n];
}
}

return 0;
}
MakeStaticHook(hook_ResultList_Display, ResultList_Display);

Somewhere in your code you set h_Data:

hook_ResultList_Display.h_Data = (APTR)reqdata_titles;
&lt;/pre&gt;

You can either build a hook object that h_entry part is your function and use MUIM_CallHook or subclass the object id_main_add so that it handles a particular method, and in the case of your method is received call your add some function (it's the recommended way).. the callhook stuff would be something like

 struct Hook h = { addsome, NULL, NULL };

 DoMethod(id_main_add, MUIM_Notify, MUIA_Pressed, FALSE, id_main_add,2, MUIM_CallHook, &amp;h );

for AROS you have to change
&lt;pre&gt;
#define MUI_LIST_DISP(x,y) ULONG SAVEDS ASM x (REG(a2,char **array), REG(a1, y ))
to
#define MUI_LIST_DISP(x,y) ULONG SAVEDS ASM x (REG(a0,struct Hook *h), REG(a2,char **array), REG(a1, y ))
&lt;/pre&gt; 
so that a pointer to the Hook is the 1st argument. Same for other [hook macros http://aros.sourceforge.net/documentation/developers/headerfiles/aros/asmcall.h].

We have some hints about hooks in our [documentation http://aros.sourceforge.net/documentation/developers/app-dev/portable.php#hooks]

&lt;pre&gt;
MUIM_List_Clear
MUIM_List_CreateImage
MUIM_List_DeleteImage
MUIM_List_Exchange
MUIM_List_GetEntry
MUIM_List_Insert
MUIM_List_InsertSingle
MUIM_List_Jump
MUIM_List_Move
MUIM_List_NextSelected
MUIM_List_Redraw
MUIM_List_Remove
MUIM_List_Select
MUIM_List_Sort
MUIM_List_TestPos

MUIA_List_Active
MUIA_List_AdjustHeight
MUIA_List_AdjustWidth
MUIA_List_AutoVisible
MUIA_List_CompareHook
MUIA_List_ConstructHook
MUIA_List_DestructHook
MUIA_List_DisplayHook
MUIA_List_DragSortable
MUIA_List_DropMark
MUIA_List_Entries
MUIA_List_First
MUIA_List_Format
MUIA_List_InsertPosition
MUIA_List_MinLineHeight
MUIA_List_MultiTestHook
MUIA_List_Pool
MUIA_List_PoolPuddleSize
MUIA_List_PoolThreshSize
MUIA_List_Quiet
MUIA_List_ShowDropMarks
MUIA_List_SourceArray
MUIA_List_Title
MUIA_List_Visible
&lt;/pre&gt;

====Strings====

How to get notification of when an MUI string gadget is made active? So I know when the user has clicked on the gadget and activated the cursor, but before they start typing anything? I've tried setting MUIA_InputMode to MUIV_InputMode_RelVerify and MUIV_InputMode_Immediate, but neither work with either the MUIA_Pressed or MUIA_Selected notifications.

Build a subclass of String.mui and do what ever you need to do in the MUIM_GoActive and MUIM_GoInactive methods.

Converts input from a 'text box' (using Zune/MUI) to a floating point number. 
&lt;pre&gt;
get(my-string-object, MUIA_String_Contents, &amp;str);
    stcd_l(str, &amp;num);
&lt;/pre&gt;

Subclass the gadget and overload MUIM_GoInactive. Just be sure you've considered every situation the user may be in, e.g. leaving the gadget temporarily to copy the rest of the value from some other place or similar. 
Needed to subclass string gadget and add own event handler. As a workaround (imho), return DoSuperMethodA(cl,obj,(Msg)msg); when you return 0.

You can notify MUIA_String_Contents, which will be triggered each time the content change.
You can probably also use MUIA_Window_ActiveObject, which should be set to everything but the string gadget when it goes inactive. And if you use one of the string gadget replacements then there's also the possibility of overloading MUIM_GoInactive for the string class (Textinput, Newstring or Betterstring). But keep in mind that inactivating the gadget (using tab, the mouse, opening a new window or similar) should never have a confirming effect!

&lt;pre&gt;
MUIA_String_Accept
MUIA_String_Acknowledge
MUIA_String_AdvanceOnCR
MUIA_String_AttachedList
MUIA_String_BufferPos
MUIA_String_Contents
MUIA_String_DisplayPos
MUIA_String_EditHook
MUIA_String_Format
MUIA_String_Integer
MUIA_String_LonelyEditHook
MUIA_String_MaxLen
MUIA_String_Reject
MUIA_String_Secret
&lt;/pre&gt;

====Numeric (slider, knobs, levelmeters etc)====

Releasing the button when NOT over the gadget is well regarded to be a &quot;cancel&quot; action. Like
&quot;whoops! I accidentally pressed the button, but now I don't want to exit, so I'll move my mouse away&quot; 
Sliders also keep the value you dragged them to if you release the mouse outside the gadget.

How about getting a notification on a slider when the slider is released only? I tried MUIA_Pressed but that didn't work.  If you also use Area.mui/MUIA_InputMode. Also, I noted that MUIA_Slider_Level says (OBSOLETE). Use 
MUIA_Numeric_Value instead.

If pressing TAB key cycles options. How can I implement that ? 
You just set MUIA_CycleChain (area class) as TRUE in all the objects you want to be part of the cycle-chain.

Cycle object 
&lt;pre&gt;
STRPTR colors[] = { &quot;Red&quot;, &quot;Green&quot;, &quot;Blue&quot;, NULL };
ULONG colorsV;
STRPTR ch;
// then in the program...
get(cy1, MUIA_Cycle_Active, &amp;colorsV);
ch = (char *)colorsV;
&lt;/pre&gt;

Cycle_active contains the NUMBER of the selected item. To get the string you need to do something like this:

 ch = colors[ colorsv ];

Since MUIA_Cycle_Entries is [I..] the only way is to create a new cycle every time you want to change the entries. To do this you do MUIM_Group_InitChange on the group containing the cycle, then OM_REMMEMBER the old one, OM_ADDMEMBER the new one and do MUIM_Group_ExitChange. You may have to use MUIM_Group_Sort to get the cycle to the right place or put it into a separate group.

Can anyone tell me if it is possible to create a dynamic cycle gadger
You can &quot;emulate&quot; it by removing the gadget and creating a new one with MUIA_Cycle_Entries changed. Use MUIM_Group_InitChange/ExitChange for this.

&lt;pre&gt;
MUIA_Cycle_Active
MUIA_Cycle_Entries
&lt;/pre&gt;

a slider with gradient background. You can set gradient by MUIA_Background (but attribute string is undocumented) or maybe overloading MUIM_DrawBackground...

Sliders that look like a regular button when not pressed, but when pressed, they pop up and become a slider. They save a lot of space. It's a NumericbuttonObject - it's used in the demo program Slidorama.

&lt;pre&gt;
MUIM_Numeric_Decrease
MUIM_Numeric_Increase
MUIM_Numeric_ScaleToValue
MUIM_Numeric_SetDefault
MUIM_Numeric_Stringify
MUIM_Numeric_ValueToScale

MUIA_Numeric_CheckAllSizes
MUIA_Numeric_Default
MUIA_Numeric_Format
MUIA_Numeric_Max
MUIA_Numeric_Min
MUIA_Numeric_Reverse
MUIA_Numeric_RevLeftRight
MUIA_Numeric_RevUpDown
MUIA_Numeric_Value
&lt;/pre&gt;

====Menus====

Mui has its own methods for menus but the old NewMenu calls can still be used.

The best way is maybe to create&amp;dispose the context menus you need in a subclass of window class. 
Menu items are set for currently active window? In the case you can set up different menu for each of window, preferably inside window subclass, and with notification which will call method or attribute or your's window class and it'll be able to react.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
&lt;/syntaxhighlight&gt;

How to notify on pressing shortcut combination with shift, control and alt keys? I tried such code:
 DoMethod(win, MUIM_Notify,MUIA_Window_InputEvent, &quot;-control x&quot;,app, 2,MUIM_Application_ReturnID,MEN_RUN);
but I get notification each time X button is pressed (no matter whether control is pressed).

You need a normal eventhandler in your class for that. Please do not use returned stuff? So I see the only way is to use rawkey hook. Want such shortcuts for menu items, there are too many of them so I can't use combinations with Amiga for each one. menu item &quot;MUI Settings...&quot;. To set a notify to the menu item that calls MUIM_Application_OpenConfigWindow

The way to do this would be to implement a MenuTrigger method in one of your subclasses (MUIC_Window or the window's Root MUIC_Group are always safe picks) and have a MUIA_Window_MenuAction notification call it. There you could either have a switch with all the IDs, or simply use methodIDs instead of menu IDs and just do it like:

&lt;pre&gt;
ULONG mMenuTrigger(struct IClass *cl, Object *obj, struct mpMenuTrigger *msg)
{
DoMethod(obj, msg-&gt;menutriggercommand);
}
&lt;/pre&gt;
Once all menu triggers are nicely done as methods (say MUIM_MyClass_Open, MUIM_MyClass_DoSomething) and you've built a menu using those IDs, you could also implement an eventhandler in the Group subclass I mentioned and simply map raw keys into methods again. This could be done nicely using something like:
&lt;pre&gt;
struct MenuKey
{
ULONG methodForQualifierShift;
ULONG methodForQualifierControl;
ULONG methodForQualifierAlt;
ULONG methodForQualifierAltShift;
};
&lt;/pre&gt;
and then have these mapped like
&lt;pre&gt;
struct MenuKey hotkeys[256] = 
{
{0, MUIM_MyClass_Jump}, // RAWKEY_TILDE
{MUIM_MyClass_First}, // RAWKEY_1
....
};
&lt;/pre&gt;

so you can easily map every key combo into a method.

Well... just one of the many possible approaches to this problem, but one that will leave you with a nice OO structure in the source.

Added a check for msg-&gt;imsg-&gt;Code==MENUDOWN which reatcs the RMB being pressed and stops the timer. I also did the reverse msg-&gt;imsg-&gt;Code==MENUUP which would start the timer again. BUT - once the Menu is open the mouse button presses are attached to the menu and not my window/object so the MENUUP button event is never seen so my timer remains stopped and does not start again after using a menu. 
You could use MUIA_Window_MenuAction to be notified when a menuitem was chosen, 
 DoMethod (win, MUIM_Notify, MUIA_Window_MenuAction, MUIV_EveryTime, obj, 2, MM_Main_MenuAction, MUIV_TriggerValue); 
Not sure if the attribute gets triggered when no item was selected...

Checking window activation does not help either as the window remains active when a menu is opened so nothing changes. You could add a global input handler for checking of RMB pressing and releasing and then also check if the mouse pointer is over your window...

'''Redundant''' MUIA_Application_Menu and MUIA_Window_Menu (old New Menus system)

'''Redundant''' MUIM_Application_GetMenuCheck, MUIM_Application_GetMenuState, MUIM_Application_SetMenuCheck, MUIM_Application_SetMenuState

'''Redundant''' MUIM_Window_SetMenuCheck, MUIM_Window_SetMenuState,  MUIM_Window_GetMenuCheck, MUIM_Window_GetMenuState

&lt;pre&gt;
MUIA_Menu_Enabled
MUIA_Menu_Title
&lt;/pre&gt;

=====MenuStrip=====

Menustrip class is the base class for MUI's object oriented menus. Its children are objects of Menu class, each of them describes exactly one menu.

A Menustrip object doesn't feature many options itself, but as a subclass of Family class, it simply acts as father for multiple Menu objects.

The Menustrip object is usually specified as a child of either Application class or window class with the attributes MUIA_Application_Menustrip or MUIA_Window_Menustrip.

Have you tried using MenustripObject and MenuObject instead of MenuitemObject, and MUIA_Menu_Title instead of MUIA_Menitem_Title? Though to be honest, I'm not sure if all of those macros exist in AROS.

the hierarchy is:    MenustripObject -&gt; MenuObject -&gt; MenuitemObject

Using Menuitems everywhere worked before, but it was not compatible with MUI and was changed.

With family objects (from Wanderer/Info):

DoMethod(_win(obj), MUIM_Notify, MUIA_Window_MenuAction, MUIV_EveryTime, obj, 2, MUIM_MySubClass_MenuThingy, MUIV_TriggerValue);

Read more about Menus in MUIA_Window_MenuAction section of muidevs.

See also DiskSpeed.c in DiskSpeed drawer of the contrib-source of AROS.

In one MenuItem tag there wasn`t a &quot;MUIA_UserData&quot; tag identifier in front of the ID of that menuitem and so on a dispose gcc somehow freed an area in memory that caused the crash where sas/c didn`t somehow.

&lt;pre&gt;
entry = MUI_MakeObject(MUIO_Menuitem,advance_name_translation(i),NULL,0,0);
set(entry,MUIA_UserData,i);
DoMethod(entry,MUIM_Notify,MUIA_Menuitem_Trigger, MUIV_EveryTime, entry,6, MUIM_CallHook, &amp;civstandard_hook, diplomacy_tech, pdialog, plr0-&gt;player_no,entry);
DoMethod(menu_title,MUIM_Family_AddTail, entry);
&lt;/pre&gt;

&lt;pre&gt;
MUIA_Menustrip_Enabled
&lt;/pre&gt;

====Requesters====

 MUI_Request(app, mainwnd, 0L, &quot;Sorry...&quot;, &quot;Close&quot;, &quot;...but this feature is not yet implemented&quot;, NULL);

Either create your new objects outside this huge MUI constructions, and in there use just a pointer, or get rid of the &quot;End&quot; macro and exchange it with &quot;TAG_DONE)&quot;. On MOS and AmigaOS, the NewObject variadic function is kept in the static library. It takes most of the parameters on the stack - thanks to that the implementation of NewObject calls the NewObjectA function. Everything works perfect, and the typical MUI macros may be easily used.

This, however, is not the case when you compile for AROS. Here, NewObject is a variadic macro, not a function. Thanks such approach we do not need any custom compiler in case of systems, where the arguments of variadic functions are passed partially through registers and partially through the stack (This is the case of PPC and x86_64, this is also the reason why both OS4 and MOS require specially patched compilers).

Since NewObject is a macro, the gcc's preprocessor expects the list of macros arguments enclosed within parentheses. In MUI macros it is not the case.

=====ASL requester=====

this should [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=1430&amp;forum=2&amp;post_id=11642#forumpost11642 help]:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
struct FileRequester *req;

if ((req=MUI_AllocAslRequestTags(ASL_FileRequest,
ASLFR_Window,win ,
ASLFR_TitleText, &quot;A requester for AmiDevCpp&quot;,
ASLFR_InitialDrawer , &quot;T:&quot;,
ASLFR_InitialFile, &quot;foo.txt&quot;,
ASLFR_InitialPattern , &quot;#?.txt&quot;,
ASLFR_DoPatterns , TRUE,
ASLFR_RejectIcons , TRUE,
TAG_DONE))) {

if (MUI_AslRequestTags(req,TAG_DONE)) {
/* you can find the drawer in req-&gt;fr_Drawer and the file in req-&gt;fr_File */
}
}
&lt;/syntaxhighlight&gt;

MUI_AslRequest() functions and MUI takes care of window refresh for you.

&lt;pre&gt;
MUIA_Popasl_Active
MUIA_Popasl_StartHook
MUIA_Popasl_StopHook
MUIA_Popasl_Type
&lt;/pre&gt;

====Pop Up Pen etc====

MUIA_Window or MUIA_WindowObject? MUIA_Window should refer to struct Window * but MUIA_WindowObject to Object *

Both are always NULL for a popup list, whether open or not.

An interesting point is that the window object pointer supplied to the MUIA_Popobject_WindowHook is non-NULL. 
checking for whether popup is open such work around anyway? Popup object is open only a while, when user clicked popup button and popup object appeared on screen- any clicking causes popup object to disappear. So, I can't even imagine where and why are you checking this.. From 2nd parallel running task?

If popup object is made by you, you always can subclass any MUI class. And this way you will get all methods and attributes like f.e. OM_SET/OM_GET and MUIM_Setup/MUIM_Cleanup/MUIM_Show/MUIM_Hide. Probably listening on show/hide might help checking whether popup is currently open. This method probably should work also for other MUI applications, if you're not owner of app, but making monitor software- but instead subclassing get and store dispatcher address, then put your own, and listen methods/attrs like above, then call original dispatcher to return control to original application.

It looks like [http://www.sasg.com/mui/autodocs/MUI_Popstring.html Popstring] has special hooks for this task 
* MUIA_Popstring_OpenHook
* MUIA_Popstring_CloseHook

Shift up/down is (normally) bound to page up/down, and if the listview hasn't been drawn once, then there are no page dimensions.

DoMethod(PP_String, MUIM_Notify, MUIA_String_Acknowledge, MUIV_EveryTime, App_p, 2, MUIM_Application_ReturnID, RID_EXECUTE);

A notify watch if a tag changes (for the given object) - MUIA_String_Acknowledge is a tag of the string class (not the Popph-string) and is set (and therefor changed) for the string object. So the notify must be on this object, rather than the container (which is Popph)

Either get the pointer to the internal string-object, and setup a notify on this (and do try to avoid ReturnID's ;-) ) Should just be to forward MUIM_Notify to the child objects, preferably only if OM_GET returns TRUE for the tag in question. I.e. if OM_GET returns TRUE for the Popph object itself (an Area class tag probably) then keep the notify, otherwise try to see which of the children supports it. Or maybe it'd be better if Popph introduced two new methods a la MUIM_Popph_NotifyString &amp; List. Then one could use either of these to setup a notify on an internal object.

nothing wrong with ObtainBestPenA() if you don't want the user to configure the pen values (which you often do want) - though avoid placing the pen-stuff in MUIM_Show/Hide, it should be MUIM_Setup/Cleanup, otherwise it'll re-allocate pens each time you resize the window

If you want the user to be able to configure the pens then you do so by using the Poppen-object together with MUI_ObtainPen() - here's a snip from MUI_PopPen.Doc:

Anyway, you do not have to care about the internals of this class. Just create it like

obj = MUI_NewObject(MUIC_Poppen,
MUIA_CycleChain , 1,
MUIA_Window_Title, &quot;Followed Links Color&quot;,
TAG_DONE);

somewhere in your prefs window and everything will be fine. You can get/set the current color from a Poppen object by using the MUIA_Pendisplay_Spec attribute. The resulting struct MUI_SpenSpec may then be saved somewhere in your preferences and used as parameter for MUI_ObtainPen() and MUI_ReleasePen().

comes back in the format of: &quot;rxxxxxxgxxxxxxbxxxxxx&quot;. There are 3 parameters in MUI_ObtainPen() *mri , *spec &amp; flags.l

look in libraries/mui.h and you will fin a macro like this muiRenderInfo() just do this 
 mymri = muiRenderInfo(myobj);
and should have a valid MUI_RenderInfo but this macro should only be used between MUIM_Setup/MUIM_Cleanup

A popobject which is connected to a string gadget. The popobject is a listview. So that pressing up/down in the string gadget will scroll the listview updown (even when the listview is hidden) ?
 MUIA_String_AttachedList -- (V4 ) [ISG], Object *

&lt;pre&gt;
MUIA_Popobject_Follow
MUIA_Popobject_Light
MUIA_Popobject_Object
MUIA_Popobject_ObjStrHook
MUIA_Popobject_StrObjHook
MUIA_Popobject_Volatile
MUIA_Popobject_WindowHook
&lt;/pre&gt;

&lt;pre&gt;
MUIA_Poplist_Array
&lt;/pre&gt;

&lt;pre&gt;
MUIM_Popstring_Close
MUIM_Popstring_Open

MUIA_Popstring_Button
MUIA_Popstring_CloseHook
MUIA_Popstring_OpenHook
MUIA_Popstring_String
MUIA_Popstring_Toggle
&lt;/pre&gt;

====Text====

* (N)Floattext already does exactly the same as you did using the list. It splits a long text into separate lines, inserts some spaces to produce an aligned text and displays them.
* The TextEditor class in read-only does more or less the same like Floattext, but with the ability to apply different styles and coloring apart from the standard MUI text engine. Furthermore it allows to let the user edit the text in read-write mode. YAM makes heavy use of it in both modes to show and edit the mails.

Where ony Text() is done. So the size of the area depends on the size of the actual default font. Using  rp(obj)-&gt;Font, but in AskMinMax it seems that when it is first called, the Font is not yet initialized.
You can use _font(obj) to obtain the font. If you also need a rastport then you can setup one temporarily to do your calculations.

&lt;pre&gt;
struct RastPort rp;
InitRastPort(&amp;rp);
SetFont(&amp;rp, _font(obj));
WORD size = TextLength(&amp;rp, &quot;The Text&quot;, 8);
&lt;/pre&gt;

The problem is that text will not stay the right size. They are either spread all over the window, or cramped into one edge, when all I want them to do is to stay on the right and just as big to display 6 chars (as long as possible). MUIA_String_Maxlen seems to have no effect, and just forcing one width doesn't seem right as you never know wether the user may prefer to use a font 50 pixels wide.

Use tag MUIA_FixWidthTxt. For example

 str = StringObject, MUIA_FixWidthTxt, &quot;0000000&quot;, End;

Note 7 characters there: one is for cursor. And use characters which are wide by nature (read MUI_Area.doc and you understand why).

It could also be solved by using   MUIA_Weight, weight. 
Try a combination of &quot;MUIA_Weight, weight&quot; for the string(s) and Put RectangleObjects before/and/or/after the stringobject.

For example, to align a gadget to the right 
&lt;pre&gt;
HGroup,
Child, RectangleObject, MUIA_Weight, 75, End,
Child, StringObject,...,MUIA_Weight, 25, End,
End,
&lt;/pre&gt;

Which means that if you want to change the label and the key shortcut using one attr, you should subclass text, and handle a specific tag for changing the label and the shortcut, parsing yourself the string. Examples of subclassing a mui class can be found in mui dev kit (especially psi contains many subclasses...) and some tools can help you to have a skeleton class using a meta definition of the class you want (mui2c or bcc do such things).

If you create a subgroup something like:
&lt;pre&gt;
mygroup=Group ( MUIA_Group_PageMode,True
Child,SimpleButton(&quot;_Download&quot;),
Child,SimpleButton(&quot;_Resume&quot;),
TAG_DONE)
&lt;/pre&gt;
you get much better result. The &quot;Download&quot; button is now visible, but if you

 set (mygroup, MUIA_Group_ActivePage, 1)

&quot;Download&quot; disappears and &quot;Resume&quot; becomes visible. This is very common trick in MUI applications.

Buttons are simply text objects, which have the following tag:

 MUIA_Text_SetVMax, TRUE

Setting this to FALSE makes a TextObjects y-size unlimited. Defaults to TRUE which means the objects height is fixed. A plain text object cannot be higher than its text, unless you set MUIA_Text_SetVMax to FALSE (default is TRUE). This will give your object unrestricted height, but the text will be displayed vertically centered, unless you set MUIA_Text_VCenter to FALSE.

MUIA_Text_Contents is ISG so:

 SetAttrs(text, MUIA_Text_Contents, &quot;NewContent&quot;, TAG_DONE);

 set (object-&gt;STR_text, MUIA_Text_Contents, myText);

object-&gt;STR_Text ? Looks like MUIBuilder generated code :)

If your 'text-edit-box' is a String object, you'd rather use

 set( object-&gt;STR_text, MUIA_String_Contents, myText );

How to calculate the x/y coords to use with the Move() function so that when using Text() to draw the label it appears centred. There is bunch of macros in mui.h: 
&lt;pre&gt;
_mleft() = starting x coordinate of your drawing area
_mtop() = starting y coord etc.
_mwidth() = width of your drawing area
_mheight() = obvious =)
&lt;/pre&gt;

&lt;pre&gt;
text_height=GetItSomeHow();
text_len=TextLength(&quot;heipparallaa&quot;);

Move(rp, _mleft(obj) + ((_mwidth(obj) - text_len) / 2), _mtop(obj) + ((_mheight(obj) - text_height) / 2) );
&lt;/pre&gt;

(TextObject) If you really need to change the text, then you must set() it again after the modification.

If using a TextObject, then it has the FULL initial size... but if appending extra lines then these are not visible (although a bug causes it to write outside of itself!). The only way to get it to enlarge for the new text is to iconise &amp; then uniconise the MUI window. Also, the text is not word-wrapped.

You must not modify the text as long as it is &quot;in use&quot; by the object. MUI will calculate the required dimensions on basis of the given text and expects it to be constant. If you really need to change the text, then you must set() it again after the modification. This will let MUI do a relayout to display all of the new text.

But this will work to a certain extend only, namely when the complete text's height becomes larger than the window's maximum height. If you need to display larger texts, then the object should be placed into a Scrollgroup object (some of which is MUI4 compatible) like this:

&lt;pre&gt;
ScrollgroupObject,
  MUIA_Scrollgroup_AutoBars, TRUE,
  MUIA_Scrollgroup_Contents, VGroupV,
    Child, TextObject,
      MUIA_Text_Contents, &quot;insert your text here&quot;,
      MUIA_Text_Copy, TRUE,
      End,
    End,
  End,
&lt;/pre&gt;

The attribute MUIA_Scrollgroup_AutoBars will let the scrollgroup show the scrollbars only if they are really needed, i.e. the contents' dimensions are larger than the scrollgroup's dimensions. This attribute is available in MUI4 only like MUIA_Text_Copy, MUI3 will silently ignore it and always show the scrollbars.

Second, the attribute MUIA_Text_Copy instructs Text.mui to keep a copy of your text. This makes it possible to free() the text given to MUIA_Text_Contents after object creation of after set() and it also allows you to modify the text without risking any graphical glitches due to redraw operations while the text is still modified.

However, your text will always be displayed exactly as you specify it. This means that you need to insert line breaks yourself.

If using FloattextObject or TextEditorObject, then no matter the initial contents, the initial size is always three lines of text (which is the minimum space needed by the scrollbar + arrows), but it is at least vertically scrollable. Also, the text is word-wrapped.

Since Floattext.mui inserts line breaks itself you cannot expect a variable height, because the text's height depends on the object's width. You can enforce a certain object height by using something like MUIA_FixHeightTxt, &quot;\n\n\n\n&quot;. This will give you a fixed height of four lines while respecting the object's font.

Floattext.mui is a subclass of List.mui and as such has no restrictions on its dimensions, except you enforce them, i.e. by using MUIA_FixHeightTxt or by subclassing Floattext.mui yourself with a restricting implementation of MUIM_AskMinMax. MUI cannot just resize an object to display the entire initial content, because the content is arbitrary. It may be zero lines, but it may be a million lines. What should the initial size be in this case? Of course you can override MUIM_AskMinMax and return the dimensions which fit you best, but you must be prepared and accept that MUI will adapt the actual dimensions of the object within the limits that your (or the default) MUIM_AskMinMax method returns.

If want to the Floattext object to be resizeable then you must make the label resizeable as well by adding at least one space object above or below the label object like this:

Child, VGroup, Child, Label2(&quot;FloattextObject&quot;), Child, VSpace(0), End,

This will give you a top aligned label. Placing the label after the VSpace(0) object will make it bottom aligned. Using VCenter() will give you a vertically centered label. Choose the solution which fits your needs best.

Have a look at MUI's demo application MUI-Demo. It uses Floattext objects in every single window.

&lt;pre&gt;
MUIA_Text_Contents
MUIA_Text_PreParse
MUIA_Text_SetMax
MUIA_Text_SetMin
MUIA_Text_SetVMax
&lt;/pre&gt;

====Fonts====

try putting SetFont(_font(obj)); in your MUIM_Draw.

In OM_NEW you should set MUIA_Font to one of the predefined values (the MUIV_Font_XXXXXX values) and mui will open the font for you and make it accessible using _font(obj)

In MUIM_Draw, SetFont() to my fonts opened in MUIM_Setup. If SetFont(_font(obj)) otally lose user-settable-fonts. You are not allowed to change settings of _rp( obj ) directly! So make sure you are working on a copy of original rastport and then set fonts, colours or whatever.

&lt;pre&gt;
struct RastPort rp1 = *_rp( obj );
struct RastPort *rp = &amp;rp1;

SetAPen( rp, 0 );
&lt;/pre&gt;

The same applies to normal gadgetclass BOOPSI objects, where before drawing anything you have to ObtainGIRPort(), draw and then ReleaseGIRPort()...

MUICFG_Font_Fixed

====Gadgets====

MUIM_Import/Export and handle the loading and saving yourself. The advantages are that you don't need to create, and call MUIM_Export for the pages that the user doesn't visit, as you'll export the settings (from the created/visited pages) into an already filled dataspace object (loaded during program startup) - which should save both time, memory and complexity. Another advantage is that it makes it very easy to add options such as &quot;Reset to defaults&quot;, &quot;Restore&quot; etc.

Two functions which should make it easier to save/read IFF files into dataspace objects.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
VOID LoadDataspace (STRPTR file, Object *dataspace)
{
BPTR fh;
if(fh = Open(file, MODE_OLDFILE))
{
struct IFFHandle *iff;
if(iff = AllocIFF())
{
InitIFFasDOS(iff);
iff-&gt;iff_Stream = (ULONG)fh;
if(!OpenIFF(iff, IFFF_READ))
{
if(!StopChunk(iff, 'PREF', 'IPRB'))
{
if(!ParseIFF(iff, IFFPARSE_SCAN))
DoMethod(dataspace, MUIM_Dataspace_ReadIFF, iff);
}
CloseIFF(iff);
}
FreeIFF(iff);
}
Close(fh);
}
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
VOID SaveDataspace (STRPTR file, Object *dataspace, Object *app)
{
BOOL retry;
do {

retry = FALSE;
BPTR fh;
if(fh = Open(file, MODE_NEWFILE))
{
struct IFFHandle *iff;
if(iff = AllocIFF())
{
InitIFFasDOS(iff);
iff-&gt;iff_Stream = (ULONG)fh;
if(!OpenIFF(iff, IFFF_WRITE))
{
if(!PushChunk(iff, 'PREF', 'FORM', IFFSIZE_UNKNOWN))
DoMethod(dataspace, MUIM_Dataspace_WriteIFF, iff, 0, 'IPRB');

CloseIFF(iff);
}
FreeIFF(iff);
}
Close(fh);
}
else
{
UBYTE buf[84];
Fault(IoErr(), &quot;DOS&quot;, buf, 84);
retry = MUI_Request(app, NULL, 0L, &quot;Error&quot;, &quot;_Retry|_Cancel&quot;, &quot;\33cError saving:\n%s\n\n%s&quot;, file, buf);
}

} while(retry);
}
&lt;/syntaxhighlight&gt;

One object can't belong to two parents.

How does one insure free pens being allocated? I am running most applications on 16 bit screens. Not sure what is required but I would think there should be some way to have some free. What/how does on &quot;free&quot; pens? 
On True/Hi color screens You may expect to have unlimited number of free pens (or at least 65536/16777216 pens), because you can change the color of every single pixel without affecting the rest. But unfortunately all RastPort rendering functions rely on pen scheme and pen fields in RastPort are only 8-bit wide. It gives you only 256 pens.

Tried to use the MUIA_Bitmap_SourceColors and the MUIA_Bitmap_Precision but all I get is a big black rectangle in place of the discoloured image. Did you set MUIA_Bodychunk_Depth to 5 and MUIA_Bodychunk_Masking to 0
(but check if you save the brush *without* mask plane)? And remember that you should repeat R, G, B values in every byte of a longword, so for example some colour like R=$A5, G=$32, B=$0A, in palette data it looks like $A5A5A5A5,$32323232,$0A0A0A0A. So every palette entry takes 12 bytes.

You need to set the MUIA_Window_UseBottomBorderScroller (or whatever side you want) on the window. Then create a Prop Object and set the MUIA_Prop_UseWinBorder to the corresponding side(s) that you did in the window. Then just set up a notification on the prop object to listen for changes in MUIA_Prop_First. 
When you place the one on the right and open the window, MUI opens the window the smallest possible and doesn't draw any of the other objects that should be in the window.

====dtpic Datatypes====

If you would like to get a pointer to the bitmap that holds the data of the picture or a way to copy it to your own bitmap but all Zune attributes did not work.

In that case you will want to use datatypes.library directly. Dtpic AFAIK is just for easily including datatype images into MUI/Zune GUIs (as button imagery, in listviews and so on...).

If AROS supports the superbitmap window refresh method then you can. For a non-borderless window you will probably want to make it gimmezerozero (gzz) as well so that the borders and window contents have separate layers (uses slightly more memory). 
That being said just blitting the bitmap into the window is probably a simpler and more portable solution.

How to &quot;convert&quot; e.g. a png image to a bitmap structure (datatypes?). DTpic.mui is your friend. 
Using picture.datatype and then blitting bitmap to object rastport in MUIM_Draw.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
Child, image_button = MakeButton(&quot;PROGDIR:Imagesg/test_but.png&quot;, 't',&quot;\33uT\33nest Button&quot;),

static APTR MakeButton(UBYTE *Image, UBYTE Key, UBYTE *Help)
{
return(MUI_NewObject(&quot;Dtpic.mui&quot;,
MUIA_Dtpic_Name,Image,
MUIA_InputMode, MUIV_InputMode_RelVerify,
MUIA_ControlChar, Key,
MUIA_Background, MUII_ButtonBack,
MUIA_ShortHelp, Help,
PropFrame,TRUE,
ImageButtonFrame,
TAG_DONE));
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
if(app)
{
   struct BitMapHeader *bmhd;
   struct BitMap *bitmap;
   Object *datatype_obj;       /* pointer to the Datatype Object          */
   Object *bitmap_obj;         /* a mui BitmapObject                      */
   Object *list_obj;           /* the one that should be used in the list */

   if(datatype_obj = NewDTObject(&quot;Images/www.iff&quot;,
      DTA_SourceType , DTST_FILE,
      DTA_GroupID    , GID_PICTURE,
      TAG_DONE))
   {
      if(DoMethod(datatype_obj, DTM_PROCLAYOUT, NULL, 1))
      {
         get(datatype_obj, PDTA_BitMapHeader, &amp;bmhd);
         GetDTAttrs(datatype_obj, PDTA_DestBitMap, &amp;bitmap, TAG_DONE);
         if(!bitmap)
            GetDTAttrs(datatype_obj, PDTA_BitMap, &amp;bitmap, TAG_DONE);

         if(bitmap_obj = BitmapObject,
            MUIA_Bitmap_SourceColors  , xget(datatype_obj, PDTA_CRegs),
            MUIA_Bitmap_Width         , bmhd-&gt;bmh_Width,
            MUIA_Bitmap_Height        , bmhd-&gt;bmh_Height,
            MUIA_FixWidth             , bmhd-&gt;bmh_Width,
            MUIA_FixHeight            , bmhd-&gt;bmh_Height,
            MUIA_Bitmap_Transparent   , 0,
            MUIA_Bitmap_Bitmap        , bitmap,
            End)
         {
            list_obj = (Object *)DoMethod(LV_ButtonBank, MUIM_List_CreateImage, bitmap_obj, NULL);
         }
      }
   }
}
&lt;/syntaxhighlight&gt;

in MUI4.0

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
Child, zoneimage = (Object *) MUI_NewObject(MUIC_Dtpic,
				MUIA_Dtpic_Name, &quot;PROGDIR:resource/zone_local.png&quot;,
				TAG_DONE),
					
DEFSMETHOD(OWBWindow_UpdateZone)
{
	GETDATA;

	char *image;

	switch(msg-&gt;zone)
	{
		default:
		case MV_OWBBrowser_Zone_Local:
			image = &quot;PROGDIR:resource/zone_local.png&quot;;
			break;
		case MV_OWBBrowser_Zone_Internet:
			image = &quot;PROGDIR:resource/zone_internet.png&quot;;
			break;
	}

	set(data-&gt;zoneimage, MUIA_Dtpic_Name, image);

	return 0;
}
&lt;/syntaxhighlight&gt;

i.e. by default we set zone_local image, and then by notification calls updatezone when the attribute is set. And it should changes (image i mean), but did't not. I see that i am in the Zone_Internet (by printfs), but image not sets. Problems with 3.9

===Removal===

&lt;pre&gt;
void ExitClasses(void)
{
    if (NewList)
	{
        MUI_DeleteCustomClass(NewList);
		NewList = NULL;
	}
}

BOOL InitClasses(void)
{
    NewList = MUI_CreateCustomClass(NULL,MUIC_NList ,NULL,sizeof(struct NewList_Data),&amp;NewList_Dispatcher);

	if (NewList) return(TRUE);
	else        return FALSE;
}
&lt;/pre&gt;

Another thing, which your compiler should notice immediately, is that MyCustomClass is struct IClass * and assigning Object * to it is very, very wrong, and should effect crash at MUI_DeleteCustomClass()...

&lt;pre&gt;
#define MyCustomObject NewObject(MyCustomClass-&gt;mcc_Class,NULL,

Object *mycustomobject;
mycustomobject = MyCustomObject, End;
if( mycustomobject != NULL )
{
app = ApplicationObject, [... ]
End;
if( app != NULL )
{
[...]
MUI_DisposeObject( app );
}
MUI_DisposeObject( mycustomobject );
}
&lt;/pre&gt;

Or preferably you should subclass Application.mui class and do your non-visible code there... That's the best way to handle it IMHO... This way main program code will be almost untouched and going back to using standard Application.mui within seconds, just rename MyApplicationObject to ApplicationObject (always define such macros instead of writing NewObject() directly!)

Objects are removed using OM_REMMEMBER method (must use parent object of course)

==References==

http://alfie.altervista.org/rxmui/rxmuidoc/classes.html

http://amiga.sourceforge.net/amigadevhelp/phpwebdev.php

When one of the qualifier (shift, ctrl, alt) keys is clicked then the opposite key should get the same state. I tried in the callback function: 
&lt;pre&gt;
BOOL shift = XGET(data-&gt;keybutton[96], MUIA_Pressed) |
XGET(data-&gt;keybutton[97], MUIA_Pressed);

NNSET(data-&gt;keybutton[96], MUIA_Pressed, shift);
NNSET(data-&gt;keybutton[97], MUIA_Pressed, shift);
&lt;/pre&gt;
Pressing the qualifier keys on the keyboard should act as if the button was clicked. I've therefore added an event handler method. It works so far as the visual state of the buttons is changed. Problem is that SET(keyobj, MUIA_Pressed, state) in that event method doesn't trigger the callback hook.

Try MUIA_Selected, instead of MUIA_Pressed (which is really just a thing to be used for notification, not a real attribute). You'll also have to change code logic, because once the two SHIFT buttons are selected, it won't be possible to unselected them (&quot;shift&quot; var would always be TRUE).

Networking with a non-blocking recv(), start with one task and make all my interfaces push-based. 
That is, no-one will call recv() but instead be called with the data received from a socket (when it arrives). 
So in your main-loop you wait for both sockets and user events and distribute these to the proper receiver (where the latter would be done by MUI). 
The reason for this approach is to simplify code (eliminate the need to lock resources/data with semaphores etc), and also because found  out that spawning tasks had a noticeable overhead (but you could keep one network manager running all the time to get by this), not to mention that if you receive data on 8 sockets (each having its own process) then your program will be represented with 9 total tasks and thus if another program needs cpu-time it'll only get 1/10th of the time, where your program will get 9/10th, unless you fiddle with the priority of your tasks but then other problems appear. 
If the data you receive needs to be parsed in some way you may at first find it irritating to have to write your parser as a state-machine, but these also have advantages IMO. For example it makes it very easy to add filters to the data stream or create virtual data on the fly...

Basically you need a socket operating in the non-blocking &amp; asynchronous mode. This prevents GUI being locked while accessing network. Another step is allocate signal bit for bsdsocket and use GetSocketEvent() to find out network actions without braindead select() or WaitSelect() functions. So that whenever network signal is set you call GetSocketEvent() in loop. This GetSocketEvent() returns socket descriptor ID and possible events occurred. 
Avoid GetSocketEvent() and its minion like it was the bubonic plague!!!!!!!! As it turned out, it only
works under Miami. Even though AmiTCP copied the API from M$, it never worked correctly. Use WaitSelect() instead of Wait() in your MUI main loop. See STRICQ 2 src. 
How do you receive data from sockets? Is there a way to associate a signal to a socket? 
You can associate a signal with a socket by using SocketBaseTags(). Use WaitSelect() in the STRICQ v2 socket code. But in v1, used a signal.

You can encapsulate internet client in MUI application subclass, create some useful methods and attributes like
MUIM_NetApplication_Connect/Disconnect/Send/Receive, and then when user press Connect/Disconnect button, call these methods in notification or callback function (so if NetApplication connected you will disable Connect, and
enable Disconnect etc. gadgets). And so on. Never connect to the internet immediately in OM_NEW, that would be stupid as well as creating needed subprocess in there (which from other side might be not good idea). It can wait then as long as application sends the connect signal or message and then do it's network job, until it receives MUIM_NetApplication_Disconnect method.. How to... merge bsdsocket.library and muimaster.library in single, nicely OOP, application.

==Examples==

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/*
    Copyright © 2002, The AROS Development Team.
    All rights reserved.

    $Id: aircos_server_gui.c 30794 2009-03-08 02:19:07Z neil $
*/

//#include    &lt;exec/types.h&gt;
#include    &lt;stdlib.h&gt;
#include    &lt;stdio.h&gt;
#include    &lt;string.h&gt;

#include    &lt;proto/alib.h&gt;
#include    &lt;proto/exec.h&gt;
#include    &lt;proto/dos.h&gt;
#include    &lt;proto/intuition.h&gt;
#include    &lt;proto/muimaster.h&gt;
#include    &lt;proto/utility.h&gt;

#include    &lt;dos/dos.h&gt;
#include    &lt;intuition/gadgetclass.h&gt;
#include    &lt;intuition/icclass.h&gt;
#include    &lt;clib/alib_protos.h&gt;

#include &lt;libraries/mui.h&gt;
#include &lt;mui/NListtree_mcc.h&gt;
#include &lt;mui/NListview_mcc.h&gt;
#include &lt;mui/NList_mcc.h&gt;

#include &quot;aircos_global.h&quot;
#include &quot;locale.h&quot;

extern struct AiRcOS_internal *AiRcOS_Base;
struct List                   aircos_Prefs_ServerNetworks;
struct List                   aircos_Prefs_Servers;
struct aircos_servernode      *aircos_Prefs_ServerActive;
struct Hook                   aircos_serversave_hook;
struct Hook                   aircos_networklistupdate_hook;
struct Hook                   aircos_serverlistupdate_hook;
struct Hook                   aircos_chooseserver_hook;

BOOL                          aircos_Prefs_ServersLoaded = FALSE;

Object	                     *input_server_address = NULL;
Object	                     *input_server_port =  NULL;
Object	                     *input_server_description =  NULL;
Object	                     *input_server_network =  NULL;
Object	                     *input_server_pass =  NULL;

Object                        *select_dropboxgrp_network = NULL;
Object                        *select_dropbox_network = NULL;
Object                        *select_dropboxgrp_server = NULL;
Object                        *select_dropbox_server = NULL;

STRPTR	                     network_list_empty[2] =
{
  {&quot;&lt;List Empty&gt;&quot;},
  NULL
};
STRPTR	                     server_list_empty[2] =
{
  {&quot;&lt;List Empty&gt;&quot;},
  NULL
};
Object	                     *servermodWin;
STRPTR	                     *network_list;
STRPTR	                     *server_list;

//network_list_empty[0] = &quot;&lt;List Empty&gt;&quot;;		//MSG(MSG_LIST_EMPTY);
//network_list_empty[1] = NULL;

//server_list_empty[0] = &quot;&lt;List Empty&gt;&quot;;		//MSG(MSG_LIST_EMPTY);
//server_list_empty[1] = NULL;

#define AIRCOS_DEF_SERVERSFILE &quot;servers.dat&quot;

aircosApp_LoadServers()
{
  aircos_Prefs_ServersLoaded = TRUE;
}

struct aircos_networknode *aircosApp_FindServerNetworkNode(char * findNetwork)
{
  struct aircos_networknode *current_Node = NULL;
  ForeachNode(&amp;aircos_Prefs_ServerNetworks, current_Node)
  {
D(bug(&quot;[AiRcOS](FindServerNetworkNode) Checking against record for '%s'\n&quot;, current_Node-&gt;ann_Network));
      if (strcasecmp(current_Node-&gt;ann_Network, findNetwork)==0) return current_Node;
  }
  return NULL;
}

struct aircos_servernode  *aircosApp_FindServerNode(char * findServer)
{
struct aircos_servernode  *current_Node = NULL;
  ForeachNode(&amp;aircos_Prefs_Servers, current_Node)
  {
D(bug(&quot;[AiRcOS](FindServerNode) Checking against record for '%s'\n&quot;, current_Node-&gt;asn_Server));
      if (strcasecmp(current_Node-&gt;asn_Server, findServer)==0) return current_Node;
  }
  return NULL;
}

AROS_UFH3(void, chooseserver_func,
   AROS_UFHA(struct Hook *, unused_hook, A0),
   AROS_UFHA(APTR, obj, A2),
   AROS_UFHA(struct IRC_Channel_Priv  *, hook_channel_arg, A1 ))
{
   AROS_USERFUNC_INIT
D(bug(&quot;[AiRcOS] chooseserver_func()\n&quot;));
  ULONG                      currentPrefsServerID;
  get(select_dropbox_server, MUIA_Cycle_Active, &amp;currentPrefsServerID);

  struct aircos_servernode *currentPrefsServer = NULL;
  if (!(currentPrefsServer = aircosApp_FindServerNode(server_list[currentPrefsServerID])))
  {
D(bug(&quot;[AiRcOS] chooseserver_func: Couldnt find Server Node!\n&quot;));
    return;
  }

  aircos_Prefs_ServerActive = currentPrefsServer;

  AROS_USERFUNC_EXIT
};

AROS_UFH3(void, updatenetworklist_func,
   AROS_UFHA(struct Hook *, unused_hook, A0),
   AROS_UFHA(APTR, obj, A2),
   AROS_UFHA(struct IRC_Channel_Priv  *, hook_channel_arg, A1 ))
{
   AROS_USERFUNC_INIT
D(bug(&quot;[AiRcOS] updatenetworklist_func()\n&quot;));
  struct aircos_networknode *currentPrefsNetwork = NULL;
  ULONG                      prefsNetworkCount = 0;
  ULONG                      setprefsNetworkActive = 0;
  Object                     *new_dropbox_network = NULL;
  
  ForeachNode(&amp;aircos_Prefs_ServerNetworks, currentPrefsNetwork)
  {
      prefsNetworkCount++;
      if (aircos_Prefs_ServerActive)
        if (strcasecmp(currentPrefsNetwork-&gt;ann_Network, aircos_Prefs_ServerActive-&gt;asn_Network-&gt;ann_Network)==0)
        {
          setprefsNetworkActive = prefsNetworkCount -1;
        }
  }

D(bug(&quot;[AiRcOS] updatenetworklist_func: %d network nodes\n&quot;, prefsNetworkCount));
  
  if (prefsNetworkCount &gt; 0)
  {
    if (network_list != network_list_empty) {
      FreeVec(network_list);
    }
    
    if ((network_list = AllocVec(sizeof(IPTR) * prefsNetworkCount+1, MEMF_CLEAR|MEMF_PUBLIC)))
    {
      int loop_count = 0;

      ForeachNode(&amp;aircos_Prefs_ServerNetworks, currentPrefsNetwork)
      {
        network_list[loop_count] = currentPrefsNetwork-&gt;ann_Network;
        loop_count++;
      }
    }
    else
    {
D(bug(&quot;[AiRcOS] updatenetworklist_func: ERROR - couldnt allocate memory for network name pointer table\n&quot;));
      network_list = network_list_empty;
    }
  } else if (network_list != network_list_empty) {
    FreeVec(network_list);
    network_list = network_list_empty; 
  }

  if (!(new_dropbox_network = MUI_MakeObject(MUIO_Cycle, NULL, network_list)))
  {
D(bug(&quot;[AiRcOS] updatenetworklist_func: Failed to create Network dropdown\n&quot;));
    return NULL;
  }

  if (DoMethod(select_dropboxgrp_network, MUIM_Group_InitChange))
  {
    DoMethod(select_dropboxgrp_network, OM_REMMEMBER, select_dropbox_network);
    DoMethod(select_dropboxgrp_network, OM_ADDMEMBER, new_dropbox_network);
    DoMethod(select_dropboxgrp_network, MUIM_Group_ExitChange);
    select_dropbox_network = new_dropbox_network;
  }

  DoMethod(select_dropbox_network, MUIM_NoNotifySet, MUIA_Cycle_Active, setprefsNetworkActive);
  DoMethod
  (
      select_dropbox_network, MUIM_Notify, MUIA_Cycle_Active, MUIV_EveryTime,
      (IPTR) AiRcOS_Base-&gt;aircos_app, 3, MUIM_CallHook, &amp;aircos_serverlistupdate_hook, NULL
  );
        
  AROS_USERFUNC_EXIT
};

AROS_UFH3(void, updateserverlist_func,
   AROS_UFHA(struct Hook *, unused_hook, A0),
   AROS_UFHA(APTR, obj, A2),
   AROS_UFHA(struct IRC_Channel_Priv  *, hook_channel_arg, A1 ))
{
   AROS_USERFUNC_INIT
D(bug(&quot;[AiRcOS] updateserverlist_func()\n&quot;));
  struct aircos_servernode   *currentPrefsServer = NULL;
  ULONG                      prefsNetworkServerCount = 0;
  ULONG                      setprefsServerActive = 0;
  Object                     *new_dropbox_server = NULL;

  ULONG                      currentPrefsNetworkID;
  get(select_dropbox_network, MUIA_Cycle_Active, &amp;currentPrefsNetworkID);

  struct aircos_networknode *currentPrefsNetwork = NULL;
  if (!(currentPrefsNetwork = aircosApp_FindServerNetworkNode(network_list[currentPrefsNetworkID])))
  {
D(bug(&quot;[AiRcOS] updateserverlist_func: Couldnt find Network Node!\n&quot;));
    return;
  }

  ForeachNode(&amp;aircos_Prefs_Servers, currentPrefsServer)
  {
      if (strcasecmp(currentPrefsServer-&gt;asn_Network-&gt;ann_Network, currentPrefsNetwork-&gt;ann_Network)==0)
      {
        prefsNetworkServerCount++;
        if (aircos_Prefs_ServerActive)
          if (strcasecmp(currentPrefsServer-&gt;asn_Server, aircos_Prefs_ServerActive-&gt;asn_Server)==0)
          {
            setprefsServerActive = prefsNetworkServerCount -1;
          }
      }
  }

D(bug(&quot;[AiRcOS] updateserverlist_func: %d server nodes for network '%s'\n&quot;, prefsNetworkServerCount, currentPrefsNetwork-&gt;ann_Network));
  
  if (prefsNetworkServerCount &gt; 0)
  {
    if (server_list != server_list_empty) {
      FreeVec(server_list);
    }
    
    if ((server_list = AllocVec(sizeof(IPTR) * prefsNetworkServerCount+1, MEMF_CLEAR|MEMF_PUBLIC)))
    {
      int loop_count = 0;

      ForeachNode(&amp;aircos_Prefs_Servers, currentPrefsServer)
      {
        if (strcasecmp(currentPrefsServer-&gt;asn_Network-&gt;ann_Network, currentPrefsNetwork-&gt;ann_Network)==0)
        {
          server_list[loop_count] = currentPrefsServer-&gt;asn_Server;
          loop_count++;
        }
      }
    }
    else
    {
D(bug(&quot;[AiRcOS] updateserverlist_func: ERROR - couldnt allocate memory for server name pointer table\n&quot;));
      server_list = server_list_empty;
    }
  } else if (server_list != server_list_empty) {
    FreeVec(server_list);
    server_list = server_list_empty; 
  }

  if (!(new_dropbox_server = MUI_MakeObject(MUIO_Cycle, NULL, server_list)))
  {
D(bug(&quot;[AiRcOS] updateserverlist_func: Failed to create Server dropdown\n&quot;));
    return NULL;
  }

  if (DoMethod(select_dropboxgrp_server, MUIM_Group_InitChange))
  {
    DoMethod(select_dropboxgrp_server, OM_REMMEMBER, select_dropbox_server);
    DoMethod(select_dropboxgrp_server, OM_ADDMEMBER, new_dropbox_server);
    DoMethod(select_dropboxgrp_server, MUIM_Group_ExitChange);
    select_dropbox_server = new_dropbox_server;
  }

  DoMethod(select_dropbox_server, MUIM_NoNotifySet, MUIA_Cycle_Active, setprefsServerActive);

  AROS_USERFUNC_EXIT
};

AROS_UFH3(void, serversave_func,
   AROS_UFHA(struct Hook *, unused_hook, A0),
   AROS_UFHA(APTR, obj, A2),
   AROS_UFHA(struct IRC_Channel_Priv  *, hook_channel_arg, A1 ))
{
   AROS_USERFUNC_INIT
D(bug(&quot;[AiRcOS] serversave_func()\n&quot;));

  struct aircos_networknode *newsaveNetwork = NULL;
  char                      *newsaveNetwork_name;
  BOOL                      newsaveNetwork_update = FALSE;

  struct aircos_servernode  *newsaveServer = NULL;
  char                      *newsaveServer_name;
  BOOL                      newsaveServer_update = FALSE;

   get( input_server_network, MUIA_String_Contents, &amp;newsaveNetwork_name);
   get( input_server_address, MUIA_String_Contents, &amp;newsaveServer_name);

  if (!(newsaveNetwork = aircosApp_FindServerNetworkNode(newsaveNetwork_name)))
  {
D(bug(&quot;[AiRcOS](serversave_func) created new network node for '%s'\n&quot;, newsaveNetwork_name));
     newsaveNetwork = AllocVec(sizeof(struct aircos_networknode), MEMF_CLEAR|MEMF_PUBLIC);
     newsaveNetwork-&gt;ann_Network = AllocVec(strlen(newsaveNetwork_name)+1, MEMF_CLEAR|MEMF_PUBLIC);
     CopyMem(newsaveNetwork_name, newsaveNetwork-&gt;ann_Network, strlen(newsaveNetwork_name)+1);

     AddTail((struct List *)&amp;aircos_Prefs_ServerNetworks, (struct Node *)&amp;newsaveNetwork-&gt;ann_Node);
     newsaveNetwork_update = TRUE;
  }
  newsaveNetwork-&gt;ann_ServerCount += 1;
D(bug(&quot;[AiRcOS](serversave_func) %s Network node server count = %d\n&quot;, newsaveNetwork-&gt;ann_Network, newsaveNetwork-&gt;ann_ServerCount));

  if (!(newsaveServer = aircosApp_FindServerNode(newsaveServer_name)))
  {
D(bug(&quot;[AiRcOS](serversave_func) created new server node for '%s'\n&quot;, newsaveServer_name));
     newsaveServer = AllocVec(sizeof(struct aircos_servernode), MEMF_CLEAR|MEMF_PUBLIC);
     newsaveServer-&gt;asn_Server = AllocVec(strlen(newsaveServer_name)+1, MEMF_CLEAR|MEMF_PUBLIC);
     CopyMem(newsaveServer_name, newsaveServer-&gt;asn_Server, strlen(newsaveServer_name)+1);
     newsaveServer-&gt;asn_Network = newsaveNetwork;
     get( input_server_port, MUIA_String_Integer, &amp;newsaveServer-&gt;asn_Port);

#warning &quot;TODO: we need to store the password also here ..&quot;

     AddTail((struct List *)&amp;aircos_Prefs_Servers, (struct Node *)&amp;newsaveServer-&gt;asn_Node);
     newsaveServer_update = TRUE;
  }
  else
  {
D(bug(&quot;[AiRcOS](serversave_func) node already exists for server '%s'\n&quot;, newsaveServer_name));
  }

  aircos_Prefs_ServerActive = newsaveServer;

  set( servermodWin, MUIA_Window_Open, FALSE);

  if (newsaveNetwork_update) CallHookPkt(&amp;aircos_networklistupdate_hook, obj, hook_channel_arg);
  if (newsaveServer_update) CallHookPkt(&amp;aircos_serverlistupdate_hook, obj, hook_channel_arg);

  AROS_USERFUNC_EXIT
};

Object	*aircos_showServerConnect()
{
D(bug(&quot;[AiRcOS] showServerConnect()\n&quot;));
  if (aircos_Prefs_ServersLoaded)
  {
D(bug(&quot;[AiRcOS](showServerConnect) Server windows already configured!\n&quot;));
    return NULL;
  }

   Object   *tmp_connectWin = NULL;

  NewList((struct List *)&amp;aircos_Prefs_ServerNetworks);
  NewList((struct List *)&amp;aircos_Prefs_Servers);

	Object	*butt_addServer = NULL;
	Object	*butt_editServer = NULL;
	Object	*butt_delServer = NULL;
	Object	*butt_serverConnect = NULL;
	Object   *butt_serverSave = NULL;

   network_list = network_list_empty;
   server_list = server_list_empty;

	if (!(select_dropbox_network = MUI_MakeObject(MUIO_Cycle, NULL, network_list)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create Network dropdown\n&quot;));
      return NULL;
	}
	
	if (!(select_dropbox_server = MUI_MakeObject(MUIO_Cycle, NULL, server_list)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create Server dropdown\n&quot;));
      return NULL;
	}

   if (!(butt_addServer = SimpleButton(&quot;Add&quot;)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create 'ADD' button\n&quot;));
      return NULL;
	}
	
   if (!(butt_editServer = SimpleButton(&quot;Edit&quot;)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create 'EDIT' button\n&quot;));
      return NULL;
	}
	
   if (!(butt_delServer = SimpleButton(&quot;Del&quot;)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create 'DEL' button\n&quot;));
      return NULL;
	}

   if (!(butt_serverConnect = SimpleButton(&quot;Connect!&quot;)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create 'CONNECT' button\n&quot;));
      return NULL;
	}

   if (!(butt_serverSave = SimpleButton(&quot;Save!&quot;)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create 'SAVE' button\n&quot;));
      return NULL;
	}

   select_dropboxgrp_network = VGroup,
                                 Child, (IPTR) select_dropbox_network,
                               End;

   select_dropboxgrp_server = VGroup,
                                Child, (IPTR) select_dropbox_server,
                              End;

	tmp_connectWin = WindowObject,
            MUIA_Window_Title, (IPTR) &quot;Connect to Server..&quot;,
            MUIA_Window_Activate, TRUE,
            MUIA_Window_Width,200,
            MUIA_Window_Height,200,
     
            WindowContents, (IPTR) VGroup,
                Child, (IPTR) HGroup,
                  GroupFrame,
					   Child, (IPTR) VGroup,
						  Child, (IPTR) LLabel(&quot;IRC Network&quot;),
						  Child, (IPTR) HGroup,
						    Child, (IPTR) HSpace(0),
						    Child, (IPTR) select_dropboxgrp_network,
						    Child, (IPTR) HSpace(0),
						  End,
					   End,
					   Child, (IPTR) HVSpace,
                End,
                Child, (IPTR) HGroup,
                  GroupFrame,
					   Child, (IPTR) VGroup,
						  Child, (IPTR) LLabel(&quot;IRC Server&quot;),
						  Child, (IPTR) HGroup,
						    Child, (IPTR) HVSpace,
						    Child, (IPTR) select_dropboxgrp_server,
						    Child, (IPTR) HVSpace,
						  End,
					   End,
  					   Child, (IPTR) HVSpace,
                End,
                Child, (IPTR) HGroup,
					   Child, (IPTR) HVSpace,
					   Child, (IPTR) butt_addServer,
					   Child, (IPTR) butt_editServer,
					   Child, (IPTR) butt_delServer,
                End,
                Child, (IPTR) butt_serverConnect,
            End,
        End;

	servermodWin = WindowObject,
        
            MUIA_Window_Title, (IPTR) &quot;Edit Server..&quot;,
            MUIA_Window_Activate, TRUE,
            MUIA_Window_Width,350,
            MUIA_Window_Height,400,
     
            WindowContents, (IPTR) VGroup,
               Child, (IPTR) VGroup,
                 GroupFrame,
                 Child, (IPTR) HGroup,
					    Child, (IPTR) LLabel(&quot;IRC Server Address&quot;),
					    Child, (IPTR) (input_server_address = StringObject,
										StringFrame,
                              MUIA_CycleChain, TRUE,
										MUIA_String_Format, MUIV_String_Format_Right,
                   End ),
                 End,
                 Child, (IPTR) HGroup,
					    Child, (IPTR) LLabel(&quot;Port&quot;),
					    Child, (IPTR) (input_server_port = StringObject,
										StringFrame,
                              MUIA_CycleChain, TRUE,
										MUIA_String_Format, MUIV_String_Format_Right,
										MUIA_String_Accept, &quot;0123456789&quot;,
										MUIA_String_Integer, 0,
					    End),
                 End,
                 Child, (IPTR) HGroup,
					    Child, (IPTR) LLabel(&quot;Server Description&quot;),
					    Child, (IPTR) (input_server_description = StringObject,
										StringFrame,
                              MUIA_CycleChain, TRUE,
										MUIA_String_Format, MUIV_String_Format_Right,
					    End),
                 End,
                 Child, (IPTR) HGroup,
					    Child, (IPTR) LLabel(&quot;IRC Network&quot;),
					    Child, (IPTR) (input_server_network = StringObject,
										StringFrame,
                              MUIA_CycleChain, TRUE,
										MUIA_String_Format, MUIV_String_Format_Right,
					    End),
                 End,
               End,
               Child, (IPTR) VGroup,
                 GroupFrame,
				     Child, (IPTR) LLabel(&quot;Enter server password here if applicable.&quot;),
                 Child, (IPTR) HGroup,
					    Child, (IPTR) LLabel(&quot;Password&quot;),
					    Child, (IPTR) (input_server_pass = StringObject,
										StringFrame,
                              MUIA_CycleChain, TRUE,
										MUIA_String_Format, MUIV_String_Format_Right,
					    End),
                 End,
               End,
               Child, (IPTR) butt_serverSave,
            End,
        End;

	if ((tmp_connectWin)&amp;&amp;(servermodWin))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Created GUI objects\n&quot;));
      DoMethod
        (
            AiRcOS_Base-&gt;aircos_app, OM_ADDMEMBER,
            (IPTR) tmp_connectWin
        );

      DoMethod
        (
            AiRcOS_Base-&gt;aircos_app, OM_ADDMEMBER,
            (IPTR) servermodWin
        );

        DoMethod
        (
            tmp_connectWin, MUIM_Notify, MUIA_Window_Open, TRUE,
            (IPTR) AiRcOS_Base-&gt;aircos_quickconnectwin, 3, MUIM_Set, MUIA_Window_Open, FALSE
        );

        DoMethod
        (
            AiRcOS_Base-&gt;aircos_quickconnectwin, MUIM_Notify, MUIA_Window_Open, TRUE,
            (IPTR) tmp_connectWin, 3, MUIM_Set, MUIA_Window_Open, FALSE
        );

        DoMethod
        (
            tmp_connectWin, MUIM_Notify, MUIA_Window_Open, FALSE,
            (IPTR) servermodWin, 3, MUIM_Set, MUIA_Window_Open, FALSE
        );

      DoMethod
        (
            butt_addServer, MUIM_Notify, MUIA_Selected, FALSE,
            (IPTR) servermodWin, 3, MUIM_Set, MUIA_Window_Open, TRUE
        );

      DoMethod
        (
            butt_editServer, MUIM_Notify, MUIA_Selected, FALSE,
            (IPTR) servermodWin, 3, MUIM_Set, MUIA_Window_Open, TRUE
        );

//      DoMethod
//        (
//            butt_delServer, MUIM_Notify, MUIA_Selected, FALSE,
//            (IPTR) servermodWin, 3, MUIM_Set, MUIA_ShowMe, FALSE
//        );

        DoMethod
        (
            tmp_connectWin, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
            (IPTR) tmp_connectWin, 3, MUIM_Set, MUIA_Window_Open, FALSE
        );
        
        DoMethod
        (
            servermodWin, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
            (IPTR) servermodWin, 3, MUIM_Set, MUIA_Window_Open, FALSE
        );

        DoMethod
        (
            butt_serverConnect, MUIM_Notify, MUIA_Pressed, FALSE,
                (IPTR) AiRcOS_Base-&gt;aircos_app, 3, MUIM_CallHook, &amp;AiRcOS_Base-&gt;aircos_connect_hook, NULL
        );

D(bug(&quot;[AiRcOS](showServerConnect) prepare list update hooks\n&quot;));
    
       aircos_serversave_hook.h_MinNode.mln_Succ = NULL;
       aircos_serversave_hook.h_MinNode.mln_Pred = NULL;
       aircos_serversave_hook.h_Entry = HookEntry;
       aircos_serversave_hook.h_SubEntry = (void *)serversave_func;

       aircos_networklistupdate_hook.h_MinNode.mln_Succ = NULL;
       aircos_networklistupdate_hook.h_MinNode.mln_Pred = NULL;
       aircos_networklistupdate_hook.h_Entry = HookEntry;
       aircos_networklistupdate_hook.h_SubEntry = (void *)updatenetworklist_func;
       
       aircos_serverlistupdate_hook.h_MinNode.mln_Succ = NULL;
       aircos_serverlistupdate_hook.h_MinNode.mln_Pred = NULL;
       aircos_serverlistupdate_hook.h_Entry = HookEntry;
       aircos_serverlistupdate_hook.h_SubEntry = (void *)updateserverlist_func;

       aircos_chooseserver_hook.h_MinNode.mln_Succ = NULL;
       aircos_chooseserver_hook.h_MinNode.mln_Pred = NULL;
       aircos_chooseserver_hook.h_Entry = HookEntry;
       aircos_chooseserver_hook.h_SubEntry = (void *)chooseserver_func;

        DoMethod
        (
            butt_serverSave, MUIM_Notify, MUIA_Pressed, FALSE,
                (IPTR) AiRcOS_Base-&gt;aircos_app, 3, MUIM_CallHook, &amp;aircos_serversave_hook, NULL
        );

        DoMethod
        (
            select_dropbox_network, MUIM_Notify, MUIA_Cycle_Active, MUIV_EveryTime,
                (IPTR) AiRcOS_Base-&gt;aircos_app, 3, MUIM_CallHook, &amp;aircos_serverlistupdate_hook, NULL
        );

        DoMethod
        (
            select_dropbox_server, MUIM_Notify, MUIA_Cycle_Active, MUIV_EveryTime,
                (IPTR) AiRcOS_Base-&gt;aircos_app, 3, MUIM_CallHook, &amp;aircos_chooseserver_hook, NULL
        );

D(bug(&quot;[AiRcOS](showServerConnect) Configured NOTIFICATIONS\n&quot;));

       set(tmp_connectWin, MUIA_Window_Open, TRUE);
       D(bug(&quot;[AiRcOS](showServerConnect) Window opened ..\n&quot;));
     }
     else
     {
      if (!(servermodWin))
      {
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create server edit window..\n&quot;));
      }
      else MUI_DisposeObject(servermodWin);
      
      if (!(tmp_connectWin))
      {
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create server selection window..\n&quot;));      
      }
      else MUI_DisposeObject(tmp_connectWin);
     }

	return tmp_connectWin;
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/*
    Copyright © 2002, The AROS Development Team.
    All rights reserved.

    $Id: mini2.c 30792 2009-03-07 22:40:04Z neil $
*/

#include &lt;exec/types.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;stdio.h&gt;
#include &lt;string.h&gt;

#include &lt;dos/dos.h&gt;
#include &lt;intuition/gadgetclass.h&gt;
#include &lt;intuition/icclass.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

/* the following should go in a single include file which then only
** constits of the public constants and members. Actually this is easiey
*/

#include &lt;libraries/mui.h&gt;

#define DEBUG 1
#include &lt;aros/debug.h&gt;

Object *app;

int main(void)
{
    Object *wnd;
    static char *radio_entries2[] = {&quot;Paris&quot;,&quot;London&quot;,NULL};

    app = ApplicationObject,
   	SubWindow, wnd = WindowObject,
    	    WindowContents, VGroup,
	Child, HGroup,
	    MUIA_InputMode, MUIV_InputMode_Immediate,
/*              MUIA_ShowSelState, FALSE, */
	    Child, ImageObject,
                MUIA_ShowSelState, FALSE,
	        MUIA_Image_FontMatch, TRUE,
	        MUIA_Image_Spec, MUII_RadioButton,
	        MUIA_Frame, MUIV_Frame_None,
   	        End,
	    Child, TextObject,
                MUIA_ShowSelState, FALSE,
	        MUIA_Text_Contents, &quot;London&quot;,
	        MUIA_Frame, MUIV_Frame_None,
	        MUIA_Text_PreParse, &quot;\33l&quot;,
	        End,
	End,
		End,
	    End,
	End;

    if (app)
    {
	ULONG sigs = 0;
/*  #if 0 */
	DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE, app, 2, MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

/*  #endif */
	set(wnd, MUIA_Window_Open, TRUE);

/*  #if 0 */
	while((LONG) DoMethod(app, MUIM_Application_NewInput, &amp;sigs) != MUIV_Application_ReturnID_Quit)
	{
	    if (sigs)
	    {
		sigs = Wait(sigs | SIGBREAKF_CTRL_C | SIGBREAKF_CTRL_D);
		if (sigs &amp; SIGBREAKF_CTRL_C) break;
		if (sigs &amp; SIGBREAKF_CTRL_D) break;
	    }
	}
/*  #endif */
	set(wnd, MUIA_Window_Open, FALSE);
	MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/*
    Copyright © 2002, The AROS Development Team.
    All rights reserved.

    $Id: dirlist.c 30792 2009-03-07 22:40:04Z neil $
*/

#include &lt;exec/types.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;stdio.h&gt;
#include &lt;string.h&gt;

#include &lt;dos/dos.h&gt;
#include &lt;intuition/gadgetclass.h&gt;
#include &lt;intuition/icclass.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

/* the following should go in a single include file which then only
** constits of the public constants and members. Actually this is easiey
*/

#include &lt;libraries/mui.h&gt;

struct Library *MUIMasterBase;

Object *app;

int main(void)
{
    Object *wnd, *str, *dirlist, *page;
    
    MUIMasterBase = (struct Library*)OpenLibrary(&quot;muimaster.library&quot;,0);

    app = ApplicationObject,
   	SubWindow, wnd = WindowObject,
    	    MUIA_Window_Title, &quot;dirlist&quot;,
	    MUIA_Window_Activate, TRUE,

    	    WindowContents, VGroup,
	    	MUIA_Background, MUII_GroupBack,
		Child, ListviewObject,
		    MUIA_Listview_List, dirlist = DirlistObject,
    	    	    	InputListFrame,
		    	End,
		    End,
		Child, HGroup,
		    Child, str = StringObject,
			StringFrame,
			MUIA_String_Contents, (IPTR)&quot;SYS:&quot;,
			End,
		    Child, page = PageGroup,
		    	MUIA_Weight, 0,
			MUIA_FixWidthTxt, (IPTR)&quot;AA&quot;,
		    	Child, ColorfieldObject,
			    MUIA_Colorfield_Red, 0xFFFFFFFF,
			    MUIA_Colorfield_Green, 0,
			    MUIA_Colorfield_Blue, 0,
			    End,
		    	Child, ColorfieldObject,
			    MUIA_Colorfield_Red, 0xFFFFFFFF,
			    MUIA_Colorfield_Green, 0xFFFFFFFF,
			    MUIA_Colorfield_Blue, 0,
			    End,
		    	Child, ColorfieldObject,
			    MUIA_Colorfield_Red, 0,
			    MUIA_Colorfield_Green, 0x66666666,
			    MUIA_Colorfield_Blue, 0,
			    End,
		    	End,
		    End,
		End,
	    End,
	End;

    if (app)
    {
	ULONG sigs = 0;

	DoMethod
        (
            wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE, (IPTR) app, 
            2, MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit
        );

    	DoMethod(str, MUIM_Notify, MUIA_String_Acknowledge, MUIV_EveryTime,
	    	 (IPTR)dirlist, 3, MUIM_Set, MUIA_Dirlist_Directory, MUIV_TriggerValue);
		 
    	DoMethod(dirlist, MUIM_Notify, MUIA_Dirlist_Status, MUIV_EveryTime,
	    	 (IPTR)page, 3, MUIM_Set, MUIA_Group_ActivePage, MUIV_TriggerValue);
		 
    	set(dirlist, MUIA_Dirlist_Directory, &quot;SYS:&quot;);
	
	set(wnd,MUIA_Window_Open,TRUE);

	while (DoMethod(app, MUIM_Application_NewInput, (IPTR) &amp;sigs) != MUIV_Application_ReturnID_Quit)
	{
	    if (sigs)
	    {
		sigs = Wait(sigs | SIGBREAKF_CTRL_C | SIGBREAKF_CTRL_D);
		if (sigs &amp; SIGBREAKF_CTRL_C) break;
		if (sigs &amp; SIGBREAKF_CTRL_D) break;
	    }
	}

	MUI_DisposeObject(app);
    }

    CloseLibrary(MUIMasterBase);
    
    return 0;
}
&lt;/syntaxhighlight&gt;

WaitSelect() needs a pointer to your signal mask. So you need to do something like: 
&lt;pre&gt;
sigs |= SIGBREAKF_CTRL_C;
ret = WaitSelect(s+1, &amp;rdfs, NULL, NULL, &amp;sigs);
&lt;/pre&gt;
Then 'sigs' should contain the bits normally returned by Wait().

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/*
 * Amiga Generic Set - set of libraries and includes to ease sw development for all Amiga platforms
 * Copyright (C) 2004-2008 Tomasz Wiszkowski Tomasz.Wiszkowski at gmail.com.
 * 
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU Lesser General Public License
 * as published by the Free Software Foundation; either version 2.1
 * of the License, or (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program; if not, write to the Free Software
 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
 */

#include &quot;MUIPictureClass.h&quot;
#include &lt;Generic/LibrarySpool.h&gt;
#include &lt;libclass/intuition.h&gt;
#include &lt;libclass/muimaster.h&gt;
#include &lt;libraries/mui.h&gt;
#include &lt;libclass/utility.h&gt;

using namespace GenNS;

#define __NOGLOBALIFACE__
#include &lt;proto/graphics.h&gt;

   static struct Library *GfxBase = 0;
#ifdef __AMIGAOS4__
   static struct GraphicsIFace *IGraphics = 0;
#endif

   MUICustomClassT&lt;MUIPictureClass&gt; *MUIPictureClass::muiclass = 0;
   static int            openCount = 0;

MUIPictureClass::MUIPictureClass(IClass *cls)
{
   openCount++;
   parent   = cls;
   image1   = &quot;&quot;;
   image2   = &quot;&quot;;
   width    = 64;
   height   = 48;
   dtimg1   = 0;
   dtimg2   = 0;
   dt       = DatatypesIFace::GetInstance(44);
   if (dt == 0)
   {
      request(&quot;Warning&quot;, &quot;This program requires datatypes.library v44 or later\nGraphical buttons will not be displayed.&quot;, &quot;Continue&quot;, 0);
   }

   if (GfxBase == 0)
   {
      GfxBase = Exec-&gt;OpenLibrary(&quot;graphics.library&quot;, 39);
   }
#ifdef __AMIGAOS4__
   if ((GfxBase != 0) &amp;&amp; (IGraphics == 0))
   {
      IGraphics = (GraphicsIFace*)Exec-&gt;GetInterface(GfxBase, &quot;main&quot;, 1, (TagItem*)NULL);
   }
#endif
}

MUIPictureClass::~MUIPictureClass()
{
   closeImages();
   dt-&gt;FreeInstance();
   openCount--;
   if (0 == openCount)
   {
#ifdef __AMIGAOS4__
      Exec-&gt;DropInterface((Interface*)IGraphics);
      IGraphics = 0;
#endif
      Exec-&gt;CloseLibrary(GfxBase);
      GfxBase = 0;
   }
}

iptr MUIPictureClass::DoMtd(iptr *obj, iptr *msg)
{
   uint16  *minmax;
   iptr      k;

   switch (msg[0]) 
   {
      case OM_NEW:
         {
            if (!(obj = (Object*)DoSuperMtd(parent, obj, msg))) 
               return 0;

            k = (iptr)Utility-&gt;GetTagData(MUIA_Picture_NormalImage, 0, (TagItem*)msg[1]);
            if (k != 0)
               image1 = (char*)k;
            k = (iptr)Utility-&gt;GetTagData(MUIA_Picture_SelectedImage, 0, (TagItem*)msg[1]);
            if (k != 0)
               image2 = (char*)k;

            isDisabled = Utility-&gt;GetTagData(MUIA_Disabled, 0, (struct TagItem*)msg[1]) ? true : false;
            isSelected = Utility-&gt;GetTagData(MUIA_Selected, 0, (struct TagItem*)msg[1]) ? true : false;

            openImages();

            return (ULONG)obj;
         }
         break;

      case OM_DISPOSE:
      case MUIM_Hide:
         break;
      
      case MUIM_Show:
         {
            if (dt != 0)
            {
               if (dtimg1 != 0)
               {
                  dt-&gt;SetDTAttrsA(dtimg1, 0, 0, (TagItem*)ARRAY(
                     PDTA_Screen,         (iptr)_screen(obj), 
                     PDTA_DestMode,       PMODE_V43, 
                     PDTA_UseFriendBitMap,true,
                     TAG_DONE,            0));

                  dt-&gt;DoDTMethodA(dtimg1, 0, 0, ARRAY(DTM_PROCLAYOUT, 0, 1));
               }
               if (dtimg2 != 0)
               {
                  dt-&gt;SetDTAttrsA(dtimg2, 0, 0, (TagItem*)ARRAY(
                     PDTA_Screen,         (iptr)_screen(obj), 
                     PDTA_DestMode,       PMODE_V43, 
                     PDTA_UseFriendBitMap,true,
                     TAG_DONE,            0));
                  
                  dt-&gt;DoDTMethodA(dtimg2, 0, 0, ARRAY(DTM_PROCLAYOUT, 0, 1));
               }
            }
         }
         break;

      case MUIM_AskMinMax:
         {
            DoSuperMtd(parent, obj, msg);

            minmax = (uint16*)msg[1];
            minmax[0] = width;
            minmax[2] = width;
            minmax[4] = width;
            minmax[1] = height;
            minmax[3] = height;
            minmax[5] = height;
         }
         return 0;

      case OM_SET:
         {
            bool flg;
            bool refresh = false;
//            image1 = (char*)GetTagData(MUIA_Picture_NormalImage,   (int32)image1.Data(), (TagItem*)msg[1]);
//            image2 = (char*)GetTagData(MUIA_Picture_SelectedImage, (int32)image2.Data(), (TagItem*)msg[1]);
            flg = Utility-&gt;GetTagData(MUIA_Disabled, isDisabled, (struct TagItem*)msg[1]) ? true : false;
            if (flg != isDisabled)
            {
               isDisabled = flg;
               refresh = true;
            }

            flg = Utility-&gt;GetTagData(MUIA_Selected, isSelected, (struct TagItem*)msg[1]) ? true : false;
            if (isSelected != flg)
            {
               isSelected = flg;
               refresh = true;
            }

            if (refresh)
               MUIMaster-&gt;MUI_Redraw(obj, 0);
         }
         break;

      case MUIM_NoNotifySet:
      case MUIM_Set:
         {
            bool refresh = false;
            if (msg[1] == MUIA_Picture_NormalImage)
               image1 = (char*)msg[2];

            if (msg[1] == MUIA_Picture_SelectedImage)
               image2 = (char*)msg[2];

            if (msg[1] == MUIA_Disabled)
            {
               bool flg = msg[2] ? true : false;
               if (flg != isDisabled)
               {
                  isDisabled = flg;
                  refresh = true;
               }
            }

            if (msg[1] == MUIA_Selected)
            {
               bool flg = msg[2] ? true : false;
               if (flg != isSelected)
               {
                  refresh = true;
                  isSelected = flg;
               }
            }
            if (refresh)
               MUIMaster-&gt;MUI_Redraw(obj, 0);
         }
         break;

      case MUIM_Draw:
         {
            Object* o = 0;
            BitMap* bitmap = 0;
            void*   drawinfo = 0;

            if (0 == _rp(obj)) 
               break;

            if ((isSelected) &amp;&amp; (dtimg2 != 0))
               o = dtimg2;
            else if (dtimg1 != 0)
               o = dtimg1;
            else
               break;

            drawinfo = dt-&gt;ObtainDTDrawInfoA(o, (TagItem*)ARRAY(
               PDTA_Screen,   (iptr)_screen(obj),
               TAG_DONE,      0));

            if (drawinfo != 0)
            {
               dt-&gt;DrawDTObjectA(
                  _rp(obj),
                  o,
                  _mleft(obj),
                  _mtop(obj),
                  width,
                  height,
                  0,
                  0,
                  0);
               dt-&gt;ReleaseDTDrawInfo(o, drawinfo);
            }
            else
            {
               dt-&gt;GetDTAttrsA(o, (TagItem*)ARRAY(
                        PDTA_DestBitMap,     (iptr)&amp;bitmap,
                        TAG_DONE,            0));
               if ((0 != bitmap) &amp;&amp; (0 != GfxBase))
               {
#ifndef __amigaos4
                  BltBitMapRastPort(bitmap, 0, 0, _rp(obj), _mleft(obj), _mtop(obj), width, height, 0xc0);
#else
                  IGraphics-&gt;BltBitMapRastPort(bitmap, 0, 0, _rp(obj), _mleft(obj), _mtop(obj), width, height, 0xc0);
#endif
               }
            }
         }
         return 0;

   }
   return DoSuperMtd(parent, obj, msg);
}

void MUIPictureClass::openImages()
{
   if (dt == 0)
      return;

   closeImages();

   dtimg1 = dt-&gt;NewDTObjectA(image1.Data(), (TagItem*)ARRAY(
            DTA_GroupID,      (iptr)GID_PICTURE,
            PDTA_Remap,       true,
            OBP_Precision,    (iptr)PRECISION_EXACT,
            TAG_DONE,         0));

   dtimg2 = dt-&gt;NewDTObjectA(image2.Data(), (TagItem*)ARRAY(
            DTA_GroupID,      (iptr)GID_PICTURE,
            PDTA_Remap,       true,
            OBP_Precision,    (iptr)PRECISION_EXACT,
            TAG_DONE,         0));

   width  = 0x7fff;
   height = 0x7fff;

   if (dtimg1 != 0)
   {
      BitMapHeader *bmhd;

      dt-&gt;GetDTAttrsA(dtimg1, (TagItem*)ARRAY(
         PDTA_BitMapHeader,   (iptr)&amp;bmhd,
         TAG_DONE,            0));

      width  = width  &lt;? bmhd-&gt;bmh_Width;
      height = height &lt;? bmhd-&gt;bmh_Height;
   }

   if (dtimg2 != 0)
   {
      BitMapHeader *bmhd;

      dt-&gt;GetDTAttrsA(dtimg1, (TagItem*)ARRAY(
         PDTA_BitMapHeader,   (iptr)&amp;bmhd,
         TAG_DONE,            0));

      width  = width  &lt;? bmhd-&gt;bmh_Width;
      height = height &lt;? bmhd-&gt;bmh_Height;
   }

   if ((width == 0x7fff) &amp;&amp; (height == 0x7fff))
   {
      width = 64;
      height = 48;
   }
}

void MUIPictureClass::closeImages()
{
   if (dt != 0)
   {
      if (dtimg1 != 0)
      {
         dt-&gt;DisposeDTObject(dtimg1);
      }
      if (dtimg2 != 0)
      {
         dt-&gt;DisposeDTObject(dtimg2);
      }
   }
   width    = 64;
   height   = 48;
   dtimg1   = 0;
   dtimg2   = 0;
}

iptr* MUIPictureClass::CreateClass()
{
    if (MUIPictureClass::muiclass == 0)
    {
	MUIPictureClass::muiclass = new MUICustomClassT&lt;MUIPictureClass&gt;(MUIC_Area);
    }
    return (iptr*)MUIPictureClass::muiclass;
}

void MUIPictureClass::DestroyClass()
{
    MUICustomClassT&lt;MUIPictureClass&gt; *p = MUIPictureClass::muiclass;
    MUIPictureClass::muiclass = 0;
    delete p;
}
&lt;/syntaxhighlight&gt;

Check out #mui on irc.freenode.net and report bugs/problems there and [http://finance.groups.yahoo.com/group/MUI/ MUI Yahoo Group]


;[https://library.morph.zone/Magic_User_Interface_Programming Magic User Interface MUI]</text>
      <sha1>1sfcwbr8t5d2kk8l950mk2dxcjy2bck</sha1>
    </revision>
    <revision>
      <id>4668972</id>
      <parentid>4668971</parentid>
      <timestamp>2026-09-05T17:53:41Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668972</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="142538" sha1="6iunzm4qg6p1qkkgouuo4eqo5px49io" xml:space="preserve">{{ArosNav}}

==Introduction==

Mui original classes are identified by the trailing .mui like List, String, etc

MUI (Zune) replacement classes MCCs came later which include Nlist, BetterString, etc which some developers frown upon.

Please read autodocs/MUI_Application.doc/MUIM_Application_NewInput it has a proper example for a '''complete''' main loop. A MUI program has a main loop, but in an ideal application the loop is empty. Main loops as well as hooks are a thing of the past but backwards compatibility is still there.

'''New method'''
So nowadays, in order to handle notifications from buttons, sliders, etc. - you [http://guidetoamigacompatibleprogramming.googlecode.com/svn-history/r4/trunk/english/CAP_4.txt subclass Application.mui], Window.mui or &lt;one of the groups&gt;.mui of your choice, define your own private methods there and set up notifications on your buttons to call these methods. This lets you keep a neat internal structure rather than having everything in a one huge switch statement of return ids.

Methods have no TRUE or FALSE states nor anything other defined states, they are just function calls (well, sort of). The only approach is subclassing technique and overload the method. You can then do anything you wish. The custom class is your way.

To define your own private method and attribute ids you could start with TAG_USER.
;Read more [https://github.com/chfhhd/guidetoamigacompatibleprogramming here]

'''Old Method'''
With MUI you can also call hooks to avoid creating subclasses, but only the change of an attribute can cause an action.

* First set Application and Window classes information. 
* Use Horizontal Groups (HGroup) or Vertical Groups (VGroup) to stuff objects (buttons, sliders, directory listers, etc) into them. Objects are not placed directly to some fixed locations but are instead grouped in special containers which are then dynamically displayed and positioned. 
* Use Notification to do something when object changes (pressed, slide, etc) 
* Release them when finished or when ending app

Macros play a part in programming Zune interfaces. Get and Xget can replace GetAttrs and Set and Xset similarly with SetAttrs.

When you read the mui autodocs there is a field after the function name with [ISG] and sometimes also [ISGN]

And that indicates what to can do with the tag.
&lt;pre&gt;
I = Init
S = SetAttr can be used
G = GetAttr can be used
N = Supports Notify
&lt;/pre&gt;

So if you see [I.G] that means that you can use the Tag at Init and use GetAttr on it.

==MUI Zune Base Classes==

{| class=&quot;wikitable&quot;
|-
|+ BOOPSI rootclass connected to Zune NOTIFY.mui class
! [ Application.mui]      
! [ Window.mui]          
! [ Family.mui]     
! [ Area.mui] 
|-
| 
| Aboutmui
| Menustrip
| Rectangle
|-
| 
| 
| Menu
| Balance
|-
| 
| 
| Menulist
| Image
|-
| 
| 
| 
| Menubar
|-
| 
| 
| 
| Bitmap
|-
| 
| 
| 
| Text
|-
| 
| 
| 
| Gadget
|-
| 
| 
| 
| Gauge
|-
| 
| 
| 
| Scale
|-
| 
| 
| 
| Colorfield
|-
| 
| 
| 
| List
|-
| 
| 
| 
| Numeric
|-
| 
| 
| 
| Pendisplay
|-
| 
| 
| 
| Group
|-
|}

encapsulation is what you have with all the MUI classes. For example to use a listview you have a well defined interface for this gadget, and all implementation details are encapsulated into the class (like private variables etc.)

You would do similar with an advanced application. Locate all sub-systems and implement these as &quot;isolated&quot; modules with interfaces and implementation details encapsulated into the modules, not visible from the outside.

inheritance via subclassing

polymorphism

===Subclasses===

Good source examples [http://www.onyxsoft.se/snakee.html Snakee], [http://www.bluemind.org/amiga-lister-dopus-magellan-lister-system-amigaos/ List],

====Application====

Instead of MUI_NewObject(MUIC_Application, ,etc) is often replaced by the macro ApplicationObject, etc, etc...

When subclassing window or application class there aren't MUIM_Setup/Cleanup methods at all.

If you want to make a gui where everything is made of custom classes (at least the outer stuff, ie application and windows), you define all your classes as usual, and then instantiate your application with a single newobject() call. It's no problem to add elements to a group/window/application when it is being allocated (inside OM_NEW).

====Window====

Instead of MUI_NewObject(MUIC_Window, ,etc) is often shortened to the macro WindowObject,etc,etc but can be still used in Child Windows...

The way to do this would be to implement a method in one of your subclasses (MUIC_Window or the window's Root MUIC_Group are always safe picks) and have a MUIA_Window_? notification call it.

For the positions to be remembered, you have to close the windows (set MUIA_Window_Open to false) before disposing the Zune Application object

====Classes====

Instead of MUI_NewObject(MUIC_Group, ,etc) is often rewritten as the macro &lt;Group&gt;GroupObject,etc,etc...

Then class creation:

 TheClass = MUI_CreateCustomClass (NULL, supername, NULL, sizeof (MyObjectData), dispatcher);

&lt;pre&gt;
  if (!(mcc = MUI_CreateCustomClass(NULL,MUIC_Area,NULL,sizeof(struct NewClass_Data),NewClass_Dispatcher)))
  {
    printf(&quot;Cannot create custom class.\n&quot;);
    return(0);
  }
&lt;/pre&gt;

Is it ok to inherit from other types of object? Yes, to subclass slider class to overload MUIM_Numeric_Stringify method.

How to check for a minimum version of a MUI MCC when building a GUI? [...] 
Your best chance is that the custom class writer has overloaded MUIA_Version/Revision.

===Doing Stuff===

And here is a way to access this inside a method:

&lt;pre&gt;
LONG AnyMethod (Class *cl, Object *obj, Msg msg)
{
struct MyObjectData *data = INST_DATA(cl,obj);

/*...*/

if (!strcmp (&quot;Amiga&quot;, data-&gt;Pointer)) DoSomething();

/*...*/
}
&lt;/pre&gt;

Memory allocated for object data structure is freed automatically by MUI in object destructor, you have to do nothing.

 struct MyObjectData *data = (MyObjectData *)INST_DATA(cl, obj);

====Dispatcher====

Then, in your dispatcher subprogram, you write something like case MUIM_NList_ContextMenuBuild then MyOwnContextMenuBuild(cl,obj,msg); then you write a subprogram MyOwnContextMenuBuild that does what you want your class to do when this method is called.

Every object in your subclass gets its own data area added to the object &quot;structure&quot;. Also known as a data instantation. It is your own var area privately for the object with the given size in the MUI_CreateCustomClass() call but do not use the obsolete MUI_GetClass() and MakeClass() pairing. See the [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=2765 Class2.c] example in the MUI:Developer/C/Examples dir.

====Overloading====

'''Overloading''' class methods is the main and best design to use when you need to add some class features or use some specials behaviours. In MUI C version this is done by creating a new MCC (MUI Custom Class) and a dispatcher routine catching incoming BOOPSI messages when DoMethod() is called on instance of this MCC.

To find out when a superclass's attribute changes without using a Notify? Yes, just overload OM_SET. 
Most (if not all) calls to OM_SET are done with a temporary tag list allocated on the stack, so it'll be lost anyway...

If you need this pointer separate for every object, you should place it in object data structure.

&lt;pre&gt;
struct MyObjectData
{
char *Pointer;
};
&lt;/pre&gt;

Tag list or method structures should be untouched in any way if it's not documented. If MUI or 3rd party mcc's do this they're broken... Example of documented method structures touched by MUI are MUIM_Draw and MUIM_AskMinMax...

MUI will call MUIM_Hide, MUIM_Show on your object if the dimension change. So no need to check this in MUIM_Draw. MUIM_Draw is btw always called for a reason, so see no reason for you to omit a redraw here.

&lt;pre&gt;
ULONG NewList_New(struct IClass *cl , Object *obj, Msg msg)
{
    return 0;
}

ULONG NewList_Set(struct IClass *cl , Object *obj, Msg msg)
{

    return(DoSuperMethodA(cl, obj, msg));
}

ULONG NewList_Get(struct IClass *cl, Object *obj, Msg msg)
{

    return(DoSuperMethodA(cl, obj, msg));
}

&lt;/pre&gt;

===Application and Window===

How can you get a pointer to an active window object at any time?
Normally you should search for MUIA_Window_Active in Application window list. 
Can create MUIC_Window subclass and intercept MUIA_Window_Active, and create your API for this. 
On the other hand, you can set up notification on this tag and if window receives it you will know about it and set some field in memory to window pointer or so.

MUIA_Window_Screen for your own screen and trying to have window size completely under control. 
Setting MUIA_Window_Width and MUIA_Window_Height always works when you don't specify window ID (MUIA_Window_ID) for WindowObject.
In case you specify this ID, height and width are set automatically by system and are remembered for next time you run application.

&lt;pre&gt;
     app = ApplicationObject,
         MUIA_Application_Title, (IPTR)&quot;KeyShow&quot;,
         MUIA_Application_Version, (IPTR)&quot;$VER: KeyShow 1.0 (24.02.2012)&quot;,
         MUIA_Application_Copyright, (IPTR)_(MSG_AppCopyright),
         MUIA_Application_Author, (IPTR)&quot;The AROS Development Team&quot;,
         MUIA_Application_Description, (IPTR)_(MSG_AppDescription),
         MUIA_Application_Base, (IPTR)&quot;KEYSHOW&quot;,
 
         SubWindow, (IPTR)(win = WindowObject,
             MUIA_Window_Title, (IPTR)_(MSG_WI_TITLE),
             MUIA_Window_ID, MAKE_ID('K','S','W','N'),
             WindowContents, (IPTR)KeyboardGroupObject,
             End,
         End),
     End;
 
     if (app == NULL)
&lt;/pre&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/*
    Copyright © 2002, The AROS Development Team.
    All rights reserved.

    $Id: dtpic.c 30792 2009-03-07 22:40:04Z neil $
*/

#include &lt;dos/dos.h&gt;

#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;

#include &lt;libraries/mui.h&gt;

struct Library *MUIMasterBase;

Object *app;

int main(void)
{
    Object *wnd;
    
    MUIMasterBase = (struct Library*)OpenLibrary(&quot;muimaster.library&quot;,0);

    app = ApplicationObject,
   	SubWindow, wnd = WindowObject,
    	    MUIA_Window_Title, &quot;dtpic test&quot;,
	    MUIA_Window_Activate, TRUE,

    	    WindowContents, VGroup,
    	    	Child, MUI_NewObject(&quot;Dtpic.mui&quot;,MUIA_Dtpic_Name,&quot;SYS:System/Images/AROS.png&quot;,TAG_DONE),
		End,
	    End,
	End;

    if (app)
    {
	ULONG sigs = 0;

	DoMethod
        (
            wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE, (IPTR) app, 
            2, MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit
        );

	set(wnd,MUIA_Window_Open,TRUE);

	while (DoMethod(app, MUIM_Application_NewInput, (IPTR) &amp;sigs) != MUIV_Application_ReturnID_Quit)
	{
	    if (sigs)
	    {
		sigs = Wait(sigs | SIGBREAKF_CTRL_C | SIGBREAKF_CTRL_D);
		if (sigs &amp; SIGBREAKF_CTRL_C) break;
		if (sigs &amp; SIGBREAKF_CTRL_D) break;
	    }
	}

	MUI_Object(app);
    }

    CloseLibrary(MUIMasterBase);
    
    return 0;
}
&lt;/syntaxhighlight&gt;

You must OM_ADDMEMBER a window to an application before opening it and you must OM_ADDMEMBER an area object to a group object (in a MUIM_Group_InitChange/ExitCHange pair) if you want to show it in a window (be part of your GUI). Mui Dev docs have a section on  Dynamic Windows (Dynamic Object Linking/Windows) which are detailed documentation for dynamic window creation.

But you can create a custom class and get notified just by looking for incoming methods. Overloading MUIM_Setup is probably the best idea. You can subclass your window and put screen change detection in MUIM_Setup. E.g. in every MUIM_Setup you can remember screen pointer somewhere in object data, compare it with the previous value and do some things if screen has changed. use _app(obj) after MUIM_Setup.

You could have subclass of MUIC_Group where the all objects are placed... When you detect in MUIM_Setup that _screen() changed, you set MUIA_Window_CloseRequest to TRUE...  If you app runs on WB screen user can change WB screen resolution/depth at any time. User can change your screen from the custom screen database at any time. Other thing to consider is iconify from the Exchange or ARexx. You _must_ react for screen changes.

Then you should place MUIM_Application_Save after your main loop.

Overloading MUIM_Window_Snapshot with some code which saves the prefs would do a save whenever the user selects the Snapshot icon on the window border, it would not do that only at program end. If you really want to save on Snapshot, you have to create a new class with CreateCustomClass() which must be a subclass of MUIC_Window. In the dispatcher of this sub class you have to call your own code whenever the dispatcher receives the MUIM_Window_Snapshot method. Then you have to change the application creation code: You have to replace every window creation with creation of an object of your window sub class (Intuition.NewObject()).

There seems to be a general problem when disposing windows: You must *not* reference the application object in a windows dispose method! Why? Because before disposing a window, you unlink it from the application (OM_REMMEMBER). After that, the window does no longer belong to an application and using _app(obj) is illegal. You don't have _app(obj) available during OM_NEW, the same is true for OM_DISPOSE.

Using _app(obj) anywhere in setup/cleanup methods (either before or after the DoSuperMethod) is fine. In fact, there is another layer between new/dispose and setup/cleanup where an object learns about its application context. However, this layer has not been made publically available through methods yet.

MUIA_Window_IsSubWindow does exactly this (skipping OM_REMMEMBER and OM_DISPOSE). However, this is not the solution to all problems which arise from the &quot;global&quot; window list in the application object. Window class should probably be able to have more window children itself.

How do we get the actual Window from my MUI-object ???

&lt;pre&gt;
struct Window *win;
DoMethod(obj,MUIA_Window,&amp;win);
&lt;/pre&gt;

MUIA_Window is an attribute. You can read attributes by calling GetAttr() from Intuition:

GetAttr(MUIA_Window, obj, &amp;x);

And few warnings:

* MUIA_Window is only valid when the window is opened
* MUIA_Window is an area class tag. Use MUIA_Window_Window for window objects.

To call ChangeWindowBox on MUI windows. Just take care that the window is currently open (MUIA_Window_Window!=NULL) need the screen, you can always get MUIA_Window_Window and use window-&gt;WScreen etc. like with other intuition windows.

'''MUIM_Application_PushMethod'''

So you want to get out of the object context first, and this is easily done with MUIM_Application_PushMethod.

&lt;pre&gt;
/* From your mail window */
DoMethod(_app(obj), MUIM_Application_PushMethod, _app(obj), 2,
MUIM_MyApplication_RemoveObject, obj);

/* From your application subclass */
case MUIM_MyApplication_RemoveObject:
{
DoMethod(obj, OM_REMMEMBER, msg-&gt;Obj);
MUI_DisposeObject(msg-&gt;Obj);
}
break;
&lt;/pre&gt;

Basically have a rendering task that does a heap of computation and renders into an offscreen rastport. When it's finished a frame, it sets a flag (Drawn) to FALSE, releases a semaphore, and does a PushMethod.

The main program, waiting patiently in its event loop, at some point will be awakened by the PushMethod, which triggers the custom class to do a MUI_Redraw() internally, which in turn obtains the semaphore, copies the offscreen bitmap to the window, sets Drawn to TRUE, and releases the semaphore. Then it goes back to sleep.

The rendering subtask, in the meantime, has done an ObtainSemaphore. When it gets it, it checks to see if Drawn is TRUE. If so, it can continue because it means the main task successfully copied the bitmap. Otherwise it releases it, does a little Delay, and tries again, to try and give the main task time to snatch the semaphore and do its work.

So, the semaphore is, in effect, protecting the offscreen rastport (and the Drawn flag) - neither task can access or change it without obtaining the semaphore first, and the flag is used to tell the draw task whether the main task has had a chance to do its job or not. Most of the time (i.e. almost always) the main task does, in fact, manage to grab the semaphore immediately so the draw task doesn't manage to steal it back again too quickly. If the main task finishes quickly, then when the draw task tries to obtain the semaphore it succeeds immediately, so there's no penalty.

PushMethod should not be too heavily overloaded, however, for inter-process communication recommends using private messageports for more intensive stuff. Use it as a signalling mechanism to wake up the main task and get it to send a MUI_Redraw to the custom class, and only ever send one at once (although there are 30-60 of them per second). Never had any problems with it in those circumstances.

&lt;pre&gt;
struct SignalSemaphore lock_AddEntry_Sem;
...
InitSemaphore(&amp;lock_AddEntry_Sem);
...
while(something){
...
   ObtainSemaphore(lock_AddEntry_Sem);     // Grab the semaphore
   while (lock_AddEntry){                  // Main task completed its job?
      ReleaseSemaphore(lock_AddEntry_Sem); // No, release semaphore
      Delay(1);                            // Wait a bit
      ObtainSemaphore(lock_AddEntry_Sem);  // Try again
   }
...
   lock_AddEntry = TRUE;                   // Set flag
   ReleaseSemaphore(lock_AddEntry_Sem);    // Give CPU back to main task
...
}
&lt;/pre&gt;

MsgPorts are slower. Semaphores are better to use under any AmigaOS like.

MUIM_HandleEvent is called for each event handler node unless MUI_EventHandlerRC_Eat is returned. MUIM_HandleInput is called for an active object if it was not eaten by MUIM_HandleEvent.

Should use EventHandler and not request? To avoid getting events even if my object is not the active one ?
Yes - eventhandlers respect properties such as the active and default object, priorites etc. 
HotkeyString is a subclass of BetterString. It adds a new eventhandler with a higher priority, thus get the events before its superclass, which wouldn't be the case for the other approach (one could override MUIM_HandleInput, but this was just *one* example...)

Eventhandlers also allow you to swallow input, another thing which isn't possible with IDCMP-requesting. This means many objects (which use the old way) will only interpret input when they are the active or default object, which is bad e.g. in IProbe where I want HTMLview to react on arrow up/down, even when the URL-string is active - and this is AFAIK only possible with eventhandlers.

the proper way to know the current active window (IDCMP_ACTIVEWINDOW/IDCMP_INACTIVEWINDOW was what I tracked before). What is the proper MUI way to know a window has become active? You can attempt a setup dispatcher that add the required actions to the event handler.

&lt;pre&gt;
struct your_data
{
struct MUI_EventHandlerNode ehnode;
};

ULONG yoursetup(struct IClass *cl, Object *obj, Msg msg)
{
struct your_data *data = (struct your_data *)INST_DATA(cl, obj);

if (!DoSuperMethodA(cl, obj, msg))
return(FALSE);

data-&gt;ehnode.ehn_Object = obj;
data-&gt;ehnode.ehn_Class = cl;
data-&gt;ehnode.ehn_Events = IDCMP_ACTIVEWINDOW | IDCMP_INACTIVEWINDOW;

DoMethod(_win(obj), MUIM_Window_AddEventHandler, &amp;data-&gt;ehnode);

return(TRUE);
}
&lt;/pre&gt;

add a cleanup dispatcher that looks like :

&lt;pre&gt;
ULONG yourcleanup(struct IClass *cl, Object *obj, struct MUIP_HandleInput *msg)
{
struct your_data *data = (struct your_data *)INST_DATA(cl, obj);

DoMethod(_win(obj), MUIM_Window_RemEventHandler, &amp;data-&gt;ehnode);
return(DoSuperMethodA(cl,obj,msg));
}
&lt;/pre&gt;

Add a dispatcher for MUIM_HandleEvent and take care of your wanted event like :

&lt;pre&gt;
ULONG yourhandler(struct IClass *cl, Object *obj, struct MUIP_HandleInput *msg)
{
struct your_data *data = (struct your_data *)INST_DATA(cl, obj);

if (msg-&gt;imsg)
{
case IDCMP_ACTIVEWINDOW:
// Do what you want here
break;

case IDCMP_INACTIVEWINDOW:
// Do what you want...
break;
}

return(DoSuperMethodA(cl, obj, (Msg)msg));

}
&lt;/pre&gt;

or You could try to install an event listener that triggers every time MUIA_Window_Activate gets changed.

Be able to receive mouse co-ordinates and keypresses into my application, even when the window is not active. 
You can poll intuition base and read mouse coords at any time. An interrupt routine would be the best solution if your app wants keep an eye on it all the time... (might be possible with other libraries)

Everything is single threaded unless you specifically use MUIM_Application_InputBuffered. No functions are interrupted in order to handle a signal. Would a better method be to offload the MUI interface handling onto a
separate task, and communicate with the network task through signals? This would at least solve the problem mentioned above. STRICQ uses MUI and is setup to handle any number of simultaneous sockets, both TCP and UDP. 
First create another window, then call MUIM_Application_InputBuffered (even though you should really try to avoid this) and then do the PushMethod. What should I do if the InputBuffered had to be used to handle other actions? Come up with a design pattern that avoids this nasty input probing in the middle of your program 
Creating a subclass of application class for this purpose where you could call one method with the object to be deleted as an argument and the application sub-class then stored a pointer to this object and deleted it after MUIM_Application_Input returned (and a nested counter tells me that there is no other recursive call to MUIM_Application_Method). Remember that the MUIM_PushMethod is not safe in the sense that it can fail (e.g. out of memory) and then your object doesn't get deleted (i.e. memory leak). The solution using a sub class of application class is safe as there is no need to allocate memory for the pointer to the object by adding it to an 'internal' Group class.

====Iconify====

&lt;pre&gt;
#ifdef __amigaos4__
    MUIA_Application_DiskObject , diskobject = GetDiskObject(_ProgramName),
    #endif
&lt;/pre&gt;

MUIA_Application_DiskObject,GetDiskObject(&quot;PROGDIR:mp3player&quot;),

where PROGDIR:mp3player is the name of your app. Be aware, that you are leaking the disk object this way. Be sure to assign it to pointer and FreeDiskObject after your application has ended..

&lt;pre&gt;
struct DiskObject *my_app_icon;
MUIA_Application_DiskObject,my_app_icon=GetDiskObject(&quot;PROGDIR:zamp&quot;),

ULONG iconified=0;
get(application, MUIA_Application_Iconified, &amp;iconified);
if( !iconified)
&lt;/pre&gt;

How to execute an arexx script from your own program as though it was run from your program's arexx port.
An application subclass that adds one method called MUIM_Application_RunScript, just call this method with the scriptname and its arguments then it will be launched with your (MUI) port as host and it will make sure your program doesn't quit before the script has completed.

&lt;pre&gt;
ULONG ListWindows( Object *application )
{
ULONG windows = 0;
struct MinList *windowlist;
windowlist = (struct MinList *) xget( application,
MUIA_Application_WindowList );
if( windowlist &amp;&amp; !IsListEmpty( (struct List *) windowlist ) )
{
Object *object, *objectstate = (Object *) windowlist-&gt;mlh_Head;
while( object = NextObject( &amp;objectstate ) )
{
Printf( &quot;Object 0x%08lx is %swindow.\n&quot;,
object,
IsWindow( object ) ? &quot;&quot; : &quot;not &quot; );
windows++;
}
}
return( windows );
}
&lt;/pre&gt;

You can check whether object class is class or subclass of MUIC_Window, using similar code to below:

&lt;pre&gt;
BOOL IsWindow( Object *object )
{
struct IClass *windowclass = MUI_GetClass( MUIC_Window );
struct IClass *class;
for( class = OCLASS( object ); class; class = class-&gt;cl_Super )
if( class == windowclass )
return( TRUE );
return( FALSE );
}
&lt;/pre&gt;

====External input====

 MUIM_Application_AddInputHandler(struct( MUI_InputHandlerNode ) in the MUIM_Setup and MUIM_Cleanup methods of your class (not subclass?).

Remove with MUIM_Application_RemInputHandler

'''Obsolete Hooks''' Is it safe to call the MUI_DisposeObject() inside a hook which is called by a notification if it frees the object the notification is attached to? This is not safe. The hook contents are not freed because after returning from the hook, there is still some return code from the calling class which has to be executed.

&lt;pre&gt;
MUIM_Application_AboutMUI 
MUIM_Application_AddInputHandler 
MUIM_Application_CheckRefresh 
MUIM_Application_InputBuffered 
MUIM_Application_Load 
MUIM_Application_NewInput (replaces old Input) 
MUIM_Application_OpenConfigWindow 
MUIM_Application_PushMethod 
MUIM_Application_RemInputHandler 
MUIM_Application_ReturnID 
MUIM_Application_Save 
MUIM_Application_SetConfigItem  
MUIM_Application_ShowHelp        
&lt;/pre&gt;

&lt;pre&gt;
MUIA_Application_Active 
MUIA_Application_Author 
MUIA_Application_Base 
MUIA_Application_Broker 
MUIA_Application_BrokerHook 
MUIA_Application_BrokerPort 
MUIA_Application_BrokerPri 
MUIA_Application_Commands 
MUIA_Application_Copyright 
MUIA_Application_Description 
MUIA_Application_DiskObject 
MUIA_Application_DoubleStart 
MUIA_Application_DropObject 
MUIA_Application_ForceQuit 
MUIA_Application_HelpFile 
MUIA_Application_Iconified 
MUIA_Application_MenuAction 
MUIA_Application_MenuHelp 
MUIA_Application_Menustrip 
MUIA_Application_RexxHook 
MUIA_Application_RexxMsg 
MUIA_Application_RexxString 
MUIA_Application_SingleTask 
MUIA_Application_Sleep 
MUIA_Application_Title 
MUIA_Application_UseCommodities 
MUIA_Application_UsedClasses 
MUIA_Application_UseRexx 
MUIA_Application_Version 
MUIA_Application_Window 
MUIA_Application_WindowList 
&lt;/pre&gt;

&lt;pre&gt;
MUIM_Window_AddEventHandler 
MUIM_Window_Cleanup 
MUIM_Window_RemEventHandler 
MUIM_Window_ScreenToBack 
MUIM_Window_ScreenToFront   
MUIM_Window_Setup 
MUIM_Window_Snapshot 
MUIM_Window_ToBack 
MUIM_Window_ToFront 
&lt;/pre&gt;

&lt;pre&gt;
MUIA_Window_Activate 
MUIA_Window_ActiveObject 
MUIA_Window_AltHeight 
MUIA_Window_AltLeftEdge 
MUIA_Window_AltTopEdge 
MUIA_Window_AltWidth 
MUIA_Window_AppWindow 
MUIA_Window_Backdrop 
MUIA_Window_Borderless 
MUIA_Window_CloseGadget 
MUIA_Window_CloseRequest 
MUIA_Window_DefaultObject 
MUIA_Window_DepthGadget 
MUIA_Window_DisableKeys 
MUIA_Window_DragBar 
MUIA_Window_FancyDrawing 
MUIA_Window_Height 
MUIA_Window_ID 
MUIA_Window_InputEvent 
MUIA_Window_IsSubWindow 
MUIA_Window_LeftEdge 
MUIA_Window_MenuAction 
MUIA_Window_Menustrip 
MUIA_Window_MouseObject 
MUIA_Window_NeedsMouseObject 
MUIA_Window_NoMenus 
MUIA_Window_Open 
MUIA_Window_PublicScreen 
MUIA_Window_RefWindow 
MUIA_Window_RootObject 
MUIA_Window_Screen 
MUIA_Window_ScreenTitle 
MUIA_Window_SizeGadget 
MUIA_Window_SizeRight 
MUIA_Window_Sleep 
MUIA_Window_Title 
MUIA_Window_TopEdge 
MUIA_Window_UseBottomBorderScroller 
MUIA_Window_UseLeftBorderScroller 
MUIA_Window_UseRightBorderScroller 
MUIA_Window_Width 
MUIA_Window_Window 
&lt;/pre&gt;

===Objects===

DoMethod( object1, method, attribute, value, object2, parameter_number, method2, attribute2, value2 [,...])

* MUIM_Application_NewInput 
* MUIM_Window_
* MUIM_CallHook MUIM_FindUData MUIM_GetUData MUIM_SetUData 
* MUIM_KillNotify MUIM_NoNotifySet MUIM_Notify 
* MUIM_Set MUIM_MultiSet  MUIM_SetAsString 
* MUIM_List_InsertSingle

When a Zune object is created and destroyed several methods are called:

&lt;pre&gt;
OM_NEW
MUIM_Setup
MUIM_AskMinMax
[ window is opened here ]
MUIM_Show
MUIM_Draw
MUIM_Hide
[ window is closed here ]
MUIM_Cleanup
OM_DISPOSE
&lt;/pre&gt;

If something is only valid between setup and cleanup it means that the first place where you can use it is the setup method and you aren't allowed to use it after cleanup.

If you want to manage a set of invisible objects the class MUIC_Family may be of help.

Need to know size of object while program is between MUIM_GroupInitChange and MUIM_GroupExitChange. Simple asking about MUIA_Width a MUIA_Height returns 0. Anyone have any idea? 
Width/height is not valid until you call ExitChange again. But if you need to know object dimensions subclassing is probably the best way to do so. You can get object dimensions by using _width()/_height() macros.

The object can't tell the difference of whether OM_SET was invoked through SetAttr() or through MUIM_MultiSet. 
Some standard MUI classes do indeed modify the taglist passed to them. A good example is Group class; it sets certain tags to TAG_IGNORE, because they either cannot be forwarded to the children, or shouldn't be handled by its superclass (Area).

How do you add a selected image to an app to use a different image for normal and selected states ?
Most people are using a Group with PageMode set, so that the group simply toggle the displayed page, when pressed, and each page has the desired image shown on it.

====Notifications====

Basically, MUI doesn't use BOOPSI's notification system. Notification happens transparently; the only thing you need to do is pass the method up to your superclass, and you should be doing that anyway—you don't need to use the approach that non-MUI BOOPSI classes use.

You can put notification on every attribute of your custom class. That's assuming your class is derived from MUIC_Notify. Then MUI will automagically execute the notification whenever you set an attribute.

You can place a notification on any (public) attribute of any class (or its ancestors) using the MUIM_Notify method. These notifications can be placed at any time from anywhere.

All you have to do is only change attributes of your object using set(), and in your set method handler add
  return (DoSuperMethodA(cl, obj, msg)); 
at the end. This will pass on the OM_SET up the class hierarchy to Notify.mui, which will then perform the notifications. The other thing, of course, is to always use set() whenever you want to change a value, rather than just assigning it directly. Only within the OM_SET method should you assign it directly.

When some other class puts a notification on one of your attributes, and your attribute gets changed using set() (or OM_SET), then when it does the DoSuperMethod() call the OM_SET will eventually reach the root class of all MUI classes—Notify.mui. This keeps a list of notifications to be performed.

&lt;pre&gt;
    /* This is setting up a notification on the MUIA_Robot_FrameRate * attribute */ 
    DoMethod(MyObj,
            MUIM_Notify, MUIA_Robot_FrameRate, MUIV_EveryTime,
            FrameCntObj,
            4,
            MUIM_SetAsString, MUIA_Text_Contents, MUIX_R&quot;%ld&quot;, MUIV_TriggerValue
    );

...

    /* This is setting the frame rate (actually done within the class
     * itself -- ie. I use set() rather than just changing the value
     * directly in case there are notifications on it. */
    set(obj, MUIA_Robot_FrameRate, data-&gt;framecnt - data-&gt;lastframecnt);

...

/* This is the relevant part of my custom class's OM_SET method
 * handler. */
static ULONG mSet(struct IClass * cl, Object * obj, Msg msg)
{
    struct MyData *data = INST_DATA(cl, obj);
    struct TagItem *tags, *tag;

    for (tags = ((struct opSet *) msg)-&gt;ops_AttrList; tag = NextTagItem(&amp;tags);)
    {
        switch (tag-&gt;ti_Tag) {
...
          case MUIA_Robot_FrameRate:    data-&gt;framerate = (ULONG) tag-&gt;ti_Data;
                                        break;
...
        }
    }

    return(DoSuperMethodA(cl, obj, msg));
}
&lt;/pre&gt;

If you have an attribute MUIA_Xxx_Yyy that is readable and notifiable, and recognized by mGet() (your OM_GET method). Internally it reads from data-&gt;Yyy. Further, let's say you have a private attribute MUIA_Xxx_YyyP (probably best to give it a numeric value quite different to the rest in your class) that is recognized by mSet() and writes to data-&gt;Yyy. mSet(), however, does *not* recognize MUIA_Xxx_Yyy. The code in the mSet() switch statement that recognizes MUIA_Xxx_YyyP, in addition to writing to data-&gt;Yyy, changes tag-&gt;ti_Tag to MUIA_Xxx_Yyy. Then, when the DoSuperMethodA() call is made, Notify class recognizes the attribute that was changed as MUIA_Xxx_Yyy and correctly performs the notification.

Suppose your class use the custom attribute MUIA_HHH_MyAttr. Other objects can ask MUI to be notified whenever this attribute is set()ted to a given value,for example you can have something like this:

 DoMethod(obj1,MUIM_Notify,MUIA_HHH_MyAttr,32,obj2,1,MUIM_MyObj_Changed);

Here object obj2 asks to be notified with method MUIM_MyObj_Changed whenever the attribute MUIA_HHH_MyAttr of obj1 is set()ted to 32.

Child, Label2(&quot;Allow duplicates:&quot;),
Child, ck6 = CheckMark(TRUE),

DoMethod(ck6, MUIM_Notify, MUIA_Selected, MUIV_EveryTime, app, 2, MUIM_Application_ReturnID, ACT_CK6);

The confusing thing about this bug is that it only affects CheckMark(TRUE) objects (or if you use MUIM_Application_Load to restore the state of checkmarks then those that become set to TRUE will exhibit the same problem).

The autodocs state you 'simply' add your checkmarks and strings (paired together) even in 'invisible' space. You need the string because the autostring for a checkmark is only place-able at the left side (which would be unintuitive).

&lt;pre&gt;
Object *MakeCheck(BYTE state, char *label)
{
  return ImageObject,
           ImageButtonFrame,
           MUIA_Text_Contents, label,
           MUIA_InputMode   , MUIV_InputMode_Toggle,
           MUIA_Image_Spec  , MUII_CheckMark,
           MUIA_Background  , MUII_ButtonBack,
           MUIA_ShowSelState, state,
           MUIA_CycleChain  , TRUE,
         End;
}
&lt;/pre&gt;

 DoMethod(timerobj,MUIM_Notify,MA_Timer_Seconds,MUIV_EveryTime,obj,2,MM_Clock_Seconds,MUIV_TriggerValue);

This should call MM_Clock_Seconds everytime MA_Timer_Seconds changes.

&lt;pre&gt;
WaitIO(data-&gt;req);
CurrentTime(&amp;raw,&amp;micros);
today = raw%86400;
SetAttrs(obj,MA_Timer_Seconds,today%60,TAG_DONE);
&lt;/pre&gt;

Notify does not happen

&lt;pre&gt;
data-&gt;seconds = today%60+30;
data-&gt;minutes = (today%3600)/60;
data-&gt;hours = today/3600;
data-&gt;req-&gt;tr_node.io_Command = TR_ADDREQUEST;
data-&gt;req-&gt;tr_time.tv_secs = 1;
data-&gt;req-&gt;tr_time.tv_micro = 0;
SendIO((struct IORequest *)data-&gt;req); 
&lt;/pre&gt;

timerobj's OM_GET:

&lt;pre&gt;
case MA_Timer_Seconds:
 *msg-&gt;opg_Storage = data-&gt;seconds;
return TRUE; 
&lt;/pre&gt;

Class has no OM_SET but you '''must implement OM_SET''' to notify. I would not use MUI notifications for this kind of events because due to BOOPSI latency. The timer does work (tested by getting MA_Timer_Seconds in every MUIM_Draw for the clock class, but MM_Clock_Seconds never gets called.

SetAttrs(NULL, ...
In theory you do not have to because SetAttrsA() is only a wrapper call to DoMethodA() which accepts NULL object pointer but this is not documented behaviour either in SetAttrsA() nor DoMethodA(). So do not rely on it but use macro instead to save you from typing if statements.

Restore a button frame - D&amp;D lately but it seems it clashes with MUI's own D&amp;D drawing. You could look into Ambient D&amp;D for ideas. It uses its own dropmarks.

&lt;pre&gt;
MUI_DISPATCH(NewList_Dispatcher)
{
    switch (msg-&gt;MethodID)
    {
        case OM_NEW              : return(NewList_New  (cl,obj,(APTR)msg));
        case OM_SET              : return(NewList_Set  (cl,obj,(APTR)msg));
        case OM_GET              : return(NewList_Get  (cl,obj,(APTR)msg));
        
        case MUIM_DragQuery : return(NewList_DragQuery(cl,obj,(APTR)msg));
        case MUIM_DragDrop   : return(MyList_DragDrop (cl,obj,(APTR)msg));
        case MUIM_ExternDrop :return(MyList_ExternDrop(obj,(APTR)msg));
    }
    return(DoSuperMethodA(cl,obj,msg));
}
&lt;/pre&gt;

added an internal notification method to each checkmark (checkbox) and added the method to the dispatcher,

&lt;pre&gt;
DISPATCHERPROTO(MCC_BIA_dispatcher)
{
struct mydata *mydata = INST_DATA(cl,obj);

switch (msg-&gt;MethodID)
{
case OM_NEW: return( MCC_BIA_New (cl, obj, (APTR) msg));
case OM_SET: return( MCC_BIA_Set (cl, obj, (APTR) msg));
case OM_GET: return( MCC_BIA_Get (cl, obj, (APTR) msg));
case OM_DISPOSE: return( MCC_BIA_Dispose (cl, obj, (APTR) msg));
case MUIM_AskMinMax: return( MCC_BIA_AskMinMax (cl, obj, (APTR) msg));
case MUIM_BIA_Changed: return( MCC_BIA_Changed (cl, obj, (APTR) msg));
default: return( DoSuperMethodA (cl, obj, msg)); 
}
}
&lt;/pre&gt;

Each time click on one of the checkboxes you get an MUIM_BIA_changed and the function get's called. Within the function readout the checkboxes and rebuild the bit array which can be read and set by using the MUIA_BIA_Array tag.

Now a notification for MUIA_BIA_Array is required. Do I need to call the class itself by using set(MUIA_BIA_Array) to cause a notification to take place, or is there a more simple way. Calling the class from inside would cause the checkboxes to change and this would result in another MUIM_BIA_changed and we have an endless loop.

The problem is that setting would cause an update of the class internal gadgets. These would cause a notify and the notify would cause another set().

&lt;pre&gt;
//The best way to handle it is to filter out tag list..
struct TagItem *tagitem;
tagitem = FindTagItem( MUIA_xxx_name, taglist );
if( tagitem != NULL )
{
tagitem-&gt;ti_Tag = TAG_IGNORE;
}
&lt;/pre&gt;

do-notify set might still causing infinite loop in some circumstances that vary on super class attributes implementation, and therefore in one class version working fine, in second crashing system...

&lt;pre&gt;
MUIA_ApplicationObject 
MUIA_AppMessage	
MUIA_HelpLine 
MUIA_HelpNode 
MUIA_NoNotify 
MUIA_ObjectID 
MUIA_Parent 
MUIA_Revision 
MUIA_UserData 
MUIA_Version

MUIM_CallHook 
MUIM_Export 
MUIM_FindUData 
MUIM_GetConfigItem 
MUIM_GetUData 
MUIM_Import 
MUIM_KillNotify 
MUIM_KillNotifyObj 
MUIM_MultiSet 
MUIM_NoNotifySet 
MUIM_Notify 
MUIM_Set 
MUIM_SetAsString 
MUIM_SetUData 
MUIM_SetUDataOnce	
MUIM_WriteLong 
MUIM_WriteString 
&lt;/pre&gt;

====Layouts====

&lt;pre&gt;
// Create your GUI 
 app = ApplicationObject,
 SubWindow, wnd = WindowObject,
 MUIA_Window_Title, (IPTR) &quot;Title&quot;,
 MUIA_Window_CloseGadget, FALSE,

 WindowContents, (IPTR) VGroup,
  MUIA_Group_SameWidth, TRUE,

  Child, (IPTR) HGroup,

   Child, (IPTR) VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText1&quot;,
    End,

    [...]

   End,

   Child, VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText2&quot;,
    End,

    [...]

   End,

   Child, VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText3&quot;,
    End,

    [...]

   End,

   Child, VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText4&quot;,
    End,

    [...]

   End,

   Child, VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText5&quot;,
    End,

    [...]

   End,

   Child, VGroup,

    Child, TextObject,
    MUIA_Text_Contents, &quot;33cText6&quot;,
    End,

    [...]

   End,
  End,

  Child, HGroup,

   Child, Scan_button = SimpleButton(&quot;Button&quot;),
   Child, Quit_button = SimpleButton(&quot;Quit&quot;),
  End,
 End,
 End,
 End;
&lt;/pre&gt;

&lt;pre&gt;
 Object *exampleWinObj, *exampleVirtGObj, *exampleContainerObj;

Object *exampleChildObj;

exampleWinObj = (Object *)WindowObject,
                    MUIA_Window_CloseGadget, FALSE,
                    MUIA_Window_Title, (IPTR)&quot;Example Window&quot;,
                    WindowContents, (IPTR) (exampleVirtGObj= (Object *)GroupObject,
                        MUIA_Group_Virtual, TRUE,
                        Child, (exampleContainerObj = (Object *)VGroup,
                        End),
                    End),
                End;

if (exampleWinObj)
{
    int i;
    for (i = 0; i &lt; 10; i++)
    {
        exampleChildObj = HVSpace;

        if (DoMethod(exampleContainerObj, MUIM_Group_InitChange))
        {
            DoMethod(exampleContainerObj, OM_ADDMEMBER, exampleChildObj);
            DoMethod(exampleContainerObj, MUIM_Group_ExitChange);
        }
    }
}
&lt;/pre&gt;

Change the HVSpace for whatever object (group, etc) you want to add..

'''Obsolete Hooks.'''

MUI does not allow own position of Components, only automatic positions available (group concept) but by setting and Layout Hook and add and Left, Top, Width and Height to every Object, you can disable this behaviour

Your notify should preferably invoke a method on the class responsible for the action you want to have executed. Tend to gather more general stuff in window or application subclasses. If there's really no place it belongs then you can have it call a hook instead.

You must add your own layout hook which reports the size. Then simply invoke MUIM_Group_Init/ExitChange on your virtgroup object, as that will cause a re-layout == invocation of your layout hook, which can report new sizes for the contents. If your family tree needs any layout (before rendering) then the layout hook is also the ideal place for this. Take a look at 2b_VRastPort sources on Aminet.

&lt;pre&gt;
/* gcc syntax */
ULONG __attribute__((regparm(3))) Genealo_Layout(struct Hook *hook, struct
MUI_LayoutMsg *lmsg, Object *obj )
{
ULONG result = 0;
int longueur=500, haut=500;

switch(lmsg-&gt;lm_Type)
{
case MUILM_MINMAX:
{
printf(&quot;MinMax\n&quot;);
lmsg-&gt;lm_MinMax.MinWidth = 500;
lmsg-&gt;lm_MinMax.MinHeight = 500;
lmsg-&gt;lm_MinMax.MaxWidth = 500;
lmsg-&gt;lm_MinMax.MaxHeight = 500;
lmsg-&gt;lm_MinMax.DefWidth = 500;
lmsg-&gt;lm_MinMax.DefHeight = 500;
}
break;

case MUILM_LAYOUT:
{
printf(&quot;Layout...\n&quot;);

lmsg-&gt;lm_Layout.Width = longueur;
lmsg-&gt;lm_Layout.Height = haut;
result = TRUE;
}
break;
}
return result;
}
&lt;/pre&gt;

&lt;pre&gt;
ULONG __attribute__((regparm(3))) Genealo_Dispatcher(struct IClass *cl ,
void *msg,Object *obj )
{
Msg msg2 = ( Msg ) msg;
struct Genealo_Data *data;
ULONG result;

switch (msg2-&gt;MethodID)
{
case OM_NEW:
{
result = DoSuperMethodA(cl,obj,msg);
if(obj = (Object *)(result))
{
data = (struct Genealo_Data *)INST_DATA(cl,obj);

data-&gt;LayoutHook.h_Entry = (ULONG(*) ())Genealo_Layout;
data-&gt;LayoutHook.h_Data = data;
SetAttrs(obj,MUIA_Group_LayoutHook, &amp;data-&gt;LayoutHook,TAG_DONE);
}
printf(&quot;%p\n&quot;,result);
return( result );
}
break;
/* ..... */
&lt;/pre&gt;

How to do multithreading in MUI, where the same thread to be running several times simultaneously? Your application tree may only be accessed by one task, as no MUI object is re-entrant nor thread-safe (the
classes are, not the objects). Using 
 DoMethod(app,MUIM_CallHook,&amp;hook)
works fine for running different threads at the same time but when calling the same hook a second time, the first one pauses. 
It is because both threads are running on the same OS task. If you want to have them running simultaneously, you have to create a separate task for each thread, e.g. by CreateProc() from dos.library. 
That method is the same as CallHookA(&amp;hook, app, NULL) which again is the same as just calling the hook-function directly, with 'app' and '&amp;hook' as parameters. Not sure why you think this equals 'multi-threading'. 
If the second event then terminates, the first one continues, but it seems all the local variables have been altered by the second event. Because your code is not reentrant.

====Finding====

there is also a user field in IClass and you can access to this through MUI_CreateCustomClass() as in the Dispatcher. 
&lt;pre&gt;
mcc = MUI_CreateCust..()
mcc-&gt;mcc_Class-&gt;cl_UserData = data;
&lt;/pre&gt;
in the Dispatcher:
&lt;pre&gt;
data = cl-&gt;cl_UserData;
&lt;/pre&gt;

use MUIA_UserData, to store a pointer to a private struct where IT store information that object/related code might need ... e.g pointers to paths/filenames, whatever you like really.

the MUIA_UserData of the object contains the given udata\  and returns the object pointer in this case.

====Area (dragging, RMB etc)====

Let the program know if the user clicks anywhere on the map, the answer is yes: Group class is a child of area class, thus you
can use any attribute of area class, for example MUIA_Pressed.

Let the program know, if and where the user clicked on the map, the answer is no. That's exactly what custom classes are for. 
If any drawing will be manipulated by the user (e.g. an area for painting with the mouse), you write a subclass of Area class. 
Bitmap is just for displaying rastered images. If you want to have a (resizeable) area for application specific drawings, sub-classing Area is still the right thing to do.

If you want to create a bitmap of them tiled, which would then be displayed inside the application. 
For this application it is certainly simpler to use a Column group with Bitmap objects as children, or even a group with a custom LayoutHook that adapts the number of columns to the size of the area.

&lt;pre&gt;
// want the image to be the same size as the picture or if the object has to be bigger then the picture,
// it should be centered (horiz and vertically). 
TextAttr ta = { &quot;topaz&quot;, 8, 0, 0 };
TextFont *Topaz8Font = OpenFont(&amp;ta);

Object *guiobject = ImageObject,
MUIA_Image_Spec, &quot;5:&lt;path&gt;&quot;,
MUIA_Image_FreeHoriz, FALSE,
MUIA_Image_FreeVert, FALSE,
MUIA_Image_FontMatch, TRUE,
MUIA_Font, Topaz8Font,
End;
&lt;/pre&gt;

the Image class is a subclass of Area class, and the Area class can handle input, thus it should be possible to create an Image object that behaves like an ordinary button. Simply try to create an Image object, init the attribute MUIA_Image_Spec as &quot;5:picture_filename&quot; (to load the image via datatypes) and try to init the Area class attribute MUIA_InputMode as MUIV_InputMode_RelVerify.

Then set up a notification for that object, so you will hear from it, open the window...

It might help to have a look at the &quot;default macros&quot; for images and buttons in mui.h to initialize the other attributes (frame type etc.) properly.

# Call MUIM_Group_InitChange on a parent group of your object.
# OM_REMMEMBER it from the group.
# Change the size ie you should modify the data used in MUIM_AskMinMax to fill the structure.
# OM_ADDMEMBER it back.
# Call MUIM_Group_ExitChange on the group.

=====MUIM_DRAW=====

If you want to code yourself what your class will display (eg the wireframe drawing with the mui class1 demoprogram), you implement this overriding the MUIM_Draw method. (have a look at the three examples of custom classes class1 (ok), class2 (ok), class3 (obsolete).

Is it possible to draw on objects outside of MUIM_Draw? MUIM_Draw adds some overhead compared to direct draw (like in gadtools) but overhead is very minimal and you can't notice any slow down either...

Is there a safe way to do draw into a window/MUI-object outside a Draw-event? 
You can draw only inside MUIM_Draw because:
* your object may belong to virtual group and needs clipping (MUI installs this automatically for MUIM_Draw)
* your application can be hidden (in the iconified state) at anytime and thus _rp(obj) is not always valid.
* your object could be hidden for some reason (page and register groups)

If you just want draw new parts of your objects without full redraw? Then you could do something like this:

&lt;pre&gt;
data-&gt;DrawCommand = MY_OWN_DRAW_COMMAND;
MUI_Redraw(obj, MADF_DRAWUPDATE);
&lt;/pre&gt;

And then in your MUIM_Draw method:

&lt;pre&gt;
MyDraw()
{
DoSuperMethod();

if (msg-&gt;flags &amp; MADF_DRAWUPDATE)
{
switch (data-&gt;DrawCommand)
{
/* UPDATE PARTS YOU WANT TO */
}
}
else
{
/* FULL REDRAW */
}
}
&lt;/pre&gt;

In MUIM_Draw simply call BltBitMapRastPort() to display stuff in screen:

 BltBitMapRastPort(data-&gt;RastPort.BitMap, 0, 0, rp, mleft, mtop , mwidth, mheight, 0xc0);

create a bitmap, embed it in a rastport and set this rastport in your MUI renderinfo - then simply call MUIM_DrawBackground, and the background is drawn into your off-screen bitmap. Remember to set back the rastport

within your objects area you ae absolutely free to render whatever you want. And about the rastport: You *should* attach an own rastport to the object, if you use any graphics.library functions: Mui expects to find the objects own rastport in the same state after MUIM_Draw is executed.

If MUIM_Draw not being called (blank area with a frame) then check that you are not calling DoSuperMethodA() first in your MUIM_Draw method and that the MUIM_Draw Method only checks for msg-&gt;flags == MADF_DRAWOBJECT.

&lt;pre&gt;
switch( msg-&gt;MethodID )
{
[...]
case MUIM_Draw: return( draw( class, object, msg ) );
[...]
}
&lt;/pre&gt;

solved the problem, replaced them in the draw method

&lt;pre&gt;
if(!DoSuperMethodA(cl,obj,(APTR)msg)) 
    DoSuperMethodA(cl,obj,(APTR)msg);
&lt;/pre&gt;

Typically your object should have an internal buffer where you store the objects state after the last MUIM_Draw. This allows you to draw only those parts of your map, that need to be updated.

Stuff the parameters into you instance data and call MUI_Redraw() with MADF_DRAWUPDATE. That's what it is for. 
Basically, all rendering is done inside MUIM_Draw. If another method wants to render, it sets up parameters and calls MUI_Redraw().
MUI_Redraw() will then call MUIM_Draw for you.

However, you must be aware that MUIM_Draw might _not_ be called, e.g. when your object is currently hidden. So, MUIM_Draw should only draw; your other methods should do all the other stuff (if you draw an ellipse, you have to store that information somewhere in case a refresh comes in, the application is iconified etc. So, you MUIM_xxx_DrawEllipse will store all that information somewhere (adding the ellipse to a list or drawing it into an offscreen bitmap), then it will call MUI_Redraw(TheObject,MADF_DRAWUPDATE) to update the display).

What about a 3ds viewer with mui buttons ? Titler display opengl and mui on the same window, so what class/methods can use to display/redirect opengl output onto mui win? 
You need an area subclass to display your GL stuff in MUI window. You only need an offscreen bitmap which is blitted to the window in your MUIM_Draw method.

InitRastPort(&amp;data-&gt;RastPort) is done in other part of code! Once opengl context is initialized you can render to your offscreen bitmap using GL calls.

Have a look to aminet/wazp3d in soft3d_opengl.c. Inside there is code to start mesa for aros
(seek ifdef aros...) But aros mesa cant render in a bitmap: You will need to use your mui window + glscissor

[http://aminet.net/package/dev/mui/GLArea_src AreaGL] may be helpful.

&lt;pre&gt;
MUIA_Image_FontMatch
MUIA_Image_FontMatchHeight
MUIA_Image_FontMatchWidth
MUIA_Image_FreeHoriz
MUIA_Image_FreeVert
MUIA_Image_OldImage
MUIA_Image_Spec
MUIA_Image_State
&lt;/pre&gt;

=====MUI_Redraw=====

With MUI_Redraw(), an object tells itself to refresh, e.g. when some internal attributes were changed. Calling MUI_Redraw() is only legal within a custom class dispatcher, &quot;using this function within an applications main part is invalid!&quot;. To solve the same problem with my GUI for the UAE port of AROS, and simply wrapped the MUI_Redraw inside a custom method.

&lt;pre&gt;
MUIM_UAEDisplay_Update, struct MUIP_UAEDisplay_Update *,
({

if (message-&gt;top &gt;= data-&gt;height || message-&gt;bottom &lt;= 0)
return TRUE;

if (message-&gt;top &lt;= 0)
message-&gt;top = 0;

data-&gt;update_top = message-&gt;top;
data-&gt;update_bottom = message-&gt;bottom;

MUI_Redraw(self, MADF_DRAWUPDATE);

return TRUE;
})

case OM_SET:
{
struct TagItem *tagitem, *tagstate = msg-&gt;ops_AttrList;
while( tagitem = NextTagItem( &amp;tagstate ) )
{
case MUIA_[classname]_Update:
{
MUI_Redraw( obj, MADF_DRAWUPDATE);
break;
}
}
return( DoSuperMethodA( cl, obj, msg ) );
}
&lt;/pre&gt;

But better might be making just attribute to passing array of vectors.. When it's passed redraw is called.. or custom method:

&lt;pre&gt;
case MUIM_[classname]_Update:
{
MUI_Redraw( obj, MADF_DRAWUPDATE);
return( 0 );
}
&lt;/pre&gt;

You must not completely intercept OM_SET. Program sub-class some MUI class like Area.mui or Group.mui and they have their own attributes that might be set during program running.. Intercepting them or redrawing window might cause illegal actions..

=====Groups=====

The group class was designed to contain other groups and gadgets not to be a gadget by self. It's a side effect because it's a subclass of area class (making it a subclass of notify class and copying part of methods would be senseless). Well... if you want create an image button (button with text and gfx), apart from the group class it could be done by creating subclass of MUIC_Area which in MUIM_Setup load necessary picture(s) using datatypes.library, draw it in MUIM_Draw and dispose in MUIM_Cleanup. 
Btw. the group class isn't a subclass of area class by mistake.

Only group objects can have children. To get children there's MUIA_Group_ChildList. Walking through list is done with NextObject(). Example:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
	Object *obj1;
	struct List *children	= (struct List *)XGET(_maingrp, MUIA_Group_ChildList);
	APTR pObj               = GetHead(children);

	// Parse the children
	while(NULL != (obj1 = NextObject((Object **)&amp;pObj)))
	{
		printf(&quot;ID is: %ld\n&quot;, XGET(obj1,MUIA_ObjectID));
	}
&lt;/syntaxhighlight&gt;

To get parent there's MUIA_Parent.

If you don't know number of children or it's variable you would have to alloc some memory for the method struct (
sizeof(struct MUIP_Group_Sort) + sizeof(Object *) * num_children) and then call it with DoMethodA(obj, alloc'd_method). Then free the method struct again.

num_children = number of successful NextObject() calls on child list.

There's MUIM_Group_Sort method allowing you to tell the group object the exact order of the childs. NListview.mcc uses this and the group_initchange/group_exitchange stuff to dynamically show/hide scrollbars.

Almost all attributes you set on a group will be forwarded to its children. You can set MUIA_Group_Forward to FALSE to prevent this (while setting the tag in question).

a MUIM_Group_Insert method for inserting a child into a group in specified place, just like MUIM_Family_Insert. Currently move the child list from the group to my private family, insert the new child into my family with MUIM_Family_Insert and move all children from the family to the group again. on groups just like MUIM_Family_Sort on families.

&lt;pre&gt;
#define MUIM_Group_Sort 0x80427417 /* V4 */
DoMethod(parent, MUIM_Group_InitChange);
    DoMethod(parent, REMMEMBER, obj);
    set(obj, MUIA_FixWidth, 100);  // just some changing beyond the object borders
    DoMethod(parent, ADDMEMBER, obj);
DoMethod(parent, MUIM_Group_ExitChange);
&lt;/pre&gt;

InitChange/ExitChange during setup/cleanup is not a good idea. You should add your childs in MUIM_Setup *before* the DoSuperMethod() and remove your childs in MUIM_Cleanup *after* the DoSuperMethod().

should not disable groups anyway just to disable its children. Better disable each child for itself, since this will indeed look nicer. You can do this with one DoMethod, e.g. MUIM_MultiSet or MUIM_SetUData

Group is intended for objects having visual representation. For a text editor, if you group Buffer and Display objects it will be a bit tricky since Buffer isn't really a gadget. Editor should be a subclass of Display, and Buffer should be attached via pointer in object data structure. It better shows relations between Buffer and Display, they are not just a gadgets in a group.

Basically you have to call MUIM_InitChange before removing or adding objects and then call MUIM_ExitChange:

&lt;pre&gt;
DoMethod(yourgroup,MUIM_InitChange)
DoMethod(OM_ADDMEMBER,newobject)
DoMethod(yourgroup,MUIM_ExitChange)
&lt;/pre&gt;

to trigger a relayout by doing a MUIM_Group̠InitChange and MUIM_Group_Exitchange on the _parent(obj)

Every object should be responsible for passing the new settings on to its children. Like when you have a subclass of group that contains a numeric and a string gadget, it will have some attribute that holds a structure of the gadgets' respective values, and the group object has to know which value goes to which of its children and set them accordingly when itself it receives an OM_SET. Then you'd ideally do a set(mywindow,PREFS_ATTRIBUTE,&amp;some_structure) and the object tree would handle the rest by itself. 
Then there's no other way than to remember each object that needs to be updated in some structure and set() it &quot;by hand&quot;.

virtgroup.mui are internal part of MUI (they're &quot;inside&quot; muimaster.library).

The virtual group it's like a container that can scroll if the content exceeds its boundaries. A Virtual group makes sense inside a ScrollGroup.

you should not use MUIA_Pressed for notifying toggle gadgets (only for RelVerify ones like buttons). Use MUIA_Selected.

&lt;pre&gt;
window
---&gt; group (&lt;--- set MaxWidth/MaxHeight here, works)
------&gt; scrollgroup
---------&gt; virtgroup
------------&gt; text
------&gt; rectangle (&lt;--- or here, works, too)
&lt;/pre&gt;

How to get a virtgroup which is only in the horiz direction virtual w/o using scrollgroup (use MUIA_Scrollgroup_FreeVert, FALSE) or is there a way to have the scrollbar hidden all the time?

You need a [http://morphosambient.cvs.sourceforge.net/morphosambient/ambient/virtgroupclass.c?revision=1.5&amp;view=markup custom class] which uses fixed height or width thus locking virtgroup vertically or horizontally.

Adding objects to a group on the fly. First you have to '''init''' the changes you want to do, then '''perform''' them and then declare you have '''finished'''. Example of code to add or remove a group from another group:
&lt;syntaxhighlight lang=&quot;c&quot;&gt;
        Object *_maingrp = .... // the container
        Object *_subgrp = .... // the content

	// add the subgroup
	if(DoMethod(_maingrp, MUIM_Group_InitChange))
	{
           DoMethod(_maingrp, OM_ADDMEMBER, _subgrp);
           DoMethod(_maingrp, MUIM_Group_ExitChange);
	}

	// remove the subgroup
	if(DoMethod(_maingrp, MUIM_Group_InitChange))
	{
           DoMethod(_maingrp, OM_REMMEMBER, _subgrp);
           DoMethod(_maingrp, MUIM_Group_ExitChange);
	}
&lt;/syntaxhighlight&gt;

&lt;pre&gt;
LONG sigs;
DoMethod(app,MUIM_Application_NewInput,&amp;sigs);
&lt;/pre&gt;
This seems to be a general pitfall for MUI programmers, but 'sigs' really has to be initialized to zero! 
It's worse: sigs is the result of Wait(), i.e. the signals received by the process. So if you give a random value, MUI will think random signals were received, and act on these. Normally the effect of this is not noticeable, as a message-port signal will just cause a &quot;while(GetMsg(port))&quot;, which will immediately terminate, but in theory serious problems could arise

Want to reproduce the Workbench way of dealing with icons. Want to be able to move images from a point to another. Derive a Group (virtual or otherwise) with its own custom layout hook and make the objects of that group Draggable; when you get a drop event, re-layout the group (force this using MUIM_Group_InitChange = followed by ExitChange)

[http://www.henning-thielemann.de/ProgramsE.html TableGroup]

&lt;pre&gt;
MUIM_Group_ExitChange
MUIM_Group_InitChange
MUIM_Group_Sort

MUIA_Group_ActivePage
MUIA_Group_Child
MUIA_Group_ChildList
MUIA_Group_Columns
MUIA_Group_Horiz
MUIA_Group_HorizSpacing
MUIA_Group_LayoutHook
MUIA_Group_PageMode
MUIA_Group_Rows
MUIA_Group_SameHeight
MUIA_Group_SameSize
MUIA_Group_SameWidth
MUIA_Group_Spacing
MUIA_Group_VertSpacing
&lt;/pre&gt;

=====RMB and LMB=====

RMB menus to gadgets. Context menus are a feature of the Area class, and can be set with MUIA_ContextMenu, or dynamically created by overloading MUIM_ContextMenuBuild. 
Is it possible to use rmb as lmb in MUI? Yes, you should override MUIM_ContextMenuBuild for your object. Create fake Menu object (just with one menu and no items), give it to MUIA_ContextMenu attribute and do your job in MUIM_ContextMenuBuild, returning NULL from there (it means no context menu will be drawn). 
Well, its not easy, because there is no simple method to get informed about RMB _release_. You have to sub-class Text class and write own MUIM_HandleInput, which is mentioned in docs as obsolete. But unfortunately MUI event handlers don't react to RMB (bug in MUI?). can look at the MUIMine source (on Aminet). It does something like that and mentions problems with the RMB. It's also using MUIM_HandleInput.

=====Dragging=====

&lt;pre&gt;
ULONG MyList_DragQuery(struct IClass *cl,Object *obj,struct MUIP_DragDrop *msg)
{
    if (msg-&gt;obj==obj)
    {   //return(MUIV_DragQuery_Accept);
        return(DoSuperMethodA(cl,obj,(Msg)msg));
    }
    else
    {
        if (msg-&gt;obj==(Object *)muiUserData(obj))
            return(MUIV_DragQuery_Accept);

        else
            return(MUIV_DragQuery_Refuse);
    }

}
&lt;/pre&gt;

Whenever there are no conflicting inputs, MUI starts the drag operation immediately. If the LMB is needed for anything else (ie on a button), MUI starts dragging like specified in the prefs. set MUI_Draggable, TRUE to an object of a MUI_Area subclass

&lt;pre&gt;
get(obj,MUIA_List_DropMark,&amp;dropmark);
DoMethod(obj,MUIM_List_InsertSingle,entry,dropmark);
&lt;/pre&gt;

Note that you must get the dropmark from the destination object, *not* from the source.

One mode allows you to enter the data in the string gadget. The other allows dragging.  In the dragging mode you make the StringObject a TextObject.  That way you have no problems dragging the objects around.  You could also try making a Custom string class.

How to get MUI to report the dropped position relative to the object that is accepting the drop?  Also is there some way to get mui to report based on the top, left of the object that was grabbed and not report from where you grabbed the object at? If the position is screen based, just substract from it _mleft(obj) and _window(obj)-&gt;LeftEdge, _mtop(obj and _window(obj)-&gt;TopEdge.

Is there a way to react to a dragging of a workbench icon into an appwindow created with MUI.
The desktop manager sends message to an application only when user stopped dragging so it is not possible.

MUI has its way to handle d&amp;d with MUIM_DragBegin/DragFinish for its MUI object.... 
MUIM_DragBegin/Finish are for internal MUI D&amp;D. AppWindow messages are externally generated and MUI can not control it.

This is typically a method that you usually won't call yourself (like the drag'n'drop methods of area.mui)

&lt;pre&gt;
MUIM_AskMinMax
MUIM_Cleanup
MUIM_ContextMenuBuild
MUIM_ContextMenuChoice
MUIM_CreateBubble
MUIM_CreateShortHelp
MUIM_DeleteBubble
MUIM_DeleteShortHelp
MUIM_DragBegin
MUIM_DragDrop
MUIM_DragFinish
MUIM_DragQuery
MUIM_DragReport
MUIM_Draw
MUIM_DrawBackground
MUIM_HandleEvent
MUIM_HandleInput
MUIM_Hide
MUIM_Setup
MUIM_Show

MUIA_Background
MUIA_BottomEdge
MUIA_ContextMenu
MUIA_ContextMenuTrigger
MUIA_ControlChar
MUIA_CycleChain
MUIA_Disabled
MUIA_Draggable
MUIA_Dropable
MUIA_ExportID
MUIA_FillArea
MUIA_FixHeight
MUIA_FixHeightTxt
MUIA_FixWidth
MUIA_FixWidthTxt
MUIA_Font
MUIA_Frame
MUIA_FramePhantomHoriz
MUIA_FrameTitle
MUIA_Height
MUIA_HorizDisappear
MUIA_HorizWeight
MUIA_InnerBottom
MUIA_InnerLeft
MUIA_InnerRight
MUIA_InnerTop
MUIA_InputMode
MUIA_LeftEdge
MUIA_MaxHeight
MUIA_MaxWidth
MUIA_Pressed
MUIA_RightEdge
MUIA_Selected
MUIA_ShortHelp
MUIA_ShowMe
MUIA_ShowSelState
MUIA_Timer
MUIA_TopEdge
MUIA_VertDisappear
MUIA_VertWeight
MUIA_Weight
MUIA_Width
MUIA_Window
MUIA_WindowObject
&lt;/pre&gt;

====register (TABS)====

how can a child (a tab) of a register (Tab) know that he is currently visible w/o knowing in which tab it is? 
Have a .mcc which is a subclass of group and creates a row of cycletitle-objects (like cycle gadget, but with a fixed title string within the cyclegadget) where each button represents a window. The group gets notified (by notifyintuition.library) when a new window is opened or one win gets closed. 
or create a subclass of group which has a new attribute of something like MUIA_XGroup_PageIndex. You could then compare this to the &quot;main groups&quot; objects active page. You should know the &quot;main group&quot; object as it gets this from reading MUIA_Parent of the &quot;tab page&quot;.

 if tabpage.pageindex = tabpage.parent.activepage then (simple pseudo code)

Or create a subclass of register which as well as MUIA_Group_ActivePage has say MUIA_Group_ActivePageObj which is set on a change of MUA_Group_ActivePage. You could then compare this to the &quot;tab page&quot;.

 if tabpage = tabpage.parent.activepageobj then (simple pseudo code)

Or create a new method of register that returns the current obj (similar to your above idea) but as a method it will be usable for all your register groups.

&lt;pre&gt;
MUIA_Register_Frame
MUIA_Register_Titles
&lt;/pre&gt;

====Lists====

* The list class is a class which can hold and manipulate (to some extent) a linked list of data. 
* The listview class is a group subclass which handles the layout and interconnection of a list and the required sliders.

Listtree which uses images for the branches, but afaik doesn't allow you to change the image.

At startup the list is empty and add entries with MUIM_List_InsertSingle.

MUIA_List_SourceArray to assign an strarray then use the MUIA_List_Active result as the index for that array.

MUIM_List_Remove

listview to have the width of the text inside and no more and no less.

 MUIA_List_Format - MAXWIDTH/MINWIDTH

 MUIA_List_AdjustWidth, TRUE

to insert strings in a ListView:

 DoMethod(projectfiles,MUIM_List_InsertSingle,(long unsigned int)TXT.sfilename.c_str(),(IPTR)MUIV_List_Insert_Bottom);

COPYING you will need to define Construct &amp; Destruct hooks as List object does NOT copy your string (just takes a pointer) until you order otherwise. If you got simple one column list and you will be satisfied storing just strings in it, MUI offers builtin construct hooks for this. Refer autodocs for construct &amp; destructs (must set both!).

 MUIA_List_ConstructHook, MUIV_List_ConstructHook_String

 MUIA_List_DestructHook, MUIV_List_DestructHook_String

MUIV_List_Remove_Selected

You can call MUIM_List_CreateImage as soon as the list class completed its setup method. You must call MUIM_List_DeleteImage before the list completes its cleanup method.

MUIM_Insert_xyz inserts an Object to a List, this meant that the List class can handle any Object and so you can not add only Strings to it. only a Pointer is stored and not the content of it. Note the List is not responsible for Displaying its' content, this was done by the Listview and by default it´s Displayhook expects pointers to a Text in the list.

how to add a small image next to a string in the list? game/think/MUIMastermind.lha might have a simple approach without CreateImage() and so on.

Reading MUIA_List_Active gives me the entry number, but if the order's changed, it doesn't mean anything? 
GetEntry returns pointer to your entry and you can access any column you wish. It's your private pointer anyway.

If you want a page background for an app, simply use MUIA_Background, MUII_PageBack for your group object.

'''Obsolete Hooks.''' If hooks are being used, multicolumn List object to display the result but want to add title to columns

&lt;pre&gt;
HOOKPROTO(ResultList_Display, ULONG, char **array, struct ReqData *reqdata)
{
if (reqdata) {

int n;
for (n=0; n&lt;reqdata-&gt;nb ; n++) {
*array++ = reqdata-&gt;columns[n];
}
} else {
reqdata = (struct ReqData *)hook-&gt;h_Data; // list titles

int n;

for (n=0; n&lt;reqdata-&gt;nb ; n++) {
*array++ = reqdata-&gt;columns[n];
}
}

return 0;
}
MakeStaticHook(hook_ResultList_Display, ResultList_Display);

Somewhere in your code you set h_Data:

hook_ResultList_Display.h_Data = (APTR)reqdata_titles;
&lt;/pre&gt;

You can either build a hook object that h_entry part is your function and use MUIM_CallHook or subclass the object id_main_add so that it handles a particular method, and in the case of your method is received call your add some function (it's the recommended way).. the callhook stuff would be something like

 struct Hook h = { addsome, NULL, NULL };

 DoMethod(id_main_add, MUIM_Notify, MUIA_Pressed, FALSE, id_main_add,2, MUIM_CallHook, &amp;h );

for AROS you have to change
&lt;pre&gt;
#define MUI_LIST_DISP(x,y) ULONG SAVEDS ASM x (REG(a2,char **array), REG(a1, y ))
to
#define MUI_LIST_DISP(x,y) ULONG SAVEDS ASM x (REG(a0,struct Hook *h), REG(a2,char **array), REG(a1, y ))
&lt;/pre&gt; 
so that a pointer to the Hook is the 1st argument. Same for other [hook macros http://aros.sourceforge.net/documentation/developers/headerfiles/aros/asmcall.h].

We have some hints about hooks in our [documentation http://aros.sourceforge.net/documentation/developers/app-dev/portable.php#hooks]

&lt;pre&gt;
MUIM_List_Clear
MUIM_List_CreateImage
MUIM_List_DeleteImage
MUIM_List_Exchange
MUIM_List_GetEntry
MUIM_List_Insert
MUIM_List_InsertSingle
MUIM_List_Jump
MUIM_List_Move
MUIM_List_NextSelected
MUIM_List_Redraw
MUIM_List_Remove
MUIM_List_Select
MUIM_List_Sort
MUIM_List_TestPos

MUIA_List_Active
MUIA_List_AdjustHeight
MUIA_List_AdjustWidth
MUIA_List_AutoVisible
MUIA_List_CompareHook
MUIA_List_ConstructHook
MUIA_List_DestructHook
MUIA_List_DisplayHook
MUIA_List_DragSortable
MUIA_List_DropMark
MUIA_List_Entries
MUIA_List_First
MUIA_List_Format
MUIA_List_InsertPosition
MUIA_List_MinLineHeight
MUIA_List_MultiTestHook
MUIA_List_Pool
MUIA_List_PoolPuddleSize
MUIA_List_PoolThreshSize
MUIA_List_Quiet
MUIA_List_ShowDropMarks
MUIA_List_SourceArray
MUIA_List_Title
MUIA_List_Visible
&lt;/pre&gt;

====Strings====

How to get notification of when an MUI string gadget is made active? So I know when the user has clicked on the gadget and activated the cursor, but before they start typing anything? I've tried setting MUIA_InputMode to MUIV_InputMode_RelVerify and MUIV_InputMode_Immediate, but neither work with either the MUIA_Pressed or MUIA_Selected notifications.

Build a subclass of String.mui and do what ever you need to do in the MUIM_GoActive and MUIM_GoInactive methods.

Converts input from a 'text box' (using Zune/MUI) to a floating point number. 
&lt;pre&gt;
get(my-string-object, MUIA_String_Contents, &amp;str);
    stcd_l(str, &amp;num);
&lt;/pre&gt;

Subclass the gadget and overload MUIM_GoInactive. Just be sure you've considered every situation the user may be in, e.g. leaving the gadget temporarily to copy the rest of the value from some other place or similar. 
Needed to subclass string gadget and add own event handler. As a workaround (imho), return DoSuperMethodA(cl,obj,(Msg)msg); when you return 0.

You can notify MUIA_String_Contents, which will be triggered each time the content change.
You can probably also use MUIA_Window_ActiveObject, which should be set to everything but the string gadget when it goes inactive. And if you use one of the string gadget replacements then there's also the possibility of overloading MUIM_GoInactive for the string class (Textinput, Newstring or Betterstring). But keep in mind that inactivating the gadget (using tab, the mouse, opening a new window or similar) should never have a confirming effect!

&lt;pre&gt;
MUIA_String_Accept
MUIA_String_Acknowledge
MUIA_String_AdvanceOnCR
MUIA_String_AttachedList
MUIA_String_BufferPos
MUIA_String_Contents
MUIA_String_DisplayPos
MUIA_String_EditHook
MUIA_String_Format
MUIA_String_Integer
MUIA_String_LonelyEditHook
MUIA_String_MaxLen
MUIA_String_Reject
MUIA_String_Secret
&lt;/pre&gt;

====Numeric (slider, knobs, levelmeters etc)====

Releasing the button when NOT over the gadget is well regarded to be a &quot;cancel&quot; action. Like
&quot;whoops! I accidentally pressed the button, but now I don't want to exit, so I'll move my mouse away&quot; 
Sliders also keep the value you dragged them to if you release the mouse outside the gadget.

How about getting a notification on a slider when the slider is released only? I tried MUIA_Pressed but that didn't work.  If you also use Area.mui/MUIA_InputMode. Also, I noted that MUIA_Slider_Level says (OBSOLETE). Use 
MUIA_Numeric_Value instead.

If pressing TAB key cycles options. How can I implement that ? 
You just set MUIA_CycleChain (area class) as TRUE in all the objects you want to be part of the cycle-chain.

Cycle object 
&lt;pre&gt;
STRPTR colors[] = { &quot;Red&quot;, &quot;Green&quot;, &quot;Blue&quot;, NULL };
ULONG colorsV;
STRPTR ch;
// then in the program...
get(cy1, MUIA_Cycle_Active, &amp;colorsV);
ch = (char *)colorsV;
&lt;/pre&gt;

Cycle_active contains the NUMBER of the selected item. To get the string you need to do something like this:

 ch = colors[ colorsv ];

Since MUIA_Cycle_Entries is [I..] the only way is to create a new cycle every time you want to change the entries. To do this you do MUIM_Group_InitChange on the group containing the cycle, then OM_REMMEMBER the old one, OM_ADDMEMBER the new one and do MUIM_Group_ExitChange. You may have to use MUIM_Group_Sort to get the cycle to the right place or put it into a separate group.

Can anyone tell me if it is possible to create a dynamic cycle gadger
You can &quot;emulate&quot; it by removing the gadget and creating a new one with MUIA_Cycle_Entries changed. Use MUIM_Group_InitChange/ExitChange for this.

&lt;pre&gt;
MUIA_Cycle_Active
MUIA_Cycle_Entries
&lt;/pre&gt;

a slider with gradient background. You can set gradient by MUIA_Background (but attribute string is undocumented) or maybe overloading MUIM_DrawBackground...

Sliders that look like a regular button when not pressed, but when pressed, they pop up and become a slider. They save a lot of space. It's a NumericbuttonObject - it's used in the demo program Slidorama.

&lt;pre&gt;
MUIM_Numeric_Decrease
MUIM_Numeric_Increase
MUIM_Numeric_ScaleToValue
MUIM_Numeric_SetDefault
MUIM_Numeric_Stringify
MUIM_Numeric_ValueToScale

MUIA_Numeric_CheckAllSizes
MUIA_Numeric_Default
MUIA_Numeric_Format
MUIA_Numeric_Max
MUIA_Numeric_Min
MUIA_Numeric_Reverse
MUIA_Numeric_RevLeftRight
MUIA_Numeric_RevUpDown
MUIA_Numeric_Value
&lt;/pre&gt;

====Menus====

Mui has its own methods for menus but the old NewMenu calls can still be used.

The best way is maybe to create&amp;dispose the context menus you need in a subclass of window class. 
Menu items are set for currently active window? In the case you can set up different menu for each of window, preferably inside window subclass, and with notification which will call method or attribute or your's window class and it'll be able to react.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
&lt;/syntaxhighlight&gt;

How to notify on pressing shortcut combination with shift, control and alt keys? I tried such code:
 DoMethod(win, MUIM_Notify,MUIA_Window_InputEvent, &quot;-control x&quot;,app, 2,MUIM_Application_ReturnID,MEN_RUN);
but I get notification each time X button is pressed (no matter whether control is pressed).

You need a normal eventhandler in your class for that. Please do not use returned stuff? So I see the only way is to use rawkey hook. Want such shortcuts for menu items, there are too many of them so I can't use combinations with Amiga for each one. menu item &quot;MUI Settings...&quot;. To set a notify to the menu item that calls MUIM_Application_OpenConfigWindow

The way to do this would be to implement a MenuTrigger method in one of your subclasses (MUIC_Window or the window's Root MUIC_Group are always safe picks) and have a MUIA_Window_MenuAction notification call it. There you could either have a switch with all the IDs, or simply use methodIDs instead of menu IDs and just do it like:

&lt;pre&gt;
ULONG mMenuTrigger(struct IClass *cl, Object *obj, struct mpMenuTrigger *msg)
{
DoMethod(obj, msg-&gt;menutriggercommand);
}
&lt;/pre&gt;
Once all menu triggers are nicely done as methods (say MUIM_MyClass_Open, MUIM_MyClass_DoSomething) and you've built a menu using those IDs, you could also implement an eventhandler in the Group subclass I mentioned and simply map raw keys into methods again. This could be done nicely using something like:
&lt;pre&gt;
struct MenuKey
{
ULONG methodForQualifierShift;
ULONG methodForQualifierControl;
ULONG methodForQualifierAlt;
ULONG methodForQualifierAltShift;
};
&lt;/pre&gt;
and then have these mapped like
&lt;pre&gt;
struct MenuKey hotkeys[256] = 
{
{0, MUIM_MyClass_Jump}, // RAWKEY_TILDE
{MUIM_MyClass_First}, // RAWKEY_1
....
};
&lt;/pre&gt;

so you can easily map every key combo into a method.

Well... just one of the many possible approaches to this problem, but one that will leave you with a nice OO structure in the source.

Added a check for msg-&gt;imsg-&gt;Code==MENUDOWN which reatcs the RMB being pressed and stops the timer. I also did the reverse msg-&gt;imsg-&gt;Code==MENUUP which would start the timer again. BUT - once the Menu is open the mouse button presses are attached to the menu and not my window/object so the MENUUP button event is never seen so my timer remains stopped and does not start again after using a menu. 
You could use MUIA_Window_MenuAction to be notified when a menuitem was chosen, 
 DoMethod (win, MUIM_Notify, MUIA_Window_MenuAction, MUIV_EveryTime, obj, 2, MM_Main_MenuAction, MUIV_TriggerValue); 
Not sure if the attribute gets triggered when no item was selected...

Checking window activation does not help either as the window remains active when a menu is opened so nothing changes. You could add a global input handler for checking of RMB pressing and releasing and then also check if the mouse pointer is over your window...

'''Redundant''' MUIA_Application_Menu and MUIA_Window_Menu (old New Menus system)

'''Redundant''' MUIM_Application_GetMenuCheck, MUIM_Application_GetMenuState, MUIM_Application_SetMenuCheck, MUIM_Application_SetMenuState

'''Redundant''' MUIM_Window_SetMenuCheck, MUIM_Window_SetMenuState,  MUIM_Window_GetMenuCheck, MUIM_Window_GetMenuState

&lt;pre&gt;
MUIA_Menu_Enabled
MUIA_Menu_Title
&lt;/pre&gt;

=====MenuStrip=====

Menustrip class is the base class for MUI's object oriented menus. Its children are objects of Menu class, each of them describes exactly one menu.

A Menustrip object doesn't feature many options itself, but as a subclass of Family class, it simply acts as father for multiple Menu objects.

The Menustrip object is usually specified as a child of either Application class or window class with the attributes MUIA_Application_Menustrip or MUIA_Window_Menustrip.

Have you tried using MenustripObject and MenuObject instead of MenuitemObject, and MUIA_Menu_Title instead of MUIA_Menitem_Title? Though to be honest, I'm not sure if all of those macros exist in AROS.

the hierarchy is:    MenustripObject -&gt; MenuObject -&gt; MenuitemObject

Using Menuitems everywhere worked before, but it was not compatible with MUI and was changed.

With family objects (from Wanderer/Info):

DoMethod(_win(obj), MUIM_Notify, MUIA_Window_MenuAction, MUIV_EveryTime, obj, 2, MUIM_MySubClass_MenuThingy, MUIV_TriggerValue);

Read more about Menus in MUIA_Window_MenuAction section of muidevs.

See also DiskSpeed.c in DiskSpeed drawer of the contrib-source of AROS.

In one MenuItem tag there wasn`t a &quot;MUIA_UserData&quot; tag identifier in front of the ID of that menuitem and so on a dispose gcc somehow freed an area in memory that caused the crash where sas/c didn`t somehow.

&lt;pre&gt;
entry = MUI_MakeObject(MUIO_Menuitem,advance_name_translation(i),NULL,0,0);
set(entry,MUIA_UserData,i);
DoMethod(entry,MUIM_Notify,MUIA_Menuitem_Trigger, MUIV_EveryTime, entry,6, MUIM_CallHook, &amp;civstandard_hook, diplomacy_tech, pdialog, plr0-&gt;player_no,entry);
DoMethod(menu_title,MUIM_Family_AddTail, entry);
&lt;/pre&gt;

&lt;pre&gt;
MUIA_Menustrip_Enabled
&lt;/pre&gt;

====Requesters====

 MUI_Request(app, mainwnd, 0L, &quot;Sorry...&quot;, &quot;Close&quot;, &quot;...but this feature is not yet implemented&quot;, NULL);

Either create your new objects outside this huge MUI constructions, and in there use just a pointer, or get rid of the &quot;End&quot; macro and exchange it with &quot;TAG_DONE)&quot;. On MOS and AmigaOS, the NewObject variadic function is kept in the static library. It takes most of the parameters on the stack - thanks to that the implementation of NewObject calls the NewObjectA function. Everything works perfect, and the typical MUI macros may be easily used.

This, however, is not the case when you compile for AROS. Here, NewObject is a variadic macro, not a function. Thanks such approach we do not need any custom compiler in case of systems, where the arguments of variadic functions are passed partially through registers and partially through the stack (This is the case of PPC and x86_64, this is also the reason why both OS4 and MOS require specially patched compilers).

Since NewObject is a macro, the gcc's preprocessor expects the list of macros arguments enclosed within parentheses. In MUI macros it is not the case.

=====ASL requester=====

this should [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=1430&amp;forum=2&amp;post_id=11642#forumpost11642 help]:

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
struct FileRequester *req;

if ((req=MUI_AllocAslRequestTags(ASL_FileRequest,
ASLFR_Window,win ,
ASLFR_TitleText, &quot;A requester for AmiDevCpp&quot;,
ASLFR_InitialDrawer , &quot;T:&quot;,
ASLFR_InitialFile, &quot;foo.txt&quot;,
ASLFR_InitialPattern , &quot;#?.txt&quot;,
ASLFR_DoPatterns , TRUE,
ASLFR_RejectIcons , TRUE,
TAG_DONE))) {

if (MUI_AslRequestTags(req,TAG_DONE)) {
/* you can find the drawer in req-&gt;fr_Drawer and the file in req-&gt;fr_File */
}
}
&lt;/syntaxhighlight&gt;

MUI_AslRequest() functions and MUI takes care of window refresh for you.

&lt;pre&gt;
MUIA_Popasl_Active
MUIA_Popasl_StartHook
MUIA_Popasl_StopHook
MUIA_Popasl_Type
&lt;/pre&gt;

====Pop Up Pen etc====

MUIA_Window or MUIA_WindowObject? MUIA_Window should refer to struct Window * but MUIA_WindowObject to Object *

Both are always NULL for a popup list, whether open or not.

An interesting point is that the window object pointer supplied to the MUIA_Popobject_WindowHook is non-NULL. 
checking for whether popup is open such work around anyway? Popup object is open only a while, when user clicked popup button and popup object appeared on screen- any clicking causes popup object to disappear. So, I can't even imagine where and why are you checking this.. From 2nd parallel running task?

If popup object is made by you, you always can subclass any MUI class. And this way you will get all methods and attributes like f.e. OM_SET/OM_GET and MUIM_Setup/MUIM_Cleanup/MUIM_Show/MUIM_Hide. Probably listening on show/hide might help checking whether popup is currently open. This method probably should work also for other MUI applications, if you're not owner of app, but making monitor software- but instead subclassing get and store dispatcher address, then put your own, and listen methods/attrs like above, then call original dispatcher to return control to original application.

It looks like [http://www.sasg.com/mui/autodocs/MUI_Popstring.html Popstring] has special hooks for this task 
* MUIA_Popstring_OpenHook
* MUIA_Popstring_CloseHook

Shift up/down is (normally) bound to page up/down, and if the listview hasn't been drawn once, then there are no page dimensions.

DoMethod(PP_String, MUIM_Notify, MUIA_String_Acknowledge, MUIV_EveryTime, App_p, 2, MUIM_Application_ReturnID, RID_EXECUTE);

A notify watch if a tag changes (for the given object) - MUIA_String_Acknowledge is a tag of the string class (not the Popph-string) and is set (and therefor changed) for the string object. So the notify must be on this object, rather than the container (which is Popph)

Either get the pointer to the internal string-object, and setup a notify on this (and do try to avoid ReturnID's ;-) ) Should just be to forward MUIM_Notify to the child objects, preferably only if OM_GET returns TRUE for the tag in question. I.e. if OM_GET returns TRUE for the Popph object itself (an Area class tag probably) then keep the notify, otherwise try to see which of the children supports it. Or maybe it'd be better if Popph introduced two new methods a la MUIM_Popph_NotifyString &amp; List. Then one could use either of these to setup a notify on an internal object.

nothing wrong with ObtainBestPenA() if you don't want the user to configure the pen values (which you often do want) - though avoid placing the pen-stuff in MUIM_Show/Hide, it should be MUIM_Setup/Cleanup, otherwise it'll re-allocate pens each time you resize the window

If you want the user to be able to configure the pens then you do so by using the Poppen-object together with MUI_ObtainPen() - here's a snip from MUI_PopPen.Doc:

Anyway, you do not have to care about the internals of this class. Just create it like

obj = MUI_NewObject(MUIC_Poppen,
MUIA_CycleChain , 1,
MUIA_Window_Title, &quot;Followed Links Color&quot;,
TAG_DONE);

somewhere in your prefs window and everything will be fine. You can get/set the current color from a Poppen object by using the MUIA_Pendisplay_Spec attribute. The resulting struct MUI_SpenSpec may then be saved somewhere in your preferences and used as parameter for MUI_ObtainPen() and MUI_ReleasePen().

comes back in the format of: &quot;rxxxxxxgxxxxxxbxxxxxx&quot;. There are 3 parameters in MUI_ObtainPen() *mri , *spec &amp; flags.l

look in libraries/mui.h and you will fin a macro like this muiRenderInfo() just do this 
 mymri = muiRenderInfo(myobj);
and should have a valid MUI_RenderInfo but this macro should only be used between MUIM_Setup/MUIM_Cleanup

A popobject which is connected to a string gadget. The popobject is a listview. So that pressing up/down in the string gadget will scroll the listview updown (even when the listview is hidden) ?
 MUIA_String_AttachedList -- (V4 ) [ISG], Object *

&lt;pre&gt;
MUIA_Popobject_Follow
MUIA_Popobject_Light
MUIA_Popobject_Object
MUIA_Popobject_ObjStrHook
MUIA_Popobject_StrObjHook
MUIA_Popobject_Volatile
MUIA_Popobject_WindowHook
&lt;/pre&gt;

&lt;pre&gt;
MUIA_Poplist_Array
&lt;/pre&gt;

&lt;pre&gt;
MUIM_Popstring_Close
MUIM_Popstring_Open

MUIA_Popstring_Button
MUIA_Popstring_CloseHook
MUIA_Popstring_OpenHook
MUIA_Popstring_String
MUIA_Popstring_Toggle
&lt;/pre&gt;

====Text====

* (N)Floattext already does exactly the same as you did using the list. It splits a long text into separate lines, inserts some spaces to produce an aligned text and displays them.
* The TextEditor class in read-only does more or less the same like Floattext, but with the ability to apply different styles and coloring apart from the standard MUI text engine. Furthermore it allows to let the user edit the text in read-write mode. YAM makes heavy use of it in both modes to show and edit the mails.

Where ony Text() is done. So the size of the area depends on the size of the actual default font. Using  rp(obj)-&gt;Font, but in AskMinMax it seems that when it is first called, the Font is not yet initialized.
You can use _font(obj) to obtain the font. If you also need a rastport then you can setup one temporarily to do your calculations.

&lt;pre&gt;
struct RastPort rp;
InitRastPort(&amp;rp);
SetFont(&amp;rp, _font(obj));
WORD size = TextLength(&amp;rp, &quot;The Text&quot;, 8);
&lt;/pre&gt;

The problem is that text will not stay the right size. They are either spread all over the window, or cramped into one edge, when all I want them to do is to stay on the right and just as big to display 6 chars (as long as possible). MUIA_String_Maxlen seems to have no effect, and just forcing one width doesn't seem right as you never know wether the user may prefer to use a font 50 pixels wide.

Use tag MUIA_FixWidthTxt. For example

 str = StringObject, MUIA_FixWidthTxt, &quot;0000000&quot;, End;

Note 7 characters there: one is for cursor. And use characters which are wide by nature (read MUI_Area.doc and you understand why).

It could also be solved by using   MUIA_Weight, weight. 
Try a combination of &quot;MUIA_Weight, weight&quot; for the string(s) and Put RectangleObjects before/and/or/after the stringobject.

For example, to align a gadget to the right 
&lt;pre&gt;
HGroup,
Child, RectangleObject, MUIA_Weight, 75, End,
Child, StringObject,...,MUIA_Weight, 25, End,
End,
&lt;/pre&gt;

Which means that if you want to change the label and the key shortcut using one attr, you should subclass text, and handle a specific tag for changing the label and the shortcut, parsing yourself the string. Examples of subclassing a mui class can be found in mui dev kit (especially psi contains many subclasses...) and some tools can help you to have a skeleton class using a meta definition of the class you want (mui2c or bcc do such things).

If you create a subgroup something like:
&lt;pre&gt;
mygroup=Group ( MUIA_Group_PageMode,True
Child,SimpleButton(&quot;_Download&quot;),
Child,SimpleButton(&quot;_Resume&quot;),
TAG_DONE)
&lt;/pre&gt;
you get much better result. The &quot;Download&quot; button is now visible, but if you

 set (mygroup, MUIA_Group_ActivePage, 1)

&quot;Download&quot; disappears and &quot;Resume&quot; becomes visible. This is very common trick in MUI applications.

Buttons are simply text objects, which have the following tag:

 MUIA_Text_SetVMax, TRUE

Setting this to FALSE makes a TextObjects y-size unlimited. Defaults to TRUE which means the objects height is fixed. A plain text object cannot be higher than its text, unless you set MUIA_Text_SetVMax to FALSE (default is TRUE). This will give your object unrestricted height, but the text will be displayed vertically centered, unless you set MUIA_Text_VCenter to FALSE.

MUIA_Text_Contents is ISG so:

 SetAttrs(text, MUIA_Text_Contents, &quot;NewContent&quot;, TAG_DONE);

 set (object-&gt;STR_text, MUIA_Text_Contents, myText);

object-&gt;STR_Text ? Looks like MUIBuilder generated code :)

If your 'text-edit-box' is a String object, you'd rather use

 set( object-&gt;STR_text, MUIA_String_Contents, myText );

How to calculate the x/y coords to use with the Move() function so that when using Text() to draw the label it appears centred. There is bunch of macros in mui.h: 
&lt;pre&gt;
_mleft() = starting x coordinate of your drawing area
_mtop() = starting y coord etc.
_mwidth() = width of your drawing area
_mheight() = obvious =)
&lt;/pre&gt;

&lt;pre&gt;
text_height=GetItSomeHow();
text_len=TextLength(&quot;heipparallaa&quot;);

Move(rp, _mleft(obj) + ((_mwidth(obj) - text_len) / 2), _mtop(obj) + ((_mheight(obj) - text_height) / 2) );
&lt;/pre&gt;

(TextObject) If you really need to change the text, then you must set() it again after the modification.

If using a TextObject, then it has the FULL initial size... but if appending extra lines then these are not visible (although a bug causes it to write outside of itself!). The only way to get it to enlarge for the new text is to iconise &amp; then uniconise the MUI window. Also, the text is not word-wrapped.

You must not modify the text as long as it is &quot;in use&quot; by the object. MUI will calculate the required dimensions on basis of the given text and expects it to be constant. If you really need to change the text, then you must set() it again after the modification. This will let MUI do a relayout to display all of the new text.

But this will work to a certain extend only, namely when the complete text's height becomes larger than the window's maximum height. If you need to display larger texts, then the object should be placed into a Scrollgroup object (some of which is MUI4 compatible) like this:

&lt;pre&gt;
ScrollgroupObject,
  MUIA_Scrollgroup_AutoBars, TRUE,
  MUIA_Scrollgroup_Contents, VGroupV,
    Child, TextObject,
      MUIA_Text_Contents, &quot;insert your text here&quot;,
      MUIA_Text_Copy, TRUE,
      End,
    End,
  End,
&lt;/pre&gt;

The attribute MUIA_Scrollgroup_AutoBars will let the scrollgroup show the scrollbars only if they are really needed, i.e. the contents' dimensions are larger than the scrollgroup's dimensions. This attribute is available in MUI4 only like MUIA_Text_Copy, MUI3 will silently ignore it and always show the scrollbars.

Second, the attribute MUIA_Text_Copy instructs Text.mui to keep a copy of your text. This makes it possible to free() the text given to MUIA_Text_Contents after object creation of after set() and it also allows you to modify the text without risking any graphical glitches due to redraw operations while the text is still modified.

However, your text will always be displayed exactly as you specify it. This means that you need to insert line breaks yourself.

If using FloattextObject or TextEditorObject, then no matter the initial contents, the initial size is always three lines of text (which is the minimum space needed by the scrollbar + arrows), but it is at least vertically scrollable. Also, the text is word-wrapped.

Since Floattext.mui inserts line breaks itself you cannot expect a variable height, because the text's height depends on the object's width. You can enforce a certain object height by using something like MUIA_FixHeightTxt, &quot;\n\n\n\n&quot;. This will give you a fixed height of four lines while respecting the object's font.

Floattext.mui is a subclass of List.mui and as such has no restrictions on its dimensions, except you enforce them, i.e. by using MUIA_FixHeightTxt or by subclassing Floattext.mui yourself with a restricting implementation of MUIM_AskMinMax. MUI cannot just resize an object to display the entire initial content, because the content is arbitrary. It may be zero lines, but it may be a million lines. What should the initial size be in this case? Of course you can override MUIM_AskMinMax and return the dimensions which fit you best, but you must be prepared and accept that MUI will adapt the actual dimensions of the object within the limits that your (or the default) MUIM_AskMinMax method returns.

If want to the Floattext object to be resizeable then you must make the label resizeable as well by adding at least one space object above or below the label object like this:

Child, VGroup, Child, Label2(&quot;FloattextObject&quot;), Child, VSpace(0), End,

This will give you a top aligned label. Placing the label after the VSpace(0) object will make it bottom aligned. Using VCenter() will give you a vertically centered label. Choose the solution which fits your needs best.

Have a look at MUI's demo application MUI-Demo. It uses Floattext objects in every single window.

&lt;pre&gt;
MUIA_Text_Contents
MUIA_Text_PreParse
MUIA_Text_SetMax
MUIA_Text_SetMin
MUIA_Text_SetVMax
&lt;/pre&gt;

====Fonts====

try putting SetFont(_font(obj)); in your MUIM_Draw.

In OM_NEW you should set MUIA_Font to one of the predefined values (the MUIV_Font_XXXXXX values) and mui will open the font for you and make it accessible using _font(obj)

In MUIM_Draw, SetFont() to my fonts opened in MUIM_Setup. If SetFont(_font(obj)) otally lose user-settable-fonts. You are not allowed to change settings of _rp( obj ) directly! So make sure you are working on a copy of original rastport and then set fonts, colours or whatever.

&lt;pre&gt;
struct RastPort rp1 = *_rp( obj );
struct RastPort *rp = &amp;rp1;

SetAPen( rp, 0 );
&lt;/pre&gt;

The same applies to normal gadgetclass BOOPSI objects, where before drawing anything you have to ObtainGIRPort(), draw and then ReleaseGIRPort()...

MUICFG_Font_Fixed

====Gadgets====

MUIM_Import/Export and handle the loading and saving yourself. The advantages are that you don't need to create, and call MUIM_Export for the pages that the user doesn't visit, as you'll export the settings (from the created/visited pages) into an already filled dataspace object (loaded during program startup) - which should save both time, memory and complexity. Another advantage is that it makes it very easy to add options such as &quot;Reset to defaults&quot;, &quot;Restore&quot; etc.

Two functions which should make it easier to save/read IFF files into dataspace objects.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
VOID LoadDataspace (STRPTR file, Object *dataspace)
{
BPTR fh;
if(fh = Open(file, MODE_OLDFILE))
{
struct IFFHandle *iff;
if(iff = AllocIFF())
{
InitIFFasDOS(iff);
iff-&gt;iff_Stream = (ULONG)fh;
if(!OpenIFF(iff, IFFF_READ))
{
if(!StopChunk(iff, 'PREF', 'IPRB'))
{
if(!ParseIFF(iff, IFFPARSE_SCAN))
DoMethod(dataspace, MUIM_Dataspace_ReadIFF, iff);
}
CloseIFF(iff);
}
FreeIFF(iff);
}
Close(fh);
}
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
VOID SaveDataspace (STRPTR file, Object *dataspace, Object *app)
{
BOOL retry;
do {

retry = FALSE;
BPTR fh;
if(fh = Open(file, MODE_NEWFILE))
{
struct IFFHandle *iff;
if(iff = AllocIFF())
{
InitIFFasDOS(iff);
iff-&gt;iff_Stream = (ULONG)fh;
if(!OpenIFF(iff, IFFF_WRITE))
{
if(!PushChunk(iff, 'PREF', 'FORM', IFFSIZE_UNKNOWN))
DoMethod(dataspace, MUIM_Dataspace_WriteIFF, iff, 0, 'IPRB');

CloseIFF(iff);
}
FreeIFF(iff);
}
Close(fh);
}
else
{
UBYTE buf[84];
Fault(IoErr(), &quot;DOS&quot;, buf, 84);
retry = MUI_Request(app, NULL, 0L, &quot;Error&quot;, &quot;_Retry|_Cancel&quot;, &quot;\33cError saving:\n%s\n\n%s&quot;, file, buf);
}

} while(retry);
}
&lt;/syntaxhighlight&gt;

One object can't belong to two parents.

How does one insure free pens being allocated? I am running most applications on 16 bit screens. Not sure what is required but I would think there should be some way to have some free. What/how does on &quot;free&quot; pens? 
On True/Hi color screens You may expect to have unlimited number of free pens (or at least 65536/16777216 pens), because you can change the color of every single pixel without affecting the rest. But unfortunately all RastPort rendering functions rely on pen scheme and pen fields in RastPort are only 8-bit wide. It gives you only 256 pens.

Tried to use the MUIA_Bitmap_SourceColors and the MUIA_Bitmap_Precision but all I get is a big black rectangle in place of the discoloured image. Did you set MUIA_Bodychunk_Depth to 5 and MUIA_Bodychunk_Masking to 0
(but check if you save the brush *without* mask plane)? And remember that you should repeat R, G, B values in every byte of a longword, so for example some colour like R=$A5, G=$32, B=$0A, in palette data it looks like $A5A5A5A5,$32323232,$0A0A0A0A. So every palette entry takes 12 bytes.

You need to set the MUIA_Window_UseBottomBorderScroller (or whatever side you want) on the window. Then create a Prop Object and set the MUIA_Prop_UseWinBorder to the corresponding side(s) that you did in the window. Then just set up a notification on the prop object to listen for changes in MUIA_Prop_First. 
When you place the one on the right and open the window, MUI opens the window the smallest possible and doesn't draw any of the other objects that should be in the window.

====dtpic Datatypes====

If you would like to get a pointer to the bitmap that holds the data of the picture or a way to copy it to your own bitmap but all Zune attributes did not work.

In that case you will want to use datatypes.library directly. Dtpic AFAIK is just for easily including datatype images into MUI/Zune GUIs (as button imagery, in listviews and so on...).

If AROS supports the superbitmap window refresh method then you can. For a non-borderless window you will probably want to make it gimmezerozero (gzz) as well so that the borders and window contents have separate layers (uses slightly more memory). 
That being said just blitting the bitmap into the window is probably a simpler and more portable solution.

How to &quot;convert&quot; e.g. a png image to a bitmap structure (datatypes?). DTpic.mui is your friend. 
Using picture.datatype and then blitting bitmap to object rastport in MUIM_Draw.

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
Child, image_button = MakeButton(&quot;PROGDIR:Imagesg/test_but.png&quot;, 't',&quot;\33uT\33nest Button&quot;),

static APTR MakeButton(UBYTE *Image, UBYTE Key, UBYTE *Help)
{
return(MUI_NewObject(&quot;Dtpic.mui&quot;,
MUIA_Dtpic_Name,Image,
MUIA_InputMode, MUIV_InputMode_RelVerify,
MUIA_ControlChar, Key,
MUIA_Background, MUII_ButtonBack,
MUIA_ShortHelp, Help,
PropFrame,TRUE,
ImageButtonFrame,
TAG_DONE));
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
if(app)
{
   struct BitMapHeader *bmhd;
   struct BitMap *bitmap;
   Object *datatype_obj;       /* pointer to the Datatype Object          */
   Object *bitmap_obj;         /* a mui BitmapObject                      */
   Object *list_obj;           /* the one that should be used in the list */

   if(datatype_obj = NewDTObject(&quot;Images/www.iff&quot;,
      DTA_SourceType , DTST_FILE,
      DTA_GroupID    , GID_PICTURE,
      TAG_DONE))
   {
      if(DoMethod(datatype_obj, DTM_PROCLAYOUT, NULL, 1))
      {
         get(datatype_obj, PDTA_BitMapHeader, &amp;bmhd);
         GetDTAttrs(datatype_obj, PDTA_DestBitMap, &amp;bitmap, TAG_DONE);
         if(!bitmap)
            GetDTAttrs(datatype_obj, PDTA_BitMap, &amp;bitmap, TAG_DONE);

         if(bitmap_obj = BitmapObject,
            MUIA_Bitmap_SourceColors  , xget(datatype_obj, PDTA_CRegs),
            MUIA_Bitmap_Width         , bmhd-&gt;bmh_Width,
            MUIA_Bitmap_Height        , bmhd-&gt;bmh_Height,
            MUIA_FixWidth             , bmhd-&gt;bmh_Width,
            MUIA_FixHeight            , bmhd-&gt;bmh_Height,
            MUIA_Bitmap_Transparent   , 0,
            MUIA_Bitmap_Bitmap        , bitmap,
            End)
         {
            list_obj = (Object *)DoMethod(LV_ButtonBank, MUIM_List_CreateImage, bitmap_obj, NULL);
         }
      }
   }
}
&lt;/syntaxhighlight&gt;

in MUI4.0

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
Child, zoneimage = (Object *) MUI_NewObject(MUIC_Dtpic,
				MUIA_Dtpic_Name, &quot;PROGDIR:resource/zone_local.png&quot;,
				TAG_DONE),
					
DEFSMETHOD(OWBWindow_UpdateZone)
{
	GETDATA;

	char *image;

	switch(msg-&gt;zone)
	{
		default:
		case MV_OWBBrowser_Zone_Local:
			image = &quot;PROGDIR:resource/zone_local.png&quot;;
			break;
		case MV_OWBBrowser_Zone_Internet:
			image = &quot;PROGDIR:resource/zone_internet.png&quot;;
			break;
	}

	set(data-&gt;zoneimage, MUIA_Dtpic_Name, image);

	return 0;
}
&lt;/syntaxhighlight&gt;

i.e. by default we set zone_local image, and then by notification calls updatezone when the attribute is set. And it should changes (image i mean), but did't not. I see that i am in the Zone_Internet (by printfs), but image not sets. Problems with 3.9

===Removal===

&lt;pre&gt;
void ExitClasses(void)
{
    if (NewList)
	{
        MUI_DeleteCustomClass(NewList);
		NewList = NULL;
	}
}

BOOL InitClasses(void)
{
    NewList = MUI_CreateCustomClass(NULL,MUIC_NList ,NULL,sizeof(struct NewList_Data),&amp;NewList_Dispatcher);

	if (NewList) return(TRUE);
	else        return FALSE;
}
&lt;/pre&gt;

Another thing, which your compiler should notice immediately, is that MyCustomClass is struct IClass * and assigning Object * to it is very, very wrong, and should effect crash at MUI_DeleteCustomClass()...

&lt;pre&gt;
#define MyCustomObject NewObject(MyCustomClass-&gt;mcc_Class,NULL,

Object *mycustomobject;
mycustomobject = MyCustomObject, End;
if( mycustomobject != NULL )
{
app = ApplicationObject, [... ]
End;
if( app != NULL )
{
[...]
MUI_DisposeObject( app );
}
MUI_DisposeObject( mycustomobject );
}
&lt;/pre&gt;

Or preferably you should subclass Application.mui class and do your non-visible code there... That's the best way to handle it IMHO... This way main program code will be almost untouched and going back to using standard Application.mui within seconds, just rename MyApplicationObject to ApplicationObject (always define such macros instead of writing NewObject() directly!)

Objects are removed using OM_REMMEMBER method (must use parent object of course)

==References==

http://alfie.altervista.org/rxmui/rxmuidoc/classes.html

http://amiga.sourceforge.net/amigadevhelp/phpwebdev.php

When one of the qualifier (shift, ctrl, alt) keys is clicked then the opposite key should get the same state. I tried in the callback function: 
&lt;pre&gt;
BOOL shift = XGET(data-&gt;keybutton[96], MUIA_Pressed) |
XGET(data-&gt;keybutton[97], MUIA_Pressed);

NNSET(data-&gt;keybutton[96], MUIA_Pressed, shift);
NNSET(data-&gt;keybutton[97], MUIA_Pressed, shift);
&lt;/pre&gt;
Pressing the qualifier keys on the keyboard should act as if the button was clicked. I've therefore added an event handler method. It works so far as the visual state of the buttons is changed. Problem is that SET(keyobj, MUIA_Pressed, state) in that event method doesn't trigger the callback hook.

Try MUIA_Selected, instead of MUIA_Pressed (which is really just a thing to be used for notification, not a real attribute). You'll also have to change code logic, because once the two SHIFT buttons are selected, it won't be possible to unselected them (&quot;shift&quot; var would always be TRUE).

Networking with a non-blocking recv(), start with one task and make all my interfaces push-based. 
That is, no-one will call recv() but instead be called with the data received from a socket (when it arrives). 
So in your main-loop you wait for both sockets and user events and distribute these to the proper receiver (where the latter would be done by MUI). 
The reason for this approach is to simplify code (eliminate the need to lock resources/data with semaphores etc), and also because found  out that spawning tasks had a noticeable overhead (but you could keep one network manager running all the time to get by this), not to mention that if you receive data on 8 sockets (each having its own process) then your program will be represented with 9 total tasks and thus if another program needs cpu-time it'll only get 1/10th of the time, where your program will get 9/10th, unless you fiddle with the priority of your tasks but then other problems appear. 
If the data you receive needs to be parsed in some way you may at first find it irritating to have to write your parser as a state-machine, but these also have advantages IMO. For example it makes it very easy to add filters to the data stream or create virtual data on the fly...

Basically you need a socket operating in the non-blocking &amp; asynchronous mode. This prevents GUI being locked while accessing network. Another step is allocate signal bit for bsdsocket and use GetSocketEvent() to find out network actions without braindead select() or WaitSelect() functions. So that whenever network signal is set you call GetSocketEvent() in loop. This GetSocketEvent() returns socket descriptor ID and possible events occurred. 
Avoid GetSocketEvent() and its minion like it was the bubonic plague!!!!!!!! As it turned out, it only
works under Miami. Even though AmiTCP copied the API from M$, it never worked correctly. Use WaitSelect() instead of Wait() in your MUI main loop. See STRICQ 2 src. 
How do you receive data from sockets? Is there a way to associate a signal to a socket? 
You can associate a signal with a socket by using SocketBaseTags(). Use WaitSelect() in the STRICQ v2 socket code. But in v1, used a signal.

You can encapsulate internet client in MUI application subclass, create some useful methods and attributes like
MUIM_NetApplication_Connect/Disconnect/Send/Receive, and then when user press Connect/Disconnect button, call these methods in notification or callback function (so if NetApplication connected you will disable Connect, and
enable Disconnect etc. gadgets). And so on. Never connect to the internet immediately in OM_NEW, that would be stupid as well as creating needed subprocess in there (which from other side might be not good idea). It can wait then as long as application sends the connect signal or message and then do it's network job, until it receives MUIM_NetApplication_Disconnect method.. How to... merge bsdsocket.library and muimaster.library in single, nicely OOP, application.

==Examples==

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/*
    Copyright © 2002, The AROS Development Team.
    All rights reserved.

    $Id: aircos_server_gui.c 30794 2009-03-08 02:19:07Z neil $
*/

//#include    &lt;exec/types.h&gt;
#include    &lt;stdlib.h&gt;
#include    &lt;stdio.h&gt;
#include    &lt;string.h&gt;

#include    &lt;proto/alib.h&gt;
#include    &lt;proto/exec.h&gt;
#include    &lt;proto/dos.h&gt;
#include    &lt;proto/intuition.h&gt;
#include    &lt;proto/muimaster.h&gt;
#include    &lt;proto/utility.h&gt;

#include    &lt;dos/dos.h&gt;
#include    &lt;intuition/gadgetclass.h&gt;
#include    &lt;intuition/icclass.h&gt;
#include    &lt;clib/alib_protos.h&gt;

#include &lt;libraries/mui.h&gt;
#include &lt;mui/NListtree_mcc.h&gt;
#include &lt;mui/NListview_mcc.h&gt;
#include &lt;mui/NList_mcc.h&gt;

#include &quot;aircos_global.h&quot;
#include &quot;locale.h&quot;

extern struct AiRcOS_internal *AiRcOS_Base;
struct List                   aircos_Prefs_ServerNetworks;
struct List                   aircos_Prefs_Servers;
struct aircos_servernode      *aircos_Prefs_ServerActive;
struct Hook                   aircos_serversave_hook;
struct Hook                   aircos_networklistupdate_hook;
struct Hook                   aircos_serverlistupdate_hook;
struct Hook                   aircos_chooseserver_hook;

BOOL                          aircos_Prefs_ServersLoaded = FALSE;

Object	                     *input_server_address = NULL;
Object	                     *input_server_port =  NULL;
Object	                     *input_server_description =  NULL;
Object	                     *input_server_network =  NULL;
Object	                     *input_server_pass =  NULL;

Object                        *select_dropboxgrp_network = NULL;
Object                        *select_dropbox_network = NULL;
Object                        *select_dropboxgrp_server = NULL;
Object                        *select_dropbox_server = NULL;

STRPTR	                     network_list_empty[2] =
{
  {&quot;&lt;List Empty&gt;&quot;},
  NULL
};
STRPTR	                     server_list_empty[2] =
{
  {&quot;&lt;List Empty&gt;&quot;},
  NULL
};
Object	                     *servermodWin;
STRPTR	                     *network_list;
STRPTR	                     *server_list;

//network_list_empty[0] = &quot;&lt;List Empty&gt;&quot;;		//MSG(MSG_LIST_EMPTY);
//network_list_empty[1] = NULL;

//server_list_empty[0] = &quot;&lt;List Empty&gt;&quot;;		//MSG(MSG_LIST_EMPTY);
//server_list_empty[1] = NULL;

#define AIRCOS_DEF_SERVERSFILE &quot;servers.dat&quot;

aircosApp_LoadServers()
{
  aircos_Prefs_ServersLoaded = TRUE;
}

struct aircos_networknode *aircosApp_FindServerNetworkNode(char * findNetwork)
{
  struct aircos_networknode *current_Node = NULL;
  ForeachNode(&amp;aircos_Prefs_ServerNetworks, current_Node)
  {
D(bug(&quot;[AiRcOS](FindServerNetworkNode) Checking against record for '%s'\n&quot;, current_Node-&gt;ann_Network));
      if (strcasecmp(current_Node-&gt;ann_Network, findNetwork)==0) return current_Node;
  }
  return NULL;
}

struct aircos_servernode  *aircosApp_FindServerNode(char * findServer)
{
struct aircos_servernode  *current_Node = NULL;
  ForeachNode(&amp;aircos_Prefs_Servers, current_Node)
  {
D(bug(&quot;[AiRcOS](FindServerNode) Checking against record for '%s'\n&quot;, current_Node-&gt;asn_Server));
      if (strcasecmp(current_Node-&gt;asn_Server, findServer)==0) return current_Node;
  }
  return NULL;
}

AROS_UFH3(void, chooseserver_func,
   AROS_UFHA(struct Hook *, unused_hook, A0),
   AROS_UFHA(APTR, obj, A2),
   AROS_UFHA(struct IRC_Channel_Priv  *, hook_channel_arg, A1 ))
{
   AROS_USERFUNC_INIT
D(bug(&quot;[AiRcOS] chooseserver_func()\n&quot;));
  ULONG                      currentPrefsServerID;
  get(select_dropbox_server, MUIA_Cycle_Active, &amp;currentPrefsServerID);

  struct aircos_servernode *currentPrefsServer = NULL;
  if (!(currentPrefsServer = aircosApp_FindServerNode(server_list[currentPrefsServerID])))
  {
D(bug(&quot;[AiRcOS] chooseserver_func: Couldnt find Server Node!\n&quot;));
    return;
  }

  aircos_Prefs_ServerActive = currentPrefsServer;

  AROS_USERFUNC_EXIT
};

AROS_UFH3(void, updatenetworklist_func,
   AROS_UFHA(struct Hook *, unused_hook, A0),
   AROS_UFHA(APTR, obj, A2),
   AROS_UFHA(struct IRC_Channel_Priv  *, hook_channel_arg, A1 ))
{
   AROS_USERFUNC_INIT
D(bug(&quot;[AiRcOS] updatenetworklist_func()\n&quot;));
  struct aircos_networknode *currentPrefsNetwork = NULL;
  ULONG                      prefsNetworkCount = 0;
  ULONG                      setprefsNetworkActive = 0;
  Object                     *new_dropbox_network = NULL;
  
  ForeachNode(&amp;aircos_Prefs_ServerNetworks, currentPrefsNetwork)
  {
      prefsNetworkCount++;
      if (aircos_Prefs_ServerActive)
        if (strcasecmp(currentPrefsNetwork-&gt;ann_Network, aircos_Prefs_ServerActive-&gt;asn_Network-&gt;ann_Network)==0)
        {
          setprefsNetworkActive = prefsNetworkCount -1;
        }
  }

D(bug(&quot;[AiRcOS] updatenetworklist_func: %d network nodes\n&quot;, prefsNetworkCount));
  
  if (prefsNetworkCount &gt; 0)
  {
    if (network_list != network_list_empty) {
      FreeVec(network_list);
    }
    
    if ((network_list = AllocVec(sizeof(IPTR) * prefsNetworkCount+1, MEMF_CLEAR|MEMF_PUBLIC)))
    {
      int loop_count = 0;

      ForeachNode(&amp;aircos_Prefs_ServerNetworks, currentPrefsNetwork)
      {
        network_list[loop_count] = currentPrefsNetwork-&gt;ann_Network;
        loop_count++;
      }
    }
    else
    {
D(bug(&quot;[AiRcOS] updatenetworklist_func: ERROR - couldnt allocate memory for network name pointer table\n&quot;));
      network_list = network_list_empty;
    }
  } else if (network_list != network_list_empty) {
    FreeVec(network_list);
    network_list = network_list_empty; 
  }

  if (!(new_dropbox_network = MUI_MakeObject(MUIO_Cycle, NULL, network_list)))
  {
D(bug(&quot;[AiRcOS] updatenetworklist_func: Failed to create Network dropdown\n&quot;));
    return NULL;
  }

  if (DoMethod(select_dropboxgrp_network, MUIM_Group_InitChange))
  {
    DoMethod(select_dropboxgrp_network, OM_REMMEMBER, select_dropbox_network);
    DoMethod(select_dropboxgrp_network, OM_ADDMEMBER, new_dropbox_network);
    DoMethod(select_dropboxgrp_network, MUIM_Group_ExitChange);
    select_dropbox_network = new_dropbox_network;
  }

  DoMethod(select_dropbox_network, MUIM_NoNotifySet, MUIA_Cycle_Active, setprefsNetworkActive);
  DoMethod
  (
      select_dropbox_network, MUIM_Notify, MUIA_Cycle_Active, MUIV_EveryTime,
      (IPTR) AiRcOS_Base-&gt;aircos_app, 3, MUIM_CallHook, &amp;aircos_serverlistupdate_hook, NULL
  );
        
  AROS_USERFUNC_EXIT
};

AROS_UFH3(void, updateserverlist_func,
   AROS_UFHA(struct Hook *, unused_hook, A0),
   AROS_UFHA(APTR, obj, A2),
   AROS_UFHA(struct IRC_Channel_Priv  *, hook_channel_arg, A1 ))
{
   AROS_USERFUNC_INIT
D(bug(&quot;[AiRcOS] updateserverlist_func()\n&quot;));
  struct aircos_servernode   *currentPrefsServer = NULL;
  ULONG                      prefsNetworkServerCount = 0;
  ULONG                      setprefsServerActive = 0;
  Object                     *new_dropbox_server = NULL;

  ULONG                      currentPrefsNetworkID;
  get(select_dropbox_network, MUIA_Cycle_Active, &amp;currentPrefsNetworkID);

  struct aircos_networknode *currentPrefsNetwork = NULL;
  if (!(currentPrefsNetwork = aircosApp_FindServerNetworkNode(network_list[currentPrefsNetworkID])))
  {
D(bug(&quot;[AiRcOS] updateserverlist_func: Couldnt find Network Node!\n&quot;));
    return;
  }

  ForeachNode(&amp;aircos_Prefs_Servers, currentPrefsServer)
  {
      if (strcasecmp(currentPrefsServer-&gt;asn_Network-&gt;ann_Network, currentPrefsNetwork-&gt;ann_Network)==0)
      {
        prefsNetworkServerCount++;
        if (aircos_Prefs_ServerActive)
          if (strcasecmp(currentPrefsServer-&gt;asn_Server, aircos_Prefs_ServerActive-&gt;asn_Server)==0)
          {
            setprefsServerActive = prefsNetworkServerCount -1;
          }
      }
  }

D(bug(&quot;[AiRcOS] updateserverlist_func: %d server nodes for network '%s'\n&quot;, prefsNetworkServerCount, currentPrefsNetwork-&gt;ann_Network));
  
  if (prefsNetworkServerCount &gt; 0)
  {
    if (server_list != server_list_empty) {
      FreeVec(server_list);
    }
    
    if ((server_list = AllocVec(sizeof(IPTR) * prefsNetworkServerCount+1, MEMF_CLEAR|MEMF_PUBLIC)))
    {
      int loop_count = 0;

      ForeachNode(&amp;aircos_Prefs_Servers, currentPrefsServer)
      {
        if (strcasecmp(currentPrefsServer-&gt;asn_Network-&gt;ann_Network, currentPrefsNetwork-&gt;ann_Network)==0)
        {
          server_list[loop_count] = currentPrefsServer-&gt;asn_Server;
          loop_count++;
        }
      }
    }
    else
    {
D(bug(&quot;[AiRcOS] updateserverlist_func: ERROR - couldnt allocate memory for server name pointer table\n&quot;));
      server_list = server_list_empty;
    }
  } else if (server_list != server_list_empty) {
    FreeVec(server_list);
    server_list = server_list_empty; 
  }

  if (!(new_dropbox_server = MUI_MakeObject(MUIO_Cycle, NULL, server_list)))
  {
D(bug(&quot;[AiRcOS] updateserverlist_func: Failed to create Server dropdown\n&quot;));
    return NULL;
  }

  if (DoMethod(select_dropboxgrp_server, MUIM_Group_InitChange))
  {
    DoMethod(select_dropboxgrp_server, OM_REMMEMBER, select_dropbox_server);
    DoMethod(select_dropboxgrp_server, OM_ADDMEMBER, new_dropbox_server);
    DoMethod(select_dropboxgrp_server, MUIM_Group_ExitChange);
    select_dropbox_server = new_dropbox_server;
  }

  DoMethod(select_dropbox_server, MUIM_NoNotifySet, MUIA_Cycle_Active, setprefsServerActive);

  AROS_USERFUNC_EXIT
};

AROS_UFH3(void, serversave_func,
   AROS_UFHA(struct Hook *, unused_hook, A0),
   AROS_UFHA(APTR, obj, A2),
   AROS_UFHA(struct IRC_Channel_Priv  *, hook_channel_arg, A1 ))
{
   AROS_USERFUNC_INIT
D(bug(&quot;[AiRcOS] serversave_func()\n&quot;));

  struct aircos_networknode *newsaveNetwork = NULL;
  char                      *newsaveNetwork_name;
  BOOL                      newsaveNetwork_update = FALSE;

  struct aircos_servernode  *newsaveServer = NULL;
  char                      *newsaveServer_name;
  BOOL                      newsaveServer_update = FALSE;

   get( input_server_network, MUIA_String_Contents, &amp;newsaveNetwork_name);
   get( input_server_address, MUIA_String_Contents, &amp;newsaveServer_name);

  if (!(newsaveNetwork = aircosApp_FindServerNetworkNode(newsaveNetwork_name)))
  {
D(bug(&quot;[AiRcOS](serversave_func) created new network node for '%s'\n&quot;, newsaveNetwork_name));
     newsaveNetwork = AllocVec(sizeof(struct aircos_networknode), MEMF_CLEAR|MEMF_PUBLIC);
     newsaveNetwork-&gt;ann_Network = AllocVec(strlen(newsaveNetwork_name)+1, MEMF_CLEAR|MEMF_PUBLIC);
     CopyMem(newsaveNetwork_name, newsaveNetwork-&gt;ann_Network, strlen(newsaveNetwork_name)+1);

     AddTail((struct List *)&amp;aircos_Prefs_ServerNetworks, (struct Node *)&amp;newsaveNetwork-&gt;ann_Node);
     newsaveNetwork_update = TRUE;
  }
  newsaveNetwork-&gt;ann_ServerCount += 1;
D(bug(&quot;[AiRcOS](serversave_func) %s Network node server count = %d\n&quot;, newsaveNetwork-&gt;ann_Network, newsaveNetwork-&gt;ann_ServerCount));

  if (!(newsaveServer = aircosApp_FindServerNode(newsaveServer_name)))
  {
D(bug(&quot;[AiRcOS](serversave_func) created new server node for '%s'\n&quot;, newsaveServer_name));
     newsaveServer = AllocVec(sizeof(struct aircos_servernode), MEMF_CLEAR|MEMF_PUBLIC);
     newsaveServer-&gt;asn_Server = AllocVec(strlen(newsaveServer_name)+1, MEMF_CLEAR|MEMF_PUBLIC);
     CopyMem(newsaveServer_name, newsaveServer-&gt;asn_Server, strlen(newsaveServer_name)+1);
     newsaveServer-&gt;asn_Network = newsaveNetwork;
     get( input_server_port, MUIA_String_Integer, &amp;newsaveServer-&gt;asn_Port);

#warning &quot;TODO: we need to store the password also here ..&quot;

     AddTail((struct List *)&amp;aircos_Prefs_Servers, (struct Node *)&amp;newsaveServer-&gt;asn_Node);
     newsaveServer_update = TRUE;
  }
  else
  {
D(bug(&quot;[AiRcOS](serversave_func) node already exists for server '%s'\n&quot;, newsaveServer_name));
  }

  aircos_Prefs_ServerActive = newsaveServer;

  set( servermodWin, MUIA_Window_Open, FALSE);

  if (newsaveNetwork_update) CallHookPkt(&amp;aircos_networklistupdate_hook, obj, hook_channel_arg);
  if (newsaveServer_update) CallHookPkt(&amp;aircos_serverlistupdate_hook, obj, hook_channel_arg);

  AROS_USERFUNC_EXIT
};

Object	*aircos_showServerConnect()
{
D(bug(&quot;[AiRcOS] showServerConnect()\n&quot;));
  if (aircos_Prefs_ServersLoaded)
  {
D(bug(&quot;[AiRcOS](showServerConnect) Server windows already configured!\n&quot;));
    return NULL;
  }

   Object   *tmp_connectWin = NULL;

  NewList((struct List *)&amp;aircos_Prefs_ServerNetworks);
  NewList((struct List *)&amp;aircos_Prefs_Servers);

	Object	*butt_addServer = NULL;
	Object	*butt_editServer = NULL;
	Object	*butt_delServer = NULL;
	Object	*butt_serverConnect = NULL;
	Object   *butt_serverSave = NULL;

   network_list = network_list_empty;
   server_list = server_list_empty;

	if (!(select_dropbox_network = MUI_MakeObject(MUIO_Cycle, NULL, network_list)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create Network dropdown\n&quot;));
      return NULL;
	}
	
	if (!(select_dropbox_server = MUI_MakeObject(MUIO_Cycle, NULL, server_list)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create Server dropdown\n&quot;));
      return NULL;
	}

   if (!(butt_addServer = SimpleButton(&quot;Add&quot;)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create 'ADD' button\n&quot;));
      return NULL;
	}
	
   if (!(butt_editServer = SimpleButton(&quot;Edit&quot;)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create 'EDIT' button\n&quot;));
      return NULL;
	}
	
   if (!(butt_delServer = SimpleButton(&quot;Del&quot;)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create 'DEL' button\n&quot;));
      return NULL;
	}

   if (!(butt_serverConnect = SimpleButton(&quot;Connect!&quot;)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create 'CONNECT' button\n&quot;));
      return NULL;
	}

   if (!(butt_serverSave = SimpleButton(&quot;Save!&quot;)))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create 'SAVE' button\n&quot;));
      return NULL;
	}

   select_dropboxgrp_network = VGroup,
                                 Child, (IPTR) select_dropbox_network,
                               End;

   select_dropboxgrp_server = VGroup,
                                Child, (IPTR) select_dropbox_server,
                              End;

	tmp_connectWin = WindowObject,
            MUIA_Window_Title, (IPTR) &quot;Connect to Server..&quot;,
            MUIA_Window_Activate, TRUE,
            MUIA_Window_Width,200,
            MUIA_Window_Height,200,
     
            WindowContents, (IPTR) VGroup,
                Child, (IPTR) HGroup,
                  GroupFrame,
					   Child, (IPTR) VGroup,
						  Child, (IPTR) LLabel(&quot;IRC Network&quot;),
						  Child, (IPTR) HGroup,
						    Child, (IPTR) HSpace(0),
						    Child, (IPTR) select_dropboxgrp_network,
						    Child, (IPTR) HSpace(0),
						  End,
					   End,
					   Child, (IPTR) HVSpace,
                End,
                Child, (IPTR) HGroup,
                  GroupFrame,
					   Child, (IPTR) VGroup,
						  Child, (IPTR) LLabel(&quot;IRC Server&quot;),
						  Child, (IPTR) HGroup,
						    Child, (IPTR) HVSpace,
						    Child, (IPTR) select_dropboxgrp_server,
						    Child, (IPTR) HVSpace,
						  End,
					   End,
  					   Child, (IPTR) HVSpace,
                End,
                Child, (IPTR) HGroup,
					   Child, (IPTR) HVSpace,
					   Child, (IPTR) butt_addServer,
					   Child, (IPTR) butt_editServer,
					   Child, (IPTR) butt_delServer,
                End,
                Child, (IPTR) butt_serverConnect,
            End,
        End;

	servermodWin = WindowObject,
        
            MUIA_Window_Title, (IPTR) &quot;Edit Server..&quot;,
            MUIA_Window_Activate, TRUE,
            MUIA_Window_Width,350,
            MUIA_Window_Height,400,
     
            WindowContents, (IPTR) VGroup,
               Child, (IPTR) VGroup,
                 GroupFrame,
                 Child, (IPTR) HGroup,
					    Child, (IPTR) LLabel(&quot;IRC Server Address&quot;),
					    Child, (IPTR) (input_server_address = StringObject,
										StringFrame,
                              MUIA_CycleChain, TRUE,
										MUIA_String_Format, MUIV_String_Format_Right,
                   End ),
                 End,
                 Child, (IPTR) HGroup,
					    Child, (IPTR) LLabel(&quot;Port&quot;),
					    Child, (IPTR) (input_server_port = StringObject,
										StringFrame,
                              MUIA_CycleChain, TRUE,
										MUIA_String_Format, MUIV_String_Format_Right,
										MUIA_String_Accept, &quot;0123456789&quot;,
										MUIA_String_Integer, 0,
					    End),
                 End,
                 Child, (IPTR) HGroup,
					    Child, (IPTR) LLabel(&quot;Server Description&quot;),
					    Child, (IPTR) (input_server_description = StringObject,
										StringFrame,
                              MUIA_CycleChain, TRUE,
										MUIA_String_Format, MUIV_String_Format_Right,
					    End),
                 End,
                 Child, (IPTR) HGroup,
					    Child, (IPTR) LLabel(&quot;IRC Network&quot;),
					    Child, (IPTR) (input_server_network = StringObject,
										StringFrame,
                              MUIA_CycleChain, TRUE,
										MUIA_String_Format, MUIV_String_Format_Right,
					    End),
                 End,
               End,
               Child, (IPTR) VGroup,
                 GroupFrame,
				     Child, (IPTR) LLabel(&quot;Enter server password here if applicable.&quot;),
                 Child, (IPTR) HGroup,
					    Child, (IPTR) LLabel(&quot;Password&quot;),
					    Child, (IPTR) (input_server_pass = StringObject,
										StringFrame,
                              MUIA_CycleChain, TRUE,
										MUIA_String_Format, MUIV_String_Format_Right,
					    End),
                 End,
               End,
               Child, (IPTR) butt_serverSave,
            End,
        End;

	if ((tmp_connectWin)&amp;&amp;(servermodWin))
	{
D(bug(&quot;[AiRcOS](showServerConnect) Created GUI objects\n&quot;));
      DoMethod
        (
            AiRcOS_Base-&gt;aircos_app, OM_ADDMEMBER,
            (IPTR) tmp_connectWin
        );

      DoMethod
        (
            AiRcOS_Base-&gt;aircos_app, OM_ADDMEMBER,
            (IPTR) servermodWin
        );

        DoMethod
        (
            tmp_connectWin, MUIM_Notify, MUIA_Window_Open, TRUE,
            (IPTR) AiRcOS_Base-&gt;aircos_quickconnectwin, 3, MUIM_Set, MUIA_Window_Open, FALSE
        );

        DoMethod
        (
            AiRcOS_Base-&gt;aircos_quickconnectwin, MUIM_Notify, MUIA_Window_Open, TRUE,
            (IPTR) tmp_connectWin, 3, MUIM_Set, MUIA_Window_Open, FALSE
        );

        DoMethod
        (
            tmp_connectWin, MUIM_Notify, MUIA_Window_Open, FALSE,
            (IPTR) servermodWin, 3, MUIM_Set, MUIA_Window_Open, FALSE
        );

      DoMethod
        (
            butt_addServer, MUIM_Notify, MUIA_Selected, FALSE,
            (IPTR) servermodWin, 3, MUIM_Set, MUIA_Window_Open, TRUE
        );

      DoMethod
        (
            butt_editServer, MUIM_Notify, MUIA_Selected, FALSE,
            (IPTR) servermodWin, 3, MUIM_Set, MUIA_Window_Open, TRUE
        );

//      DoMethod
//        (
//            butt_delServer, MUIM_Notify, MUIA_Selected, FALSE,
//            (IPTR) servermodWin, 3, MUIM_Set, MUIA_ShowMe, FALSE
//        );

        DoMethod
        (
            tmp_connectWin, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
            (IPTR) tmp_connectWin, 3, MUIM_Set, MUIA_Window_Open, FALSE
        );
        
        DoMethod
        (
            servermodWin, MUIM_Notify, MUIA_Window_CloseRequest, TRUE,
            (IPTR) servermodWin, 3, MUIM_Set, MUIA_Window_Open, FALSE
        );

        DoMethod
        (
            butt_serverConnect, MUIM_Notify, MUIA_Pressed, FALSE,
                (IPTR) AiRcOS_Base-&gt;aircos_app, 3, MUIM_CallHook, &amp;AiRcOS_Base-&gt;aircos_connect_hook, NULL
        );

D(bug(&quot;[AiRcOS](showServerConnect) prepare list update hooks\n&quot;));
    
       aircos_serversave_hook.h_MinNode.mln_Succ = NULL;
       aircos_serversave_hook.h_MinNode.mln_Pred = NULL;
       aircos_serversave_hook.h_Entry = HookEntry;
       aircos_serversave_hook.h_SubEntry = (void *)serversave_func;

       aircos_networklistupdate_hook.h_MinNode.mln_Succ = NULL;
       aircos_networklistupdate_hook.h_MinNode.mln_Pred = NULL;
       aircos_networklistupdate_hook.h_Entry = HookEntry;
       aircos_networklistupdate_hook.h_SubEntry = (void *)updatenetworklist_func;
       
       aircos_serverlistupdate_hook.h_MinNode.mln_Succ = NULL;
       aircos_serverlistupdate_hook.h_MinNode.mln_Pred = NULL;
       aircos_serverlistupdate_hook.h_Entry = HookEntry;
       aircos_serverlistupdate_hook.h_SubEntry = (void *)updateserverlist_func;

       aircos_chooseserver_hook.h_MinNode.mln_Succ = NULL;
       aircos_chooseserver_hook.h_MinNode.mln_Pred = NULL;
       aircos_chooseserver_hook.h_Entry = HookEntry;
       aircos_chooseserver_hook.h_SubEntry = (void *)chooseserver_func;

        DoMethod
        (
            butt_serverSave, MUIM_Notify, MUIA_Pressed, FALSE,
                (IPTR) AiRcOS_Base-&gt;aircos_app, 3, MUIM_CallHook, &amp;aircos_serversave_hook, NULL
        );

        DoMethod
        (
            select_dropbox_network, MUIM_Notify, MUIA_Cycle_Active, MUIV_EveryTime,
                (IPTR) AiRcOS_Base-&gt;aircos_app, 3, MUIM_CallHook, &amp;aircos_serverlistupdate_hook, NULL
        );

        DoMethod
        (
            select_dropbox_server, MUIM_Notify, MUIA_Cycle_Active, MUIV_EveryTime,
                (IPTR) AiRcOS_Base-&gt;aircos_app, 3, MUIM_CallHook, &amp;aircos_chooseserver_hook, NULL
        );

D(bug(&quot;[AiRcOS](showServerConnect) Configured NOTIFICATIONS\n&quot;));

       set(tmp_connectWin, MUIA_Window_Open, TRUE);
       D(bug(&quot;[AiRcOS](showServerConnect) Window opened ..\n&quot;));
     }
     else
     {
      if (!(servermodWin))
      {
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create server edit window..\n&quot;));
      }
      else MUI_DisposeObject(servermodWin);
      
      if (!(tmp_connectWin))
      {
D(bug(&quot;[AiRcOS](showServerConnect) Failed to create server selection window..\n&quot;));      
      }
      else MUI_DisposeObject(tmp_connectWin);
     }

	return tmp_connectWin;
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/*
    Copyright © 2002, The AROS Development Team.
    All rights reserved.

    $Id: mini2.c 30792 2009-03-07 22:40:04Z neil $
*/

#include &lt;exec/types.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;stdio.h&gt;
#include &lt;string.h&gt;

#include &lt;dos/dos.h&gt;
#include &lt;intuition/gadgetclass.h&gt;
#include &lt;intuition/icclass.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

/* the following should go in a single include file which then only
** constits of the public constants and members. Actually this is easiey
*/

#include &lt;libraries/mui.h&gt;

#define DEBUG 1
#include &lt;aros/debug.h&gt;

Object *app;

int main(void)
{
    Object *wnd;
    static char *radio_entries2[] = {&quot;Paris&quot;,&quot;London&quot;,NULL};

    app = ApplicationObject,
   	SubWindow, wnd = WindowObject,
    	    WindowContents, VGroup,
	Child, HGroup,
	    MUIA_InputMode, MUIV_InputMode_Immediate,
/*              MUIA_ShowSelState, FALSE, */
	    Child, ImageObject,
                MUIA_ShowSelState, FALSE,
	        MUIA_Image_FontMatch, TRUE,
	        MUIA_Image_Spec, MUII_RadioButton,
	        MUIA_Frame, MUIV_Frame_None,
   	        End,
	    Child, TextObject,
                MUIA_ShowSelState, FALSE,
	        MUIA_Text_Contents, &quot;London&quot;,
	        MUIA_Frame, MUIV_Frame_None,
	        MUIA_Text_PreParse, &quot;\33l&quot;,
	        End,
	End,
		End,
	    End,
	End;

    if (app)
    {
	ULONG sigs = 0;
/*  #if 0 */
	DoMethod(wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE, app, 2, MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);

/*  #endif */
	set(wnd, MUIA_Window_Open, TRUE);

/*  #if 0 */
	while((LONG) DoMethod(app, MUIM_Application_NewInput, &amp;sigs) != MUIV_Application_ReturnID_Quit)
	{
	    if (sigs)
	    {
		sigs = Wait(sigs | SIGBREAKF_CTRL_C | SIGBREAKF_CTRL_D);
		if (sigs &amp; SIGBREAKF_CTRL_C) break;
		if (sigs &amp; SIGBREAKF_CTRL_D) break;
	    }
	}
/*  #endif */
	set(wnd, MUIA_Window_Open, FALSE);
	MUI_DisposeObject(app);
    }
    
    return 0;
}
&lt;/syntaxhighlight&gt;

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/*
    Copyright © 2002, The AROS Development Team.
    All rights reserved.

    $Id: dirlist.c 30792 2009-03-07 22:40:04Z neil $
*/

#include &lt;exec/types.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;stdio.h&gt;
#include &lt;string.h&gt;

#include &lt;dos/dos.h&gt;
#include &lt;intuition/gadgetclass.h&gt;
#include &lt;intuition/icclass.h&gt;
#include &lt;proto/exec.h&gt;
#include &lt;proto/intuition.h&gt;
#include &lt;proto/muimaster.h&gt;
#include &lt;clib/alib_protos.h&gt;

/* the following should go in a single include file which then only
** constits of the public constants and members. Actually this is easiey
*/

#include &lt;libraries/mui.h&gt;

struct Library *MUIMasterBase;

Object *app;

int main(void)
{
    Object *wnd, *str, *dirlist, *page;
    
    MUIMasterBase = (struct Library*)OpenLibrary(&quot;muimaster.library&quot;,0);

    app = ApplicationObject,
   	SubWindow, wnd = WindowObject,
    	    MUIA_Window_Title, &quot;dirlist&quot;,
	    MUIA_Window_Activate, TRUE,

    	    WindowContents, VGroup,
	    	MUIA_Background, MUII_GroupBack,
		Child, ListviewObject,
		    MUIA_Listview_List, dirlist = DirlistObject,
    	    	    	InputListFrame,
		    	End,
		    End,
		Child, HGroup,
		    Child, str = StringObject,
			StringFrame,
			MUIA_String_Contents, (IPTR)&quot;SYS:&quot;,
			End,
		    Child, page = PageGroup,
		    	MUIA_Weight, 0,
			MUIA_FixWidthTxt, (IPTR)&quot;AA&quot;,
		    	Child, ColorfieldObject,
			    MUIA_Colorfield_Red, 0xFFFFFFFF,
			    MUIA_Colorfield_Green, 0,
			    MUIA_Colorfield_Blue, 0,
			    End,
		    	Child, ColorfieldObject,
			    MUIA_Colorfield_Red, 0xFFFFFFFF,
			    MUIA_Colorfield_Green, 0xFFFFFFFF,
			    MUIA_Colorfield_Blue, 0,
			    End,
		    	Child, ColorfieldObject,
			    MUIA_Colorfield_Red, 0,
			    MUIA_Colorfield_Green, 0x66666666,
			    MUIA_Colorfield_Blue, 0,
			    End,
		    	End,
		    End,
		End,
	    End,
	End;

    if (app)
    {
	ULONG sigs = 0;

	DoMethod
        (
            wnd, MUIM_Notify, MUIA_Window_CloseRequest, TRUE, (IPTR) app, 
            2, MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit
        );

    	DoMethod(str, MUIM_Notify, MUIA_String_Acknowledge, MUIV_EveryTime,
	    	 (IPTR)dirlist, 3, MUIM_Set, MUIA_Dirlist_Directory, MUIV_TriggerValue);
		 
    	DoMethod(dirlist, MUIM_Notify, MUIA_Dirlist_Status, MUIV_EveryTime,
	    	 (IPTR)page, 3, MUIM_Set, MUIA_Group_ActivePage, MUIV_TriggerValue);
		 
    	set(dirlist, MUIA_Dirlist_Directory, &quot;SYS:&quot;);
	
	set(wnd,MUIA_Window_Open,TRUE);

	while (DoMethod(app, MUIM_Application_NewInput, (IPTR) &amp;sigs) != MUIV_Application_ReturnID_Quit)
	{
	    if (sigs)
	    {
		sigs = Wait(sigs | SIGBREAKF_CTRL_C | SIGBREAKF_CTRL_D);
		if (sigs &amp; SIGBREAKF_CTRL_C) break;
		if (sigs &amp; SIGBREAKF_CTRL_D) break;
	    }
	}

	MUI_DisposeObject(app);
    }

    CloseLibrary(MUIMasterBase);
    
    return 0;
}
&lt;/syntaxhighlight&gt;

WaitSelect() needs a pointer to your signal mask. So you need to do something like: 
&lt;pre&gt;
sigs |= SIGBREAKF_CTRL_C;
ret = WaitSelect(s+1, &amp;rdfs, NULL, NULL, &amp;sigs);
&lt;/pre&gt;
Then 'sigs' should contain the bits normally returned by Wait().

&lt;syntaxhighlight lang=&quot;c&quot;&gt;
/*
 * Amiga Generic Set - set of libraries and includes to ease sw development for all Amiga platforms
 * Copyright (C) 2004-2008 Tomasz Wiszkowski Tomasz.Wiszkowski at gmail.com.
 * 
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU Lesser General Public License
 * as published by the Free Software Foundation; either version 2.1
 * of the License, or (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program; if not, write to the Free Software
 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
 */

#include &quot;MUIPictureClass.h&quot;
#include &lt;Generic/LibrarySpool.h&gt;
#include &lt;libclass/intuition.h&gt;
#include &lt;libclass/muimaster.h&gt;
#include &lt;libraries/mui.h&gt;
#include &lt;libclass/utility.h&gt;

using namespace GenNS;

#define __NOGLOBALIFACE__
#include &lt;proto/graphics.h&gt;

   static struct Library *GfxBase = 0;
#ifdef __AMIGAOS4__
   static struct GraphicsIFace *IGraphics = 0;
#endif

   MUICustomClassT&lt;MUIPictureClass&gt; *MUIPictureClass::muiclass = 0;
   static int            openCount = 0;

MUIPictureClass::MUIPictureClass(IClass *cls)
{
   openCount++;
   parent   = cls;
   image1   = &quot;&quot;;
   image2   = &quot;&quot;;
   width    = 64;
   height   = 48;
   dtimg1   = 0;
   dtimg2   = 0;
   dt       = DatatypesIFace::GetInstance(44);
   if (dt == 0)
   {
      request(&quot;Warning&quot;, &quot;This program requires datatypes.library v44 or later\nGraphical buttons will not be displayed.&quot;, &quot;Continue&quot;, 0);
   }

   if (GfxBase == 0)
   {
      GfxBase = Exec-&gt;OpenLibrary(&quot;graphics.library&quot;, 39);
   }
#ifdef __AMIGAOS4__
   if ((GfxBase != 0) &amp;&amp; (IGraphics == 0))
   {
      IGraphics = (GraphicsIFace*)Exec-&gt;GetInterface(GfxBase, &quot;main&quot;, 1, (TagItem*)NULL);
   }
#endif
}

MUIPictureClass::~MUIPictureClass()
{
   closeImages();
   dt-&gt;FreeInstance();
   openCount--;
   if (0 == openCount)
   {
#ifdef __AMIGAOS4__
      Exec-&gt;DropInterface((Interface*)IGraphics);
      IGraphics = 0;
#endif
      Exec-&gt;CloseLibrary(GfxBase);
      GfxBase = 0;
   }
}

iptr MUIPictureClass::DoMtd(iptr *obj, iptr *msg)
{
   uint16  *minmax;
   iptr      k;

   switch (msg[0]) 
   {
      case OM_NEW:
         {
            if (!(obj = (Object*)DoSuperMtd(parent, obj, msg))) 
               return 0;

            k = (iptr)Utility-&gt;GetTagData(MUIA_Picture_NormalImage, 0, (TagItem*)msg[1]);
            if (k != 0)
               image1 = (char*)k;
            k = (iptr)Utility-&gt;GetTagData(MUIA_Picture_SelectedImage, 0, (TagItem*)msg[1]);
            if (k != 0)
               image2 = (char*)k;

            isDisabled = Utility-&gt;GetTagData(MUIA_Disabled, 0, (struct TagItem*)msg[1]) ? true : false;
            isSelected = Utility-&gt;GetTagData(MUIA_Selected, 0, (struct TagItem*)msg[1]) ? true : false;

            openImages();

            return (ULONG)obj;
         }
         break;

      case OM_DISPOSE:
      case MUIM_Hide:
         break;
      
      case MUIM_Show:
         {
            if (dt != 0)
            {
               if (dtimg1 != 0)
               {
                  dt-&gt;SetDTAttrsA(dtimg1, 0, 0, (TagItem*)ARRAY(
                     PDTA_Screen,         (iptr)_screen(obj), 
                     PDTA_DestMode,       PMODE_V43, 
                     PDTA_UseFriendBitMap,true,
                     TAG_DONE,            0));

                  dt-&gt;DoDTMethodA(dtimg1, 0, 0, ARRAY(DTM_PROCLAYOUT, 0, 1));
               }
               if (dtimg2 != 0)
               {
                  dt-&gt;SetDTAttrsA(dtimg2, 0, 0, (TagItem*)ARRAY(
                     PDTA_Screen,         (iptr)_screen(obj), 
                     PDTA_DestMode,       PMODE_V43, 
                     PDTA_UseFriendBitMap,true,
                     TAG_DONE,            0));
                  
                  dt-&gt;DoDTMethodA(dtimg2, 0, 0, ARRAY(DTM_PROCLAYOUT, 0, 1));
               }
            }
         }
         break;

      case MUIM_AskMinMax:
         {
            DoSuperMtd(parent, obj, msg);

            minmax = (uint16*)msg[1];
            minmax[0] = width;
            minmax[2] = width;
            minmax[4] = width;
            minmax[1] = height;
            minmax[3] = height;
            minmax[5] = height;
         }
         return 0;

      case OM_SET:
         {
            bool flg;
            bool refresh = false;
//            image1 = (char*)GetTagData(MUIA_Picture_NormalImage,   (int32)image1.Data(), (TagItem*)msg[1]);
//            image2 = (char*)GetTagData(MUIA_Picture_SelectedImage, (int32)image2.Data(), (TagItem*)msg[1]);
            flg = Utility-&gt;GetTagData(MUIA_Disabled, isDisabled, (struct TagItem*)msg[1]) ? true : false;
            if (flg != isDisabled)
            {
               isDisabled = flg;
               refresh = true;
            }

            flg = Utility-&gt;GetTagData(MUIA_Selected, isSelected, (struct TagItem*)msg[1]) ? true : false;
            if (isSelected != flg)
            {
               isSelected = flg;
               refresh = true;
            }

            if (refresh)
               MUIMaster-&gt;MUI_Redraw(obj, 0);
         }
         break;

      case MUIM_NoNotifySet:
      case MUIM_Set:
         {
            bool refresh = false;
            if (msg[1] == MUIA_Picture_NormalImage)
               image1 = (char*)msg[2];

            if (msg[1] == MUIA_Picture_SelectedImage)
               image2 = (char*)msg[2];

            if (msg[1] == MUIA_Disabled)
            {
               bool flg = msg[2] ? true : false;
               if (flg != isDisabled)
               {
                  isDisabled = flg;
                  refresh = true;
               }
            }

            if (msg[1] == MUIA_Selected)
            {
               bool flg = msg[2] ? true : false;
               if (flg != isSelected)
               {
                  refresh = true;
                  isSelected = flg;
               }
            }
            if (refresh)
               MUIMaster-&gt;MUI_Redraw(obj, 0);
         }
         break;

      case MUIM_Draw:
         {
            Object* o = 0;
            BitMap* bitmap = 0;
            void*   drawinfo = 0;

            if (0 == _rp(obj)) 
               break;

            if ((isSelected) &amp;&amp; (dtimg2 != 0))
               o = dtimg2;
            else if (dtimg1 != 0)
               o = dtimg1;
            else
               break;

            drawinfo = dt-&gt;ObtainDTDrawInfoA(o, (TagItem*)ARRAY(
               PDTA_Screen,   (iptr)_screen(obj),
               TAG_DONE,      0));

            if (drawinfo != 0)
            {
               dt-&gt;DrawDTObjectA(
                  _rp(obj),
                  o,
                  _mleft(obj),
                  _mtop(obj),
                  width,
                  height,
                  0,
                  0,
                  0);
               dt-&gt;ReleaseDTDrawInfo(o, drawinfo);
            }
            else
            {
               dt-&gt;GetDTAttrsA(o, (TagItem*)ARRAY(
                        PDTA_DestBitMap,     (iptr)&amp;bitmap,
                        TAG_DONE,            0));
               if ((0 != bitmap) &amp;&amp; (0 != GfxBase))
               {
#ifndef __amigaos4
                  BltBitMapRastPort(bitmap, 0, 0, _rp(obj), _mleft(obj), _mtop(obj), width, height, 0xc0);
#else
                  IGraphics-&gt;BltBitMapRastPort(bitmap, 0, 0, _rp(obj), _mleft(obj), _mtop(obj), width, height, 0xc0);
#endif
               }
            }
         }
         return 0;

   }
   return DoSuperMtd(parent, obj, msg);
}

void MUIPictureClass::openImages()
{
   if (dt == 0)
      return;

   closeImages();

   dtimg1 = dt-&gt;NewDTObjectA(image1.Data(), (TagItem*)ARRAY(
            DTA_GroupID,      (iptr)GID_PICTURE,
            PDTA_Remap,       true,
            OBP_Precision,    (iptr)PRECISION_EXACT,
            TAG_DONE,         0));

   dtimg2 = dt-&gt;NewDTObjectA(image2.Data(), (TagItem*)ARRAY(
            DTA_GroupID,      (iptr)GID_PICTURE,
            PDTA_Remap,       true,
            OBP_Precision,    (iptr)PRECISION_EXACT,
            TAG_DONE,         0));

   width  = 0x7fff;
   height = 0x7fff;

   if (dtimg1 != 0)
   {
      BitMapHeader *bmhd;

      dt-&gt;GetDTAttrsA(dtimg1, (TagItem*)ARRAY(
         PDTA_BitMapHeader,   (iptr)&amp;bmhd,
         TAG_DONE,            0));

      width  = width  &lt;? bmhd-&gt;bmh_Width;
      height = height &lt;? bmhd-&gt;bmh_Height;
   }

   if (dtimg2 != 0)
   {
      BitMapHeader *bmhd;

      dt-&gt;GetDTAttrsA(dtimg1, (TagItem*)ARRAY(
         PDTA_BitMapHeader,   (iptr)&amp;bmhd,
         TAG_DONE,            0));

      width  = width  &lt;? bmhd-&gt;bmh_Width;
      height = height &lt;? bmhd-&gt;bmh_Height;
   }

   if ((width == 0x7fff) &amp;&amp; (height == 0x7fff))
   {
      width = 64;
      height = 48;
   }
}

void MUIPictureClass::closeImages()
{
   if (dt != 0)
   {
      if (dtimg1 != 0)
      {
         dt-&gt;DisposeDTObject(dtimg1);
      }
      if (dtimg2 != 0)
      {
         dt-&gt;DisposeDTObject(dtimg2);
      }
   }
   width    = 64;
   height   = 48;
   dtimg1   = 0;
   dtimg2   = 0;
}

iptr* MUIPictureClass::CreateClass()
{
    if (MUIPictureClass::muiclass == 0)
    {
	MUIPictureClass::muiclass = new MUICustomClassT&lt;MUIPictureClass&gt;(MUIC_Area);
    }
    return (iptr*)MUIPictureClass::muiclass;
}

void MUIPictureClass::DestroyClass()
{
    MUICustomClassT&lt;MUIPictureClass&gt; *p = MUIPictureClass::muiclass;
    MUIPictureClass::muiclass = 0;
    delete p;
}
&lt;/syntaxhighlight&gt;

Check out #mui on irc.freenode.net and report bugs/problems there and [http://finance.groups.yahoo.com/group/MUI/ MUI Yahoo Group]


;[https://library.morph.zone/Magic_User_Interface_Programming Magic User Interface MUI]</text>
      <sha1>6iunzm4qg6p1qkkgouuo4eqo5px49io</sha1>
    </revision>
  </page>
  <page>
    <title>History of Western Theatre: 17th Century to Now/Russian Realist</title>
    <ns>0</ns>
    <id>242439</id>
    <revision>
      <id>4669089</id>
      <parentid>4528515</parentid>
      <timestamp>2026-09-06T09:09:54Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <comment>typo</comment>
      <origin>4669089</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="82911" sha1="7e8u708m7xywf35txvztopqodjlpm00" xml:space="preserve">=Anton Chekhov=

[[File:Anton Chekov 1901.jpg|thumb|Anton Chekhov was the dominant playwright of late 19th century Russian theatre, 1901]]

The dominant playwright of the Russian realist school is Anton Chekhov (1860-1904), whose main play of the 19th century is &quot;Дядя Ваня&quot; (Uncle Vanya, 1899), characterized like the rest of his mature plays by tragicomic characters ridden with anguish and purposelessness, some of whom with great hopes that their life, contrary to what seems, has not spent in vain, but serves as a harbinger of humankind's future happiness. In the view of Bakshy (1916), &quot;the Russian intelligentsia of the time of Chekhov presented, in its greatest part at least, a class of weak-willed individuals, handicapped in applying their gifts to the solution of practical problems by the peculiar social and political conditions prevalent at the time, and for this reason mostly given to introspection and dreaming, that helped to relieve the soul. Despair and pessimism born of aimless life, and the pursuit of dreamy idealism in the hope of finding refuge from a depressing environment, concealed innumerable elements of personal tragedy which, in the irresistible and unalterable flow of events, approached even the ancient tragedy of fate&quot; (p 41).

On Chekhov's plays in general, Williams (1965) commented that &quot;there is no modern dramatist whose characters are more consistently concerned with explicit self-revelation. All his plays might be described as plays of confession&quot; (p 132). Thompson (1942) further related that &quot;nobody in a Chekhov play seems to forward the action, such as it is. On the contrary, each character spends his time in egotistical self-absorption or hopeless yearning. Characteristically the dialogue is not about something to be done or faced, but is rather a series of self-revelatory monologues cut up in alternate speeches. One's interlocutor interrupts momentarily but scarcely disturbs one's train of introspection or reminiscence. These people do not listen; they merely think aloud. As their thoughts flitter from one thing to another, they change the subject without warning. At times they fall silent (a most revolutionary thing for the stage of Chekhov's time). Just as their minds wander on and off the subject, so their bodies wander on and off the stage without apparent dramatic occasion. They seem to be living their inconsequent and will-less lives before us&quot; (p 337). Gruber (1977) took issue with the notion that Chekhov's plays are plotless. &quot;Chekhov structures the action of his plays to create an illusion of inaction. In the plays of Chekhov, as in real life, the future is only vaguely felt. Chekhovian drama...presents the fate that we expect to issue from dramatic action is repeatedly denied, even as each separate act is 'undramatic' not because he portrays his characters' inner lives, nor because his plays are unified by emotion and not plot...Chekhov is undramatic because he does not cultivate in his plays the sense of impending destiny we normally expect of the dramatic illusion&quot; (p 512). In Chekhov’s dramaturgy, there is no big scene “no obligatory or great denouements...used to reveal through action the truth about the play’s central characters...We see...the drama and the complexity of the seemingly trivial...Almost all his dramatic devices were ironical...best seen in the disparity between what the characters say and what they do...Chekhov characters are addicted at making speeches...[by which we see how the character views himself rather than how others view him]...Chekhov’s symbol are...always concrete...effective because they grow out of the action...e.g. Moscow [as] the symbol of the three sisters’ dream of happiness...[There is also] the tendency on the part of his characters to aestheticize life...the most obvious is the tendency...to identify with great artists of the past” (Corrigan, 1965 pp 86-93). 

Agate (1944) was overly negative about the dramatic characters in &quot;Uncle Vanya&quot;. “Chekhov’s Uncle Vanya is an embroidery upon the theme of apprenticeship to sorrow...Vanya, the sentimentalist, unpacks his heart with words, nags at the fate he will not unbend his idealistic soul to conquer. Astrov, the man of action, gives his life to drunkenness and the cultivation of trees. Serebryakov, the invalid, is pure humbug. His wife, Elena, loving Astrov, lacks the courage of adultery; she is in no sense moral. Sonia, his daughter, loving Astrov, is a sick lily” (pp 99-100). Other critics have been more generous-minded: life in Uncle Vanya &quot;simply rusts away. And, what is truly important, these lives did not deserve to rust away, because they are rich with sensitivity and with the capacity for service. Vanya, who might have gone out into the world and advanced himself, fixed his life to the false star of a pedantic brother-in-law from whom he expected great things. Unhappily, he is too gentle and too isolated in the provinces to start a new life once he realizes that he was not serving humanity by relieving the professor of economic burdens. He is left with nothing except his fierce longing: 'If only one could live the remnant of one's life in some new way'. He knows only that 'we must make haste and work, make haste and do something' if life is not to become unbearable...And Vanya’s dream is expressed even more strongly by the district doctor, Astrov, who is in despair because in the whole district there are only two decent, well-educated people, himself and Uncle Vanya, both of whom have been swamped by 'the common round of trivial life...with its putrid vapors'. Astrov cannot even do justice to his profession, fighting as he does alone and without adequate means and preparation against a typhus epidemic. 'Those who will live a hundred or two hundred years after us, for whom we are struggling now to beat out a road,' he wonders, 'will they remember and say a good word for us?' The play is thus both a personal tragedy (or tragi-comedy perhaps) and the drama of a shipwrecked generation&quot; (Gassner, 1954a pp 516-517). Astrov “is a man of ideals, respected by all in the play except the self-centered Serebryakov. Yelena sees his excellence clearly...The symbol of tree planting is particularly apt in communicating Chekov’s vision, for it is an act which yields no instant gratification. Astrov sees that the casual destruction of forests will create a dismal future, but deliberate efforts to restore them will bring hope for a better life” (Short, 1986 p 378). “It seems to me especially meaningful that the most energetic, the most vital, the most balanced, the most intelligent, and all in all, the most attractive person in the play carries the point that work as it has meaning after death is the only good and meaningful work that we can ultimately do” (Freedman, 1967 p 39). Astrov is “the very image of what the good country doctor should be: dedicated, self-denying, sensitive to the needs of those around him. But that he is in fact over-sensitive leads to his one crippling quality: he cannot deal with the guilt he associates with his real or imagined deficiencies as a doctor, and so has turned to excessive drink” (Manheim, 2002 pp 126-127). Vanya must be seen as gifted and his resentment towards the professor justified; otherwise he is “merely a shallow kvetch occupying the stage for long periods with nothing more than cryptic and surly behavior. The play becomes little more than a sterile exercise devoid of compassion” (Krasner, 2012 p 125). “Only in flashes do we glimpse the man within, an adolescent who can neither be his age nor live up tom his looks. It is a lightweight who peers out through the pale eyes of the heavyweight face. He knows that he squandered his life on an old humbug, he knows that he has lost the power to live for himself, yet always he keeps up appearances. Dignity never deserts him. He clings to it even in the shooting spree, which becomes in its mad way a matter of honour, an assertion of principle rather than a display of temperament, and in tenacity like this there is a kind of heroism” (Tynan, 1961 p 437). “When Chekhov found it justifiable to expose the professor-egotist who had been subsisting ungratefully on the devotion and labor of Vanya, he produced a vivid and scathing portrait of a pedant who expects everyone to cater to him...[the] hard glitter of an educated parasite” (Gassner, 1960 p 190). “One point of the play may well be that the world exists to serve people like the professor and Elena. He is a pompous ass and she is beautiful but bored, idle, and utterly useless. The soft characters lack the will, the potency, the energy to change things” (Abbott, 1989 p 36). Vanya, Sonya, and Astrov discover that “our ordinary existence has a genuine horror in it...Sebryakov has all the...obtuseness, vainglory, and ignorance that are the curse of the academic profession” (Bloom, 2005 pp 181-182).

In Uncle Vanya, &quot;Chekhov follows in the steps of Turgenev. His favourite theme is disillusionment, and as for the kind of beauty he creates, beneath it also might be written ‘desolation is a delicate thing’. He is fond of the same kind of setting for his stories as Turgenev: summer woods, an old country-house full of cultivated people, who talk and talk. There you will find the idealist who melts over the futility of his own idealism, the girl who keeps a faster clutch upon daily duties in order to forget that youth is sliding away under her feet, the slightly stronger, clever man turned maudlin-cynical after his failure to find a purpose which can hold him- to think, so he feels, he, too, should be wasted- the old woman who only wants things to go on peaceably on old humdrum lines. The current of days is slow here; the air they breathe is sultry with undischarged energy, and broken only by unrefreshing nerve-storms; it is an atmosphere of sighs and yawns and self-reproaches, vodka, endless tea, and endless discussion. These people are like those loosely agglutinated sticks and straws which revolve together slowly in some sluggish eddy. They long to be detached and ride down the rushing stream, which they imagine somewhere near sparkles for ever past them. Where it is rushing they do not know. Some day- two hundred, five hundred years hence- perhaps life will be life...Elena...has already played her stake. In the professor she thought- heaven help her!- she had found a great mind, one it would be good and thrilling always to be near. Now, she has found her mistake. She is like a ship aground on a mudbank, and the only breezes which come to shake her sails are the passions she rouses in men, but she does not believe that they will blow her to any port where she would be. Like the others she has no sense of direction, no destination. Vanya’s helpless passion merely pesters her, and what between that and the exactions and pomposities of her eminent husband, who, now he has retired, only wants to watch his diseases and jaw to admirers, she is almost beside herself. The doctor, Astrov, through knowing better than the others what he wants and despising them, does move her a little. She nearly [succumbs to him]. . .but she is afraid. This man throws a fascination over poor, plain, dutiful Sonya,too. He has that attraction for women which the idealist a little damaged often exercises. Astrov, to Sonya, is so fine in himself; his slackness and coarseness are to her but wounds he got beneath the devil-defended walls of his peculiar virtues. He is a person to be saved (there is joy, too, in that) and comforted as well as loved; then he is handsome, and his voice is beautiful, and she is most affectionate. Lastly, the old professor, he is an industrious and magniloquent fraud. We know his prototypes and regret that so large a public should read again with so much admiration what has often been written before. For years Uncle Vanya and Sonya have slaved on the estate to provide tribute for the loquacious monster, the former at first with the conviction he was watering the roots of genius. On retirement the professor came to live there, bringing his beautiful, unhappy, baleful wife. That was event number one in the play; event number two, they departed. In between arrival and departure: nerve-storms (one of them homicidal), exasperations, and draggle-tailed disorder. Astrov seeking to renew his capacity to feel by keeping near Elena’s charms, forgets his work, Sonya is tortured by his continual presence, the long-retarded tide of youth is loosed together with a flood of bitterness in Uncle Vanya, and upstairs the tyrannic old invalid gasses and scribbles and groans among his medicine bottles&quot; (MacCarthy, 1940 pp 124-128).

&quot;The attitude of the various characters in the play towards work provides the underlying unity of theme in Uncle Vanya. Elena alone has no theories about it, but her devotion to her husband is itself a kind of work. Her husband, the professor, is extremely rigid in his demands on the people who surround him. He has lectured on art for twenty-five years; theoretically he believes in the importance of work, although his own work has always been of an impractical and selfish sort. Vanya, who has worked hard all his hfe, has become completely demoralized by the appearance of Yelena. At the end of the play, when he realizes that his love for her is doomed to disappointment, he takes up his work again as a help to him in enduring his mental anguish. Sonya is a thorough idealist. She keeps on doggedly at her work, sustained by her hope of a reward after death. She realizes that there is very little happiness in store for her in this world. She is not beautiful or attractive, and there is no hope that her love for Astrov will ever be returned. The views of Astrov, the doctor loved by Sonya and drawn to Elena, give 'Uncle Vanya' much of its distinctive tonal coloring. He is a curious combination of idealism and disillusionment. He is the antithesis of Uncle Vanya in that Vanya takes to drink during his temporary loss of ideals; Astrov drinks vodka regularly, and only under its influence can he recapture the dreams of his youth&quot; (Perry, 1939 p 347). 

&quot;Chekhov’s dualistic vision of reality is reflected in Astrov’s alternation between moods of hope and despair. Just as the terminally sick Dr Chekhov knew that, from his individual short-term view, there was little he could do to improve humanity’s lot during his brief lifetime, so Dr Astrov, in his darker moods, is depressed by the fact that his own puny efforts seem pointless and will even fail to be noticed. At the beginning of the play the overworked doctor is in just such a depressed mood. He has just lost a patient and this reminds him of the limitations of his profession and his own inability to significantly improve the lot of the peasants. Astrov, in this mood, loses the scientific objectivity that is vital for survival in the profession of medicine where the inevitability of death is a given. He recounts how his personal emotions became involved when his patient died. This leads him to voice his current feeling that perhaps his work, and life in general, are futile...Despite Astrov’s awareness that from his personal individual viewpoint there is no hope, he nevertheless continues to behave in a manner that takes into account future generations...Nothing could be more ludicrous than Vanya’s perfect comic entrance bearing autumn roses for Helen and finding her in the arms of Astrov. It is Vanya who, having wasted his own life, blames the professor for his own lack of vision and then makes the comically ludicrous claim, which even he realises is silly, that, but for the professor, he would have been a man of genius...Sonya’s long speech of faith at the end of the play is undercut by the fact that she is preaching to the unconverted&quot; (Borny, 2006a pp 178-181). 

==&quot;Uncle Vanya&quot;==

[[File:Uncle Vanya MAT.jpg|thumb|From left to right: Artem as Telegin, Lilina as Sonya, Raevskaya as Maria Voynitsky, Constantin Stanislavsky (1863-1938) as Dr Astrov, Olga Knipper (1868-1959) as Elena, Vishnevsky as Voynitsky, Moscow Art Theater, 1899]]

Time: 1890s. Place: Russia.

Text at http://en.wikisource.org/wiki/Uncle_Vanya http://www.gutenberg.org/ebooks/1756 http://www.readbookonline.net/plays/ https://archive.org/details/dli.ernet.241587 https://archive.org/details/dli.ernet.2826 https://archive.org/details/dli.ernet.234940

Astrov, a country doctor, attends to a retired professor, Alexander Serebryakov, master of an estate, mainly under the management of Vanya, the brother of his deceased wife, and Sonya, his daughter by this previous marriage. Vanya complains that the order of the household is disrupted by the arrival of the professor. He virulently criticizes himself for misjudging the intellectual quality of his former brother-in-law in front of Astrov, having wasted twenty-five years at the service of a charlatan, to which Vanya’s mother mildly objects. In contrast, Vanya only has praises for the professor's present wife, Elena. After noting that Alexander has no physical ailment as such, Astrov criticizes the idleness and indifference of country life, particularly the mismanagement of the environment. Vanya declares his love for Elena, but she rejects him. Late that night, Alexander complains to his wife of breathing problems and old age. Because of her father's complaints, Sonya sends for Astrov again, but the professor, suddenly feeling better, nonchalantly leaves without seeing him. Elena is distraught by discords in the house, Vanya by lost hopes. In his view, he met Elena too late, and the professor is not the genius he first thought he was in his youth, having accomplished nothing of worth. Concerned with their own woes, Astrov and Vanya drink heavily. Sonya scolds Vanya for it, convinced that the only way out of their doldrums is by working. Sonya also laments Astrov's heavy drinking in a tone suggesting love and concern of him, to which he appears unaware. Sonya meets Elena to resolve their past differences, but both are fixated on their own problems. Elena is unhappy about her marriage, Sonya hoping to marry Astrov. The following day, Alexander calls for a family meeting. Aside with Elena, Vanya urges her to break free from her husband, but once again she rejects him. Noticing Sonya's love for Astrov, Elena proposes to sound him on his feelings towards her. When she does so, Astrov reveals he has no amorous passion for Sonya whatsoever, laughingly concluding that this question is meant to sound his eligibility for her own passion towards him. Astrov kisses Elena as Vanya pathetically enters with a bunch of roses. More distraught than ever, Elena begs Vanya to use his influence on her husband so that the married couple may leave the house immediately. As the retired professor enters, Elena briefly signals to Sonya Astrov's negative response. Alexander proposes to sell the estate, at which, Vanya, crushed, asks him where does he propose he and Sonya should live. Vanya casts in his former mentor's teeth his ingratitude, for it is he and Sonya who have managed his estate. Angry words are exchanged and Vanya quickly leaves the room. Alexander follows to placate him, but a pistol shot is heard whereby Alexander returns, chased by Vanya, who fires again, misses, laughs at himself, and sinks into a chair. Later, Astrov demands that Vanya give him back a vial of morphine, enough to kill a man, which he relunctantly does after Sonya's intervention. Agreed to leave the estate, Alexander and  Elena bid everyone farewell. As so many times in the past, Sonya and Vanya are left to take care of house accounts. &quot;We shall live a long line of days, endless evenings; we’ll bear patiently the trials fate sends us; we’ll work for others now and in our old age without ever knowing any rest, and when our hour comes, we’ll die humbly and there beside the coffin we’ll say that we suffered, that we cried, that we felt bitter, and God will take pity on us, and you and I, uncle, darling uncle, shall see life bright, beautiful, fine, we shall be happy and will look back tenderly with a smile on these misfortunes we have now and we shall rest. I have faith, I believe warmly, passionately, we shall rest,&quot; Sonya asserts.

=Ivan Turgenev=

[[File:Félix Nadar 1820-1910 portraits Yvan Tourgueniev.jpg|thumb|Ivan Turgenev described the pains of unrequited love in country life. Photo of the author by Félix Nadar (1820-1910)]]

An important precursor of Chekhov's plays is &quot;Месяц в деревне&quot; (A month in the country, 1855) by Ivan Turgenev (1818-1883). In particular, &quot;A Month in the Country anticipates Chekhov in its attention to psychological detail and also in the way the story returns full circle to its starting-point” (Lamm, 1952 p 181).

&quot;A month in the country&quot; &quot;is as well made as though it concerned nothing in particular. The subtlety throughout is extraordinary, and Turgenev pays our minds a compliment by leaving the most important things unsaid. Natalia’s anguish in declining self-respect, Viera’s transition from the child to the woman who knows that her life will never be lived- these things have no words, yet they move us deeply. Ultimately both the languid lover and the tutor go away, leaving Viera to a loveless marriage and Natalia to the house which the presence of her well-meaning husband makes all the emptier. There is no climax, but then why should there be? A gentle melancholy suffuses this piece, and like Shelley’s wave, gives an ‘intenser day’ to all that it envelops” (Agate, 1944 p 94). &quot;The substance of A Month in the Country is the manner in which the restless Natalia tries to keep the devotion of each of several men but succeeds only in losing all of them except her docile and patient husband. She is one of those types never quite ready to relinquish her hold upon anyone, no matter what the cost in misery to the captive. As the play ends, the house will soon be quite empty. Natalia has reaped the harvest of her egotism&quot; (Skinner, 1931 p 257).

A Month in the Country “is really a bitter satire on sentimental, conventional love, with a dénouement featuring two very unromantic betrothals. Vera’s engagement with Bolshintsov and Lizaveta Bogdanova’s to Dr Shpigelsky are arrangements of convenience; the parties enter into their relationships only because they have admitted defeat in their quest for live. Vera’s disillusionment with her guardian is heightened by her tragically delayed realization that she loves Belyayev...Natasha’s jealous machinations thwarted any chance Vera might have of finding a young, romantic mate. In bitterness and defeat, she scorns Natasha and rejects the social and financial dependence she has grown to hate. Elizaveta, already 37 years old, knows that she is doomed to be the companion of an aging woman who will always treat her as a servant. Her union with Shpigelsky, though loveless, will free her from genteel servitude...Vera will be merely a pretty object; Bolshintsov will be unable to communicate with her at any level. Curiously, the wordly and sophisticated Shpigelsky is in a similar position. Weary of his own duplicity, he confesses his strengths and weaknesses to Lizaveta, offering her a loveless union that may give both of them the security they need to continue their twisted and stupid existences” (Grace, 1973 pp 96-97). “Vera’s plight moves us all the more because she is such an ordinary girl, and even Natalya, who deliberately consigns her to unhappiness, seems in some respects almost as pitiable as her victim. She is, after all, brought down by two uncontrollable forces: the ageing process, which is just beginning to tell on her, although she is not yet quite thirty, and the power of erotic passion, which we know to have ruined stronger persons than her. She is also trapped in an unrewarding marriage. Her unforgivable behaviour can at least be understood. The pull towards sympathy which Turgenev exerts upon us in relation to this ostensibly shameful character demonstrates his deep knowledge of human personality and his interest in the complexities of motivation and behaviour” (Briggs, 1999 p 102).

&quot;A month in the country&quot; &quot;ends without having reached a very decisive conclusion. Natalya, her husband, her husband’s mother, her son, and her son’s German tutor will continue living on the estate. Life will go on in much the same way as it has done heretofore, and Natalya will no doubt continue to be restless and dissatisfied. She and Belyayev seem to be badly coordinated people by comparison with Rakitin and Vera, both of whom have secured emotional tranquillity at the cost of immediate happiness. None of the four principal characters in this play has an agreeable prospect for the future. Only Natalya’s stupid husband thinks that everything has come out in the best possible way for himself and all the others...All of the people in A Month in the Country have more or less violent passions, but no one of them is able to satisfy his impulses. There is some inhibiting force within them, all which makes it impossible for them to express themselves as they would like to do. The practical circumstances of their lives have too much influence over them. They lack the strength of character that they should have if they are to be the masters of their own fates&quot; (Perry, 1939 p 331). In the final scene, &quot;as he bids them all farewell, Belyaev suddenly understands that he himself has been the cause of all this tangled web of misdirected affections, and in a rush of remorse such as only a Russian can comprehend, he, too, departs, and life on the estate resumes its monotonous course above the wreckage of unfulfilled passions&quot; (Sayler, 1921 p 396).

==&quot;A month in the country&quot;==

[[File:Stanislavski&amp;Knipper1909.jpg|thumb|Mihail loves Natalia but is not loved in return, played respectively by Constantin Stanislavski (1863-1938) and Olga Knipper (1868-1959) at the Moscow Art Theatre in 1909]]

Time: 1850s. Place: Russia.

Text at http://gutenberg.net.au/ebooks03/0300831h.html https://archive.org/details/in.ernet.dli.2015.105455
https://archive.org/details/in.gov.ignca.29218

A wealthy landowner and bachelor friend of the family, Mihail Rakitin, spends much time in the company of Arkady Islayev's wife, Natalia. When Mihail questions Alexey  Belyaev, the recently hired tutor to their son, about his past life, the latter mentions once translating a French novel without even knowing any French at all. A neighbor of theirs, Afanasy Bolshintsov, owner of over three hundred serfs, requests the advice of their family doctor, Ignaty Shpigelsky, concerning a possible marriage between himself and Vera, orphaned ward of the Islayevs. Should this be accomplished, Afanasy will give him three horses. Ignaty introduces the subject to Mihail, who, in turn, does so to Natalia, who dislikes the idea, considering the man a &quot;stupid creature&quot;. Of greater importance to himself, in view of his love of her, Mihail notices Natalia's infatuation for Alexey. When Natalia questions Vera about her feelings for Afanasy, she miserably answers: &quot;I'm in your power, Natalia Petrovna.&quot; Natalia assures her that she will be free to choose her choice of a husband. Then she learns that Vera loves the man she herself loves, Alexey, her son's tutor. Suspecting he may lose Natalia, a worried Mihail selfishly advises her to dismiss Alexey. Instead, Natalia seeks to find out whether Alexey loves Vera. He does not seem to. Meanwhile, Ignaty courts Lizaveta, another family friend, and seems to make some headway there. Vera discovers that Alexey does not love her and also that Natalia loves him and perhaps plans to marry her off to Afanasy after all. To Alexey's astonishment, Natalia declares her love to him, but she hesitates on whether he should leave the house, finally deciding she cannot have him go. Meanwhile, Arkady notices Mihail's attachment towards his wife. A sad witness to Natalia's love of another, Mihail decides to leave the house. Also unable to live any longer with Natalia, Vera questions the doctor about Afanasy, who assures her he is most kind-hearted and &quot;like dough&quot;. To Natalia's grief, Alexey, uncomfortable with his position as the recipient of his mistress' love, decides to leave the house as well. Mihail grits his teeth while Arkady expresses his gratitude for this sacrifice to their friendship. Lizaveta is also free to go, having agreed to marry Ignaty, most glad at obtaining the horses.

=Leo Tolstoy=

[[File:Ilya Efimovich Repin (1844-1930) - Portrait of Leo Tolstoy (1887).jpg|thumb|Leo Tolstoy wrote about greed and murder in the peasant class. Portrait of the author by Ilya Repin (1844–1930), 1887]]

Of further interest in Russian realistic drama is a gritty peasant play: &quot;Власть тьмы&quot; (The power of darkness, 1886) by Leo Tolstoy (1828-1910).

&quot;I am much disposed...to recognise in The Power of Darkness one of the most perfect masterpieces which ever graced any literature, and to perceive that Tolstoi seems to have imported in it a new form of popular drama, and one capable of universal application. The idea that a fault may be atoned for by voluntary confession and expiation is certainly not a new one. But none of Tolstoi's predecessors has succeeded, so far as my knowledge goes, in expressing it in so dramatic a fashion, nor with so much true and simple grandeur. He gives us Nature herself, as she lives and moves, taken from the rustic life, without the smallest affectation, or the slightest touch of rhetoric. Figures and surroundings, methods of speech and ways of feeling, have all been observed, noted even to their most delicate shades, and rendered in a fashion that is miraculous. Though Nikita, the guilty peasant, speaks the ordinary language of the populace, he uses some phrases and expressions which reveal his knowledge of circles other than those of his own village. You realise that a railway must have been made through the place, and that the foam of city civilisation has thus been cast, by way of the tavern, on to the threshold of the peasant's hut&quot; (Waliszewski, 1900 pp 391-392).

&quot;Act 1 introduces a problem in terms long familiar to the comic theatre. Peter...is the typical cuckold. He has taken as his second wife some ten years junior in years...Anisya is correct in her complaint to her husband that his plans are based on desires for his own comfort and a disinterest in hers...It is typical of the comedy of cuckolding, too, that the wife should take a younger man as her lover...The other characters, too, are presented in this first act in comic terms. Matrena, Nikita's mother, is the old bawd- crafty, vulgar, hypocritical...In Act 2 greed becomes  the controlling motive...[it] opens with the problem of the lovers' ridding themselves of Peter, finding his money, and concealing the crime, and almost every speech in this act is concerned with this problem...There is [in act 3] not merely the  grimness that we expect from the naturalistic view, but there is also the hopelessness...Nikita offers his father money, his father refuses. He orders Anisya from the house, but she does not leave, Akim speaks of the 'ruin' that is coming, but, in truth, the ruin is already there. Only the half-witted Akulina finds any pleasure at all...Act 4 [is] a scene of horror, a drama of the grotesque...more closely akin to Webster's 'The duchess of Malfi'...than to anything in modern drama...[This play] is the only modern drama that systematically uses dramatic points of view, not for the purpose of arriving at a relativist conclusion about the impossibility of truth, but to demonstate the supremacy of the moral-religious view&quot; (Nolan, 1965, pp 3-9).

&quot;Of the three chief characters involved, all the blackest of criminals, only two suffer from the pangs of a guilty conscience. Matryona, the mother of Nikita, is at the bottom of aU the crimes. Her husband is a devout and god-fearing man, who pleads with his son to forsake his evil ways. Yet she encourages her son in his downward career and finally helps in forcing him to murder his own child. Yet she does not seem to have the slightest feeling of guilt. She is even pious about her crimes, insists on baptizing the infant before it is murdered by its father, and constantly has the name of God on her lips: 'Well, but with the Lord's help, when we've covered this business, there'll be an end of it'...Aniaya, who with the help of Matryona murdered her husband to get his wealth and to be able to marry Nikita, gradually becomes more hardened in her career of crime. Yet her guilt weighs heavily upon her conscience...She feels remorse, but with her it does not change to repentance as in the case of Nikita. To revenge herself on him for having betrayed her, she, fiend-like, drives him on to the same condition. He, on the other hand, after he has once been brought to his senses, assumes not only his own guilt but also that of his wife and of his mother. He makes his confession not because his crime has been found out, but at the very point when it is least likely to be discovered. The pangs of remorse, a deep conviction of guilt, force him to make his confession&quot; (Cast, 1917 pp 523-524).

“Matriona...is a bustling old woman, quite unscrupulous in her desire to make her son’s fortune, and perfectly ready to serve as procuress or a blender of poisons...Her husband Akim...seems half crazy; he is a shy stammering man...and every good action is the result of some impulse of his...Akulina, an ugly over-grown child, is at first completely under her mother’s thumb, but later on, with the help of Nikita and after her father's death, she learns to browbeat her in her turn...Everything, even scenes of horror, seems to happen and be discussed as if it were quite natural, with the result that the audience is doubly moved...Nikita...is always musing about his crimes, partly because his conscience is uneasy but partly also because they have served no purpose” (Lamm, 1952 pp 183-185). Nikita &quot;drifts through life along the line of least resistance. He is not deliberately vicious; yet he is impelled from crime to crime by influences that are stronger than himself. The germs of sin are fructified within his soul by the power of darkness&quot; (Hamilton, 1920 p 152). Matryona is &quot;a memorable character, repulsive, hypocritical and callous, yet in a queer, perverted fashion devoted to her son&quot; (Wilson, 1927 p 191). “The women in this play are enslaved by superstition and convention. The men weigh morality, the women consider expediency only. After he has murdered his infant, Nikita constantly emphasizes his terrible fall and the destructiveness of the women...But Matrena and Anisya, oblivious to moral as opposed to social consequences, devote their energies to the continuation of a corrupt society that is based upon money, security, and respectability” (Grace, 1973 p 106).

Gassner (1954a) concluded that &quot;if the play derives its strength from the marvelous naturalistic portrayal of the culprits, it is the totality of effect that is important. The play is a tragedy of sin and expiation, and it takes the Russian drama beyond Ostrovsky in one important respect: it adds the dimension of humanitarianism to the stark photography of life&quot; (p 506). Goldman (1914) described the social impact of the play as &quot;a terrible picture of poverty, ignorance and superstition. To write such a work it is not sufficient to be a creative artist: it requires a deeply sympathetic human soul. Tolstoy possessed both. He understood that the tragedy of the peasants' life is due not to any inherent viciousness but to the power of darkness which permeates their existence from the cradle to the grave. Something heavy is oppressing them- in the words of Anisya- weighing them down, something that saps all humanity out of them and drives them into the depths. 'The power of darkness' is a social picture at once appalling and gripping&quot; (p 282).

==&quot;The power of darkness&quot;== 

[[File:Scene from The Power of Darkness.jpg|thumb|Illustration of &quot;The power of darkness&quot; from Russian Theatre, Brentano's, New York, 1922]]

Time: 1880s. Place: Rural Russia. 

Text at http://en.wikisource.org/wiki/The_Power_of_Darkness https://archive.org/details/in.ernet.dli.2015.531140
https://archive.org/details/in.gov.ignca.29219

Nikita, a laborer on Peter Ignatitch's estate, is forced by his father to marry Marina. Anisya, Peter's wife but Nikita's lover, weeps at these news and feels betrayed. &quot;My old man will die one of these fine days, I'm thinking; then we could cover our sin, make it all right and lawful, and then you'll be master here,&quot; she says, consoling herself. Matryona, Nikita's mother, observing their embraces, is content merely to say: &quot;What I saw I didn't perceive, what I heard, I didn't hearken to. Playing with the lass, eh? Well,- even a calf will play. Why shouldn't one have some fun when one's young?&quot; She is against the marriage, preferring Nikita to keep his well-paid position, and so she buys poison so that Anisya may use it on her husband, at which the latter pays her back. Matryona's husband, Akim, finds a job in town cleaning cesspools and prefers to have his son stay at home, all the more so because otherwise he will wrong Marina if he does not marry her, but Matryona calls her a common slut and her son suggests in a roundabout way the same. Marina accuses Nikita of deceit, knows he does not love her any more, and knows whom he loves at the moment, at which he brutally sends her on her way. As Peter is being slowly poisoned over the course of several months, Anisya's anxieties grow because she does not yet know where her husband hides his money. He may give it to his sister, Martha. While tea is prepared, Matryona assures the suffering Peter he will obtain a fine burial service. As Matryona helps him into the house, she feels the money on his person, so that Anisya succeeds in retrieving it and gives it to Nikita to bury. She then re-enters the house and comes out screaming. Matryona rolls up her sleeves to lay out the body. As Anisya wished, Nikita becomes the new master, but he quickly becomes enamored of Anisya's step-daughter, Akoulina, and squanders on her the money his wife killed for. He puts on airs with Akoulina and throws money at Akim, who finds such doings filthy, but nevertheless keeps the money. Akoulina quarrels with Anisya and accuses her of murdering Peter. To settle the quarrel, Nikita pushes Anisya out of the house, but after a while calls her back and gives her a present. Even more disgusted at such doings and considering he is heading for ruin, Akim gives back the money to his son. Several months later, Akolina is about to give birth as Matryona tries to arrange a marriage for her. Since she is unmarried, Anisya and Matryona plot to get rid of the baby, asking Nikita to dig a hole in the cellar, which he reluctantly does. Anisya retrieves the newborn wrapped in rags and throws it for Nikita to take care of, who is surprised to see it still alive. &quot;Be quick and smother it, and then it won't be alive.&quot; she says. &quot;It's your doing and you must finish it.&quot; Nikita comes out of the cellar trembling and upset: &quot;How the little bones crunched under me!&quot; he exclaims. He imagines he hears it whimpering still. In mortal conflict, he chases Anisya about with the spade. &quot;How can it whimper?&quot; asks his mother. &quot;Why, you've flattened it into a pancake. The whole head is smashed to bits.&quot; During Akolina's wedding ceremony with another man, Nikita feels unable to give the blessing. Instead, he ties a rope around his neck. Matryona removes it. Anisya invites him back to the party. As they go, he picks up the rope again, but one of his laborers hangs on to it laughingly and drunkenly till he gives up. On entering the room with the guests, he falls drunkenly and declares: &quot;Christian Commune, I have sinned and I wish to confess.&quot; Very much alarmed at the beginning of this speech, Matryona says her son must be taken away. Despite her intervention, he confesses to Akim's joy to the murder of Peter and the baby, which Akoulina confirms to have borne. He says he did everything alone.

=Alexander Ostrovsky=

[[File:Aleksandr Nikolayevich Ostrovsky 2.jpg|thumb|Alexander Ostrovsky described the vehement conflicts between a mother, her son, and his wife, 1870s]]

Another dramatist of interest is Alexander Ostrovsky (1823–1886), who wrote 48 plays from 1847 to 1884, including three major ones: &quot;Гроза&quot; (The thunderstorm, 1859), &quot;Лес&quot; (The forest, 1871), and “На всякого мудреца довольно простоты” (No fool like a wise one, 1868, also known as Enough stupidity in every wise man).

The Thunderstorm &quot;is the atmosphere of the little Russian town, with its primitive inhabitants, merchants, and workpeople, an atmosphere untouched, unadulterated by the ideas of any exterior European influence. It is the Russia of Peter the Great and Catherine's time, the Russian patriarchal family life that has existed for hundreds of years through all the towns and villages of Great Russia, that lingers indeed today in out-of-the-way corners of the Empire, though now invaded and much broken up by modern influences. It is, in fact, the very Muscovite life that so puzzled our forefathers, and that no doubt will seem strange to many English readers. But the special triumph of The Thunderstorm is that although it is a realistic picture of old-fashioned Russian patriarchal life, it is one of the deepest and simplest psychological analyses of the Russian soul ever made. It is a very deep though a very narrow analysis. Katerina, the heroine, to the English will seem weak, and crushed through her weakness; but to a Russian she typifies revolt, freedom, a refusal to be bound by the cruelty of life&quot; (Garnett, 1922 pp 136-137). The play &quot;is one of the best dramas in the modern repertoire of the Russian stage. From the stage point of view it is simply admirable. Every scene Is impressive, the drama develops rapidly, and everyone of the twelve characters introduced in it is a joy to the dramatic artist&quot; (Kropotkin, 1905 p 270). “Boris and Katerina have only two stones alone together during the play: one at the end of the 3rd act and their scene of parting in the 5th act. Boris appears momentarily in the 4th act; but while his presence is dramatic, no words are spoken between them. This situation involving unlawful love and marital infidelity would have given rise to a very different series of scenes in the hands of a contemporary French, German or English dramatist. Either a problem play or a semi-romantic tragedy would have evolved. Ostrovski does not emphasize either plot or the discussion of the problem of marriage. Therefore, he has plenty of time to analyze his characters and to present his theme through their actions, personalities and conversations, especially as the actual story of the play does not begin to unfold until towards the dose of the third act…Katerina does not exist primarily as a study of a dramatic character. She is entirely subservient to the theme; but diminution of the element of plot made such analysis of character possible in drama as well as in the novel in which the element of time is not a vital question” (Stuart, 1960 pp 601-603). Ostrovsky “knew his types and presented them with faithful realism...But his realism was more than photography. For her refused to give his plays an ending, just as plots of real life always carry on into new ones. The endings of his last acts always show a vista of the story that continues beyond. The peasant heroine of The Thunderstorm, after her faithlessness has been discovered and her lover drowned, sees the long, bitter life ahead of her: slavery and social disgrace” (Moderwell, 1972 p 181). &quot;The conflict is very strongly marked between the mysticism and hunger for beauty, which are the dominant characteristics of Katerina, and the narrow ignorance and tyranny, which are exemplified in the household of Kabanova...The next act stresses still further the cramped environment of Katerina, in showing the jealous tyranny of her mother-in-law and the weakness and selfishness of her husband, who, anxious to escape from Kabanova's domineering for a few weeks of dissipation, turns a deaf ear to his wife's premonitions of evil and refuses to spoil his holiday by taking her with him...Katerina's longing for some colour and beauty in life is too great for her to make any long resistance...The superstitions and rough despotism of the older generation are contrasted with the sentimentality of Varvara and her friend and the passionate tenderness of the newly-met lovers...The crisis comes with the fourth act, where the storm of the elements is re-echoed by the tempest in Katerina's heart and mind. After her husband's unexpected return, she realises her guilt and, in her suffering, feels that the storm, according to the beliefs of the townspeople, had come as punishment for her sin. Everything conspires to play on her overstrained nerves,- the storm, a sudden meeting with Boris, the denunciations of a religious maniac, who appears at intervals throughout the play, and an inscription about Gehenna and the Day of Judgment on the walls of the ruins, where they have taken shelter. These last two details, together with Katerina's fear of storms, have been suggested much earlier in the play and therefore fit in quite easily in obtaining the cumulative effect of strain, which breaks down her silence and makes her cry aloud her shame...She...eludes the careful watch, which is kept over her, and coming down to the river, half-dazed from the emotional struggle she has undergone, she meets Boris. This rather inadequate lover is completely dependent on his uncle and therefore, when sent to an appointment in Siberia, can think of no other course than to obey instructions. Family discipline was very strong among the merchants. He can only return tender words to Katerina's request for freedom and show her that it is impossible to take her with him. Life then holds no possibilities for her. Feeling herself completely accursed, she does not hesitate long. What does another sin matter? Better suicide than this half-death&quot; (Beasley, 1928 pp 606-608). &quot;Kabanova...declares that Katerina cannot love her husband, because otherwise, when he went away, she would have howled for an hour and a half and fallen down on the porch. That was the accepted method as Kabanova understands it, and she abuses Katerina for not doing it. She treats her son as badly as she does his wife. Her daughter has learned the method of acting under this regime. She obeys meekly and slips out the back door to her lover. Katerina is induced to try it but she takes that also too seriously and finally she drowns herself. Her husband who loves her dearly threatens to rebel against the harsh rule of his mother, but she merely sneers...We agree to the moral callousness of the old woman but she is the dominating character. Katerina with her charm is really weak. So is the son, and there will be a long way yet to go before they seriously threaten the rule of the old shrew...Thus, as we run through the plays of Ostrovsky, we find that they picture the newer life which was replacing that of the stern old patriarchs of the thirties and the forties&quot; (Manning, 1930 pp 37-40). &quot;Catherine is a romantic, with leanings towards mysticism. She sins and curses her love and her lover even as she yields to them. Her husband is a brute, with coarse instincts and some good feeling. His mother is a domestic tyrant, brought up in the school of Pope Sylvester. When, at the moment of her indifferent husband's departure, Catherine, with a presentiment of her impending fate, casts herself on his breast, beseeching him to stay, or to take her with him, the old woman interferes...and so Catherine seeks in another man's arms the caress, the loving words, the tender clasp for which her soul- the soul of a modern woman- hungers&quot; (Waliszewski, 1900 p 274). “Dikoy represents the greedy miser, whose every walking movement is planned to exhort money dishonestly. When confronted by logic, he uses brute force and outmoded irrational arguments to maintain his position. The equally vile matriarch, Kabanikha, defends medieval practices, among them absolute submission by her family...Tikhon passively assents to [Katerina’s] mistreatment, too fearful of his mother to defend his wife. Katerina’s lover, Boris, is similarly weak-willed and sacrifices her to Dikoy’s cruel dictates...Katerina...is torn between rejecting the strictures of the old and remaining loyal to religious tradition” (Frank, 1986 p 1450). 

The Forest &quot;shares with The Thunderstorm the honor of being regarded as his masterpiece. Less exclusively original, the comedy is extraordinarily rich in its character drawing. Of all Ostrovsky’s plays, it is the one in which the essential nobility of man is most triumphantly asserted. But it also contains the most unsweetened types of cynical and compla- cent meanness and selfishness in the whole of Russian literature&quot; (Mirsky, 1949 p 239). The play &quot;is a concentration of all the previous history of both west European and Russian theater. This effect is provided first of all (though not entirely) by the characters of two actors, the tragedian Gennady Neschastlivtsev (Unlucky) and the comedian Arkashka (Arkady) Schastlivtsev (Lucky). They both behave theatrically in real life, and their theatricality is the sum of all the roles they have ever played. For Neschastlivtsev, these include, first of all, Shakespeare (Hamlet), Schiller (Karl Moor), and Cervantes (the non-dramatic role of Don Quixote). Meanwhile, Schastlivtsev, who acts as Sganarelle, the role once played by Molière himself, with its roots in French théâtre de la foire (‘fair theater’) and Italian commedia dell’arte, impersonates the tradition of all the ‘comic unfortunates'&quot; (Kuptsova, 2019a p 114). “Ostrovsky presents two provincial actors, Grigory Neschastlivtsev and Arkashka Schastlivtsev, whose dramatic talents are doubtful and whose everyday behaviors are flawed, as far superior to and more noble than the residents of the Penki Estate (the shabby-genteel nobility and the emerging ravenous entrepreneurs). It is interesting (from a historical perspective, too) in this regard to observe the successive set of the actors’ self-characterizations in the play, their gradual evolution from skomorokh (the nomadic type, ‘unmounted travelers’), court jester, actor, to noble artist...The roles they play in life correspond to the characters they play on stage, Neschastlivtsev being a tragic, Schastlivtsev a comedic actor...All of the quotes from Shakespeare’s tragedy pronounced by Neschastlivtsev (whether appropriately or not, whether they be small or very important fragments of the role) in The Forest rhyme the story of Penki residents with that of the Prince of Denmark. In both cases, deception, hypocrisy, and crime are discovered with the help of comedians...In the final part, one of the two dramas in the prompter Arkashka Schastlivtsev’s parcel turns out to be the five-act The Robbers by Friedrich Schiller, whose influence on Russian Romantic theater was at least as significant as that of Shakespeare. The robbers theme is represented in The Forest in two parallel dimensions. On the one hand, the social perception of skomorokhs/actors and robbers is very much identical. On the other hand, the theme of noble robbers is of central importance in the Romantic repertoire. Therefore, the forest fellowship of noble robbers and the guild fellowship of “noble artists” act as contextual synonyms, forming a unique theatrical metaphor” (Kuptsova, 2019b pp 209-211).
 
&quot;No fool like a wise one&quot; &quot;emphasizes the fact that simple human beings like to be flattered, even when they know the painful truth about themselves, and also points out that some flaw is to be found in the armor of the most hardened hypocrite&quot; (Perry, 1939 p 333).

&quot;While Gogol, Griboyedov, and their contemporaries had confined themselves to a bitter exposure of the nobles and the bureaucrats, Ostrovsky went further, and showed up this unproductive section of society in direct contrast to the bourgeoisie, whose character and conduct he paints sympathetically, though not without some shrewd criticism. His comedies were the first to deal, on a large with the mentality of a class which no Russian dramatist as yet had thought it worthwhile to describe with such particularity. His method was to exclude any touch of romance or pathos, his sole concern being to represent men and matters as they actually are; his plays mark the beginning of realism on the Russian stage- that realism to which it was to owe its most important successes in the future&quot; (Fülöp-Miller and Gregor, 1930 p 40). 

Ostrovsky's &quot;plays, as a rule, are neither comedies nor dramas. Dobrolioubov called them 'representations of life'. The audience is not given anything to laugh at, nor yet anything to cry over. The general setting of the piece is some social sphere which has little or no connection with the characters we see in it. These characters moving themselves are neutral in tint neither heroes nor malefactors. Not one of them rouses direct sympathy. They are all overwhelmed by a condition of things the weight of which they might shake off, the danger of which would vanish, if they showed some little energy. But of this they have not a spark. And the struggle is not between them, but between the facts, the fatal influence of which they undergo, for the most part, unconsciously. A sort of gloomy fatalism presides over this conception of mundane matters, an idea that anyman belonging to a particular moral type must act in a particular manner. The natural deduction from this theory is that actions are not good or bad in themselves. They are merely life. And so life itself is neither good nor evil. It is as it is, and has no account to give to anybody. Ostrovski's pieces have generally no denouement, or, if they have one, it is always of an uncertain nature. The dramatic action never really closes, it is broken off; the author cutting it short, not by an effective scene or phrase, but frequently, and deliberately, at the most commonplace point, or in the middle of a rejoinder. He seems to avoid effect just where it naturally would occur in the situation. Ostrovski's admirers hold this to be his manner of typifying real life, which, in nature, has neither beginning nor end. I have already made my reservations on this head; and I am glad indeed to affirm that no other Russian writer, save Tolstoi, has painted so great a number of types and circles corresponding with almost every group in Russian society. His language, full of power and fancy, constitutes, with that of Krylov, the richest treasure-house of picturesque and original expressions to be found in Russia. Pushkin had already declared that the way to learn Russian was by talking to the Moscow Prosvirnie (the women who make the sacred bread, prosford). They taught Ostrovski precious lessons&quot; (Waliszewski, 1900 pp 276-277).

&quot;Ostrovsky’s pictures of the sordid and disagreeable world into which he introduces us do not provide the relief of either noble suffering or hearty laughter. The flat realism which he presents is more inclusive than that of Gogol or Turgenev and therefore less selectively refined than that of the earlier writers. It is, however, a powerful description of the externals of a mediocre social group. It is, in addition, thoroughly representative of the aesthetic tendencies of the nineteenth century in Russia and elsewhere throughout Europe. The continuous rise of the middle class tended to stimulate a kind of art which does not make excessive demands upon the imagination. Ostrovsky offered his audiences plenty of variety in scenes drawn from observation and experience. In some of his plays the merchants are good; in others they are bad. In some, children get their way; in others, parents or guardians get theirs. Conditions are never the same in any two cases, and therefore, in his view, no general principles can be extracted from the welter of human society. The aim of a realistic artist like Ostrovsky is to present life as he sees it, vividly and accurately, with the utmost photographic exactness&quot; (Perry, 1939 pp 334-335).

&quot;The virtues and defects of Ostrovsky’s plays are, on the whole, the same which we find in Russian prose writers. He is, above all, simple and natural- so natural that he gives the impression of following the depicted events rather than organizing them. He neglects the plot and concentrates upon the characters and their dramatic conflicts. These arc taken straight from life with great tolerance and objectivity. This is why his plays have the logic of life itself and not that of literary inventions. His sober eye, as well as his strong sense of measure, avoids all tricks or effects for their own sake. His very irony seems to be the irony of life caught by the author quite by chance, as it were. Yet there is perhaps just one flaw in his figures they are those of a great observer rather than a great creator&quot; (Lavrin, 1928 p 54).

“It is diversity of his characterisation which provides one of the most striking features of Ostrovsky’s work. His plays explore a whole spectrum of humanity from peasants to the nobility. A brief examination of the principal characters in his early works alone reveals civil servants, noblemen, landowners, peasants, teachers and servants, depicted alongside the merchants. His later works would go on to portray members of ‘high society’, provincial actors and representatives of the emerging capitalist class” (Rahman, 1999 pp 169-170). 

==&quot;The thunderstorm&quot;== 

[[File:Merchant Dikoy from Storm (Ostrovskiy) by Kustodiev (1920, priv.coll).jpg|thumb|Dukoy deviously robs Boris of his inheritance. 1920 picture of the merchant by Boris Kustodiev (1878-1927]]

Time: 1850s. Place: Kalinov, Russia.

Text at http://www.gutenberg.org/ebooks/7991 https://archive.org/details/storm01ostrgoog https://archive.org/details/cu31924026730311 https://archive.org/details/cu31924026730329 https://archive.org/details/storm00ostr
 
Being an orphan, Boris is the recipient of his grandmother's will whereby his uncle, Dukoy, a merchant, is to pay him and his sister a fair share of her fortune provided he shows proper respect for his authority. But Dukoy takes advantage of the situation by pretending never to be satisfied and thereby keeps the money for himself. In the Kabanov household, Marfa is unhappy about the way her son, Tihon, handles his wife, Katerina, too softly in her view. Tihon does not understand why he should foster fear in his wife. &quot;Why should she fear you!&quot; she exclaims. &quot;What do you mean? Why, you must be crazy. If she doesn't fear you, she's not likely to fear me.&quot; Katerina confesses to Varvara, Tihon' sister, that she is in love with another man. Varvara promises to help her. &quot;No, no, that must not be,&quot; she says. &quot;What are you saying! God forbid!&quot; She fears a storm is brewing. &quot;Don't talk of not being afraid,&quot; she says. &quot;Everyone must be afraid. What is dreadful is not it's killing you, but that death may overtake you all of a sudden, just as you are, with all your sins, with all your erring thoughts. I have no fear of death, but when I think that I shall be brought all at once before the face of God just as I am here, with you, after this talk,- that's what is awful! What I had in my heart! What wickedness! Fearful to think of!&quot; Varvara guesses correctly that Katerina loves Boris. As Tihon prepares to leave on a two-week journey, his mother mentions some specific recommendations. &quot;Lay your commands on your wife, exhort her how she is to live in your absence,&quot; his mother insists, &quot;and then when you come back, you can ask if she has performed everything exactly.&quot; Varvara steals the garden-key from her mother, so that Katerina can meet her lover in the summerhouse and delivers at the same time a message to Boris that he must be near. While waiting for her, he confides to a friend, Kudriash, that he loves a married woman. Kudriash guesses who it is. Katerina meets Boris, veiled. &quot;Do you know that never by any prayer can I be free of this sin, never again?&quot; she asks. &quot;Like a stone it will lie on my soul, like a stone.&quot; But yet she is determined to go on. &quot;If they lock me up, that will be my death. And if they don't lock me up, I will find some way to see you again,&quot; she adds. As they retire together, Kudriash meets Varvara. They kiss and yawn. When Tihon eventually returns from his journey, Marfa notes how unhappy Katerina appears. A storm is on its way and Katerina is afraid. Tihon says that being afraid of storms is a question of temperament, to which Marfa comments: &quot;The heart of another is darkness.&quot; When Boris suddenly appears for a visit, Katerina shrieks. After he leaves, she reveals to her husband and his mother in the thunderstorm that from the first night and every night of his voyage, she went out with Boris. &quot;Well, son! You see what freedom leads to,&quot; says Marfa triumphantly. &quot;I told you so, but you wouldn't heed me. See what you've brought on yourself!&quot; Tihon tells a friend it is not his fault, but his mother's. He still loves her, cannot hurt her, only giving her a few blows now and then at his mother's bidding. Meanwhile, Dukoy orders Boris away to Siberia. Varvara flees the house with Kudriash. Tihon then learns that Katerina has disappeared. By chance, Katerina finds Boris and asks to go with him, but he, being dependent on his uncle's will, says he cannot. Her condition is miserable, her husband's kindness being worse than his blows. They go their separate ways. A bystander notices a woman in the river. As a fearful Tihon heads in that direction, his mother holds him. When Katerina's corpse is carried in, Tihon blames his mother for her death, crying out to her ghost: &quot;It is well with you, Katia, but why am I left to live and suffer!&quot;

==&quot;The forest&quot;==

[[File:Larix_gmelinii_Kochechum.jpg|thumb|Trouble starts when Raissa Gourmyskaia wants to sell her forest. Larix gmelinii forest, Kochechum River, Evenkiyskiy Avtonomnyy Okrug, Russia]]

Time: 1870s. Place: Russia. 

Text at ?

To reduce her expenses, a rich widow, Raissa Gourmyskaia, plans to marry off two of her dependants, Alexis and Axinia, to each other, although neither love the other. To augment her revenues, she intends to sell part of the forest surrounding her estate. A prospective buyer is found: Ivan Vosmibratof, who arrives to negotiate with her along with his son, Piotr, who secretly loves Axinia as much as she loves him. Raissa has already sold one part of the woods to Ivan for 1,500 roubles but cannot find the receipt. Before her properties are discussed, Ivan asks whether she agrees to a marriage between his son and Axinia. She immediately refuses, but agrees to let go another part of the woods for 1,500 roubles. Ivan's assent to this proposition is rather vague. After sounding out Axinia about the proposed marriage with Alexis, Raissa finds her unwilling and defiant. Unexpectedly, Raissa's long-lost nephew, Guennari, arrives, in dire straits as a failing actor, along with a fellow-actor, Arkadi, also fallen on hard times. She finds their visit to be a wearisome load on her finances and hopes to be rid of both. When Ivan returns, Raissa discovers she has lost her receipt again. Nevertheless, she gives him a certificate stating she has received the entire sum of 3,000 roubles. Ivan takes the certificate and to her dismay hands over only 1,800 roubles, the sum he pretends to have agreed to until Guennari arrives and intimidates him into yielding the correct sum. Piotr needs his father's consent to marry Axinia. Ivan agrees provided that they obtain 2,000 roubles as a dowry. Thinking he is rich, Axinia begs Guennari to give her the money. Instead, the actor proposes to turn her into an actress. One day, the housekeeper announces to Raissa that Axinia has left the house. &quot;Perfect!&quot; she exclaims. With her gone, Raissa all the more boldly flirts with Alexis. But when he kisses her and takes her familiarly by the waist, she cries out: &quot;Are you crazy?&quot; Nevertheless, she makes him her steward. No longer wanted, Guennari prepares to leave the house. Raissa gives him 1,000 roubles, only part of the sum she owes him from long ago. As Axinia prepares to follow the actors, Piotr succeeds in reducing his father's demands down to 1,000 roubles, which Guennari yields to so, that he and Axinia can marry. 

==“No fool like a wise one”==

[[File:Stanislavski_and_Kachalov_in_Ostrovsky%27s_Enough_Stupidity_in_Every_Wise_Man_1910.jpg|thumb|Vasili Kachalov pretends subservience to General Krutitski, played respectively by Vasili Kachalov (1875-1948) and Konstantin Stanislavski (1863-1938), at the Moscow Art Theatre, 1910]]

Time: 1860s. Place: Moscow, Russia.

Glafira Glumova points out to her son, Yegor, that Masha Turusina with her 200 hundred thousand rouble dowry, will be difficult to obtain in view of their poverty relative to the prospects of Vasilich Kurchayev, a hussar and nephew of a rich man, Nil Mamayev, also Yegor’s more distant uncle. Yegor sees his chance when Vasilich scribbles a drawing of Nil supplemented by a legend of the liberal satirist, Golutvin, which Yegor pockets up for future use. Another possible stroke of luck arises when Vasilich informs Yegor that Mamayev’s wife, Cleopatra Mamayeva, has taken a fancy to him with a mere glance at a theater. To his mother’s surprise, Yegor already has a trap set for Nil after having falsely advertised apartments to a man who likes to visit them. When Nil arrives as expected, Yegor shows him Vasilich’s satirical drawing, at which he is affronted. More plotting is in store when Yegor offers to pay Manefa, a fortune-teller, in his interest. Vasilich returns, suspecting Yegor as the cause of why his rich uncle now appears angry with him, at which Yegor pretends innocence. Nil’s friend, Krutitsky, is looking for a writer who will support conservative causes. Nil believes he knows the man for him: Yegor Glumov. Meanwhile, Glafira complains to Cleopatra Mamayeva that her son is liable to languish in obscurity, to which the latter says that women should enlist their husbands to help him out. When Glafira mentions how much he admires his uncle and aunt, Cleopatra is enthused. “Let us love him together,” she says. After his mother leaves, Yegor himself shows up, pretending to be shy as her aunt appears so young. She is intrigued and stipulates that a word from her should procure him a situation. To follow up his advantage, Yegor insinuates that he loves someone but is unable to declare who she is, at which his aunt is led to think it might be herself.  She first asks an enterprising man, Gorodulin, whether a position may be obtained for this handsome young man. He answers positively and immediately requests him to write a speech for him. Equally impressed, Nil advises the apparently timid Yegor to flatter his wife more often, to which Yegor pretends to hesitate. Gorodulin returns to Cleopatra to say that in two weeks Yegor will have an appointment. Yegor is elated, Cleopatra anxious to know who his loved one is. “You,” he says falling on his knee. “I forgive you,” she responds while kissing his forehead. Masha Turusina is bored with her present life, requesting more freedom from her superstitious aunt, Sofia, inclined to be choosy as to her choice of husband. They receive the visit of Krutitsky, who speaks favorably of a man he has heard good things about: Yegor Glumov, followed by Gorodulin, also impressed by Yegor, and then Manefa, who, in the pay of Yegor, as if in an inspired trance, pronounces that a good choice of a husband might be ‘Yegor of a foreign shore’. To crown the piece, Nil introduces his nephew, Yegor himself, solemnly kissing Sofia’s hand. Still in pursuit of a conservative treatise, Krutitsky eagerly subscribes to Yegor’s ideas. After learning of Gorodulin’s promise of a post, Krutitsky promises him a better one. After Yegor leaves, Krutitsky informs Cleopatra of Yegor’s intention to marry Masha, which she finds impossible to believe, feeling ill at the thought. She rushes to Yegor’s house and, though he denies loving the heiress, she suspects the worst. She hides in the adjoining room as Golutvin shows up with evidence of some of Yegor’s tricks, requesting 25 roubles to keep quiet. But Yegor refuses. While ushering the tell-tale out, she discovers Yegor’s diary, containing a daily summary of his activities, and takes off with it. When Gorodulin learns of Yegor’s treatise on behalf of Krutitsky, he proposes to sign his name to Yegor’s attack against his own treatise. Meanwhile, Cleopatra encourages Vasilich to keep hoping in regard to Masha, with all the more reason when Sofia receives an envelope containing a satiric article against Yegor accompanied by his hand-written diary. She apologizes to her niece for trying to control her choice of a husband. “My choice has already been made, aunt,” Masha declares as Sofia turns to Vasilich.

=Mikhail Saltykov-Shchedrin=

[[File:Kramskoj - saltykov-schedrin.jpg|thumb|Saltykov-Shchedrin exposed the schemes of legacy hunters. Portrait of the author by Ivan Kramskoi (1837-1887), 1879]]

Mikhail Saltykov-Shchedrin (1826-1889) continued the realist tradition with “Смерть Пазухина” (Pazukhin’s death, 1857).

“Saltykov’s play returns to the ancient Roman theme of legacy-hunting, which has already proven to be fruitful for Ben Jonson. Indeed, in its indignant savagery, Shchedrin’s play has more than a little in common with ‘Volpone’: there is the same division of mankind into knaves and gulls, the same exuberant wielding of odd idioms and dialects, the same sarcastic belief that money makes the world go round and, if it doesn’t, ego does. But where Jonson feels the moral need to submit his villains to poetic justice, Saltykov, more jaundiced, lets the big fish eat the little fish and swim victoriously away…The town’s panorama of vice can range from the Pecksniffian hypocrisy of State Councilor Furnachyov, who finds legal camouflage for his thefts, to Prokofy Pazukhin, whose conversion to a fundamentalist creed cannot withstand the temptations of a rich inheritance, to a variegated assortment of hangers-on and dependents whose only social adhesive is greed” (Senelick, 1997 pp 16-17).

==“Pazukhin’s death”==

[[File:Luzhsky Lobastov.jpg|thumb|Played by Vasily Luzhsky (1869-1931) in the 1916 Moscow Art Theatre production, General Andrei Lobastov intends to take away the Pazukhin family fortune from the son and heir]]

Time: 1857. Place: Fictional city of Krutogorsk, Russia.

Text at ?

Prokofy Pazukhin is frustrated because his rich father, Ivan, has disowned him because he grew a beard and married against his wishes, a second marriage to Vasiliva’s daughter, Mavra. Prokofy requests his father’s friend, General Andrei Lobastov, to help him in his need. General Lobastov informs Prokofy that his father is near death and that he was sent for because of his intention to make up his will. When Andrei arrived, Semyon Furnachyov, a state councilor, and Gavrilo, Prokofy’s son, were already there. But Ivan threw the unsigned will on Semyon’s face, claiming to be able to outlive them all. Andrei promises to help Prokofy provided he agrees to a marriage between Gavrilo and his 31-year old crippled daughter, Lenochka, and that she obtain one third of the Pazukhin fortune. Prokofy agrees but haggles till he gets it down to one fourth. Prokofy’s musings are interrupted by retired second lieutenant Fyodor Zhivnovsky, who contradicts Andrei’s version of his visit to Ivan’s bedside by stating that he himself witnessed the signing of the will. “Part of the estate, says he, goes to my grandson, Gavrilo,” Fyodor announces, “part to my beloved daughter, Nastasya Ivanovna, part to be used to erect cathedrals to God, and to my beloved son, Prokofy Ivanych, l leave my paternal blessing.” Along with her husband, Semyon, Nastasya sympathizes with the troubles of Anna Petrovna, Ivan’s housekeeper and mistress since the age of 15, who, like Prokofy, might receive nothing after her master’s death. With his wife out of hearing, Semyon proposes that Anna obtain a waxen impression of the lock on Ivan’s strongbox. Despite her fears, Semyon takes her agreement for granted and receives the visit of Prokovy, still convinced that the will is unsigned, who proposes that in exchange for 150,000 roubles, Semyon prevent his father from signing it. Semyon refuses and, in front of his own father, reveals Prokovy’s attempt at bribery. “Begone, my good sir,” Semyon sententiously orders, “and remember that virtue is as honorable and praiseworthy as vice is ignoble and indecent.” Andrei succeeds in finding out from the still fearful Anna about the plan to pick Ivan’s strongbox, proposing to divide the spoils between the three of them. Meanwhile, before an infirm Ivan ensconced in his chair, Lenochka announces that Gavrilo appears uninterested in her. Despite Anna’s pleas to shut him out, a beardless Prokofy appears contrite before his father, who accepts the suggestion that his son visit him more often, alongside his wife, provided that she comes at night when no one is around. These pleasant feelings between father and son are disrupted by the arrival of Semyon, who reminds Ivan of Prokofy’s attempt at bribery, so that the irate father flings his cane at his son and orders him out. Late at night, Anna sends word to Semyon and Andrei that her master is dying, but Ivan’s mentor, Finagei Gayev, learns of the message and ushers in Prokovy, who hides in a store-room and overhears her tell Andrei that her master is dead and of their plan to steal the strongbox. Prokovy appears alongside Fyodor and Trofim and watches Andrei enter the dead man’s room. By peeking through the key-hole, he observes Andrei stuff his pockets with the strongbox’ contents. When Andrei comes back out, Prokovy orders Fyodor and Trofim to frisk the thief’s bulging pockets and then calls for Mavra and Nastasya as witnesses to his shame. He then requests the thief to sign a paper admitting his deed.

=Aleksey Pisemski=

[[File:Перов Писемский.jpg|thumb|Alexsey Pisemski exposed troubles that arise when a woman commits adultery with her master. Portrait of the author by Vasily Perov (1833-1882), 1862]]

In addition to Tolstoy’s peasant drama laden with crime, Alexsey Pisemski (1821-1881) contributed an earlier one fraught with similar intensity: &quot;Горькая судьбина&quot; (A bitter fate, 1859).

&quot;A bitter fate&quot; &quot;is a genuine tragedy at supreme logical unity which is the great characteristic of the plays of Racine. The subject, like those of Racine, is simple, almost geometrical. A squire, a weakling of the Hamlet, idealist type, has seduced, in the absence of her husband, the wife of one of his serfs. The husband is a strong character of the type that occurs in Pisemsky’s and Leskov’s popular stories. Though a serf, he is a prosperous tradesman and has made money in Petersburg. He returns home (this is the initial situation) and by degrees discovers the guilt of his wife and reacts accordingly. The squire is the master of the husband, while the husband is the master of his wife- so it is a conflict between, on the one hand, the squire’s rights as a serf owner and the dignity of his serf; on the other, between the rights of free love (an essential point is that the squire and the serf’s wife do love each other) and the rights of the master of the house over his wife. The double conflict is unfolded with supreme mastery, and the spectator’s sympathy is held in balance between the rights of human dignity and the rights of free love. The tragedy ends in the husband’s killing the lovers’ child and then (a trait particularly praised by Russian critics but suggested to Pisemsky by the actor Martynov) delivering himself into the hand of the law&quot; (Mirsky, 1949 pp 240-241).

“Of the three protagonists of the play, Anany, Lizaveta, and Cheglov, it is Anany who occupies the central place. He is a truly tragic figure and, like so many of Shakespeare's characters, he carries the seeds of his tragedy within himself. If Othello's tragedy springs from his jealousy and that of Richard III or Macbeth from unbridled ambition, Anany's tragedy is the result of excessive pride. It is not by chance that a critic compared him precisely with a memorable character from Shakespeare and called him ‘King Lear of the peasant kingdom’...Anany is observed through the eyes of other characters placed against different backgrounds. Thus, he is discussed by his mother-in-law and her friend who sympathize with him, by his wife who bitterly resents him, by the bailiff who holds a grudge against him, and finally by police officials to whom he is just another criminal...The scene where the husband and lover, serf and master, face other is one of the most striking in the play. The result of this encounter is a complete misunderstanding, which eventually leads to the tragic climax. Cheglov unwittingly does and say wrong things, for Anany, by virtue of his very character, cannot appreciate Cheglov's good intentions. Cheglov’s assurances that Lizaveta never loved Anany, which he makes in the presence of the bailiff, only aggravate Anany's annoyance with his wife, for it is loyalty and obedience and not love which in Anany’s moral code is the primary factors of marriage...As in classical tragedy, in this play there is a presentiment of doom from the very early scenes, which is intensified by the absence of sub-plots or comic interludes. Nothing is irrelevant to the main course of the story, every remark is linked with a further remark or resolved finally in some action. It is significant that throughout the drama, its central figure, Anany, is either on the stage himself, or the subject of conversation, and always present in the mind of the reader or spectator” (Jenkins, 1958 pp 82-85).

==“A bitter fate”==

[[File:Strepetova_as_Elizabeth_by_Repin.jpg|thumb|As played by Pelageya Antipevna Strepetova (1850-1903) depicted in a 1881 painting by Ilya Repin (1844–1930), Lizaveta is overwhelmed with troubles]]‎

Time: 1850s. Place: Sokovina, Russia.

Text at ?

While Anany Yakovlich has been away as a merchant for business purposes to St Petersburg, his wife, Lizaveta, entered into an adulterous relation with their master, Squire Cheglov, and has borne him a baby. As Anany returns to his home along with an old laborer, Uncle Nikon, the two argue over technological discoveries and who is the most valuable, a merchant or a laborer, until the latter, angry at being contradicted, insinuates that his companion is a cuckold. When Anany confronts his wife with this rumor, she bends her head. “There is no reply I can make,” she says. ‘”You can do to me whatever you please.” But then she proffers some excuses. “I didn’t want to do it, but then they gave me all sorts of orders and commands and I couldn’t disobey,” she says. But Anany dismisses these. To avoid disgrace, he opts to pretend that nothing has happened and that the baby is his. On leaning of the cuckold’s return, Cheglov is tormented about what will happen to Lizaveta and his baby, leading him to drink excessive amounts of vodka. In contrast, his friend, Sergey Zolotilov, considers that there is little cause to worry, suggesting that he raise the baby in his house. “I am also convinced,” Sergey adds, “that this woman encourages you in this unfortunate weakness, because it is easier to fish in troubled waters.” The bailiff, Kalistrat, brings her over with the news that Anany behaves awfully. Indeed, she enters tentatively to announce that Anany stares at her like a wild beast, “as if he were trying to kill me with his look,” she adds. As she scampers off, the bailiff leads her husband in. Cheglov offers Anany money, but he refuses. He wants to bring his wife and baby to St Petersburg, but Cheglov refuses. Cheglov next proposes a duel, but Anany declines that solution as well. “Our blood is worthless next to a gentleman’s,” he declares. The squire can only command Kalistrat to watch over Lizaveta day and night.  At Anany’s house, Kalistrat leads a group of peasants and a deputy to protect Lizaveta and to judge the husband, because is unable to control him. The peasants are bewildered, want to be left alone, and wish her to the devil. “My axe is very sharp,” Anany warns. “Bind him with ropes for me,” Kalistrat commands, “and set the wife free.” Anany further warns them that he will punish his wife before their very faces. “You’ve ruled over me long enough,” Lizaveta declares. “I was carried off in the bridal sledge almost bound. I’d rather have thrown away my innocence to a bandit in the forest than to him.” Admitting she is the squire’s mistress, she collects her clothes, aiming to be taken to him. “I won’t give you the baby,” Anany states. When she advances to take the baby away, Anany splits his skull and escapes as the peasants run after him. As a result, Kalistrat is interrogated by the district police chief and a lawyer. In an attempt to prevent the squire knowing about the escape, the bailiff bribes the two men with 150 roubles. They try to interrogate Lizaveta’s mother, Matrena, but soon let her go as she babbles in fright. The two men are joined by Shpringel, the government official, and interrogate Uncle Nikon, but he is drunkenly incoherent. They receive news that Anany has been captured. Sergey tries to prevent the legal procedures, but they urge Anany forward. However, he gives little information, keeping silent as to who cuckolded him as a throng of peasants enter, including the sobbing Lizaveta. Nikon avers that she committed adultery with the squire, but Anany keep silent despite Shpringel’s protest that he may receive a lighter sentence in that case. Shpringel rises to see the governor, convinced of the existence of collusion among both officials and peasants. Still seeking to protect Cheglov, Sergey intends to counteract this move. “You can’t give over a noblemen, bound hand and foot, to any young puppy,” he decrees.   
           

{{BookCat}}</text>
      <sha1>7e8u708m7xywf35txvztopqodjlpm00</sha1>
    </revision>
  </page>
  <page>
    <title>User:Jimmy Pitt</title>
    <ns>2</ns>
    <id>245219</id>
    <revision>
      <id>4668993</id>
      <parentid>1996443</parentid>
      <timestamp>2026-09-05T19:05:20Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4668993</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="441" sha1="qb79wdonay0efa7wk78amjz3472rlzu" xml:space="preserve">&lt;div style=&quot;font-size:85%; vertical-align:top; background:#E0E8EF;{{Text default color}}; border:1px solid #E0E8EF; {{{style|margin-bottom:4pt; padding:2pt; margin-top:4pt; padding-top:2pt}}}; text-align:center;&quot;&gt;
&lt;div style=&quot;padding:0 .3em 0;&quot;&gt;Unified login: '''Jimmy Pitt''' is the [[m:Help:Unified login|unique login]] of this user for all public [[wmf:Our projects|Wikimedia projects]].
&lt;/div&gt;
&lt;/div&gt;

{{userpage}}
{{Babel|en|es-1|fr-1}}</text>
      <sha1>qb79wdonay0efa7wk78amjz3472rlzu</sha1>
    </revision>
  </page>
  <page>
    <title>User:Wd930/EnergyHampsterLaboratory/Periodic table</title>
    <ns>2</ns>
    <id>246039</id>
    <revision>
      <id>4669018</id>
      <parentid>2007605</parentid>
      <timestamp>2026-09-05T19:33:24Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669018</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="10963" sha1="9k1waborglqlrq06u5eze25dhflyxhw" xml:space="preserve">&lt;onlyinclude&gt;{| border=&quot;0&quot; cellpadding=&quot;0&quot; cellspacing=&quot;1&quot; style=&quot;width:80%; background:#f7f7e9;{{Text default color}}; {{{1|}}} border:1px solid #a9a9a9; margin-left: auto; margin-right: auto;&quot;
|- style=&quot;background-color:#e9e955;{{Text default color}};&quot;
! scope=&quot;col&quot; style=&quot;width: 1.0%;&quot; | [[Periodic table group|Group]]&amp;nbsp;#
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Alkali metal|1]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Alkaline earth metal|2]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Group 3 element|3]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Group 4 element|4]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Group 5 element|5]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Group 6 element|6]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Group 7 element|7]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Group 8 element|8]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Group 9 element|9]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Group 10 element|10]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Group 11 element|11]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Group 12 element|12]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Boron group|13]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Carbon group|14]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Nitrogen group|15]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Chalcogen|16]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Halogen|17]]
! scope=&quot;col&quot; style=&quot;width: 5.5%;&quot; | [[Noble gas|18]]
|-
! scope=&quot;col&quot; | [[Periodic table period|Period]]
| colspan=&quot;18&quot; | &lt;br /&gt;
|-
! scope=&quot;row&quot; | [[Period 1 element|1]]
| {{element cell| 1|hydrogen  |H |1.00794(7)    |Gas  |Nonmetals|Primordial}}
| colspan=&quot;16&quot; | &lt;br /&gt;
| {{element cell| 2|helium    |He|4.002602(2)   |Gas  |Noble gases|Primordial}}
|-
! scope=&quot;row&quot; | [[Period 2 element|2]]
| {{element cell| 3|lithium   |Li|6.941(2)      |Solid|Alkali metals|Primordial}}
| {{element cell| 4|beryllium |Be|9.012182(3)   |Solid|Alkaline earth metals|Primordial}}
| colspan=&quot;10&quot; | &lt;br /&gt;
| {{element cell| 5|boron     |B |10.811(7)     |Solid|Metalloids|Primordial}}
| {{element cell| 6|carbon    |C |12.0107(8)    |Solid|Nonmetals|Primordial}}
| {{element cell| 7|nitrogen  |N |14.00674(7)   |Gas  |Nonmetals|Primordial}}
| {{element cell| 8|oxygen    |O |15.9994(3)    |Gas  |Nonmetals|Primordial}}
| {{element cell| 9|fluorine  |F |18.9984032(5) |Gas  |Halogens|Primordial}}
| {{element cell|10|neon      |Ne|20.1797(6)    |Gas  |Noble gases|Primordial}}
|-
! scope=&quot;row&quot; | [[Period 3 element|3]]
| {{element cell|11|sodium    |Na|22.98976928(2)|Solid|Alkali metals|Primordial}}
| {{element cell|12|magnesium |Mg|24.3050(6)    |Solid|Alkaline earth metals|Primordial}}
| colspan=&quot;10&quot; | &lt;br /&gt;
| {{element cell|13|aluminium |Al|26.9815386(8) |Solid|Poor metals|Primordial}}
| {{element cell|14|silicon   |Si|28.0855(3)    |Solid|Metalloids|Primordial}}
| {{element cell|15|phosphorus|P |30.973762(2)  |Solid|Nonmetals|Primordial}}
| {{element cell|16|sulfur    |S |32.066(6)     |Solid|Nonmetals|Primordial}}
| {{element cell|17|chlorine  |Cl|35.4527(9)    |Gas  |Halogens|Primordial}}
| {{element cell|18|argon     |Ar|39.948(1)     |Gas  |Noble gases|Primordial}}
|-
! scope=&quot;row&quot; | [[Period 4 element|4]]
| {{element cell|19|potassium |K |39.0983(1)    |Solid|Alkali metals|Primordial}}
| {{element cell|20|calcium   |Ca|40.078(4)     |Solid|Alkaline earth metals|Primordial}}
| {{element cell|21|scandium  |Sc|44.955912(6)  |Solid|Transition metals|Primordial}}
| {{element cell|22|titanium  |Ti|47.867(1)     |Solid|Transition metals|Primordial}}
| {{element cell|23|vanadium  |V |50.9415(1)    |Solid|Transition metals|Primordial}}
| {{element cell|24|chromium  |Cr|51.9961(6)    |Solid|Transition metals|Primordial}}
| {{element cell|25|manganese |Mn|54.938045(5)  |Solid|Transition metals|Primordial}}
| {{element cell|26|iron      |Fe|55.845(2)     |Solid|Transition metals|Primordial}}
| {{element cell|27|cobalt    |Co|58.933195(5)  |Solid|Transition metals|Primordial}}
| {{element cell|28|nickel    |Ni|58.6934(2)    |Solid|Transition metals|Primordial}}
| {{element cell|29|copper    |Cu|63.546(3)     |Solid|Transition metals|Primordial}}
| {{element cell|30|zinc      |Zn|65.39(2)      |Solid|Transition metals|Primordial}}
| {{element cell|31|gallium   |Ga|69.723(1)     |Solid|Poor metals|Primordial}}
| {{element cell|32|germanium |Ge|72.61(2)      |Solid|Metalloids|Primordial}}
| {{element cell|33|arsenic   |As|74.92160(2)   |Solid|Metalloids|Primordial}}
| {{element cell|34|selenium  |Se|78.96(3)      |Solid|Nonmetals|Primordial}}
| {{element cell|35|bromine   |Br|79.904(1)     |Liquid|Halogens|Primordial}}
| {{element cell|36|krypton   |Kr|83.80(1)      |Gas  |Noble gases|Primordial}}
|-
! scope=&quot;row&quot; | [[Period 5 element|5]]
| {{element cell|37|rubidium  |Rb|85.4678(3)    |Solid|Alkali metals|Primordial}}
| {{element cell|38|strontium |Sr|87.62(1)      |Solid|Alkaline earth metals|Primordial}}
| {{element cell|39|yttrium   |Y |88.90585(2)   |Solid|Transition metals|Primordial}}
| {{element cell|40|zirconium |Zr|91.224(2)     |Solid|Transition metals|Primordial}}
| {{element cell|41|niobium   |Nb|92.90638(2)   |Solid|Transition metals|Primordial}}
| {{element cell|42|molybdenum|Mo|95.94(1)      |Solid|Transition metals|Primordial}}
| {{element cell|43|technetium|Tc|[97.9072]     |Solid|Transition metals|Natural radio}}
| {{element cell|44|ruthenium |Ru|101.07(2)     |Solid|Transition metals|Primordial}}
| {{element cell|45|rhodium   |Rh|102.90550(2)  |Solid|Transition metals|Primordial}}
| {{element cell|46|palladium |Pd|106.42(1)     |Solid|Transition metals|Primordial}}
| {{element cell|47|silver    |Ag|107.8682(2)   |Solid|Transition metals|Primordial}}
| {{element cell|48|cadmium   |Cd|112.411(8)    |Solid|Transition metals|Primordial}}
| {{element cell|49|indium    |In|114.818(3)    |Solid|Poor metals|Primordial}}
| {{element cell|50|tin       |Sn|118.710(7)    |Solid|Poor metals|Primordial}}
| {{element cell|51|antimony  |Sb|121.760(1)    |Solid|Metalloids|Primordial}}
| {{element cell|52|tellurium |Te|127.60(3)     |Solid|Metalloids|Primordial}}
| {{element cell|53|iodine    |I |126.90447(3)  |Solid|Halogens|Primordial}}
| {{element cell|54|xenon     |Xe|131.29(2)     |Gas  |Noble gases|Primordial}}
|-
! scope=&quot;row&quot; | [[Period 6 element|6]]
| {{element cell|55|caesium   |Cs|132.9054519(2)|Solid|Alkali metals|Primordial}}
| {{element cell|56|barium    |Ba|137.327(7)    |Solid|Alkaline earth metals|Primordial}}
| {{element cell|*|lanthanides|  |              |Solid|Lanthanoids|Undiscovered}}
| {{element cell|72|hafnium   |Hf|178.49(2)     |Solid|Transition metals|Primordial}}
| {{element cell|73|tantalum  |Ta|180.94788(2)  |Solid|Transition metals|Primordial}}
| {{element cell|74|tungsten  |W |183.84(1)     |Solid|Transition metals|Primordial}}
| {{element cell|75|rhenium   |Re|186.207(1)    |Solid|Transition metals|Primordial}}
| {{element cell|76|osmium    |Os|190.23(3)     |Solid|Transition metals|Primordial}}
| {{element cell|77|iridium   |Ir|192.217(3)    |Solid|Transition metals|Primordial}}
| {{element cell|78|platinum  |Pt|195.084(9)    |Solid|Transition metals|Primordial}}
| {{element cell|79|gold      |Au|196.966569(4) |Solid|Transition metals|Primordial}}
| {{element cell|80|mercury   |Hg|200.59(2)     |Liquid|Transition metals|Primordial|mercury (element)}}
| {{element cell|81|thallium  |Tl|204.3833(2)   |Solid|Poor metals|Primordial}}
| {{element cell|82|lead      |Pb|207.2(1)      |Solid|Poor metals|Primordial}}
| {{element cell|83|bismuth   |Bi|208.98040(1)  |Solid|Poor metals|Primordial}}
| {{element cell|84|polonium  |Po|[208.9824]    |Solid|Metalloids|Natural radio}}
| {{element cell|85|astatine  |At|[209.9871]    |Solid|Halogens|Natural radio}}
| {{element cell|86|radon     |Rn|[222.0176]    |Gas  |Noble gases|Natural radio}}
|-
! scope=&quot;row&quot; | [[Period 7 element|7]]
| {{element cell|87|francium      |Fr|[223.0197] |Solid|Alkali metals|Natural radio}}
| {{element cell|88|radium        |Ra|[226.0254] |Solid|Alkaline earth metals|Natural radio}}
| {{element cell|**|actinides     |  |           |Solid|Actinoids|Undiscovered}}
| {{element cell|104|rutherfordium|Rf|[264]      |UnknownPhase|Transition metals|Synthetic}}
| {{element cell|105|dubnium      |Db|[265]      |UnknownPhase|Transition metals|Synthetic}}
| {{element cell|106|seaborgium   |Sg|[266]      |UnknownPhase|Transition metals|Synthetic}}
|-
| colspan=&quot;19&quot; | &lt;br /&gt;
|-
! scope=&quot;row&quot; colspan=&quot;3&quot; style=&quot;text-align: right; padding-right: 1em;&quot; | * [[Lanthanoid]]s
| {{element cell|57|lanthanum   |La|138.90547(7)|Solid|Lanthanoids|Primordial}}
| {{element cell|58|cerium      |Ce|140.116(1)  |Solid|Lanthanoids|Primordial}}
| {{element cell|59|praseodymium|Pr|140.90765(2)|Solid|Lanthanoids|Primordial}}
| {{element cell|60|neodymium   |Nd|144.242(3)  |Solid|Lanthanoids|Primordial}}
| {{element cell|61|promethium  |Pm|[144.9127]  |Solid|Lanthanoids|Natural radio}}
| {{element cell|62|samarium    |Sm|150.36(2)   |Solid|Lanthanoids|Primordial}}
| {{element cell|63|europium    |Eu|151.964(1)  |Solid|Lanthanoids|Primordial}}
| {{element cell|64|gadolinium  |Gd|157.25(3)   |Solid|Lanthanoids|Primordial}}
| {{element cell|65|terbium     |Tb|158.92535(2)|Solid|Lanthanoids|Primordial}}
| {{element cell|66|dysprosium  |Dy|162.500(1)  |Solid|Lanthanoids|Primordial}}
| {{element cell|67|holmium     |Ho|164.93032(2)|Solid|Lanthanoids|Primordial}}
| {{element cell|68|erbium      |Er|167.259(3)  |Solid|Lanthanoids|Primordial}}
| {{element cell|69|thulium     |Tm|168.93421(2)|Solid|Lanthanoids|Primordial}}
| {{element cell|70|ytterbium   |Yb|173.04(3)   |Solid|Lanthanoids|Primordial}}
| {{element cell|71|lutetium    |Lu|174.967(1)  |Solid|Lanthanoids|Primordial}}
| &lt;br /&gt;
|-
! scope=&quot;row&quot; colspan=&quot;3&quot; style=&quot;text-align: right; padding-right: 1em;&quot; | ** [[Actinoid]]s
| {{element cell|89|actinium    |Ac|227.02700   |Solid|Actinoids|Natural radio}}
| {{element cell|90|thorium     |Th|232.03806(2)|Solid|Actinoids|Primordial}}
| {{element cell|91|protactinium|Pa|231.03588(2)|Solid|Actinoids|Natural radio}}
| {{element cell|92|uranium     |U |238.02891(3)|Solid|Actinoids|Primordial}}
| {{element cell|93|neptunium   |Np|[237.0482]  |Solid|Actinoids|Natural radio}}
| {{element cell|94|plutonium   |Pu|[244.0642]  |Solid|Actinoids|Primordial}}
| {{element cell|95|americium   |Am|[243.0614]  |Solid|Actinoids|Synthetic}}
| {{element cell|96|curium      |Cm|[242.1562]  |Solid|Actinoids|Synthetic}}
| {{element cell|97|berkelium   |Bk|[248.4595]  |Solid|Actinoids|Synthetic}}
| {{element cell|98|californium |Cf|[248.8953]  |Solid|Actinoids|Synthetic}}
| {{element cell|99|einsteinium |Es|[252.9999]  |Solid|Actinoids|Synthetic}}
| {{element cell|100|fermium    |Fm|[253.7698]  |Solid|Actinoids|Synthetic}}
| {{element cell|101|mendelevium|Md|[258.0984]  |Solid|Actinoids|Synthetic}}
| {{element cell|102|nobelium   |No|[259.1011]  |Solid|Actinoids|Synthetic}}
| {{element cell|103|lawrencium |Lr|[263.0353]  |Solid|Actinoids|Synthetic}}
| &lt;br /&gt;
|}</text>
      <sha1>9k1waborglqlrq06u5eze25dhflyxhw</sha1>
    </revision>
  </page>
  <page>
    <title>User:German Lessons/Level I/Essen</title>
    <ns>2</ns>
    <id>247930</id>
    <revision>
      <id>4668995</id>
      <parentid>4644003</parentid>
      <timestamp>2026-09-05T19:08:38Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668995</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31259" sha1="reiu9v7trv5jsofxbyt1ihrs1b5fril" xml:space="preserve">&lt;br clear=&quot;all&quot;&gt;
{|style=&quot;magin:0 auto;&quot;
 | __TOC__
|}

&lt;big&gt;&lt;big&gt;&lt;big&gt;Lesson I.6: Essen&lt;/big&gt;&lt;/big&gt;&lt;/big&gt;
----

==Dialogue==

{| {{German table|Dialogue|I'm hungry!|Ich habe Hunger!|0|2}}
!Franz
|Hallo, Greta! Wie geht's?
|-
!Greta
|Sehr gut. Ich bin hungrig.
|-
!Franz
|Ich auch. Möchtest du etwas essen?
|-
!Greta
|Ja!
|-
!||''In der Gaststätte''
|-
!Greta
|Ich möchte Salat, Brot und Wasser.
|-
!Franz
|Hast du jetzt keinen Hunger?
|-
!Greta
|Doch, ich habe großen Hunger. Was bekommst du?
|-
!Franz
|Ich bekomme ein Stück Apfelstrudel und einen Eisbecher.
|-
!Greta
|Warum das? Du sollst eine Bratwurst nehmen.
|-
!Franz
|Nein, ich bin zufrieden. Ich habe keinen großen Hunger.
|-
!Greta
|Ach so, dann ist das genug.
|-
!||''Nach zwanzig Minuten''
|-
!Greta
|Diese Gaststätte ist schrecklich! Ich möchte etwas zu essen!
|-
!Franz
|Wir gehen!
|}

==Food!==
{| {{German table|Vocabulary|Food|die Nahrungsmittel (pl.)|0|4}}
! colspan=2 | die Früchte (das Obst) - fruits
! colspan=2 | das Gemüse - vegetables
|-
|die Banane||banana||die Möhre, die Karotte||carrot
|-
|die Kirsche||cherry||der Spinat||spinach
|-
|die Zitrone||lemon||die Zwiebel||onion
|-
|die Erdbeere||strawberry||die Erbsen||peas
|-
|die Orange||orange||die Kartoffel||potato
|-
|der Apfel||apple||die Tomate||tomato
|-
|die Traube||grape||der Spargel||asparagus
|-
|die Grapefruit||grapefruit||die Bohnen|| beans
|-
!colspan=2 | das Fleisch - meat
!colspan=2 | die Meeresfrüchte - shellfish, seafood
|-
|das Lammfleisch||lamb||die Kammmuschel||scallop
|-
|der Truthahn||turkey||die Krabbe||crab
|-
|der Schinken||ham||die Garnele||shrimp  
|-
|das Schweinefleisch||pork
!colspan=2 | der Fisch - fish
|-
|das Hähnchen||chicken||die Sardellen||anchovies
|-
|das Rindfleisch||beef||der Lachs||salmon
|-
|die Wurst||sausage||der Aal||eel
|-
! colspan=2 | die Milchprodukte - dairy products
! colspan=2 | Other Foods
|-
|die Butter||butter||die Suppe||soup
|-
|der Käse||cheese||die Fritten||French fries
|-
|die Milch||milk||die Pizza||pizza
|-
|der Joghurt||yogurt||der Hamburger||hamburger
|-
! colspan=2 | die Nachspeise - dessert
|der Senf||mustard
|-
|das Bonbon||candy||das Brot||bread
|-
|die Schokolade||chocolate||die Butter||butter
|-
|die Torte||tart||der Salat||salad
|-
|der Kuchen||cake||der Pfeffer||pepper
|-
|der Apfelstrudel||apple strudel||der Reis||rice
|-
|der (Apfel)Kuchen||(apple) pie||das Salz||salt
|-
|das Eis||ice cream||der Zucker||sugar
|-
|der Eisbecher||bowl of ice cream||die Konfitüre||jam
|}
&lt;big&gt;[[/Problems#Food!|Section Problems]] &gt;&gt;&lt;/big&gt;

==&lt;span style=&quot;color: green;&quot;&gt;Accusative Case&lt;/span&gt;==

As you know from the [[../Introduction|introduction]], in German, there are four cases. Three are used often. The first, &lt;span style=&quot;color: blue;&quot;&gt;'''Nominative Case'''&lt;/span&gt;, you learned in [[../Wie heißt du?#Nominative Case|Lesson 1]]. It covers the [[w:Subject (grammar)|subject]], and the predicate noun (in &quot;He is (noun).&quot;, (noun) is the predicate noun). The second, the &lt;span style=&quot;color: green;&quot;&gt;'''Accusative Case'''&lt;/span&gt;, you will learn now. It covers the [[w:Direct object|direct object]] and the [[w:Preposition|object of several prepositions]]. The third, the &lt;span style=&quot;color: red&quot;&gt;'''Dative Case'''&lt;/span&gt; will be taught later on. It covers the [[w:Indirect object|indirect object]] and the object of many other prepositions. 

The object of a sentence will be in accusative case.  In, &quot;You hurt me.&quot;, 'me' would be accusative.

Note: The &lt;span style=&quot;color: green;&quot;&gt;'''Accusative Case'''&lt;/span&gt; and &lt;span style=&quot;color: red&quot;&gt;'''Dative Case'''&lt;/span&gt; are identical in English; that's why German has one case extra.

===Articles===
{| border=&quot;1&quot; style=&quot;background-color: #99FF99;{{Text default color}}; width:50%&quot;
|- style=&quot;text-align:center;&quot;
|
 || &lt;u&gt;Masculine&lt;/u&gt; || &lt;u&gt;Feminine&lt;/u&gt;
| &lt;u&gt;Neuter&lt;/u&gt; || &lt;u&gt;Plural&lt;/u&gt;
|- style=&quot;text-align:center;&quot;
| Definite Article || '''den''' || die
| das || die
|- style=&quot;text-align:center;&quot;
| Indefinite Article || '''einen''' || eine
| ein || -eine*
|}
&lt;small&gt;'''* The indefinite article for plurals is non-existent. However related words, such as possessives and the kein- words that you will learn later this lesson, will end in ''eine'' for plurals.'''&lt;/small&gt;

In the articles, the memory hook for accusative case is &quot;Der goes to den (pronounced &quot;dane&quot; {{audio|De-den.ogg|audio}}) and the rest stays the same.&quot; The masculine indefinite article goes to ''einen'', and everything else stays the same there. Therefore above, ''der'' Hamburger goes to ''den'' Hamburger and ''ein'' Hamburger goes to ''einen'' Hamburger when the hamburger is the direct object, such as in &quot;Er hat einen Hamburger.&quot; (&quot;He has a hamburger.&quot;)

If you are getting confused, it's fine. This topic is one of the hardest for English speakers to grasp. Here are some solutions:

To find out the case of something, first find the verb. The verb rules the sentence. Everything revolves around it. Next you find the subject of the sentence. The subject is the thing/person that is ''doing'' the verb. '''The subject is always in the &lt;span style=&quot;color: blue;&quot;&gt;Nominative Case&lt;/span&gt;, so it takes on the der, die, das, die, or ein, eine, ein.''' 

Now you look back at the verb. If it is a being verb (am, are, is, etc.), the next noun after the verb is the '''predicate noun'''. An easy way to figure this out is to write an equation. If the verb can be replaced with an equals sign (=), then the following noun is a predicate noun. If it can't be replaced by an equals sign, refer to the next paragraph. '''The predicate noun is also always in the &lt;span style=&quot;color: blue;&quot;&gt;Nominative Case&lt;/span&gt;, so the same rules apply to it.'''

 &lt;span style=&quot;color: blue;&quot;&gt;Ich&lt;/span&gt; bin &lt;span style=&quot;color: blue;&quot;&gt;'''ein''' Junge&lt;/span&gt;.
 &lt;span style=&quot;color: blue;&quot;&gt;Sie&lt;/span&gt; ist &lt;span style=&quot;color: blue;&quot;&gt;'''eine''' Frau&lt;/span&gt;.

If the verb of the sentence is an action verb (playing, throwing, making, eating), find what the subject is doing the verb to. For example, if the verb is &quot;makes&quot; (macht), you look for what is being made. That is the direct object. '''The direct object is always in the &lt;span style=&quot;color: green;&quot;&gt;Accusative Case&lt;/span&gt;, so it takes on the den, die, das, die, or einen, eine, ein.'''

 &lt;span style=&quot;color: blue;&quot;&gt;Sie&lt;/span&gt; haben &lt;span style=&quot;color: green;&quot;&gt;'''den''' Cheeseburger&lt;/span&gt;.
 Habt &lt;span style=&quot;color: blue;&quot;&gt;ihr&lt;/span&gt; &lt;span style=&quot;color: green;&quot;&gt;'''einen''' Salat&lt;/span&gt;?

The indefinite articles, when you just look at their endings, select e, -, e for nominative case, and en, e, -, e for accusative.

Remember, between nominative and accusative, the only third-person change is in the masculine form.

&lt;big&gt;[[/Problems#Articles|Section Problems]] &gt;&gt;&lt;/big&gt;

===Pronouns===

The pronouns experience a much bigger change than the articles. This is also true in English, as the articles (a, an, the) do not change ever, but ''I'' goes to ''me'', ''we'' goes to ''us'', etc. 

Not everything is the same, though. While ''me'' is ''mich'' and ''us'' is ''uns'', the second and third persons undergo different changes. In third person, as in the articles, the only change is in masculine singular. Following the &quot;der goes to den&quot; rule, ''er'' goes to ''ihn'' when in the accusative case. 

The second person in English never changes. In German, ''du'' goes to ''dich'' and ''ihr'' goes to ''euch''. ''Sie'', the formal version of either, stays the same. Remember, ''Sie'' (2nd person formal) and ''sie'' (3rd person plural) only differ in their meanings and the fact that the former is capitalized and the latter is not. This stays true throughout German grammar.

Here is a tabular representation of the above.

{| border=&quot;1&quot; style=&quot;background-color: #99FF99;{{Text default color}}; width:50%;&quot;
|- style=&quot;text-align:center;&quot;
| Person || colspan=&quot;2&quot; | '''Singular'''
|
| colspan=&quot;2&quot; | '''Plural'''
|- style=&quot;text-align:center;&quot;
|
 || &lt;u&gt;English&lt;/u&gt; || &lt;u&gt;German&lt;/u&gt; ||
 || &lt;u&gt;English&lt;/u&gt;
| &lt;u&gt;German&lt;/u&gt;
|- style=&quot;text-align:center;&quot;
| 1st || me || ''mich'' ||
 || us
| ''uns''
|- style=&quot;text-align:center;&quot;
| 2nd || you || ''dich'' ||
 || you (all)
| ''euch''
|- style=&quot;text-align:center;&quot;
| 3rd || him, her, it || ''ihn, sie, es''
|
 || them || ''sie''
|}
&lt;big&gt;[[/Problems#Pronouns|Section Problems]] &gt;&gt;&lt;/big&gt;

===Antecedents===

Note: ''This is just a quick lesson in English grammar applied into German. If you already know all about antecedents in English, skip the first paragraph.''

When using a pronoun, you have to know what it is for it to work. There are some rare exceptions, such as in mysteries or drama, but otherwise this is always true. Sometimes in dialogue this is taken care of by pointing or making some other gesture, but most of the time, the pronoun modifies something already mentioned. '''The object/person mentioned earlier that turns into a pronoun later is called the antecedent.''' 

In German this is very useful. You can't simply say 'it' anymore. Many food words are masculine and feminine, and when you turn them into pronouns, they turn into 'he', 'she', 'him', and 'her', not always 'it'. For example, the sentence &quot;The cheeseburger tastes good. It's very crunchy.&quot; turns into &quot;The cheeseburger tastes good. ''He's'' very crunchy.&quot; Note: You will learn how to say this in German later in this lesson.

Why is it &quot;he&quot;? This is where the antecedent comes in. Because there are foods that are masculine and feminine in German, you can't assume the 'es'. You have to look back at the previous sentence, at the antecedent, ''der Cheeseburger''. &quot;Der Cheeseburger&quot; is replaced by ''er'' (since it is the subject, and therefore in Nominative Case). Therefore, all you need to know are these connections: der/den-er/ihn, die-sie, das-es, die-sie.

&lt;big&gt;[[/Problems#Antecedents|Section Problems]] &gt;&gt;&lt;/big&gt;

==Food-Related Verbs==

* ''essen (I)''  - to eat, to be eating, to do eat
* ''trinken'' - to drink, to be drinking, to do drink
* ''bekommen'' - to get/receive, to be getting/receiving, to do get/receive
* ''möchten (M)'' - would like
* ''wollen (M)'' - to want, to be wanting, to do want

Of these five verbs, only trinken and bekommen are regular. Essen is ''irregular'' (that's what the &quot;I&quot; means). Do you remember from the last lesson 'lesen' and 'sehen'? In both of them, the first 'e' changed to 'ie' in the du- and er/sie/es-forms. Well ''essen'' experiences the same change, except that it changes to 'i', not 'ie'. Also, it acts the same as 'lesen' in the du-form: You don't have three s's in a row.

{| border=&quot;1&quot; style=&quot;background-color: #FFFF66;{{Text default color}}; width:50%&quot;
|- style=&quot;text-align:center;&quot;
| &lt;u&gt;Person&lt;/u&gt; || colspan=&quot;2&quot; | &lt;u&gt;Singular&lt;/u&gt;
|
| colspan=&quot;2&quot; | &lt;u&gt;Plural&lt;/u&gt;
|- style=&quot;text-align:center;&quot;
| '''1st''' || ich || ''esse'' ||
 || wir
| ''essen''
|- style=&quot;text-align:center;&quot;
| '''2nd''' || du || ''isst'' ||
 || ihr
| ''esst''
|- style=&quot;text-align:center;&quot;
| '''3rd''' || er/sie/es || ''isst''
|
 || sie || ''essen''
|}


''Isst'' sounds and looks a lot like ''ist''. The minute difference happens to be in the way you pronounce the ''s''. When you mean ''eats'' it is sometimes an overstressed hissing (i.e. extremely sharp) sound. In normal life Germans, too, can only tell which verb is meant from knowing the context. 

Just like in last lesson, where you could say, ''&quot;Ich spiele gerne Fußball.&quot;'', you can also extend it to food. &quot;I like to eat cheeseburgers.&quot; is translated as ''&quot;Ich esse gerne Cheeseburger.&quot;'' 

Before [[w:German spelling reform of 1996|1996]], the usage of ''ißt'' and ''eßt'' were common, but the new reform rules specify that these spellings are now the only correct spellings.

The last two verbs (marked ''(M)'') are ''modals''. They will be discussed in the next section.

&lt;big&gt;[[/Problems#Food-Related Verbs|Section Problems]] &gt;&gt;&lt;/big&gt;

==Modals==

In [[../Introduction|the introduction]], you learned that German has no helping verbs. Instead, they have '''modals''', words that basically do the same thing.

Modals are conjugated very differently from normal verbs. The ich- and er/sie/es-forms are always the same, while the du-form adds an 'st'. Most modals experience a vowel change from singular to plural, and the rest is the same.

===Möchten===

'Möchten' isn't technically a modal, but it acts exactly the same. There is no vowel change, and the ich- and er/sie/es forms are &quot;möchte&quot;. Here is the complete conjugation:


{| border=&quot;1&quot; style=&quot;background-color: #FFFF66;{{Text default color}};; width:50%&quot;
|- style=&quot;text-align:center;&quot;
| &lt;u&gt;Person&lt;/u&gt; || colspan=&quot;2&quot; | &lt;u&gt;Singular&lt;/u&gt;
|
| colspan=&quot;2&quot; | &lt;u&gt;Plural&lt;/u&gt;
|- style=&quot;text-align:center;&quot;
| '''1st''' || ich || ''möchte'' ||
 || wir
| ''möchten''
|- style=&quot;text-align:center;&quot;
| '''2nd''' || du || ''möchtest'' ||
 || ihr
| ''möchtet''
|- style=&quot;text-align:center;&quot;
| '''3rd''' || er/sie/es || ''möchte''
|
 || sie || ''möchten''
|}

'Möchten' means &quot;would like&quot; and can be applied to food (i.e. Ich möchte einen Cheeseburger.). Möchten can be translated even more literally as &quot;would like to&quot;, and is traditionally used with an infinitive verb at the end of the sentence (i.e. &quot;Ich möchte jetzt gehen&quot;/&quot;I would like to go now&quot;). However, this infinitive is not neccesary if it's completely obvious what you're talking about (If you say &quot;Ich möchte einen Cheeseburger&quot;, everyone will assume that you would like a cheeseburger to eat.)

(Note: ''Technically, &quot;möchten&quot; is not a word. The above cited conjugation is actually the &quot;Konjunktiv&quot; of &quot;mögen&quot;, which has become so popular as a phrase, that even many Germans today aren't aware of it anymore, so you don't need to worry about it. &quot;Etwas mögen&quot; means &quot;to like to&quot;, and &quot;I would like&quot; is the closest translation of &quot;ich möchte.&quot;'')

===Wollen===

'Wollen' is a true modal; it even changes vowels. Ich/er/sie/es ''will'' and du ''willst''. Here is the complete conjugation:


{| border=&quot;1&quot; style=&quot;background-color: #FFFF66;{{Text default color}}; width:50%&quot;
|- style=&quot;text-align:center;&quot;
| &lt;u&gt;Person&lt;/u&gt; || colspan=&quot;2&quot; | &lt;u&gt;Singular&lt;/u&gt;
|
| colspan=&quot;2&quot; | &lt;u&gt;Plural&lt;/u&gt;
|- style=&quot;text-align:center;&quot;
| '''1st''' || ich || ''will'' ||
 || wir
| ''wollen''
|- style=&quot;text-align:center;&quot;
| '''2nd''' || du || ''willst'' ||
 || ihr
| ''wollt''
|- style=&quot;text-align:center;&quot;
| '''3rd''' || er/sie/es || ''will'' ||
 || sie
| ''wollen''
|}

'Wollen' can also be applied to food, but may be considered impolite and demanding (&quot;Ich will einen Cheeseburger!&quot; roughly means &quot;I demand a cheeseburger!&quot; ''Möchten'' should be used instead: &quot;Ich möchte einen Cheeseburger!&quot; = &quot;I want a cheeseburger!&quot;).

'Wollen' should not be confused with the future tense, despite the presence of the English word 'will' in the conjugations. However, [[Wiktionary:will|will]] can also mean an intent or a document showing what one ''wants'' to happen. So it is not so different from 'to want' as possibly originally presumed.

===Modals with other verbs===

'''This is very important.''' When you need to use another verb with a modal (such as expressing you would like or want to perform an action), the sentence's word order is somewhat different than it would be in English. In English, you would state the subject pronoun (such as &quot;I&quot;), an English equivalent to the modal verb (such as &quot;want&quot;), the action you want to perform (such as &quot;to eat&quot;) and then what the action will be performed on (such as &quot;hamburger&quot;), making the sentence &quot;I want to eat a hamburger.&quot; In German you must put the action at the end of the sentence, making the sentence &quot;I want a hamburger to eat.&quot; (''&quot;Ich will einen Hamburger essen.&quot;'')

&lt;big&gt;[[/Problems#Modals|Section Problems]] &gt;&gt;&lt;/big&gt;

==Hunger and Thirst==

In German, instead of saying, &quot;I'm hungry.&quot;, you say &quot;I have hunger.&quot; The same applies to thirst. Here are the German translations of the corresponding nouns:

Hunger - der Hunger

Thirst - der Durst

Like in English, these two words do not have a plural form. When using them, you don't need to worry about the 'der'; you can just say, &quot;Ich habe Hunger.&quot; to say &quot;I am hungry.&quot;

&lt;big&gt;[[/Problems#Hunger and Thirst|Section Problems]] &gt;&gt;&lt;/big&gt;

==Formal Conversations==

In [[../Wie heißt du?|Lesson 1]], you learned how to talk formally, using phrases like &quot;Guten Morgen!&quot; and &quot;Wie heißen Sie?&quot;. There are, however, a few words that are 'survival words' in Germany, specifically:

'''Danke''' - Thank you, Thanks

'''Bitte''' - Please ''and'' You're welcome.

To make this even more formal, you can tack on the word 'schön' to the end of &quot;Thank you&quot; and &quot;You're welcome&quot; to make 'dankeschön' and 'bitteschön' (both one word) in response. 'Schön' literally means 'pretty' (you'll relearn this next lesson). 

'''Some other ways to say &quot;thank you&quot;:'''
* Dankeschön - Thank you very much
* Danke sehr - Thanks a lot
* Herzlichen Dank (&quot;herzlichen&quot; means sincere or from the heart; you may remember it from &quot;&lt;u&gt;Herzlichen&lt;/u&gt; Glückwunsch zum Geburtstag!&quot; last lesson)
* Vielen Dank - Thanks a lot
* Tausend Dank* - Thanks a million (literally meaning a thousand, but English is more generous)
* Aufrichtigen Dank* - would be &quot;thank you sincerely&quot; (''very'' formal)

&lt;small&gt;* - You will not be tested on these phrases.&lt;/small&gt;

'''Some other ways to say &quot;You are welcome&quot;:'''

* Bitteschön!
* Bitte sehr!
* Gern geschehen! - Don't mention it
* Gerne! - also meaning &quot;gladly&quot;
* Kein Problem! - No problem
* Dafür nicht!* - (Do) not (thank me) for this (only used in Northern Germany)

&lt;small&gt;* - You will not be tested on this phrase.&lt;/small&gt;

These might also be useful:

'''Entschuldigung''' - Excuse me, Pardon

'''Es tut mir leid''' - Sorry, I'm sorry

&lt;big&gt;[[/Problems#Formal Conversations|Section Problems]] &gt;&gt;&lt;/big&gt;

==Kein-words==

Twice you have been taught that the ending of the indefinite article for plurals ''would be'' eine (for Nominative and Accusative cases), if there was an indefinite article for plurals. Now that lesson applies. The '''k'''ein-words have the same endings as the ein-words, and they mean the opposite: no, not any, none. For example, &quot;kein Cheeseburger&quot; means &quot;no cheeseburger&quot;. &quot;Keine Cheeseburger&quot; (in this case Cheeseburger is plural) means &quot;No cheeseburger'''s'''&quot;. Notice the 'e' at the end of 'keine'. That's the ending for plurals and feminine nouns and can be likened to the &quot;der, die, das -&gt; die&quot; relationship, where the feminine article serves for the plural as well.

&lt;big&gt;[[/Problems#Kein-words|Section Problems]] &gt;&gt;&lt;/big&gt;

==Ordering at a Restaurant in Germany==

das Restaur'ant' (French pronunciation)&lt;!--Gaststätte is older German and somewhat &quot;deprecated&quot;--&gt; - Restaurant {{Audio|Fr-Restaurant.ogg}}

There are many restaurants you might find in Germany. Much like in English-speaking countries, you would more likely use the name of the restaurant than name what kind of restaurant. If you want to address the wish to eat a certain food, there are two ways:

example: &quot;wanting to eat chinese food&quot;

1. &quot;Ich möchte gerne zum Chinesen.&quot; - literally: &quot;I want to go to the Chinese (restaurant).&quot;
2. &quot;Ich möchte gerne chinesisch essen (gehen).&quot; - literally: &quot;I want to (go) eat Chinese (style food).&quot;

Here are some more restaurants you can find in Germany:

* American food: &quot;zum Amerikaner&quot; / &quot;amerikanisch essen&quot;*
* Arabic food: &quot;zum Araber&quot; / &quot;arabisch essen&quot;
* Chinese food: &quot;zum Chinesen&quot; / &quot;chinesisch essen&quot;
* French food: &quot;zum Franzosen&quot; / &quot;französisch essen&quot;
* Greek food: &quot;zum Griechen&quot; / &quot;griechisch essen&quot;
* Italian food: &quot;zum Italiener&quot; / &quot;italienisch essen&quot;
* Indian food: &quot;zum Inder&quot; / &quot;indisch essen&quot;
* Japanese food: &quot;zum Japaner&quot; / &quot;japanisch essen&quot;
* Mexican food: &quot;zum Mexikaner&quot; / &quot;mexikanisch essen&quot;
* Spanish food: &quot;zum Spanier&quot; / &quot;spanisch essen&quot;
* Turkish food: &quot;zum Türken&quot; / &quot;türkisch essen&quot;
&lt;small&gt;* &quot;zum Amerikaner&quot; is often used in a jokey way, to express that one is going to either McDonald's or Burger King. There are few American restaurants, in Germany and they are mostly referred to as &quot;(American) Diner&quot;, so it is not used like &quot;zum Italiener&quot;.&lt;/small&gt;

==Accusative case prepositions==
You read at the beginning of this lesson that the &lt;span style=&quot;color: green;&quot;&gt;'''Accusative Case'''&lt;/span&gt; covers the direct object and the objects of some prepositions. Here are those prepositions that always fall under Accusative Case

''bis'' - until

''durch'' - through

''entlang'' - along

''für'' - for

''gegen'' - against

''ohne'' - without

''um'' - at, around

You learned ''um'' last lesson, and ''ohne'' earlier this lesson. ''Bis'', ''durch'', ''entlang'' and ''gegen'' will be taught in depth later, and ''für'' will be taught now. 

Up until this point, you have only worried about the Accusative Case in third person. ''Für'', meaning 'for', can and should be used in the first and second persons, too. Here's an example:

&quot;The cheeseburger is for me.&quot; - &quot;Der Cheeseburger ist ''für mich''.&quot;

As you can see, 'me' is put into accusative case because the preposition is ''für''.

&lt;big&gt;[[/Problems#Accusative case preparations|Section Problems]] &gt;&gt;&lt;/big&gt;

==Saying How Food Tastes==

In German (as in English) there are several ways of telling how food tastes. You can do this with 'gut' and 'schlecht' from [[../Wie heißt du?|Lesson 1]] to say:

'''Der Cheeseburger schmeckt gut - The cheeseburger tastes good'''  

'''Der Cheeseburger schmeckt schlecht - The cheeseburger tastes bad'''

But this is bland. Hopefully the food has more flavor than the description of it. You can use the following words to more colorfully describe how the cheeseburger tastes:

* delicious - ''lecker''

* delicious - ''delikat''* (a lot more formal than lecker)

* tasty - ''schmackhaft''

* juicy - ''saftig''*

* crunchy - ''knackig'' (can also mean ''crispy'')

* crispy - ''knusprig''*

* spicy - ''würzig'', ''pikant''

* stale, tasteless - ''fade''* (Austria: fad) 

* salty - ''salzig''

* oversalted - ''versalzen''*

* sweet - ''süß''

* bitter - ''bitter''

* sour - ''sauer''

* creamy - ''cremig''*

* hot (in the sense of &quot;very spicy&quot;) - ''scharf'' - literally meaning &quot;sharp&quot;

* hot (in the sense of &quot;very warm&quot;) - ''heiß''

* burnt - ''angebrannt''*

* cold - ''kalt''

* disgusting, terrible - ''schrecklich''

&lt;small&gt;* - You will not be tested on these descriptors.&lt;/small&gt;

'''Schmecken''' is a regular verb. Here is it's conjugation:


{| border=&quot;1&quot; style=&quot;background-color: #FFFF66;{{Text default color}}; width:50%&quot;
|- style=&quot;text-align:center;&quot;
| &lt;u&gt;Person&lt;/u&gt; || colspan=&quot;2&quot; | &lt;u&gt;Singular&lt;/u&gt; || || colspan=&quot;2&quot; | &lt;u&gt;Plural&lt;/u&gt;
|- style=&quot;text-align:center;&quot;
| '''1st''' || ich || ''schmecke'' ||
 || wir
| ''schmecken''
|- style=&quot;text-align:center;&quot;
| '''2nd''' || du || ''schmeckst'' ||
 || ihr
| ''schmeckt''
|- style=&quot;text-align:center;&quot;
| '''3rd''' || er/sie/es || ''schmeckt''
|
 || sie || ''schmecken''
|}

The first and second persons really shouldn't be used. No one is going to say, &quot;You guys taste salty&quot; or &quot;I taste creamy.&quot; So the only forms you ''really'' need to know are er/sie/es ''schmeckt'' and sie (plural) ''schmecken''.

You can use 'schmeckt' and 'schmecken' or 'ist' and 'sind' to state how the food tastes. Just use whichever one you would use in English and it'll usually be correct.

Although the English meaning of ''schmecken'' is simply ''to taste'', ''&quot;Schmeckt der Cheeseburger?&quot;'' can be taken in a positive way to mean &quot;Do you like the cheeseburger?&quot;. In other words, ''schmecken'' alone can mean ''to taste good''.

&lt;big&gt;[[/Problems#Saying How Food Tastes|Section Problems]] &gt;&gt;&lt;/big&gt;

==Dieser-forms==

&quot;''The'' cheeseburger tastes good.&quot; does not sound that specific as to which cheeseburger you are talking about. You could be talking about a cheeseburger that is not directly in front of you. It just isn't clear. Now, if you said, &quot;''This'' cheeseburger tastes good.&quot;, it would be obvious that you're talking about the cheeseburger you're eating. 'Dieser' is the German translation for 'this': &quot;Dieser Cheeseburger schmeckt gut.&quot;

===Dieser===

'Dieser' is a special adjective. It changes forms in different situations: different genders and different cases. It can also mean 'these' when modifying a plural. Here are its forms:

{| border=&quot;1&quot; style=&quot;background-color: #99FF99;{{Text default color}}; width:50%&quot;
|- style=&quot;text-align:center;&quot;
|
 || &lt;u&gt;Masculine&lt;/u&gt; || &lt;u&gt;Feminine&lt;/u&gt;
| &lt;u&gt;Neuter&lt;/u&gt; || &lt;u&gt;Plural&lt;/u&gt;
|- style=&quot;text-align:center;&quot;
| Nominative Case || dies'''er''' || dies'''e'''
| dies'''es''' || dies'''e'''
|- style=&quot;text-align:center;&quot;
| Accusative Case || dies'''en''' || dies'''e'''
| dies'''es''' || dies'''e'''
|}

As you can see, ''dieser'' is only appropriate for modifying masculine nouns in nominative case. But 'Cheeseburger', which is masculine, is the subject of the sentence, &quot;Dieser Cheeseburger schmeckt gut.&quot; So it is correct in that circumstance.

===Jeder===

''Jeder'' means 'every'. It acts exactly like 'dieser' in its endings, so it should be easy to remember. Here are the different forms:

{| border=&quot;1&quot; style=&quot;background-color: #99FF99;{{Text default color}}; width:50%&quot;
|- style=&quot;text-align:center;&quot;
|
 || &lt;u&gt;Masculine&lt;/u&gt; || &lt;u&gt;Feminine&lt;/u&gt;
| &lt;u&gt;Neuter&lt;/u&gt;
|- style=&quot;text-align:center;&quot;
| Nominative Case || jed'''er''' || jed'''e'''
| jed'''es'''
|- style=&quot;text-align:center;&quot;
| Accusative Case || jed'''en''' || jed'''e'''
| jed'''es'''
|}

Notice the absence of the plural form. When you think about this, it's the same in English: no one says 'every books'.

===Welcher===

'Welcher' is the third of this threesome of adjectives. 'Welcher' means 'which' and is used like the other [w:Interrogative word|interrogatives] (wer, was, wann, wo, warum, wie, and welcher). However, because the general subject has to be specified, ''welcher'' must be inflected before use: &quot;Welcher Hamburger ist seine?&quot;  Its forms have the same endings as 'dieser'.

{| border=&quot;1&quot; style=&quot;background-color: #99FF99;{{Text default color}}; width:50%&quot;
|- style=&quot;text-align:center;&quot;
|
 || &lt;u&gt;Masculine&lt;/u&gt; || &lt;u&gt;Feminine&lt;/u&gt;
| &lt;u&gt;Neuter&lt;/u&gt; || &lt;u&gt;Plural&lt;/u&gt;
|- style=&quot;text-align:center;&quot;
| Nominative Case || welch'''er''' || welch'''e'''
| welch'''es''' || welch'''e'''
|- style=&quot;text-align:center;&quot;
| Accusative Case || welch'''en''' || welch'''e'''
| welch'''es''' || welch'''e'''
|}

===Connection with Time===

You might want to say 'every day', 'this week', 'every morning', or 'which Tuesday night?'. But to do this, not only do you need to know the jeder-forms, but also the genders of the times and the cases. The second one is easy: '''Whenever you do something at a certain time, that time is put into &lt;span style=&quot;color: green;&quot;&gt;Accusative Case&lt;/span&gt;.''' Last lesson, you learned the gender of one time: ''der'' Tag. So now you know everything to say 'diesen Tag', 'jeden Tag', and 'welchen Tag?' (this day, every day, and which day?). Here are the cases of all the times in [[../Freizeit|Lesson 2]]:


{| border=&quot;1&quot; style=&quot;width:50%&quot;
|- style=&quot;text-align:center;&quot;
| &lt;u&gt;Masculine&lt;/u&gt; || &lt;u&gt;Feminine&lt;/u&gt; || &lt;u&gt;Neuter&lt;/u&gt;
|- style=&quot;vertical-align:top;&quot;
|
* Tag
* Monat
* Morgen
* Abend
* Nachmittag
|
* Woche
* Nacht
|
* Jahr
* Wochenende
|}

When extending to 'which Tuesday night?', remember that the night stays feminine on Tuesday, so it stays &quot;Welche Dienstagnacht?&quot;. Likewise, you can say 'every June' the same as 'every month': 'jeden Juni'.

===This and That===

''Ich möchte einen Cheeseburger. Der schmeckt sehr gut.''

''Ich esse jeden Tag Cheeseburger. Die habe ich gern.''

Look at the second sentence of each of these German dialogues. What's missing? That's right, instead of &quot;Der Cheeseburger schmeckt sehr gut.&quot; and &quot;Die Cheeseburger habe ich gern.&quot;, both of the 'Cheeseburger's, so to speak, are dropped. We're left with just the articles, only in this case, they aren't articles. They're '''demonstrative pronouns'''.

Demonstrative pronouns aren't scary. They're just the same as the normal pronouns, only they give more ''oomph'' to the sentence. They can be translated as either 'this' or 'that' (&quot;I'd like a cheeseburger. That tastes very good.&quot;), or 'these' or 'those' for plurals (&quot;I eat cheeseburgers every day. These I like.&quot;).

Demonstrative pronouns are exactly the same as the definite articles (well, there is one change in dative, but that will be covered in [[../Das Fest|Lesson 7]]). If you are not sure of the gender (meaning in context, the speaker doesn't know, not that you've forgotten that it's 'der Cheeseburger'), use 'das', like in &quot;Was ist das?&quot; (What is that?).

==Money and Paying==


Germany, Austria, Luxemburg, Belgium and Südtirol – in other words: all German speaking regions except Switzerland and Liechtenstein– have given up their former currencies and adopted the Euro as of 1999. One ''Euro'' is worth 100 ''Cents''. Because they are not members of the European Union, Switzerland and Liechtenstein have kept the Swiss Francs (''Franken'' = 100 ''Rappen''). 

'Euro' normally does not change in the plural in German, so you would still say &quot;Ich habe 500 Euro.&quot; Nevertheless, there is an exception: Euro ''coins''. If you say &quot;Ich habe vier Euros.&quot;, you actually are saying that you have four 1-Euro coins. Because the backsides of euro coins look different in each country, many people in Europe have started collecting foreign euro coins. In this case you can say &quot;Ich habe irische Euros.&quot; (I have Irish euro coins.) for example.

There is not yet a rule whether or not the word ''&quot;Cent&quot;'' has a different plural form. The majority of Germans are using the word ''&quot;Cent&quot;'' as a plural form, but when they don't it is simply ''&quot;Cents&quot;''.

In German &quot;euro&quot; is pronounced [‘oi-ro], not [you-ro]. For &quot;Cent&quot; there are two pronunciations: you can either pronounce it as in English or you say &quot;tzent&quot;. The latter version seems to be preferred by older people.

When at a restaurant, you will want to pay at the end. You can use this vocabulary to help you.

* to pay - ''zahlen''

* the bill - ''die Rechnung''*

* the waiter - ''der Kellner'', ''die Bedienung'' (also ''der Ober'')**

* the waitress - ''die Kellnerin'' (but '''not''' ''die Oberin'' because this means ''Reverend Mother'')

* &quot;How much is that?&quot; - ''&quot;Was macht das?&quot;'' (&quot;What does that make?&quot;) or the &quot;umgangssprachliche&quot; ''&quot;Wie viel kostet das?&quot;''

&lt;small&gt; * To ask for the bill you can say, &quot;Bitte zahlen!&quot;, or make it a complete sentence: &quot;Ich würde gern zahlen!&quot;, or &quot;Wir möchten/wollen zahlen!&quot;. You can also say, &quot;(Herr Ober), die Rechnung bitte!&quot;. The term &quot;der Ober&quot; is the waiter, but this sounds very old fashioned and is hardly ever used today. To address the waiter you would probably say &quot;Entschuldigen Sie, ...&quot; (&quot;Pardon, ...&quot;) like in &quot;Entschuldigen Sie, wir würden gern zahlen&quot; (Pardon me, we would like to pay&quot;).&lt;/small&gt; 

&lt;small&gt; ** Although it is perfectly OK to say “Bedienung” or “Kellner” when talking about a waiter or a waitress, you should not address the waiter by saying &quot;Bedienung!&quot; or even “Fräulein!” which is regarded very impolite since the 1980s. &lt;/small&gt;

&lt;big&gt;[[/Problems#Dieser-forms|Section Problems]] &gt;&gt;&lt;/big&gt;

==Test==

The test will be located [[/Test|here]], but the test for this lesson is not yet completed.  

&lt;noinclude&gt;{{German/Level I/Footer|100%}}{{BookCat}}&lt;/noinclude&gt;</text>
      <sha1>reiu9v7trv5jsofxbyt1ihrs1b5fril</sha1>
    </revision>
  </page>
  <page>
    <title>OpenSSH/Server</title>
    <ns>0</ns>
    <id>248406</id>
    <revision>
      <id>4668914</id>
      <parentid>4629160</parentid>
      <timestamp>2026-09-05T12:00:24Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <minor />
      <comment>typo</comment>
      <origin>4668914</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="18641" sha1="ml12elkukxhlfhi2xp5weq8k5j6wbac" xml:space="preserve">The OpenSSH Server, [http://man.openbsd.org/sshd.8 sshd(8)], listens for connections from clients and starts a new process or two for each new incoming connection to handle key exchange, encryption, authentication, program execution, and data exchange.  In the case of multiplexing, some processes are reused.  It can run standalone and wait in the background, be run in the foreground, or it can be loaded on demand by any Internet services daemon.  

Since version 8.2, the listening process title shown in [http://man.openbsd.org/ps.1 ps(1)] also shows the number of connections pending authentication. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ps -p $(pgrep -u root sshd) -o pid,user,args 
  PID USER     COMMAND
44476 root     sshd: /usr/sbin/sshd [listener] 0 of 10-100 startups (sshd)
&lt;/syntaxhighlight&gt;

Note that this is the number pending authentication, not the number which of those which have already been authenticated.  Those each have their own separate handler process owned by the account which has authenticated.  

&lt;noinclude&gt;__TOC__&lt;/noinclude&gt;

==sshd(8)==

[http://man.openbsd.org/sshd.8 sshd(8)] is the secure shell daemon and it listens for incoming connections.  The standard port for [http://man.openbsd.org/ssh.1 ssh(1)] as specified by IANA is 22 &lt;ref name=&quot;IANA_ports&quot;&gt;{{cite web |url=http://www.ietf.org/assignments/service-names-port-numbers/service-names-port-numbers.txt |title=Service Name and Transport Protocol Port Number Registry |publisher=IETF |year=2012}}&lt;/ref&gt;.  If [http://man.openbsd.org/sshd.8 sshd(8)] does not listen to a privileged port, it does not have to be launched by root, as long as the host keys are readable.  However there are few, if any occasions where a non-standard port should be considered.  A single instance of [http://man.openbsd.org/sshd.8 sshd(8)] can be bound to specific addresses, or even multiple addresses.  Multiple instances of [http://man.openbsd.org/sshd.8 sshd(8)], each with a different configuration, can be run on the same machine, something which may be useful on multi-homed machines or in testing new a configuration.  An absolute path must be given to launch [http://man.openbsd.org/sshd.8 sshd(8)], i.e. &lt;code&gt;/usr/sbin/sshd&lt;/code&gt;

:[http://man.openbsd.org/sshd.8 sshd(8)] - The SSH daemon that permits you to log in.
:[http://man.openbsd.org/sshd_config.5 sshd_config(5)] - The server configuration file.

:[http://man.openbsd.org/sftp-server.8 sftp-server(8)] - SFTP server subsystem, started automatically by [http://man.openbsd.org/sshd.8 sshd(8)] when needed.
:[http://man.openbsd.org/ssh-keysign.8 ssh-keysign(8)] - Helper program for hostbased authentication, also started automatically by [http://man.openbsd.org/sshd.8 sshd(8)] when needed.

The first time a server configuration directive is matched it is set and subsequent values will be ignored.  Configuration data is parsed first from the run time arguments and options passed by the shell.  After that the system-wide configuration file is read.  

For testing, the [http://man.openbsd.org/sshd.8 sshd(8)] daemon can be made to parse its configuration file, while testing it for validity, and then report on the effective configuration settings.  This is done by running the extended test mode ('''-T''') which will print out the actual default server settings.  Or, apply various inputs by adding the '''-C''' option as well.  In either case, output from the '''-T''' option is long so it might be sensible to organize it by piping it through [http://man.openbsd.org/sort.1 sort(1)] and then view it through a pager like [http://man.openbsd.org/less.1 less(1)].  See the section on [[OpenSSH/Logging_and_Troubleshooting#Debugging_a_server_configuration| Debugging a Server Configuration]] for more options.  Again, the directives are taken by the daemon in the following order at start or upon receiving SIGHUP:
# run time options for [http://man.openbsd.org/sshd.8 sshd(8)]
# directives from the system configuration file [http://man.openbsd.org/sshd_config.5 sshd_config(5)]

By default, login is allowed for all groups.  However, if either '''AllowGroups''' or '''AllowUsers''' is specified, then all users or groups not listed are prohibited from logging in.   The allow/deny directives are processed in the following order: 
# '''DenyUsers''', 
# '''AllowUsers''', 
# '''DenyGroups''', and finally, 
# '''AllowGroups'''.  

For the most flexibility, it is recommended to use '''AllowGroups'''.  But, if '''AllowUsers''' exists it will completely override '''AllowGroups''' regardless of the order in which they appear in the configuration file.   Note that '''DenyUsers''' and '''DenyGroups''' take precedence over both but, in contrast, '''DenyUsers''' and '''DenyGroups''' do not interfere with each other and may be used together.  Groups can be identified by their names directly or included through patterns matching group names, all separated by spaces.  If a group is specified directly or via a pattern, login is allowed or denied only for users who are members of a group that matches a group or pattern on the list.  Only the names of group or user accounts are valid here; numerical group or user IDs are not recognized.

===The Sequence In Which Files Are Read From /etc/ssh/sshd_config.d/ Matters===

If additional configuration files are read from the '''/etc/ssh/sshd_config.d/''' directory as a result of an '''Include''' directive, then the order in which these files are read really matters&lt;ref name=&quot;order of files in sshd_config.d&quot;&gt;{{cite web |url=https://utcc.utoronto.ca/~cks/space/blog/sysadmin/OpenSSHConfigOrderMatters |title=The order of files in /etc/ssh/sshd_config.d/ matters (and may surprise you) |publisher=The University of Toronto | date=2025-04-02 | accessdate=2025-05-23 | author=Chris Siebenmann}}&lt;/ref&gt; a lot.  As mentioned above, configuration values are set on a first-match basis.  So if files contain contradictory settings, the first file read takes precedence and any conflicting configuration directives from subsequent files will be ignored.  It is easy to check and verify the final server settings using the '''-T''' option, with or without the '''-C''' option.  

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ /usr/sbin/sshd -T | sort | less -X 
&lt;/syntaxhighlight&gt;

Since [http://man.openbsd.org/sshd_config sshd_config(5)] affects the behavior of outward facing services, it is most important to ensure that the end results are correct.  So the '''-C''' option might be included when using '''-T''' to check the what happens when the '''Match''' directive is applied in regards to relevant combinations of source addresses, incoming account names, resolved source host names, local server addresses, local server port numbers, and routing tables respectively.

The following will print out the specific configurations which will be applied if the user 'fred' tries to log in to the host ''server.example.org'' from the address ''192.168.100.5''.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ /usr/sbin/sshd -TC user=fred,host=server.example.org,addr=192.168.100.5
&lt;/syntaxhighlight&gt;

The options for '''-C''' are discussed more in the  [[OpenSSH/Logging_and_Troubleshooting#Debugging_a_server_configuration| Debugging a Server Configuration]] section.

==sshd under inetd / xinetd==

An Internet services daemon is a server to launch other servers on demand.  [http://linux.die.net/man/8/xinetd xinetd(8)] and [http://man.openbsd.org/inetd.8 inetd(8)] are two variants, either of which can be used to specify additional parameters and constraints, including running the launched service as a particular user and group.  By having a single daemon active, which invokes others as needed, demands on the system can be reduced.  Launching [http://man.openbsd.org/sshd.8 sshd(8)] this way means [http://man.openbsd.org/inetd.8 inetd(8)] waits for an incoming request, launches [http://man.openbsd.org/sshd.8 sshd(8)] and then when the SSH session is over, closes [http://man.openbsd.org/sshd.8 sshd(8)].  

&lt;pre&gt;
              Packet
 Internet --&gt; Filter --&gt; tcpwrappers --&gt; (x)inetd --&gt; sshd
             (firewall)  (aka tcpd)
&lt;/pre&gt;

Either can be used for additional logging such as successful or unsuccessful login, access restriction even including time of day, cpu priority, and number of connections.  There are many more possibilities.  See the manual pages for [http://linux.die.net/man/5/xinetd.conf xinetd.conf(5)] or [http://man.openbsd.org/inetd.conf.5 inetd.conf(5)] for a full overview of configuration options.  

[http://man.openbsd.org/inetd.8 inetd(8)] was '''tcpd'''-aware and could make use of '''tcpd''''s tcpwrappers to further control access or logging.  So was [http://man.openbsd.org/sshd.8 sshd(8)] by itself, up through 6.6.  See the manual pages for [ht ormation about how to use the configuration files '''hosts.allow''' and '''hosts.deny'''.  Since 6.7, OpenSSH itself no longer supports tcpwrappers because current packet filters filters made it mostly redundant.  

The two main disadvantages of using [http://man.openbsd.org/inetd.8 inetd(8)] or xinetd(8) are that there can be a slight increase in the delay during the start of the connection and that [http://man.openbsd.org/sshd.8 sshd(8)] must be configured to allow launching from the services daemon.  The delay only affects the initial connection and thus does not get in the way of actual operation.  An Internet services daemon should not be used for stateless services like HTTP and HTTPS, where every action is essentially a new connection.  Again, see the manual page for [http://linux.die.net/man/5/xinetd.conf xinetd.conf(5)] or [http://man.openbsd.org/inetd.conf.5 inetd.conf(5)] for more details.  

Example from [http://linux.die.net/man/5/xinetd.conf xinetd.conf(5)]
&lt;pre&gt;
service ssh
{
	socket_type     = stream
	protocol        = tcp
	wait            = no
	user            = root
	server          = /usr/sbin/sshd
	server_args     = -i
	per_source      = UNLIMITED
	log_on_failure  = USERID HOST
	# log_on_success  = PID HOST DURATION TRAFFIC EXIT
	# instances       = 10
	# nice            = 10
	# bind            = 192.168.0.100
	# only_from       = 192.168.0.0
	# access_times    = 08:00-15:25
	# no_access       = 192.168.54.0
	# no_access       += 192.168.33.0
	# banner          = /etc/banner.inetd.connection.txt
	# banner_success  = /etc/banner.inetd.welcome.txt
	# banner_fail     = /etc/banner.inetd.takeahike.txt
}
&lt;/pre&gt;

Example from [http://man.openbsd.org/inetd.conf.5 inetd.conf(5)]
&lt;pre&gt;
ssh    stream  tcp     nowait  root /usr/sbin/sshd -i
ssh    stream  tcp6    nowait  root /usr/sbin/sshd -i
&lt;/pre&gt;

There are several advantages with [http://linux.die.net/man/8/xinetd xinetd(8)] over 
[http://man.openbsd.org/inetd.8 inetd(8)] in capabilities but use-cases where either would be useful are rare.  

==The SFTP Server Subsystem==

The SFTP subsystem first appeared in OpenBSD 2.8 / OpenSSH 2.3&lt;ref name=&quot;OpenSSH_2.3.0p1_Release_Notes&quot;&gt;{{cite web |url=http://www.openssh.org/txt/release-2.3.0p1 |title=OpenSSH 2.3.0p1 release notes |publisher=OpenSSH.org |orig-date=2000}}&lt;/ref&gt;.  It is called by [http://man.openbsd.org/sshd.8 sshd(8)] as needed using the '''Subsystem''' configuration directive and not intended to operate standalone.  There are two forms of the subsystem.  One is the regular [http://man.openbsd.org/sftp-server.8 sftp-server(8)].  The other is an in-process SFTP server, which requires no support files when used with the '''ChrootDirectory''' directive.  The '''Subsystem''' configuration directive can be used to pass options: 

'''-d''' specifies an alternate starting directory for users, the default is the user's home directory.  (First in 6.2)

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Subsystem sftp internal-sftp -d /var/www
&lt;/syntaxhighlight&gt;

'''-e''' causes logging information to be sent to '''stderr''' instead of [http://man.openbsd.org/syslog.3 syslog(3)].  

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Subsystem sftp internal-sftp -e
&lt;/syntaxhighlight&gt;

'''-f''' specifies the [http://man.openbsd.org/syslog.3 syslog(3)] facility code that is used when logging messages from [http://man.openbsd.org/sftp-server.8 sftp-server(8)].  The possible values are: DAEMON, USER, AUTH, LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7.   

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Subsystem    sftp    /usr/libexec/sftp-server -f LOCAL0
&lt;/syntaxhighlight&gt;

'''-l''' Specifies which messages will be logged by [http://man.openbsd.org/sftp-server.8 sftp-server(8)].  The default is AUTH.  The other possible values are: QUIET, FATAL, ERROR, INFO, VERBOSE, DEBUG, DEBUG1, DEBUG2, and DEBUG3.  INFO and VERBOSE log transactions that sftp-server performs on behalf of the client.  DEBUG and DEBUG1 are equivalent while DEBUG2 and DEBUG3 each specify higher levels of debugging output.  Log levels DEBUG through DEBUG3 will violate user privacy and should not be used for regular operation.  The default log level is ERROR.  The actual path will vary depending on distro or operating system.

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Subsystem    sftp    /usr/libexec/sftp-server -l VERBOSE
&lt;/syntaxhighlight&gt;

'''-p''' and '''-P''' specify whitelisted and blacklisted protocol requests, respectively.  The comma separated lists are permitted or prohibited accordingly, the blacklist  is applied first if both are used.  '''-Q''' provides a list of protocol features supported by the server.  All three are available as of version 6.5.  The actual path will vary depending on distro or operating system.

In version 6.5 ''requests'' are the only protocol features queriable.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ /usr/libexec/sftp-server -Q requests
&lt;/syntaxhighlight&gt;

'''-R''' places the SFTP subsystem in read-only mode.  Attempts to change the filesystem, including opening files for writing, will fail.

'''-u''' overrides the user's default umask and explicitly sets the [http://man.openbsd.org/umask.2 umask(2)] to be used for creating files and directories.  See the manual page for [http://man.openbsd.org/syslog.conf.5 syslog.conf(5)] for more information about log level or log facility.  
[http://man.openbsd.org/sshd.8 sshd(8)] must be able to access '''/dev/log''' for logging to work.  Using the [http://man.openbsd.org/sftp-server.8 sftp-server(8)] subsystem in conjunction with the main SSH server's '''ChrootDirectory''' option therefore requires that [http://man.openbsd.org/syslogd.8 syslogd(8)] establish a logging node inside the chrooted directory.

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Subsystem sftp internal-sftp -u 0002
&lt;/syntaxhighlight&gt;

That sets the umask for the SFTP subsystem in OpenSSH 5.4 and later.

==Environment Variables==

[http://man.openbsd.org/ssh.1 ssh(1)] and [http://man.openbsd.org/sshd.8 sshd(8)] set some environment variables automatically when logging in.  Other variables can be explicitly defined by users in the '''~/.ssh/environment''' file if the file exists and if the user is allowed to change the environment.  Variables can also be set on a key by key basis in the '''authorized_keys''' file, again only if the user is allowed to change the environment.

In '''~/.ssh/environment''', the format '''NAME=value''' is used to set the variable.  In '''~/.ssh/authorized_keys''' and '''/etc/ssh/authorized_keys''' the format is '''environment=&quot;NAME=value&quot;'''  For more information, see the '''PermitUserEnvironment''' and '''AcceptEnv''' configuration directives in [http://man.openbsd.org/sshd_config.5 sshd_config(5)] and the '''SendEnv''' directive in [http://man.openbsd.org/sshd_config.5 ssh_config(5)].

The following variables can be set by [http://man.openbsd.org/ssh.1 ssh(1)], depending on the situation.  

'''DISPLAY'''	If X11 is tunneled, this is set so that the '''DISPLAY''' variable indicates the location of the X11 server.  When it is automatically set by [http://man.openbsd.org/ssh.1 ssh(1)] it points to a value in the form ''hostname'':''n'', where ''hostname'' indicates the host where the shell runs, and ''n'' is an integer greater than or equal to one.  [http://man.openbsd.org/ssh.1 ssh(1)] uses this special value to forward X11 connections over the secure channel.  The user should normally not set '''DISPLAY''' explicitly, as that will render the X11 connection insecure and will require the user to manually copy any required authorization cookies.

'''HOME'''	The path of the user's home directory.

'''LOGNAME'''	Synonym for USER.  This is set for compatibility with systems that use this variable.

'''MAIL'''	The path of the user's mailbox.

'''PATH'''	The default PATH, as specified when compiling [http://man.openbsd.org/ssh.1 ssh(1)].

'''SSH_ASKPASS'''	If '''DISPLAY''' and '''SSH_ASKPASS''' are both set, and the SSH session does not have an associated terminal or pseudo-terminal, the program specified by '''SSH_ASKPASS''' will execute and open an X11 window to read the passphrase when one is needed.  This is particularly useful when calling [http://man.openbsd.org/ssh.1 ssh(1)] from an xsession or related script.  On some machines it may be necessary to redirect the input from '''/dev/null''' to make this work.

'''SSH_AUTH_SOCK'''	The path on the client machine to tell [http://man.openbsd.org/ssh.1 ssh(1)] the UNIX-domain socket used to communicate with an SSH key agent.

'''SSH_CLIENT'''	Identifies the client end of the connection.  It contains three space-separated values: the client IP address, client port number and the server port number.  

'''SSH_CONNECTION'''	Identifies the client and server ends of the connection.  The variable contains four space-separated values: client IP address, client port number, server IP address, and server port number.

'''SSH_ORIGINAL_COMMAND'''	If the '''ForceCommand''' directive was used, or '''Command=&quot;...&quot;''' in a key, then this variable contains the original command including the original options.  It can be used to extract the original arguments.

'''SSH_TTY'''	This is set to the name of the TTY (path to the device) associated with the current shell or command.  If the current session has no TTY, this variable is not set.

'''SSH_USER_AUTH'''	This will contain the name of a temporary file containing the authentication methods used for this particular session if '''ExposeAuthInfo''' is set in [http://man.openbsd.org/sshd_config.5 sshd_config(5)].  

'''TZ'''	This variable is set to indicate the present time zone if it was set when the daemon was started.  The SSH daemon passes this value on to new connections.

'''USER'''	Set to the name of the user logging in.

&lt;noinclude&gt;
== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>ml12elkukxhlfhi2xp5weq8k5j6wbac</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Garygaryj</title>
    <ns>3</ns>
    <id>255252</id>
    <revision>
      <id>4669053</id>
      <parentid>2231040</parentid>
      <timestamp>2026-09-06T06:37:08Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4669053</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4580" sha1="60x6tacs8xghpu78ah6hjhwsyvxm7f7" xml:space="preserve">&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Garygaryj!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;text-align:right; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks. [[User:Recent Runes|Recent Runes]] ([[User talk:Recent Runes|discuss]] • [[Special:Contributions/Recent Runes|contribs]]) 23:35, 9 August 2011 (UTC)&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;</text>
      <sha1>60x6tacs8xghpu78ah6hjhwsyvxm7f7</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:AshishDandekar7</title>
    <ns>3</ns>
    <id>258533</id>
    <revision>
      <id>4669048</id>
      <parentid>2193633</parentid>
      <timestamp>2026-09-06T06:34:09Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669048</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4589" sha1="5qt3xikmlztc7qwapuxmd6ulxwz1s1a" xml:space="preserve">&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, AshishDandekar7!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}};; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;text-align:right; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks. [[User:Recent Runes|Recent Runes]] ([[User talk:Recent Runes|discuss]] • [[Special:Contributions/Recent Runes|contribs]]) 18:50, 18 October 2011 (UTC)&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;</text>
      <sha1>5qt3xikmlztc7qwapuxmd6ulxwz1s1a</sha1>
    </revision>
  </page>
  <page>
    <title>User:U118656/Wikibooks projects/Reversing the Effects of Insulin Resistance with Aerobic Exercise Fact Sheet</title>
    <ns>2</ns>
    <id>258901</id>
    <revision>
      <id>4668918</id>
      <parentid>2199473</parentid>
      <timestamp>2026-09-05T12:07:52Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668918</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6672" sha1="2zpzs1zgu04kbbbfhdy12wy2s6b98rp" xml:space="preserve">==What is Insulin Resistance? &lt;ref name=&quot;Appel&quot;&gt;Appel, SJ. Sizing up patients for metabolic syndrome. Nursing 35: 20-21, 2005.&lt;/ref&gt; &lt;ref name=&quot;Diabetes&quot;&gt;Diabetes Australia. National Diabetes Services Scheme. 2011, 2011.&lt;/ref&gt; &lt;ref name=&quot;Gallagher&quot;&gt;Gallagher, EJ, LeRoith, D, and Karnieli, E. Insulin Resistance in Obesity as the Underlying Cause for the Metabolic Syndrome. Mount Sinai Journal of Medicine 77: 511-523, 2010.&lt;/ref&gt; &lt;ref name=&quot;Valensi&quot;&gt;Valensi, P, Chanu, B, and Cosson, E. Obesity, Metabolic Syndrome, Diabetes and Arterial Hypertension. Immunology, Endocrine &amp; Metabolic Agents - Medicinal Chemistry 6: 407-423, 2006.&lt;/ref&gt;==  

Insulin Resistance (IR) is a condition in which the cells of the body become resistant to the effects of insulin. Thus, a person is said to have impaired glucose tolerance / pre-diabetes. IR results in higher levels of insulin being required to maintain normal blood glucose levels. Eventually, the pancreas may be unable to keep up with insulin demand leading to long term health issues.

*''1 in 4 adults in Australia may at some time in their life have impaired glucose tolerance''

*''Being diagnosed with impaired glucose tolerance does not necessarily mean you will develop diabetes, but it makes you 10-20 times more likely than a normal person''

*''It is estimated that up to 1.8 million Australians are living with diabetes / impaired glucose tolerance''

==Who is at Risk of Developing Insulin Resistance? Patients who - &lt;ref name=&quot;Appel&quot;/&gt; &lt;ref name=&quot;Diabetes&quot;/&gt; &lt;ref&gt;Akram, T, Hasan, S, Imran, M, Karim, A, and Arslan, M. Association of polycystic ovary syndrome with cardiovascular risk factors. Gynecological Endocrinology 26: 47-53, 2010.&lt;/ref&gt; &lt;ref&gt;Viljoen, A, and Wierzbicki, AS. Potential Options to Treat Hypertriglyceridaemia. Curr. Drug Targets 10: 356-362, 2009.&lt;/ref&gt;==
{| 
| 
*Are overweight / obese
*Are Aboriginal or Torres Strait Islanders
*Are pregnant
| 
*Have a high fat diet
*Have a family history of type 2 diabetes, hypertension or heart disease
*Have a sedentary lifestyle
|}

==Classic Side Effects &lt;ref name=&quot;Diabetes&quot;/&gt; &lt;ref name=&quot;Gallagher&quot;/&gt; &lt;ref name=&quot;Valensi&quot;/&gt; &lt;ref&gt;Reinehr, T. Clinical presentation of type 2 diabetes mellitus in children and adolescents. Int. J. Obes. 29: S105-S110, 2005.&lt;/ref&gt;== 

A patient with IR may remain asymptomatic (no signs of symptoms) for an extended period of time, classic symptoms are often linked to:

{| class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;
|+ '''Acute Side Effects'''
! scope=&quot;col&quot; style=&quot;width:230px;&quot; | Hyperglycaemia Symptoms   
! scope=&quot;col&quot; style=&quot;width:230px;&quot; | Hyperinsulinemia Symptoms  
|-
| Slow Healing || Brain Fogginess (inability to concentrate)  
|-
| Frequent Thirst || Blurred Vision  
|-
| Frequent Urination || Fatigue  
|}
{| class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;
|+ '''Chronic Side Effects'''
! scope=&quot;col&quot; style=&quot;width:225px;&quot; |  Macro Vascular Issues  
! scope=&quot;col&quot; style=&quot;width:225px;&quot; |  Micro Vascular Issues  
! scope=&quot;col&quot; style=&quot;width:225px;&quot; |  Hyperinsulinemia Issues  
|-
|  Stroke  ||  Retinopathy (Blindness)  ||  Type 2 Diabetes  
|-
|  Heart Disease  ||  Nephropathy (Kidney Disease)  ||  Hypertension  
|-
|   ||  Neuropathy (Nervous Tissue Damage)    ||  Bad Cholesterol  
|- 
|   ||   ||  Weight Gain / Central Obesity    
|- 
|   ||   ||  Polycystic Ovary Disease  
|}

==Recommendations for Insulin Resistance Management &lt;ref&gt;Department of Health and Ageing. Physical Activity Guidelines. 2011, 2011.&lt;/ref&gt; &lt;ref&gt;Exercise &amp; Sports Science Australia. Adult Pre-Exercise Screening System. 2011, 2011.&lt;/ref&gt; &lt;ref&gt;Nocon, M, Hiemann, T, Müller-Riemenschneider, F, Thalau, F, Roll, S, and Willich, SN. Association of physical activity with all-cause and cardiovascular mortality: a systematic review and meta-analysis. Eur J Cardiovasc Prev Rehabil 15: 239-246, 2008.&lt;/ref&gt; &lt;ref&gt;Sassen, B, Cornelissen, V, Kiers, H, Wittink, H, Kok, G, and Vanhees, L. Physical fitness matters more than physical activity in controlling cardiovascular disease risk factors. Eur J Cardiovasc Prev Rehabil 16: 677-683, 2009.&lt;/ref&gt;==

''Always seek professional health guidance before commencing a training regime''

''Remember adherance to any form of physical activity is the most crucial step in reversing Insulin Resistance''

{| class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;
|+ '''Aerobic Exercise Recommendations'''
! scope=&quot;col&quot; style=&quot;width:500px;&quot; | Guidelines
! scope=&quot;col&quot; style=&quot;width:10px; background: black; color:white;&quot; | 
! scope=&quot;col&quot; style=&quot;width:500px;&quot; | Benefits
|-
| At least 30 minutes / moderate intensity on most days of the week  || style=&quot;background: black;color:white;&quot; | || Improves insulin sensitivity (Reverses IR)
|-
| Or at least 20 minutes / vigorous intensity three times per week || style=&quot;background: black;color:white;&quot; | || Improves quality of life
|-
| Influencing lifestyle choices can also contribute to daily aerobic activity || style=&quot;background: black;color:white;&quot; | || Controls blood glucose, insulin and blood pressure levels
|-
| • Transport - substitute driving with walking or cycling to work || style=&quot;background: black;color:white;&quot; | || Reduces the risk of obesity, death and illness
|-
| • Recreation - substitute indoor activities for outdoor activities || style=&quot;background: black;color:white;&quot; | || Reduces the risk of chronic IR issues
|-
| • Occupation - substitute the elevator for the stairs to the office || style=&quot;background: black;color:white;&quot; | || • Macro Vascular issues
|- 
| • Home - subtitute take away for a home cooked meal || style=&quot;background: black;color:white;&quot; | || • Micro Vascular issues
|- 
| || style=&quot;background: black;color:white;&quot; | || • Hyperinsulinemia issues  
|}
{| class=&quot;wikitable&quot; style=&quot;margin: 1em auto 1em auto;&quot;
|+ '''Examples of Aerobic Activity that Meets the Guidelines'''
! scope=&quot;col&quot; style=&quot;width:300px;&quot; | Low Intensity 
! scope=&quot;col&quot; style=&quot;width:300px;&quot; | Moderate Intensity 
! scope=&quot;col&quot; style=&quot;width:300px;&quot; | High / Vigorous Intensity
|-
| Does not cause a noticeable change in breathing rate || Able to maintain a conversation uninterrupted || Unable to maintain a conversation uniterrupted
|-
| • Washing || • Walking || • Jogging
|-
| • Cooking || • Swimming || • Aerobics
|-
| • Cleaning in the Home || • Social Sports || • Competitive Sports
|}

==Further Reading / Informational Sources==
*Diabetes Australia - National Diabetes Services Scheme - http://www.diabetesaustralia.com.au/ndss/
*Department of Health and Ageing – http://www.health.gov.au/
*Exercise &amp; Sports Science Australia - http://www.essa.org.au/

&lt;references/&gt;

{{BookCat}}</text>
      <sha1>2zpzs1zgu04kbbbfhdy12wy2s6b98rp</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Collinheretick</title>
    <ns>3</ns>
    <id>262378</id>
    <revision>
      <id>4669054</id>
      <parentid>2229121</parentid>
      <timestamp>2026-09-06T06:37:51Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669054</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4587" sha1="atmf9pkq996harjh7bfauknthej665h" xml:space="preserve">&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Collinheretick!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;text-align:right; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks. [[User:Recent Runes|Recent Runes]] ([[User talk:Recent Runes|discuss]] • [[Special:Contributions/Recent Runes|contribs]]) 21:21, 5 December 2011 (UTC)&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;</text>
      <sha1>atmf9pkq996harjh7bfauknthej665h</sha1>
    </revision>
  </page>
  <page>
    <title>User:Abdars</title>
    <ns>2</ns>
    <id>264926</id>
    <revision>
      <id>4668989</id>
      <parentid>2259228</parentid>
      <timestamp>2026-09-05T19:01:56Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668989</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="467" sha1="aazto4f6pp23t2rqpyh3akjagrecc3a" xml:space="preserve">{{Userpage}}

----


== Dear visitors ==


Hi! My name is Abdullah Danish Shervani... Thanks for paying a visit to my page. Please visit my talk page to leave a message.


Appreciated!


-- &lt;span style=&quot;position:relative;overflow:hidden;&quot;&gt; &lt;span style=&quot;position:absolute;bottom:1px;width:100%;height:5px;background:#eee;{{Text default color}};&quot;&gt;&amp;nbsp;&lt;/span&gt;[[User:abdars| &lt;span style=&quot;position:relative;border:1px solid #bbb&quot;&gt;&amp;nbsp;abdars&amp;nbsp;&lt;/span&gt; ]]&lt;/span&gt;</text>
      <sha1>aazto4f6pp23t2rqpyh3akjagrecc3a</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:AstroAlgebra</title>
    <ns>3</ns>
    <id>274461</id>
    <revision>
      <id>4669052</id>
      <parentid>2365561</parentid>
      <timestamp>2026-09-06T06:36:23Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669052</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4355" sha1="0qd0n6x0e8lxcn5d0k7odcmmagf76ki" xml:space="preserve">&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, AstroAlgebra!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;</text>
      <sha1>0qd0n6x0e8lxcn5d0k7odcmmagf76ki</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Dokidokis</title>
    <ns>3</ns>
    <id>276639</id>
    <revision>
      <id>4669046</id>
      <parentid>3417540</parentid>
      <timestamp>2026-09-06T06:32:34Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669046</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4484" sha1="q16z3c8eal9rfhardgkgn7bzyry6xiv" xml:space="preserve">&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Scchriz!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;
--[[User:Pi zero|Pi zero]] ([[User talk:Pi zero|discuss]] • [[Special:Contributions/Pi zero|contribs]]) 12:09, 14 August 2012 (UTC)</text>
      <sha1>q16z3c8eal9rfhardgkgn7bzyry6xiv</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Lisa Svenska</title>
    <ns>3</ns>
    <id>276944</id>
    <revision>
      <id>4669045</id>
      <parentid>4594987</parentid>
      <timestamp>2026-09-06T06:31:50Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669045</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2453" sha1="l19uy2hovlsiy14jldyf8gvonapneyx" xml:space="preserve">{| style=&quot;margin: 1em auto 1em auto&quot;
|+
|-
| 
{| style=&quot;text-align:center; border: 1px solid #000000; background-color:#F8EFFF;{{text default color}};&quot;
|-  style=&quot;padding:1em;padding-top:0.5em;&quot; 
|style=&quot;font-size: 85%&quot;|'''This is a &amp;#x0057;&amp;#x0069;&lt;!-- Wikipedia --&gt;&amp;#x006B;&amp;#x0069;&amp;#x0070;&amp;#x0065;&amp;#x0064;&amp;#x0069;&amp;#x0061; user talk page.'''

If you find this page on any site other than &amp;#x0057;&amp;#x0069;&lt;!-- Wikipedia --&gt;&amp;#x006B;&amp;#x0069;&amp;#x0070;&amp;#x0065;&amp;#x0064;&amp;#x0069;&amp;#x0061;, you are viewing a mirror site. Be aware that the page may be outdated, and that the user this page belongs to may have no personal affiliation with any site other than &amp;#x0057;&amp;#x0069;&lt;!-- Wikipedia --&gt;&amp;#x006B;&amp;#x0069;&amp;#x0070;&amp;#x0065;&amp;#x0064;&amp;#x0069;&amp;#x0061; itself. The original page is located at http://en.wiki&lt;!----&gt;pedia.org/wiki/{{FULLPAGENAMEE}}.
|}
{| width=&quot;100%&quot; align=&quot;center&quot; cellspacing=&quot;3&quot; style=&quot;border: 1px solid #000000; background-color: #F8EFFF;{{text default color}}; margin-bottom: 0px;&quot;
|align=center|'''This is the [[Wikipedia:Talk_page#User_talk_pages|User talk page]] for [[User:{{PAGENAME}}|{{PAGENAME}}]] '''
|}

{| width=&quot;100%&quot; align=&quot;center&quot; cellspacing=&quot;3&quot; style=&quot;border: 1px solid #000000; background-color: #F8FCFF;{{text default color}}; margin-bottom: 3px;&quot;
|align=left|
{| width=&quot;100%&quot; align=&quot;left&quot; cellspacing=&quot;10&quot; style=&quot;border: 0px solid #000000; background-color: #F8FCFF;{{text default color}}; margin-bottom: 0px;&quot;
|align=left valign=middle|Please sign your comments using four tildes (&amp;#126;&amp;#126;&amp;#126;&amp;#126;). Place comments that start a new topic at the bottom of the page by [{{fullurl:{{ns:3}}:{{PAGENAMEE}}|action=edit&amp;section=new}} starting a new thread]&lt;!--and give them a &lt;nowiki&gt;==A Descriptive Header==&lt;/nowiki&gt;--&gt;. If you're new to Wikipedia, please see [[Wikipedia:Introduction|Welcome to Wikipedia]] and [[Wikipedia:FAQ|frequently asked questions]]. 
|}
|align=right valign=middle| 
{| width=&quot;90%&quot; align=&quot;center&quot; cellspacing=&quot;3&quot; style=&quot;border: 1px solid #000000; background-color: #F8EFFF;{{text default color}}; margin-left: 20px; margin-bottom: 0px; margin-right: 3px;&quot;
|align=center|'''[[Wikipedia:Talk page guidelines|Talk page guidelines]]'''
|-
|align=center|Please respect [[Wikipedia:Wikiquette|Wikiquette]], [[Wikipedia:Assume good faith|assume good faith]] and [[Wikipedia:no personal attacks|be nice]], and bear in mind [[Wikipedia:What Wikipedia is not|what Wikipedia is not]].
|}
|}
|+
|-
|  
|+
|-
|
|}</text>
      <sha1>l19uy2hovlsiy14jldyf8gvonapneyx</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Areil314</title>
    <ns>3</ns>
    <id>277010</id>
    <revision>
      <id>4669047</id>
      <parentid>2398999</parentid>
      <timestamp>2026-09-06T06:33:21Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669047</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4351" sha1="d6wuk3li6tv65u76yqcvnvae921zlcs" xml:space="preserve">&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Areil314!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;</text>
      <sha1>d6wuk3li6tv65u76yqcvnvae921zlcs</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Avocato</title>
    <ns>3</ns>
    <id>277237</id>
    <revision>
      <id>4669044</id>
      <parentid>2402036</parentid>
      <timestamp>2026-09-06T06:30:57Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669044</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="742" sha1="2exlkgy7yimeangumn0rfqeh69zz80b" xml:space="preserve">&lt;div dir=ltr&gt;&lt;div style=&quot;background: #FFFFFF;{{text default color}}; text-align: center; font-family: Calibri; font-size: 1.6em; font-weight: bold;&quot;&gt;&lt;div style=&quot;padding: 5px; border: 3px solid #003882; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius: 10px;&quot;&gt;Please, Do not leave your message here. You can contact me using any of the following:
&lt;div style=&quot;margin-top: 10px; padding: 2px; background: #f4f3f0;{{text default color}}; border: 2px solid #fb139e; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius: 10px;&quot;&gt;[[w:ar:User talk:Avocato|w:ar:user talk:Avocato]] &amp;#124; [[w:en:User talk:Avocato|w:en:user talk:Avocato]] &amp;#124; [[m:User talk:Avocato|meta:user talk:Avocato]]&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</text>
      <sha1>2exlkgy7yimeangumn0rfqeh69zz80b</sha1>
    </revision>
  </page>
  <page>
    <title>User:Writ3562</title>
    <ns>2</ns>
    <id>278077</id>
    <revision>
      <id>4669012</id>
      <parentid>2412275</parentid>
      <timestamp>2026-09-05T19:28:15Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669012</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1716" sha1="6w4p5ypjho855kjpwt8chj8u2ybfeqo" xml:space="preserve">==About writ3562==
{| align=&quot;right&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; width=&quot;350px&quot;
! style=&quot;background:#efefef;{{Text default color}}; text-align:right; vertical-align:top&quot;| Name:
| writ3562

|-
! style=&quot;background:#efefef;{{Text default color}}; text-align:right; vertical-align:top&quot;| Hometown:
| Midwest, USA

|-
! style=&quot;background:#efefef;{{Text default color}}; text-align:right; vertical-align:top&quot;| Current Home:
| Midwest, USA

|-
! style=&quot;background:#efefef;{{Text default color}}; text-align:right; vertical-align:top&quot;| Education:
| College of Education and Human Development&lt;br&gt;Big Ten University&lt;br&gt;
 

|-
! style=&quot;background:#efefef;{{Text default color}}; text-align:right; vertical-align:top&quot;| Websites:
| [http://www.pinterest.com My favorite website]
[http://www.tumblr.com Another fun website]&lt;br&gt;


|}
=About Me=
I am a college student at Big Ten University in the United States. I grew up in a small town, but love big cities. 

=Academics=
I am halfway through my college degree, but plan on attending Graduate school after obtaining my undergraduate degree. My focus is on languages and healthcare. My main goal is to find a career I am passionate about and help the people around me. 

=Interests=

I love to travel the world and the United States. Two of my favorite things to do are read and run. I am an aspiring cook; I loved to try new, healthy recipes. I am an animal lover and cannot wait to be able to have time for my own pet. 

=Family=

My family is extremely important to me. My immediate family is small, but I grew up surrounded by my extended family whom I am very close to. I also have a dog who I consider to be my baby. She is definitely the princess of our family.</text>
      <sha1>6w4p5ypjho855kjpwt8chj8u2ybfeqo</sha1>
    </revision>
  </page>
  <page>
    <title>Structural Biochemistry/Vyvanse</title>
    <ns>0</ns>
    <id>281983</id>
    <revision>
      <id>4669094</id>
      <parentid>3117667</parentid>
      <timestamp>2026-09-06T10:31:05Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <comment>typo</comment>
      <origin>4669094</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1881" sha1="cpeaif44ua529l016mp23j6wwenql7l" xml:space="preserve">==Introduction==
[[Image:Lisdexamfetamine.svg|250px|thumb|Lisdexamfetamine]]

''Vyvanse'' is a nervous controlled medication used to treat people with attention deficit hyperactivity disorder (ADHD) who show symptoms of loss of memory or having difficulty focusing. Its structure consists of dextroamphetamine with an amino acid L-lysine. ADHD is caused by some of the natural substances in the brain, and Vyvanse can help to manipulate the amount of these substances to work properly. Vyvanse also helps patients dealing with particular symptoms of ADHD; it can increasing their attention and decrease the impulsiveness.

==History and Usage==
Vyvanse was developed by New River Pharmaceuticals and has been on the market since 2008. Vyvanse can be taken directly by mouth and usually in the morning because it can cause difficulty in sleeping if you take it in late afternoon or at night. It is suggested that Vyvanse should not be taken more than what it is prescribed because it can cause some severe side effects. A doctor will probably prescribe a patient with a low dose to see how their body can adapt to the medication. Oftentimes, the physician will adjust the dosage during a patient's treament. Besides taking Vyvanse as a part of a complete treatment, patients with ADHD should follow up with other therapies.

==Side Effects==
Because Vyvanse can lead to dependence or addiction, it should be used properly. Just as other drugs, Vyvanse does have some common side effects:
*Difficulty falling asleep
*Stomach pain
*Flu, fever, sweating
*Headache, dizziness, diarrhoea.

But for some people, this drug can have some serious side effects: 
*Seizures
*Vision problems
*Slowing of growth in children
*Worsening of sudden

A doctor should be contacted if these side effects occur.

==References==
http://www.drugs.com/pro/vyvanse.html

http://www.vyvanse.com/

{{BookCat}}</text>
      <sha1>cpeaif44ua529l016mp23j6wwenql7l</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/Platforms/Arm Raspberry Pi support</title>
    <ns>0</ns>
    <id>286123</id>
    <revision>
      <id>4668931</id>
      <parentid>4668855</parentid>
      <timestamp>2026-09-05T12:41:43Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668931</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="93636" sha1="788x7cxdpgtal4i28fcmtk17j5er7z4" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

==Introduction==

[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 1Gb+ RAM ideally as you may have to switch to 256Mb gfx mode depending on the application running - it is still a work in progress 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power 
nothing else is done especially CSI DSI etc 
*Up to Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


Pi500+ keyboard wedge - 

Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok but not great - wifi and lan ethernet partial working but no web browser to fully test - 


* Pi 5 - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 (Rev1.0) or D0 (rev1.1) 
* Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with heatsinks on 3b to prevent cpu 80C+ overheating 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


'''Download''' [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd and copied to fat32 8GB+ microSD card (there will be folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=60&amp;pid=13363#post_13363 Aros Raspberry pi 3 64bit thread] 

Boots with '''USB3''' based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb boot it works if a little slower than SD card 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon Prefs needed? 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 


[[File:Wifi00.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi01.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi02.png|thumb|Setup wifi on Aros Pi3b]]

Wifi setup needs the network prefs with the TCP/IP tab click add interface -&gt; change Device to bwfm.device as net0:, IP Mode as DHCP and IPv4 

Once you’ve configured the device, simply save the Wireless Networks tab Wi-Fi configuration even if it’s empty. This will create the Wireless.prefs file in the Env-Archive/SYS directory, and you’ll automatically see the Wireless Manager icon in Wanderer. Although a reboot maybe necessary. Wireless tab gets your router settings. 

If it does not set to start at boot, settings are preserved. Instead, add this to the user-startup:
&lt;pre&gt;
execute sys:system/network/arostcp/s/startnet
run wirelessmanager device=bwfm.device &gt;nil:
&lt;/pre&gt;
Network will start automatically on boot. If you don't want the wirelessmanager icon on Wanderer desktop, just add 'nogui' to the wirelessmanager line


Lan ethernet port on 
*lan9514  Pi3b Pi2 no support at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device  


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 


Only the Pi5 has a RTC real time clock, the other Pis will need to use [https://aminet.net/package/util/time/NTPSync ntpsync] or similar to get the date and time from the internet 


USB classes support from Prefs/Trident is still work in process 
*usbaudio not working as no rt isochronous on usb2otg (white or black) for pi3b and zero 2w but '''working''' on usb3 port (blue) on pi4, 400 
*camdusbmidi no class compiled but eventually 64bit ports of [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], 


Regarding 680x0 emulation, there are several options that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


The status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use MACAros github for discussion, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 
*[ PiMiga] 

*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behaviour, and that shorting the power supplies can cause instant death of the Pi.


In the shell 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ - work in process 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Linux hosted Pi build] 

[https://github.com/BlitterStudio/aros-compiler-docker Aros Docker for various systems], 

[https://github.com/aros-development-team/AROS/commit/d84b9a337f9aa059154d9af69275935125166bdd Apple Silicon support]


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo 20TOPs
*2026 RPI AI HAT+ 2 - Hailo  40TOPs 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE-HAT Power Over Ethernet Hat 
*2020 Raspberry Pi PoE+HAT Power Over Ethernet Hat 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 

=== GPU ===

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No
hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent
years. It is the job of graphics HIDDs to allocate bitmaps etc. so that
they have the most suitable characteristics, including allocating them
from GPU RAM where possible. The concept of chip RAM is only for legacy
code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS/OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs are a bit weird and far from optimal, especially MorphOS one, because it aims for m68k binary compatibility.
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?
 
I have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

I so far have -:
 
vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and  returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,
 
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer.
don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses)

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.

Why did usbromstartup become HW-specific ?
In  the  past i have done a big job separating kickstart into several parts. I have never got any responses, so i re-describe my idea.

For now it loads the hs otg chipset driver ..

The  idea  is  to minimize amount of archirecture-specific modules to
    make   user's  life  easier.  So,  the kickstart was split into 'base'
    (which  does  not  contain anything machine-specific) and 'BSP' (Board
    Support Package) which contains all hardware-specific stuff.
     This  way,  for  example, distribution makers can save up space on CD
    and  make  CDs with multiple platform support. Different configuration
    would load the same base with different BSP's.
     Next  there  was some part which is entirely missing on hosted. These
    are   filesystems.  Hosted  ports  do  not need them to boot up, so on
    hosted   they  are  left  out.  At  the  other  hand,  they  are  also
    architecture-agnostic.  So  i put them into 'FS' package (standing for
    'filesystem').

     Poseidon  is  one  more  big part. I made it into separate package in
    order to allow users to omit it if they don't need it (for example, to
    run  on retro PCs without USB). Personally i have one. Again, Poseidon
    is  hardware-agnostic (well, there are USB drivers but HCIs are pretty
    standard).

It's mandatory on PI since there are no other interface types - so being a separate package is irrelevant/pointless.

Is Raspberry's USB controller non-HCI compliant? Actually i expect it to be compliant, then wouldn't it be better to make existing drivers discovering them? 
 
AFAIK its HCI 1.0 compliant but I'm not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.


* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI]

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*Green BentoIO CMX0 - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued sadly, 3 x Pi4 probably better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box with pi4 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


{{BookCat}}</text>
      <sha1>788x7cxdpgtal4i28fcmtk17j5er7z4</sha1>
    </revision>
    <revision>
      <id>4668936</id>
      <parentid>4668931</parentid>
      <timestamp>2026-09-05T13:18:54Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668936</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="93628" sha1="jwdttynx1ttuo17ld89xzaibbkws27f" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

==Introduction==

[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 1Gb+ RAM ideally as you may have to switch to 256Mb gfx mode depending on the application running - it is still a work in progress 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power 
nothing else is done especially CSI DSI etc 
*Up to Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


Pi500+ keyboard wedge - 

Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok but not great - wifi and lan ethernet partial working but no web browser to fully test - 


* Pi 5 - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 (Rev1.0) or D0 (rev1.1) 
* Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with heatsinks on 3b to prevent cpu 80C+ overheating 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


'''Download''' [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd and copied to fat32 8GB+ microSD card (there will be folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=60&amp;pid=13363#post_13363 Aros Raspberry pi 3 64bit thread] 

Boots with '''USB3''' based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb boot it works, double time of SD card 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon Prefs needed? 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 


[[File:Wifi00.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi01.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi02.png|thumb|Setup wifi on Aros Pi3b]]

Wifi setup needs the network prefs with the TCP/IP tab click add interface -&gt; change Device to bwfm.device as net0:, IP Mode as DHCP and IPv4 

Once you’ve configured the device, simply save the Wireless Networks tab Wi-Fi configuration even if it’s empty. This will create the Wireless.prefs file in the Env-Archive/SYS directory, and you’ll automatically see the Wireless Manager icon in Wanderer. Although a reboot maybe necessary. Wireless tab gets your router settings. 

If it does not set to start at boot, settings are preserved. Instead, add this to the user-startup:
&lt;pre&gt;
execute sys:system/network/arostcp/s/startnet
run wirelessmanager device=bwfm.device &gt;nil:
&lt;/pre&gt;
Network will start automatically on boot. If you don't want the wirelessmanager icon on Wanderer desktop, just add 'nogui' to the wirelessmanager line


Lan ethernet port on 
*lan9514  Pi3b Pi2 no support at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device  


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 


Only the Pi5 has a RTC real time clock, the other Pis will need to use [https://aminet.net/package/util/time/NTPSync ntpsync] or similar to get the date and time from the internet 


USB classes support from Prefs/Trident is still work in process 
*usbaudio not working as no rt isochronous on usb2otg (white or black) for pi3b and zero 2w but '''working''' on usb3 port (blue) on pi4, 400 
*camdusbmidi no class compiled but eventually 64bit ports of [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], 


Regarding 680x0 emulation, there are several options that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


The status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use MACAros github for discussion, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 
*[ PiMiga] 

*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behaviour, and that shorting the power supplies can cause instant death of the Pi.


In the shell 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ - work in process 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Linux hosted Pi build] 

[https://github.com/BlitterStudio/aros-compiler-docker Aros Docker for various systems], 

[https://github.com/aros-development-team/AROS/commit/d84b9a337f9aa059154d9af69275935125166bdd Apple Silicon support]


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo 20TOPs
*2026 RPI AI HAT+ 2 - Hailo  40TOPs 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE-HAT Power Over Ethernet Hat 
*2020 Raspberry Pi PoE+HAT Power Over Ethernet Hat 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 

=== GPU ===

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No
hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent
years. It is the job of graphics HIDDs to allocate bitmaps etc. so that
they have the most suitable characteristics, including allocating them
from GPU RAM where possible. The concept of chip RAM is only for legacy
code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS/OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs are a bit weird and far from optimal, especially MorphOS one, because it aims for m68k binary compatibility.
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?
 
I have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

I so far have -:
 
vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and  returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,
 
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer.
don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses)

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.

Why did usbromstartup become HW-specific ?
In  the  past i have done a big job separating kickstart into several parts. I have never got any responses, so i re-describe my idea.

For now it loads the hs otg chipset driver ..

The  idea  is  to minimize amount of archirecture-specific modules to
    make   user's  life  easier.  So,  the kickstart was split into 'base'
    (which  does  not  contain anything machine-specific) and 'BSP' (Board
    Support Package) which contains all hardware-specific stuff.
     This  way,  for  example, distribution makers can save up space on CD
    and  make  CDs with multiple platform support. Different configuration
    would load the same base with different BSP's.
     Next  there  was some part which is entirely missing on hosted. These
    are   filesystems.  Hosted  ports  do  not need them to boot up, so on
    hosted   they  are  left  out.  At  the  other  hand,  they  are  also
    architecture-agnostic.  So  i put them into 'FS' package (standing for
    'filesystem').

     Poseidon  is  one  more  big part. I made it into separate package in
    order to allow users to omit it if they don't need it (for example, to
    run  on retro PCs without USB). Personally i have one. Again, Poseidon
    is  hardware-agnostic (well, there are USB drivers but HCIs are pretty
    standard).

It's mandatory on PI since there are no other interface types - so being a separate package is irrelevant/pointless.

Is Raspberry's USB controller non-HCI compliant? Actually i expect it to be compliant, then wouldn't it be better to make existing drivers discovering them? 
 
AFAIK its HCI 1.0 compliant but I'm not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.


* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI]

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*Green BentoIO CMX0 - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued sadly, 3 x Pi4 probably better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box with pi4 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


{{BookCat}}</text>
      <sha1>jwdttynx1ttuo17ld89xzaibbkws27f</sha1>
    </revision>
    <revision>
      <id>4668937</id>
      <parentid>4668936</parentid>
      <timestamp>2026-09-05T13:30:50Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668937</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="93628" sha1="s9skvae7riexe51pe1x46xw6j2lag7x" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

==Introduction==

[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 1Gb+ RAM ideally as you may have to switch to 256Mb gfx mode depending on the application running - it is still a work in progress 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power 
nothing else is done especially CSI DSI etc 
*Up to Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


Pi500+ keyboard wedge - 

Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok but not great - wifi and lan ethernet partial working but no web browser to fully test - 


* Pi 5 - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 (Rev1.0) or D0 (rev1.1) 
* Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with heatsinks on 3b to prevent cpu 80C+ overheating 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


'''Download''' [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd and copied to fat32 8GB+ microSD card (there will be folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=60&amp;pid=13363#post_13363 Aros Raspberry pi 3 64bit thread] 

Boots with '''USB3''' based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb boot it works but slower than SD card 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon Prefs needed? 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 


[[File:Wifi00.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi01.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi02.png|thumb|Setup wifi on Aros Pi3b]]

Wifi setup needs the network prefs with the TCP/IP tab click add interface -&gt; change Device to bwfm.device as net0:, IP Mode as DHCP and IPv4 

Once you’ve configured the device, simply save the Wireless Networks tab Wi-Fi configuration even if it’s empty. This will create the Wireless.prefs file in the Env-Archive/SYS directory, and you’ll automatically see the Wireless Manager icon in Wanderer. Although a reboot maybe necessary. Wireless tab gets your router settings. 

If it does not set to start at boot, settings are preserved. Instead, add this to the user-startup:
&lt;pre&gt;
execute sys:system/network/arostcp/s/startnet
run wirelessmanager device=bwfm.device &gt;nil:
&lt;/pre&gt;
Network will start automatically on boot. If you don't want the wirelessmanager icon on Wanderer desktop, just add 'nogui' to the wirelessmanager line


Lan ethernet port on 
*lan9514  Pi3b Pi2 no support at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device  


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 


Only the Pi5 has a RTC real time clock, the other Pis will need to use [https://aminet.net/package/util/time/NTPSync ntpsync] or similar to get the date and time from the internet 


USB classes support from Prefs/Trident is still work in process 
*usbaudio not working as no rt isochronous on usb2otg (white or black) for pi3b and zero 2w but '''working''' on usb3 port (blue) on pi4, 400 
*camdusbmidi no class compiled but eventually 64bit ports of [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], 


Regarding 680x0 emulation, there are several options that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


The status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use MACAros github for discussion, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 
*[ PiMiga] 

*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behaviour, and that shorting the power supplies can cause instant death of the Pi.


In the shell 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ - work in process 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Linux hosted Pi build] 

[https://github.com/BlitterStudio/aros-compiler-docker Aros Docker for various systems], 

[https://github.com/aros-development-team/AROS/commit/d84b9a337f9aa059154d9af69275935125166bdd Apple Silicon support]


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo 20TOPs
*2026 RPI AI HAT+ 2 - Hailo  40TOPs 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE-HAT Power Over Ethernet Hat 
*2020 Raspberry Pi PoE+HAT Power Over Ethernet Hat 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 

=== GPU ===

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No
hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent
years. It is the job of graphics HIDDs to allocate bitmaps etc. so that
they have the most suitable characteristics, including allocating them
from GPU RAM where possible. The concept of chip RAM is only for legacy
code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS/OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs are a bit weird and far from optimal, especially MorphOS one, because it aims for m68k binary compatibility.
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?
 
I have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

I so far have -:
 
vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and  returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,
 
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer.
don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses)

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.

Why did usbromstartup become HW-specific ?
In  the  past i have done a big job separating kickstart into several parts. I have never got any responses, so i re-describe my idea.

For now it loads the hs otg chipset driver ..

The  idea  is  to minimize amount of archirecture-specific modules to
    make   user's  life  easier.  So,  the kickstart was split into 'base'
    (which  does  not  contain anything machine-specific) and 'BSP' (Board
    Support Package) which contains all hardware-specific stuff.
     This  way,  for  example, distribution makers can save up space on CD
    and  make  CDs with multiple platform support. Different configuration
    would load the same base with different BSP's.
     Next  there  was some part which is entirely missing on hosted. These
    are   filesystems.  Hosted  ports  do  not need them to boot up, so on
    hosted   they  are  left  out.  At  the  other  hand,  they  are  also
    architecture-agnostic.  So  i put them into 'FS' package (standing for
    'filesystem').

     Poseidon  is  one  more  big part. I made it into separate package in
    order to allow users to omit it if they don't need it (for example, to
    run  on retro PCs without USB). Personally i have one. Again, Poseidon
    is  hardware-agnostic (well, there are USB drivers but HCIs are pretty
    standard).

It's mandatory on PI since there are no other interface types - so being a separate package is irrelevant/pointless.

Is Raspberry's USB controller non-HCI compliant? Actually i expect it to be compliant, then wouldn't it be better to make existing drivers discovering them? 
 
AFAIK its HCI 1.0 compliant but I'm not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.


* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI]

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*Green BentoIO CMX0 - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued sadly, 3 x Pi4 probably better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box with pi4 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


{{BookCat}}</text>
      <sha1>s9skvae7riexe51pe1x46xw6j2lag7x</sha1>
    </revision>
    <revision>
      <id>4668940</id>
      <parentid>4668937</parentid>
      <timestamp>2026-09-05T13:39:57Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668940</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="93632" sha1="av3gem5g0d7mrfduu0ttpdkr6zayvwp" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

==Introduction==

[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 1Gb+ RAM ideally as you may have to switch to 256Mb gfx mode depending on the application running - it is still a work in progress 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power 
nothing else is done especially CSI DSI etc 
*Up to Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


Pi500+ keyboard wedge - 

Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok but not great - wifi and lan ethernet partial working but no web browser to fully test - 


* Pi 5 - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 (Rev1.0) or D0 (rev1.1) 
* Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with heatsinks on 3b to prevent cpu 80C+ overheating 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


'''Download''' [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd and copied to fat32 8GB+ microSD card (there will be folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=60&amp;pid=13363#post_13363 Aros Raspberry pi 3 64bit thread] 

Boots with '''USB3''' based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb boot it works but slower than SD card 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 


[[File:Wifi00.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi01.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi02.png|thumb|Setup wifi on Aros Pi3b]]

Wifi setup needs the network prefs with the TCP/IP tab click add interface -&gt; change Device to bwfm.device as net0:, IP Mode as DHCP and IPv4 

Once you’ve configured the device, simply save the Wireless Networks tab Wi-Fi configuration even if it’s empty. This will create the Wireless.prefs file in the Env-Archive/SYS directory, and you’ll automatically see the Wireless Manager icon in Wanderer. Although a reboot maybe necessary. Wireless tab gets your router settings. 

If it does not set to start at boot, settings are preserved. Instead, add this to the user-startup:
&lt;pre&gt;
execute sys:system/network/arostcp/s/startnet
run wirelessmanager device=bwfm.device &gt;nil:
&lt;/pre&gt;
Network will start automatically on boot. If you don't want the wirelessmanager icon on Wanderer desktop, just add 'nogui' to the wirelessmanager line


Lan ethernet port on 
*lan9514  Pi3b Pi2 no support at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device  


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 


Only the Pi5 has a RTC real time clock, the other Pis will need to use [https://aminet.net/package/util/time/NTPSync ntpsync] or similar to get the date and time from the internet 


USB classes support from Prefs/Trident is still work in process 
*usbaudio not working as no rt isochronous on usb2otg (white or black) for pi3b and zero 2w but '''working''' on usb3 port (blue) on pi4, 400 
*camdusbmidi no class compiled but eventually 64bit ports of [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], 


Regarding 680x0 emulation, there are several options that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


The status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use MACAros github for discussion, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 
*[ PiMiga] 

*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behaviour, and that shorting the power supplies can cause instant death of the Pi.


In the shell 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ - work in process 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Linux hosted Pi build] 

[https://github.com/BlitterStudio/aros-compiler-docker Aros Docker for various systems], 

[https://github.com/aros-development-team/AROS/commit/d84b9a337f9aa059154d9af69275935125166bdd Apple Silicon support]


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo 20TOPs
*2026 RPI AI HAT+ 2 - Hailo  40TOPs 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE-HAT Power Over Ethernet Hat 
*2020 Raspberry Pi PoE+HAT Power Over Ethernet Hat 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 

=== GPU ===

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No
hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent
years. It is the job of graphics HIDDs to allocate bitmaps etc. so that
they have the most suitable characteristics, including allocating them
from GPU RAM where possible. The concept of chip RAM is only for legacy
code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS/OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs are a bit weird and far from optimal, especially MorphOS one, because it aims for m68k binary compatibility.
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?
 
I have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

I so far have -:
 
vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and  returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,
 
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer.
don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses)

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.

Why did usbromstartup become HW-specific ?
In  the  past i have done a big job separating kickstart into several parts. I have never got any responses, so i re-describe my idea.

For now it loads the hs otg chipset driver ..

The  idea  is  to minimize amount of archirecture-specific modules to
    make   user's  life  easier.  So,  the kickstart was split into 'base'
    (which  does  not  contain anything machine-specific) and 'BSP' (Board
    Support Package) which contains all hardware-specific stuff.
     This  way,  for  example, distribution makers can save up space on CD
    and  make  CDs with multiple platform support. Different configuration
    would load the same base with different BSP's.
     Next  there  was some part which is entirely missing on hosted. These
    are   filesystems.  Hosted  ports  do  not need them to boot up, so on
    hosted   they  are  left  out.  At  the  other  hand,  they  are  also
    architecture-agnostic.  So  i put them into 'FS' package (standing for
    'filesystem').

     Poseidon  is  one  more  big part. I made it into separate package in
    order to allow users to omit it if they don't need it (for example, to
    run  on retro PCs without USB). Personally i have one. Again, Poseidon
    is  hardware-agnostic (well, there are USB drivers but HCIs are pretty
    standard).

It's mandatory on PI since there are no other interface types - so being a separate package is irrelevant/pointless.

Is Raspberry's USB controller non-HCI compliant? Actually i expect it to be compliant, then wouldn't it be better to make existing drivers discovering them? 
 
AFAIK its HCI 1.0 compliant but I'm not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.


* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI]

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*Green BentoIO CMX0 - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued sadly, 3 x Pi4 probably better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box with pi4 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


{{BookCat}}</text>
      <sha1>av3gem5g0d7mrfduu0ttpdkr6zayvwp</sha1>
    </revision>
    <revision>
      <id>4668941</id>
      <parentid>4668940</parentid>
      <timestamp>2026-09-05T14:40:50Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668941</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="93634" sha1="tlrughq2epuzgpjg6p5q3lw8bx2x986" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

==Introduction==

[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 1Gb+ RAM ideally as you may have to switch to 256Mb gfx mode depending on the application running - it is still a work in progress 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power 
nothing else is done especially CSI DSI etc 
*Up to Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


Pi500+ keyboard wedge - 

Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok but not great - wifi and lan ethernet partial working but no web browser to fully test - 


* Pi 5 - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 (Rev1.0) or D0 (rev1.1) 
* Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with heatsink/fan on 3b to prevent cpu 82C+ throttling 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


'''Download''' [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd and copied to fat32 8GB+ microSD card (there will be folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=60&amp;pid=13363#post_13363 Aros Raspberry pi 3 64bit thread] 

Boots with '''USB3''' based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb boot it works but slower than SD card 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 


[[File:Wifi00.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi01.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi02.png|thumb|Setup wifi on Aros Pi3b]]

Wifi setup needs the network prefs with the TCP/IP tab click add interface -&gt; change Device to bwfm.device as net0:, IP Mode as DHCP and IPv4 

Once you’ve configured the device, simply save the Wireless Networks tab Wi-Fi configuration even if it’s empty. This will create the Wireless.prefs file in the Env-Archive/SYS directory, and you’ll automatically see the Wireless Manager icon in Wanderer. Although a reboot maybe necessary. Wireless tab gets your router settings. 

If it does not set to start at boot, settings are preserved. Instead, add this to the user-startup:
&lt;pre&gt;
execute sys:system/network/arostcp/s/startnet
run wirelessmanager device=bwfm.device &gt;nil:
&lt;/pre&gt;
Network will start automatically on boot. If you don't want the wirelessmanager icon on Wanderer desktop, just add 'nogui' to the wirelessmanager line


Lan ethernet port on 
*lan9514  Pi3b Pi2 no support at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device  


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 


Only the Pi5 has a RTC real time clock, the other Pis will need to use [https://aminet.net/package/util/time/NTPSync ntpsync] or similar to get the date and time from the internet 


USB classes support from Prefs/Trident is still work in process 
*usbaudio not working as no rt isochronous on usb2otg (white or black) for pi3b and zero 2w but '''working''' on usb3 port (blue) on pi4, 400 
*camdusbmidi no class compiled but eventually 64bit ports of [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], 


Regarding 680x0 emulation, there are several options that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


The status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use MACAros github for discussion, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 
*[ PiMiga] 

*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behaviour, and that shorting the power supplies can cause instant death of the Pi.


In the shell 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ - work in process 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Linux hosted Pi build] 

[https://github.com/BlitterStudio/aros-compiler-docker Aros Docker for various systems], 

[https://github.com/aros-development-team/AROS/commit/d84b9a337f9aa059154d9af69275935125166bdd Apple Silicon support]


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo 20TOPs
*2026 RPI AI HAT+ 2 - Hailo  40TOPs 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE-HAT Power Over Ethernet Hat 
*2020 Raspberry Pi PoE+HAT Power Over Ethernet Hat 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 

=== GPU ===

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No
hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent
years. It is the job of graphics HIDDs to allocate bitmaps etc. so that
they have the most suitable characteristics, including allocating them
from GPU RAM where possible. The concept of chip RAM is only for legacy
code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS/OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs are a bit weird and far from optimal, especially MorphOS one, because it aims for m68k binary compatibility.
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?
 
I have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

I so far have -:
 
vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and  returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,
 
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer.
don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses)

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.

Why did usbromstartup become HW-specific ?
In  the  past i have done a big job separating kickstart into several parts. I have never got any responses, so i re-describe my idea.

For now it loads the hs otg chipset driver ..

The  idea  is  to minimize amount of archirecture-specific modules to
    make   user's  life  easier.  So,  the kickstart was split into 'base'
    (which  does  not  contain anything machine-specific) and 'BSP' (Board
    Support Package) which contains all hardware-specific stuff.
     This  way,  for  example, distribution makers can save up space on CD
    and  make  CDs with multiple platform support. Different configuration
    would load the same base with different BSP's.
     Next  there  was some part which is entirely missing on hosted. These
    are   filesystems.  Hosted  ports  do  not need them to boot up, so on
    hosted   they  are  left  out.  At  the  other  hand,  they  are  also
    architecture-agnostic.  So  i put them into 'FS' package (standing for
    'filesystem').

     Poseidon  is  one  more  big part. I made it into separate package in
    order to allow users to omit it if they don't need it (for example, to
    run  on retro PCs without USB). Personally i have one. Again, Poseidon
    is  hardware-agnostic (well, there are USB drivers but HCIs are pretty
    standard).

It's mandatory on PI since there are no other interface types - so being a separate package is irrelevant/pointless.

Is Raspberry's USB controller non-HCI compliant? Actually i expect it to be compliant, then wouldn't it be better to make existing drivers discovering them? 
 
AFAIK its HCI 1.0 compliant but I'm not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.


* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI]

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*Green BentoIO CMX0 - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued sadly, 3 x Pi4 probably better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box with pi4 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


{{BookCat}}</text>
      <sha1>tlrughq2epuzgpjg6p5q3lw8bx2x986</sha1>
    </revision>
    <revision>
      <id>4668942</id>
      <parentid>4668941</parentid>
      <timestamp>2026-09-05T14:44:10Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668942</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="93613" sha1="6qqyi29ke9gpwv9jjlxbb0lslz5gi53" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

==Introduction==

[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 1Gb+ RAM ideally as you may have to switch to 256Mb gfx mode depending on the application running - it is still a work in progress 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power 
nothing else is done especially CSI DSI etc 
*Up to Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


Pi500+ keyboard wedge - 

Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok but not great - wifi and lan ethernet partial working but no web browser to fully test - 


* Pi 5 - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 (Rev1.0) or D0 (rev1.1) 
* Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with heatsink/fan on 3b to prevent cpu 82C+ throttling 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


'''Download''' [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd and copied to fat32 8GB+ microSD card (there will be folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 Aros Raspberry pi 3 64bit thread] 

Boots with '''USB3''' based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb boot it works but slower than SD card 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 


[[File:Wifi00.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi01.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi02.png|thumb|Setup wifi on Aros Pi3b]]

Wifi setup needs the network prefs with the TCP/IP tab click add interface -&gt; change Device to bwfm.device as net0:, IP Mode as DHCP and IPv4 

Once you’ve configured the device, simply save the Wireless Networks tab Wi-Fi configuration even if it’s empty. This will create the Wireless.prefs file in the Env-Archive/SYS directory, and you’ll automatically see the Wireless Manager icon in Wanderer. Although a reboot maybe necessary. Wireless tab gets your router settings. 

If it does not set to start at boot, settings are preserved. Instead, add this to the user-startup:
&lt;pre&gt;
execute sys:system/network/arostcp/s/startnet
run wirelessmanager device=bwfm.device &gt;nil:
&lt;/pre&gt;
Network will start automatically on boot. If you don't want the wirelessmanager icon on Wanderer desktop, just add 'nogui' to the wirelessmanager line


Lan ethernet port on 
*lan9514  Pi3b Pi2 no support at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device  


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 


Only the Pi5 has a RTC real time clock, the other Pis will need to use [https://aminet.net/package/util/time/NTPSync ntpsync] or similar to get the date and time from the internet 


USB classes support from Prefs/Trident is still work in process 
*usbaudio not working as no rt isochronous on usb2otg (white or black) for pi3b and zero 2w but '''working''' on usb3 port (blue) on pi4, 400 
*camdusbmidi no class compiled but eventually 64bit ports of [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], 


Regarding 680x0 emulation, there are several options that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


The status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use MACAros github for discussion, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 
*[ PiMiga] 

*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behaviour, and that shorting the power supplies can cause instant death of the Pi.


In the shell 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ - work in process 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Linux hosted Pi build] 

[https://github.com/BlitterStudio/aros-compiler-docker Aros Docker for various systems], 

[https://github.com/aros-development-team/AROS/commit/d84b9a337f9aa059154d9af69275935125166bdd Apple Silicon support]


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo 20TOPs
*2026 RPI AI HAT+ 2 - Hailo  40TOPs 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE-HAT Power Over Ethernet Hat 
*2020 Raspberry Pi PoE+HAT Power Over Ethernet Hat 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 

=== GPU ===

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No
hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent
years. It is the job of graphics HIDDs to allocate bitmaps etc. so that
they have the most suitable characteristics, including allocating them
from GPU RAM where possible. The concept of chip RAM is only for legacy
code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS/OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs are a bit weird and far from optimal, especially MorphOS one, because it aims for m68k binary compatibility.
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?
 
I have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

I so far have -:
 
vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and  returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,
 
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer.
don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses)

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.

Why did usbromstartup become HW-specific ?
In  the  past i have done a big job separating kickstart into several parts. I have never got any responses, so i re-describe my idea.

For now it loads the hs otg chipset driver ..

The  idea  is  to minimize amount of archirecture-specific modules to
    make   user's  life  easier.  So,  the kickstart was split into 'base'
    (which  does  not  contain anything machine-specific) and 'BSP' (Board
    Support Package) which contains all hardware-specific stuff.
     This  way,  for  example, distribution makers can save up space on CD
    and  make  CDs with multiple platform support. Different configuration
    would load the same base with different BSP's.
     Next  there  was some part which is entirely missing on hosted. These
    are   filesystems.  Hosted  ports  do  not need them to boot up, so on
    hosted   they  are  left  out.  At  the  other  hand,  they  are  also
    architecture-agnostic.  So  i put them into 'FS' package (standing for
    'filesystem').

     Poseidon  is  one  more  big part. I made it into separate package in
    order to allow users to omit it if they don't need it (for example, to
    run  on retro PCs without USB). Personally i have one. Again, Poseidon
    is  hardware-agnostic (well, there are USB drivers but HCIs are pretty
    standard).

It's mandatory on PI since there are no other interface types - so being a separate package is irrelevant/pointless.

Is Raspberry's USB controller non-HCI compliant? Actually i expect it to be compliant, then wouldn't it be better to make existing drivers discovering them? 
 
AFAIK its HCI 1.0 compliant but I'm not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.


* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI]

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*Green BentoIO CMX0 - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued sadly, 3 x Pi4 probably better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box with pi4 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


{{BookCat}}</text>
      <sha1>6qqyi29ke9gpwv9jjlxbb0lslz5gi53</sha1>
    </revision>
    <revision>
      <id>4668949</id>
      <parentid>4668942</parentid>
      <timestamp>2026-09-05T16:14:55Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4668949</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="93642" sha1="bd7pmzn1k2ck9ozfrdig8v9aq5xjkbt" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

==Introduction==

[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 1Gb+ RAM ideally as you may have to switch to 256Mb gfx mode depending on the application running - it is still a work in progress 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power 
nothing else is done especially CSI DSI etc 
*Up to Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


Pi500+ keyboard wedge - 

Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok but not great - wifi and lan ethernet partial working but no web browser to fully test - 


* Pi 5 - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 (Rev1.0) or D0 (rev1.1) 
* Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with heatsink/fan on 3b to prevent cpu 82C+ throttling 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


'''Download''' [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd and copied to fat32 8GB+ microSD card (there will be folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 Aros Raspberry pi 3 64bit thread] 

Boots with '''USB3''' based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb boot it works but slower than SD card 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 


[[File:Wifi00.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi01.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi02.png|thumb|Setup wifi on Aros Pi3b]]

Wifi setup needs the network prefs with the TCP/IP tab click add interface -&gt; change Device to bwfm.device as net0:, IP Mode as DHCP and IPv4 

Once you’ve configured the device, simply save the Wireless Networks tab Wi-Fi configuration even if it’s empty. This will create the Wireless.prefs file in the Env-Archive/SYS directory, and you’ll automatically see the Wireless Manager icon in Wanderer. Although a reboot maybe necessary. Wireless tab gets your router settings. 

If it does not set to start at boot, settings are preserved. Instead, add this to the user-startup:
&lt;pre&gt;
execute sys:system/network/arostcp/s/startnet
run wirelessmanager device=bwfm.device &gt;nil:
&lt;/pre&gt;
Network will start automatically on boot. If you don't want the wirelessmanager icon on Wanderer desktop, just add 'nogui' to the wirelessmanager line


Lan ethernet port on 
*lan9514  Pi3b Pi2 no support at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device  


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 


Only the Pi5 has a RTC real time clock, the other Pis will need to use [https://aminet.net/package/util/time/NTPSync ntpsync] or similar to get the date and time from the internet 


USB classes support from Prefs/Trident is still work in process 
*usbaudio not working as no rt isochronous on usb2otg (white or black) for pi3b and zero 2w but '''working''' on usb3 port (blue) on pi4, 400 
*camdusbmidi no class compiled but eventually 64bit ports of [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], 


Regarding 680x0 emulation, there are several options that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


The status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use MACAros github for discussion, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 
*[ PiMiga] 

*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behaviour, and that shorting the power supplies can cause instant death of the Pi.


In the shell 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ - work in process 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Linux hosted Pi build] 

[https://github.com/BlitterStudio/aros-compiler-docker Aros Docker for various systems], 

[https://github.com/aros-development-team/AROS/commit/d84b9a337f9aa059154d9af69275935125166bdd Apple Silicon support]


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE-HAT Power Over Ethernet Hat 
*2020 Raspberry Pi PoE+HAT Power Over Ethernet Hat 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 

=== GPU ===

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No
hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent
years. It is the job of graphics HIDDs to allocate bitmaps etc. so that
they have the most suitable characteristics, including allocating them
from GPU RAM where possible. The concept of chip RAM is only for legacy
code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS/OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs are a bit weird and far from optimal, especially MorphOS one, because it aims for m68k binary compatibility.
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?
 
I have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

I so far have -:
 
vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and  returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,
 
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer.
don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses)

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.

Why did usbromstartup become HW-specific ?
In  the  past i have done a big job separating kickstart into several parts. I have never got any responses, so i re-describe my idea.

For now it loads the hs otg chipset driver ..

The  idea  is  to minimize amount of archirecture-specific modules to
    make   user's  life  easier.  So,  the kickstart was split into 'base'
    (which  does  not  contain anything machine-specific) and 'BSP' (Board
    Support Package) which contains all hardware-specific stuff.
     This  way,  for  example, distribution makers can save up space on CD
    and  make  CDs with multiple platform support. Different configuration
    would load the same base with different BSP's.
     Next  there  was some part which is entirely missing on hosted. These
    are   filesystems.  Hosted  ports  do  not need them to boot up, so on
    hosted   they  are  left  out.  At  the  other  hand,  they  are  also
    architecture-agnostic.  So  i put them into 'FS' package (standing for
    'filesystem').

     Poseidon  is  one  more  big part. I made it into separate package in
    order to allow users to omit it if they don't need it (for example, to
    run  on retro PCs without USB). Personally i have one. Again, Poseidon
    is  hardware-agnostic (well, there are USB drivers but HCIs are pretty
    standard).

It's mandatory on PI since there are no other interface types - so being a separate package is irrelevant/pointless.

Is Raspberry's USB controller non-HCI compliant? Actually i expect it to be compliant, then wouldn't it be better to make existing drivers discovering them? 
 
AFAIK its HCI 1.0 compliant but I'm not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.


* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI]

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*Green BentoIO CMX0 - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued sadly, 3 x Pi4 probably better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box with pi4 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


{{BookCat}}</text>
      <sha1>bd7pmzn1k2ck9ozfrdig8v9aq5xjkbt</sha1>
    </revision>
    <revision>
      <id>4669087</id>
      <parentid>4668949</parentid>
      <timestamp>2026-09-06T07:53:12Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4669087</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="93719" sha1="msxa4p9de17gcuzokkx64mezeliplp5" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

==Introduction==

[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 1Gb+ RAM ideally as you may have to switch to 256Mb gfx mode depending on the application running - it is still a work in progress 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power 
nothing else is done especially CSI DSI etc 
*Up to Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


Pi500+ keyboard wedge - 

Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok but not great - wifi and lan ethernet partial working but no web browser to fully test - 


* Pi 5 - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 (Rev1.0) or D0 (rev1.1) 
* Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with heatsink/fan on 3b to prevent cpu 82C+ throttling 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


'''Download''' [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd and copied to fat32 8GB+ microSD card (there will be folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 Aros Raspberry pi 3 64bit thread] 

Boots with '''USB3''' based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb boot it works but slower than SD card 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 


[[File:Wifi00.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi01.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi02.png|thumb|Setup wifi on Aros Pi3b]]

Wifi setup needs the network prefs with the TCP/IP tab click add interface -&gt; change Device to bwfm.device as net0:, IP Mode as DHCP and IPv4 

Once you’ve configured the device, simply save the Wireless Networks tab Wi-Fi configuration even if it’s empty. This will create the Wireless.prefs file in the Env-Archive/SYS directory, and you’ll automatically see the Wireless Manager icon in Wanderer. Although a reboot maybe necessary. Wireless tab gets your router settings. 

If it does not set to start at boot, settings are preserved. Instead, add this to the user-startup:
&lt;pre&gt;
execute sys:system/network/arostcp/s/startnet
run wirelessmanager device=bwfm.device &gt;nil:
&lt;/pre&gt;
Network will start automatically on boot. If you don't want the wirelessmanager icon on Wanderer desktop, just add 'nogui' to the wirelessmanager line


Lan ethernet port on 
*lan9514  Pi3b Pi2 no support at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device  


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 


Only the Pi5 has a RTC real time clock, the other Pis will need to use [https://aminet.net/package/util/time/NTPSync ntpsync] or similar to get the date and time from the internet 


USB classes support from Prefs/Trident is still work in process 
*usbaudio not working as no rt isochronous on usb2otg (white or black) for pi3b and zero 2w but '''working''' on usb3 port (blue) on pi4, 400 
*camdusbmidi no class compiled but eventually 64bit ports of [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], 


Regarding 680x0 emulation, there are several options that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


The status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use MACAros github for discussion, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 
*[ PiMiga] 

*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behaviour, and that shorting the power supplies can cause instant death of the Pi.


In the shell 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ - work in process 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Linux hosted Pi build] 

[https://github.com/BlitterStudio/aros-compiler-docker Aros Docker for various systems], 

[https://github.com/aros-development-team/AROS/commit/d84b9a337f9aa059154d9af69275935125166bdd Apple Silicon support]


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE-HAT Power Over Ethernet Hat 
*2020 Raspberry Pi PoE+HAT Power Over Ethernet Hat 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 

=== GPU ===

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No
hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent
years. It is the job of graphics HIDDs to allocate bitmaps etc. so that
they have the most suitable characteristics, including allocating them
from GPU RAM where possible. The concept of chip RAM is only for legacy
code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS/OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs are a bit weird and far from optimal, especially MorphOS one, because it aims for m68k binary compatibility.
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?
 
I have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

I so far have -:
 
vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and  returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,
 
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer.
don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses)

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.

Why did usbromstartup become HW-specific ?
In  the  past i have done a big job separating kickstart into several parts. I have never got any responses, so i re-describe my idea.

For now it loads the hs otg chipset driver ..

The  idea  is  to minimize amount of archirecture-specific modules to
    make   user's  life  easier.  So,  the kickstart was split into 'base'
    (which  does  not  contain anything machine-specific) and 'BSP' (Board
    Support Package) which contains all hardware-specific stuff.
     This  way,  for  example, distribution makers can save up space on CD
    and  make  CDs with multiple platform support. Different configuration
    would load the same base with different BSP's.
     Next  there  was some part which is entirely missing on hosted. These
    are   filesystems.  Hosted  ports  do  not need them to boot up, so on
    hosted   they  are  left  out.  At  the  other  hand,  they  are  also
    architecture-agnostic.  So  i put them into 'FS' package (standing for
    'filesystem').

     Poseidon  is  one  more  big part. I made it into separate package in
    order to allow users to omit it if they don't need it (for example, to
    run  on retro PCs without USB). Personally i have one. Again, Poseidon
    is  hardware-agnostic (well, there are USB drivers but HCIs are pretty
    standard).

It's mandatory on PI since there are no other interface types - so being a separate package is irrelevant/pointless.

Is Raspberry's USB controller non-HCI compliant? Actually i expect it to be compliant, then wouldn't it be better to make existing drivers discovering them? 
 
AFAIK its HCI 1.0 compliant but I'm not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.


* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI]

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*Green BentoIO CMX0 - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued sadly, 3 x Pi4 probably better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


{{BookCat}}</text>
      <sha1>msxa4p9de17gcuzokkx64mezeliplp5</sha1>
    </revision>
    <revision>
      <id>4669088</id>
      <parentid>4669087</parentid>
      <timestamp>2026-09-06T08:03:47Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4669088</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="93724" sha1="92ky668g9fav1ugvy0qjvo215d5m1gq" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

==Introduction==

[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 1Gb+ RAM ideally as you may have to switch to 256Mb gfx mode depending on the application running - it is still a work in progress 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power 
nothing else is done especially CSI DSI etc 
*Up to Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


Pi500+ keyboard wedge - 

Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok but not great - wifi and lan ethernet partial working but no web browser to fully test - 


* Pi 5 - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 (Rev1.0) or D0 (rev1.1) 
* Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with heatsink/fan on 3b to prevent cpu 82C+ throttling 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


'''Download''' [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd and copied to fat32 8GB+ microSD card (there will be folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 Aros Raspberry pi 3 64bit thread] 

Boots with '''USB3''' port based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb boot it works but slower than SD card 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 


[[File:Wifi00.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi01.png|thumb|Setup wifi on Aros Pi3b]]
[[File:Wifi02.png|thumb|Setup wifi on Aros Pi3b]]

Wifi setup needs the network prefs with the TCP/IP tab click add interface -&gt; change Device to bwfm.device as net0:, IP Mode as DHCP and IPv4 

Once you’ve configured the device, simply save the Wireless Networks tab Wi-Fi configuration even if it’s empty. This will create the Wireless.prefs file in the Env-Archive/SYS directory, and you’ll automatically see the Wireless Manager icon in Wanderer. Although a reboot maybe necessary. Wireless tab gets your router settings. 

If it does not set to start at boot, settings are preserved. Instead, add this to the user-startup:
&lt;pre&gt;
execute sys:system/network/arostcp/s/startnet
run wirelessmanager device=bwfm.device &gt;nil:
&lt;/pre&gt;
Network will start automatically on boot. If you don't want the wirelessmanager icon on Wanderer desktop, just add 'nogui' to the wirelessmanager line


Lan ethernet port on 
*lan9514  Pi3b Pi2 no support at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device  


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 


Only the Pi5 has a RTC real time clock, the other Pis will need to use [https://aminet.net/package/util/time/NTPSync ntpsync] or similar to get the date and time from the internet 


USB classes support from Prefs/Trident is still work in process 
*usbaudio not working as no rt isochronous on usb2otg (white or black) for pi3b and zero 2w but '''working''' on usb3 port (blue) on pi4, 400 
*camdusbmidi no class compiled but eventually 64bit ports of [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], 


Regarding 680x0 emulation, there are several options that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


The status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use MACAros github for discussion, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 
*[ PiMiga] 

*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behaviour, and that shorting the power supplies can cause instant death of the Pi.


In the shell 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ - work in process 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Linux hosted Pi build] 

[https://github.com/BlitterStudio/aros-compiler-docker Aros Docker for various systems], 

[https://github.com/aros-development-team/AROS/commit/d84b9a337f9aa059154d9af69275935125166bdd Apple Silicon support]


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE-HAT Power Over Ethernet Hat 
*2020 Raspberry Pi PoE+HAT Power Over Ethernet Hat 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 

=== GPU ===

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No
hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent
years. It is the job of graphics HIDDs to allocate bitmaps etc. so that
they have the most suitable characteristics, including allocating them
from GPU RAM where possible. The concept of chip RAM is only for legacy
code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS/OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs are a bit weird and far from optimal, especially MorphOS one, because it aims for m68k binary compatibility.
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?
 
I have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

I so far have -:
 
vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and  returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,
 
So, AROS creates the framebuffer bitmap (I have verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to.

The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer.
don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses)

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.

Why did usbromstartup become HW-specific ?
In  the  past i have done a big job separating kickstart into several parts. I have never got any responses, so i re-describe my idea.

For now it loads the hs otg chipset driver ..

The  idea  is  to minimize amount of archirecture-specific modules to
    make   user's  life  easier.  So,  the kickstart was split into 'base'
    (which  does  not  contain anything machine-specific) and 'BSP' (Board
    Support Package) which contains all hardware-specific stuff.
     This  way,  for  example, distribution makers can save up space on CD
    and  make  CDs with multiple platform support. Different configuration
    would load the same base with different BSP's.
     Next  there  was some part which is entirely missing on hosted. These
    are   filesystems.  Hosted  ports  do  not need them to boot up, so on
    hosted   they  are  left  out.  At  the  other  hand,  they  are  also
    architecture-agnostic.  So  i put them into 'FS' package (standing for
    'filesystem').

     Poseidon  is  one  more  big part. I made it into separate package in
    order to allow users to omit it if they don't need it (for example, to
    run  on retro PCs without USB). Personally i have one. Again, Poseidon
    is  hardware-agnostic (well, there are USB drivers but HCIs are pretty
    standard).

It's mandatory on PI since there are no other interface types - so being a separate package is irrelevant/pointless.

Is Raspberry's USB controller non-HCI compliant? Actually i expect it to be compliant, then wouldn't it be better to make existing drivers discovering them? 
 
AFAIK its HCI 1.0 compliant but I'm not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.


* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI]

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*Green BentoIO CMX0 - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued sadly, 3 x Pi4 probably better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


{{BookCat}}</text>
      <sha1>92ky668g9fav1ugvy0qjvo215d5m1gq</sha1>
    </revision>
  </page>
  <page>
    <title>User:Melikamp</title>
    <ns>2</ns>
    <id>291080</id>
    <revision>
      <id>4669006</id>
      <parentid>2706601</parentid>
      <timestamp>2026-09-05T19:22:05Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4669006</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1581" sha1="5p6q6of8pftn1ye697mxbdicq8ytk20" xml:space="preserve">Hello World!

[[User:Melikamp/ma225|ma225]] is a sandbox page which may be later incorporated in [[Calculus]].

[[User:Melikamp/calc|calc]] is a sandbox page which may be later incorporated in [[Calculus]].

[[User:Melikamp/b-calc|b-calc]] is a sandbox page which may be later incorporated in [[Calculus]].

[[User:Melikamp/alg-trig|alg-trig]] is a sandbox page which may be later incorporated in a college algebra and trigonometry text.

[[User:Melikamp/elementary_math|elementary math]] is a sandbox page which may be later incorporated in an appropriate elementary math textbook.

[[User:Melikamp/basic_algebra|basic algebra]] is a sandbox page which may be later incorporated in an appropriate basic algebra textbook.

== Mew ==

{{Question-answer|question=Who am I?|answer=the Question-answer template}}

{{Message_box
|backgroundcolor = #eee;{{text default color}};
|heading = message_box heading
|message = message_box message
|image = Nuvola apps edu miscellaneous.svg
}}

{{TextBox
|1 = TextBox message
|BG = #eee
|W = 100%
}}

{{ExampleRobox|title=Robox Test title&lt;br /&gt;&lt;math&gt;\frac12&lt;/math&gt;}}
Test content using Robox

&lt;math&gt;\frac12&lt;/math&gt;
{{Robox/Close}}

&lt;div style=&quot;background: #eee;{{text default color}}; padding-top: .5em; padding-bottom: .5em; padding-left: 2em; padding-right: 2em; border-style: solid; border-width: 1px; border-color: #aaa;&quot;&gt;
just div title
&lt;/div&gt;
&lt;div style=&quot;padding-top: .5em; padding-bottom: .5em; padding-left: 2em; padding-right: 2em; border-style: solid; border-width: 1px; border-color: #aaa; border-top-width: 0px;&quot;&gt;
just div text
&lt;/div&gt;</text>
      <sha1>5p6q6of8pftn1ye697mxbdicq8ytk20</sha1>
    </revision>
  </page>
  <page>
    <title>User:Fabartus/temp1</title>
    <ns>2</ns>
    <id>292062</id>
    <revision>
      <id>4668925</id>
      <parentid>2542626</parentid>
      <timestamp>2026-09-05T12:29:19Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668925</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="90106" sha1="87km8gw7bh2zenord5n1cuj6a1q8xgq" xml:space="preserve">{{TOL-Proj-top}}
=TOL Wiki project DLS fixups=
{{TOCright}}
This is a demo project to show how the Trainzer user community can help one another using the Project namespace of the TrainzOnline wiki. I have an unusual perspective on the whole Auran/N3V community having more time editing wiki's (since I discovered both Trainz and Wikipedia back in 2004) than I do fixing [[Trainz Errors]] under the new data model, and whilst I find N3V Games a company worthy of sympathies, there are things that we the user community can do to assist one another more easily than they with their numerically challenged and overworked staff can possibly do to help us as easily.

We all know how poorly the N3V staff communicates, this wiki project is spurred by the short-sighted establishment of the DLS clean-up project and the failure of N3V to do more than make a feeble attempt to have some kind of wiki... and because it was feeble, I figure they and we in the community must be nearly as dissatisfied with the results as the other. In the last couple of weeks, I've taken {{plain link|http://online.ts2009.com/mediaWiki/index.php5?title=Special:Contributions&amp;offset=&amp;limit=500&amp;tagfilter=&amp;contribs=user&amp;target=Fabartus&amp;namespace=10&amp;topOnly=1|gobs of time}} to begin fixing the wiki so all of us can be as comfortable as the typical 11 year-old with making contributory edits.

Part of what I'm proposing here is an expansion of the (challenged) base DLS cleanup paradigm to incorporate a discussion of community standards&amp;mdash;using this wiki and it's projects pages to ''have community consensus'' in how different fields in '''our content''' should be fixed up going forward. The programmers and we users have different focus. When making a route, we need different information, they merely consider whether an asset is a problem in their data model and rendering software needs. When it is, they change the model, usually with their typically poor prior announcements in advance of the new changes. Hence the establishment of this wiki to have a dynamic place where they can 'publish' (albeit with insufficient consultation or notice to the user community) changes they need to evolve the Trainz simulators. 

==Welcome to our DLS fixups!==
Did you know you can keep up with unheralded data model changes using this wiki? It's fairly easy. When we are looking at a page you or I can add it to our wiki '[[TOL:WATCH|Watch list]]' using the tab '[[TrainzOnline:Using the Wiki page features#Watch-list_tab|Watch tab]]' and further, can set up our [[TrainzOnline:Using the Wiki page features#preferences|Preferences]] to send us an email when a page has been changed. When and if, the Programmers change the model&amp;mdash;when they make the change without discussing the fact with the user community first, or update the model without commenting out the older tag name with an annotation as to the last valid [[&quot;Trainz-build&quot; tag]] tech level it was valid for, it gives us two things as users:
* A way of being alerted the change is in the works or part of the (hopefully) forthcoming release; not something the geeks are back documenting.
* A valid reason to gripe about the N3V staff communication to us all. Point being we're the one's likely to get burned, and their track record for [[TOL:FILT|auto-fixing assets]] with {{wp|Filter (Unix)|filters}} set up to auto-update the DLS is dismal, putting it kindly as possible.
 
In the near future, all the Official reference pages in the TrainzOnline wiki will be tagged with {{tl|ORP-top}} and {{tl|ORP-bot}} tags, enabling one to access all programmer maintained pages from a single category: [[:Category:reference pages|Reference pages]]. When that process is complete, we'll be initiating a text page listing all the pages to watch as a text asset. Any one of us can then cut and paste that document into their own watch page editor's applet, and voila', instant watch list monitoring of all changes to the geek-speak of our programmers references. In the meantime, I invite the many to join those of us in Yesterdayz Trainz to 'dumb down' the Official reference pages. Documenting when a tag becomes invalid by commenting the line with a REM statement is and should be the standard practice in all versions of Trainz, yet according to that inexperienced Trainzer Jcitron, that most needed tag has mysteriously disappeared from the [[TrainzBaseSpec]] as did the prior ability to have &quot;//...&quot; end of line comments, and the defacto ability of using  ';' (semi-colon) on a line to delimit a comment as was once possible back from Trainz 1.x and through in the many versions TRS2004-TRS2006. NOT PROCESSING these as comments any more is out and out creation of bugs, and putting them onto the user communities backs. 

The ability to comment in a text file is absolutely necessary when all the file names are 'config.txt', one standard we will propose here is a standard block of comments up in the first lines of the [[config.txt file]]s &amp;mdash; among other possible fields, are the several just above the English language description documenting the the file kuid, region, era, and especially the '''[[username]] fields'''... the very folder name the asset should be opened for edit when viewed. An important datum when a user is fixing multiple download issues and might have ten or more Windows Explorer windows open at once. The programmers have little appreciation for that condition we all see when downloading older routes and sessions.

{{-}}

==Attempting to build a searchable list==
[https://www.auran.com/planetauran/dls_cleanup_list.php?CurrentPage=11&amp;Mine=0&amp;Search=&amp;NoClaimed=0 source page1]

 KUID 	Name 	Description 	Repairer
 &lt;KUID:104001:60532&gt; 	DR_US_2H0F2A_045 	DR-Bahn€ng 2-gleisig mit 5,0 m Abstand f€ amerikanische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60533&gt; 	DR_US_2H0F2A_135 	DR-Bahn€ng 2-gleisig mit 5,0 m Abstand f€ amerikanische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60551&gt; 	DR_SW_2H0F4A_090 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ schwedische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60552&gt; 	DR_SW_2H0F4A_045 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ schwedische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60553&gt; 	DR_SW_2H0F4A_135 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ schwedische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60554&gt; 	DR_SW_2H0F2A_090 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ schwedische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60555&gt; 	DR_SW_2H0F2A_045 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ schwedische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60556&gt; 	DR_SW_2H0F2A_135 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ schwedische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60557&gt; 	DR_US_2H0F4A_090 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ amerikanische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60558&gt; 	DR_US_2H0F4A_045 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ amerikanische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60559&gt; 	DR_US_2H0F4A_135 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ amerikanische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60560&gt; 	DR_US_2H0F2A_090 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ amerikanische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60561&gt; 	DR_US_2H0F2A_045 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ amerikanische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60562&gt; 	DR_US_2H0F2A_135 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ amerikanische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60581&gt; 	DR_SW_2H2F4A_090 	DR-Bahn€ng 1-gleisig f€ schwedische Strassensystem.onplatI 	Claim for repair
 &lt;KUID:104001:60582&gt; 	DR_SW_2H2F4A_090 	DR-Bahn€ng 2-gleisig mit 4,0 m Abstand f€ schwedische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60583&gt; 	DR_SW_2H2F4A_090 	DR-Bahn€ng 2-gleisig mit 5,0 m Abstand f€ schwedische Strassensystem.I 	Claim for repair
 &lt;KUID:104001:60584&gt; 	DR_SW_2H2F4A_090 	DR-Bahn€ng 3-gleisig Typ A (3 Gleise nebeneinander) mit 4,0 m Abstand f€ schwedische Strassensyst... 	Claim for repair
 &lt;KUID:104001:60585&gt; 	DR_SW_2H2F4A_090 	DR-Bahn€ng 3-gleisig Typ A (3 Gleise nebeneinander) mit 5,0 m Abstand f€ schwedische Strassensyst... 	Claim for repair
 &lt;KUID:104001:60586&gt; 	DR_SW_2H2F4A_090 	DR-Bahn€ng 3-gleisig Typ B (2 Gleise nebeneinander, 1 Gleis frei, 1 Gleis) mit 4,0 m Abstand f€ s... 	Claim for repair
 &lt;KUID2:104722:1042:5&gt; 	Ortner 3-bay Auto MFX-2 Hopper v3 AG3 	One of the most distinctive cars in service today, the Ortner 100-Ton Aggregate Cars are built fo... 	Claim for repair


==Pages 1-6 &lt;kuid:-1&gt; and (-1)==
'''Pages searched by 'unclaimed' and &lt;kuid:-1&gt;'''
&amp;nbsp;
===group-01 (-1)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID or KUID2
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; |Description 
!style=&quot;width:07%&quot; |Repairer
|-
| &amp;lt;KUID :-10:170&amp;gt; || Gen DL500 mph rhd  || (null) ||
|-
| &amp;lt;KUID:-10:172&amp;gt; || Gen1960 op1  || (null) ||
|-
| &amp;lt;KUID:-10:173&amp;gt; || Gen RC4  || (null) ||
|-
| &amp;lt;KUID:-10:221&amp;gt; || Gen 218  || (null) ||
|-
| &amp;lt;KUID:-12:460&amp;gt; || AN Guard Van  || 8300 Class Guard Van Company: Australian National Length (over coupler): 10.2m Width (over... ||
|-
| &amp;lt;KUID:-12:505&amp;gt; || QR PWA  || PWA Company: Queensland Rail Length: 12.1m Width: 2.5m Height: 2.2m Length: 8.1m (b'... ||
|-
| &amp;lt;KUID:-18:1101&amp;gt; || sw  || (null) ||
|-
| &amp;lt;KUID:-18:1213&amp;gt; || Flash HUD Icon  || (null) ||
|-
| &amp;lt;KUID:-18:1214&amp;gt; || Flash HUD Panel  || (null) ||
|-
| &amp;lt;KUID:-18:1846763744&amp;gt; || Banks Heath  || A strict schedule keeps the traffic flowing on this picturesque countryside branch; and the peopl... ||
|-
| &amp;lt;KUID:-1:1&amp;gt; || ATSF F7A  || GM-EMD F7A &amp; B In 1939 General Motors Electro - Motive Division issued a challenge to the supr... ||
|-
| &amp;lt;KUID:-1:100007&amp;gt; || V/Line S  || Victorian Railways 'S' Class Clyde Engineering acquired the services of former SAR Chief M... ||
|-
| &amp;lt;KUID:-1:100012&amp;gt; || CO-OP Bulk Hopper  || centre flow hopper Length (over coupler): 17.5m Width (overall): 3.1m Height (overal... ||
|-
| &amp;lt;KUID:-1:100018&amp;gt; || VR S blue  || Victorian Railways 'S' Class Clyde Engineering acquired the services of former SAR Chief M... ||
|-
| &amp;lt;KUID:-1:100039&amp;gt; || BR HST 125  || Class 43 HST The debate still rages over whether the HST should be regarded as a diesel mu... ||
|-
| &amp;lt;KUID:-1:100042&amp;gt; || CN Cupola Caboose  || Cupola Caboose CN Length (over coupler): 11.4m Width (overall): 3.0m Height (overall... ||
|-
| &amp;lt;KUID:-1:100043&amp;gt; || B&amp;O Cupola Caboose  || Cupola Caboose B&amp;O Length (over coupler): 11.4m Width (overall): 3.0m Height (overal... ||
|-
| &amp;lt;KUID:-1:100046&amp;gt; || NYC Cupola Caboose  || Cupola Caboose NYC Length (over coupler): 11.4m Width (overall): 3.0m Height (overall)... ||
|-
| &amp;lt;KUID:-1:100121&amp;gt; || CP FP7A  || GM-EMD FP7A In 1939 General Motors Electro - Motive Division issued a challenge to the suprema... ||
|-
| &amp;lt;KUID:-1:100122&amp;gt; || CP F7B  || GM-EMD F7A &amp; B In 1939 General Motors Electro - Motive Division issued a challenge to the supr...  ||&amp;nbsp;
|}
&amp;nbsp;
===group-02 (-1)===

{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID or KUID2
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer
|-
| &amp;lt;KUID :-1:100127&amp;gt; || MR F7A  || GM-EMD F7A &amp; B In 1939 General Motors Electro - Motive Division issued a challenge to the ... ||
|-
| &amp;lt;KUID:-1:100128&amp;gt; || MR F7B  || GM-EMD F7A &amp; B In 1939 General Motors Electro - Motive Division issued a challenge to the ... ||
|-
| &amp;lt;KUID:-1:100131&amp;gt; || NYC F7A  || GM-EMD F7A &amp; B In 1939 General Motors Electro - Motive Division issued a challenge to the supr... ||
|-
| &amp;lt;KUID:-1:100132&amp;gt; || NYC F7B  || GM-EMD F7A &amp; B In 1939 General Motors Electro - Motive Division issued a challenge to the ... ||
|-
| &amp;lt;KUID:-1:100135&amp;gt; || ATSF F7B  || GM-EMD F7A &amp; B In 1939 General Motors Electro - Motive Division issued a challenge to the supr... ||
|-
| &amp;lt;KUID:-1:100136&amp;gt; || Southern F7A  || GM-EMD F7A &amp; B In 1939 General Motors Electro - Motive Division issued a challenge to the supr... ||
|-
| &amp;lt;KUID:-1:100137&amp;gt; || Southern F7B  || GM-EMD F7A &amp; B In 1939 General Motors Electro - Motive Division issued a challenge to the supr... ||
|-
| &amp;lt;KUID:-1:100143&amp;gt; || ER FA1  || American Locomotive Company FA-1 F - for freight, A - for A unit, 1 - the model number. AL... ||
|-
| &amp;lt;KUID:-1:100144&amp;gt; || LV FA1  || American Locomotive Company FA-1 F - for freight, A - for A unit, 1 - the model number. AL... ||
|-
| &amp;lt;KUID:-1:100145&amp;gt; || Rock Island FA1  || American Locomotive Company FA-1 F - for freight, A - for A unit, 1 - the model number. AL... ||
|-
| &amp;lt;KUID:-1:100150&amp;gt; || CN FPA4  || American Locomotive Company FPA-4 F - for freight, A - for A unit, 1 - the model number. A... ||
|-
| &amp;lt;KUID:-1:100153&amp;gt; || CP FPA2  || American Locomotive Company FPA-2 F - for freight, A - for A unit, 1 - the model number. A... ||
|-
| &amp;lt;KUID:-1:100159&amp;gt; || ATSF SS Baggage Car  || SUPER CHIEF The Atchison Topeka &amp; Santa Fe railroad launched the first streamlined Super Chi... ||
|-
| &amp;lt;KUID:-1:100160&amp;gt; || ATSF SS Chair Car  || SUPER CHIEF The Atchison Topeka &amp; Santa Fe railroad launched the first streamlined Super Chi... ||
|-
| &amp;lt;KUID:-1:100161&amp;gt; || ATSF SS Diner  || SUPER CHIEF The Atchison Topeka &amp; Santa Fe railroad launched the first streamlined Super Chi... ||
|-
| &amp;lt;KUID:-1:100162&amp;gt; || ATSF SS Pleasure Dome  || SUPER CHIEF The Atchison Topeka &amp; Santa Fe railroad launched the first streamlined Super Chi... ||
|-
| &amp;lt;KUID:-1:100163&amp;gt; || ATSF SS Pullman - Pine series  || SUPER CHIEF The Atchison Topeka &amp; Santa Fe railroad launched the first streamlined Super Chi... ||
|-
| &amp;lt;KUID:-1:100181&amp;gt; || sw  || (null) ||
|-
| &amp;lt;KUID:-1:100186&amp;gt; || f7interior  || (null) ||
|-
| &amp;lt;KUID:-1:100382&amp;gt; || class37 int cab  || (null)  ||&amp;nbsp;
|}
&amp;nbsp;
===group-03 (-1)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID or KUID2
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer
|-
| &amp;lt;KUID :-1:100554&amp;gt; || bb15000  || (null) ||
|-
| &amp;lt;KUID:-1:100611&amp;gt; || Bridge Stone 2t  || (null) ||
|-
| &amp;lt;KUID:-1:100725&amp;gt; || NSWGR 48 Class  || ALCo DL531 - NSWGR 48 Class The ALCo DL531 was once a common sight on Australia's railways, ... ||
|-
| &amp;lt;KUID:-1:100734&amp;gt; || Silverton 48s  || ALCo DL531 Silverton The ALCo DL531 was once a common sight on Australia's railways, designe... ||
|-
| &amp;lt;KUID:-1:100737&amp;gt; || AN 830 Class  || ALCo DL531 - AN 830 Class The ALCo DL531 was once a common sight on Australia's railways, de... ||
|-
| &amp;lt;KUID:-1:100754&amp;gt; || QR 2100 Class  || 2100 Class Assembed by Clyde Engineering under license from GM-EMD, the 2100 class was i... ||
|-
| &amp;lt;KUID:-1:100770&amp;gt; || NSWGR NLKY louvred van  || NLK Lovred van Company: New South Wales Government Railways Built: 1973-76 Tare: 27t ... ||
|-
| &amp;lt;KUID:-1:100778&amp;gt; || SAR 930 Class  || American Locomotive Company DL500 'World Series' Known as the 'World Series', the ALCo DL500... ||
|-
| &amp;lt;KUID:-1:100812&amp;gt; || NSWGR 44 Class  || American Locomotive Company DL500 'World Series' Known as the 'World Series', the ALCo DL500... ||
|-
| &amp;lt;KUID:-1:100814&amp;gt; || VR-SAR Overland Club Car  || Overland Club Car - Melbourne to Adelaide For over a hundred years the Overland over-night... ||
|-
| &amp;lt;KUID:-1:100815&amp;gt; || VR-SAR Overland AJ  || The Overland - Melbourne to Adelaide For over a hundred years the Overland over-nightly po... ||
|-
| &amp;lt;KUID:-1:100816&amp;gt; || VR-SAR Overland BJ  || The Overland - Melbourne to Adelaide For over a hundred years the Overland over-nightly po... ||
|-
| &amp;lt;KUID:-1:100817&amp;gt; || VR-SAR Overland RoomTantini  || The Overland - Melbourne to Adelaide For over a hundred years the Overland over-nightly po... ||
|-
| &amp;lt;KUID:-1:100820&amp;gt; || SAR 930 Class single  || American Locomotive Company DL500 'World Series' Known as the 'World Series', the ALCo DL500... ||
|-
| &amp;lt;KUID:-1:100825&amp;gt; || Enafer DL500  || American Locomotive Company DL500 'World Series' Known as the 'World Series', the ALCo DL500... ||
|-
| &amp;lt;KUID:-1:100828&amp;gt; || NSWGR NOD  || NOD Gondola Company: New South Wales Government Railways Built: 1977-81 Length: 14.2m H... ||
|-
| &amp;lt;KUID:-1:100841&amp;gt; || PRR GG1  || PRR GG1 With plans to electrify it's 2,800 track miles, the Pennsylvania Railroad required ... ||
|-
| &amp;lt;KUID:-1:100861&amp;gt; || NSW SRA 44 Class  || American Locomotive Company DL500 'World Series' Known as the 'World Series', the ALCo DL500... ||
|-
| &amp;lt;KUID:-1:100871&amp;gt; || ATSF SD40-2  || GM-EMD SD40-2 One of the problems with the popular 'carbody' units was that the strength l... ||
|-
| &amp;lt;KUID:-1:101060&amp;gt; || SS Tipper Car  || Tipper Length (over coupler): 7.1m Width (overall): 3.0m Height (overall): 2.7m B...  ||&amp;nbsp;
|}
&amp;nbsp;
===group-04 (-1)===

{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID or KUID2
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer
|-
| &amp;lt;KUID :-1:101115&amp;gt; || Bridge 2t Steel Arch  || (null) ||
|-
| &amp;lt;KUID:-1:101153&amp;gt; || QR QLX Bronco  || QLX Length (over coupler): 14.7m Width (overall): 3.1m Height (overall): 3.7m Bogie pi... ||
|-
| &amp;lt;KUID:-1:101154&amp;gt; || QR QLX  || QLX Length (over coupler): 14.7m Width (overall): 3.1m Height (overall): 3.7m Bogie pi... ||
|-
| &amp;lt;KUID:-1:101168&amp;gt; || class43 interior  || (null) ||
|-
| &amp;lt;KUID:-1:101202&amp;gt; || f7interior mph rhd  || (null) ||
|-
| &amp;lt;KUID:-1:101206&amp;gt; || Bridge 2t Brick  || (null) ||
|-
| &amp;lt;KUID:-1:101211&amp;gt; || f7interior kph lhd  || (null) ||
|-
| &amp;lt;KUID:-1:101212&amp;gt; || f7interior mph lhd  || (null) ||
|-
| &amp;lt;KUID:-1:101220&amp;gt; || SS Foundry Car  || Foundry Car Length (over coupler): 10.7m Width (overall): 2.6m Height (overall): 3.... ||
|-
| &amp;lt;KUID:-1:101221&amp;gt; || BR HST MK3 TGS  || Type TGS Built 1976 - 1985 Length 23m Height 3.9m Weight 33.47t Seating Capacity 63 ... ||
|-
| &amp;lt;KUID:-1:101222&amp;gt; || NSWGR NOD Loaded  || NOD Gondola Company: New South Wales Government Railways Built: 1977-81 Length: 14.2m H... ||
|-
| &amp;lt;KUID:-1:101224&amp;gt; || IC 4 bay Hopper Loaded  || 4 bay Hopper Length (over coupler): 13.4m Width (overall): 3.1m Height (overall): 3.3m ... ||
|-
| &amp;lt;KUID:-1:101242&amp;gt; || IP ARL Twinette 1st  || Indian Pacific ARL From 1917 it was possible to travel Trans-Australia by rail, but the trip ... ||
|-
| &amp;lt;KUID:-1:101246&amp;gt; || IP BRJ Twinnette 2nd  || Indian Pacific BRJ From 1917 it was possible to travel Trans-Australia by rail, but the t... ||
|-
| &amp;lt;KUID:-1:101248&amp;gt; || IP DF Dining Car  || Indian Pacific DF From 1917 it was possible to travel Trans-Australia by rail, but the tr... ||
|-
| &amp;lt;KUID:-1:101249&amp;gt; || IP HGM Power Van  || Indian Pacific HGM From 1917 it was possible to travel Trans-Australia by rail, but the t... ||
|-
| &amp;lt;KUID:-1:101251&amp;gt; || IP HM Baggage Brake  || Indian Pacific HM From 1917 it was possible to travel Trans-Australia by rail, but the tr... ||
|-
| &amp;lt;KUID:-1:101292&amp;gt; || SAR Guard Van  || 8300 Class Guard Van Company: SAR Length (over coupler): 10.2m Width (overall): 2.6m ... ||
|-
| &amp;lt;KUID:-1:101412&amp;gt; || SNCF TGV SE  || SNCF TGV SE Train a Grande Vitesse (high speed train) of the Societe Nationale des Chemins d... ||
|-
| &amp;lt;KUID:-1:101416&amp;gt; || SNCF TGV SE Unit 2  || SNCF TGV SE Unit 2 Train a Grande Vitesse (high speed train) of the Societe Nationale des Ch...  ||&amp;nbsp;
|}
&amp;nbsp;
===group-05 (-1)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID or KUID2
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer
|-
| &amp;lt;KUID :-1:101417&amp;gt; || SNCF TGV SE Unit 3  || SNCF TGV SE Unit 3 Train a Grande Vitesse (high speed train) of the Societe Nationale des Ch... ||
|-
| &amp;lt;KUID:-1:101419&amp;gt; || SNCF TGV SE Unit 1  || SNCF TGV SE Unit 1 Train a Grande Vitesse (high speed train) of the Societe Nationale des ... ||
|-
| &amp;lt;KUID:-1:101420&amp;gt; || SNCF TGV SE Unit 4  || SNCF TGV SE Unit 4 Train a Grande Vitesse (high speed train) of the Societe Nationale des Ch... ||
|-
| &amp;lt;KUID:-1:101472&amp;gt; || Gen DL500  || (null) ||
|-
| &amp;lt;KUID:-1:101474&amp;gt; || gen gg  || (null)  ||&amp;nbsp;
|}
&amp;nbsp;
===Kuid's mixing begins===

;Interesting, search is now picking up '-1' in non-kuid fields
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID 
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; |Description 
!style=&quot;width:07%&quot; |Repairer
|-
| &amp;lt;KUID:109502:1000151&gt;  || EUROMED-VAGON-1  || Vagon pasajeros primera clase para el Euromed
|-
| &amp;lt;KUID:109502:1000161&gt;  || AVE-2-VAGON-1  || Vagn primera clase para AVE.2 Contributors (Dependencies) ... || 
|-
| &amp;lt;KUID:110115:133&gt;  || DR_br132_675-1  || DR 132 675-1||
|-
| &amp;lt;KUID2:178987:1560:3&gt;  || DE-1_TRS-light  || NS Blauwe Engel Length 26350 mm Width 2740 mm Height 3520 mm Model: DE 1||
|-
| &amp;lt;KUID:178987:3111&gt;  || NS_Plan-U_111-1_mBDk  || NS Plan-U 111 mBDk Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1960 Lengte 24622 mm De total...||
|-
| &amp;lt;KUID:178987:3151&gt;  || NS_Plan-U_151-1_mBDk  || NS Plan-U 151 mBDk Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1963 Lengte 24622 mm De total...||
|-
| &amp;lt;KUID:178987:5500&gt;  || NS_Plan-T_502-1_BK1  || NS_Plan-T_502 Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1965 Lengte 25500 mm De totale len...||
|-
| &amp;lt;KUID:178987:5510&gt;  || NS_Plan-T_529-1_BK1  || NS_Plan-T_529_BK1 Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1965 Lengte 25500 mm De totale...||
|-
| &amp;lt;KUID:189904:182134&gt;  || Virgin MkIII DVT (82134 - Sir Henry Doulton 1820-1897)  || Not quite the real thing but it will do for now. Virgin MkIII DVT (82134 - Sir Henry Doulton 182...||
|-
| &amp;lt;KUID:195962:100092&gt;  || Aus-Tran HST-180  || paintshed skin||
|-
| &amp;lt;KUID:328583:3768&gt;  || JVC(V)Trees#26 Maple avenue spline low 10-15m  || V.I.P. Shrub set, spline version||
|-
| &amp;lt;KUID:438196:1154&gt;  || kiha187-1502  || Japanese Diesel Car kiha187-1502, Limited Express 'Super Inaba' of West JR. Make a unit with kiha...||
|-
| &amp;lt;KUID:45588:1222&gt;  || DS4-4-10 Reading 729  || Baldwin switcher model DS-4-4-10 as used on the Reading. This unit was rebuilt with an EMD engine...||
|-
| &amp;lt;KUID:45588:1224&gt;  || DS4-4-10 Reading 38  || Baldwin switcher model DS-4-4-10 as used on the Reading. US loco sound effects by Wulf_9 enginesp...||
|-
| &amp;lt;KUID:45588:1540&gt;  || DS4-4-10 CNJ 1073  || Baldwin DS4-4-10 switcher operated by the Central Railroad of New Jersey (3 units, #1072-1074). ...||
|-
|}

===group-06 (-1)===

{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID 
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer
|-
| &amp;lt;KUID2:82412:5000048:1&gt;  || Mine-1009  || Mine-1009||
|-
| &amp;lt;KUID2:82412:5000049:1&gt;  || Mine-10010  || Mine-10010||
|-
| &amp;lt;KUID2:82412:5000051:1&gt;  || Log-Stack-Industrie-101  || Log Stack Industry. Loads TUME's Log Stack Products.||
|-
| &amp;lt;KUID2:82412:6097012:1&gt;  || MILW-Sub-HV-Connect-10m-01  || MILW-Sub-HV-Connect-10m-01||
|-
| &amp;lt;KUID2:82412:70074:1&gt;  || Bush-Spline-10m-44-DMD-BLB  || David Drake's BlackBerry-spline-3 with reduced texture size especially for application within lar...||
|-
| &amp;lt;KUID2:82412:850001:1&gt;  || Messenger-MILW-Bitterroots-101  || Messenger-MILW-Bitterroots-101. Contains Videos, Session Objectives and Voice Sound||
|-
| &amp;lt;KUID2:82412:850002:1&gt;  || Messenger-MILW-Bitterroots-102  || Messenger-MILW-Bitterroots-102. Contains Pop-up Messages.||
|-
| &amp;lt;KUID2:82412:850003:1&gt;  || Messenger-NP-Bitterroots-101  || Messenger-NP-Bitterroots-101. Contains Session Objectives anf further descripions||
|-
| &amp;lt;KUID2:82412:850004:1&gt;  || Messenger-NP-Bitterroots-102  || Messenger-NP-Bitterroots-102. Contains Pop-up Messages.||
|-
| &amp;lt;KUID:93985:20001&gt;  || Britain SR 1970s-1980s  || Originally based on the UTC Britain layout, this is the 2nd version of the Southern Region themed...||
|-
| &amp;lt;KUID:45588:15561&gt;  || HT Virginian 2056 H-14  || Virginian Railway had similar hoppers to this one. McClure &amp; Plant (Morning Sun Books) 'The Virgi...||
|-
| &amp;lt;KUID:45588:1615&gt;  || DS4-4-10 WM 133 Speedlettering  || Baldwin switcher model DS-4-4-10 as used on the Western Maryland. WM owned only 2 units, #133 and...||
|-
| &amp;lt;KUID2:45588:1959:1&gt;  || DS4-4-10 Monongahela 421  || Baldwin switcher model DS-4-4-10 as used on the Monongahela Railway, which operated 27 of these e...||
|-
| &amp;lt;KUID:45588:1960&gt;  || DS4-4-10 Monongahela 412  || Baldwin switcher model DS-4-4-10 as used on the Monongahela Railway, which operated 27 of these e...||
|-
| &amp;lt;KUID2:50587:1663:1&gt;  || QR 1620-1650  || The 1620 class were built from 1967 to 1969. There were a total of 34 class members. The 1620s we...||
|-
| &amp;lt;KUID2:58422:10107:4&gt;  || Pullman 12s-1d-1smk  || Pullman heavyweight cars of the 1920's were to replace the old wood cars. They were built from 19...||
|-
| &amp;lt;KUID2:58422:10109:4&gt;  || Pullman 10s-1d-2c  || Pullman heavyweight cars of the 1920's were to replace the old wood cars. They were built from 19...||
|-
| &amp;lt;KUID:58422:10114&gt;  || Pullman 10s-1d-2c  || Pullman heavyweight cars of the 1920's were to replace the old wood cars. They were built from 19...||
|-
| &amp;lt;KUID2:58843:239:1&gt;  || CN 12-1 Sleeper  || Canadian National Pullman 12-1 Sleeper. By far the most popular model of sleeping car that Pullma...||
|-
| &amp;lt;KUID:63822:9012&gt;  || GMR Alco FA-1  || paintshed skin||
|-
| &amp;lt;KUID2:69974:37022:1&gt;  || Stuetzmauer01-10M  || en: Retaining Wall  || 
|-
| &amp;lt;KUID2:69974:37034:1&gt;  || Stuetzmauer04-10M  || en: Retaining Wall  || 
|-
| &amp;lt;KUID2:69974:37035:1&gt;  || Stuetzmauer08-10M  || en: Retaining Wall  || 
|-
| &amp;lt;KUID2:82412:5000040:1&gt;  || Mine-1001  || Mine-1001||
|-
| &amp;lt;KUID2:82412:5000041:1&gt;  || Mine-1002  || Mine-1002||
|-
| &amp;lt;KUID2:82412:5000042:1&gt;  || Mine-1003  || Mine-1003||
|-
| &amp;lt;KUID2:82412:5000043:1&gt;  || Mine-1004  || Mine-1004||
|-
| &amp;lt;KUID2:82412:5000044:1&gt;  || Mine-1005  || Mine-1005||
|-
| &amp;lt;KUID2:82412:5000045:1&gt;  || Mine-1006  || Mine-1006||
|-
| &amp;lt;KUID2:82412:5000046:1&gt;  || Mine-1007  || Mine-1007||
|-
|}
&amp;nbsp;

==Pages 1-6 &lt;kuid:-2&gt;==
This search new, using &lt;kuid:-2&gt; and so some items are redundant. e.g. the first item below should be listed above as well.
===group-07 (-2)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
|&lt;KUID:-1:100871&gt; || ATSF SD40-2 || GM-EMD SD40-2 One of the problems with the popular 'carbody' units was that the strength l... || &amp;nbsp;
|-
| &lt;KUID2:104722:1042:5&gt; || Ortner 3-bay Auto MFX-2 Hopper v3 AG3 || One of the most distinctive cars in service today, the Ortner 100-Ton Aggregate Cars are built fo... || &amp;nbsp;
|-
| &lt;KUID:104822:99001259&gt; || L&amp;N SD40-2 ARN 1259 || paintshed skin Contributors (Dependencies):   W... || &amp;nbsp;
|-
| &lt;KUID:104822:99003554&gt; || L&amp;N SD40-2 3554 ARN || paintshed skin Contributors (Dependencies):   W... || &amp;nbsp;
|-
| &lt;KUID:104822:99004051&gt; || L&amp;N GP38-2 4050 ARN || paintshed skin Contributors (Dependencies):   W... || &amp;nbsp;
|-
| &lt;KUID:104822:99006011&gt; || L&amp;N GP38-2 6011 ARN || paintshed skin Contributors (Dependencies):   W... || &amp;nbsp;
|-
| &lt;KUID:104822:99008000&gt; || L&amp;N SD40-2 8000 ARN || paintshed skin Contributors (Dependencies):   W... || &amp;nbsp;
|-
| &lt;KUID:104822:99008133&gt; || L&amp;N SD40-2 8133 ARN || paintshed skin Contributors (Dependencies):   W... || &amp;nbsp;
|-
| &lt;KUID:109502:1000161&gt; || AVE-2-VAGON-1 || Vagn primera clase para AVE.2 Contributors (Dependencies): ... || &amp;nbsp;
|-
| &lt;KUID:113556:51031&gt; || Loco UPSD40-2 #802 || UP Sd40-2 reskin #802 (Weathered) Dependencies enginesound &lt;KUID:104722:53466&gt; Bogey &lt;KUID:113556:... || &amp;nbsp;
|-
| &lt;KUID2:121945:15033:4&gt; || WR4u-28 || Vierachsiger Speisewagen Bauart 1928 Ganzstahlbauart (WR4u-28) Features: ... || &amp;nbsp;
|-
| &lt;KUID2:135744:146:1&gt; || Detroit &amp; Mackinac #124 4-8-2 Mountain Type || Here is a Detroit &amp; Mackinac Railroad 4-8-2 Mountain Type locomotive #124 reskinned from Bill Sco... || &amp;nbsp;
|-
| &lt;KUID2:135744:148:1&gt; || Pere Marquette #1224 4-8-2 Mountain Type || Here we have a Pere Marquette 4-8-2 Mountain Type loco #1224. This was reskinned from Bill Scott... || &amp;nbsp;
|-
| &lt;KUID2:135744:616:1&gt; || NS SD40-2 Patched || This is a patched version of a Norfolk Southern SD40-2. This was reskinned from sureshot28's Nor... || &amp;nbsp;
|-
| &lt;KUID:178987:3112&gt; || NS_Plan-U_111-2_B || NS Plan-U 111 B Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1960 Lengte 23694 mm De totale l... || &amp;nbsp;
|-
| &lt;KUID:178987:3152&gt; || NS_Plan-U_151-2_B || NS Plan-U 151 B Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1963 Lengte 23694 mm De totale l... || &amp;nbsp;
|-
| &lt;KUID:178987:5501&gt; || NS_Plan-T_502-2_BD || NS_Plan-T_529 Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1965 Lengte 24550 mm De totale len... || &amp;nbsp;
|-
| &lt;KUID:178987:5511&gt; || NS_Plan-T_529-2_BD || NS_Plan-T_529_BD Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1965 Lengte 24550 mm De totale ... || &amp;nbsp;
|-
| &lt;KUID:243294:1156&gt; || NZ Turntable-2 42in gauge || Aliased to Auran's Built-in Tside Turntable AUS 2 modified for 42in track. Suitable for TRS2... || &amp;nbsp;
|-
| &lt;KUID:328583:3766&gt; || JVC(V)Trees#26 Maple avenue spline high 20-25m || V.I.P. Shrub set, spline version || &amp;nbsp;
|}
&amp;nbsp;
===group-08 (-2)===
&amp;nbsp;
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
|&lt;KUID:328583:3767&gt; || JVC(V)Trees#26 Maple avenue spline medium 15-20m || V.I.P. Shrub set, spline version || &amp;nbsp;
|-
| &lt;KUID:440847:42003&gt; || PKP SM42-234 PR.Gdynia || SM42 Contributors (Dependencies):   makibax &lt;li... || &amp;nbsp;
|-
| &lt;KUID:4468:225&gt; || 4-6-2 Duchess Class Tender BR Blue || 10,000 gallon Tender for the 4-6-2 Duchess Class. || &amp;nbsp;
|-
| &lt;KUID:4468:4001&gt; || 4-6-2 West Country Class SR || 4-6-2 West Country Class SR SR No. BR No. Name Date Built 21C101 34001 Exeter 1945 Protot... || &amp;nbsp;
|-
| &lt;KUID:4468:4002&gt; || 4-6-2 West Country Class SR Tender || 4-6-2 West Country Class SR Tender At the end of World War II, a fast and powerful mixed traffic... || &amp;nbsp;
|-
| &lt;KUID:4468:4049&gt; || 4-6-2 Battle of Britain Class BR Green || 4-6-2 West Country Class SR (Battle of Britain Class) SR No. BR No. Name Date Built 21C151 34... || &amp;nbsp;
|-
| &lt;KUID:4468:4050&gt; || 4-6-2 Battle of Britain Class BR Green Tender || 4-6-2 Battle of Britain Class BR Green Tender At the end of World War II, a fast and powerful mi... || &amp;nbsp;
|-
| &lt;KUID:4468:4771&gt; || 2-6-2 V2 LNER Green || Gresley Mixed Traffic V2 2-6-2 4771 Green Arrow 4806 Green Howard 4844 Coldstreamer (60873) 48... || &amp;nbsp;
|-
| &lt;KUID:45324:100001&gt; || BNSF GP38-2 || Burlington Northern Santa Fe GP38-2 || &amp;nbsp;
|-
| &lt;KUID:45324:100012&gt; || SP SD40T-2 || Southern Pacific SD40T-2 || &amp;nbsp;
|-
| &lt;KUID:45324:100013&gt; || UP SD40T-2 || Union Pacific SD40T-2 || &amp;nbsp;
|-
| &lt;KUID:45588:10229&gt; || Pittsburgh &amp; West Virginia 4-6-2 Pacific 200 Tender || Pittsburgh &amp; West Virginia 4-6-2 Pacific Tender, Coal, lettered for #200. Original tender bogey w... || &amp;nbsp;
|-
| &lt;KUID:45588:10230&gt; || Pittsburgh &amp; West Virginia 4-6-2 Pacific 200 || P&amp;WV operated 3 light Pacifics, #200-202. Passenger service was discontinued before the Connelsvi... || &amp;nbsp;
|-
| &lt;KUID:45588:1162&gt; || SD40-2 C&amp;NW 6854 || Chicago &amp; Northwestern owned dynamic brake-equipped SD40-2's, purchased following UP-specs for co... || &amp;nbsp;
|-
| &lt;KUID:45588:1209&gt; || GP40-2 FEC 419 light || Florida East Coast owned 10 GP40's (#401-410) and 19 GP40-2's (#411-429) for bridge line freight ... || &amp;nbsp;
|-
| &lt;KUID:45588:1214&gt; || GP40-2 FEC 434 new || Florida East Coast owned 10 GP40's (#401-410), 19 GP40-2's (#411-429), and 24 secondhand GP40-2's... || &amp;nbsp;
|-
| &lt;KUID:45588:1280&gt; || GP39-2 RDG 3405 || Roger Crouch's GP39 model reskinned into Reading's best paint scheme, the final green and yellow ... || &amp;nbsp;
|-
| &lt;KUID:45588:1311&gt; || GP38-2 NY&amp;A 261 || Former Long Island GP38-2 working on the former LIRR freight operations, the New York &amp; Atlantic.... || &amp;nbsp;
|-
| &lt;KUID:45588:1359&gt; || SD38-2 Utah Railway 2053 || I read that Utah Railway had four SD38-2's on order from EMD in 1977, but cancelled them. Here th... || &amp;nbsp;
|-
| &lt;KUID:45588:1428&gt; || SD40-2 Conrail 6358 || Conrail SD40-2. Model was created by Prjindigo, Roger Crouch and the reskin by Adam Gase. Contri... || &amp;nbsp;
|}
&amp;nbsp;
===group-09 (-2)===

{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
|&lt;KUID:45588:1647&gt; || GP38-2 LV 325 || Lehigh Valley bought 12 new GP38-2's in 1972, operating them for four years before the formation ... || &amp;nbsp;
|-
| &lt;KUID:45588:1779&gt; || Clinchfield 4-6-2 Pacific 153 || Clinchfield operated 5 light Pacifics, class P-1 #150-152 initially for passenger service and cla... || &amp;nbsp;
|-
| &lt;KUID:45588:333&gt; || GP40-2 GTW 6413 ex-DT&amp;I || GP40-2 GTW 6413 ex-DT&amp;I without dynamic brakes Contributors (Dependencies) || &amp;nbsp;
|-
| &lt;KUID:45588:4022&gt; || SD40-2 Ohio Central 4022 || Roger Crouch's SD40 model painted for the Ohio Central in their Erie-Lackawanna-style paint schem... || &amp;nbsp;
|-
| &lt;KUID:45588:4352&gt; || GP40-2 Chessie WM 4352 || GP40-2 Chessie (WM) 4352. Western Maryland owned 35 GP40-2's, #4257-4261, 4312-4321, and 4352-437... || &amp;nbsp;
|-
| &lt;KUID:45588:4408&gt; || GP40-2 Chessie C&amp;O 4408 || GP40-2 Chessie (C&amp;O) - B&amp;O and WM notwithstanding. C&amp;O owned 95 GP40-2's, #4165-4184, 4262-4286, ... || &amp;nbsp;
|-
| &lt;KUID:45588:455&gt; || GP38-2 P&amp;LE 2059 Yellow cab front || Pittsburgh &amp; Lake Erie bought 6 new GP38-2's in 1977 and || &amp;nbsp;
|-
| &lt;KUID:45588:542&gt; || GP38-2 Utah Belt 2016 || Auran's GP38 painted for Eric Brooman's Utah Belt. Contributors (Dependencies): || &amp;nbsp;
|-
| &lt;KUID:45588:543&gt; || GP38-2 Utah Belt 2009 || Auran's GP38 painted for Eric Brooman's Utah Belt. Contributors (Dependencies):... || &amp;nbsp;
|-
| &lt;KUID:45588:5937&gt; || SD40-2 GTW 5937 ex-UP || Grand Trunk Western SD40-2 5937, ex-UP, nee-Missouri Pacific, without dynamic brakes. Dynamic bra... || &amp;nbsp;
|-
| &lt;KUID:45588:842&gt; || GP40-2 RF&amp;P 142 || Richmond Fredericksburg &amp; Potomac owned 7 GP40's and 7 GP40-2's for bridge line freight service b... || &amp;nbsp;
|-
| &lt;KUID:45588:844&gt; || GP40-2 RF&amp;P 144 || Richmond Fredericksburg &amp; Potomac owned 7 GP40's and 7 GP40-2's for bridge line freight service b... || &amp;nbsp;
|-
| &lt;KUID:51275:1&gt; || CSX GP 38-2 || Paint shed skin 2003 William Works || &amp;nbsp;
|-
| &lt;KUID:51275:54&gt; || CSX GP 38-2 || Pa || &amp;nbsp;
|-
| &lt;KUID:51275:56&gt; || CSX GP 38-2 || CSX Locomotive ver.2 needs the horn and GP38 file!!! || &amp;nbsp;
|-
| &lt;KUID:523:1094&gt; || IR SD40-2 || GM-EMD SD40-2 One of the problems with the popular 'carbody' units was that the strength l... || &amp;nbsp;
|-
| &lt;KUID:55290:606&gt; || Loco EMD NSSD40-2 || NS SD40-2. Model was created by Prjindigo, Roger Crouch and the paintwork was created by Phil_C, ... || &amp;nbsp;
|-
| &lt;KUID:55290:616&gt; || LOCO NS SD40-2 wide alpha || The SD40 can be said to have been the mainstay of the rail systems through the 70s and 80s, good ... || &amp;nbsp;
|-
| &lt;KUID:55290:620&gt; || SPGP39-2 HSH || NS GP39-2 with a high short hood.Model was created by Prjindigo, Roger Crouch and the paintwork w... || &amp;nbsp;
|-
| &lt;KUID:55290:626&gt; || csx mow GP40-2 || CSX MOW GP40-2. Model was created by Prjindigo, Roger Crouch and the paintwork was created by Sea... || &amp;nbsp;
|}
&amp;nbsp;
===group-10 (-2)===

{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
|&lt;KUID:55290:632&gt; || CHESSIE SYSTEM GP40-2 || CHESSIE SYSTEM GP40-2. Model was created by Prjindigo, Roger Crouch and the paintwork was created... || &amp;nbsp;
|-
| &lt;KUID:55290:633&gt; || CSX GREY GP38-2 || CSX GP38-2. Model was created by Prjindigo, Roger Crouch and the paintwork was created by Sean Po... || &amp;nbsp;
|-
| &lt;KUID:55976:51012&gt; || 4-2-2 Stirling GNR #1 Enginespec || loco || &amp;nbsp;
|-
| &lt;KUID:58377:311&gt; || PRJX7042 SD40-2 || PRJX leasing SD40-2 || &amp;nbsp;
|-
| &lt;KUID:58377:312&gt; || PRJX7047 SD40-2 no dynamics || PRJX leasing SD40-2 without dynamic brakes || &amp;nbsp;
|-
| &lt;KUID:58377:313&gt; || PRJX7051 SD40-2 High Short Hood || PRJX leasing SD40-2 with a high short hood || &amp;nbsp;
|-
| &lt;KUID:58377:316&gt; || PRJX7066 SD40-2 HSH steam no dynamics || PRJX leasing SD40-2 HSH with a steam generator without dynamic brakes || &amp;nbsp;
|-
| &lt;KUID:58377:374&gt; || PRJX GP39-2 HSH no dynamics || PRJX leasing GP39-2 with a high short hood and no dynamic brakes || &amp;nbsp;
|-
| &lt;KUID:58377:376&gt; || PRJX GP39-2 steam no dynamics || PRJX leasing GP39-2 with a steam generator without dynamic brakes || &amp;nbsp;
|-
| &lt;KUID:58377:393&gt; || PRJX GP40-2 HSH || PRJX leasing GP40-2 with a high short hood || &amp;nbsp;
|-
| &lt;KUID:58377:394&gt; || PRJX GP40-2 HSH no dynamics || PRJX leasing GP40-2 with a high short hood without dynamic brakes || &amp;nbsp;
|-
| &lt;KUID:58377:516&gt; || SD40-2 undecorated || SD40-2 undecorated || &amp;nbsp;
|-
| &lt;KUID:58377:9997&gt; || PRJX GP38-2 Steam || PRJX leasing GP38-2 with a steam generator || &amp;nbsp;
|-
| &lt;KUID2:58422:10109:4&gt; || Pullman 10s-1d-2c || (null) || &amp;nbsp;
|-
| &lt;KUID:58422:10114&gt; || Pullman 10s-1d-2c || Pullman heavyweight cars of the 1920's were to replace the old wood cars. They were built from 19... || &amp;nbsp;
|-
| &lt;KUID:58843:10052&gt; || IC 4-4-2 Sleeper || On February 4, 1911, The Illinois Central Railroad renamed its 'Chicago &amp; New Orleans Limited' as... || &amp;nbsp;
|-
| &lt;KUID:61014:1776&gt; || DT&amp;I GP 38-2 #1776 || Delivered in this Bicentennial paint scheme in September of 1975,re-painted as DT&amp;I #228 in 1981 || &amp;nbsp;
|-
| &lt;KUID:62456:445&gt; || BR 101 210-2 || Model: DB 101 DB Baujahr: 1996 Hersteller: Adtranz Dauerleistung: 6400 kW Vmax: 2... || &amp;nbsp;
|-
| &lt;KUID:63822:100362&gt; || SD40-2 CLRR || paintshed skin || &amp;nbsp;
|-
| &lt;KUID:7592:1000308&gt; || TPR MKT SD40-2 || paintshed skin || &amp;nbsp;
|}
&amp;nbsp;
===group-11 (-2)===
&amp;nbsp;
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
|&lt;KUID2:7592:10175:1&gt; || CRR #311 4-8-2 Mountain || The CRR #311 is a fictional roadnumber of the USRA Mountain Type Locomotive owned by nearly every... || &amp;nbsp;
|-
| &lt;KUID2:7592:10178:1&gt; || GN #2507 4-8-2 Mountain || The GN #2507 is a prototypical roadnumber of the USRA Mountain Type Locomotive owned by nearly ev... || &amp;nbsp;
|-
| &lt;KUID2:7592:10180:1&gt; || UP #7000 4-8-2 Mountain || The UP #7000 is a prototypical roadnumber of the USRA Mountain Type Locomotive owned by nearly ev... || &amp;nbsp;
|-
| &lt;KUID2:7592:10182:1&gt; || L&amp;N #419 4-8-2 Mountain || The L&amp;N #419 4-8-2 Mountain is a fictional roadnumber of the USRA Mountain Type Locomotive owned ... || &amp;nbsp;
|-
| &lt;KUID2:7592:10184:1&gt; || Southern #1409 4-8-2 Mountain || The Southern #1409 4-8-2 Mountain is a fictional roadnumber of the USRA Mountain Type Locomotive ... || &amp;nbsp;
|-
| &lt;KUID2:7592:10186:1&gt; || GN #2512 4-8-2 Mountain || The GN #2512 is a prototypical roadnumber of the USRA Mountain Type Locomotive owned by nearly ev... || &amp;nbsp;
|-
| &lt;KUID2:7592:10187:1&gt; || DMIR #244 4-8-2 Mountain || The UP #7000 is a prototypical roadnumber of the USRA Mountain Type Locomotive owned by nearly ev... || &amp;nbsp;
|-
| &lt;KUID:76538:100177&gt; || GP38-2 Mohawk &amp; Hudson 3850 || paintshed skin || &amp;nbsp;
|-
| &lt;KUID:79097:1001&gt; || Frisco 1522 4-8-2 'Mountain Type' || The Frisco 1522 was built by the Baldwin Locomotive Company in 1925 and has a wheel arrangement o... || &amp;nbsp;
|-
| &lt;KUID:81997:51420&gt; || SP_GS-2_Engine_Specs || Engine spec for SP GS-2 4-8-4 loco || &amp;nbsp;
|-
| &lt;KUID2:82412:4001005:1&gt; || JVC-60-Oak-S-LO-24m-01 || JVC Oak Tree (JVC__Trees_60 Oak summer 24m) with reduced texture size especially for application ... || &amp;nbsp;
|-
| &lt;KUID2:82412:4001020:1&gt; || JVC-9-Birch-S-LO-25m-01 || JVC Oak Tree (JVC_S1_Trees_9 Birch 25m Summer) with reduced texture size especially for applicati... || &amp;nbsp;
|-
| &lt;KUID2:82412:4001021:1&gt; || JVC-2-Tree-LO-20m-01 || JVC Tree 2 (jvc__trees_2 20m single) with reduced texture size especially for application within ... || &amp;nbsp;
|-
| &lt;KUID2:82412:4001022:1&gt; || JVC-49-Oak-S-LO-29m-01 || JVC Tree 2 (jvc_trees_49 oak summer lo_res 29m) with reduced texture size especially for applicat... || &amp;nbsp;
|-
| &lt;KUID2:82412:5000052:1&gt; || Log-Stack-Industrie-201 || Log Stack Industry. Loads TUME's Log Stack Products. || &amp;nbsp;
|-
| &lt;KUID2:82412:6097013:1&gt; || MILW-Sub-HV-Connect-20m-01 || MILW-Sub-HV-Connect-20m-01 || &amp;nbsp;
|-
| &lt;KUID:83815:100002&gt; || SD40-2 Florida East Coast || SD40-2 Florida East Coast Contributors (Dependencies): ... || &amp;nbsp;
|-
| &lt;KUID:86105:6213&gt; || US Army Sd40-2 4641 || paintshed skin || &amp;nbsp;
|-
| &lt;KUID:86105:6221&gt; || Loco SD40-2 Western Pacific || Western Pacific SD40-2. Model was created be Prjindigo, Roger Crouch and the paintwork was create... || &amp;nbsp;
|-
| &lt;KUID:86105:6222&gt; || Loco SD40-2 Southern Pacific || Southern Pacific SD40-2. Model was created be Prjindigo, Roger Crouch and the paintwork was creat... || &amp;nbsp;
|}
&amp;nbsp;
===group-12 (-2)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
| &lt;KUID:86105:6223&gt; || Loco SD40-2 FURX || FURX SD40-2. Model was created be Prjindigo, Roger Crouch and the paintwork was created by Phil_C... || &amp;nbsp;
|-
| &lt;KUID:86105:6224&gt; || Loco SD40-2 Grand Trunk Western || Grand Trunk Western SD40-2. Model was created by Prjindigo, Roger Crouch and the paintwork was cr... || &amp;nbsp;
|-
| &lt;KUID:86105:6225&gt; || Loco SD40-2 Kansas City Southern || Kansas City Southern Railways SD40-2. Model was created be Prjindigo, Roger Crouch and the paintw... || &amp;nbsp;
|-
| &lt;KUID:86105:6231&gt; || Loco SD40-2 Bessemer &amp; Lake Erie || Bessemer &amp; Lake Erie SD40-2. Model was created be Prjindigo, Roger Crouch and the paintwork was c... || &amp;nbsp;
|-
| &lt;KUID:86105:6232&gt; || Loco SD40-2 Atlantic Coast Lines || Atlantic Coast Lines SD40-2. Model was created be Prjindigo, Roger Crouch and the paintwork was c... || &amp;nbsp;
|-
| &lt;KUID:86105:6233&gt; || Loco SD40-2 Baltimore &amp; Ohio || Baltimore &amp; Ohio SD40-2. Model was created be Prjindigo, Roger Crouch and the paintwork was creat... || &amp;nbsp;
|-
| &lt;KUID:86105:6234&gt; || Loco SD40-2 Chicago &amp; North Western || Chicago &amp; North Western SD40-2. Model was created be Prjindigo, Roger Crouch and the paintwork wa... || &amp;nbsp;
|-
| &lt;KUID:86105:6239&gt; || Loco SD40-2 Paducah &amp; Louisville Railway || Paducah &amp; Louisville Railway SD40-2. Model was created be Prjindigo, Roger Crouch and the paintwo... || &amp;nbsp;
|-
| &lt;KUID:86105:6274&gt; || Loco EMD SD40-2 CSX Bright Future || CSX SD40-2 in Bright Future paint scheme. Model was created by Prjindigo, Roger Crouch and the pa... || &amp;nbsp;
|-
| &lt;KUID:86105:6275&gt; || Loco EMD SD40-2 CSX MaintenanceOfWay || CSX SD40-2 Maintenance Of Way. Model was created by Prjindigo, Roger Crouch and the paintwork was... || &amp;nbsp;
|-
| &lt;KUID:86105:6276&gt; || Loco EMD SD40-2 CSX Grey || CSX SD40-2 in Grey and Blue Paint scheme. Model was created by Prjindigo, Roger Crouch and the pa... || &amp;nbsp;
|-
| &lt;KUID:86105:9904&gt; || Loco EMD GP38-2HSH Southern Railway || GP38-2 HSH Southern Railway. Model was created by Prjindigo, Roger Crouch and the paintwork was c... || &amp;nbsp;
|-
| &lt;KUID:87051:1&gt; || Overland3974 SD40-2 || Overland3974 SD40-2 Contributors (Dependencies):  &lt;... || &amp;nbsp;
|-
| &lt;KUID:87051:2&gt; || Overland9928 SD40-2 || Overland9928 SD40-2 Contributors (Dependencies):  &lt;... || &amp;nbsp;
|-
| &lt;KUID:87783:1141&gt; || SD40-2 - Midwest Central || Midwest Central's SD40-2 is a Paintshed reskin of the Auran model in the green and brown MidCen l... || &amp;nbsp;
|-
| &lt;KUID:87854:982511580&gt; || CSX SD40-2 8808 || paintshed skin || &amp;nbsp;
|-
| &lt;KUID:87854:982511581&gt; || CSX SD40-2 8855 || paintshed skin || &amp;nbsp;
|-
| &lt;KUID2:93502:60:1&gt; || A10 engine 0-4-2S class engine || A10 #6 is one of the oldest steam engines still in operation in the southern hemisphere. Contrib... || &amp;nbsp;
|-
| &lt;KUID:93502:61&gt; || 3F6I A10 engine 0-4-2S class engine || The A10 is one of the oldest steam engines still in operation in the southern hemisphere. || &amp;nbsp;
|-
| &lt;KUID:93502:72&gt; || Emily engine 4-2-2T class engine || Emily is new engine to arrive on the happy island of sodor. || &amp;nbsp;
|-
| &lt;KUID:98966:3009&gt; || Norfolk southern SD40-2 Booster with Steam || Norfolk southern SD40-2 Booster with Steam-unit. Many thanks to Prjindigo for the mesh and For Le... || &amp;nbsp;
|-
| &lt;KUID:98966:529786&gt; || Norflok Southern GP38-2 HSH || Norflok Southern GP38-2 HSH , large file size do to major alterations to the secondary texture fi... || &amp;nbsp;
|}
&amp;nbsp;
==Pages 1-2 &lt;kuid:-3&gt;==
'''All pages with &lt;kuid:-3&gt; and '-3' in names'''
===group-13 (-3)===
&amp;nbsp;
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
| &lt;KUID:-3:10035&gt; || GATX Oil Tanker || length: 37'4 width: 9'8 height: 13'9 bogie wheelbase: 5'6 bogie pivot centres: 27'2 || &amp;nbsp;
|-
| &lt;KUID:-3:10059&gt; || Seaport || (null) || &amp;nbsp;
|-
| &lt;KUID:-3:10063&gt; || CB Woodchips_Gondola || Woodchips Gondola Company: Chippies Bits Ltd Built: 1977-81ish Length: 14.2m Height: 2... || &amp;nbsp;
|-
| &lt;KUID:-3:100878&gt; || NSWGR NQOX Flat Car || Container Flat Car || &amp;nbsp;
|-
| &lt;KUID:-3:10123&gt; || Multiple Industry || (null) || &amp;nbsp;
|-
| &lt;KUID:-3:10139&gt; || Container Station Basic || (null) || &amp;nbsp;
|-
| &lt;KUID:-3:10142&gt; || Oil Field Basic || (null) || &amp;nbsp;
|-
| &lt;KUID:-3:10145&gt; || Seaport Basic || (null) || &amp;nbsp;
|-
| &lt;KUID:-3:10162&gt; || gen renfe 305 || (null) || &amp;nbsp;
|-
| &lt;KUID:-3:10165&gt; || Multiple Industry basic || (null) || &amp;nbsp;
|-
| &lt;KUID:109502:100030&gt; || AVE-3-CABEZA || Model: AVE-350 Manufactor: Siemens Power: 4800 bhp (compleet trainset) || &amp;nbsp;
|-
| &lt;KUID2:121945:15032:4&gt; || B4u-30 || Vierachsiger Einheits-D-Zugwagen, 2. Klasse Bauart 1930 Ganzstahlbauart (B4u-30) ... || &amp;nbsp;
|-
| &lt;KUID:1551:10021&gt; || SNCF TGV-PSE Unit 2-3 || TGV Paris Sud-est Unit 2 Company: SNCF || &amp;nbsp;
|-
| &lt;KUID:178987:3113&gt; || NS_Plan-U_111-3_ABk || NS Plan-U 111 ABk Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1960 Lengte 24622 mm De totale... || &amp;nbsp;
|-
| &lt;KUID:178987:3153&gt; || NS_Plan-U_151-3_ABk || NS Plan-U 151 ABk Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1960 Lengte 24622 mm De totale... || &amp;nbsp;
|-
| &lt;KUID:178987:5502&gt; || NS_Plan-T_502-3_AB || NS_Plan-T_529 Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1965 Lengte 24550 mm De totale len... || &amp;nbsp;
|-
| &lt;KUID:178987:5512&gt; || NS_Plan-T_529-3_AB || NS_Plan-T_529_AB Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1965 Lengte 24550 mm De totale ... || &amp;nbsp;
|-
| &lt;KUID:284555:100421&gt; || Durango and silverton K-36 #485 Tender || D&amp;RGW #485 Tender This is the Tender for the D&amp;RGW K-36 #485. THIS IS A RESKIN OF PROWLER901'S... || &amp;nbsp;
|-
| &lt;KUID:284555:100422&gt; || Durango &amp; Silverton K-36 #485 || D&amp;RGW K-36 Mikado #485 The K-36 class was built for the D&amp;RGW by the Baldwin Locomotive Works of... || &amp;nbsp;
|-
| &lt;KUID:403674:1&gt; || PKP_EU07-337_PKP _CARGO_ZT_Gdynia_303e || Polish electric universal locomotive EU07 class, factory type 303E Contributors (Dependencies): ... || &amp;nbsp;
|}
&amp;nbsp;
===group-14 (-3)===
&amp;nbsp;
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
| &lt;KUID:45588:857&gt; || SD40-3 W&amp;LE 3016 || Roger Crouch's SD40 model painted for the (new) Wheeling &amp; Lake Erie in their Rio Grande-style pa... || &amp;nbsp;
|-
| &lt;KUID:49267:1009&gt; || NS ICE-3 1 || Model: NS ICE-3 Manufactor: Siemens Power: 4800 bhp (compleet trainset) Max.Speed: 330 km/h Head... || &amp;nbsp;
|-
| &lt;KUID2:67794:2001:1&gt; || UTLX 38\' X-3 Tank Car || UTLX tank car based (somewhat) on the 38' long frame X-3 design from the 1920's. Used through out... || &amp;nbsp;
|-
| &lt;KUID2:67794:2002:1&gt; || SHPX 38\' X-3 Tank Car || SHPX tank car based (somewhat) on the 38' long frame X-3 design from the 1920's. Used through out... || &amp;nbsp;
|-
| &lt;KUID2:82412:4001006:1&gt; || JVC-60-Oak-S-LO-30m-01 || JVC Oak Tree (JVC__Trees_60 Oak summer 30m) with reduced texture size especially for application ... || &amp;nbsp;
|-
| &lt;KUID2:82412:4001016:1&gt; || JVC-39-Oak-S-LO-32m-01 || JVC Oak Tree (JVC__Trees_39 Oak 32m) with reduced texture size especially for application within ... || &amp;nbsp;
|-
| &lt;KUID:83329:20521&gt; || Ansett Douglas DC-3 || I would like to thank Minitrix for letting me reskin his Douglas DC-3 Contributors (Dependencies... || &amp;nbsp;
|-
| &lt;KUID:83329:20522&gt; || TAA Douglas DC-3 || I would like to thank Minitrix for letting me reskin his Douglas DC-3 Contributors (Dependencies... || &amp;nbsp;
|-
| &lt;KUID:9999:10024&gt; || OBB CAT 88-33 controll || City Airport Train Doppelstockwagen-Steuerwagen der Ö³terreichisen Bundesbahnen AG Based on the ... || &amp;nbsp;
|-
| &lt;KUID:9999:10026&gt; || OBB Wiesel 88-33 controll || City Airport Train Doppelstockwagen-Steuerwagen der Ö³terreichisen Bundesbahnen AG Based on the ... || &amp;nbsp;
|}
&amp;nbsp;
&amp;nbsp;
==Pages 1-4 &lt;kuid:-4&gt;==
'''Searches finding &lt;kuid:-4&gt; and '-4' '''
&amp;nbsp;
===group-15 (-4)===

{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID 
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer
|-
| &amp;lt;KUID2:113556:60000:3&gt;||SP 8-40b #8024 ||GE B40-8 SP, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, and W...
| 
|-
|&amp;lt;KUID2:113556:600015:2&gt; || SSW 8-40b #8049 || GE B40-8 SSW, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, and ...
| 
|-
| &amp;lt;KUID2:113556:60003:3&gt; || SP 8-40b #8019 || GE B40-8 SP, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, and W...
|
|-
| &amp;lt;KUID2:113556:60004:2&gt; ||SSW 8-40b #8051 ||GE B40-8 SSW, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, and ...
|
|-
| &amp;lt;KUID2:113556:60020:3&gt; ||SP 8-40b #8001 ||GE B40-8 SP, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, and W...
|
|-
| &amp;lt;KUID2:113556:60056:3&gt; ||BNSF 8-40b #8618 ||GE B40-8 SP, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
| &amp;lt;KUID2:113556:60059:3&gt; ||CSX 8-40b #5952 ||GE B40-8 CSX, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf...
|
|-
| &amp;lt;KUID2:113556:60060:3&gt; ||CSX 8-40b #5942 ||GE B40-8 CSX, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf...
|
|-
|KUID2:113556:60077:3&gt; ||BNSF 8-40b #8603 ||GE B40-8 SP, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
|KUID2:113556:60080:2&gt; ||ATSF 8-40b #7442 ||GE B40-8 ATSF mesh made by SP_OR_BUST, Thanks to CSX_sd60 for the great horn, Thanks to Weevil fo...
|
|-
|KUID2:113556:60084:2&gt; ||ATSF 8-40b #8615 ||GE B40-8 ATSF mesh made by SP_OR_BUST, Thanks to CSX_sd60 for the great horn, Thanks to Weevil fo...
|
|-
|KUID2:113556:60087:2&gt; ||ATSF 8-40b #8617 ||GE B40-8 ATSF mesh made by SP_OR_BUST, Thanks to CSX_sd60 for the great horn, Thanks to Weevil fo...
|
|-
|KUID2:113556:70020:2&gt; ||Susq 8-40b #4002 ||GE B40-8 Susq, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wul...
|
|-
|KUID2:113556:70089:2&gt; ||SP KODAK 8-40b #8151 ||GE B40-8 SP Kodachrome mesh made by SP_OR_BUST, Thanks to CSX_sd60 for the great horn, Thanks to ...
|
|-
|KUID2:135744:2:1&gt; ||Santa Fe Warbonnet Dash 9-44CW ||This is A Santa Fe Warbonnet scheme Dash 9 locomotive reskinned from norfolksouthern37's BNSF Das...
|
|-
|KUID2:135744:48734:1&gt; ||Santa Fe Warbonnet Dash 9-44CW ||This is a revision of my original Santa Fe Warbonnet Dash 9-44CW locomotive, originally reskinned...
|
|-
|KUID:152373:9000&gt; ||FR8Net Dash 9-44CW ||FR8Net's first Locomotive purchase's from GM on the 10th Dec 04, 8846,8847 and 8848 Working on th...
|
|-
|KUID:178987:5503&gt; ||NS_Plan-T_502-4_BK2 ||NS_Plan-T_502 Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1965 Lengte 25500 mm De totale len...
|
|-
|KUID:178987:5513&gt; ||NS_Plan-T_529-4_BK2 ||NS_Plan-T_529_BK2 Gebouwd door Werkspoor/Heemaf/Smit In dienst in 1965 Lengte 25500 mm De totale...
|
|-
|KUID:200726:24031&gt; ||OEBB H-40/60 Tunnel ||OEBB Lichtsignal geskripted 3-begriffiges Hauptsignal Tunnelausfuehrung
|
|}


===group-16 (-4)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID 
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description  
!style=&quot;width:08%&quot; |Repairer
|-
|  &amp;lt;KUID:32711:100340&gt; ||0-4-0T Jay Street Connecting #1 ||An ALCo 0-4-0T saddle tank locomotive. This engine is based on Georgia Power #30, currently opera...
|
|-
|KUID:32711:100353&gt; ||0-4-0T Jay Street Connecting #2 ||An ALCo 0-4-0T saddle tank locomotive. This engine is based on Georgia Power #30, currently opera...
|
|-
|KUID:32711:100430&gt; ||0-4-0T Sounds ||0-4-0T sounds
|
|-
|KUID:35848:1001&gt; ||BNSF Dash 9-44CW ||ReSkin of the 1001 of the Elgin, Joliet &amp; Eastern (EJE) Mesh-file by Justin Cornell (norfolksouth...
|
|-
|KUID:45324:100015&gt; ||BNSF Dash 9-44CW ||BNSF dash nine set
|
|-
|KUID:45324:100018&gt; ||BNSF Warbonnet Dash 9-44CW ||BNSF dash nine set
|
|-
|KUID:45588:1222&gt; ||DS4-4-10 Reading 729 ||Baldwin switcher model DS-4-4-10 as used on the Reading. This unit was rebuilt with an EMD engine...
|
|-
|KUID:45588:1224&gt; ||DS4-4-10 Reading 38 ||Baldwin switcher model DS-4-4-10 as used on the Reading. US loco sound effects by Wulf_9 enginesp...
|
|-
|KUID:45588:1540&gt; ||DS4-4-10 CNJ 1073 ||Baldwin DS4-4-10 switcher operated by the Central Railroad of New Jersey (3 units, #1072-1074). ...
|
|-
|KUID:45588:1615&gt; ||DS4-4-10 WM 133 Speedlettering ||Baldwin switcher model DS-4-4-10 as used on the Western Maryland. WM owned only 2 units, #133 and...
|
|-
|KUID2:45588:1959:1&gt; ||DS4-4-10 Monongahela 421 ||Baldwin switcher model DS-4-4-10 as used on the Monongahela Railway, which operated 27 of these e...
|
|-
|KUID:45588:1960&gt; ||DS4-4-10 Monongahela 412 ||Baldwin switcher model DS-4-4-10 as used on the Monongahela Railway, which operated 27 of these e...
|
|-
|KUID:45588:4465&gt; ||CW44-8 V&amp;O 4460-4465 ||GE CW44-8 (Dash 9 predecessor) in Appalchian Lines (V&amp;O) color scheme. Contributors (Dependencie...
|
|-
|KUID:47092:15312&gt; ||IM wellcars 1-40ft/1-48ft ||A wellcarpack! you need realsquash's bogies for these! which they can be found here at this link ...
|
|-
|KUID:47092:15313&gt; ||IM wellcars 1-40ft ||A wellcarpack! you need realsquash's bogies for these! which they can be found here at this link ...
|
|-
|KUID:47092:15314&gt; ||IM wellcars 2-40ft ||A wellcarpack! you need realsquash's bogies for these! which they can be found here at this link ...
|
|-
|KUID:47092:15315&gt; ||IM wellcars 2-48ft ||A wellcarpack! you need realsquash's bogies for these! which they can be found here at this link ...
|
|-
|KUID:47092:15316&gt; ||IM wellcars 1-48ft ||A wellcarpack! you need realsquash's bogies for these! which they can be found here at this link ...
|
|-
|KUID:55290:100015&gt; ||NS HORSEHEAD Dash 9-44CW ||THIS IS A NS HORSEDHEAD DASH 9 MADE BY JUSTIN AND REPAINTED BY SURESHOT28 Contributors (Dependen...
|
|-
|KUID2:55290:60000:1&gt; ||NS 8-40b #4800 ||GE B40-8 NS, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|}


===group-17 (-4)===

{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID 
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description  
!style=&quot;width:08%&quot; |Repairer
|-
| &amp;lt;KUID2:55290:60003:1&gt; ||NS 8-40b #4804 ||GE B40-8 NS, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
|KUID2:55290:60005:1&gt; ||NS 8-40b #4805 ||GE B40-8 NS, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
|KUID2:55290:60007:1&gt; ||CR 8-40b #5083 ||GE B40-8 CR, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
|KUID2:55290:60008:1&gt; ||CR 8-40b #4804 NS Patch ||GE B40-8 CR, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
|KUID2:55290:60009:1&gt; ||CR 8-40b #5077 ||GE B40-8 CR, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
|KUID2:55290:60010:1&gt; ||CR 8-40b #4808 NS PATCH ||GE B40-8 CR, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
|KUID2:55290:60011:1&gt; ||CR 8-40b #5959 CSX PATCH ||GE B40-8 CR, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
|KUID2:55290:60012:1&gt; ||CR 8-40b #5954 CSX Patch ||GE B40-8 CR, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
|KUID2:55290:60013:1&gt; ||CSX 8-40b #5945 ||GE B40-8 CR, Thanks to CSX_sd60 for the great horn, Thanks to Weevil for the nice eng Spec, Wulf ...
|
|-
|KUID:58843:10052&gt; ||IC 4-4-2 Sleeper ||On February 4, 1911, The Illinois Central Railroad renamed its 'Chicago &amp; New Orleans Limited' as...
|
|-
|KUID:58843:10054&gt; ||IC 6-6-4 Sleeper King Coal ||On February 4, 1911, The Illinois Central Railroad renamed its 'Chicago &amp; New Orleans Limited' as...
|
|-
|KUID:58843:10055&gt; ||IC 6-6-4 Sleeper King Cotton ||On February 4, 1911, The Illinois Central Railroad renamed its 'Chicago &amp; New Orleans Limited' as...
|
|-
|KUID:58843:10056&gt; ||IC 6-6-4 Sleeper Sugarland ||On February 4, 1911, The Illinois Central Railroad renamed its 'Chicago &amp; New Orleans Limited' as...
|
|-
|KUID:58843:10057&gt; ||IC 6-6-4 Sleeper Timberland ||On February 4, 1911, The Illinois Central Railroad renamed its 'Chicago &amp; New Orleans Limited' as...
|
|-
|KUID:63971:110018&gt; ||Pilbara rail Dash 9-44CW ||GE dash-9 in pilbara rail livery Contributors (Dependencies)...
|
|-
|KUID:63971:110019&gt; ||BHP Dash 9-44CW ||GE dash-9 in BHP livery Contributors (Dependencies)...
|
|-
|KUID:63971:110020&gt; ||Hammersley Iron Dash 9-44CW ||GE dash-9 in Hammersley Iron livery Contributors (Dependencies)...
|
|-
|KUID:63971:110021&gt; ||GE Green Machine Dash 9-44CW ||GE dash-9 in corporate livery Contributors (Dependencies)......
|
|-
|KUID:74708:37003&gt; ||raccord-4x2 ||raccord 4 Ã  2 voies
|
|-
|KUID:74708:38007&gt; ||pont-4voies ||pont routier 4 voies
|
|}


===group-18 (-4)===

{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID 
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description  
!style=&quot;width:08%&quot; |Repairer
|-
| &amp;lt;KUID2:82412:20115:1&gt; ||Products-Car-C-4x4-01 ||Products-Car-C-4x4-01
|
|-
|KUID2:82412:4001022:1&gt; ||JVC-49-Oak-S-LO-29m-01 ||JVC Tree 2 (jvc_trees_49 oak summer lo_res 29m) with reduced texture size especially for applicat...
|
|-
|KUID2:82412:4001023:1&gt; ||JVC-46-Beech-S-LO-08m-01 ||JVC Tree 2 (jvc__trees_46 beech summer lo_res 8m) with reduced texture size especially for applic...
|
|-
|KUID2:82412:70074:1&gt; ||Bush-Spline-10m-44-DMD-BLB ||David Drake's BlackBerry-spline-3 with reduced texture size especially for application within lar...
|
|-
|KUID2:93502:60:1&gt; ||A10 engine 0-4-2S class engine ||A10 #6 is one of the oldest steam engines still in operation in the southern hemisphere. Contrib...
|
|-
|KUID:93502:61&gt; ||3F6I A10 engine 0-4-2S class engine ||The A10 is one of the oldest steam engines still in operation in the southern hemisphere.
|
|-
|KUID:93502:78&gt; ||Blue A10 engine 2-4-0S class engine ||The A10 is one of the oldest steam engines sto run on the QR network, this one uses to run the No...
|
|-
|KUID:93502:97&gt; ||DD17 engine 4-6-4ST class engine ||DD17 #1051 is one of the last four DD17 steam tank engines still in operation in the southern hemisphere.
|
|-
|}

==Pages 1-1 &lt;kuid:-5&gt;==
===group-19 (-5)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID 
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description  
!style=&quot;width:08%&quot; |Repairer
|-
|&lt;KUID:115270:110007&gt; || A-5 - Skrzyzowanie drog rownorzednych || A-5 - Skrzyzowanie drog rownorzednych || &amp;nbsp;
|-
|  &lt;KUID2:193148:1385:1&gt; || NSWGR D-59 class || NSWGR 59 class Locomotive 2004/2006 compatible This content is revised with the kind permission o... || &amp;nbsp;
|-
|  &lt;KUID2:193148:1392:1&gt; || NSWGR D-59 class tender || NSWGR D-59 class tender 2004/2006 compatible This content is revised with the kind permission of ... || &amp;nbsp;
|-
|  &lt;KUID:438196:1151&gt; || kiha187-502 || Japanese Diesel Car kiha187-502, Limited Express 'Super Inaba' of West JR. Make a unit with kiha1... || &amp;nbsp;
|-
|  &lt;KUID:440847:42001&gt; || PKP SU42-524 PR.Gdynia || SU42 Contributors (Dependencies):  || &amp;nbsp;
|-
|  &lt;KUID:62456:419&gt; || BR 189 023-5 || Model: BR 189 Railion Baujahr: 2002 Hersteller: Siemens Dauerleistung: 6400 kW Vmax: 140 km... || &amp;nbsp;
|-
|  &lt;KUID2:69974:37021:1&gt; || Stuetzmauer-5M ||  || &amp;nbsp;
|-
|  &lt;KUID2:69974:37029:1&gt; || Stuetzmauer03-5M ||  || &amp;nbsp;
|-
|  &lt;KUID2:69974:37030:1&gt; || Stuetzmauer05-5M ||  || &amp;nbsp;
|-
|  &lt;KUID2:69974:37031:1&gt; || Stuetzmauer07-5M ||  || &amp;nbsp;
|-
|  &lt;KUID2:69974:37032:1&gt; || Stuetzmauer10-5M ||  || &amp;nbsp;
|-
|  &lt;KUID2:82412:5000016:1&gt; || Warehouse-Ind-50m-S2-Mullan-001 || Large warehouse for rail and truck with two rail loadingbays. Not based on any real warehouse. || &amp;nbsp;
|-
|  &lt;KUID2:82412:5000019:1&gt; || Load-Yard-50m-S2-Lucky-Friday-001 || Load-Yard-50m-S2-Lucky-Friday-001 || &amp;nbsp;
|-
|  &lt;KUID2:82412:6097014:1&gt; || MILW-Sub-HV-Connect-50m-01 || MILW-Sub-HV-Connect-50m-01 || &amp;nbsp;
|-
|  &lt;KUID2:82412:6097015:1&gt; || MILW-Sub-HV-WP-50m-003 || MILW-Sub-HV-WP-50m-003 || &amp;nbsp;
|}
==Pages 1-3 &lt;kuid:-6&amp;gt; and (-6)==
===group-20 (-6)===

{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; |Description 
!style=&quot;width:07%&quot; |Repairer 
|-
| &amp;lt;KUID:115270:110008&amp;gt; || A-6A - Skrzyzowanie z drogami podporzadkowanymi  || A-6A - Skrzyzowanie z drogami podporzadkowanymi ||
|-
| &amp;lt;KUID:115270:110009&amp;gt; || A-6B - Skrzyzowanie z droga podporzadkowana R  || A-6B - Skrzyzowanie z droga podporzadkowana R ||
|-
| &amp;lt;KUID:115270:110010&amp;gt; || A-6C - Skrzyzowanie z droga podporzadkowana L  || A-6C - Skrzyzowanie z droga podporzadkowana L ||
|-
| &amp;lt;KUID:115270:110011&amp;gt; || A-6D - Skrzyzowanie z droga podporzadkowana 1kier R  || A-6D - Skrzyzowanie z droga podporzadkowana 1kier R ||
|-
| &amp;lt;KUID:115270:110012&amp;gt; || A-6E - Skrzyzowanie z droga podporzadkowana 1kier L  || A-6E - Skrzyzowanie z droga podporzadkowana 1kier L ||
|-
| &amp;lt;KUID2:135744:1283:1&amp;gt; || SP 0-6-0 Switcher #1283  || This is a Southern Pacific 0-6-0 Switcher #1283 reskinned from AltoDave's Union Pacific 0-6-0 Swi... ||
|-
| &amp;lt;KUID2:135744:1284:1&amp;gt; || SP 0-6-0 Switcher #1284  || This is a Southern Pacific 0-6-0 Switcher #1284 reskinned from AltoDave's Union Pacific 0-6-0 Swi... ||
|-
| &amp;lt;KUID2:135744:1285:1&amp;gt; || SP 0-6-0 Switcher #1285  || This is a Southern Pacific 0-6-0 Switcher #1285 reskinned from AltoDave's Union Pacific 0-6-0 Swi... ||
|-
| &amp;lt;KUID2:135744:15573:2&amp;gt; || Detroit &amp; Mackinac 0-6-0 Switcher Tender  || This is the tender that goes with the Detroit &amp; Mackinac 0-6-0 Switcher. It is being re-released ... ||
|-
| &amp;lt;KUID2:135744:6830:2&amp;gt; || Detroit &amp; Mackinac 0-6-0 Switcher 174  || This is an update to my original Detroit &amp; Mackinac 0-6-0 Switcher. I have fixed many problems an... ||
|-
| &amp;lt;KUID2:135744:6831:2&amp;gt; || Pere Marquette 0-6-0 Switcher 1132  || This is an update to my original Pere Marquette 0-6-0 Switcher. I have fixed many problems and bu... ||
|-
| &amp;lt;KUID2:135744:6832:2&amp;gt; || Pere Marquette 0-6-0 Switcher Tender  || This is the tender that goes with the Pere Marquette 0-6-0 Switcher. It is being re-released in t... ||
|-
| &amp;lt;KUID:136383:1000&amp;gt; || 218 001-6  || paintshed skin ||
|-
| &amp;lt;KUID:208456:1025&amp;gt; || CFL-60 DCL  || Dieser Content enthält eine CFL-60 DCL welche bei der Parkeisenbahn Chemnitz im Küchwaldpark mit ... ||
|-
| &amp;lt;KUID:4468:225&amp;gt; || 4-6-2 Duchess Class Tender BR Blue  || 10,000 gallon Tender for the 4-6-2 Duchess Class. ||
|-
| &amp;lt;KUID:4468:4001&amp;gt; || 4-6-2 West Country Class SR  || 4-6-2 West Country Class SR SR No. BR No. Name Date Built 21C101 34001 Exeter 1945 Protot... ||
|-
| &amp;lt;KUID:4468:4002&amp;gt; || 4-6-2 West Country Class SR Tender  || 4-6-2 West Country Class SR Tender At the end of World War II, a fast and powerful mixed traffic... ||
|-
| &amp;lt;KUID:4468:4049&amp;gt; || 4-6-2 Battle of Britain Class BR Green  || 4-6-2 West Country Class SR (Battle of Britain Class) SR No. BR No. Name Date Built 21C151 34... ||
|-
| &amp;lt;KUID:4468:4050&amp;gt; || 4-6-2 Battle of Britain Class BR Green Tender  || 4-6-2 Battle of Britain Class BR Green Tender At the end of World War II, a fast and powerful mi... ||
|-
| &amp;lt;KUID:4468:4771&amp;gt; || 2-6-2 V2 LNER Green  || Gresley Mixed Traffic V2 2-6-2 4771 Green Arrow 4806 Green Howard 4844 Coldstreamer (60873) 48...  ||&amp;nbsp;
|}
&amp;nbsp;
===group-21 (-6)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
|&amp;lt;KUID:4468:775&amp;gt; || BR 4-6-0 N15 King Arthur Class Tender  || 5000 gallon Tender for the BR 4-6-0 N15 King Arthur Class. ||
|-
| &amp;lt;KUID:44797:6830&amp;gt; || NYC-060-6825  || This is my first attempt at engine building. The engine I selected to build is NYC USRA design. T... ||
|-
| &amp;lt;KUID:45588:10229&amp;gt; || Pittsburgh &amp; West Virginia 4-6-2 Pacific 200 Tender  || Pittsburgh &amp; West Virginia 4-6-2 Pacific Tender, Coal, lettered for #200. Original tender bogey w... ||
|-
| &amp;lt;KUID:45588:10230&amp;gt; || Pittsburgh &amp; West Virginia 4-6-2 Pacific 200  || P&amp;WV operated 3 light Pacifics, #200-202. Passenger service was discontinued before the Connelsvi... ||
|-
| &amp;lt;KUID:45588:1779&amp;gt; || Clinchfield 4-6-2 Pacific 153  || Clinchfield operated 5 light Pacifics, class P-1 #150-152 initially for passenger service and cla... ||
|-
| &amp;lt;KUID2:46075:6930:4&amp;gt; || UP 0-6-0 #4609  || The original NYC 0-6-0 engine was done by Bill Klene of New Lenox, IL. Rebuilt here into a late m... ||
|-
| &amp;lt;KUID:46219:65&amp;gt; || GWR 94xx 0-6-0T class engine  || A GWR 94xx 0-6-0T Hawksworth engine. Built at Swindon engineering works in 1947. ||
|-
| &amp;lt;KUID:46219:85&amp;gt; || GWR 43xx 2-6-0 Mogul Engine  || GWR 2-6-0 4300 class Mogul Locomotive ||
|-
| &amp;lt;KUID:58843:10054&amp;gt; || IC 6-6-4 Sleeper King Coal  || On February 4, 1911, The Illinois Central Railroad renamed its 'Chicago &amp; New Orleans Limited' as... ||
|-
| &amp;lt;KUID:58843:10055&amp;gt; || IC 6-6-4 Sleeper King Cotton  || On February 4, 1911, The Illinois Central Railroad renamed its 'Chicago &amp; New Orleans Limited' as... ||
|-
| &amp;lt;KUID:58843:10056&amp;gt; || IC 6-6-4 Sleeper Sugarland  || On February 4, 1911, The Illinois Central Railroad renamed its 'Chicago &amp; New Orleans Limited' as... ||
|-
| &amp;lt;KUID:58843:10057&amp;gt; || IC 6-6-4 Sleeper Timberland  || On February 4, 1911, The Illinois Central Railroad renamed its 'Chicago &amp; New Orleans Limited' as... ||
|-
| &amp;lt;KUID:63290:2&amp;gt; || D&amp;RG 2-6-0 2  || Denver &amp; Rio Grande Rail Way Class 35 3 foot gauge 2-6-0 Number 2, the Tabi-wachi. This engine is... ||
|-
| &amp;lt;KUID:63290:3&amp;gt; || D&amp;RG 2-6-0 3  || Denver &amp; Rio Grande Rail Way Class 35 3 foot gauge 2-6-0 Number 3, the Shou-wa-no. This engine is... ||
|-
| &amp;lt;KUID:63290:5&amp;gt; || D&amp;RG 2-6-0 5  || Denver &amp; Rio Grande Rail Way Class 35 3 foot gauge 2-6-0 Number 5, the Ouray. This engine is show... ||
|-
| &amp;lt;KUID:63290:8&amp;gt; || D&amp;RG 2-6-0 8  || Denver &amp; Rio Grande Rail Way Class 35 3 foot gauge 2-6-0 Number 8, the Arkansas. This engine is s... ||
|-
| &amp;lt;KUID2:7592:10169:1&amp;gt; || CRR 0-6-0 Tender #9049  || USRA 6000gallon/10ton Tender. Original in NYC paint by Bill Klene, relettered for CRR. This is a ... ||
|-
| &amp;lt;KUID2:7592:10170:1&amp;gt; || CRR 0-6-0 #9049  || The original NYC 0-6-0 engine was done by Bill Klene of New Lenox, IL. Rebuilt here into a late m... ||
|-
| &amp;lt;KUID2:7592:10174:1&amp;gt; || GN 0-6-0 #27  || The original NYC 0-6-0 engine was done by Bill Klene of New Lenox, IL. Rebuilt here into a late m... ||
|-
| &amp;lt;KUID2:82412:22003:1&amp;gt; || Lamp-No-Pool-65-001  || Lamp-No-Pool-65-001  ||&amp;nbsp;
|}
&amp;nbsp;
===group-22 (-6)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
| &amp;lt;KUID2:82412:22004:1&amp;gt; || Lamp-Wall-65-001  || Lamp-Wall-65-001 ||
|-
| &amp;lt;KUID2:82412:22005:1&amp;gt; || Lamp-Wood-Pool-65-001  || Lamp-Wood-Pool-65-001 ||
|-
| &amp;lt;KUID2:82412:22006:1&amp;gt; || Lamp-Wall-60-001  || Lamp-Wall-60-001 ||
|-
| &amp;lt;KUID2:82412:4001005:1&amp;gt; || JVC-60-Oak-S-LO-24m-01  || JVC Oak Tree (JVC__Trees_60 Oak summer 24m) with reduced texture size especially for application ... ||
|-
| &amp;lt;KUID2:82412:4001006:1&amp;gt; || JVC-60-Oak-S-LO-30m-01  || JVC Oak Tree (JVC__Trees_60 Oak summer 30m) with reduced texture size especially for application ... ||
|-
| &amp;lt;KUID:93502:63&amp;gt; || PB15 engine 4-6-0S class engine  || The PB15 is one of the steam engines still in operation in the southern hemisphere. ||
|-
| &amp;lt;KUID:93502:64&amp;gt; || 3F6I PB15 engine 4-6-0S class engine  || The PB15 is one of the steam engines still in operation in the southern hemisphere. ||
|-
| &amp;lt;KUID:93502:97&amp;gt; || DD17 engine 4-6-4ST class engine  || DD17 #1051 is one of the last four DD17 steam tank engines still in operation in the southern hem...  ||&amp;nbsp;
|}
&amp;nbsp;
==Group-23 &lt;kuid:-7&gt; and (-7)==
;Pages 1-3 combined

'''&lt;big&gt;NOTE on formats:&lt;/big&gt;''' At this juncture, having verified the above groups can be put into a table format, revising presentation into longer combined table instead of accepting the short list pages of the https://www.auran.com/planetauran/dls_cleanup_list.php.


'''Searches finding &lt;kuid:-7&gt; and '-7' in names:'''
&amp;nbsp;
===group-23a (-7's)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
| &lt;KUID:101340:512700&gt; || BWL C30-7 5127 || A C30-7 for use on the Blue Water Line Contributors (Dependencies): ... 
| &amp;nbsp;
|-
| &lt;KUID:108523:100001&gt; || DHI-71 || The Clyde DHI-71 was originally built for the sugar industry. The first entered service in 1954 a... || &amp;nbsp;
|-
| &lt;KUID2:135744:191:1&gt; || Detroit &amp; Mackinac C30-7 381 || This is a former Detroit &amp; Mackinac C30-7 #381. You can still see this locomotive on the Lake St... || &amp;nbsp;
|-
| &lt;KUID2:135744:192:1&gt; || LSRC C30-7 1280 || This is a loco found on the Lake State Railway Company in the former Detroit &amp; Mackinac Railroad ... || &amp;nbsp;
|-
| &lt;KUID2:135744:8074:1&gt; || LSRC C30-7 1195 (Weathered) || Lake State Railway Company C30-7 1195 City of East Tawas (Weathered Version) Lake State Railway ... || &amp;nbsp;
|-
| &lt;KUID2:135744:8075:1&gt; || LSRC C30-7 1195 || Lake State Railway Company C30-7 1195 City of East Tawas Lake State Railway Company is a railroa... || &amp;nbsp;
|-
| &lt;KUID2:135744:8076:1&gt; || LSRC C30-7 181 || Lake State Railway Company C30-7 181 City of Bay City Lake State Railway Company is a railroad c... || &amp;nbsp;
|-
| &lt;KUID2:135744:850:1&gt; || Conrail C30-7 Patched || Here is the newest locomotive to come from the Icebreaker Locomotive Works.....a Conrail C30-7 pa... || &amp;nbsp;
|-
| &lt;KUID:136383:1001&gt; || 218 232-7 || paintshed skin || &amp;nbsp;
|-
| &lt;KUID:138423:1042&gt; || ln C30-7 || L&amp;N/Family Lines C30-7 Loco Contributors (Dependencies): ... || &amp;nbsp;
|-
| &lt;KUID:142675:500790&gt; || Ty1-76 || In 1916 railway officials had to concede that there was no heavy freight locomotive adequate to t... || &amp;nbsp;
|-
| &lt;KUID:142675:500793&gt; || Ty1-76_cab || The Prussian freight locomotive G12.2 of 1917 was named Ty1 in PKP service. Polycounts: 12012 b... || &amp;nbsp;
|-
| &lt;KUID:1551:10014&gt; || SNCF TGV-PSE Unit 5-7 || TGV Paris Sud-est Unit 5-7 Company: SNCF || &amp;nbsp;
|-
| &lt;KUID:1551:10023&gt; || SNCF TGV-PSE Unit 5-7 || TGV Paris Sud-est Unit 5-7 Company: SNCF || &amp;nbsp;
|-
| &lt;KUID:35815:101&gt; || CBQ C30-7 101 || A C30-7 In Burlington red Aliased to orignal mesh by Justin Cornell Contributors (Dependencies):... || &amp;nbsp;
|-
| &lt;KUID:35815:1550&gt; || L&amp;N C30-7 931 || C30-7 skinned for the L&amp;N Original mesh by Justin Cornell Uses Auto running number script by Wulf... || &amp;nbsp;
|-
| &lt;KUID:35815:2253&gt; || WP C30-7 2253 || Western Pacific C30-7 Aliased to original mesh by Justin Cornell Contributors (Dependencies): &lt;u... || &amp;nbsp;
|-
| &lt;KUID:35815:3601&gt; || Clinchfield C30-7 || Clinchfield C30-7 Aliased to original mesh by Justin Cornell Contributors (Dependencies): ... || &amp;nbsp;
|-
| &lt;KUID:35815:5001&gt; || MILW C30-7 5001 || Aliased reskin of Justin Cornells C30-7 into Milwaukee Road #5001 Skin done in Photoshop Contrib... || &amp;nbsp;
|-
| &lt;KUID:35815:501&gt; || MRL C30-7 501 || Alias skin for Justin Cornell's C-30-7 for Montana Ral Link Contributors (Dependencies): ... || &amp;nbsp;

|-
| &lt;KUID:35815:5127&gt; || BN C30-7 5127 || Aliased reskin of Justin Cornells C30-7 into Burlington Northern #5127 Skin done in Photoshop Co... || &amp;nbsp;
|-
| &lt;KUID:35815:8075&gt; || SP C30-7 || Aliased reskin of Justin Cornells C30-7 into Southern Pacific Skin done in Photoshop Contributor... || &amp;nbsp;
|-
| &lt;KUID:35815:931&gt; || CNW C30-7 931 || A C30-7 in CNW colors Aliased to orginal mesh by Justin Cornell Painted in Photoshop Contributor... || &amp;nbsp;
|-
|}
&amp;nbsp;
===group-23b (-7's)===
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; | Description 
!style=&quot;width:07%&quot; |Repairer 
|-
| &lt;KUID:35848:103245&gt; || BR 103.245-7 || hochleistungs-Schnellzuglok der Deutschen Bundesbahn in orientroter ... || &amp;nbsp;
|-
| &lt;KUID:45324:100022&gt; || ATSF C30-7 || C30-7 pack ATSF UP NS || &amp;nbsp;
|-
| &lt;KUID:45324:100023&gt; || UP C30-7 || C30-7 pack ATSF UP NS || &amp;nbsp;
|-
| &lt;KUID:45324:100024&gt; || Norfolk Southern C30-7 || C30-7 pack ATSF UP NS || &amp;nbsp;
|-
| &lt;KUID:45588:3304&gt; || C30-7 C&amp;O 3304 || Two of C&amp;O's 13 U30C's using the C30-7 mesh as a stand-in for a real U30C. Created from photos. ... || &amp;nbsp;
|-
| &lt;KUID:45588:3310&gt; || C30-7 C&amp;O 3310 || Two of C&amp;O's 13 U30C's using the C30-7 mesh as a stand-in for a real U30C. Created from photos. ... || &amp;nbsp;
|-
| &lt;KUID:45588:615&gt; || C30-7 Lake Superior &amp; Ishpeming 3072 || LS&amp;I bought a number of BN U30C's and C30-7's to replace their RSD12's, RSD15's, U25C's, and U23C... || &amp;nbsp;
|-
| &lt;KUID:45588:616&gt; || C30-7 Lake Superior &amp; Ishpeming 3006 || LS&amp;I bought a number of BN U30C's and C30-7's to replace their RSD12's, RSD15's, U25C's, and U23C... || &amp;nbsp;
|-
| &lt;KUID:45588:756&gt; || C30-7 Cartier Railway 34 || QCM did not own C30-7's, but did own C630's (30-39), C636's (77-79), and M636's (41-49, 71-76, 81... || &amp;nbsp;
|-
| &lt;KUID:45588:758&gt; || C30-7 Delaware &amp; Hudson 758 || D&amp;H did not own C30-7's, but swapped their 3 SD45's to EL for 3 U33C's, 751-753, then bought 9 br... || &amp;nbsp;
|-
| &lt;KUID:45588:759&gt; || C30-7 Delaware &amp; Hudson 759 || D&amp;H did not own C30-7's, but swapped their 3 SD45's to EL for 3 U33C's, 751-753, then bought 9 br... || &amp;nbsp;
|-
| &lt;KUID:45588:760&gt; || C30-7 Cartier Railway 42 || QCM did not own C30-7's, but did own C630's (30-39), C636's (77-79), and M636's (41-49, 71-76, 81... || &amp;nbsp;
|-
| &lt;KUID:45588:761&gt; || C30-7 Cartier Railway 75 || QCM did not own C30-7's, but did own C630's (30-39), C636's (77-79), and M636's (41-49, 71-76, 81... || &amp;nbsp;
|-
| &lt;KUID:45588:762&gt; || C30-7 Delaware &amp; Hudson 762 || D&amp;H did not own C30-7's, but swapped their 3 SD45's to EL for 3 U33C's, 751-753, then bought 9 br... || &amp;nbsp;
|-
| &lt;KUID:45588:792&gt; || C30-7 Cartier Railway 81 || QCM did not own C30-7's, but did own C630's (30-39), C636's (77-79), and M636's (41-49, 71-76, 81... || &amp;nbsp;
|-
| &lt;KUID:55290:850&gt; || CONRAIL C30-7 || THIS A REPAINT OF NORFOLKSOUTHERN37 C30-7. REPAINTED BY SURESHOT28. Contributors (Dependencies):... || &amp;nbsp;
|-
| &lt;KUID:55290:851&gt; || B&amp;O C30-7 || THIS A REPAINT OF NORFOLKSOUTHERN37 C30-7. REPAINTED BY SURESHOT28. Contributors (Dependencies):... || &amp;nbsp;
|-
| &lt;KUID:55290:852&gt; || NW C30-7 || THIS IS A REPAINT OF NORFOLKSOUTHER37 C30-7A. PAINTED BY SURESHOT28 Contributors (Dependencies):... || &amp;nbsp;
|-
| &lt;KUID:55290:854&gt; || CN C30-7 || THANKS TO NORFOLKSOUTHERN37 FOR THE MESH. REPAINTED BY SURESHOT28. Contributors (Dependencies): ... || &amp;nbsp;
|-
| &lt;KUID2:78193:923:1&gt; || Drivable Robt E. Lee Steamboat -7m || Steamboat for 7m deep track Contributors (Dependencies): ... || &amp;nbsp;
|-
| &lt;KUID2:82412:6097035:1&gt; || Powerline-735kV-Cable-01 || Powerline 735kV Cable, to use with Powerline-Tower's (kuid2:82412:6097031:1 and kuid2:82412:60970... || &amp;nbsp;
|-
| &lt;KUID2:82412:6097038:1&gt; || Powerline-735kV-Cable-03 || Powerline 735kV Cable, to use with Powerline-Tower's (kuid2:82412:6097033:1). Just click the cabl... || &amp;nbsp;
|}
&amp;nbsp;
==Kuid's -8, -9 &amp; -10==

===group-24 (-8's)===
&amp;nbsp;
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; |Description 
!style=&quot;width:07%&quot; |Repairer 
|-
|&lt;KUID:115270:110014&gt; || A-8 - Skrzyzowanie ruch okrezny || A-8 - Skrzyzowanie ruch okrezny || &amp;nbsp;
|-
|&lt;KUID2:135744:146:1&gt; || Detroit &amp; Mackinac #124 4-8-2 Mountain Type || Here is a Detroit &amp; Mackinac Railroad 4-8-2 Mountain Type locomotive #124 reskinned from Bill Sco... || &amp;nbsp;
|-
|&lt;KUID2:135744:148:1&gt; || Pere Marquette #1224 4-8-2 Mountain Type || Here we have a Pere Marquette 4-8-2 Mountain Type loco #1224. This was reskinned from Bill Scott... || &amp;nbsp;
|-
|&lt;KUID:37049:1&gt; || BCR Dash-8 40CM || BC RAIL Dash-8 40CM || &amp;nbsp;
|-
|&lt;KUID:37049:2&gt; || BCR Dash-8 40CM || BC RAIL Dash-8 40CM || &amp;nbsp;
|-
|&lt;KUID:37049:3&gt; || BCR Dash-8 40CM || BC RAIL Dash-8 40CM || &amp;nbsp;
|-
|&lt;KUID:45588:4465&gt; || CW44-8 V&amp;O 4460-4465 || GE CW44-8 (Dash 9 predecessor) in Appalchian Lines (V&amp;O) color scheme. Contributors (Dependencie... || &amp;nbsp;
|-
|&lt;KUID:74708:37027&gt; || carrefour-8x6 || carrefour entre route principal8m. et route secondaires 6m. || &amp;nbsp;
|-
|&lt;KUID:74708:37028&gt; || carrefour-8x6clair || carrefour entre route principal8m. et route secondaires 6m. || &amp;nbsp;
|-
|&lt;KUID2:7592:10175:1&gt; || CRR #311 4-8-2 Mountain || The CRR #311 is a fictional roadnumber of the USRA Mountain Type Locomotive owned by nearly every... || &amp;nbsp;
|-
|&lt;KUID2:7592:10178:1&gt; || GN #2507 4-8-2 Mountain || The GN #2507 is a prototypical roadnumber of the USRA Mountain Type Locomotive owned by nearly ev... || &amp;nbsp;
|-
|&lt;KUID2:7592:10180:1&gt; || UP #7000 4-8-2 Mountain || The UP #7000 is a prototypical roadnumber of the USRA Mountain Type Locomotive owned by nearly ev... || &amp;nbsp;
|-
|&lt;KUID2:7592:10182:1&gt; || L&amp;N #419 4-8-2 Mountain || The L&amp;N #419 4-8-2 Mountain is a fictional roadnumber of the USRA Mountain Type Locomotive owned ... || &amp;nbsp;
|-
|&lt;KUID2:7592:10184:1&gt; || Southern #1409 4-8-2 Mountain || The Southern #1409 4-8-2 Mountain is a fictional roadnumber of the USRA Mountain Type Locomotive ... || &amp;nbsp;
|-
|&lt;KUID2:7592:10186:1&gt; || GN #2512 4-8-2 Mountain || The GN #2512 is a prototypical roadnumber of the USRA Mountain Type Locomotive owned by nearly ev... || &amp;nbsp;
|-
|&lt;KUID2:7592:10187:1&gt; || DMIR #244 4-8-2 Mountain || The UP #7000 is a prototypical roadnumber of the USRA Mountain Type Locomotive owned by nearly ev... || &amp;nbsp;
|-
|&lt;KUID:79097:1001&gt; || Frisco 1522 4-8-2 'Mountain Type' || The Frisco 1522 was built by the Baldwin Locomotive Company in 1925 and has a wheel arrangement o... || &amp;nbsp;
|-
|&lt;KUID2:82412:22002:1&gt; || Lamp-Wall-80-001 || Lamp-Wall-80-001 || &amp;nbsp;
|-
|&lt;KUID:9999:10023&gt; || OBB CAT 50-81 Bmpz-dl || City Airport Train Doppelstockwagen der Ö³terreichisen Bundesbahnen AG Based on the DB DBuza 747... || &amp;nbsp;
|-
|&lt;KUID:9999:10025&gt; || OBB Wiesel 50-81 Bmpz-dl || City Airport Train Doppelstockwagen der Ö³terreichisen Bundesbahnen AG Based on the DB DBuza 747... || &amp;nbsp;
|-
|}
&amp;npsp;
===Group-25 (-9's)===
&amp;nbsp;
{| style=&quot;font face: Times; font-size:10pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:12%&quot; |KUID
!style=&quot;width:19%&quot; |Name 
!style=&quot;width:40%&quot; |Description 
!style=&quot;width:07%&quot; |Repairer 
|-
|&lt;KUID:113556:20000&gt; || Loco -9 UP #5878 || General Electric Dash-9 in Union Pacific color scheme. Email fordtruc@norex.com.au for repaint re... ||
|-
|&lt;KUID:113556:510030&gt; || Loco -9 UP #5840 || General Electric Dash-9 in Union Pacific color scheme. Email fordtruc@norex.com.au for repaint re... ||
|-
|&lt;KUID:113556:51029&gt; || Loco SP-9 SP#245 || General Electric Dash-9 in Southern Pacific color scheme. Email fordtruc@norex.com.au for repaint... ||
|-
|&lt;KUID:113556:51040&gt; || Loco SP-9 SP#211 || General Electric Dash-9 in Southern Pacific color scheme. Email fordtruc@norex.com.au for repaint... ||
|-
|&lt;KUID:45588:4401&gt; || CW44-9 B&amp;O || General Electric CW44-9 in B&amp;O passenger (blue-black-gold-gray) color scheme normally used on E- ... ||
|-
|&lt;KUID:45588:4402&gt; || CW44-9 NYS&amp;W || GE CW44-9 as an NYS&amp;W 'Yellow Jacket'. Contributors (Dependencies): &quot;margin-top:0px;ma... ||
|-
|&lt;KUID:45588:4403&gt; || CW44-9 B&amp;O CSX || GEl CW44-9 in B&amp;O passenger (blue-black-gold-gray) color scheme normally used on E- and F-units w... ||
|-
|&lt;KUID:45588:4404&gt; || CW44-9 Western Maryland CSX || GE CW44-9 in Western Maryland 'what if' paint with CSX lettering (as in, 'what if' CSX got a clue... ||
|-
|&lt;KUID:45588:4405&gt; || CW44-9 B&amp;O CSX small || GEl CW44-9 in B&amp;O passenger (blue-black-gold-gray) color scheme normally used on E- and F-units w... ||
|-
|&lt;KUID:45588:4406&gt; || CW44-9 B&amp;O Chessie Seaboard || GEl CW44-9 in B&amp;O passenger (blue-black-gold-gray) color scheme normally used on E- and F-units w... ||
|-
|&lt;KUID:45588:4412&gt; || CW44-9 Susquehanna || GE CW44-9 as an NYS&amp;W 'Yellow Jacket'. Contributors (Dependencies): &quot;margin-top:0px;ma... ||
|-
|&lt;KUID:45588:4453&gt; || CW44-9 Western Maryland 1 || GE CW44-9 in Western Maryland 'what if' paint. Version 1 places the Fireball logo on the side of ... ||
|-
|&lt;KUID:45588:4457&gt; || CW44-9 W&amp;LE || GE CW44-9 in Wheeling &amp; Lake Erie paint (Fictional). Contributors (Dependencies): &quot;mar... ||
|-
|&lt;KUID:45588:4458&gt; || CW44-9 NYO&amp;W || GE CW44-9 in New York Ontario &amp; western paint. Another 'what if'. Usess autonumbering, with three... ||
|-
|&lt;KUID:45588:4459&gt; || CW44-9 Lehigh &amp; New England || GE CW44-9 in Lehigh &amp; New England 'what if' (fictional) paint. Contributors (Dependencies): &lt;ul ... ||
|-
|&lt;KUID:45588:4460&gt; || CW44-9 Western Maryland 2 || GE CW44-9 in Western Maryland 'what if' paint. Version 2 places the Fireball logo on the hood doo... ||
|-
|&lt;KUID:45588:4462&gt; || CW44-9 Clinchfield 4401 black || GE CW44-9 in Clinchfield 'what if' paint. Contributors (Dependencies): &quot;margin-top:0px... ||
|-
|&lt;KUID:45588:4463&gt; || CW44-9 Lehigh &amp; New England Whiskers || GE CW44-9 in Lehigh &amp; New England 'what if' (fictional) paint matching the scheme worn by the RS2... ||
|-
|&lt;KUID:45588:4466&gt; || CW44-9 Nickel Plate 4412 || GE Dash-9 in Nickel Plate Road paint scheme (Fictional). Contributors (Dependencies): ... ||
|-
|&lt;KUID:45588:4467&gt; || CW44-9 Nickel Plate 4403 || GE Dash-9 in Nickel Plate Road paint scheme (Fictional). Contributors (Dependencies): ... ||
|-
|&lt;KUID:45588:4470&gt; || CW44-9 Utah Belt || General Electric Dash-9 in Utah Belt color scheme. Contributors (Dependencies): &quot;margi... ||
|-
|&lt;KUID:45588:4471&gt; || CW44-9 Chessie System (B&amp;O) || GE CW44-9 in Chessie System paint. Contributors (Dependencies): &quot;margin-top:0px;margin... ||
|-
|&lt;KUID:45588:4472&gt; || CW44-9 Chessie System (C&amp;O) || GE CW44-9 in Chessie System paint, owned by the Chesapeake &amp; Ohio Railway. Contributors (Depende... ||
|-
|&lt;KUID:45588:4473&gt; || CW44-9 Chessie System (WM) || GE CW44-9 in Chessie System paint, owned by Western Maryland Railway. Contributors (Dependencies... ||
|-
|&lt;KUID:49267:15261&gt; || Sggmrss-90' B Empty (white) || Sggmrss 90 Empty B unit (back) White Will load: - Auran's 20' and 40' Container - 20' Containers ... ||
|-
|&lt;KUID2:82412:300126:1&gt; || MILW-Caboose-991265-01 || A caboose of The Milwaukee Road, originally created by Deadfred by using paintshed. The caboose t... ||
|-
|&lt;KUID2:82412:300127:1&gt; || MILW-Caboose-991269-01 || A caboose of The Milwaukee Road, originally created by Deadfred by using paintshed. The caboose t... ||
|-
|&lt;KUID2:82412:4001020:1&gt; || JVC-9-Birch-S-LO-25m-01 || JVC Oak Tree (JVC_S1_Trees_9 Birch 25m Summer) with reduced texture size especially for applicati... ||
|-
|&lt;KUID:85324:5430&gt; || CW44-9 Jersey Central 5430 || GE CW44-9 in Central of New Jersey 'what if' paint. Colors by Jacob Newman at http://jnewman.m72e... ||
|-
|&lt;KUID:85324:5431&gt; || CW44-9 Jersey Central 5431 || GE CW44-9 in Central of New Jersey 'what if' paint. Colors by Jacob Newman at http://jnewman.m72e... ||
|-
|&lt;KUID:-10:170&gt; || Gen DL500 mph rhd || (null) ||
|-
|&lt;KUID:-10:172&gt; || Gen1960 op1 || (null) ||
|-
|&lt;KUID:-10:173&gt; || Gen RC4 || (null) ||
|-
|&lt;KUID:-10:221&gt; || Gen 218 || (null) ||
|-
|}
==Missing on DLS==
The second list below is '''an add to list'''... assets called for '''''when something has been downloaded''''' that includes the asset on the route or session '''as a dependency''', but which has not been uploaded to the DLS by the asset creator. The first list is an index to those sites which provide Trainz content, and usually, host downloading services of their own. Several listings therein however make it policy to place their content on the DLS for free access by all.
&amp;nbsp;
===Content source sites===
{| style=&quot;background-color:#f9f9f9;{{Text default color}}; font face: Verdana,Garamond,Helvetica,Arial; font-size:14pt; width:100%; padding:1px; border:3px solid green; &quot;
! &lt;u&gt;Table of [https://www.auran.com/TRS2004/DLS.php Alternative source sites]&lt;/u&gt;&lt;hr/&gt; &lt;div style=&quot;font face:Arial;&quot;&gt;&lt;small&gt;(use column one for note in Column five below)&lt;/small&gt;&lt;/div&gt;
|-
|
{| cellspacing=&quot;2&quot; border=&quot;1&quot; cellpadding=&quot;3&quot; style=&quot;font face: Garamond,Roman,Times,Arial; font-size:12pt; width:100%; padding:3px; border:1px solid blue; text-align:left; background:lightyellow;{{Text default color}};&quot;
!style=&quot;width:12%&quot; |Nickname
!style=&quot;width:28%&quot; |Common name
!N3V-Prtr
!Description 
!style=&quot;width:15%&quot; |login Url 
!style=&quot;width:15%&quot; |DnLd url
|-
| HP-Tz
|HP-Trainz
|yes
|user group, freeware and payware assets and routes
|[http://www.hp-trainz.de/html/News_EN.html website]
|[http://www.hp-trainz.de/html/Geschenkt_EN.html downloads]
|-
| TPR
|TrainzProRoutes
|yes
|Freeware (mainly) user group
|[http://www.trainzproroutes.org/ website]
|[http://www.trainzproroutes.org/tprdownloads/index.php downloads]
|-
| JR &amp; J-R || Jointed Rail
|yes || Mostly payware Prof. content
|[http://www.jointedrail.com/ website]
|[http://jointedrail.com/index.php/customer/account/login/ downloads]
|-
| TNG || Trainz Narrowgaugers ||yes|| User interest group
| [http://www.virtualrailroader.com/TNG.html website]
| none
|-
| Yz-Tz || Yesterdayz Trainz || n/a||User interest group training content creation and using Trainz
| [http://yesterdayztrainz.federalproductions.com/ website]
| [http://forums.auran.com/trainz/showthread.php?100965-Yesterdayz-Trainz-Group N3V forum]&lt;br/&gt;No Downloads
|}
|}
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&amp;nbsp;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&amp;nbsp;
;Assets missing on the DLS 
&amp;nbsp;
This section will give new Trainzers a www-web-wide Kuid indexed searchable source page to quickly find where an asset might be located, should they have that hated '''''missing dependency'''''' after downloading a asset such as a session or route. Asset creators and users should feel to update the page reflecting a newly discovered missing asset and delete those which are no longer 'missing' on the DLS.
&amp;nbsp;
{| cellspacing=&quot;3&quot; cellpadding=&quot;2&quot; border=&quot;2&quot; style=&quot;font face: Garamond,Verdana,Times,Arial; font-size:12pt; width:100%; padding:3px; border:1px solid blue; &quot;
!style=&quot;width:17%&quot; |KUID
!style=&quot;width:19%&quot; |Asset Name 
!style=&quot;width:40%&quot; |Description 
!style=&quot;width:07%&quot; |creator
!Source 
|-
|a
|b
|c
|d
|e
|-
|a
|b
|c
|d
|e
|-
|&lt;kuid:45324:50203:2&gt;&lt;br/&gt;&lt;kuid:45324:50204:2&gt;&lt;br/&gt;&lt;kuid:45324:50205:2&gt;&lt;br/&gt;&lt;kuid:45324:50206:2&gt;&lt;br/&gt;&lt;kuid:37581:1221&gt;
|S-2 Trucks, various wheel diameters, {x= 100T, 70T, 125T, 50Tons} &lt;br/&gt;&amp; generic sounds 
|p/o J-R S2 Truck pack freeware ([[traincar]]s bogey wheels, 36&quot;, 33&quot;, 38&quot;, and 28&quot; respectively)
|style=&quot;text-align:center;&quot;|norfolksouthern&lt;br/&gt;&quot;&lt;br/&gt;&quot;&lt;br/&gt;&quot;&lt;br/&gt;&amp; therock
|J-R
&lt;!-- if your kuid is a lower number put it towards the top, if larger, then towards the bottom.
This is boilerplate to cut and paste. The 'stub' lines can be written over once there are more than 5-7 kuids listed herein
Questions: [[User:Fabartus|Fra]]&lt;font color=&quot;green&quot;&gt;[[User talk:Fabartus|nkB]]&lt;/font&gt; 01:34, 10 July 2013 (UTC)
--&gt;
|-
|a
|b
|c
|d
|e
|-
|a
|b
|c
|d
|e
|-
|}</text>
      <sha1>87km8gw7bh2zenord5n1cuj6a1q8xgq</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Egmason</title>
    <ns>3</ns>
    <id>299094</id>
    <revision>
      <id>4669055</id>
      <parentid>2631978</parentid>
      <timestamp>2026-09-06T06:38:33Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669055</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4566" sha1="680xl6f3bj7hz19bfxhgsxxzl0s1r9i" xml:space="preserve">== Welcome! ==

&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Egmason!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;text-align:right; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks, --[[User:Xania|ЗAНИA]] [[Image:Flag_of_Estonia.svg|15px]][[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 23:41, 20 April 2014 (UTC)&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;</text>
      <sha1>680xl6f3bj7hz19bfxhgsxxzl0s1r9i</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Surement</title>
    <ns>3</ns>
    <id>300586</id>
    <revision>
      <id>4669049</id>
      <parentid>2667126</parentid>
      <timestamp>2026-09-06T06:34:50Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669049</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4565" sha1="1v98bj30ayowfvw9umafx7sh3fujctn" xml:space="preserve">== Welcome! ==

&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Surement!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;text-align:right; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks, --[[User:Xania|ЗAНИA]] [[Image:Flag_of_Estonia.svg|15px]][[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 23:03, 28 May 2014 (UTC)&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;</text>
      <sha1>1v98bj30ayowfvw9umafx7sh3fujctn</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:46.108.136.27</title>
    <ns>3</ns>
    <id>301233</id>
    <revision>
      <id>4669043</id>
      <parentid>2673310</parentid>
      <timestamp>2026-09-06T06:30:34Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4669043</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="744" sha1="8p8jlrt97spwzmi3ar4g6ftj6jcn54f" xml:space="preserve">&lt;div style=&quot;padding:5px; border:1px solid #A9A9A9; background-color:#FFEFD5;{{text default color}}; min-height:40px;&quot;&gt;[[File:Stop x nuvola with clock.svg|40px|left|link=]] '''[[Wikibooks:Blocking policy|You cannot edit]] for 1 month due to disruptive editing'''. You are welcome to contribute constructively when editing privileges are restored. You may appeal this action with a reasonable argument by adding the text &lt;!-- Copy the text as it appears on your page, not as it appears in this edit area. Do not include the &quot;tlx&quot; argument. --&gt;{{tlx|unblock|Your reason here}} below. &lt;/div&gt;&lt;!-- Template:blocked --&gt;

--[[User:Xania|ЗAНИA]] [[Image:Flag_of_the_Isle_of_Mann.svg|15px]][[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 20:05, 14 June 2014 (UTC)</text>
      <sha1>8p8jlrt97spwzmi3ar4g6ftj6jcn54f</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Richardlholmes</title>
    <ns>3</ns>
    <id>302048</id>
    <revision>
      <id>4669066</id>
      <parentid>2682488</parentid>
      <timestamp>2026-09-06T06:43:13Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669066</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4581" sha1="cgtcuw1j7vwiu7fkcnlfv6zqio4nasn" xml:space="preserve">== Welcome! ==

&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Richardlholmes!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;text-align:right; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks, --[[User:Xania|ЗAНИA]] [[Image:Flag_of_the_Isle_of_Mann.svg|15px]][[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 16:46, 18 July 2014 (UTC)&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;</text>
      <sha1>cgtcuw1j7vwiu7fkcnlfv6zqio4nasn</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Apogjack</title>
    <ns>3</ns>
    <id>308058</id>
    <revision>
      <id>4669060</id>
      <parentid>2754671</parentid>
      <timestamp>2026-09-06T06:40:32Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669060</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4487" sha1="a539cxp0e0neif3p1icgl8wf5peiaox" xml:space="preserve">== Welcome! ==

&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Apogjack!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;text-align:right; padding:0.2em 0.5em 0.2em 0.5em;&quot;&gt;Thanks, --Leaderboard 17:24, 11 January 2015 (UTC)&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;</text>
      <sha1>a539cxp0e0neif3p1icgl8wf5peiaox</sha1>
    </revision>
  </page>
  <page>
    <title>User:Legoeric/sandbox</title>
    <ns>2</ns>
    <id>308694</id>
    <revision>
      <id>4668932</id>
      <parentid>4667930</parentid>
      <timestamp>2026-09-05T12:43:43Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668932</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="97095" sha1="oaveuhpcxrm5s2uqzxou87r8r0ftmyp" xml:space="preserve">
{{shortcut|WP:MATH|WP:MATHS|Help:Math}}

{{redirect6|WP:MATH&quot; and &quot;WP:MATHS|the WikiProject on mathematics|Wikipedia:WikiProject Mathematics|Wikipedia's mathematics style manual|Wikipedia:Manual of Style/Mathematics|the mathematics reference desk|Wikipedia:Reference desk/Mathematics}}

[[MediaWiki]] uses a subset of [[AMS-LaTeX]] markup, a superset of [[LaTeX]] markup which is in turn a superset of [[TeX]] markup, for mathematical formulae. It generates [[Portable Network Graphics|PNG]] images by default. Alternatively, the [[MathJax]] renderer can be selected in the [[Help:Preferences|user preferences]]; this uses a combination of HTML and CSS to display the equation.

Although, in all cases mentioned, TeX is generated by [[Compiler|compilation]], and not by an interpreter program, there is one essential difference between, e.g., [[Donald Knuth|Knuth]]'s [[TeX]] or [[Leslie Lamport|Lamport]]'s [[LaTeX]] and the present implementation: whereas in the first two cases the compiler typically generates an ''all-in-one'' printable output, which has the quality of a whole book with all chapters, sections and subsections, and where no line is &quot;special&quot;, in the present case one has, typically, a mixture of TeX images (more precisely: PNG images) for the equations, embedded into usual text, and with short TeX elements usually replaced by HTML parts. As a consequence, in many cases TeX-elements, e.g. vector symbols, &quot;stick out&quot; below (or above) the text line. This &quot;sticking out&quot; is ''not''&amp;nbsp; the case in the above-mentioned original products, and the HTML-substitutes for small TeX additions to the text are often insufficient in quality for many readers. In spite of these shortcomings, the present product characterized by &quot;many embedded PNG-images&quot; should be preferred for small texts, where the equations do not dominate.

More precisely, MediaWiki filters the markup through [[Wikipedia:Texvc|Texvc]], which in turn passes the commands to TeX or [[MathJax]] for the actual [[Rendering (computer graphics)|render]]ing. Thus, only a limited part of the full TeX language is supported; see below for details.

To have math rendered in a particular MediaWiki installation, one has to set &lt;source lang=&quot;php&quot; enclose=&quot;none&quot;&gt;$wgUseTeX = true;&lt;/source&gt; in [[mw:Manual:LocalSettings.php|LocalSettings.php]].

Conrad's 

== Basics ==

Math markup goes inside {{tag|math}}.

The TeX code has to be put literally: MediaWiki templates, predefined templates, and parameters cannot be used within math tags: pairs of double braces are ignored and &quot;#&quot; gives an error message. However, math tags work in the then and else part of #if, etc. See {{tim|Demo of attempt to use parameters within TeX}} for more information.

=== LaTeX commands ===

LaTeX commands are case-sensitive, and take one of the following two formats:

* They start with a backslash \ and then have a name consisting of letters only. Command names are terminated by a space, a number or any other &quot;non-letter&quot;.
* They consist of a backslash \ and exactly one non-letter.

Some commands need an argument, which has to be given between curly braces { } after the command name. Some commands support optional parameters, which are added after the command name in square brackets []. The general syntax is:

 \commandname[option1,option2,...]{argument1}{argument2}...

=== Special characters ===

The following symbols are reserved characters that either have a special meaning under LaTeX or are unavailable in all the fonts. If you enter them directly in your text, they will normally not render, but rather do things you did not intend.

 # $ % ^ &amp; _ { } ~ \

These characters can be entered by adding a prefix backslash:

 \# \$ \% \textasciicircum{} \&amp; \_ \{ \} \~{} \textbackslash{}

The other symbols and many more can be rendered with special commands in mathematical formulae or as accents.

The backslash character \ can ''not'' be entered by adding another backslash in front of it (\\); this sequence is used for line breaking. For introducing a backslash in math mode, you can use \backslash instead.

The command \~ produces a tilde which is placed over the next letter. For example \~n gives ñ. To produce just the character ~, use \~{} which places a ~ over an empty box. Alternatively \sim produces a large centred ~ which may be more appropriate in some situations, but may not render properly in simple expressions which are converted to HTML.

Similarly, the command \^ produces a hat over the next character, for example \^{o} produces ô. If you need in text to display the ^ symbol you have to use \textasciicircum.

=== Spaces ===

&quot;Whitespace&quot; characters, such as blank or tab, are treated uniformly as &quot;space&quot; by LaTeX. Several consecutive whitespace characters are treated as one &quot;space&quot;. See [[#Spacing|below]] for commands that produces spaces of different size.

=== LaTeX environments ===

''Environments'' in LaTeX have a role that is quite similar to commands, but they usually have effect on a wider part of formula. Their syntax is:
&lt;source lang=&quot;latex&quot;&gt;
 \begin{environmentname}
   text to be influenced
 \end{environmentname}
&lt;/source&gt;
Environments supported by Wikipedia include ''matrix'', ''align'', etc. See [[#Fractions, matrices, multilines|below]].

=== Rendering ===

{| class=&quot;wikitable&quot; style=&quot;float:right;&quot;
| &lt;math&gt;e^{i \pi} + 1 = 0\,\!&lt;/math&gt;
| style=&quot;background-color:red;{{Text default color}};&quot; | &lt;math&gt;e^{i \pi} + 1 = 0\,\!&lt;/math&gt;
| style=&quot;background-color:red;{{Text default color}};&quot; | &lt;math&gt;e^{i \pi} + 1 = 0\,\!&lt;/math&gt;
|}

By default, the PNG images are rendered black on white, with a transparent background. On darker backgrounds, the characters may show white edges. To remove these, match the PNG background color with the background color of the page using &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\pagecolor&lt;/source&gt;. However, black text on a dark background is hard to read and should be avoided altogether where possible.

The colors, as well as font sizes and types, are independent of browser settings or CSS. Font sizes and types will often deviate from what HTML renders. Vertical alignment with the surrounding text can also be a problem (see [[bugzilla:32694|bug 32694]]); a work-around is described in the [[Help:Displaying_a_formula#Alignment with normal text flow|&quot;Alignment with normal text flow&quot;]] section below. The [[Help:User style#CSS selectors|css selector]] of the images is &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;img.tex&lt;/source&gt;.

The [[WP:ALT|alt text]] of the PNG images, which is displayed to visually impaired and other readers who cannot see the images, and is also used when the text is selected and copied, defaults to the wikitext that produced the image, excluding the &lt;code&gt;&lt;nowiki&gt;&lt;math&gt;&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;&lt;/math&gt;&lt;/nowiki&gt;&lt;/code&gt;. You can override this by explicitly specifying an &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;alt&lt;/source&gt; attribute for the &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;math&lt;/source&gt; element. For example, &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;&lt;math alt=&quot;Square root of pi&quot;&gt;\sqrt{\pi}&lt;/math&gt;&lt;/source&gt; generates an image &lt;math alt=&quot;square root of pi&quot;&gt;\sqrt{\pi}&lt;/math&gt; whose alt text is &quot;Square root of pi&quot;. This should not be confused with the ''title'' attribute that produces popup text when the hovering over the PNG image, for example &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;&lt;math title=&quot;pi&quot;&gt;\pi&lt;/math&gt;&lt;/source&gt; generates an image &lt;math title=&quot;pi&quot;&gt;\pi&lt;/math&gt; whose popup text is &quot;pi&quot;.

Apart from function and operator names, as is customary in mathematics, variables and letters are in italics; digits are not. For other text, (like variable labels) to avoid being rendered in italics like variables, use &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\text&lt;/source&gt;, &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mbox&lt;/source&gt;, or &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathrm&lt;/source&gt;. You can also define new function names using &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\operatorname{...}&lt;/source&gt;. For example, &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\text{abc}&lt;/source&gt; gives &lt;math&gt;\text{abc}&lt;/math&gt;.

Latex does not have full support for Unicode characters and not all characters render. Most Latin characters with accents render correctly. However some do not, in particular those that include multiple diacritics (e.g. with Latin letters used in Vietnamese) or that cannot be precomposed into a single character (such as the uppercase Latin letter W with ring), or that use other diacritics (like the ogonek or the double grave accent, used in Central European languages like Polish, or the horn attached above some vowels in Vietnamese), or other modified letter forms (used in IPA notations, or African languages, or in medieval texts), some digram ligatures (like Ĳ in Dutch), or Latin letters borrowed from Greek, or small capitals, as well as superscripts and subscript letters. For example &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\text{ð}&lt;/source&gt; or &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mbox{ð}&lt;/source&gt;, and &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\text{þ}&lt;/source&gt; or &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mbox{þ}&lt;/source&gt; (used in Icelandic) will give errors.

== TeX vs HTML ==
{{main|Wikipedia:Rendering math}}
Before using TeX markup for producing special characters, it should be noted that, as this comparison table shows, sometimes similar results can be achieved in HTML, with [[Template:Math]] or [[Template:Bigmath]] (also see: [[Help:Special characters]]).

{| class=&quot;wikitable&quot; border=1 &lt;!--set cell borders for MSIE browsers--&gt;
|-
! TeX syntax
! TeX rendering
! HTML syntax
! HTML rendering
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\alpha\,\!&lt;/source&gt;
| &lt;math&gt;\alpha\,\!&lt;/math&gt;
| &lt;source lang=&quot;html5&quot; enclose=&quot;none&quot;&gt;{{math|&lt;VAR&gt;&amp;alpha;&lt;/VAR&gt;}}&lt;/source&gt;
| {{math|''&amp;alpha;''}}
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;f(x) = x^2\,\!&lt;/source&gt;
| &lt;math&gt; f(x) = x^2\,\!&lt;/math&gt;
| &lt;source lang=&quot;html5&quot; enclose=&quot;none&quot;&gt;{{math|''f''(&lt;var&gt;x&lt;/var&gt;) {{=}} &lt;var&gt;x&lt;/var&gt;&lt;sup&gt;2&lt;/sup&gt;}}&lt;/source&gt;
| {{math|''f''(''x'') {{=}} ''x''&lt;sup&gt;2&lt;/sup&gt;}}
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\sqrt{2}&lt;/source&gt;
| &lt;math&gt;\sqrt{2}&lt;/math&gt;
| &lt;source lang=&quot;html5&quot; enclose=&quot;none&quot;&gt;{{math|{{radical|2}}}}&lt;/source&gt;
| {{math|{{radical|2}}}}
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\sqrt{1-e^2}&lt;/source&gt;
| &lt;math&gt;\sqrt{1-e^2}\!&lt;/math&gt;
| &lt;source lang=&quot;html5&quot; enclose=&quot;none&quot;&gt;{{math|{{radical|1 &amp;minus; ''e''&lt;sup&gt;2&lt;/sup&gt;}}}}&lt;/source&gt;
| {{math|{{radical|1 &amp;minus; ''e''&lt;sup&gt;2&lt;/sup&gt;}}}}
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\sqrt{1-z^3}&lt;/source&gt;
| &lt;math&gt;\sqrt{1-z^3}\!&lt;/math&gt;
| &lt;source lang=&quot;html5&quot; enclose=&quot;none&quot;&gt;{{bigmath|{{radical|1 &amp;minus; ''z''&lt;sup&gt;3&lt;/sup&gt;}}}}&lt;/source&gt;
| {{bigmath|{{radical|1 &amp;minus; ''z''&lt;sup&gt;3&lt;/sup&gt;}} }}
|}

The codes on the left produce the symbols on the right, but the latter can also be put directly in the wikitext, except for ‘=’.

{| class=&quot;wikitable&quot; border=1 &lt;!--set border for MSIE browsers--&gt;
|-
! Syntax
! Rendering
|- style=&quot;vertical-align:middle&quot;
|
&lt;pre&gt;&amp;amp;alpha; &amp;amp;beta; &amp;amp;gamma; &amp;amp;delta; &amp;amp;epsilon; &amp;amp;zeta;
&amp;amp;eta; &amp;amp;theta; &amp;amp;iota; &amp;amp;kappa; &amp;amp;lambda; &amp;amp;mu; &amp;amp;nu;
&amp;amp;xi; &amp;amp;omicron; &amp;amp;pi; &amp;amp;rho; &amp;amp;sigma; &amp;amp;sigmaf;
&amp;amp;tau; &amp;amp;upsilon; &amp;amp;phi; &amp;amp;chi; &amp;amp;psi; &amp;amp;omega;&lt;/pre&gt;
|
α β γ δ ε ζ &lt;br&gt;
η θ ι κ λ μ ν &lt;br&gt;
ξ ο π ρ σ ς &lt;br&gt;
τ υ φ χ ψ ω &lt;br&gt;
|- style=&quot;vertical-align:middle&quot;
|
&lt;pre&gt;&amp;amp;Gamma; &amp;amp;Delta; &amp;amp;Theta; &amp;amp;Lambda; &amp;amp;Xi; &amp;amp;Pi;
&amp;amp;Sigma; &amp;amp;Phi; &amp;amp;Psi; &amp;amp;Omega;&lt;/pre&gt;
|
Γ Δ Θ Λ Ξ Π &lt;br&gt;
Σ Φ Ψ Ω
|- style=&quot;vertical-align:middle&quot;
| &lt;pre&gt;&amp;amp;int; &amp;amp;sum; &amp;amp;prod; &amp;amp;radic; &amp;amp;minus; &amp;amp;plusmn; &amp;amp;infin;
&amp;amp;asymp; &amp;amp;prop; = &amp;amp;equiv; &amp;amp;ne; &amp;amp;le; &amp;amp;ge;
&amp;amp;times; &amp;amp;middot; &amp;amp;sdot; &amp;amp;divide; &amp;amp;part; &amp;amp;prime; &amp;amp;Prime;
&amp;amp;nabla; &amp;amp;permil; &amp;amp;deg; &amp;amp;there4; &amp;amp;empty;&lt;/pre&gt;
|
∫ ∑ ∏ √ − ± ∞&lt;br /&gt;
≈ ∝ = ≡ ≠ ≤ ≥&lt;br /&gt;
× · ⋅ ÷ ∂ ′ ″&lt;br /&gt;
∇ ‰ ° ∴ ∅
|- style=&quot;vertical-align:middle&quot;
| &lt;pre&gt;&amp;amp;isin; &amp;amp;notin; &amp;amp;cap; &amp;amp;cup; &amp;amp;sub; &amp;amp;sup; &amp;amp;sube; &amp;amp;supe;
&amp;amp;not; &amp;amp;and; &amp;amp;or; &amp;amp;exist; &amp;amp;forall;
&amp;amp;rArr; &amp;amp;hArr; &amp;amp;rarr; &amp;amp;harr; &amp;amp;uarr; &amp;amp;darr;
&amp;amp;alefsym; - &amp;amp;ndash; &amp;amp;mdash;&lt;/pre&gt;
|
∈ ∉ ∩ ∪ ⊂ ⊃ ⊆ ⊇&lt;br&gt;
¬ ∧ ∨ ∃ ∀&lt;br /&gt;
⇒ ⇔ → ↔ ↑ ↓&lt;br /&gt;
ℵ - – —
|}

The project has settled on using both HTML and TeX because each has advantages in some situations.

=== Pros of HTML ===

# Formulas in HTML behave more like regular text. In-line HTML formulae always align properly with the rest of the HTML text and, to some degree, can be copied-and-pasted (this is not a problem if TeX is rendered using [[w:MathJax|MathJax]], and the alignment should not be a problem for PNG rendering once [[bugzilla:32694|bug 32694]] is fixed).
# The formula’s background and font size match the rest of HTML contents (this can be fixed on TeX formulas by using the commands [[#Color|&lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\pagecolor&lt;/source&gt; and &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\definecolor&lt;/source&gt;]]) and the appearance respects CSS and browser settings while the typeface is conveniently altered to help you identify formulae.
# Pages using HTML code for formulae will load faster and they will create less clutter on your hard disk.
# Formulae typeset with HTML code will be accessible to client-side script links (a.k.a. scriptlets).
# The display of a formula entered using mathematical templates can be conveniently altered by modifying the templates involved; this modification will affect all relevant formulae without any manual intervention.
# The HTML code, if entered diligently, will contain all semantic information to transform the equation back to TeX or any other code as needed. It can even contain differences TeX does not normally catch, e.g. &lt;source lang=&quot;html5&quot; enclose=&quot;none&quot;&gt;{{math|''i''}}&lt;/source&gt; for the [[w:imaginary unit|imaginary unit]] and &lt;source lang=&quot;html5&quot; enclose=&quot;none&quot;&gt;{{math|&lt;var&gt;i&lt;/var&gt;}}&lt;/source&gt; for an arbitrary index variable.
# Unlike generated bitmaps, HTML is not sensitive to [[w:Dots per inch|dots per inch]] variances between viewing platforms.

=== Pros of TeX ===

# TeX is semantically more precise than HTML.
## In TeX, &quot;&lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;x&lt;/source&gt;&quot; means &quot;mathematical variable &lt;math&gt;x&lt;/math&gt;&quot;, whereas in HTML &quot;&lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;x&lt;/source&gt;&quot; is generic and somewhat ambiguous.
## On the other hand, if you encode the same formula as &quot;&lt;source lang=&quot;html5&quot; enclose=&quot;none&quot;&gt;{{math|&lt;var&gt;x&lt;/var&gt;}}&lt;/source&gt;&quot;, you get the same visual result {{math|''x''}} and no information is lost. This requires diligence and more typing that could make the formula harder to understand as you type it. However, since there are far more readers than editors, this effort is worth considering if no other rendering options are available (such as [[w:MathJax|MathJax]], which is available to logged-in users as a [[Special:Preferences#mw-prefsection-rendering|preferences]] opt-in).
# One consequence of point&amp;nbsp;1 is that TeX code can be transformed into HTML, but not vice-versa.{{ref|dilHTML}} This means that on the server side we can always transform a formula, based on its complexity and location within the text, user preferences, type of browser, etc. Therefore, where possible, all the benefits of HTML can be retained, together with the benefits of TeX. It is true that the current situation is not ideal, but that is not a good reason to drop information or contents. It is more a reason to [[#Bug reports|help improve the situation]].
# Another consequence of point&amp;nbsp;1 is that TeX can be converted to [[w:MathML|MathML]] (e.g. by MathJax) for browsers which support it, thus keeping its semantics and allowing the rendering to be better suited for the reader’s graphic device.
# TeX is the preferred text formatting language of most professional mathematicians, scientists, and engineers. It is easier to persuade them to contribute if they can write in TeX.
# TeX has been specifically designed for typesetting formulae, so input is easier and more natural if you are accustomed to it, and output is more aesthetically pleasing if you focus on a single formula rather than on the whole containing page.
# Once a formula is done correctly in TeX, it will render reliably, whereas the success of HTML formulae is somewhat dependent on browsers or versions of browsers. Another aspect of this dependency is fonts: the serif font used for rendering formulae is browser-dependent and it may be missing some important glyphs. While the browser is generally capable to substitute a matching glyph from a different font family, it need not be the case for combined glyphs (compare&amp;nbsp;‘&amp;nbsp;''{{IPA|a&amp;#773;}}''&amp;nbsp;’ and&amp;nbsp;‘&amp;nbsp;''a̅''&amp;nbsp;’).
# When writing in TeX, editors need not worry about whether this or that version of this or that browser supports this or that HTML entity. The burden of these decisions is put on the software. This does not hold for HTML formulae, which can easily end up being rendered wrongly or differently from the editor’s intentions on a different browser.{{ref|browsupp}}
# TeX formulae, by default, render larger and are usually more readable than HTML formulae and are not dependent on client-side browser resources, such as fonts, and so the results are more reliably WYSIWYG.
# While TeX does not assist you in finding HTML codes or Unicode values (which you can obtain by viewing the HTML source in your browser), copying and pasting from a TeX PNG image in Wikipedia into simple text will return the LaTeX source.

: &lt;small&gt;{{note|dilHTML}} Unless your wikitext follows the style of point&amp;nbsp;1.2&lt;/small&gt;
: &lt;small&gt;{{note|entHTML}} The entity support problem is not limited to mathematical formulae though; it can be easily solved by using the corresponding characters instead of entities, as the character repertoire links do, except for cases where the corresponding glyphs are visually indiscernible (e.g. &amp;amp;ndash; for &amp;lsquo;&amp;ndash;&amp;rsquo; and &amp;amp;minus; for &amp;lsquo;&amp;minus;&amp;rsquo;).&lt;/small&gt;

In some cases it may be the best choice to use neither TeX nor the HTML substitutes, but instead the simple ASCII symbols of a standard keyboard (see hereafter, for an example).

=== Using MathJax ===

The [[MathJax]] renderer, selectable through [[Special:Preferences#mw-prefsection-rendering|My Preferences - Appearance - Math]], uses a very different system to the standard texvc renderer. Rather than rendering a static image on the server side a combination of JavaScript, HTML and CSS is used to locally construct the formula. This allows high-quality typesetting, and other problems such as font sizes not matching your browser settings or wrong baselines are fixed as well. MathJax may also reduce the download time of images but entails a small delay as the JavaScript interpreter runs to render the formulas.  (After the small delay, the vertical dimension of the displayed page tends to update asynchronously—math content usually becomes taller—which can cause a disorienting jump in the document view position in some user agents; speedy mouse-wheelers might wish to check into this as part of their usability evaluation.)  

Alternatively to the preferences option, MathJax can also be selected using the [[User:Nageh/mathJax|mathJax]] user script. It is the basis for the global option, and hence more experimental but also more up to date. Bug reports are taken care of at the script's [[User talk:Nageh/mathJax|talk page]].

The quality of font rendering is dependent on your browser and operating system. Speed and appearance can be improved by installing the [[STIX Fonts project|STIX fonts]]; for installation details see the [http://www.mathjax.org/help/fonts/ MathJax font help] page. Further information is also available at [[User:Nageh/mathJax|this page]].

= Formatting using TeX =

== Functions, symbols, special characters ==
&lt;!-- Eight symbols per line seems to be optimal --&gt;

{| class=&quot;wikitable&quot;
|-
!colspan=&quot;2&quot;|

=== Accents/diacritics ===
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\dot{a}, \ddot{a}, \acute{a}, \grave{a} &lt;/source&gt;
| &lt;math&gt;\dot{a}, \ddot{a}, \acute{a}, \grave{a} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\check{a}, \breve{a}, \tilde{a}, \bar{a} &lt;/source&gt;
| &lt;math&gt;\check{a}, \breve{a}, \tilde{a}, \bar{a} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\hat{a}, \widehat{a}, \vec{a} &lt;/source&gt;
| &lt;math&gt;\hat{a}, \widehat{a}, \vec{a} \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Standard numerical functions ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\exp_a b = a^b, \exp b = e^b, 10^m &lt;/source&gt;
| &lt;math&gt;\exp_a b = a^b, \exp b = e^b, 10^m \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\ln c, \lg d = \log e, \log_{10} f &lt;/source&gt;
| &lt;math&gt;\ln c, \lg d = \log e, \log_{10} f \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\sin a, \cos b, \tan c, \cot d, \sec e, \csc f&lt;/source&gt;
| &lt;math&gt;\sin a, \cos b, \tan c, \cot d, \sec e, \csc f\!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\arcsin h, \arccos i, \arctan j &lt;/source&gt;
| &lt;math&gt;\arcsin h, \arccos i, \arctan j \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\sinh k, \cosh l, \tanh m, \coth n &lt;/source&gt;
| &lt;math&gt;\sinh k, \cosh l, \tanh m, \coth n \!&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\operatorname{sh}\,k, \operatorname{ch}\,l, \operatorname{th}\,m, \operatorname{coth}\,n &lt;/source&gt;
| &lt;math&gt;\operatorname{sh}\,k, \operatorname{ch}\,l, \operatorname{th}\,m, \operatorname{coth}\,n \!&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\operatorname{argsh}\,o, \operatorname{argch}\,p, \operatorname{argth}\,q &lt;/source&gt;
| &lt;math&gt;\operatorname{argsh}\,o, \operatorname{argch}\,p, \operatorname{argth}\,q \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\sgn r, \left\vert s \right\vert &lt;/source&gt;
| &lt;math&gt;\sgn r, \left\vert s \right\vert \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\min(x,y), \max(x,y) &lt;/source&gt;
| &lt;math&gt;\min(x,y), \max(x,y) \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Bounds ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\min x, \max y, \inf s, \sup t &lt;/source&gt;
| &lt;math&gt;\min x, \max y, \inf s, \sup t \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\lim u, \liminf v, \limsup w &lt;/source&gt;
| &lt;math&gt;\lim u, \liminf v, \limsup w \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\dim p, \deg q, \det m, \ker\phi &lt;/source&gt;
| &lt;math&gt;\dim p, \deg q, \det m, \ker\phi \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Projections ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Pr j, \hom l, \lVert z \rVert, \arg z &lt;/source&gt;
| &lt;math&gt;\Pr j, \hom l, \lVert z \rVert, \arg z \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Differentials and derivatives ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;dt, \operatorname{d}\!t, \partial t, \nabla\psi&lt;/source&gt;
| &lt;math&gt;dt, \operatorname{d}\!t, \partial t, \nabla\psi\!&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;dy/dx, \operatorname{d}\!y/\operatorname{d}\!x, {dy \over dx}, {\operatorname{d}\!y\over\operatorname{d}\!x}, {\partial^2\over\partial x_1\partial x_2}y &lt;/source&gt;
| &lt;math&gt;dy/dx, \operatorname{d}\!y/\operatorname{d}\!x, {dy \over dx}, {\operatorname{d}\!y\over\operatorname{d}\!x}, {\partial^2\over\partial x_1\partial x_2}y \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\prime, \backprime, f^\prime, f', f'', f^{(3)}, \dot y, \ddot y &lt;/source&gt;
| &lt;math&gt;\prime, \backprime, f^\prime, f', f'', f^{(3)} \!, \dot y, \ddot y&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Letter-like symbols or constants ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\infty, \aleph, \complement, \backepsilon, \eth, \Finv, \hbar &lt;/source&gt;
| &lt;math&gt;\infty, \aleph, \complement, \backepsilon, \eth, \Finv, \hbar \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Im, \imath, \jmath, \Bbbk, \ell, \mho, \wp, \Re, \circledS &lt;/source&gt;
| &lt;math&gt;\Im, \imath, \jmath, \Bbbk, \ell, \mho, \wp, \Re, \circledS \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Modular arithmetic ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;s_k \equiv 0 \pmod{m} &lt;/source&gt;
| &lt;math&gt;s_k \equiv 0 \pmod{m} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;a\,\bmod\,b &lt;/source&gt;
| &lt;math&gt;a\,\bmod\,b \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\gcd(m, n), \operatorname{lcm}(m, n)&lt;/source&gt;
| &lt;math&gt;\gcd(m, n), \operatorname{lcm}(m, n)&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mid, \nmid, \shortmid, \nshortmid &lt;/source&gt;
| &lt;math&gt;\mid, \nmid, \shortmid, \nshortmid \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Radicals ===
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\surd, \sqrt{2}, \sqrt[n]{}, \sqrt[3]{x^3+y^3 \over 2} &lt;/source&gt;
| &lt;math&gt;\surd, \sqrt{2}, \sqrt[n]{}, \sqrt[3]{x^3+y^3 \over 2} \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Operators ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;+, -, \pm, \mp, \dotplus &lt;/source&gt;
| &lt;math&gt;+, -, \pm, \mp, \dotplus \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\times, \div, \divideontimes, /, \backslash &lt;/source&gt;
| &lt;math&gt;\times, \div, \divideontimes, /, \backslash \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\cdot, * \ast, \star, \circ, \bullet &lt;/source&gt;
| &lt;math&gt;\cdot, * \ast, \star, \circ, \bullet \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\boxplus, \boxminus, \boxtimes, \boxdot &lt;/source&gt;
| &lt;math&gt;\boxplus, \boxminus, \boxtimes, \boxdot \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oplus, \ominus, \otimes, \oslash, \odot&lt;/source&gt;
| &lt;math&gt;\oplus, \ominus, \otimes, \oslash, \odot\!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\circleddash, \circledcirc, \circledast &lt;/source&gt;
| &lt;math&gt;\circleddash, \circledcirc, \circledast \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\bigoplus, \bigotimes, \bigodot &lt;/source&gt;
| &lt;math&gt;\bigoplus, \bigotimes, \bigodot \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Sets ===
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\{ \}, \O \empty \emptyset, \varnothing &lt;/source&gt;
| &lt;math&gt;\{ \}, \O \empty \emptyset, \varnothing \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\in, \notin \not\in, \ni, \not\ni &lt;/source&gt;
| &lt;math&gt;\in, \notin \not\in, \ni, \not\ni \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\cap, \Cap, \sqcap, \bigcap &lt;/source&gt;
| &lt;math&gt;\cap, \Cap, \sqcap, \bigcap \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\cup, \Cup, \sqcup, \bigcup, \bigsqcup, \uplus, \biguplus &lt;/source&gt;
| &lt;math&gt;\cup, \Cup, \sqcup, \bigcup, \bigsqcup, \uplus, \biguplus \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\setminus, \smallsetminus, \times &lt;/source&gt;
| &lt;math&gt;\setminus, \smallsetminus, \times \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\subset, \Subset, \sqsubset &lt;/source&gt;
| &lt;math&gt;\subset, \Subset, \sqsubset \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\supset, \Supset, \sqsupset &lt;/source&gt;
| &lt;math&gt;\supset, \Supset, \sqsupset \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\subseteq, \nsubseteq, \subsetneq, \varsubsetneq, \sqsubseteq &lt;/source&gt;
| &lt;math&gt;\subseteq, \nsubseteq, \subsetneq, \varsubsetneq, \sqsubseteq \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\supseteq, \nsupseteq, \supsetneq, \varsupsetneq, \sqsupseteq &lt;/source&gt;
| &lt;math&gt;\supseteq, \nsupseteq, \supsetneq, \varsupsetneq, \sqsupseteq \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\subseteqq, \nsubseteqq, \subsetneqq, \varsubsetneqq &lt;/source&gt;
| &lt;math&gt;\subseteqq, \nsubseteqq, \subsetneqq, \varsubsetneqq \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\supseteqq, \nsupseteqq, \supsetneqq, \varsupsetneqq &lt;/source&gt;
| &lt;math&gt;\supseteqq, \nsupseteqq, \supsetneqq, \varsupsetneqq \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Relations ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;=, \ne, \neq, \equiv, \not\equiv &lt;/source&gt;
| &lt;math&gt;=, \ne, \neq, \equiv, \not\equiv \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\doteq, \doteqdot,&lt;/source&gt; &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\overset{\underset{\mathrm{def}}{}}{=},&lt;/source&gt; &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;:=&lt;/source&gt;
| &lt;math&gt;\doteq, \doteqdot, \overset{\underset{\mathrm{def}}{}}{=}, := \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\sim, \nsim, \backsim, \thicksim, \simeq, \backsimeq, \eqsim, \cong, \ncong &lt;/source&gt;
| &lt;math&gt;\sim, \nsim, \backsim, \thicksim, \simeq, \backsimeq, \eqsim, \cong, \ncong \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\approx, \thickapprox, \approxeq, \asymp, \propto, \varpropto &lt;/source&gt;
| &lt;math&gt;\approx, \thickapprox, \approxeq, \asymp, \propto, \varpropto \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;&lt;, \nless, \ll, \not\ll, \lll, \not\lll, \lessdot &lt;/source&gt;
| &lt;math&gt;&lt;, \nless, \ll, \not\ll, \lll, \not\lll, \lessdot \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;&gt;, \ngtr, \gg, \not\gg, \ggg, \not\ggg, \gtrdot &lt;/source&gt;
| &lt;math&gt;&gt;, \ngtr, \gg, \not\gg, \ggg, \not\ggg, \gtrdot \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\le, \leq, \lneq, \leqq, \nleq, \nleqq, \lneqq, \lvertneqq &lt;/source&gt;
| &lt;math&gt;\le, \leq, \lneq, \leqq, \nleq, \nleqq, \lneqq, \lvertneqq \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\ge, \geq, \gneq, \geqq, \ngeq, \ngeqq, \gneqq, \gvertneqq &lt;/source&gt;
| &lt;math&gt;\ge, \geq, \gneq, \geqq, \ngeq, \ngeqq, \gneqq, \gvertneqq \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\lessgtr, \lesseqgtr, \lesseqqgtr, \gtrless, \gtreqless, \gtreqqless &lt;/source&gt;
| &lt;math&gt;\lessgtr, \lesseqgtr, \lesseqqgtr, \gtrless, \gtreqless, \gtreqqless \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\leqslant, \nleqslant, \eqslantless &lt;/source&gt;
| &lt;math&gt;\leqslant, \nleqslant, \eqslantless \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\geqslant, \ngeqslant, \eqslantgtr &lt;/source&gt;
| &lt;math&gt;\geqslant, \ngeqslant, \eqslantgtr \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\lesssim, \lnsim, \lessapprox, \lnapprox &lt;/source&gt;
| &lt;math&gt;\lesssim, \lnsim, \lessapprox, \lnapprox \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\gtrsim, \gnsim, \gtrapprox, \gnapprox &lt;/source&gt;
| &lt;math&gt;\gtrsim, \gnsim, \gtrapprox, \gnapprox \,&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\prec, \nprec, \preceq, \npreceq, \precneqq &lt;/source&gt;
| &lt;math&gt;\prec, \nprec, \preceq, \npreceq, \precneqq \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\succ, \nsucc, \succeq, \nsucceq, \succneqq &lt;/source&gt;
| &lt;math&gt;\succ, \nsucc, \succeq, \nsucceq, \succneqq \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\preccurlyeq, \curlyeqprec &lt;/source&gt;
| &lt;math&gt;\preccurlyeq, \curlyeqprec \,&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\succcurlyeq, \curlyeqsucc &lt;/source&gt;
| &lt;math&gt;\succcurlyeq, \curlyeqsucc \,&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\precsim, \precnsim, \precapprox, \precnapprox &lt;/source&gt;
| &lt;math&gt;\precsim, \precnsim, \precapprox, \precnapprox \,&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\succsim, \succnsim, \succapprox, \succnapprox &lt;/source&gt;
| &lt;math&gt;\succsim, \succnsim, \succapprox, \succnapprox \,&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Geometric ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\parallel, \nparallel, \shortparallel, \nshortparallel &lt;/source&gt;
| &lt;math&gt;\parallel, \nparallel, \shortparallel, \nshortparallel \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\perp, \angle, \sphericalangle, \measuredangle, 45^\circ &lt;/source&gt;
| &lt;math&gt;\perp, \angle, \sphericalangle, \measuredangle, 45^\circ \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Box, \blacksquare, \diamond, \Diamond \lozenge, \blacklozenge, \bigstar &lt;/source&gt;
| &lt;math&gt;\Box, \blacksquare, \diamond, \Diamond \lozenge, \blacklozenge, \bigstar \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\bigcirc, \triangle \bigtriangleup, \bigtriangledown &lt;/source&gt;
| &lt;math&gt;\bigcirc, \triangle \bigtriangleup, \bigtriangledown \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\vartriangle, \triangledown &lt;/source&gt;
| &lt;math&gt;\vartriangle, \triangledown\!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\blacktriangle, \blacktriangledown, \blacktriangleleft, \blacktriangleright &lt;/source&gt;
| &lt;math&gt;\blacktriangle, \blacktriangledown, \blacktriangleleft, \blacktriangleright \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Logic ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\forall, \exists, \nexists &lt;/source&gt;
| &lt;math&gt;\forall, \exists, \nexists \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\therefore, \because, \And &lt;/source&gt;
| &lt;math&gt;\therefore, \because, \And \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\or \lor \vee, \curlyvee, \bigvee &lt;/source&gt;
| &lt;math&gt;\or \lor \vee, \curlyvee, \bigvee \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\and \land \wedge, \curlywedge, \bigwedge &lt;/source&gt;
| &lt;math&gt;\and \land \wedge, \curlywedge, \bigwedge \!&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\bar{q}, \bar{abc}, \overline{q}, \overline{abc}, &lt;/source&gt;&lt;br /&gt;
&lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\lnot \neg, \not\operatorname{R}, \bot, \top&lt;/source&gt;
| &lt;math&gt;\bar{q}, \bar{abc}, \overline{q}, \overline{abc}, \!&lt;/math&gt;&lt;br /&gt;
&lt;math&gt;\lnot \neg, \not\operatorname{R}, \bot, \top \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\vdash \dashv, \vDash, \Vdash, \models &lt;/source&gt;
| &lt;math&gt;\vdash \dashv, \vDash, \Vdash, \models \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Vvdash \nvdash \nVdash \nvDash \nVDash &lt;/source&gt;
| &lt;math&gt;\Vvdash \nvdash \nVdash \nvDash \nVDash \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\ulcorner \urcorner \llcorner \lrcorner &lt;/source&gt;
| &lt;math&gt;\ulcorner \urcorner \llcorner \lrcorner \,&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Arrows ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Rrightarrow, \Lleftarrow &lt;/source&gt;
| &lt;math&gt;\Rrightarrow, \Lleftarrow \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Rightarrow, \nRightarrow, \Longrightarrow \implies &lt;/source&gt;
| &lt;math&gt;\Rightarrow, \nRightarrow, \Longrightarrow \implies\!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Leftarrow, \nLeftarrow, \Longleftarrow &lt;/source&gt;
| &lt;math&gt;\Leftarrow, \nLeftarrow, \Longleftarrow \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Leftrightarrow, \nLeftrightarrow, \Longleftrightarrow \iff &lt;/source&gt;
| &lt;math&gt;\Leftrightarrow, \nLeftrightarrow, \Longleftrightarrow \iff \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Uparrow, \Downarrow, \Updownarrow &lt;/source&gt;
| &lt;math&gt;\Uparrow, \Downarrow, \Updownarrow \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\rightarrow \to, \nrightarrow, \longrightarrow &lt;/source&gt;
| &lt;math&gt;\rightarrow \to, \nrightarrow, \longrightarrow\!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\leftarrow \gets, \nleftarrow, \longleftarrow &lt;/source&gt;
| &lt;math&gt;\leftarrow \gets, \nleftarrow, \longleftarrow\!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\leftrightarrow, \nleftrightarrow, \longleftrightarrow &lt;/source&gt;
| &lt;math&gt;\leftrightarrow, \nleftrightarrow, \longleftrightarrow \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\uparrow, \downarrow, \updownarrow &lt;/source&gt;
| &lt;math&gt;\uparrow, \downarrow, \updownarrow \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\nearrow, \swarrow, \nwarrow, \searrow &lt;/source&gt;
| &lt;math&gt;\nearrow, \swarrow, \nwarrow, \searrow \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mapsto, \longmapsto &lt;/source&gt;
| &lt;math&gt;\mapsto, \longmapsto \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\rightharpoonup \rightharpoondown \leftharpoonup \leftharpoondown \upharpoonleft \upharpoonright \downharpoonleft \downharpoonright \rightleftharpoons \leftrightharpoons&lt;/source&gt;
| &lt;math&gt;\rightharpoonup \rightharpoondown \leftharpoonup \leftharpoondown \upharpoonleft \upharpoonright \downharpoonleft \downharpoonright \rightleftharpoons \leftrightharpoons \,\!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\curvearrowleft \circlearrowleft \Lsh \upuparrows \rightrightarrows \rightleftarrows \rightarrowtail \looparrowright&lt;/source&gt;
| &lt;math&gt;\curvearrowleft \circlearrowleft \Lsh \upuparrows \rightrightarrows \rightleftarrows \rightarrowtail \looparrowright \,\!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\curvearrowright \circlearrowright \Rsh \downdownarrows \leftleftarrows \leftrightarrows \leftarrowtail \looparrowleft&lt;/source&gt;
| &lt;math&gt;\curvearrowright \circlearrowright \Rsh \downdownarrows \leftleftarrows \leftrightarrows \leftarrowtail \looparrowleft \,\!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\hookrightarrow \hookleftarrow \multimap \leftrightsquigarrow \rightsquigarrow \twoheadrightarrow \twoheadleftarrow &lt;/source&gt;
| &lt;math&gt;\hookrightarrow \hookleftarrow \multimap \leftrightsquigarrow \rightsquigarrow \twoheadrightarrow \twoheadleftarrow \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Special ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\amalg \P \S \% \dagger \ddagger \ldots \cdots &lt;/source&gt;
| &lt;math&gt;\amalg \P \S \% \dagger \ddagger \ldots \cdots \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\smile \frown \wr \triangleleft \triangleright&lt;/source&gt;
| &lt;math&gt;\smile \frown \wr \triangleleft \triangleright\!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\diamondsuit, \heartsuit, \clubsuit, \spadesuit, \Game, \flat, \natural, \sharp &lt;/source&gt;
| &lt;math&gt;\diamondsuit, \heartsuit, \clubsuit, \spadesuit, \Game, \flat, \natural, \sharp \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;|

=== Unsorted (new stuff) ===
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\diagup \diagdown \centerdot \ltimes \rtimes \leftthreetimes \rightthreetimes &lt;/source&gt;
| &lt;math&gt;\diagup \diagdown \centerdot \ltimes \rtimes \leftthreetimes \rightthreetimes \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\eqcirc \circeq \triangleq \bumpeq \Bumpeq \doteqdot \risingdotseq \fallingdotseq &lt;/source&gt;
| &lt;math&gt;\eqcirc \circeq \triangleq \bumpeq \Bumpeq \doteqdot \risingdotseq \fallingdotseq \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\intercal \barwedge \veebar \doublebarwedge \between \pitchfork &lt;/source&gt;
| &lt;math&gt;\intercal \barwedge \veebar \doublebarwedge \between \pitchfork \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\vartriangleleft \ntriangleleft \vartriangleright \ntriangleright &lt;/source&gt;
| &lt;math&gt;\vartriangleleft \ntriangleleft \vartriangleright \ntriangleright \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\trianglelefteq \ntrianglelefteq \trianglerighteq \ntrianglerighteq &lt;/source&gt;
| &lt;math&gt;\trianglelefteq \ntrianglelefteq \trianglerighteq \ntrianglerighteq \!&lt;/math&gt;
|}

For a little more semantics on these symbols, see the brief [http://www.math.upenn.edu/tex-stuff/cookbook.pdf TeX Cookbook].

== Larger expressions ==

=== Subscripts, superscripts, integrals ===

{| class=&quot;wikitable&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;4&quot; style=&quot;border-collapse:collapse&quot;
|-
! Feature !! Syntax !! How it looks rendered
|-
| Superscript
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;a^2&lt;/source&gt; || &lt;math&gt;a^2&lt;/math&gt;
|-
| Subscript
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;a_2&lt;/source&gt; || &lt;math&gt;a_2&lt;/math&gt;
|-
| rowspan=&quot;2&quot;| Grouping
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;10^{30} a^{2+2}&lt;/source&gt; || &lt;math&gt;10^{30} a^{2+2}&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;a_{i,j} b_{f'}&lt;/source&gt; || &lt;math&gt;a_{i,j} b_{f'}&lt;/math&gt;
|-
| rowspan=&quot;2&quot;| Combining sub &amp; super without and with horizontal separation
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;x_2^3&lt;/source&gt; || &lt;math&gt;x_2^3&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;{x_2}^3&lt;/source&gt; || &lt;math&gt;{x_2}^3 \,\!&lt;/math&gt;
|-
| Super super
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;10^{10^{8}}&lt;/source&gt; || &lt;math&gt;10^{10^{8}}&lt;/math&gt;
|-
| rowspan=&quot;2&quot;| Preceding and/or additional sub &amp; super
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\sideset{_1^2}{_3^4}\prod_a^b&lt;/source&gt; || &lt;math&gt;\sideset{_1^2}{_3^4}\prod_a^b&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;{}_1^2\!\Omega_3^4&lt;/source&gt; || &lt;math&gt;{}_1^2\!\Omega_3^4&lt;/math&gt;
|-
| rowspan=&quot;4&quot;| Stacking
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\overset{\alpha}{\omega}&lt;/source&gt; || &lt;math&gt;\overset{\alpha}{\omega}&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\underset{\alpha}{\omega}&lt;/source&gt; || &lt;math&gt;\underset{\alpha}{\omega}&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\overset{\alpha}{\underset{\gamma}{\omega}}&lt;/source&gt; || &lt;math&gt;\overset{\alpha}{\underset{\gamma}{\omega}}&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\stackrel{\alpha}{\omega}&lt;/source&gt; || &lt;math&gt;\stackrel{\alpha}{\omega}&lt;/math&gt;
|-
| rowspan=&quot;2&quot;| Derivatives
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;x', y'', f', f''&lt;/source&gt; || &lt;math&gt;x', y'', f', f''&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;x^\prime, y^{\prime\prime}&lt;/source&gt; || &lt;math&gt;x^\prime, y^{\prime\prime}&lt;/math&gt;
|-
| Derivative dots
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\dot{x}, \ddot{x}&lt;/source&gt; || &lt;math&gt;\dot{x}, \ddot{x}&lt;/math&gt;
|-
| rowspan=&quot;3&quot;| Underlines, overlines, vectors
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\hat a \ \bar b \ \vec c&lt;/source&gt; || &lt;math&gt; \hat a \ \bar b \ \vec c&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\overrightarrow{a b} \ \overleftarrow{c d} \ \widehat{d e f}&lt;/source&gt; || &lt;math&gt; \overrightarrow{a b} \ \overleftarrow{c d} \ \widehat{d e f}&lt;/math&gt;
|-
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\overline{g h i} \ \underline{j k l}&lt;/source&gt; || &lt;math&gt; \overline{g h i} \ \underline{j k l}&lt;/math&gt;
|-
| Arc (workaround)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\overset{\frown} {AB}&lt;/source&gt; || &lt;math&gt;\overset{\frown} {AB}&lt;/math&gt;
|-
| Arrows
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt; A \xleftarrow{n+\mu-1} B \xrightarrow[T]{n\pm i-1} C&lt;/source&gt; || &lt;math&gt; A \xleftarrow{n+\mu-1} B \xrightarrow[T]{n\pm i-1} C&lt;/math&gt;
|-
| Overbraces
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\overbrace{ 1+2+\cdots+100 }^{5050}&lt;/source&gt; || &lt;math&gt;\overbrace{ 1+2+\cdots+100 }^{5050}&lt;/math&gt;
|-
| Underbraces
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\underbrace{ a+b+\cdots+z }_{26}&lt;/source&gt; || &lt;math&gt;\underbrace{ a+b+\cdots+z }_{26}&lt;/math&gt;
|-
| Sum
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\sum_{k=1}^N k^2&lt;/source&gt; || &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;
|-
| Sum (force&amp;nbsp;&lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle&lt;/source&gt;)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle \sum_{k=1}^N k^2 &lt;/source&gt; || &lt;math&gt;\textstyle \sum_{k=1}^N k^2&lt;/math&gt;
|-
| Sum in a fraction (default &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle&lt;/source&gt;)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\frac{\sum_{k=1}^N k^2}{a}&lt;/source&gt; || &lt;math&gt;\frac{\sum_{k=1}^N k^2}{a}&lt;/math&gt;
|-
| Sum in a fraction (force &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\displaystyle&lt;/source&gt;)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\frac{\displaystyle \sum_{k=1}^N k^2}{a}&lt;/source&gt; || &lt;math&gt;\frac{\displaystyle \sum_{k=1}^N k^2}{a}&lt;/math&gt;
|-
| Sum in a fraction (alternative limits style)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\frac{\sum\limits^{^N}_{k=1} k^2}{a}&lt;/source&gt; || &lt;math&gt;\frac{\sum\limits^{^N}_{k=1} k^2}{a}&lt;/math&gt;
|-
| Product
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\prod_{i=1}^N x_i&lt;/source&gt; || &lt;math&gt;\prod_{i=1}^N x_i&lt;/math&gt;
|-
| Product (force&amp;nbsp;&lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle&lt;/source&gt;)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle \prod_{i=1}^N x_i&lt;/source&gt; || &lt;math&gt;\textstyle \prod_{i=1}^N x_i&lt;/math&gt;
|-
| Coproduct
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\coprod_{i=1}^N x_i&lt;/source&gt; || &lt;math&gt;\coprod_{i=1}^N x_i&lt;/math&gt;
|-
| Coproduct (force&amp;nbsp;&lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle&lt;/source&gt;)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle \coprod_{i=1}^N x_i&lt;/source&gt; || &lt;math&gt;\textstyle \coprod_{i=1}^N x_i&lt;/math&gt;
|-
| Limit
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\lim_{n \to \infty}x_n&lt;/source&gt; || &lt;math&gt;\lim_{n \to \infty}x_n&lt;/math&gt;
|-
| Limit (force&amp;nbsp;&lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle&lt;/source&gt;)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle \lim_{n \to \infty}x_n&lt;/source&gt; || &lt;math&gt;\textstyle \lim_{n \to \infty}x_n&lt;/math&gt;
|-
| Integral
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\int\limits_{1}^{3}\frac{e^3/x}{x^2}\, dx&lt;/source&gt; || &lt;math&gt;\int\limits_{1}^{3}\frac{e^3/x}{x^2}\, dx&lt;/math&gt;
|-
| Integral (alternative limits style)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\int_{1}^{3}\frac{e^3/x}{x^2}\, dx&lt;/source&gt; || &lt;math&gt;\int_{1}^{3}\frac{e^3/x}{x^2}\, dx&lt;/math&gt;
|-
| Integral (force&amp;nbsp;&lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle&lt;/source&gt;)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle \int\limits_{-N}^{N} e^x\, dx&lt;/source&gt; || &lt;math&gt;\textstyle \int\limits_{-N}^{N} e^x\, dx&lt;/math&gt;
|-
| Integral (force&amp;nbsp;&lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle&lt;/source&gt;, alternative limits style)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\textstyle \int_{-N}^{N} e^x\, dx&lt;/source&gt; || &lt;math&gt;\textstyle \int_{-N}^{N} e^x\, dx&lt;/math&gt;
|-
| Double integral
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\iint\limits_D \, dx\,dy&lt;/source&gt; || &lt;math&gt;\iint\limits_D \, dx\,dy&lt;/math&gt;
|-
| Triple integral
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\iiint\limits_E \, dx\,dy\,dz&lt;/source&gt; || &lt;math&gt;\iiint\limits_E \, dx\,dy\,dz&lt;/math&gt;
|-
| Quadruple integral
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\iiiint\limits_F \, dx\,dy\,dz\,dt&lt;/source&gt; || &lt;math&gt;\iiiint\limits_F \, dx\,dy\,dz\,dt&lt;/math&gt;
|-
| Line or path integral
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\int_{(x,y)\in C} x^3\, dx + 4y^2\, dy&lt;/source&gt; || &lt;math&gt;\int_{(x,y)\in C} x^3\, dx + 4y^2\, dy&lt;/math&gt;
|-
| Closed line or path integral
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\oint_{(x,y)\in C} x^3\, dx + 4y^2\, dy&lt;/source&gt; || &lt;math&gt;\oint_{(x,y)\in C} x^3\, dx + 4y^2\, dy&lt;/math&gt;
|-
| Intersections
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\bigcap_{i=_1}^n E_i&lt;/source&gt; || &lt;math&gt;\bigcap_{i=_1}^n E_i&lt;/math&gt;
|-
| Unions
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\bigcup_{i=_1}^n E_i&lt;/source&gt; || &lt;math&gt;\bigcup_{i=_1}^n E_i&lt;/math&gt;
|}

=== Fractions, matrices, multilines ===

{| class=&quot;wikitable&quot;
! Feature
! Syntax
! How it looks rendered
|-
| Fractions
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\frac{2}{4}=0.5&lt;/source&gt; or &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;{2 \over 4}=0.5&lt;/source&gt;
| &lt;math&gt;\frac{2}{4}=0.5&lt;/math&gt;
|-
| Small fractions
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\tfrac{2}{4} = 0.5&lt;/source&gt;
| &lt;math&gt;\tfrac{2}{4} = 0.5&lt;/math&gt;
|-
| Large (normal) fractions
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\dfrac{2}{4} = 0.5 \qquad \dfrac{2}{c + \dfrac{2}{d + \dfrac{2}{4}}} = a &lt;/source&gt;
| &lt;math&gt;\dfrac{2}{4} = 0.5 \qquad \dfrac{2}{c + \dfrac{2}{d + \dfrac{2}{4}}} = a&lt;/math&gt;
|-
| Large (nested) fractions
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\cfrac{2}{c + \cfrac{2}{d + \cfrac{2}{4}}} = a&lt;/source&gt;
| &lt;math&gt;\cfrac{2}{c + \cfrac{2}{d + \cfrac{2}{4}}} = a&lt;/math&gt;
|-
| Cancellations in fractions&lt;br&gt;Note does not work with MathJax
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\cfrac{x}{1 + \cfrac{\cancel{y}}{\cancel{y}}} = \cfrac{x}{2}&lt;/source&gt;
| &lt;math&gt;\cfrac{x}{1 + \cfrac{\cancel{y}}{\cancel{y}}} = \cfrac{x}{2}&lt;/math&gt;
|-
| Binomial coefficients
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\binom{n}{k}&lt;/source&gt;
| &lt;math&gt;\binom{n}{k}&lt;/math&gt;
|-
| Small binomial coefficients
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\tbinom{n}{k}&lt;/source&gt;
| &lt;math&gt;\tbinom{n}{k}&lt;/math&gt;
|-
| Large (normal) binomial coefficients
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\dbinom{n}{k}&lt;/source&gt;
| &lt;math&gt;\dbinom{n}{k}&lt;/math&gt;
|-
| rowspan=&quot;7&quot; | Matrices
| &lt;source lang=&quot;latex&quot;&gt;\begin{matrix}
x &amp; y \\
z &amp; v
\end{matrix}&lt;/source&gt;
| &lt;math&gt;\begin{matrix}
x &amp; y \\
z &amp; v
\end{matrix}&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot;&gt;\begin{vmatrix}
x &amp; y \\
z &amp; v
\end{vmatrix}&lt;/source&gt;
| &lt;math&gt;\begin{vmatrix}
x &amp; y \\
z &amp; v
\end{vmatrix}&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot;&gt;\begin{Vmatrix}
x &amp; y \\
z &amp; v
\end{Vmatrix}&lt;/source&gt;
| &lt;math&gt;\begin{Vmatrix}
x &amp; y \\
z &amp; v
\end{Vmatrix}&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot;&gt;\begin{bmatrix}
0 &amp; \cdots &amp; 0 \\
\vdots &amp; \ddots &amp; \vdots \\
0 &amp; \cdots &amp; 0
\end{bmatrix}&lt;/source&gt;
| &lt;math&gt;\begin{bmatrix}
0 &amp; \cdots &amp; 0 \\
\vdots &amp; \ddots &amp; \vdots \\
0 &amp; \cdots &amp; 0
\end{bmatrix} &lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot;&gt;\begin{Bmatrix}
x &amp; y \\
z &amp; v
\end{Bmatrix}&lt;/source&gt;
| &lt;math&gt;\begin{Bmatrix}
x &amp; y \\
z &amp; v
\end{Bmatrix}&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot;&gt;\begin{pmatrix}
x &amp; y \\
z &amp; v
\end{pmatrix}&lt;/source&gt;
| &lt;math&gt;\begin{pmatrix}
x &amp; y \\
z &amp; v
\end{pmatrix}&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot;&gt;
\bigl( \begin{smallmatrix}
a&amp;b\\ c&amp;d
\end{smallmatrix} \bigr)
&lt;/source&gt;
| &lt;math&gt;
\bigl( \begin{smallmatrix}
a&amp;b\\ c&amp;d
\end{smallmatrix} \bigr)
&lt;/math&gt;
|-
| Case distinctions
| &lt;source lang=&quot;latex&quot;&gt;
f(n) =
\begin{cases}
n/2, &amp; \text{if }n\text{ is even} \\
3n+1, &amp; \text{if }n\text{ is odd}
\end{cases}&lt;/source&gt;
| &lt;math&gt;f(n) =
\begin{cases}
n/2, &amp; \text{if }n\text{ is even} \\
3n+1, &amp; \text{if }n\text{ is odd}
\end{cases}&lt;/math&gt;
|-
| rowspan=&quot;2&quot; | Multiline equations
| &lt;source lang=&quot;latex&quot;&gt;
\begin{align}
f(x) &amp; = (a+b)^2 \\
&amp; = a^2+2ab+b^2 \\
\end{align}
&lt;/source&gt;
| &lt;math&gt;
\begin{align}
f(x) &amp; = (a+b)^2 \\
&amp; = a^2+2ab+b^2 \\
\end{align}
&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot;&gt;
\begin{alignat}{2}
f(x) &amp; = (a-b)^2 \\
&amp; = a^2-2ab+b^2 \\
\end{alignat}
&lt;/source&gt;
| &lt;math&gt;
\begin{alignat}{2}
f(x) &amp; = (a-b)^2 \\
&amp; = a^2-2ab+b^2 \\
\end{alignat}
&lt;/math&gt;
|-
| Multiline equations &lt;small&gt;(must define number of columns used ({lcl})) (should not be used unless needed)&lt;/small&gt;
| &lt;source lang=&quot;latex&quot;&gt;
\begin{array}{lcl}
z &amp; = &amp; a \\
f(x,y,z) &amp; = &amp; x + y + z
\end{array}&lt;/source&gt;
| &lt;math&gt;\begin{array}{lcl}
z &amp; = &amp; a \\
f(x,y,z) &amp; = &amp; x + y + z
\end{array}&lt;/math&gt;
|-
| Multiline equations (more)
| &lt;source lang=&quot;latex&quot;&gt;
\begin{array}{lcr}
z &amp; = &amp; a \\
f(x,y,z) &amp; = &amp; x + y + z
\end{array}&lt;/source&gt;
| &lt;math&gt;\begin{array}{lcr}
z &amp; = &amp; a \\
f(x,y,z) &amp; = &amp; x + y + z
\end{array}&lt;/math&gt;
|-
| Breaking up a long expression so that it wraps when necessary, at the expense of destroying correct spacing
| &lt;source lang=&quot;latex&quot;&gt;
f(x) =
\sum_{n=0}^\infty a_n x^n =
a_0+a_1x+a_2x^2+\cdots
&lt;/source&gt;
| &lt;math&gt;f(x) =
\sum_{n=0}^\infty a_n x^n =
a_0 +a_1x+a_2x^2+\cdots&lt;/math&gt;
|-
| Simultaneous equations
| &lt;source lang=&quot;latex&quot;&gt;\begin{cases}
3x + 5y + z \\
7x - 2y + 4z \\
-6x + 3y + 2z
\end{cases}&lt;/source&gt;
| &lt;math&gt;\begin{cases}
3x + 5y + z \\
7x - 2y + 4z \\
-6x + 3y + 2z
\end{cases}&lt;/math&gt;
|-
| Arrays
| &lt;source lang=&quot;latex&quot;&gt;
\begin{array}{|c|c|c|} a &amp; b &amp; S \\
\hline
0&amp;0&amp;1\\
0&amp;1&amp;1\\
1&amp;0&amp;1\\
1&amp;1&amp;0\\
\end{array}
&lt;/source&gt;
| &lt;math&gt;
\begin{array}{|c|c|c|} a &amp; b &amp; S \\
\hline
0&amp;0&amp;1\\
0&amp;1&amp;1\\
1&amp;0&amp;1\\
1&amp;1&amp;0\\
\end{array}
&lt;/math&gt;
|}

=== Parenthesizing big expressions, brackets, bars ===

{| class=&quot;wikitable&quot;
! Feature !! Syntax !! How it looks rendered
|-
| Bad
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;( \frac{1}{2} )&lt;/source&gt;
| &lt;math&gt;( \frac{1}{2} )&lt;/math&gt;
|-
| Good
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left ( \frac{1}{2} \right )&lt;/source&gt;
| &lt;math&gt;\left ( \frac{1}{2} \right )&lt;/math&gt;
|}

You can use various delimiters with \left and \right:

{| class=&quot;wikitable&quot;
! Feature
! Syntax
! How it looks rendered
|-
| Parentheses
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left ( \frac{a}{b} \right )&lt;/source&gt;
| &lt;math&gt;\left ( \frac{a}{b} \right )&lt;/math&gt;
|-
| Brackets
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left [ \frac{a}{b} \right ] \quad&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left \lbrack \frac{a}{b} \right \rbrack&lt;/source&gt;
| &lt;math&gt;\left [ \frac{a}{b} \right ] \quad \left \lbrack \frac{a}{b} \right \rbrack&lt;/math&gt;
|-
| Braces
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left \{ \frac{a}{b} \right \} \quad&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left \lbrace \frac{a}{b} \right \rbrace&lt;/source&gt;
| &lt;math&gt;\left \{ \frac{a}{b} \right \} \quad \left \lbrace \frac{a}{b} \right \rbrace&lt;/math&gt;
|-
| Angle brackets
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left \langle \frac{a}{b} \right \rangle&lt;/source&gt;
| &lt;math&gt;\left \langle \frac{a}{b} \right \rangle&lt;/math&gt;
|-
| Bars and double bars
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left | \frac{a}{b} \right \vert \quad&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left \Vert \frac{c}{d} \right \|&lt;/source&gt;
| &lt;math&gt;\left | \frac{a}{b} \right \vert \quad \left \Vert \frac{c}{d} \right \|&lt;/math&gt;
|-
| Floor and ceiling functions:
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left \lfloor \frac{a}{b} \right \rfloor \quad&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left \lceil \frac{c}{d} \right \rceil&lt;/source&gt;
| &lt;math&gt;\left \lfloor \frac{a}{b} \right \rfloor \quad \left \lceil \frac{c}{d} \right \rceil&lt;/math&gt;
|-
| Slashes and backslashes
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left / \frac{a}{b} \right \backslash&lt;/source&gt;
| &lt;math&gt;\left / \frac{a}{b} \right \backslash&lt;/math&gt;
|-
| Up, down, and up-down arrows
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left \uparrow \frac{a}{b} \right \downarrow \quad&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left \Uparrow \frac{a}{b} \right \Downarrow \quad&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left \updownarrow \frac{a}{b} \right \Updownarrow&lt;/source&gt;
| &lt;math&gt;\left \uparrow \frac{a}{b} \right \downarrow \quad \left \Uparrow \frac{a}{b} \right \Downarrow \quad \left \updownarrow \frac{a}{b} \right \Updownarrow&lt;/math&gt;
|-
| Delimiters can be mixed,&lt;br&gt;as long as \left and \right match
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\left [ 0,1 \right )&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\left \langle \psi \right |&lt;/source&gt;
| &lt;math&gt;\left [ 0,1 \right )&lt;/math&gt;&lt;br/&gt; &lt;math&gt;\left \langle \psi \right |&lt;/math&gt;
|-
| Use \left. and \right. if you&lt;br/&gt; do not want a delimiter to appear
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\left . \frac{A}{B} \right \} \to X&lt;/source&gt;
| &lt;math&gt;\left . \frac{A}{B} \right \} \to X&lt;/math&gt;
|-
| rowspan=&quot;7&quot; | Size of the delimiters (add &quot;l&quot; or &quot;r&quot; to indicate the side for proper spacing)
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;( \bigl( \Bigl( \biggl( \Biggl( \dots \Biggr] \biggr] \Bigr] \bigr] ]&lt;/source&gt;
| &lt;math&gt;( \bigl( \Bigl( \biggl( \Biggl( \dots \Biggr] \biggr] \Bigr] \bigr] ]&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\{ \bigl\{ \Bigl\{ \biggl\{ \Biggl\{ \dots&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Biggr\rangle \biggr\rangle \Bigr\rangle \bigr\rangle \rangle&lt;/source&gt;
| &lt;math&gt;\{ \bigl\{ \Bigl\{ \biggl\{ \Biggl\{ \dots \Biggr\rangle \biggr\rangle \Bigr\rangle \bigr\rangle \rangle&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\| \big\| \Big\| \bigg\| \Bigg\| \dots \Bigg| \bigg| \Big| \big| |&lt;/source&gt;
| &lt;math&gt;\| \big\| \Big\| \bigg\| \Bigg\| \dots \Bigg| \bigg| \Big| \big| |&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\lfloor \bigl\lfloor \Bigl\lfloor \biggl\lfloor \Biggl\lfloor \dots&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Biggr\rceil \biggr\rceil \Bigr\rceil \bigr\rceil \ceil&lt;/source&gt;
| &lt;math&gt;\lfloor \bigl\lfloor \Bigl\lfloor \biggl\lfloor \Biggl\lfloor \dots \Biggr\rceil \biggr\rceil \Bigr\rceil \bigr\rceil \rceil&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\uparrow \big\uparrow \Big\uparrow \bigg\uparrow \Bigg\uparrow \dots&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Bigg\Downarrow \bigg\Downarrow \Big\Downarrow \big\Downarrow \Downarrow&lt;/source&gt;
| &lt;math&gt;\uparrow \big\uparrow \Big\uparrow \bigg\uparrow \Bigg\uparrow \dots \Bigg\Downarrow \bigg\Downarrow \Big\Downarrow \big\Downarrow \Downarrow&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\updownarrow \big\updownarrow \Big\updownarrow \bigg\updownarrow \Bigg\updownarrow \dots&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Bigg\Updownarrow \bigg\Updownarrow \Big\Updownarrow \big\Updownarrow \Updownarrow&lt;/source&gt;
| &lt;math&gt;\updownarrow \big\updownarrow \Big\updownarrow \bigg\updownarrow \Bigg\updownarrow \dots \Bigg\Updownarrow \bigg\Updownarrow \Big\Updownarrow \big\Updownarrow \Updownarrow&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;/ \big/ \Big/ \bigg/ \Bigg/ \dots&lt;/source&gt;&lt;br/&gt; &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Bigg\backslash \bigg\backslash \Big\backslash \big\backslash \backslash&lt;/source&gt;
| &lt;math&gt;/ \big/ \Big/ \bigg/ \Bigg/ \dots \Bigg\backslash \bigg\backslash \Big\backslash \big\backslash \backslash&lt;/math&gt;
|}

=== Equation numbering ===

The templates {{tl|NumBlk}} and {{tl|EquationRef}} can be used to number equations. The template {{tl|EquationNote}} can be used to refer to a numbered equation from surrounding text. For example, the following syntax:

: &lt;code&gt;&lt;nowiki&gt;{{NumBlk|:|&lt;math&gt;x^2 + y^2 + z^2 = 1 \,&lt;/math&gt;|{{EquationRef|1}}}}&lt;/nowiki&gt;&lt;/code&gt;

produces the following result (note the equation number in the right margin):

{{NumBlk|:|&lt;math&gt;x^2 + y^2 + z^2 = 1 \,&lt;/math&gt; or {{math|''x''&lt;sup&gt;2&lt;/sup&gt; +  ''y''&lt;sup&gt;2&lt;/sup&gt; + ''z''&lt;sup&gt;2&lt;/sup&gt; {{=}} 1}}|{{EquationRef|1}}}}

Later on, the text can refer to this equation by its number using syntax like this:

: &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;As seen in equation ({{EquationNote|1}}), blah blah blah...&lt;/source&gt;

The result looks like this:

: As seen in equation ({{EquationNote|1}}), blah blah blah...

Note that the equation number produced by {{tl|EquationNote}} is a link that the user can click to go immediately to the cited equation.

== Alphabets and typefaces ==
{{See also|Wikipedia:LaTeX symbols#Fonts}}
[[Texvc]] cannot render arbitrary [[Unicode]] characters. Those it can handle can be entered by the expressions below. For others, such as [[Cyrillic]], they can be entered as Unicode or HTML entities in running text, but cannot be used in displayed formulas.

{| class=&quot;wikitable&quot;
|-
!colspan=&quot;2&quot;| Greek alphabet
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Alpha \Beta \Gamma \Delta \Epsilon \Zeta \Eta \Theta &lt;/source&gt;
| &lt;math&gt;\Alpha \Beta \Gamma \Delta \Epsilon \Zeta \Eta \Theta \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Iota \Kappa \Lambda \Mu \Nu \Xi \Pi \Rho &lt;/source&gt;
| &lt;math&gt;\Iota \Kappa \Lambda \Mu \Nu \Xi \Pi \Rho \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\Sigma \Tau \Upsilon \Phi \Chi \Psi \Omega &lt;/source&gt;
| &lt;math&gt;\Sigma \Tau \Upsilon \Phi \Chi \Psi \Omega \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\alpha \beta \gamma \delta \epsilon \zeta \eta \theta &lt;/source&gt;
| &lt;math&gt;\alpha \beta \gamma \delta \epsilon \zeta \eta \theta \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\iota \kappa \lambda \mu \nu \xi \pi \rho &lt;/source&gt;
| &lt;math&gt;\iota \kappa \lambda \mu \nu \xi \pi \rho \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\sigma \tau \upsilon \phi \chi \psi \omega &lt;/source&gt;
| &lt;math&gt;\sigma \tau \upsilon \phi \chi \psi \omega \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\varepsilon \digamma \varkappa \varpi &lt;/source&gt;
| &lt;math&gt;\varepsilon \digamma \varkappa \varpi \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\varrho \varsigma \vartheta \varphi &lt;/source&gt;
| &lt;math&gt;\varrho \varsigma \vartheta \varphi \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Hebrew symbols
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\aleph \beth \gimel \daleth &lt;/source&gt;
| &lt;math&gt;\aleph \beth \gimel \daleth \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Blackboard bold/scripts
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathbb{ABCDEFGHI} &lt;/source&gt;
| &lt;math&gt;\mathbb{ABCDEFGHI} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathbb{JKLMNOPQR} &lt;/source&gt;
| &lt;math&gt;\mathbb{JKLMNOPQR} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathbb{STUVWXYZ} &lt;/source&gt;
| &lt;math&gt;\mathbb{STUVWXYZ} \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Boldface
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathbf{ABCDEFGHI} &lt;/source&gt;
| &lt;math&gt;\mathbf{ABCDEFGHI} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathbf{JKLMNOPQR} &lt;/source&gt;
| &lt;math&gt;\mathbf{JKLMNOPQR} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathbf{STUVWXYZ} &lt;/source&gt;
| &lt;math&gt;\mathbf{STUVWXYZ} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathbf{abcdefghijklm} &lt;/source&gt;
| &lt;math&gt;\mathbf{abcdefghijklm} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathbf{nopqrstuvwxyz} &lt;/source&gt;
| &lt;math&gt;\mathbf{nopqrstuvwxyz} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathbf{0123456789} &lt;/source&gt;
| &lt;math&gt;\mathbf{0123456789} \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Boldface (Greek)
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\boldsymbol{\Alpha\Beta\Gamma\Delta\Epsilon\Zeta\Eta\Theta} &lt;/source&gt;
| &lt;math&gt;\boldsymbol{\Alpha\Beta\Gamma\Delta\Epsilon\Zeta\Eta\Theta} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\boldsymbol{\Iota\Kappa\Lambda\Mu\Nu\Xi\Pi\Rho} &lt;/source&gt;
| &lt;math&gt;\boldsymbol{\Iota\Kappa\Lambda\Mu\Nu\Xi\Pi\Rho} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\boldsymbol{\Sigma\Tau\Upsilon\Phi\Chi\Psi\Omega} &lt;/source&gt;
| &lt;math&gt;\boldsymbol{\Sigma\Tau\Upsilon\Phi\Chi\Psi\Omega} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\boldsymbol{\alpha\beta\gamma\delta\epsilon\zeta\eta\theta} &lt;/source&gt;
| &lt;math&gt;\boldsymbol{\alpha\beta\gamma\delta\epsilon\zeta\eta\theta} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\boldsymbol{\iota\kappa\lambda\mu\nu\xi\pi\rho} &lt;/source&gt;
| &lt;math&gt;\boldsymbol{\iota\kappa\lambda\mu\nu\xi\pi\rho} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\boldsymbol{\sigma\tau\upsilon\phi\chi\psi\omega} &lt;/source&gt;
| &lt;math&gt;\boldsymbol{\sigma\tau\upsilon\phi\chi\psi\omega} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\boldsymbol{\varepsilon\digamma\varkappa\varpi} &lt;/source&gt;
| &lt;math&gt;\boldsymbol{\varepsilon\digamma\varkappa\varpi} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\boldsymbol{\varrho\varsigma\vartheta\varphi} &lt;/source&gt;
| &lt;math&gt;\boldsymbol{\varrho\varsigma\vartheta\varphi} \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Italics (default for Latin alphabet)
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathit{0123456789} &lt;/source&gt;
| &lt;math&gt;\mathit{0123456789} \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Greek italics (default for lowercase Greek)
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathit{\Alpha\Beta\Gamma\Delta\Epsilon\Zeta\Eta\Theta} &lt;/source&gt;
| &lt;math&gt;\mathit{\Alpha\Beta\Gamma\Delta\Epsilon\Zeta\Eta\Theta} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathit{\Iota\Kappa\Lambda\Mu\Nu\Xi\Pi\Rho} &lt;/source&gt;
| &lt;math&gt;\mathit{\Iota\Kappa\Lambda\Mu\Nu\Xi\Pi\Rho} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathit{\Sigma\Tau\Upsilon\Phi\Chi\Psi\Omega} &lt;/source&gt;
| &lt;math&gt;\mathit{\Sigma\Tau\Upsilon\Phi\Chi\Psi\Omega} \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Roman typeface
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathrm{ABCDEFGHI} &lt;/source&gt;
| &lt;math&gt;\mathrm{ABCDEFGHI} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathrm{JKLMNOPQR} &lt;/source&gt;
| &lt;math&gt;\mathrm{JKLMNOPQR} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathrm{STUVWXYZ} &lt;/source&gt;
| &lt;math&gt;\mathrm{STUVWXYZ} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathrm{abcdefghijklm} &lt;/source&gt;
| &lt;math&gt;\mathrm{abcdefghijklm} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathrm{nopqrstuvwxyz} &lt;/source&gt;
| &lt;math&gt;\mathrm{nopqrstuvwxyz} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathrm{0123456789} &lt;/source&gt;
| &lt;math&gt;\mathrm{0123456789} \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Sans serif
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathsf{ABCDEFGHI} &lt;/source&gt;
| &lt;math&gt;\mathsf{ABCDEFGHI} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathsf{JKLMNOPQR} &lt;/source&gt;
| &lt;math&gt;\mathsf{JKLMNOPQR} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathsf{STUVWXYZ} &lt;/source&gt;
| &lt;math&gt;\mathsf{STUVWXYZ} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathsf{abcdefghijklm} &lt;/source&gt;
| &lt;math&gt;\mathsf{abcdefghijklm} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathsf{nopqrstuvwxyz} &lt;/source&gt;
| &lt;math&gt;\mathsf{nopqrstuvwxyz} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathsf{0123456789} &lt;/source&gt;
| &lt;math&gt;\mathsf{0123456789} \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Sans serif Greek (capital only)
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathsf{\Alpha \Beta \Gamma \Delta \Epsilon \Zeta \Eta \Theta} &lt;/source&gt;
| &lt;math&gt;\mathsf{\Alpha \Beta \Gamma \Delta \Epsilon \Zeta \Eta \Theta} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathsf{\Iota \Kappa \Lambda \Mu \Nu \Xi \Pi \Rho} &lt;/source&gt;
| &lt;math&gt;\mathsf{\Iota \Kappa \Lambda \Mu \Nu \Xi \Pi \Rho} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathsf{\Sigma \Tau \Upsilon \Phi \Chi \Psi \Omega}&lt;/source&gt;
| &lt;math&gt;\mathsf{\Sigma \Tau \Upsilon \Phi \Chi \Psi \Omega}\!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Calligraphy/script
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathcal{ABCDEFGHI} &lt;/source&gt;
| &lt;math&gt;\mathcal{ABCDEFGHI} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathcal{JKLMNOPQR} &lt;/source&gt;
| &lt;math&gt;\mathcal{JKLMNOPQR} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathcal{STUVWXYZ} &lt;/source&gt;
| &lt;math&gt;\mathcal{STUVWXYZ} \!&lt;/math&gt;
|-
!colspan=&quot;2&quot;| Fraktur typeface
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathfrak{ABCDEFGHI} &lt;/source&gt;
| &lt;math&gt;\mathfrak{ABCDEFGHI} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathfrak{JKLMNOPQR} &lt;/source&gt;
| &lt;math&gt;\mathfrak{JKLMNOPQR} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathfrak{STUVWXYZ} &lt;/source&gt;
| &lt;math&gt;\mathfrak{STUVWXYZ} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathfrak{abcdefghijklm} &lt;/source&gt;
| &lt;math&gt;\mathfrak{abcdefghijklm} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathfrak{nopqrstuvwxyz} &lt;/source&gt;
| &lt;math&gt;\mathfrak{nopqrstuvwxyz} \!&lt;/math&gt;
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathfrak{0123456789} &lt;/source&gt;
| &lt;math&gt;\mathfrak{0123456789} \!&lt;/math&gt;
|-
|-
!colspan=&quot;2&quot;| Small scriptstyle text
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;{\scriptstyle\text{abcdefghijklm}}&lt;/source&gt;
| &lt;math&gt;{\scriptstyle\text{abcdefghijklm}}&lt;/math&gt;
|}

=== Mixed text faces ===

{| class=&quot;wikitable&quot;
|-
! Feature
! Syntax
! How it looks rendered
|-
| Italicised characters (spaces are ignored)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;x y z&lt;/source&gt;
| &lt;math&gt;x y z&lt;/math&gt;
|-
| Non-italicised characters
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\text{x y z}&lt;/source&gt;
| &lt;math&gt;\text{x y z}&lt;/math&gt;
|-
| Mixed italics (bad)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\text{if} n \text{is even}&lt;/source&gt;
| &lt;math&gt;\text{if} n \text{is even}&lt;/math&gt;
|-
| Mixed italics (good)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\text{if }n\text{ is even}&lt;/source&gt;
| &lt;math&gt;\text{if }n\text{ is even}&lt;/math&gt;
|-
| Mixed italics (alternative: ~ or &quot;\ &quot; forces a space)
| &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\text{if}~n\ \text{is even}&lt;/source&gt;
| &lt;math&gt;\text{if}~n\ \text{is even}&lt;/math&gt;
|}

== Color ==
Equations can use color with the &lt;code&gt;\color&lt;/code&gt; command. The default [[Wikipedia:Texvc|Texvc]] renderer and the [[MathJax]] renderers have different syntaxes to support both use &lt;code&gt;{\color{Blue}{text}}&lt;/code&gt;. For example
* &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;{\color{Blue}{x^2}}+{\color{Orange}{2x}}-{\color{LimeGreen}{1}}&lt;/source&gt;
*: &lt;math&gt;{\color{Blue}{x^2}}+{\color{Orange}{2x}}-{\color{LimeGreen}{1}}&lt;/math&gt;
* &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;x_{1,2}=\frac{{\color{Blue}{-b}}\pm\sqrt{\color{Red}{b^2-4ac}}}{\color{Green}{2a}}&lt;/source&gt;
*: &lt;math&gt;x_{1,2}=\frac{{\color{Blue}{-b}}\pm\sqrt{\color{Red}{b^2-4ac}}}{\color{Green}{2a}}&lt;/math&gt;
There are several alternate notations styles
* &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;{\color{Blue}x^2}+{\color{Orange}2x}-{\color{LimeGreen}1}&lt;/source&gt; works with both texvc and MathJax
*: &lt;math&gt;{\color{Blue}x^2}+{\color{Orange}2x}-{\color{LimeGreen}1}&lt;/math&gt;
* &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\color{Blue}x^2\color{Black}+\color{Orange}2x\color{Black}-\color{LimeGreen}1&lt;/source&gt; works with both texvc and MathJax
*: &lt;math&gt;\color{Blue}x^2\color{Black}+\color{Orange}2x\color{Black}-\color{LimeGreen}1&lt;/math&gt;
* &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\color{Blue}{x^2}+\color{Orange}{2x}-\color{LimeGreen}{1}&lt;/source&gt; only works with MathJax
*: &lt;math&gt;\color{Blue}{x^2}+\color{Orange}{2x}-\color{LimeGreen}{1}&lt;/math&gt;

Some color names are predeclared according to the following table, you can use them directly for the rendering of formulas (or for declaring the intended color of the page background).

{| class=&quot;wikitable&quot;
|+ Colors supported
|-
| &lt;math&gt;\color{Apricot}{\text{Apricot}}&lt;/math&gt; ||style=&quot;background-color: gray;{{Text default color}};&quot;| &lt;math&gt;\color{Aquamarine}{\text{Aquamarine}}&lt;/math&gt; || &lt;math&gt;\color{Bittersweet}{\text{Bittersweet}}&lt;/math&gt; || &lt;math&gt;\color{Black}{\text{Black}}&lt;/math&gt;
|-
| &lt;math&gt;\color{Blue}{\text{Blue}}&lt;/math&gt; || &lt;math&gt;\color{BlueGreen}{\text{BlueGreen}}&lt;/math&gt; || &lt;math&gt;\color{BlueViolet}{\text{BlueViolet}}&lt;/math&gt; || &lt;math&gt;\color{BrickRed}{\text{BrickRed}}&lt;/math&gt;
|-
| &lt;math&gt;\color{Brown}{\text{Brown}}&lt;/math&gt; || &lt;math&gt;\color{BurntOrange}{\text{BurntOrange}}&lt;/math&gt; || &lt;math&gt;\color{CadetBlue}{\text{CadetBlue}}&lt;/math&gt; || &lt;math&gt;\color{CarnationPink}{\text{CarnationPink}}&lt;/math&gt;
|-
| &lt;math&gt;\color{Cerulean}{\text{Cerulean}}&lt;/math&gt; || &lt;math&gt;\color{CornflowerBlue}{\text{CornflowerBlue}}&lt;/math&gt; ||style=&quot;background-color: gray;{{Text default color}};&quot;| &lt;math&gt;\color{Cyan}{\text{Cyan}}&lt;/math&gt; || &lt;math&gt;\color{Dandelion}{\text{Dandelion}}&lt;/math&gt;
|-
| &lt;math&gt;\color{DarkOrchid}{\text{DarkOrchid}}&lt;/math&gt; || &lt;math&gt;\color{Emerald}{\text{Emerald}}&lt;/math&gt; || &lt;math&gt;\color{ForestGreen}{\text{ForestGreen}}&lt;/math&gt; || &lt;math&gt;\color{Fuchsia}{\text{Fuchsia}}&lt;/math&gt;
|-
| &lt;math&gt;\color{Goldenrod}{\text{Goldenrod}}&lt;/math&gt; || &lt;math&gt;\color{Gray}{\text{Gray}}&lt;/math&gt; || &lt;math&gt;\color{Green}{\text{Green}}&lt;/math&gt; ||style=&quot;background-color: gray;{{Text default color}};&quot;| &lt;math&gt;\color{GreenYellow}{\text{GreenYellow}}&lt;/math&gt;
|-
| &lt;math&gt;\color{JungleGreen}{\text{JungleGreen}}&lt;/math&gt; ||style=&quot;background-color: gray;{{Text default color}};&quot;| &lt;math&gt;\color{Lavender}{\text{Lavender}}&lt;/math&gt; || &lt;math&gt;\color{LimeGreen}{\text{LimeGreen}}&lt;/math&gt; || &lt;math&gt;\color{Magenta}{\text{Magenta}}&lt;/math&gt;
|-
| &lt;math&gt;\color{Mahogany}{\text{Mahogany}}&lt;/math&gt; || &lt;math&gt;\color{Maroon}{\text{Maroon}}&lt;/math&gt; || &lt;math&gt;\color{Melon}{\text{Melon}}&lt;/math&gt; || &lt;math&gt;\color{MidnightBlue}{\text{MidnightBlue}}&lt;/math&gt;
|-
| &lt;math&gt;\color{Mulberry}{\text{Mulberry}}&lt;/math&gt; || &lt;math&gt;\color{NavyBlue}{\text{NavyBlue}}&lt;/math&gt; || &lt;math&gt;\color{OliveGreen}{\text{OliveGreen}}&lt;/math&gt; || &lt;math&gt;\color{Orange}{\text{Orange}}&lt;/math&gt;
|-
| &lt;math&gt;\color{OrangeRed}{\text{OrangeRed}}&lt;/math&gt; || &lt;math&gt;\color{Orchid}{\text{Orchid}}&lt;/math&gt; || &lt;math&gt;\color{Peach}{\text{Peach}}&lt;/math&gt; || &lt;math&gt;\color{Periwinkle}{\text{Periwinkle}}&lt;/math&gt;
|-
| &lt;math&gt;\color{PineGreen}{\text{PineGreen}}&lt;/math&gt; || &lt;math&gt;\color{Plum}{\text{Plum}}&lt;/math&gt; || &lt;math&gt;\color{ProcessBlue}{\text{ProcessBlue}}&lt;/math&gt; || &lt;math&gt;\color{Purple}{\text{Purple}}&lt;/math&gt;
|-
| &lt;math&gt;\color{RawSienna}{\text{RawSienna}}&lt;/math&gt; || &lt;math&gt;\color{Red}{\text{Red}}&lt;/math&gt; || &lt;math&gt;\color{RedOrange}{\text{RedOrange}}&lt;/math&gt; || &lt;math&gt;\color{RedViolet}{\text{RedViolet}}&lt;/math&gt;
|-
| &lt;math&gt;\color{Rhodamine}{\text{Rhodamine}}&lt;/math&gt; || &lt;math&gt;\color{RoyalBlue}{\text{RoyalBlue}}&lt;/math&gt; || &lt;math&gt;\color{RoyalPurple}{\text{RoyalPurple}}&lt;/math&gt; || &lt;math&gt;\color{RubineRed}{\text{RubineRed}}&lt;/math&gt;
|-
| &lt;math&gt;\color{Salmon}{\text{Salmon}}&lt;/math&gt; || &lt;math&gt;\color{SeaGreen}{\text{SeaGreen}}&lt;/math&gt; || &lt;math&gt;\color{Sepia}{\text{Sepia}}&lt;/math&gt; || &lt;math&gt;\color{SkyBlue}{\text{SkyBlue}}&lt;/math&gt;
|-
| &lt;math&gt;\color{SpringGreen}{\text{SpringGreen}}&lt;/math&gt; || &lt;math&gt;\color{Tan}{\text{Tan}}&lt;/math&gt; || &lt;math&gt;\color{TealBlue}{\text{TealBlue}}&lt;/math&gt; ||style=&quot;background-color: gray;{{Text default color}};&quot;| &lt;math&gt;\color{Thistle}{\text{Thistle}}&lt;/math&gt;
|-
| &lt;math&gt;\color{Turquoise}{\text{Turquoise}}&lt;/math&gt; || &lt;math&gt;\color{Violet}{\text{Violet}}&lt;/math&gt; || &lt;math&gt;\color{VioletRed}{\text{VioletRed}}&lt;/math&gt; ||style=&quot;background-color: gray;{{Text default color}};&quot;| &lt;math&gt;{\color{White}{\text{White}}}&lt;/math&gt;
|-
| &lt;math&gt;\color{WildStrawberry}{\text{WildStrawberry}}&lt;/math&gt; ||style=&quot;background-color: gray;{{Text default color}};&quot;| &lt;math&gt;\color{Yellow}{\text{Yellow}}&lt;/math&gt; || &lt;math&gt;\color{YellowGreen}{\text{YellowGreen}}&lt;/math&gt; || &lt;math&gt;\color{YellowOrange}{\text{YellowOrange}}&lt;/math&gt;
|}

Note that color should not be used as the ''only'' way to identify something, because it will become meaningless on black-and-white media or for color-blind people. See [[Wikipedia:Manual of Style (accessibility)#Color]].

Latex does not have a command for setting the background color. The most effective of setting a background color is by setting a CSS styling rules for a table cell
&lt;pre style=&quot;display: inline-block;&quot;&gt;
{| class=&quot;wikitable&quot;
|-
| style=&quot;background: gray;{{Text default color}};&quot; | &lt;math&gt;x^2&lt;/math&gt; || style=&quot;background: Goldenrod;{{Text default color}};&quot; | &lt;math&gt;y^3&lt;/math&gt;
|}
&lt;/pre&gt;

Rendered as
{| class=&quot;wikitable&quot;
|-
| style=&quot;background: grey;{{Text default color}};&quot; | &lt;math&gt;x^2&lt;/math&gt; || style=&quot;background: Goldenrod;{{Text default color}};&quot; | &lt;math&gt;y^3&lt;/math&gt;
|}


Custom colours can be defined using
&lt;syntaxhighlight lang=&quot;latex&quot;&gt;\definecolor{myorange}{RGB}{255,165,100}\color{myorange}e^{i \pi}\color{Black} + 1 = 0&lt;/syntaxhighlight&gt;

:&lt;math&gt;\definecolor{myorange}{RGB}{255,165,100}\color{myorange}e^{i \pi}\color{Black} + 1 = 0&lt;/math&gt;

== Formatting issues ==

=== Spacing ===

Note that TeX handles most spacing automatically, but you may sometimes want manual control.

{| class=&quot;wikitable&quot;
! Feature
! Syntax
! How it looks rendered
|-
| double quad space
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;a \qquad b&lt;/source&gt;
| &lt;math&gt;a \qquad b&lt;/math&gt;
|-
| quad space
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;a \quad b&lt;/source&gt;
| &lt;math&gt;a \quad b&lt;/math&gt;
|-
| text space
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;a\ b&lt;/source&gt;
| &lt;math&gt;a\ b&lt;/math&gt;
|-
| text space without PNG conversion
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;a \mbox{ } b&lt;/source&gt;
| &lt;math&gt;a \mbox{ } b&lt;/math&gt;
|-
| large space
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;a\;b&lt;/source&gt;
| &lt;math&gt;a\;b&lt;/math&gt;
|-
| medium space
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;a\&lt;b&lt;/source&gt;
| [not supported]
|-
| small space
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;a\,b&lt;/source&gt;
| &lt;math&gt;a\,b&lt;/math&gt;
|-
| tiny space (use for multiplication of factors)
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;ab&lt;/source&gt;
| &lt;math&gt;ab&lt;/math&gt;
|-
| no space (use for multi-letter variables)
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\mathit{ab}&lt;/source&gt;
| &lt;math&gt;\mathit{ab}&lt;/math&gt;
|-
| small negative space
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;a\!b&lt;/source&gt;
| &lt;math&gt;a\!b&lt;/math&gt;
|}

Automatic spacing may be broken in very long expressions (because they produce an overfull hbox in TeX):

: &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+\cdots&lt;/source&gt;
: &lt;math&gt;0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+\cdots&lt;/math&gt;

This can be remedied by putting a pair of braces { } around the whole expression:

: &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;{0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+\cdots}&lt;/source&gt;
: &lt;math&gt;{0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+\cdots}&lt;/math&gt;

=== Alignment with normal text flow ===

Due to the default CSS

&lt;source lang=&quot;CSS&quot;&gt;img.tex { vertical-align: middle; }&lt;/source&gt;

an inline expression like &lt;math&gt;\int_{-N}^{N} e^x\, dx&lt;/math&gt; should look good.

If you need to align it otherwise, use &lt;code&gt;&lt;nowiki&gt;&lt;math style=&quot;vertical-align:-100%;&quot;&gt;...&lt;/math&gt;&lt;/nowiki&gt;&lt;/code&gt; and play with the &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;vertical-align&lt;/source&gt; argument until you get it right; however, how it looks may depend on the browser and the browser settings.

Also note that if you rely on this workaround, if/when the rendering on the server gets fixed in future releases, as a result of this extra manual offset your formulae will suddenly be aligned incorrectly. So use it sparingly, if at all.

== Commutative diagrams ==

To make a [[commutative diagram]], there are three steps:

# write the diagram in [[TeX]]
# convert to [[SVG]]
# [[commons:Commons:First steps/Upload form|upload the file]] to [[commons:|Wikimedia Commons]]

=== Diagrams in TeX ===

[http://www.tug.org/applications/Xy-pic/ Xy-pic] ([http://tex.loria.fr/graph-pack/doc-xypic/xyguide-html/xyguide-html.html online manual]) is the most powerful and general-purpose diagram package in [[TeX]]. Diagrams created using it can be found at [[commons:Category:Xy-pic diagrams|Commons: Category:Xy-pic diagrams]].

Simpler packages include:

* [[American Mathematical Society|AMS's]] [http://www.dante.de/CTAN//help/Catalogue/entries/amscd.html amscd]
* Paul Taylor's [http://www.ctan.org/tex-archive/macros/generic/diagrams/taylor/ diagrams]
* François Borceux [http://www.ctan.org/tex-archive/help/Catalogue/entries/borceux.html Diagrams]

The following is a template for Xy-pic, together with a [[Hack (technology)|hack]] to increase the [[Margin (typography)|margins]] in [[dvips]], so that the diagram is not truncated by over-eager cropping
(suggested in [[TUGboat]]: [http://www.tug.org/TUGboat/Articles/tb17-3/tb52rahtz.pdf TUGboat, Volume 17 1996, No. 3]):
&lt;source lang=latex&gt;
\documentclass{amsart}
\usepackage[all, ps, dvips]{xy}  % Loading the XY-Pic package
                                 % Using postscript driver for smoother curves
\usepackage{color}  % For invisible frame
\begin{document}
\thispagestyle{empty}  % No page numbers
\SelectTips{eu}{}  % Euler arrowheads (tips)
\setlength{\fboxsep}{0pt}  % Frame box margin
{\color{white}\framebox{{\color{black}$$  % Frame for margin

\xymatrix{
%%% Diagram goes here %%%
}

$$}}} % end math, end frame
\end{document}
&lt;/source&gt;

=== Convert to SVG ===

Once you have produced your diagram in LaTeX (or TeX), you can convert it to an SVG file using the following sequence of commands:

&lt;source lang=bash&gt;
pdflatex file.tex
pdfcrop --clip file.pdf tmp.pdf
pdf2svg tmp.pdf file.svg
rm tmp.pdf
&lt;/source&gt;

The [http://pdfcrop.sourceforge.net pdfcrop] and [http://www.cityinthesky.co.uk/opensource/pdf2svg pdf2svg] utilities are needed for this procedure. You can alternatively use [http://www.pdftron.com/pdf2svg/ pdf2svg] from PDFTron for the last step.

If you do not have [[pdfTeX]] (which is unlikely) you can use the following commands to replace the first step (TeX → PDF):
&lt;source lang=bash&gt;
latex file.tex
dvipdfm file.dvi
&lt;/source&gt;

In general, you will not be able to get anywhere with diagrams without TeX and Ghostscript, and the &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;inkscape&lt;/source&gt; program is a useful tool for creating or modifying your diagrams by hand. There is also a utility &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;pstoedit&lt;/source&gt; which supports direct conversion from Postscript files to many vector graphics formats, but it requires a non-free plugin to convert to SVG, and regardless of the format, [[User:Ryan Reich|this editor]] has not been successful in using it to convert diagrams with diagonal arrows from TeX-created files.

These programs are:

* a working TeX distribution, such as [[TeX Live]]
* [[Ghostscript]]
* [[pstoedit]]
* [[Inkscape]]

=== Upload the file ===
{{See also|commons:Commons:First steps/Upload form}}

{{See also|Help:Contents/Images and media}}

As the diagram is your own work, upload it to [[commons:|Wikimedia Commons]], so that all projects (notably, all languages) can use it without having to copy it to their language's Wiki. (If you've previously uploaded a file to somewhere other than Commons, to Commons.)

; Check size: Before uploading, check that the default size of the image is neither too large nor too small by opening in an [[SVG#Support in applications|SVG application]] and viewing at default size (100% scaling), otherwise adjust the &lt;code&gt;-y&lt;/code&gt; option to &lt;code&gt;dvips&lt;/code&gt;.
; Name: Make sure the file has a [[Wikipedia:Naming conventions|meaningful name]].
; Upload: [[commons:Special:Userlogin|Login to Wikimedia Commons]], then &lt;span class=plainlinks&gt;[http://commons.wikimedia.org/w/index.php?title=Special:Upload&amp;uselang=ownwork upload the file]&lt;/span&gt;; for the '''Summary''', give a brief description.

Now go to the [[Help:Image page|image page]] and add a [[commons:Commons:First steps/Quality and description#Good file descriptions|description]], including the '''source code''', using this template:

 &lt;nowiki&gt;{{&lt;/nowiki&gt;Information
 |description =
 &lt;nowiki&gt;{{&lt;/nowiki&gt;en|1= '''Description &lt;nowiki&gt;[[&lt;/nowiki&gt;:en:Link to WP page|topic&lt;nowiki&gt;]]&lt;/nowiki&gt;'''
 &lt;nowiki&gt;}}&lt;/nowiki&gt;
 |source = &lt;nowiki&gt;{{&lt;/nowiki&gt;own&lt;nowiki&gt;}}&lt;/nowiki&gt;, created as per:
  &lt;nowiki&gt;[[&lt;/nowiki&gt;:en:Help:Displaying a formula#Commutative diagrams&lt;nowiki&gt;]]&lt;/nowiki&gt;;
  source code below.
 |date = '''The Creation Date, like 1999-12-31'''
 |author = '''&lt;nowiki&gt;[[&lt;/nowiki&gt;User:YourUserName|Your Real Name&lt;nowiki&gt;]]&lt;/nowiki&gt;'''
 |permission = &lt;nowiki&gt;{{&lt;/nowiki&gt;self|PD-self '''(or [[commons:Licensing#Well-known licenses|other license]])'''
     |author = '''&lt;nowiki&gt;[[&lt;/nowiki&gt;User:YourUserName|Your Real Name&lt;nowiki&gt;]]&lt;/nowiki&gt;'''&lt;nowiki&gt;}}&lt;/nowiki&gt;
 &lt;nowiki&gt;}}&lt;/nowiki&gt;
 &lt;br&gt;
 
 ==TeX source==
 &amp;lt;source lang=latex&gt;
 '''% TeX source here'''
 &amp;lt;/source&gt;
 
 &lt;nowiki&gt;[[Category:Commutative diagrams]]&lt;/nowiki&gt;
 &lt;nowiki&gt;[[Category:Xy-pic diagrams]]&lt;/nowiki&gt;
 &lt;nowiki&gt;[[Category:Images with LaTeX source code]]&lt;/nowiki&gt;

; Source code:
* Include the source code in the [[Help:Image page|image page]], in the &lt;code&gt;Source&lt;/code&gt; section of the &lt;code&gt;&lt;nowiki&gt;{{&lt;/nowiki&gt;[[commons:Template:Information|Information]]&lt;nowiki&gt;}}&lt;/nowiki&gt;&lt;/code&gt; template, so that the diagram can be edited in future.
* Include the complete &lt;code&gt;.tex&lt;/code&gt; file, not just the fragment, so future editors do not need to reconstruct a compilable file.
* You may optionally make the source code section collapsible, using the &lt;code&gt;&lt;nowiki&gt;{{&lt;/nowiki&gt;[[commons:Template:cot|cot]]&lt;nowiki&gt;}}&lt;/nowiki&gt;&lt;/code&gt;/&lt;code&gt;&lt;nowiki&gt;{{&lt;/nowiki&gt;[[commons:Template:cob|cob]]&lt;nowiki&gt;}}&lt;/nowiki&gt;&lt;/code&gt; templates.
* (Don't include it in the Summary section, which is just supposed to be a summary.)
; License: The most common license for commutative diagrams is &lt;code&gt;[[commons:Template:PD-self|PD-self]]&lt;/code&gt;; some use &lt;code&gt;[[commons:Template:PD-self|PD-ineligible]]&lt;/code&gt;, especially for simple diagrams, or other licenses. Please ''do not'' use the [http://www.gnu.org/copyleft/fdl.html GFDL], as it requires the entire text of the GFDL to be attached to any document that uses the diagram.
; Description: If possible, link to a Wikipedia page relevant to the diagram. (The &lt;code&gt;1=&lt;/code&gt; is necessary if you use nest templates within the description, and harmless otherwise.)
; Category: Include &lt;code&gt;&lt;nowiki&gt;[[Category:Commutative diagrams]]&lt;/nowiki&gt;&lt;/code&gt;, so that it appears in [[commons:Category:Commutative diagrams]]. There are also subcategories, which you may choose to use.
; Include image: Now include the image on the original page via &lt;code&gt;&lt;nowiki&gt;[[File:Diagram.svg]]&lt;/nowiki&gt;&lt;/code&gt;

=== Examples ===

A sample conforming diagram is [[commons:Image:PSU-PU.svg]].

== Unimplemented elements and workarounds ==

=== &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiint&lt;/source&gt; and &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiiint&lt;/source&gt; ===

Elements which are not yet implemented are &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiint&lt;/source&gt;, a two-fold integral &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\iint&lt;/source&gt; {{nowrap|(&lt;math&gt;\iint&lt;/math&gt;)}} with a circular curve through the centre of the two integrals, and similarly &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiiint&lt;/source&gt;, a circular curve through three integrals. In contrast, &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oint&lt;/source&gt; {{nowrap|(&lt;math&gt;\oint&lt;/math&gt;)}} exists for the single dimension (integration over a curved line within a plane or any space with higher dimension).

These elements appear in many contexts: &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiint&lt;/source&gt; denotes a [[surface integral]] over the closed 2d boundary of a 3d region (which occurs in much of 3d [[vector calculus]] and physical applications – like [[Maxwell's equations]]), likewise &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiiint&lt;/source&gt; denotes integration over the closed 3d boundary (surface volume) of a 4d region, and they would be strong candidates for the next TeX version. As such there are a lot of workarounds in the present version.

:{| class=&quot;toccolours collapsible collapsed&quot; style=&quot;width:80%;text-align:left&quot;
!&lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiint&lt;/source&gt; and &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiiint&lt;/source&gt; using currently implemented symbols
|-
| &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiint&lt;/source&gt; looks like:

* &lt;math&gt;\iint\limits_{S}\!\!\!\!\!\!\!\!\!\!\!\subset\!\supset \mathbf D \cdot \mathrm{d}\mathbf A&lt;/math&gt;, which uses &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\iint&lt;/source&gt; along with &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\subset&lt;/source&gt; and &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\supset&lt;/source&gt; (overdrawn after backspacing):
: &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\iint\limits_{S}\!\!\!\!\!\!\!\!\!\!\!\subset\!\supset \mathbf D \cdot \mathrm{d}\mathbf A&lt;/source&gt;
* &lt;math&gt;\int\!\!\!\!\int_{\partial V}\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\;\;\;\bigcirc\,\,\mathbf D\cdot\mathrm{d}\mathbf A&lt;/math&gt;, which uses &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\int&lt;/source&gt; twice (with some backward [[Kern (typography)|kerning]]) along with &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\bigcirc&lt;/source&gt; (also overdrawn after backpacing) to produce a more consistent circle:
: &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\int\!\!\!\!\int_{\partial V}\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\;\;\;\bigcirc\,\,\mathbf D\cdot\mathrm{d}\mathbf A&lt;/source&gt;

&lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiiint&lt;/source&gt; (should also be preferably more tightly kerned) looks more or less like:

* &lt;math&gt;\int\!\!\!\!\!\int\!\!\!\!\!\int_{\partial V}\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\;\;\;\subset\!\supset \mathbf D\cdot\mathrm{d}\mathbf A&lt;/math&gt; which uses three \int symbols (with more backward kerning) with \subset and \supset (overdrawn after backspacing):
: &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\int\!\!\!\!\!\int\!\!\!\!\!\int_{\partial V}\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\;\;\;\subset\!\supset \mathbf D\;\cdot\mathrm{d}\mathbf A&lt;/source&gt;
* &lt;math&gt;\int\!\!\!\!\!\int\!\!\!\!\!\int_{\partial V}\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\;\;\;\bigcirc\,\,\mathbf D\;\cdot\mathrm{d}\mathbf A&lt;/math&gt;, which uses three &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\int&lt;/source&gt; symbols (with more backward kerning) along with &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\bigcirc&lt;/source&gt; (also overdrawn after backspacing):
: &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\int\!\!\!\!\!\int\!\!\!\!\!\int_{\partial V}\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\!\;\;\;\bigcirc\,\,\mathbf D\;\cdot\mathrm{d}\mathbf A&lt;/source&gt;
|}

However, since no standardisation exists as yet, any workaround like this (which uses many &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\!&lt;/source&gt; symbols for backspacing) should be avoided, if possible. See below for a possibility using PNG image enforcement.

Note that &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\iint&lt;/source&gt; (the double integral) and &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\iiint&lt;/source&gt; (the triple integral) are still not kerned as they should preferably be, and are currently rendered as if they were successive &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\int&lt;/source&gt; symbols ; this is not a major problem for reading the formulas, even if the integral symbols before the last one do not have bounds, so it's best to avoid backspacing &quot;hacks&quot; as they may be inconsistent with a possible future better implementation of integrals symbols (with more precisely computed kerning positions).

==== &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiint&lt;/source&gt; and &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiiint&lt;/source&gt; as PNG images ====

These symbols are available as PNG images which are also integrated into two templates, {{tl|oiint}} and {{tl|oiiint}}, which take care of the formatting around the symbols.

The templates have three parameters:

;preintegral: the text or formula immediately before the integral
;intsubscpt: the subscript below the integral
;integrand: the text or formula immediately after the integral

===== Examples =====

* [[Stokes' theorem]]: &lt;code&gt;&lt;nowiki&gt;{{oiint

| intsubscpt = &lt;math&gt;{\scriptstyle S}&lt;/math&gt;
| integrand=&lt;math&gt;( \nabla \times \bold{F} ) \cdot {\rm d}\bold{S} = \oint_{\partial S} \bold{F} \cdot {\rm d}\boldsymbol{\ell} &lt;/math&gt;
}}&lt;/nowiki&gt;&lt;/code&gt;

: {{oiint
| intsubscpt = &lt;math&gt;{\scriptstyle S}&lt;/math&gt;
| integrand=&lt;math&gt;( \nabla \times \mathbf{F} ) \cdot {\rm d}\mathbf{S} = \oint_{\partial S} \mathbf{F} \cdot {\rm d}\boldsymbol{\ell} &lt;/math&gt;
}}

* [[Ampère's circuital law|Ampère's law]] + correction: &lt;code&gt;&lt;nowiki&gt;{{oiint

| preintegral=&lt;math&gt;\oint_C \bold{B} \cdot {\rm d} \boldsymbol{\ell} = \mu_0 &lt;/math&gt;
| intsubscpt = &lt;math&gt;{\scriptstyle S}&lt;/math&gt;
| integrand = &lt;math&gt;\left ( \bold{J} + \epsilon_0\frac{\partial \bold{E}}{\partial t} \right ) \cdot {\rm d}\bold{S}&lt;/math&gt;
}}&lt;/nowiki&gt;&lt;/code&gt;

: {{oiint
| preintegral=&lt;math&gt;\oint_{\partial S} \mathbf{B} \cdot {\rm d} \boldsymbol{\ell} = \mu_0 &lt;/math&gt;
| intsubscpt = &lt;math&gt;{\scriptstyle S}&lt;/math&gt;
| integrand = &lt;math&gt;\left ( \mathbf{J} + \epsilon_0\frac{\partial \mathbf{E}}{\partial t} \right ) \cdot {\rm d}\mathbf{S}&lt;/math&gt;
}}

* Continuity of [[4-momentum]] flux (in [[general relativity]]):&lt;ref&gt;{{Cite book|title=Gravitation|author=J. A. Wheeler, C. Misner, K. S. Thorne| year=1973|publisher=W. H. Freeman &amp; Co|edition=2nd|isbn=0-7167-0344-0}}&lt;/ref&gt;&lt;code&gt;&lt;nowiki&gt; {{oiiint

| preintegral=&lt;math&gt;\bold{P} = &lt;/math&gt;
| intsubscpt = &lt;math&gt;{\scriptstyle \partial \Omega}&lt;/math&gt;
| integrand = &lt;math&gt;\bold{T} \cdot {\rm d}^3\boldsymbol{\Sigma} = 0&lt;/math&gt;
}}&lt;/nowiki&gt;&lt;/code&gt;

: {{oiiint
| preintegral=&lt;math&gt;\mathbf{P} = &lt;/math&gt;
| intsubscpt = &lt;math&gt;{\scriptstyle \partial \Omega}&lt;/math&gt;
| integrand = &lt;math&gt;\mathbf{T} \cdot {\rm d}^3\boldsymbol{\Sigma} = 0&lt;/math&gt;
}}

==== Oriented &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiint&lt;/source&gt; and &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiiint&lt;/source&gt; as PNG images ====

Some variants of &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiint&lt;/source&gt; and &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\oiiint&lt;/source&gt; have arrows on them to indicate the sense of integration, such as a line integral around a closed curve in the clockwise sense, and higher dimensional analogues. These are not implemented in {{TEX}} on Wikipedia either, although the template {{tl|intorient}} is available - see link for details.

=== &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\overarc&lt;/source&gt; ===

&lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\overarc&lt;/source&gt; is not yet implemented to display the arc notation. However, there exists a workaround: use &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\overset{\frown}{AB}&lt;/source&gt;, which gives
&lt;math&gt;\overset{\frown}{AB}&lt;/math&gt;

=== &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\dddot&lt;/source&gt; ===
&lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\dddot&lt;/source&gt; is not implemented in the TexVC renderer but does work in MatkJax. For a workaround use &lt;source lang=&quot;text&quot; enclose=&quot;none&quot;&gt;\overset{...}{x}&lt;/source&gt;, which gives
&lt;math&gt;\overset{...}{x}&lt;/math&gt;.

== Syntax to avoid ==

The texvc processor accepts some non-standard syntax. These should be avoided as the MathJax based renderers do not support these syntax.

====Percentages====
Texvc accepts &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;%&lt;/source&gt; for representing percentages. This cause an error with MathJax and should be replaced with &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\%&lt;/source&gt; in all renderers.

====\textrm====
In texvc spaces need to be represented inside the \textrm environment using &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\,&lt;/source&gt; &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\ &lt;/source&gt; and normal spaces are ignored i.e. &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\textrm{A\,B C}&lt;/source&gt; would render as {{math|A BC}}. In mathjax \textrm is an alias for \text which is renders its argument as normal text, hence  &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\textrm{A\,B C}&lt;/source&gt; renders as {{math|A\,B C}}. To ensure compatibility between versions alway use the \text environment: &lt;source lang=&quot;latex&quot; enclose=&quot;none&quot;&gt;\text{A B C}&lt;/source&gt;.

====unicode characters====

Unicode characters like π work in MathML, and MathJax but not in texvc so should be avoided.

== Examples of implemented TeX formulas ==

&lt;div style=&quot;text-align: center;&quot;&gt;
=== Quadratic polynomial ===

&lt;math&gt;ax^2 + bx + c = 0&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;latex&quot;&gt;&lt;math&gt;ax^2 + bx + c = 0&lt;/math&gt;&lt;/source&gt;

=== Quadratic formula ===

&lt;math&gt;x={-b\pm\sqrt{b^2-4ac} \over 2a}&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;latex&quot;&gt;&lt;math&gt;x={-b\pm\sqrt{b^2-4ac} \over 2a}&lt;/math&gt;&lt;/source&gt;

=== Tall parentheses and fractions ===

&lt;math&gt;2 = \left( \frac{\left(3-x\right) \times 2}{3-x} \right)&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;text&quot;&gt;&lt;math&gt;2 = \left(
\frac{\left(3-x\right) \times 2}{3-x}
\right)&lt;/math&gt;&lt;/source&gt;

&lt;math&gt;S_{\text{new}} = S_{\text{old}} - \frac{ \left( 5-T \right) ^2} {2}&lt;/math&gt;
&lt;source lang=&quot;text&quot;&gt;
&lt;math&gt;S_{\text{new}} = S_{\text{old}} - \frac{ \left( 5-T \right) ^2} {2}&lt;/math&gt;
&lt;/source&gt;

=== Integrals ===

&lt;math&gt;\int_a^x \!\!\!\int_a^s f(y)\,dy\,ds = \int_a^x f(y)(x-y)\,dy&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;latex&quot;&gt;&lt;math&gt;\int_a^x \!\!\!\int_a^s f(y)\,dy\,ds
= \int_a^x f(y)(x-y)\,dy&lt;/math&gt;&lt;/source&gt;

=== Matrices and determinants ===

&lt;math&gt;\det(\mathsf{A}-\lambda\mathsf{I}) = 0&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;text&quot;&gt;&lt;math&gt;\det(\mathsf{A}-\lambda\mathsf{I}) = 0&lt;/math&gt;&lt;/source&gt;

=== Summation ===

&lt;math&gt;\sum_{i=0}^{n-1} i&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;text&quot;&gt;&lt;math&gt;\sum_{i=0}^{n-1} i&lt;/math&gt;&lt;/source&gt;

&lt;math&gt;\sum_{m=1}^\infty\sum_{n=1}^\infty\frac{m^2\,n}{3^m\left(m\,3^n+n\,3^m\right)}&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;text&quot;&gt;&lt;math&gt;\sum_{m=1}^\infty\sum_{n=1}^\infty\frac{m^2\,n}
{3^m\left(m\,3^n+n\,3^m\right)}&lt;/math&gt;&lt;/source&gt;

=== Differential equation ===

&lt;math&gt;u'' + p(x)u' + q(x)u=f(x),\quad x&gt;a&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;latex&quot;&gt;&lt;math&gt;u'' + p(x)u' + q(x)u=f(x),\quad x&gt;a&lt;/math&gt;&lt;/source&gt;

=== Complex numbers ===

&lt;math&gt;|\bar{z}| = |z|, |(\bar{z})^n| = |z|^n, \arg(z^n) = n \arg(z)&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;text&quot;&gt;&lt;math&gt;|\bar{z}| = |z|,
|(\bar{z})^n| = |z|^n,
\arg(z^n) = n \arg(z)&lt;/math&gt;&lt;/source&gt;

=== Limits ===

&lt;math&gt;\lim_{z\to z_0} f(z)=f(z_0)&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;latex&quot;&gt;&lt;math&gt;\lim_{z\to z_0} f(z)=f(z_0)&lt;/math&gt;&lt;/source&gt;

=== Integral equation ===

&lt;math&gt;\phi_n(\kappa)
= \frac{1}{4\pi^2\kappa^2} \int_0^\infty \frac{\sin(\kappa R)}{\kappa R} \frac{\partial}{\partial R} \left[R^2\frac{\partial D_n(R)}{\partial R}\right]\,dR&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;text&quot;&gt;&lt;math&gt;\phi_n(\kappa) =
\frac{1}{4\pi^2\kappa^2} \int_0^\infty
\frac{\sin(\kappa R)}{\kappa R}
\frac{\partial}{\partial R}
\left[R^2\frac{\partial D_n(R)}{\partial R}\right]\,dR&lt;/math&gt;&lt;/source&gt;

=== Example ===

&lt;math&gt;\phi_n(\kappa) = 0.033C_n^2\kappa^{-11/3},\quad \frac{1}{L_0}\ll\kappa\ll\frac{1}{l_0}&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;text&quot;&gt;&lt;math&gt;\phi_n(\kappa) =
0.033C_n^2\kappa^{-11/3},\quad
\frac{1}{L_0}\ll\kappa\ll\frac{1}{l_0}&lt;/math&gt;&lt;/source&gt;

=== Continuation and cases ===

&lt;math&gt;f(x) = \begin{cases}1 &amp; -1 \le x &lt; 0 \\
\frac{1}{2} &amp; x = 0 \\ 1 - x^2 &amp; \text{otherwise}\end{cases}&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;latex&quot;&gt;&lt;math&gt;
f(x) =
\begin{cases}
1 &amp; -1 \le x &lt; 0 \\
\frac{1}{2} &amp; x = 0 \\
1 - x^2 &amp; \text{otherwise}
\end{cases}
&lt;/math&gt;&lt;/source&gt;

=== Prefixed subscript ===

&lt;math&gt;{}_pF_q(a_1,\dots,a_p;c_1,\dots,c_q;z) = \sum_{n=0}^\infty \frac{(a_1)_n\cdots(a_p)_n}{(c_1)_n\cdots(c_q)_n}\frac{z^n}{n!}&lt;/math&gt;
&lt;br&gt;
&lt;source lang=&quot;text&quot;&gt; &lt;math&gt;{}_pF_q(a_1,\dots,a_p;c_1,\dots,c_q;z)
= \sum_{n=0}^\infty
\frac{(a_1)_n\cdots(a_p)_n}{(c_1)_n\cdots(c_q)_n}
\frac{z^n}{n!}&lt;/math&gt;&lt;/source&gt;

=== Fraction and small fraction ===

&lt;math&gt;\frac{a}{b}\ \tfrac{a}{b}&lt;/math&gt;
&lt;source lang=&quot;text&quot;&gt;&lt;math&gt;\frac{a}{b}\ \tfrac{a}{b}&lt;/math&gt;&lt;/source&gt;

=== Area of a quadrilateral ===

&lt;math&gt;S=dD\,\sin\alpha\!&lt;/math&gt;
&lt;source lang=&quot;latex&quot;&gt;&lt;math&gt;S=dD\,\sin\alpha\!&lt;/math&gt;&lt;/source&gt;

=== Volume of a sphere-stand ===

&lt;math&gt;V=\frac16\pi h\left[3\left(r_1^2+r_2^2\right)+h^2\right]&lt;/math&gt;
&lt;source lang=&quot;latex&quot;&gt;&lt;math&gt;V=\frac16\pi h\left[3\left(r_1^2+r_2^2\right)+h^2\right]&lt;/math&gt;&lt;/source&gt;

=== Multiple equations ===

&lt;math&gt;\begin{align}
u &amp; = \tfrac{1}{\sqrt{2}}(x+y) \qquad &amp; x &amp;= \tfrac{1}{\sqrt{2}}(u+v)\\
v &amp; = \tfrac{1}{\sqrt{2}}(x-y) \qquad &amp; y &amp;= \tfrac{1}{\sqrt{2}}(u-v)
\end{align}&lt;/math&gt;
&amp;nbsp;
&lt;source lang=&quot;text&quot;&gt;&lt;math&gt;\begin{align}
u &amp; = \tfrac{1}{\sqrt{2}}(x+y) \qquad &amp; x &amp;= \tfrac{1}{\sqrt{2}}(u+v) \\
v &amp; = \tfrac{1}{\sqrt{2}}(x-y) \qquad &amp; y &amp;= \tfrac{1}{\sqrt{2}}(u-v)
\end{align}&lt;/math&gt;&lt;/source&gt;
&lt;/div&gt;

== See also ==

* [[Wikipedia:Manual of Style (mathematics)#Typesetting of mathematical formulae|Typesetting of mathematical formulae]]
* Proposed [[m:Music markup]] and [[Help:Musical symbols]]
* [[Table of mathematical symbols]]
* [[Wikipedia:Rendering math]]
* [[mw:Extension:Blahtex]], or [[Wikipedia talk:WikiProject Mathematics/Archive10#blahtex: a LaTeX to MathML converter|blahtex: a LaTeX to MathML converter for Wikipedia]]
* [[commons:Category:Images which should use TeX]]

== References ==
{{reflist}}

== External links ==
{{Wikibooks|LaTeX}}

* [http://www.maths.tcd.ie/~dwilkins/LaTeXPrimer/ A LaTeX tutorial]
*[http://www.codecogs.com/latex/eqneditor.php LaTex online editor]
* {{Citation

|last= Doob
|first= Michael

|title= A Gentle Introduction to TeX: A Manual for Self-study
|url= http://www.ctan.org/tex-archive/info/gentle/gentle.pdf
|doi= }}. A paper introducing TeX — see page 39 onwards for a good introduction to the maths side of things.

* {{Citation

|last= Oetiker
|first= Tobias
|last2= Partl
|first2= Hubert
|last3= Hyna
|first3= Irene
|last4= Schlegl
|first4= Elisabeth
|title= The Not So Short Introduction to LaTeX 2&lt;sub&gt;&amp;epsilon;&lt;/sub&gt;

|date= December 13, 2009
|edition= 4.27
|url= http://www.ctan.org/tex-archive/info/lshort/english/lshort.pdf
|doi= }}. A paper introducing LaTeX — skip to page 49 for the math section. See page 63 for a complete reference list of symbols included in LaTeX and AMS-LaTeX.

* [http://tug.ctan.org/tex-archive/info/symbols/comprehensive/symbols-letter.pdf The Comprehensive LaTeX Symbol List]—symbols not found here may be documented there.
* [http://www.tex.ac.uk/tex-archive/info/symbols/comprehensive/symbols-a4.pdf Long list of many symbols]
* [http://amath.colorado.edu/documentation/LaTeX/Symbols.pdf short list of common symbols]
* [http://milde.users.sourceforge.net/LUCR/Math/mathpackages/esint-symbols.pdf The esint package for closed double integrals]
* [http://mirror.ox.ac.uk/sites/ctan.org/macros/latex/contrib/esint/esint.pdf The esint package for closed double integrals]
* [http://www.math.washington.edu/tex-archive/macros/latex/contrib/cancel/cancel.pdf cancel package]
* [http://www.ams.org/tex/amslatex.html AMS-LaTeX guide].
* [http://us.metamath.org/symbols/symbols.html A set of public domain fixed-size math symbol bitmaps].
* [[MathML]]: A product of the [[W3C]] [http://www.w3.org/Math/ Math working group], is a low-level specification for describing mathematics as a basis for machine to machine communication.
{{Help navigation}}
[[Category:Wikipedia text help]]</text>
      <sha1>oaveuhpcxrm5s2uqzxou87r8r0ftmyp</sha1>
    </revision>
  </page>
  <page>
    <title>User:PGCX864</title>
    <ns>2</ns>
    <id>362886</id>
    <revision>
      <id>4668916</id>
      <parentid>4414345</parentid>
      <timestamp>2026-09-05T12:06:16Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668916</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6090" sha1="hakf93tjnge4zm6vewq7cly4ja3q8e9" xml:space="preserve">== Unicode versions table (Current style) ==
{|
|- style=&quot;vertical-align:middle&quot;
|
{| border=&quot;1&quot; cellpadding=&quot;3&quot; cellspacing=&quot;0&quot; style=&quot;border-collapse:collapse;margin:0 0 0 4em;&quot;
|----- style=&quot;text-align:center&quot;
!colspan=&quot;4&quot;|Legend:
|----- style=&quot;text-align:center&quot;
!colspan=&quot;4&quot; {{Yes|Released versions}}
|----- style=&quot;text-align:center&quot; {{Yes}}
!1.x
!2.x
!3.x
!4.x
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#f66;{{text default color}};&quot;|[[Unicode/Versions#Unicode 1.0|Unicode&amp;nbsp;1.0]]
|style=&quot;background:#ff6;{{text default color}}&quot;|[[Unicode/Versions#Unicode 2.0|Unicode&amp;nbsp;2.0]]
|style=&quot;background:#6f6;{{text default color}};&quot;|[[Unicode/Versions#Unicode 3.0|Unicode&amp;nbsp;3.0]]
|style=&quot;background:#6ff;{{text default color}};&quot;|[[Unicode/Versions#Unicode 4.0|Unicode&amp;nbsp;4.0]]
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#f96;{{text default color}};&quot;|[[Unicode/Versions#Unicode 1.1|Unicode&amp;nbsp;1.1]]
|style=&quot;background:#cf6;{{text default color}};&quot;|[[Unicode/Versions#Unicode 2.1|Unicode&amp;nbsp;2.1]]
|style=&quot;background:#6f9;{{text default color}};&quot;|[[Unicode/Versions#Unicode 3.1|Unicode&amp;nbsp;3.1]]
|style=&quot;background:#6cf;{{text default color}};&quot;|[[Unicode/Versions#Unicode 4.1|Unicode&amp;nbsp;4.1]]
|----- style=&quot;text-align:center&quot;
||
||
|style=&quot;background:#6fc;{{text default color}};&quot;|[[Unicode/Versions#Unicode 3.2|Unicode&amp;nbsp;3.2]]
||
|----- style=&quot;text-align:center&quot; {{Yes}}
!5.x
!6.x
!7.x
!8.x
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#66f;{{text default color}};&quot;|[[Unicode/Versions#Unicode 5.0|Unicode&amp;nbsp;5.0]]
|style=&quot;background:#f6f;{{text default color}};&quot;|[[Unicode/Versions#Unicode 6.0|Unicode&amp;nbsp;6.0]]
|style=&quot;background:#298;{{text default color}};&quot;|[[Unicode/Versions#Unicode 7.0|Unicode&amp;nbsp;7.0]]
|style=&quot;background:#163;{{text default color}};&quot;|[[Unicode/Versions#Unicode 8.0|Unicode&amp;nbsp;8.0]]
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#96f;{{text default color}};&quot;|[[Unicode/Versions#Unicode 5.1|Unicode&amp;nbsp;5.1]]
|style=&quot;background:#98c;{{text default color}};&quot;|[[Unicode/Versions#Unicode 6.1|Unicode&amp;nbsp;6.1]]
||
||
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#c6f;{{text default color}};&quot;|[[Unicode/Versions#Unicode 5.2|Unicode&amp;nbsp;5.2]]
|style=&quot;background:#a86;{{text default color}};&quot;|[[Unicode/Versions#Unicode 6.2|Unicode&amp;nbsp;6.2]]
||
||
|----- style=&quot;text-align:center&quot;
||
|style=&quot;background:#892;{{text default color}};&quot;|[[Unicode/Versions#Unicode 6.3|Unicode&amp;nbsp;6.3]]
||
||
|----- style=&quot;text-align:center&quot;
!colspan=&quot;4&quot; style=&quot;background:plum;{{text default color}}&quot;|Future versions
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#713;{{text default color}};&quot;|[[Unicode/Versions#Unicode 9.0|Unicode&amp;nbsp;9.0]]
|style=&quot;background:#06f;{{text default color}}&quot;|[[Unicode/Versions#Unicode 10.0|Unicode&amp;nbsp;10.0]]
|colspan=&quot;2&quot; style=&quot;background:#666;color:#fff;&quot;|Reserved
|----- style=&quot;text-align:center&quot;
|colspan=&quot;2&quot; style=&quot;background:#fff;{{text default color}}&quot;|Private use
|colspan=&quot;2&quot; style=&quot;background:#000;color:#fff;&quot;|Noncharacter
|}
|}
== Unicode versions table (New style) ==
{|
|- style=&quot;vertical-align:middle&quot;
|
{| border=&quot;1&quot; cellpadding=&quot;3&quot; cellspacing=&quot;0&quot; style=&quot;border-collapse:collapse;margin:0 0 0 4em;&quot;
|----- style=&quot;text-align:center&quot;
!colspan=&quot;4&quot;|Legend:
|----- style=&quot;text-align:center&quot;
!colspan=&quot;4&quot; {{Yes|Released versions}}
|----- style=&quot;text-align:center&quot; {{Yes}}
!1.x
!2.x
!3.x
!4.x
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#f33;{{text default color}};&quot;|[[Unicode/Versions#Unicode 1.0|Unicode&amp;nbsp;1.0]]
|style=&quot;background:#6ff;{{text default color}};&quot;|[[Unicode/Versions#Unicode 2.0|Unicode&amp;nbsp;2.0]]
|style=&quot;background:#ff3;{{text default color}};&quot;|[[Unicode/Versions#Unicode 3.0|Unicode&amp;nbsp;3.0]]
|style=&quot;background:#9f6;{{text default color}};&quot;|[[Unicode/Versions#Unicode 4.0|Unicode&amp;nbsp;4.0]]
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#f63;{{text default color}};&quot;|[[Unicode/Versions#Unicode 1.1|Unicode&amp;nbsp;1.1]]
|style=&quot;background:#6cf;{{text default color}};&quot;|[[Unicode/Versions#Unicode 2.1|Unicode&amp;nbsp;2.1]]
|style=&quot;background:#fc3;{{text default color}}&quot;|[[Unicode/Versions#Unicode 3.1|Unicode&amp;nbsp;3.1]]
|style=&quot;background:#9c6;{{text default color}}&quot;|[[Unicode/Versions#Unicode 4.1|Unicode&amp;nbsp;4.1]]
|----- style=&quot;text-align:center&quot;
||
||
|style=&quot;background:#f93;{{text default color}}&quot;|[[Unicode/Versions#Unicode 3.2|Unicode&amp;nbsp;3.2]]
||
|----- style=&quot;text-align:center&quot; {{Yes}}
!5.x
!6.x
!7.x
!8.x
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#99f;{{text default color}}&quot;|[[Unicode/Versions#Unicode 5.0|Unicode&amp;nbsp;5.0]]
|style=&quot;background:#f9c;{{text default color}}&quot;|[[Unicode/Versions#Unicode 6.0|Unicode&amp;nbsp;6.0]]
|style=&quot;background:#396;{{text default color}}&quot;|[[Unicode/Versions#Unicode 7.0|Unicode&amp;nbsp;7.0]]
|style=&quot;background:#963;{{text default color}}&quot;|[[Unicode/Versions#Unicode 8.0|Unicode&amp;nbsp;8.0]]
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#96f;{{text default color}}{{text default color}};&quot;|[[Unicode/Versions#Unicode 5.1|Unicode&amp;nbsp;5.1]]
|style=&quot;background:#f6c;{{text default color}}&quot;|[[Unicode/Versions#Unicode 6.1|Unicode&amp;nbsp;6.1]]
||
||
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#93f;{{text default color}}&quot;|[[Unicode/Versions#Unicode 5.2|Unicode&amp;nbsp;5.2]]
|style=&quot;background:#f3c;{{text default color}}&quot;|[[Unicode/Versions#Unicode 6.2|Unicode&amp;nbsp;6.2]]
||
||
|----- style=&quot;text-align:center&quot;
||
|style=&quot;background:#f0c;{{text default color}}&quot;|[[Unicode/Versions#Unicode 6.3|Unicode&amp;nbsp;6.3]]
||
||
|----- style=&quot;text-align:center&quot;
!colspan=&quot;4&quot; style=&quot;background:plum;{{text default color}}&quot;|Future versions
|----- style=&quot;text-align:center&quot;
|style=&quot;background:#933;{{text default color}}&quot;|[[Unicode/Versions#Unicode 9.0|Unicode&amp;nbsp;9.0]]
|style=&quot;background:#36f;{{text default color}}&quot;|[[Unicode/Versions#Unicode 10.0|Unicode&amp;nbsp;10.0]]
|colspan=&quot;2&quot; style=&quot;background:#666;color:#fff;&quot;|Reserved
|----- style=&quot;text-align:center&quot;
|colspan=&quot;2&quot; style=&quot;background:#fff;{{text default color}}&quot;|Private use
|colspan=&quot;2&quot; style=&quot;background:#000;color:#fff;&quot;|Noncharacter
|}
|}</text>
      <sha1>hakf93tjnge4zm6vewq7cly4ja3q8e9</sha1>
    </revision>
  </page>
  <page>
    <title>User:Williammacewen2</title>
    <ns>2</ns>
    <id>367055</id>
    <revision>
      <id>4668991</id>
      <parentid>4668913</parentid>
      <timestamp>2026-09-05T19:04:09Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4668991</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="71507" sha1="nv6juvoblfp9niysvchg0vllf389auv" xml:space="preserve">{{userpage}}
&lt;div style=&quot;padding:1em; border: ; background-color:;color:inherit;-moz-border-radius:15px; margin-left: 6px; margin-right: 6px; ; text-align: center&quot;&gt;
[[Image:Crystal message2.png|24px]] '''[http://en.wikibooks.org/w/index.php?title=User_talk:williammacewen&amp;action=edit&amp;section=new Leave me a new message here]''' &lt;/div&gt; 
Hi! My name is '''William MacEwen'''.
== About religion ==
{{cquote2|Being crafty, I caught you with guile...for if the truth of God hath more abounded through my LIE unto his glory; why yet am I also adjudged a sinner?|[[w:St Paul|St Paul]]||90|90}}
{{cquote2|What profit has not that fable of Jesus brought us!|[[w:Pope Leo X|Pope Leo X]]||90|90}}
[[Image:Uthman Koran Taschkent a.jpg|thumb|center|250px|The Samarkand Quran [[w:carbon dating|carbon dated]] to the [[w:7th century|7th century]]]]
The [[w:Early Quranic manuscripts|oldest complete Quran]] manuscript is the [[w:Samarkand Kufic Quran|Samarkand Codex]]. Based on [[w:orthography|orthographic]] and [[w:Palaeography|palaeographic]] studies, the manuscript probably dates the 8th or 9th century  CE.&lt;ref&gt;{{cite web|title=The “Qur'ān Of ʿUthmān” At Tashkent (Samarqand), Uzbekistan, From 2nd Century Hijra|url=http://www.islamic-awareness.org/Quran/Text/Mss/samarqand.html|accessdate=5 September 2013}}&lt;/ref&gt;&lt;ref&gt; E. A. Rezvan, &quot;On The Dating Of An “'Uthmanic Qur'an” From St. Petersburg&quot;, ''Manuscripta Orientalia'', 2000, Volume 6, No. 3, pp. 19-22.[http://www.kunstkamera.ru/files/lib/978-5-88431-178-7/978-5-88431-178-7_12.pdf]&lt;/ref&gt; Radio-carbon dating showed a 95.4% probability of a date between 595 CE and 855 CE.&lt;ref&gt; E. A. Rezvan, &quot;On The Dating Of An “'Uthmanic Qur'an” From St. Petersburg&quot;, ''Manuscripta Orientalia'', 2000, Volume 6, No. 3, pp. 19-22.[http://www.kunstkamera.ru/files/lib/978-5-88431-178-7/978-5-88431-178-7_12.pdf]&lt;/ref&gt;
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:250%&quot;&gt;وتَرَى الجِبَالَ تَحسَبُها جَامِدةً وهِيَ تَمُرُّ مَرَّ السَّحَاب&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:156%&quot;&gt;And you see the mountains thinking they are frozen but they move like the clouds.&lt;/span&gt;&lt;/p&gt;
&lt;div align=&quot;left&quot;&gt;– [[w:Quran|Quran]] [http://quran.com/27/88 27:88]&lt;/div&gt;
&lt;br&gt;
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:250%&quot;&gt;وهو الذى خَلَقَ اللَيلَ والنَهَارَ والشَمسَ والقَمَرَ كُلٌّ فِى فَلَكٍ يَسبَحُون&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:156%&quot;&gt;And he is the one who created the night and the day and the sun and the moon all float in an orbit.&lt;/span&gt;&lt;/p&gt;
&lt;div align=&quot;left&quot;&gt;– Quran [http://quran.com/21/33 21:33]&lt;/div&gt;
&lt;br&gt;
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:250%&quot;&gt;لا الشَمسُ يَنبَغِى لهَا أَن تُدرِكَ القَمَرَ ولا الَيلُ سَابِقٌ النَهَارِ وكُلٌّ فِى فَلَكٍ يَسبَحُون&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:156%&quot;&gt;It does not suit the sun to overtake the moon and the night does not come before the day and both [the sun and the moon] are floating in an orbit.&lt;/span&gt;&lt;/p&gt;
&lt;div align=&quot;left&quot;&gt;– Quran [http://quran.com/36/40 36:40]&lt;/div&gt;
&lt;br&gt;
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:250%&quot;&gt;والشَمسُ تَجرِى لِمُستَقَرٍّ لهَا ذلك تَقدِيرُ العَزِيزِ العَلِيم&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:156%&quot;&gt;The sun will move until a stopping point for it, that is the measure of the powerful and knowing one.&lt;/span&gt;&lt;/p&gt;
&lt;div align=&quot;left&quot;&gt;– Quran [http://quran.com/36/38 36:38]&lt;/div&gt;
== How do I conjugate Arabic verbs? ==
=== Conjugation of weak verb رَمَى ramaa to shoot ===
==== first form ====
===== active =====
{| border=1 cellpadding=7 cellspacing=1
|- bgcolor=#eeeeee
! align=left | Number 
! align=left | English pronoun
! align=left | Arabic pronoun
! align=left | perfect
! align=left | indicative
! align=left | subjunctive
! align=left | jussive
! align=left | emphatic I
! align=left | emphatic II
! align=left | simple imperative
! align=left | emphatic imperative I
! align=left | emphatic imperative II
! align=left | agent noun
|-
|3rd masc. sing. ||he||هو|| رَمَى||يَرْمِيْ||يَرْمِيَ||يَرْمِ||يَرْمِيَنَّ||يَرْمِيَنْ||n/a||n/a||n/a||رَامٍ
|-
| 3rd fem. sing. ||she||هي||رَمَتْ||تَرْمِي||ترمِيَ||ترمِ||ترمِيَنَّ||تَرْمِيَنْ||n/a||n/a||n/a||رَامِيَةٌ
|-
|3rd masc. dual ||||هما||رَمَيَا||يَرْمِيَانِ||يَرْمِيَا||[[w:Ibid|ibid]]||يَرْمِيَانِّ||[https://en.wikipedia.org/wiki/N/a n/a]||n/a||n/a||/n/a||
|-
|2nd fem. dual||||هما||رَمَتَا||تَرْمِيَانِ||تَرْمِيَا||ibid.||ترمِيَانِّ||n/a||n/a||n/a||n/a||
|-
|3rd masc. plur.||they||هم||رَمَوْا||يَرْمُونَ||يرمُوا||ibid.||يَرْمُنَّ||يرمُنْ||n/a||n/a||n/a||
|-
|3rd fem. plur. ||||هنّ||رَمَيْنَ||يَرْمِيْنَ||ibid.||ibid||يَرْمِيْنَانِّ||n/a||n/a||n/a||n/a||
|-
|2nd masc. sing.||[https://en.wikipedia.org/wiki/Thou thou]||أنتَ||رَمَيْتَ||تَرْمِيْ||ترْمِيَ||ترْمِ||تَرْمِيَنَّ||تَرْمِيَنْ||اِرْمِ||إِرْمِيَنَّ||اِرْمِيَنْ||
|-
|2nd fem. sing. ||||أنتِ||رَمَيْتِ||تَرْمِيْنَ||تَرْمِيْ||ibid||تَرْمِنَّ||تَرْمِنْ||اِرْمِيْ||اِرْمِنَّ||اِرْمِنْ||
|-
|2nd dual||||أنتما||رَمَيْتُمَا||تَرْمِيَانِ||تَرْمِيَا||ibid||تَرْمِيَانِّ||n/a||اِرْمِيَا||اِرْمِيَانِّ||n/a||
|-
|2nd masc. plur. ||[https://en.wikipedia.org/wiki/Ye_(pronoun) ye]||أنتم||رَمَيْتُمْ||تَرْمُوْنَ||تَرْمُوْا||ibid||تَرْمُنَّ||تَرْمُنْ||اِرْمُوْا||اِرْمُنَّ||إِرْمُنْ||
|-
|2nd fem. plur. ||||أنتنّ||رَمَيْتُنَّ||تَرْمِيْنَ||ibid.||ibid||تَرْمِيْنَانِّ||n/a||إِرْمِيْنَ||اِرْمِيْنَانِّ||n/a||
|-
|1st sing.||I||أنا||رَمَيْتُ||اَرْمِيْ||أَرْمِيَ||اَرْمِ||اَرْمِيَنَّ||اَرْمِيَنْ||n/a||n/a||n/a||
|-
|1st plur.||we||نحن||رَمَيْنَا||نَرْمِيْ||نَرْمِيَ||نَرْمِ||نَرْمِيَنَّ||نَرْمِيَنْ||n/a||n/a||n/a||
|}

=== Conjugation of weak verb مَدَّ madda to extend ===
==== first form ====
===== active =====
{| border=1 cellpadding=7 cellspacing=1
|- bgcolor=#eeeeee
! align=left | Number 
! align=left | English pronoun
! align=left | Arabic pronoun
! align=left | perfect
! align=left | indicative
! align=left | subjunctive
! align=left | jussive
! align=left | emphatic 1
! align=left | emphatic 2
! align=left | simple imperative
! align=left | imperative emphatic 1
! align=left | imperative emphatic 2
! align=left | agent noun
|-
|3rd masc. sing. ||he||هو||مَدَّ||يمُدُّ||يَمُدَّ||يَمْدُدْ||يَمُدَّنَّ||يمُدًّا||[https://en.wikipedia.org/wiki/N/a na]||na||na||مَادَّ
|-
| 3rd fem. sing. ||she||هی||مَدَّتْ||تمُدُّ||تمُدَّ||تَمْدُدْ||تمُدَّنَّ||تَمُدًّا||na||na||na||مَادَّة
|-
|3rd masc. dual ||||هما||مَدَّا~~
|-
|2nd fem. dual||||هما||رَمَتَا||تَرْمِيَانِ||تَرْمِيَاتَرْمِيَا||ibid.||ترمِيَانِّ||n/a||n/a||n/a||n/a||
|-
|3rd masc. plur.||they||هم||رَمَوْا||يَرْمُونَ||يرمُوا||ibid.||يَرْمُنَّ||يرمُنْ||n/a||n/a||n/a||
|-
|3rd fem. plur. ||||هنّ||رَمَيْنَ||يَرْمِيْنَ||ibid.||ibid||يَرْمِيْنَانِّ||n/a||n/a||n/a||n/a||
|-
|2nd masc. sing.||[https://en.wikipedia.org/wiki/Thou thou]||أنتَ||رَمَيْتَ||تَرْمِيْ||ترْمِيَ||ترْمِ||تَرْمِيَنَّ||تَرْمِيَنْ||اِرْمِ||إِرْمِيَنَّ||اِرْمِيَنْ||
|-
|2nd fem. sing. ||||أنتِ||رَمَيْتِ||تَرْمِيْنَ||تَرْمِيْ||ibid||تَرْمِنَّ||تَرْمِنْ||اِرْمِيْ||اِرْمِنَّ||اِرْمِنْ||
|-
|2nd dual||||أنتما||رَمَيْتُمَا||تَرْمِيَانِ||تَرْمِيَا||ibid||تَرْمِيَانِّ||n/a||اِرْمِيَا||اِرْمِيَانِّ||n/a||
|-
|2nd masc. plur. ||[https://en.wikipedia.org/wiki/Ye_(pronoun) ye]||أنتم||رَمَيْتُمْ||تَرْمُوْنَ||تَرْمُوْا||ibid||تَرْمُنَّ||تَرْمُنْ||اِرْمُوْا||اِرْمُنَّ||إِرْمُنْ||
|-
|2nd fem. plur. ||||أنتنّ||رَمَيْتُنَّ||تَرْمِيْنَ||ibid.||ibid||تَرْمِيْنَانِّ||n/a||إِرْمِيْنَ||اِرْمِيْنَانِّ||n/a||
|-
|1st sing.||I||أنا||رَمَيْتُ||اَرْمِيْ||أَرْمِيَ||اَرْمِ||اَرْمِيَنَّ||اَرْمِيَنْ||n/a||n/a||n/a||
|-
|1st plur.||we||نحن||رَمَيْنَا||نَرْمِيْ||نَرْمِيَ||نَرْمِ||نَرْمِيَنَّ||نَرْمِيَنْ||n/a||n/a||n/a||
|}

== Plurals ==
{| border=1 cellpadding=7 cellspacing=1
|- bgcolor= #FFF8E7
! align=left | &lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;شكل&lt;/span&gt;&lt;/p&gt;&lt;br&gt;Form
! align=left | &lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;&lt;span style=&quot;color: #E86100;&quot;&gt;شرط&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;br&gt;&lt;span style=&quot;font-size:125%&quot;&gt;&lt;span style=&quot;color: #E86100;&quot;&gt;Condition&lt;/span&gt;&lt;/span&gt;
! align=left | &lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;جمع&lt;/span&gt;&lt;/p&gt;&lt;br&gt;Plural
! align=left | &lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;نادر؟&lt;/span&gt;&lt;/p&gt;&lt;br&gt;Rare?
! align=left | &lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مثال مفرد&lt;/span&gt;&lt;/p&gt;&lt;br&gt;example singular
! align=left | &lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مثال جمعه&lt;/span&gt;&lt;/p&gt;&lt;br&gt;example its plural
! align=left | &lt;p align=&quot;left&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;ثنية&lt;/span&gt;&lt;/p&gt;&lt;br&gt;Exception
|-
|&lt;span style=&quot;font-size:222%&quot;&gt;فُعْلَة&lt;/span&gt;||||&lt;span style=&quot;font-size:222%&quot;&gt;فُعَل&lt;/span&gt;||||تُحْفَہ&lt;br&gt;قُبَّہ&lt;br&gt;صُورَہ||تُحَف&lt;br&gt;قُبَب&lt;br&gt;صُوَر
|-
|&lt;span style=&quot;font-size:222%&quot;&gt;فُعْلَى فُعْلا&lt;/span&gt;||fem. superl. of اَفْعَلُ||&lt;span style=&quot;font-size:222%&quot;&gt;فُعَل&lt;/span&gt;||||الكُبْرَى&lt;br&gt;العُلْيَا&lt;br&gt;اُخْرَى||الكُبَرُ&lt;br&gt;العُلَى&lt;br&gt;اُخَرُ
|-
|&lt;span style=&quot;font-size:222%&quot;&gt;فَعْلَة&lt;/span&gt;||esp. from verbs of rad و and ي|| &lt;span style=&quot;font-size:222%&quot;&gt;فُعَل&lt;/span&gt;||||قَرْيَہ&lt;br&gt;دَوْلَہ&lt;br&gt;نَوْبَہ||قُرًى&lt;br&gt;دُوَل&lt;br&gt;نُوَب
|-
|&lt;span style=&quot;font-size:222%&quot;&gt;فِعْلَة&lt;/span&gt;||from verbs of rad. و and ي||&lt;span style=&quot;font-size:222%&quot;&gt;فُعَل&lt;/span&gt;||{{yes}}||لِحْيَہ&lt;br&gt;حِلْيَہ&lt;br&gt;||لُحًى&lt;br&gt;حُلًى
|-
|&lt;span style=&quot;font-size:222%&quot;&gt;اَفْعَلُ&lt;/span&gt;||not comparative and superl.||فُعْلٌ||||اَعْمَى&lt;br&gt;اَصَمُّ&lt;br&gt;اَحْدَبُ&lt;br&gt;اَبْيَضُ&lt;br&gt;اَسْوَدُ||عُمْي&lt;br&gt;صُمّ&lt;br&gt;حُدْب&lt;br&gt;بِيْض&lt;ref&gt;for &lt;span style=&quot;font-size:222%&quot;&gt;بُيْض&lt;/span&gt;&lt;/ref&gt;&lt;br&gt;سُود
|-
|&lt;span style=&quot;font-size:222%&quot;&gt;فَعْلَاءُ&lt;/span&gt;||fem. of اَفْعَلُ not comparative and superl.||فُعْل||||صفراءُ&lt;br&gt;عَرجَاءُ&lt;br&gt;بَيْدَاءُ||صُفْر&lt;br&gt;عُرْج&lt;br&gt;بِيد||جَمْعَاءُ كَتْعَاءُ بَصْعَاءُ   بَتْعَاءُ fem. of اَجْمَعُ &amp;c. make جُمَعُ كُتَعُ بُصَعُ بُتَعُ
|-
| فُعَال&lt;br&gt;فِعَال&lt;br&gt;فَعَال||from verbs of rad و and ي||فُعْل||||عَوَان&lt;br&gt;بِوَان&lt;br&gt;خِوَان&lt;br&gt;اُوَار||عُون&lt;br&gt;بُون&lt;br&gt;خُون&lt;br&gt;اُور||These may be contractions from original فُعُل as eg
*سِوَاك has both for pl. سُوك and سُوُك
|-
|فَاعِل||from verbs of rad و and ي||فُعْل||||عَائِذ&lt;br&gt;هَائِد||عُوذ&lt;br&gt;هُود
|-
|فَاعِل||from verbs not of و and ي||فُغْل||{{yes}}||فَارِه&lt;br&gt;بَازِل||فُرْه&lt;br&gt;بُزْل||These may be contractions from فُرُه and بُزُل see also preceding.
|-
|فَعَال&lt;br&gt;فِعَال&lt;br&gt;فُعَال||not from verbs of rad و and ي||فُعُل||||رَدَاح&lt;br&gt;قَذَال&lt;br&gt;كِتَاب&lt;br&gt;فِرَاش&lt;br&gt;سِوَاك&lt;br&gt;قُرَاد||رُدُح&lt;br&gt;قُذُل&lt;br&gt;كُتُب&lt;br&gt;فُرُش&lt;br&gt;سُوُك&lt;br&gt;قُرُد
|-
| فَعِيل&lt;br&gt;فَعِيلَة&lt;br&gt;فَعُول||not from verbs of rad و and ي||فُعُل||||قَضِيب&lt;br&gt;كَثِيب&lt;br&gt;سَرِير&lt;br&gt;سَفِينَة&lt;br&gt;صَحِيفَة&lt;br&gt;عَمُود&lt;br&gt;رَسُول||
|-
| فَعِيل&lt;br&gt;فَعُول||verbal adjectives not having a passive signification and not from verbs of rad و and ي||فُعُل||||نَذِير&lt;br&gt;صَبُور&lt;br&gt;ذَلُول&lt;br&gt;غَيُور&lt;br&gt;بَيُوض
|-
| فَعْل&lt;br&gt;فَعَل&lt;br&gt;فَعَلَة&lt;br&gt;فَعِل&lt;br&gt;فَعُل||||فُعُل||{{yes}}||سَقْف&lt;br&gt;سَحْل&lt;br&gt;اَسَد&lt;br&gt;فَلَك&lt;br&gt;بَدَنَة&lt;br&gt;خَشَبَة&lt;br&gt;اَجَمَة&lt;br&gt;نَمِر&lt;br&gt;خَشِن&lt;br&gt;ضَبُع||سُقُف&lt;br&gt;سُحُل&lt;br&gt;اُسُد&lt;br&gt;فُلُك&lt;br&gt;بُدُن&lt;br&gt;خ&lt;br&gt;اُجُم&lt;br&gt;نُمُر&lt;br&gt;خُشُن&lt;br&gt;ضَبُع
|}


&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;شرط&lt;/span&gt;&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;span style=&quot;font-family: Serif; font-size: 20px; text-shadow: silver 0.2em 0.2em 0.1em;&quot;&gt;[[User:williammacewen#Plurals|&lt;span style=&quot;color=&quot; #954535&quot;&quot;&gt;return to top&lt;/span&gt;]]&lt;/span&gt;&lt;/p&gt;

== Gloss ==
=== nouns ===
&lt;div style=&quot;background: white;{{Text default color}}; border: blue; padding: 2px;&quot;&gt;
{|class=&quot;wikitable sortable&quot; border=&quot;1&quot;
|-
&lt;/div&gt;
! scope=&quot;col&quot; width=&quot;150px&quot; | en
! scope=&quot;col&quot; width=&quot;100px&quot; class=&quot;unsortable&quot; | singular
! scope=&quot;col&quot; width=&quot;100px&quot; class=&quot;unsortable&quot; | plural
|-
|[[w:cat|cat]]
|&lt;p align=&quot;right&quot;&gt;male ~ &lt;span style=&quot;font-size:222%&quot;&gt;هِرّ&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;right&quot;&gt;female ~ &lt;span style=&quot;font-size:222%&quot;&gt;هِرَّة&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;هِرَرَة&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;هِرَر&lt;/span&gt;&lt;/p&gt; 
|-
|[[w:horse|horse]]
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;فَرَس&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;أَفرَاس&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;right&quot;&gt;pl of mult&lt;ref&gt; plural of multitude. An Arabic [[w:grammar|grammatical]] class which is used ''exclusively'' for a [[w:multitude|multitude]] of objects (viz. hundreds, thousands etc., and ''not'' six or seven for which the plural of paucity q.v., is used&lt;/ref&gt; &lt;span style=&quot;font-size:222%&quot;&gt;الخَيل&lt;/span&gt;&lt;/p&gt;
|-
|[[w:husband|husband]]
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;بَعل&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;سَيِّد&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;بُعُولَة&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;سَادَة&lt;/span&gt;&lt;/p&gt;
|-
|that very night &lt;ref&gt;that night&lt;/ref&gt; it carried him to&lt;ref&gt;towards&lt;/ref&gt; the coast of the aforementioned&lt;ref&gt;just now mentioned, just mentioned&lt;/ref&gt; island
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;فاحتَمَلَه مِن لَيلَتِه إلى ساحلِ الجَزِيرَةِ الأُخرَى المتقدّم ذكرها&lt;/span&gt;&lt;/p&gt;
|-
| bag, receptacle, repository
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;وِعَاء&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;أَوعِيَة&lt;/span&gt;&lt;/p&gt; 
|-
| bag, or other receptacle, (S, * Msb, K, TA,) for travelling-provisions, (S, K, TA,) or for dates, made of leather (Msb)
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مِزوَد&lt;/span&gt;&lt;/p&gt;
||&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مَزَاوِدُ&lt;/span&gt;&lt;/p&gt;
|-
| leathern water bag, one of a pair which is borne by a camel or other beast
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مَزَادَةٌ&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مَزَائِدُ&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مَزَاوِدُ&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;right&quot;&gt;good &lt;span style=&quot;font-size:222%&quot;&gt;مَزَايِدُ&lt;/span&gt;&lt;/p&gt;
|-
|age
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;عمر سنوات&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;أَعْمَار&lt;/span&gt;&lt;/p&gt;
|-
|age
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;سنّ سنوات&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;أَسْنَان&lt;/span&gt;&lt;/p&gt;
|-
|[[w:car|car]]
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;عَرَبَة&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;عَرَبَات&lt;/span&gt;&lt;/p&gt;
|-
|[[w:vehicle|car]], vehicle
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مَركَبَة&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مَركَبَات&lt;/span&gt;&lt;/p&gt;
|-
|[[w:car|car]], cart, carriage, wheeled [[w:carriage|carriage]]
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;عَجَلَة&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;coll. generic noun &lt;span style=&quot;font-size:222%&quot;&gt;عَجَل&lt;/span&gt;&lt;/p&gt;&lt;p align=&quot;right&quot;&gt;pl. of pauc. &lt;span style=&quot;font-size:222%&quot;&gt;اَعجَال&lt;/span&gt;&lt;/p&gt;&lt;p align=&quot;right&quot;&gt;pl of multitude &lt;span style=&quot;font-size:222%&quot;&gt;عِجَال&lt;/span&gt;&lt;/p&gt;
|-
|coast, shore, sea-shore, sea-coast, seaboard
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;سَاحِل&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;سَوَاحِلُ&lt;/span&gt;&lt;/p&gt;
|-
|candlestick, lamp, chandelier, lantern
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;قِندِيل&lt;/span&gt;&lt;/p&gt;&lt;p align=&quot;right&quot;&gt;&lt;ref&gt;syn. &lt;span style=&quot;font-size:222%&quot;&gt;مَشعَل&lt;/span&gt;&lt;/ref&gt;&lt;/p&gt;
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;قَندِيل&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;قَنَادِيلُ&lt;/span&gt;&lt;/p&gt;
|-
|lamp, lantern, [[w:torch|torch]], light
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مَشعَل&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مَشَاعِلُ&lt;/span&gt;&lt;/p&gt;
|-
|problem, question, conundrum
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مَسْاَلَة&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;مَسَائِلُ&lt;/span&gt;&lt;/p&gt;
|-
|[[w:artery|artery]], pulsating veins, which spring from the heart 
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;شَِريَان&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;&lt;/span&gt;&lt;/p&gt;
|-
|[[w:mule|mule]] 
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;بَغْل&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;pl. of pauc. &lt;span style=&quot;font-size:222%&quot;&gt;#$#@&lt;/span&gt;&lt;/p&gt;&lt;p align=&quot;right&quot;&gt;pl of multitude &lt;span style=&quot;font-size:222%&quot;&gt;بِغَال&lt;/span&gt;&lt;/p&gt;
|-
|he goat, male goat
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;تَيْسٌ&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;pl. of pauc. &lt;span style=&quot;font-size:222%&quot;&gt;#$#@&lt;/span&gt;&lt;/p&gt;&lt;p align=&quot;right&quot;&gt;pl of multitude &lt;span style=&quot;font-size:222%&quot;&gt;تُيُوس&lt;/span&gt;&lt;/p&gt;
|-
|she goat, female goat
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;عَنْزَة&lt;/span&gt;&lt;/p&gt;
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;عَنْزٌ&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;pl. of pauc. &lt;span style=&quot;font-size:222%&quot;&gt;#$#@&lt;/span&gt;&lt;/p&gt;&lt;p align=&quot;right&quot;&gt;pl of multitude &lt;span style=&quot;font-size:222%&quot;&gt;عِنَازٌ/عُنُوز&lt;/span&gt;&lt;/p&gt;
|-
|}
&lt;/div&gt;
&lt;p align=&quot;center&quot;&gt;&lt;span style=&quot;font-family: Arial Black; font-size: 19px; text-shadow: silver 0.2em 0.2em 0.1em;&quot;&gt;[[User:williammacewen#Gloss|&lt;span style=&quot;color: #954535;&quot;&gt;Return to top&lt;/span&gt;]]&lt;/span&gt;&lt;/p&gt;
&lt;nowiki /&gt;

=== verbs === 
&lt;div style=&quot;background: white;{{Text default color}}; border: blue; padding: 2px;&quot;&gt;
{|class=&quot;wikitable sortable&quot; border=&quot;1&quot;
|-
&lt;/div&gt;
! scope=&quot;col&quot; width=&quot;215px&quot; | en
! scope=&quot;col&quot; width=&quot;190px&quot; class=&quot;unsortable&quot; | past
! scope=&quot;col&quot; width=&quot;110px&quot; class=&quot;unsortable&quot; | present
! scope=&quot;col&quot; width=&quot;110px&quot; class=&quot;unsortable&quot; | infinitive
! scope=&quot;col&quot; width=&quot;110px&quot; class=&quot;unsortable&quot; | 2
! scope=&quot;col&quot; width=&quot;110px&quot; class=&quot;unsortable&quot; | 3
! scope=&quot;col&quot; width=&quot;110px&quot; class=&quot;unsortable&quot; | 6
! scope=&quot;col&quot; width=&quot;110px&quot; class=&quot;unsortable&quot; | 4
! scope=&quot;col&quot; width=&quot;110px&quot; class=&quot;unsortable&quot; | 8
! scope=&quot;col&quot; width=&quot;110px&quot; class=&quot;unsortable&quot; | 10 
! scope=&quot;col&quot; width=&quot;110px&quot; class=&quot;unsortable&quot; | more
|-
|know trns.&lt;ref&gt;[[w:transitive verb|transitive]]&lt;/ref&gt; , he knew it, 
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;دَرَى الشيءَ&lt;/span&gt;&lt;/p&gt;&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;دَرَى به&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;يدرِي&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;دَرْي&lt;/span&gt;&lt;span style=&quot;font-size:222%&quot;&gt;دِريَة&lt;/span&gt;&lt;span style=&quot;font-size:222%&quot;&gt;دِرَايَة&lt;/span&gt;&lt;span style=&quot;font-size:222%&quot;&gt;دَرَيَان&lt;/span&gt;&lt;span style=&quot;font-size:222%&quot;&gt;دُرِيّ&lt;/span&gt;&lt;/p&gt;
|-
|[[w:eating|eat, consume]] trns
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;A&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;U&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;اَكْل&lt;/span&gt;&lt;/p&gt;
|-
|[[w:silence|silence]], he was became silent, mute, speechless&lt;ref&gt;used exclusively for him who has the power or faculty to speak but abstains from making use of it, ie he 'ceased or stopped speaking, he was or became silent intentionally. antonym &lt;span style=&quot;font-size:222%&quot;&gt;نطق&lt;/span&gt; synonym &lt;span style=&quot;font-size:222%&quot;&gt;صمت&lt;/span&gt;&lt;/ref&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;A&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;U&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;سُكُوت&lt;/span&gt;&lt;span style=&quot;font-size:222%&quot;&gt;سُكَات&lt;/span&gt;&lt;/p&gt;
|-
|[[w:bark (sound)|bark]], it (a [[w:dog|dog]]) barked, to bark على ~, at~
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;A&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;I, A&lt;ref&gt;lane says according to Msb. the former is more common, Steingass (and hans wehr) list A first..&lt;/ref&gt;&lt;/span&gt;&lt;/p&gt;
|&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-size:222%&quot;&gt;نَبْح&lt;/span&gt;&lt;span style=&quot;font-size:222%&quot;&gt;نُباح&lt;/span&gt;&lt;span style=&quot;font-size:222%&quot;&gt;نِباح&lt;/span&gt;&lt;span style=&quot;font-size:222%&quot;&gt;نَبِيح&lt;/span&gt;&lt;/p&gt; 
|infin n. &lt;span style=&quot;font-size:222%&quot;&gt;تَنبَاح&lt;/span&gt; (intensive)
|
|to answer each others barks (dogs at night)&lt;br/&gt; 
|4, 10 incite to barking, rouse the dogs (by imitating a bark).
|
|
|&lt;span style=&quot;font-size:222%&quot;&gt;نبّاح&lt;/span&gt; barker yelper
|-
|}
&lt;/div&gt;
&lt;p align=&quot;center&quot;&gt;&lt;span style=&quot;font-family: Arial Black; font-size: 19px; text-shadow: silver 0.2em 0.2em 0.1em;&quot;&gt;[[User:williammacewen#Gloss|&lt;span style=&quot;color: #954535;&quot;&gt;Return to top&lt;/span&gt;]]&lt;/span&gt;&lt;/p&gt;

{| border=&quot;1&quot;
|+
! scope=&quot;col&quot; | &lt;span style=&quot;font-family: Andalus; font-size: 21px; text-shadow: silver 0.2em 0.2em 0.1em;color:#004225&quot;&gt;[[user:williammacewen#Gloss]]&lt;/span&gt;
|}

== Chapter 10 (yunus jonah) of the Koran revealed in mecca ==

=== without diacritics ===
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-family: Arabic Typesetting; font-size: 50px;&quot;&gt;الر تلك آيات الكتاب الحكيم (1) أكان للناس عجبا أن أوحينا إلى رجل منهم أن أنذر الناس وبشر الذين آمنوا أن لهم قدم صدق عند ربهم قال الكافرون إن هذا لساحر مبين (2) إن ربكم الله الذي خلق السماوات والأرض في ستة أيام ثم استوى على العرش يدبر الأمر ما من شفيع إلا من بعد إذنه ذلكم الله ربكم فاعبدوه أفلا تذكرون (3) إليه مرجعكم جميعا وعد الله حقا إنه يبدأ الخلق ثم يعيده ليجزي الذين آمنوا وعملوا الصالحات بالقسط والذين كفروا لهم شراب من حميم وعذاب أليم بما كانوا يكفرون (4) هو الذي جعل الشمس ضياء والقمر نورا وقدره منازل لتعلموا عدد السنين والحساب ما خلق الله ذلك إلا بالحق يفصل الآيات لقوم يعلمون (5) إن في اختلاف الليل والنهار وما خلق الله في السماوات والأرض لآيات لقوم يتقون (6) إن الذين لا يرجون لقاءنا ورضوا بالحياة الدنيا واطمأنوا بها والذين هم عن آياتنا غافلون (7) أولئك مأواهم النار بما كانوا يكسبون (8) إن الذين آمنوا وعملوا الصالحات يهديهم ربهم بإيمانهم تجري من تحتهم الأنهار في جنات النعيم (9) دعواهم فيها سبحانك اللهم وتحيتهم فيها سلام وآخر دعواهم أن الحمد لله رب العالمين (10) ولو يعجل الله للناس الشر استعجالهم بالخير لقضي إليهم أجلهم فنذر الذين لا يرجون لقاءنا في طغيانهم يعمهون (11) وإذا مس الإنسان الضر دعانا لجنبه أو قاعدا أو قائما فلما كشفنا عنه ضره مر كأن لم يدعنا إلى ضر مسه كذلك زين للمسرفين ما كانوا يعملون (12) ولقد أهلكنا القرون من قبلكم لما ظلموا وجاءتهم رسلهم بالبينات وما كانوا ليؤمنوا كذلك نجزي القوم المجرمين (13) ثم جعلناكم خلائف في الأرض من بعدهم لننظر كيف تعملون (14) وإذا تتلى عليهم آياتنا بينات قال الذين لا يرجون لقاءنا ائت بقرآن غير هذا أو بدله قل ما يكون لي أن أبدله من تلقاء نفسي إن أتبع إلا ما يوحى إلي إني أخاف إن عصيت ربي عذاب يوم عظيم (15) قل لو شاء الله ما تلوته عليكم ولا أدراكم به فقد لبثت فيكم عمرا من قبله أفلا تعقلون (16) فمن أظلم ممن افترى على الله كذبا أو كذب بآياته إنه لا يفلح المجرمون (17) ويعبدون من دون الله ما لا يضرهم ولا ينفعهم ويقولون هؤلاء شفعاؤنا عند الله قل أتنبئون الله بما لا يعلم في السماوات ولا في الأرض سبحانه وتعالى عما يشركون (18) وما كان الناس إلا أمة واحدة فاختلفوا ولولا كلمة سبقت من ربك لقضي بينهم فيما فيه يختلفون (19) ويقولون لولا أنزل عليه آية من ربه فقل إنما الغيب لله فانتظروا إني معكم من المنتظرين (20) وإذا أذقنا الناس رحمة من بعد ضراء مستهم إذا لهم مكر في آياتنا قل الله أسرع مكرا إن رسلنا يكتبون ما تمكرون (21) هو الذي يسيركم في البر والبحر حتى إذا كنتم في الفلك وجرين بهم بريح طيبة وفرحوا بها جاءتها ريح عاصف وجاءهم الموج من كل مكان وظنوا أنهم أحيط بهم دعوا الله مخلصين له الدين لئن أنجيتنا من هذه لنكونن من الشاكرين (22) فلما أنجاهم إذا هم يبغون في الأرض بغير الحق يا أيها الناس إنما بغيكم على أنفسكم متاع الحياة الدنيا ثم إلينا مرجعكم فننبئكم بما كنتم تعملون (23) إنما مثل الحياة الدنيا كماء أنزلناه من السماء فاختلط به نبات الأرض مما يأكل الناس والأنعام حتى إذا أخذت الأرض زخرفها وازينت وظن أهلها أنهم قادرون عليها أتاها أمرنا ليلا أو نهارا فجعلناها حصيدا كأن لم تغن بالأمس كذلك نفصل الآيات لقوم يتفكرون (24) والله يدعو إلى دار السلام ويهدي من يشاء إلى صراط مستقيم (25) للذين أحسنوا الحسنى وزيادة ولا يرهق وجوههم قتر ولا ذلة أولئك أصحاب الجنة هم فيها خالدون (26) والذين كسبوا السيئات جزاء سيئة بمثلها وترهقهم ذلة ما لهم من الله من عاصم كأنما أغشيت وجوههم قطعا من الليل مظلما أولئك أصحاب النار هم فيها خالدون (27) ويوم نحشرهم جميعا ثم نقول للذين أشركوا مكانكم أنتم وشركاؤكم فزيلنا بينهم وقال شركاؤهم ما كنتم إيانا تعبدون (28) فكفى بالله شهيدا بيننا وبينكم إن كنا عن عبادتكم لغافلين (29) هنالك تبلو كل نفس ما أسلفت وردوا إلى الله مولاهم الحق وضل عنهم ما كانوا يفترون (30) قل من يرزقكم من السماء والأرض أمن يملك السمع والأبصار ومن يخرج الحي من الميت ويخرج الميت من الحي ومن يدبر الأمر فسيقولون الله فقل أفلا تتقون (31) فذلكم الله ربكم الحق فماذا بعد الحق إلا الضلال فأنى تصرفون (32) كذلك حقت كلمت ربك على الذين فسقوا أنهم لا يؤمنون (33) قل هل من شركائكم من يبدأ الخلق ثم يعيده قل الله يبدأ الخلق ثم يعيده فأنى تؤفكون (34) قل هل من شركائكم من يهدي إلى الحق قل الله يهدي للحق أفمن يهدي إلى الحق أحق أن يتبع أمن لا يهدي إلا أن يهدى فما لكم كيف تحكمون (35) وما يتبع أكثرهم إلا ظنا إن الظن لا يغني من الحق شيئا إن الله عليم بما يفعلون (36) وما كان هذا القرآن أن يفترى من دون الله ولكن تصديق الذي بين يديه وتفصيل الكتاب لا ريب فيه من رب العالمين (37) أم يقولون افتراه قل فأتوا بسورة مثله وادعوا من استطعتم من دون الله إن كنتم صادقين (38) بل كذبوا بما لم يحيطوا بعلمه ولما يأتهم تأويله كذلك كذب الذين من قبلهم فانظر كيف كان عاقبة الظالمين (39) ومنهم من يؤمن به ومنهم من لا يؤمن به وربك أعلم بالمفسدين (40) وإن كذبوك فقل لي عملي ولكم عملكم أنتم بريئون مما أعمل وأنا بريء مما تعملون (41) ومنهم من يستمعون إليك أفأنت تسمع الصم ولو كانوا لا يعقلون (42) ومنهم من ينظر إليك أفأنت تهدي العمي ولو كانوا لا يبصرون (43) إن الله لا يظلم الناس شيئا ولكن الناس أنفسهم يظلمون (44) ويوم يحشرهم كأن لم يلبثوا إلا ساعة من النهار يتعارفون بينهم قد خسر الذين كذبوا بلقاء الله وما كانوا مهتدين (45) وإما نرينك بعض الذي نعدهم أو نتوفينك فإلينا مرجعهم ثم الله شهيد على ما يفعلون (46) ولكل أمة رسول فإذا جاء رسولهم قضي بينهم بالقسط وهم لا يظلمون (47) ويقولون متى هذا الوعد إن كنتم صادقين (48) قل لا أملك لنفسي ضرا ولا نفعا إلا ما شاء الله لكل أمة أجل إذا جاء أجلهم فلا يستأخرون ساعة ولا يستقدمون (49) قل أرأيتم إن أتاكم عذابه بياتا أو نهارا ماذا يستعجل منه المجرمون (50) أثم إذا ما وقع آمنتم به آلآن وقد كنتم به تستعجلون (51) ثم قيل للذين ظلموا ذوقوا عذاب الخلد هل تجزون إلا بما كنتم تكسبون (52) ويستنبئونك أحق هو قل إي وربي إنه لحق وما أنتم بمعجزين (53) ولو أن لكل نفس ظلمت ما في الأرض لافتدت به وأسروا الندامة لما رأوا العذاب وقضي بينهم بالقسط وهم لا يظلمون (54) ألا إن لله ما في السماوات والأرض ألا إن وعد الله حق ولكن أكثرهم لا يعلمون (55) هو يحيي ويميت وإليه ترجعون (56) يا أيها الناس قد جاءتكم موعظة من ربكم وشفاء لما في الصدور وهدى ورحمة للمؤمنين (57) قل بفضل الله وبرحمته فبذلك فليفرحوا هو خير مما يجمعون (58) قل أرأيتم ما أنزل الله لكم من رزق فجعلتم منه حراما وحلالا قل آلله أذن لكم أم على الله تفترون (59) وما ظن الذين يفترون على الله الكذب يوم القيامة إن الله لذو فضل على الناس ولكن أكثرهم لا يشكرون (60) وما تكون في شأن وما تتلو منه من قرآن ولا تعملون من عمل إلا كنا عليكم شهودا إذ تفيضون فيه وما يعزب عن ربك من مثقال ذرة في الأرض ولا في السماء ولا أصغر من ذلك ولا أكبر إلا في كتاب مبين (61) ألا إن أولياء الله لا خوف عليهم ولا هم يحزنون (62) الذين آمنوا وكانوا يتقون (63) لهم البشرى في الحياة الدنيا وفي الآخرة لا تبديل لكلمات الله ذلك هو الفوز العظيم (64) ولا يحزنك قولهم إن العزة لله جميعا هو السميع العليم (65) ألا إن لله من في السماوات ومن في الأرض وما يتبع الذين يدعون من دون الله شركاء إن يتبعون إلا الظن وإن هم إلا يخرصون (66) هو الذي جعل لكم الليل لتسكنوا فيه والنهار مبصرا إن في ذلك لآيات لقوم يسمعون (67) قالوا اتخذ الله ولدا سبحانه هو الغني له ما في السماوات وما في الأرض إن عندكم من سلطان بهذا أتقولون على الله ما لا تعلمون (68) قل إن الذين يفترون على الله الكذب لا يفلحون (69) متاع في الدنيا ثم إلينا مرجعهم ثم نذيقهم العذاب الشديد بما كانوا يكفرون (70) واتل عليهم نبأ نوح إذ قال لقومه يا قوم إن كان كبر عليكم مقامي وتذكيري بآيات الله فعلى الله توكلت فأجمعوا أمركم وشركاءكم ثم لا يكن أمركم عليكم غمة ثم اقضوا إلي ولا تنظرون (71) فإن توليتم فما سألتكم من أجر إن أجري إلا على الله وأمرت أن أكون من المسلمين (72) فكذبوه فنجيناه ومن معه في الفلك وجعلناهم خلائف وأغرقنا الذين كذبوا بآياتنا فانظر كيف كان عاقبة المنذرين (73) ثم بعثنا من بعده رسلا إلى قومهم فجاءوهم بالبينات فما كانوا ليؤمنوا بما كذبوا به من قبل كذلك نطبع على قلوب المعتدين (74) ثم بعثنا من بعدهم موسى وهارون إلى فرعون وملئه بآياتنا فاستكبروا وكانوا قوما مجرمين (75) فلما جاءهم الحق من عندنا قالوا إن هذا لسحر مبين (76) قال موسى أتقولون للحق لما جاءكم أسحر هذا ولا يفلح الساحرون (77) قالوا أجئتنا لتلفتنا عما وجدنا عليه آباءنا وتكون لكما الكبرياء في الأرض وما نحن لكما بمؤمنين (78) وقال فرعون ائتوني بكل ساحر عليم (79) فلما جاء السحرة قال لهم موسى ألقوا ما أنتم ملقون (80) فلما ألقوا قال موسى ما جئتم به السحر إن الله سيبطله إن الله لا يصلح عمل المفسدين (81) ويحق الله الحق بكلماته ولو كره المجرمون (82) فما آمن لموسى إلا ذرية من قومه على خوف من فرعون وملئهم أن يفتنهم وإن فرعون لعال في الأرض وإنه لمن المسرفين (83) وقال موسى يا قوم إن كنتم آمنتم بالله فعليه توكلوا إن كنتم مسلمين (84) فقالوا على الله توكلنا ربنا لا تجعلنا فتنة للقوم الظالمين (85) ونجنا برحمتك من القوم الكافرين (86) وأوحينا إلى موسى وأخيه أن تبوآ لقومكما بمصر بيوتا واجعلوا بيوتكم قبلة وأقيموا الصلاة وبشر المؤمنين (87) وقال موسى ربنا إنك آتيت فرعون وملأه زينة وأموالا في الحياة الدنيا ربنا ليضلوا عن سبيلك ربنا اطمس على أموالهم واشدد على قلوبهم فلا يؤمنوا حتى يروا العذاب الأليم (88) قال قد أجيبت دعوتكما فاستقيما ولا تتبعان سبيل الذين لا يعلمون (89) وجاوزنا ببني إسرائيل البحر فأتبعهم فرعون وجنوده بغيا وعدوا حتى إذا أدركه الغرق قال آمنت أنه لا إله إلا الذي آمنت به بنو إسرائيل وأنا من المسلمين (90) آلآن وقد عصيت قبل وكنت من المفسدين (91) فاليوم ننجيك ببدنك لتكون لمن خلفك آية وإن كثيرا من الناس عن آياتنا لغافلون (92) ولقد بوأنا بني إسرائيل مبوأ صدق ورزقناهم من الطيبات فما اختلفوا حتى جاءهم العلم إن ربك يقضي بينهم يوم القيامة فيما كانوا فيه يختلفون (93) فإن كنت في شك مما أنزلنا إليك فاسأل الذين يقرءون الكتاب من قبلك لقد جاءك الحق من ربك فلا تكونن من الممترين (94) ولا تكونن من الذين كذبوا بآيات الله فتكون من الخاسرين (95) إن الذين حقت عليهم كلمت ربك لا يؤمنون (96) ولو جاءتهم كل آية حتى يروا العذاب الأليم (97) فلولا كانت قرية آمنت فنفعها إيمانها إلا قوم يونس لما آمنوا كشفنا عنهم عذاب الخزي في الحياة الدنيا ومتعناهم إلى حين (98) ولو شاء ربك لآمن من في الأرض كلهم جميعا أفأنت تكره الناس حتى يكونوا مؤمنين (99) وما كان لنفس أن تؤمن إلا بإذن الله ويجعل الرجس على الذين لا يعقلون (100) قل انظروا ماذا في السماوات والأرض وما تغني الآيات والنذر عن قوم لا يؤمنون (101) فهل ينتظرون إلا مثل أيام الذين خلوا من قبلهم قل فانتظروا إني معكم من المنتظرين (102) ثم ننجي رسلنا والذين آمنوا كذلك حقا علينا ننج المؤمنين (103) قل يا أيها الناس إن كنتم في شك من ديني فلا أعبد الذين تعبدون من دون الله ولكن أعبد الله الذي يتوفاكم وأمرت أن أكون من المؤمنين (104) وأن أقم وجهك للدين حنيفا ولا تكونن من المشركين (105) ولا تدع من دون الله ما لا ينفعك ولا يضرك فإن فعلت فإنك إذا من الظالمين (106) وإن يمسسك الله بضر فلا كاشف له إلا هو وإن يردك بخير فلا راد لفضله يصيب به من يشاء من عباده وهو الغفور الرحيم (107) قل يا أيها الناس قد جاءكم الحق من ربكم فمن اهتدى فإنما يهتدي لنفسه ومن ضل فإنما يضل عليها وما أنا عليكم بوكيل (108) واتبع ما يوحى إليك واصبر حتى يحكم الله وهو خير الحاكمين (109&lt;/span&gt;&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;span style=&quot;font-family: Serif; font-size: 20px; text-shadow: silver 0.2em 0.2em 0.1em;&quot;&gt;[[User:williammacewen#without diacritics|&lt;span style=&quot;color=&quot; #954535&quot;&quot;&gt;return to top&lt;/span&gt;]]&lt;/span&gt;&lt;/p&gt;

=== with diacritics ===
&lt;p align=&quot;right&quot;&gt;&lt;span style=&quot;font-family: Arabic Typesetting; font-size: 50px;&quot;&gt;الر تِلْكَ آيَاتُ الْكِتَابِ الْحَكِيمِ (1) أَكَانَ لِلنَّاسِ عَجَبًا أَنْ أَوْحَيْنَا إِلَى رَجُلٍ مِنْهُمْ أَنْ أَنْذِرِ النَّاسَ وَبَشِّرِ الَّذِينَ آمَنُوا أَنَّ لَهُمْ قَدَمَ صِدْقٍ عِنْدَ رَبِّهِمْ قَالَ الْكَافِرُونَ إِنَّ هَذَا لَسَاحِرٌ مُبِينٌ (2) إِنَّ رَبَّكُمُ اللَّهُ الَّذِي خَلَقَ السَّمَاوَاتِ وَالْأَرْضَ فِي سِتَّةِ أَيَّامٍ ثُمَّ اسْتَوَى عَلَى الْعَرْشِ يُدَبِّرُ الْأَمْرَ مَا مِنْ شَفِيعٍ إِلَّا مِنْ بَعْدِ إِذْنِهِ ذَلِكُمُ اللَّهُ رَبُّكُمْ فَاعْبُدُوهُ أَفَلَا تَذَكَّرُونَ (3) إِلَيْهِ مَرْجِعُكُمْ جَمِيعًا وَعْدَ اللَّهِ حَقًّا إِنَّهُ يَبْدَأُ الْخَلْقَ ثُمَّ يُعِيدُهُ لِيَجْزِيَ الَّذِينَ آمَنُوا وَعَمِلُوا الصَّالِحَاتِ بِالْقِسْطِ وَالَّذِينَ كَفَرُوا لَهُمْ شَرَابٌ مِنْ حَمِيمٍ وَعَذَابٌ أَلِيمٌ بِمَا كَانُوا يَكْفُرُونَ (4) هُوَ الَّذِي جَعَلَ الشَّمْسَ ضِيَاءً وَالْقَمَرَ نُورًا وَقَدَّرَهُ مَنَازِلَ لِتَعْلَمُوا عَدَدَ السِّنِينَ وَالْحِسَابَ مَا خَلَقَ اللَّهُ ذَلِكَ إِلَّا بِالْحَقِّ يُفَصِّلُ الْآيَاتِ لِقَوْمٍ يَعْلَمُونَ (5) إِنَّ فِي اخْتِلَافِ اللَّيْلِ وَالنَّهَارِ وَمَا خَلَقَ اللَّهُ فِي السَّمَاوَاتِ وَالْأَرْضِ لَآيَاتٍ لِقَوْمٍ يَتَّقُونَ (6) إِنَّ الَّذِينَ لَا يَرْجُونَ لِقَاءَنَا وَرَضُوا بِالْحَيَاةِ الدُّنْيَا وَاطْمَأَنُّوا بِهَا وَالَّذِينَ هُمْ عَنْ آيَاتِنَا غَافِلُونَ (7) أُولَئِكَ مَأْوَاهُمُ النَّارُ بِمَا كَانُوا يَكْسِبُونَ (8) إِنَّ الَّذِينَ آمَنُوا وَعَمِلُوا الصَّالِحَاتِ يَهْدِيهِمْ رَبُّهُمْ بِإِيمَانِهِمْ تَجْرِي مِنْ تَحْتِهِمُ الْأَنْهَارُ فِي جَنَّاتِ النَّعِيمِ (9) دَعْوَاهُمْ فِيهَا سُبْحَانَكَ اللَّهُمَّ وَتَحِيَّتُهُمْ فِيهَا سَلَامٌ وَآخِرُ دَعْوَاهُمْ أَنِ الْحَمْدُ لِلَّهِ رَبِّ الْعَالَمِينَ (10) وَلَوْ يُعَجِّلُ اللَّهُ لِلنَّاسِ الشَّرَّ اسْتِعْجَالَهُمْ بِالْخَيْرِ لَقُضِيَ إِلَيْهِمْ أَجَلُهُمْ فَنَذَرُ الَّذِينَ لَا يَرْجُونَ لِقَاءَنَا فِي طُغْيَانِهِمْ يَعْمَهُونَ (11) وَإِذَا مَسَّ الْإِنْسَانَ الضُّرُّ دَعَانَا لِجَنْبِهِ أَوْ قَاعِدًا أَوْ قَائِمًا فَلَمَّا كَشَفْنَا عَنْهُ ضُرَّهُ مَرَّ كَأَنْ لَمْ يَدْعُنَا إِلَى ضُرٍّ مَسَّهُ كَذَلِكَ زُيِّنَ لِلْمُسْرِفِينَ مَا كَانُوا يَعْمَلُونَ (12) وَلَقَدْ أَهْلَكْنَا الْقُرُونَ مِنْ قَبْلِكُمْ لَمَّا ظَلَمُوا وَجَاءَتْهُمْ رُسُلُهُمْ بِالْبَيِّنَاتِ وَمَا كَانُوا لِيُؤْمِنُوا كَذَلِكَ نَجْزِي الْقَوْمَ الْمُجْرِمِينَ (13) ثُمَّ جَعَلْنَاكُمْ خَلَائِفَ فِي الْأَرْضِ مِنْ بَعْدِهِمْ لِنَنْظُرَ كَيْفَ تَعْمَلُونَ (14) وَإِذَا تُتْلَى عَلَيْهِمْ آيَاتُنَا بَيِّنَاتٍ قَالَ الَّذِينَ لَا يَرْجُونَ لِقَاءَنَا ائْتِ بِقُرْآنٍ غَيْرِ هَذَا أَوْ بَدِّلْهُ قُلْ مَا يَكُونُ لِي أَنْ أُبَدِّلَهُ مِنْ تِلْقَاءِ نَفْسِي إِنْ أَتَّبِعُ إِلَّا مَا يُوحَى إِلَيَّ إِنِّي أَخَافُ إِنْ عَصَيْتُ رَبِّي عَذَابَ يَوْمٍ عَظِيمٍ (15) قُلْ لَوْ شَاءَ اللَّهُ مَا تَلَوْتُهُ عَلَيْكُمْ وَلَا أَدْرَاكُمْ بِهِ فَقَدْ لَبِثْتُ فِيكُمْ عُمُرًا مِنْ قَبْلِهِ أَفَلَا تَعْقِلُونَ (16) فَمَنْ أَظْلَمُ مِمَّنِ افْتَرَى عَلَى اللَّهِ كَذِبًا أَوْ كَذَّبَ بِآيَاتِهِ إِنَّهُ لَا يُفْلِحُ الْمُجْرِمُونَ (17) وَيَعْبُدُونَ مِنْ دُونِ اللَّهِ مَا لَا يَضُرُّهُمْ وَلَا يَنْفَعُهُمْ وَيَقُولُونَ هَؤُلَاءِ شُفَعَاؤُنَا عِنْدَ اللَّهِ قُلْ أَتُنَبِّئُونَ اللَّهَ بِمَا لَا يَعْلَمُ فِي السَّمَاوَاتِ وَلَا فِي الْأَرْضِ سُبْحَانَهُ وَتَعَالَى عَمَّا يُشْرِكُونَ (18) وَمَا كَانَ النَّاسُ إِلَّا أُمَّةً وَاحِدَةً فَاخْتَلَفُوا وَلَوْلَا كَلِمَةٌ سَبَقَتْ مِنْ رَبِّكَ لَقُضِيَ بَيْنَهُمْ فِيمَا فِيهِ يَخْتَلِفُونَ (19) وَيَقُولُونَ لَوْلَا أُنْزِلَ عَلَيْهِ آيَةٌ مِنْ رَبِّهِ فَقُلْ إِنَّمَا الْغَيْبُ لِلَّهِ فَانْتَظِرُوا إِنِّي مَعَكُمْ مِنَ الْمُنْتَظِرِينَ (20) وَإِذَا أَذَقْنَا النَّاسَ رَحْمَةً مِنْ بَعْدِ ضَرَّاءَ مَسَّتْهُمْ إِذَا لَهُمْ مَكْرٌ فِي آيَاتِنَا قُلِ اللَّهُ أَسْرَعُ مَكْرًا إِنَّ رُسُلَنَا يَكْتُبُونَ مَا تَمْكُرُونَ (21) هُوَ الَّذِي يُسَيِّرُكُمْ فِي الْبَرِّ وَالْبَحْرِ حَتَّى إِذَا كُنْتُمْ فِي الْفُلْكِ وَجَرَيْنَ بِهِمْ بِرِيحٍ طَيِّبَةٍ وَفَرِحُوا بِهَا جَاءَتْهَا رِيحٌ عَاصِفٌ وَجَاءَهُمُ الْمَوْجُ مِنْ كُلِّ مَكَانٍ وَظَنُّوا أَنَّهُمْ أُحِيطَ بِهِمْ دَعَوُا اللَّهَ مُخْلِصِينَ لَهُ الدِّينَ لَئِنْ أَنْجَيْتَنَا مِنْ هَذِهِ لَنَكُونَنَّ مِنَ الشَّاكِرِينَ (22) فَلَمَّا أَنْجَاهُمْ إِذَا هُمْ يَبْغُونَ فِي الْأَرْضِ بِغَيْرِ الْحَقِّ يَا أَيُّهَا النَّاسُ إِنَّمَا بَغْيُكُمْ عَلَى أَنْفُسِكُمْ مَتَاعَ الْحَيَاةِ الدُّنْيَا ثُمَّ إِلَيْنَا مَرْجِعُكُمْ فَنُنَبِّئُكُمْ بِمَا كُنْتُمْ تَعْمَلُونَ (23) إِنَّمَا مَثَلُ الْحَيَاةِ الدُّنْيَا كَمَاءٍ أَنْزَلْنَاهُ مِنَ السَّمَاءِ فَاخْتَلَطَ بِهِ نَبَاتُ الْأَرْضِ مِمَّا يَأْكُلُ النَّاسُ وَالْأَنْعَامُ حَتَّى إِذَا أَخَذَتِ الْأَرْضُ زُخْرُفَهَا وَازَّيَّنَتْ وَظَنَّ أَهْلُهَا أَنَّهُمْ قَادِرُونَ عَلَيْهَا أَتَاهَا أَمْرُنَا لَيْلًا أَوْ نَهَارًا فَجَعَلْنَاهَا حَصِيدًا كَأَنْ لَمْ تَغْنَ بِالْأَمْسِ كَذَلِكَ نُفَصِّلُ الْآيَاتِ لِقَوْمٍ يَتَفَكَّرُونَ (24) وَاللَّهُ يَدْعُو إِلَى دَارِ السَّلَامِ وَيَهْدِي مَنْ يَشَاءُ إِلَى صِرَاطٍ مُسْتَقِيمٍ (25) لِلَّذِينَ أَحْسَنُوا الْحُسْنَى وَزِيَادَةٌ وَلَا يَرْهَقُ وُجُوهَهُمْ قَتَرٌ وَلَا ذِلَّةٌ أُولَئِكَ أَصْحَابُ الْجَنَّةِ هُمْ فِيهَا خَالِدُونَ (26) وَالَّذِينَ كَسَبُوا السَّيِّئَاتِ جَزَاءُ سَيِّئَةٍ بِمِثْلِهَا وَتَرْهَقُهُمْ ذِلَّةٌ مَا لَهُمْ مِنَ اللَّهِ مِنْ عَاصِمٍ كَأَنَّمَا أُغْشِيَتْ وُجُوهُهُمْ قِطَعًا مِنَ اللَّيْلِ مُظْلِمًا أُولَئِكَ أَصْحَابُ النَّارِ هُمْ فِيهَا خَالِدُونَ (27) وَيَوْمَ نَحْشُرُهُمْ جَمِيعًا ثُمَّ نَقُولُ لِلَّذِينَ أَشْرَكُوا مَكَانَكُمْ أَنْتُمْ وَشُرَكَاؤُكُمْ فَزَيَّلْنَا بَيْنَهُمْ وَقَالَ شُرَكَاؤُهُمْ مَا كُنْتُمْ إِيَّانَا تَعْبُدُونَ (28) فَكَفَى بِاللَّهِ شَهِيدًا بَيْنَنَا وَبَيْنَكُمْ إِنْ كُنَّا عَنْ عِبَادَتِكُمْ لَغَافِلِينَ (29) هُنَالِكَ تَبْلُو كُلُّ نَفْسٍ مَا أَسْلَفَتْ وَرُدُّوا إِلَى اللَّهِ مَوْلَاهُمُ الْحَقِّ وَضَلَّ عَنْهُمْ مَا كَانُوا يَفْتَرُونَ (30) قُلْ مَنْ يَرْزُقُكُمْ مِنَ السَّمَاءِ وَالْأَرْضِ أَمَّنْ يَمْلِكُ السَّمْعَ وَالْأَبْصَارَ وَمَنْ يُخْرِجُ الْحَيَّ مِنَ الْمَيِّتِ وَيُخْرِجُ الْمَيِّتَ مِنَ الْحَيِّ وَمَنْ يُدَبِّرُ الْأَمْرَ فَسَيَقُولُونَ اللَّهُ فَقُلْ أَفَلَا تَتَّقُونَ (31) فَذَلِكُمُ اللَّهُ رَبُّكُمُ الْحَقُّ فَمَاذَا بَعْدَ الْحَقِّ إِلَّا الضَّلَالُ فَأَنَّى تُصْرَفُونَ (32) كَذَلِكَ حَقَّتْ كَلِمَتُ رَبِّكَ عَلَى الَّذِينَ فَسَقُوا أَنَّهُمْ لَا يُؤْمِنُونَ (33) قُلْ هَلْ مِنْ شُرَكَائِكُمْ مَنْ يَبْدَأُ الْخَلْقَ ثُمَّ يُعِيدُهُ قُلِ اللَّهُ يَبْدَأُ الْخَلْقَ ثُمَّ يُعِيدُهُ فَأَنَّى تُؤْفَكُونَ (34) قُلْ هَلْ مِنْ شُرَكَائِكُمْ مَنْ يَهْدِي إِلَى الْحَقِّ قُلِ اللَّهُ يَهْدِي لِلْحَقِّ أَفَمَنْ يَهْدِي إِلَى الْحَقِّ أَحَقُّ أَنْ يُتَّبَعَ أَمَّنْ لَا يَهِدِّي إِلَّا أَنْ يُهْدَى فَمَا لَكُمْ كَيْفَ تَحْكُمُونَ (35) وَمَا يَتَّبِعُ أَكْثَرُهُمْ إِلَّا ظَنًّا إِنَّ الظَّنَّ لَا يُغْنِي مِنَ الْحَقِّ شَيْئًا إِنَّ اللَّهَ عَلِيمٌ بِمَا يَفْعَلُونَ (36) وَمَا كَانَ هَذَا الْقُرْآنُ أَنْ يُفْتَرَى مِنْ دُونِ اللَّهِ وَلَكِنْ تَصْدِيقَ الَّذِي بَيْنَ يَدَيْهِ وَتَفْصِيلَ الْكِتَابِ لَا رَيْبَ فِيهِ مِنْ رَبِّ الْعَالَمِينَ (37) أَمْ يَقُولُونَ افْتَرَاهُ قُلْ فَأْتُوا بِسُورَةٍ مِثْلِهِ وَادْعُوا مَنِ اسْتَطَعْتُمْ مِنْ دُونِ اللَّهِ إِنْ كُنْتُمْ صَادِقِينَ (38) بَلْ كَذَّبُوا بِمَا لَمْ يُحِيطُوا بِعِلْمِهِ وَلَمَّا يَأْتِهِمْ تَأْوِيلُهُ كَذَلِكَ كَذَّبَ الَّذِينَ مِنْ قَبْلِهِمْ فَانْظُرْ كَيْفَ كَانَ عَاقِبَةُ الظَّالِمِينَ (39) وَمِنْهُمْ مَنْ يُؤْمِنُ بِهِ وَمِنْهُمْ مَنْ لَا يُؤْمِنُ بِهِ وَرَبُّكَ أَعْلَمُ بِالْمُفْسِدِينَ (40) وَإِنْ كَذَّبُوكَ فَقُلْ لِي عَمَلِي وَلَكُمْ عَمَلُكُمْ أَنْتُمْ بَرِيئُونَ مِمَّا أَعْمَلُ وَأَنَا بَرِيءٌ مِمَّا تَعْمَلُونَ (41) وَمِنْهُمْ مَنْ يَسْتَمِعُونَ إِلَيْكَ أَفَأَنْتَ تُسْمِعُ الصُّمَّ وَلَوْ كَانُوا لَا يَعْقِلُونَ (42) وَمِنْهُمْ مَنْ يَنْظُرُ إِلَيْكَ أَفَأَنْتَ تَهْدِي الْعُمْيَ وَلَوْ كَانُوا لَا يُبْصِرُونَ (43) إِنَّ اللَّهَ لَا يَظْلِمُ النَّاسَ شَيْئًا وَلَكِنَّ النَّاسَ أَنْفُسَهُمْ يَظْلِمُونَ (44) وَيَوْمَ يَحْشُرُهُمْ كَأَنْ لَمْ يَلْبَثُوا إِلَّا سَاعَةً مِنَ النَّهَارِ يَتَعَارَفُونَ بَيْنَهُمْ قَدْ خَسِرَ الَّذِينَ كَذَّبُوا بِلِقَاءِ اللَّهِ وَمَا كَانُوا مُهْتَدِينَ (45) وَإِمَّا نُرِيَنَّكَ بَعْضَ الَّذِي نَعِدُهُمْ أَوْ نَتَوَفَّيَنَّكَ فَإِلَيْنَا مَرْجِعُهُمْ ثُمَّ اللَّهُ شَهِيدٌ عَلَى مَا يَفْعَلُونَ (46) وَلِكُلِّ أُمَّةٍ رَسُولٌ فَإِذَا جَاءَ رَسُولُهُمْ قُضِيَ بَيْنَهُمْ بِالْقِسْطِ وَهُمْ لَا يُظْلَمُونَ (47) وَيَقُولُونَ مَتَى هَذَا الْوَعْدُ إِنْ كُنْتُمْ صَادِقِينَ (48) قُلْ لَا أَمْلِكُ لِنَفْسِي ضَرًّا وَلَا نَفْعًا إِلَّا مَا شَاءَ اللَّهُ لِكُلِّ أُمَّةٍ أَجَلٌ إِذَا جَاءَ أَجَلُهُمْ فَلَا يَسْتَأْخِرُونَ سَاعَةً وَلَا يَسْتَقْدِمُونَ (49) قُلْ أَرَأَيْتُمْ إِنْ أَتَاكُمْ عَذَابُهُ بَيَاتًا أَوْ نَهَارًا مَاذَا يَسْتَعْجِلُ مِنْهُ الْمُجْرِمُونَ (50) أَثُمَّ إِذَا مَا وَقَعَ آمَنْتُمْ بِهِ آلْآنَ وَقَدْ كُنْتُمْ بِهِ تَسْتَعْجِلُونَ (51) ثُمَّ قِيلَ لِلَّذِينَ ظَلَمُوا ذُوقُوا عَذَابَ الْخُلْدِ هَلْ تُجْزَوْنَ إِلَّا بِمَا كُنْتُمْ تَكْسِبُونَ (52) وَيَسْتَنْبِئُونَكَ أَحَقٌّ هُوَ قُلْ إِي وَرَبِّي إِنَّهُ لَحَقٌّ وَمَا أَنْتُمْ بِمُعْجِزِينَ (53) وَلَوْ أَنَّ لِكُلِّ نَفْسٍ ظَلَمَتْ مَا فِي الْأَرْضِ لَافْتَدَتْ بِهِ وَأَسَرُّوا النَّدَامَةَ لَمَّا رَأَوُا الْعَذَابَ وَقُضِيَ بَيْنَهُمْ بِالْقِسْطِ وَهُمْ لَا يُظْلَمُونَ (54) أَلَا إِنَّ لِلَّهِ مَا فِي السَّمَاوَاتِ وَالْأَرْضِ أَلَا إِنَّ وَعْدَ اللَّهِ حَقٌّ وَلَكِنَّ أَكْثَرَهُمْ لَا يَعْلَمُونَ (55) هُوَ يُحْيِي وَيُمِيتُ وَإِلَيْهِ تُرْجَعُونَ (56) يَا أَيُّهَا النَّاسُ قَدْ جَاءَتْكُمْ مَوْعِظَةٌ مِنْ رَبِّكُمْ وَشِفَاءٌ لِمَا فِي الصُّدُورِ وَهُدًى وَرَحْمَةٌ لِلْمُؤْمِنِينَ (57) قُلْ بِفَضْلِ اللَّهِ وَبِرَحْمَتِهِ فَبِذَلِكَ فَلْيَفْرَحُوا هُوَ خَيْرٌ مِمَّا يَجْمَعُونَ (58) قُلْ أَرَأَيْتُمْ مَا أَنْزَلَ اللَّهُ لَكُمْ مِنْ رِزْقٍ فَجَعَلْتُمْ مِنْهُ حَرَامًا وَحَلَالًا قُلْ آللَّهُ أَذِنَ لَكُمْ أَمْ عَلَى اللَّهِ تَفْتَرُونَ (59) وَمَا ظَنُّ الَّذِينَ يَفْتَرُونَ عَلَى اللَّهِ الْكَذِبَ يَوْمَ الْقِيَامَةِ إِنَّ اللَّهَ لَذُو فَضْلٍ عَلَى النَّاسِ وَلَكِنَّ أَكْثَرَهُمْ لَا يَشْكُرُونَ (60) وَمَا تَكُونُ فِي شَأْنٍ وَمَا تَتْلُو مِنْهُ مِنْ قُرْآنٍ وَلَا تَعْمَلُونَ مِنْ عَمَلٍ إِلَّا كُنَّا عَلَيْكُمْ شُهُودًا إِذْ تُفِيضُونَ فِيهِ وَمَا يَعْزُبُ عَنْ رَبِّكَ مِنْ مِثْقَالِ ذَرَّةٍ فِي الْأَرْضِ وَلَا فِي السَّمَاءِ وَلَا أَصْغَرَ مِنْ ذَلِكَ وَلَا أَكْبَرَ إِلَّا فِي كِتَابٍ مُبِينٍ (61) أَلَا إِنَّ أَوْلِيَاءَ اللَّهِ لَا خَوْفٌ عَلَيْهِمْ وَلَا هُمْ يَحْزَنُونَ (62) الَّذِينَ آمَنُوا وَكَانُوا يَتَّقُونَ (63) لَهُمُ الْبُشْرَى فِي الْحَيَاةِ الدُّنْيَا وَفِي الْآخِرَةِ لَا تَبْدِيلَ لِكَلِمَاتِ اللَّهِ ذَلِكَ هُوَ الْفَوْزُ الْعَظِيمُ (64) وَلَا يَحْزُنْكَ قَوْلُهُمْ إِنَّ الْعِزَّةَ لِلَّهِ جَمِيعًا هُوَ السَّمِيعُ الْعَلِيمُ (65) أَلَا إِنَّ لِلَّهِ مَنْ فِي السَّمَاوَاتِ وَمَنْ فِي الْأَرْضِ وَمَا يَتَّبِعُ الَّذِينَ يَدْعُونَ مِنْ دُونِ اللَّهِ شُرَكَاءَ إِنْ يَتَّبِعُونَ إِلَّا الظَّنَّ وَإِنْ هُمْ إِلَّا يَخْرُصُونَ (66) هُوَ الَّذِي جَعَلَ لَكُمُ اللَّيْلَ لِتَسْكُنُوا فِيهِ وَالنَّهَارَ مُبْصِرًا إِنَّ فِي ذَلِكَ لَآيَاتٍ لِقَوْمٍ يَسْمَعُونَ (67) قَالُوا اتَّخَذَ اللَّهُ وَلَدًا سُبْحَانَهُ هُوَ الْغَنِيُّ لَهُ مَا فِي السَّمَاوَاتِ وَمَا فِي الْأَرْضِ إِنْ عِنْدَكُمْ مِنْ سُلْطَانٍ بِهَذَا أَتَقُولُونَ عَلَى اللَّهِ مَا لَا تَعْلَمُونَ (68) قُلْ إِنَّ الَّذِينَ يَفْتَرُونَ عَلَى اللَّهِ الْكَذِبَ لَا يُفْلِحُونَ (69) مَتَاعٌ فِي الدُّنْيَا ثُمَّ إِلَيْنَا مَرْجِعُهُمْ ثُمَّ نُذِيقُهُمُ الْعَذَابَ الشَّدِيدَ بِمَا كَانُوا يَكْفُرُونَ (70) وَاتْلُ عَلَيْهِمْ نَبَأَ نُوحٍ إِذْ قَالَ لِقَوْمِهِ يَا قَوْمِ إِنْ كَانَ كَبُرَ عَلَيْكُمْ مَقَامِي وَتَذْكِيرِي بِآيَاتِ اللَّهِ فَعَلَى اللَّهِ تَوَكَّلْتُ فَأَجْمِعُوا أَمْرَكُمْ وَشُرَكَاءَكُمْ ثُمَّ لَا يَكُنْ أَمْرُكُمْ عَلَيْكُمْ غُمَّةً ثُمَّ اقْضُوا إِلَيَّ وَلَا تُنْظِرُونِ (71) فَإِنْ تَوَلَّيْتُمْ فَمَا سَأَلْتُكُمْ مِنْ أَجْرٍ إِنْ أَجْرِيَ إِلَّا عَلَى اللَّهِ وَأُمِرْتُ أَنْ أَكُونَ مِنَ الْمُسْلِمِينَ (72) فَكَذَّبُوهُ فَنَجَّيْنَاهُ وَمَنْ مَعَهُ فِي الْفُلْكِ وَجَعَلْنَاهُمْ خَلَائِفَ وَأَغْرَقْنَا الَّذِينَ كَذَّبُوا بِآيَاتِنَا فَانْظُرْ كَيْفَ كَانَ عَاقِبَةُ الْمُنْذَرِينَ (73) ثُمَّ بَعَثْنَا مِنْ بَعْدِهِ رُسُلًا إِلَى قَوْمِهِمْ فَجَاءُوهُمْ بِالْبَيِّنَاتِ فَمَا كَانُوا لِيُؤْمِنُوا بِمَا كَذَّبُوا بِهِ مِنْ قَبْلُ كَذَلِكَ نَطْبَعُ عَلَى قُلُوبِ الْمُعْتَدِينَ (74) ثُمَّ بَعَثْنَا مِنْ بَعْدِهِمْ مُوسَى وَهَارُونَ إِلَى فِرْعَوْنَ وَمَلَئِهِ بِآيَاتِنَا فَاسْتَكْبَرُوا وَكَانُوا قَوْمًا مُجْرِمِينَ (75) فَلَمَّا جَاءَهُمُ الْحَقُّ مِنْ عِنْدِنَا قَالُوا إِنَّ هَذَا لَسِحْرٌ مُبِينٌ (76) قَالَ مُوسَى أَتَقُولُونَ لِلْحَقِّ لَمَّا جَاءَكُمْ أَسِحْرٌ هَذَا وَلَا يُفْلِحُ السَّاحِرُونَ (77) قَالُوا أَجِئْتَنَا لِتَلْفِتَنَا عَمَّا وَجَدْنَا عَلَيْهِ آبَاءَنَا وَتَكُونَ لَكُمَا الْكِبْرِيَاءُ فِي الْأَرْضِ وَمَا نَحْنُ لَكُمَا بِمُؤْمِنِينَ (78) وَقَالَ فِرْعَوْنُ ائْتُونِي بِكُلِّ سَاحِرٍ عَلِيمٍ (79) فَلَمَّا جَاءَ السَّحَرَةُ قَالَ لَهُمْ مُوسَى أَلْقُوا مَا أَنْتُمْ مُلْقُونَ (80) فَلَمَّا أَلْقَوْا قَالَ مُوسَى مَا جِئْتُمْ بِهِ السِّحْرُ إِنَّ اللَّهَ سَيُبْطِلُهُ إِنَّ اللَّهَ لَا يُصْلِحُ عَمَلَ الْمُفْسِدِينَ (81) وَيُحِقُّ اللَّهُ الْحَقَّ بِكَلِمَاتِهِ وَلَوْ كَرِهَ الْمُجْرِمُونَ (82) فَمَا آمَنَ لِمُوسَى إِلَّا ذُرِّيَّةٌ مِنْ قَوْمِهِ عَلَى خَوْفٍ مِنْ فِرْعَوْنَ وَمَلَئِهِمْ أَنْ يَفْتِنَهُمْ وَإِنَّ فِرْعَوْنَ لَعَالٍ فِي الْأَرْضِ وَإِنَّهُ لَمِنَ الْمُسْرِفِينَ (83) وَقَالَ مُوسَى يَا قَوْمِ إِنْ كُنْتُمْ آمَنْتُمْ بِاللَّهِ فَعَلَيْهِ تَوَكَّلُوا إِنْ كُنْتُمْ مُسْلِمِينَ (84) فَقَالُوا عَلَى اللَّهِ تَوَكَّلْنَا رَبَّنَا لَا تَجْعَلْنَا فِتْنَةً لِلْقَوْمِ الظَّالِمِينَ (85) وَنَجِّنَا بِرَحْمَتِكَ مِنَ الْقَوْمِ الْكَافِرِينَ (86) وَأَوْحَيْنَا إِلَى مُوسَى وَأَخِيهِ أَنْ تَبَوَّآ لِقَوْمِكُمَا بِمِصْرَ بُيُوتًا وَاجْعَلُوا بُيُوتَكُمْ قِبْلَةً وَأَقِيمُوا الصَّلَاةَ وَبَشِّرِ الْمُؤْمِنِينَ (87) وَقَالَ مُوسَى رَبَّنَا إِنَّكَ آتَيْتَ فِرْعَوْنَ وَمَلَأَهُ زِينَةً وَأَمْوَالًا فِي الْحَيَاةِ الدُّنْيَا رَبَّنَا لِيُضِلُّوا عَنْ سَبِيلِكَ رَبَّنَا اطْمِسْ عَلَى أَمْوَالِهِمْ وَاشْدُدْ عَلَى قُلُوبِهِمْ فَلَا يُؤْمِنُوا حَتَّى يَرَوُا الْعَذَابَ الْأَلِيمَ (88) قَالَ قَدْ أُجِيبَتْ دَعْوَتُكُمَا فَاسْتَقِيمَا وَلَا تَتَّبِعَانِّ سَبِيلَ الَّذِينَ لَا يَعْلَمُونَ (89) وَجَاوَزْنَا بِبَنِي إِسْرَائِيلَ الْبَحْرَ فَأَتْبَعَهُمْ فِرْعَوْنُ وَجُنُودُهُ بَغْيًا وَعَدْوًا حَتَّى إِذَا أَدْرَكَهُ الْغَرَقُ قَالَ آمَنْتُ أَنَّهُ لَا إِلَهَ إِلَّا الَّذِي آمَنَتْ بِهِ بَنُو إِسْرَائِيلَ وَأَنَا مِنَ الْمُسْلِمِينَ (90) آلْآنَ وَقَدْ عَصَيْتَ قَبْلُ وَكُنْتَ مِنَ الْمُفْسِدِينَ (91) فَالْيَوْمَ نُنَجِّيكَ بِبَدَنِكَ لِتَكُونَ لِمَنْ خَلْفَكَ آيَةً وَإِنَّ كَثِيرًا مِنَ النَّاسِ عَنْ آيَاتِنَا لَغَافِلُونَ (92) وَلَقَدْ بَوَّأْنَا بَنِي إِسْرَائِيلَ مُبَوَّأَ صِدْقٍ وَرَزَقْنَاهُمْ مِنَ الطَّيِّبَاتِ فَمَا اخْتَلَفُوا حَتَّى جَاءَهُمُ الْعِلْمُ إِنَّ رَبَّكَ يَقْضِي بَيْنَهُمْ يَوْمَ الْقِيَامَةِ فِيمَا كَانُوا فِيهِ يَخْتَلِفُونَ (93) فَإِنْ كُنْتَ فِي شَكٍّ مِمَّا أَنْزَلْنَا إِلَيْكَ فَاسْأَلِ الَّذِينَ يَقْرَءُونَ الْكِتَابَ مِنْ قَبْلِكَ لَقَدْ جَاءَكَ الْحَقُّ مِنْ رَبِّكَ فَلَا تَكُونَنَّ مِنَ الْمُمْتَرِينَ (94) وَلَا تَكُونَنَّ مِنَ الَّذِينَ كَذَّبُوا بِآيَاتِ اللَّهِ فَتَكُونَ مِنَ الْخَاسِرِينَ (95) إِنَّ الَّذِينَ حَقَّتْ عَلَيْهِمْ كَلِمَتُ رَبِّكَ لَا يُؤْمِنُونَ (96) وَلَوْ جَاءَتْهُمْ كُلُّ آيَةٍ حَتَّى يَرَوُا الْعَذَابَ الْأَلِيمَ (97) فَلَوْلَا كَانَتْ قَرْيَةٌ آمَنَتْ فَنَفَعَهَا إِيمَانُهَا إِلَّا قَوْمَ يُونُسَ لَمَّا آمَنُوا كَشَفْنَا عَنْهُمْ عَذَابَ الْخِزْيِ فِي الْحَيَاةِ الدُّنْيَا وَمَتَّعْنَاهُمْ إِلَى حِينٍ (98) وَلَوْ شَاءَ رَبُّكَ لَآمَنَ مَنْ فِي الْأَرْضِ كُلُّهُمْ جَمِيعًا أَفَأَنْتَ تُكْرِهُ النَّاسَ حَتَّى يَكُونُوا مُؤْمِنِينَ (99) وَمَا كَانَ لِنَفْسٍ أَنْ تُؤْمِنَ إِلَّا بِإِذْنِ اللَّهِ وَيَجْعَلُ الرِّجْسَ عَلَى الَّذِينَ لَا يَعْقِلُونَ (100) قُلِ انْظُرُوا مَاذَا فِي السَّمَاوَاتِ وَالْأَرْضِ وَمَا تُغْنِي الْآيَاتُ وَالنُّذُرُ عَنْ قَوْمٍ لَا يُؤْمِنُونَ (101) فَهَلْ يَنْتَظِرُونَ إِلَّا مِثْلَ أَيَّامِ الَّذِينَ خَلَوْا مِنْ قَبْلِهِمْ قُلْ فَانْتَظِرُوا إِنِّي مَعَكُمْ مِنَ الْمُنْتَظِرِينَ (102) ثُمَّ نُنَجِّي رُسُلَنَا وَالَّذِينَ آمَنُوا كَذَلِكَ حَقًّا عَلَيْنَا نُنْجِ الْمُؤْمِنِينَ (103) قُلْ يَا أَيُّهَا النَّاسُ إِنْ كُنْتُمْ فِي شَكٍّ مِنْ دِينِي فَلَا أَعْبُدُ الَّذِينَ تَعْبُدُونَ مِنْ دُونِ اللَّهِ وَلَكِنْ أَعْبُدُ اللَّهَ الَّذِي يَتَوَفَّاكُمْ وَأُمِرْتُ أَنْ أَكُونَ مِنَ الْمُؤْمِنِينَ (104) وَأَنْ أَقِمْ وَجْهَكَ لِلدِّينِ حَنِيفًا وَلَا تَكُونَنَّ مِنَ الْمُشْرِFكِينَ (105) وَلَا تَدْعُ مِنْ دُونِ اللَّهِ مَا لَا يَنْفَعُكَ وَلَا يَضُرُّكَ فَإِنْ فَعَلْتَ فَإِنَّكَ إِذًا مِنَ الظَّالِمِينَ (106) وَإِنْ يَمْسَسْكَ اللَّهُ بِضُرٍّ فَلَا كَاشِفَ لَهُ إِلَّا هُوَ وَإِنْ يُرِدْكَ بِخَيْرٍ فَلَا رَادَّ لِفَضْلِهِ يُصِيبُ بِهِ مَنْ يَشَاءُ مِنْ عِبَادِهِ وَهُوَ الْغَفُورُ الرَّحِيمُ (107) قُلْ يَا أَيُّهَا النَّاسُ قَدْ جَاءَكُمُ الْحَقُّ مِنْ رَبِّكُمْ فَمَنِ اهْتَدَى فَإِنَّمَا يَهْتَدِي لِنَفْسِهِ وَمَنْ ضَلَّ فَإِنَّمَا يَضِلُّ عَلَيْهَا وَمَا أَنَا عَلَيْكُمْ بِوَكِيلٍ (108) وَاتَّبِعْ مَا يُوحَى إِلَيْكَ وَاصْبِرْ حَتَّى يَحْكُمَ اللَّهُ وَهُوَ خَيْرُ الْحَاكِمِينَ (109&lt;/span&gt;&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;span style=&quot;font-family: Serif; font-size: 20px; text-shadow: silver 0.2em 0.2em 0.1em;&quot;&gt;[[User:williammacewen#with diacritics|&lt;span style=&quot;color=&quot; #954535&quot;&quot;&gt;return to top&lt;/span&gt;]]&lt;/span&gt;&lt;/p&gt;

== References ==
{{reflist}}</text>
      <sha1>nv6juvoblfp9niysvchg0vllf389auv</sha1>
    </revision>
  </page>
  <page>
    <title>User:Broter/The Church of Jesus Christ of Latter-day Saints</title>
    <ns>2</ns>
    <id>367379</id>
    <revision>
      <id>4668921</id>
      <parentid>4414351</parentid>
      <timestamp>2026-09-05T12:15:08Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668921</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4661" sha1="qbxn7woq24qx8hakcphi09jwfdzpyvb" xml:space="preserve">__NOTOC__
{| border=&quot;0&quot; cellspacing=&quot;5&quot; cellpadding=&quot;8&quot;
|colspan=&quot;2&quot; style=&quot;background-color:#fcfcfc;{{Text default color}};border:1px solid #ccc;margin-top:.7em;&quot;|
{|style=&quot;width:100%;background-color:#fcfcfc;{{Text default color}};&quot; border=&quot;0&quot;
|style=&quot;width:100%;color:#000&quot;|
{|style=&quot;width:100%;border:solid 0px;background:none;color:inherit;&quot;
|-      
|style=&quot;padding-left: 12px;text-align:center;white-space:nowrap;color:#000&quot; |
[[Image:Saltlaketemplehighsmith13507u.jpg|thumb|right|[[:W:en:Temple Square|Temple Square]]]]
&lt;div style=&quot;font-size:162%;border:none;margin: 0;padding:.1em;color:#000&quot;&gt;
The Church of Jesus Christ of Latter-day Saints
&lt;/div&gt;
&lt;div style=&quot;top:+0.2em;font-size: 110%&quot;&gt;

A book about The Church of Jesus Christ of Latter-day Saints

&lt;/div&gt;
|}
{|style=&quot;border-spacing:8px;margin:0px -8px&quot;
|class=&quot;MainPageBG&quot; style=&quot;width:55%;border:1px solid #cef2e0;background-color:#f5fffa;{{Text default color}};vertical-align:top;color:#000&quot;|
{| cellpadding=&quot;2&quot; cellspacing=&quot;5&quot; style=&quot;width:100%;vertical-align:top;background-color:#ffffff;{{Text default color}};&quot;
|&lt;h2 style=&quot;margin:0;background-color:#cef2e0;{{Text default color}};font-family:sans-serif;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;&quot;&gt;The Church of Jesus Christ of Latter-day Saints&lt;/h2&gt;
|-
|style=&quot;color:#000&quot;|

According to LDS Church teachings, there was a Great Apostasy, which means that all churches fell away from the true gospel and teach today false doctrines. Thus the only true church on earth needed to be restored by the Prophet Joseph Smith. His successors, who are appointed by God, lead now this one true church. This is the reason for the existence of the LDS Church.&lt;ref name = Faust&gt;{{Citation |last= Faust |first= James E. |author-link= James E. Faust |title= The Restoration of All Things |url= http://lds.org/liahona/2006/05/the-restoration-of-all-things |journal= [[Liahona (magazine)|Liahona]] |publisher= LDS Church |pages= 61–62, 67–68 |date=May 2006 }}&lt;/ref&gt; &lt;ref name = Eyring&gt;{{Citation |last= Eyring |first= Henry B. |author-link= Henry B. Eyring |title= The True and Living Church |url= http://www.lds.org/ensign/2008/05/the-true-and-living-church |journal= [[Ensign (LDS magazine)|Ensign]] |publisher= LDS Church |pages= 20–24 |date= May 2008  }}&lt;/ref&gt;
|}
|class=&quot;MainPageBG&quot; style=&quot;width:55%;border:1px solid #cef2e0;background-color:#f5fffa;vertical-align:top;color:#000&quot;|
{| cellpadding=&quot;2&quot; cellspacing=&quot;5&quot; style=&quot;width:100%;vertical-align:top;background-color:#ffffff;{{Text default color}};&quot;
|&lt;h2 style=&quot;margin:0;background-color:#cef2e0;{{Text default color}};font-family:sans-serif;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;&quot;&gt;Contents&lt;/h2&gt;
|-
|style=&quot;color:#000&quot;|
#[[/The Gospel of Jesus Christ/]]
#[[/The Great Apostasy/]]
#[[/Joseph Smith/]]
#[[/Prophets and Apostles/]]
#[[/Scriptures/]]
#[[/Priesthood/]]
#[[/Relief Society/]]
#[[/Families/]]
#[[/Temples/]]
#[[/Tithing/]]
#[[/Law of Chastity/]]
#[[/Temporal Welfare/]]
#[[/Missionary Work/]]
#[[/Church Service/]]
#[[/Church Buildings/]]
#[[/Church Meetings/]]
|}

|}

{|style=&quot;border-spacing:8px;margin:-8px -8px;width:100%&quot;
|class=&quot;MainPageBG&quot; style=&quot;width:100%;border:1px solid #cef2e0;background-color:#ffffff;vertical-align:top;color:#000&quot;|
{|cellpadding=&quot;2&quot; cellspacing=&quot;5&quot; style=&quot;width:100%;vertical-align:top;background-color:#ffffff;color:#000&quot;
!

&lt;h2 style=&quot;margin:0;background-color:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;&quot;&gt;Summary of the Teachings of The Church of Jesus Christ of Latter-day Saints&lt;/h2&gt;
|-
|style=&quot;color:#000&quot;|
|}


The teachings of the LDS Church are best summarized by a quote by [[:W:en:Joseph Smith|Joseph Smith]]:
{{cquote|The fundamental principles of our religion are the testimony of the Apostles and Prophets, concerning Jesus Christ, that He died, was buried, and rose again the third day, and ascended into heaven; and all other things which pertain to our religion are only appendages to it.&lt;ref&gt;p. 121&lt;/ref&gt;}}
|}
|}
|}
==Notes==
{{sisterlinks|species=no}}
{{Reflist}}

==Bibliography==
*{{Citation
 | editor-last = Smith
 | editor-first = Joseph Fielding
 | author-link = Joseph Fielding Smith
 | title = [[:W:en:Teachings of the Prophet Joseph Smith|Teachings of the Prophet Joseph Smith]]
 | publisher = [[:W:en:Deseret Book Company|Deseret Book Company]]
 | year = 1976
 | isbn = 0-87747-665-9
 | others = (index and concordance by [[:W:en:Robert J. Matthews|Robert J. Matthews]]) 
}}

{{Subjects|Abrahamic religions}}
{{alphabetical|T}}</text>
      <sha1>qbxn7woq24qx8hakcphi09jwfdzpyvb</sha1>
    </revision>
  </page>
  <page>
    <title>Users Guide to Hartshorne Algebraic Geometry/Chapter 0</title>
    <ns>0</ns>
    <id>384578</id>
    <revision>
      <id>4669085</id>
      <parentid>3427705</parentid>
      <timestamp>2026-09-06T07:25:03Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <origin>4669085</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22184" sha1="2iq34ygwtdxtig9vkhje2tyuffo4j91" xml:space="preserve">== References ==
# Algebraic Geometry - Hartshorne
# Arithmetic - Serre
# https://people.ucsc.edu/~weissman/Math222A/SerreAnn.pdf
# http://web.mit.edu/18.705/www/12Nts-2up.pdf (for basic commutative algebra)
# https://arxiv.org/pdf/1605.04832.pdf (for more advanced commutative algebra)
# [http://wstein.org/books/ant/ant.pdf Algebraic Number Theory, A Computational Approach] - Stein

== Basic Commutative Algebra ==
===Categories of Commutative Rings and Algebras===
The starting point for this section is the definition of a '''commutative ring''': a unital ring with commutative multiplication. In this book you can assume that all rings are commutative, so we will omit the 'commutative' adjective. The most basic rings include

* &lt;math&gt;\mathbb{Z}&lt;/math&gt;
* &lt;math&gt;\mathbb{Z}/n&lt;/math&gt;
* Fields &lt;math&gt;\mathbb{F}&lt;/math&gt;
* Polynomial rings &lt;math&gt;R[x_1,\ldots,x_n]&lt;/math&gt;

We can relate rings to one another using a '''morphism''' of rings. A function &lt;math&gt;\phi: R \to S&lt;/math&gt; between rings is a morphism of rings if the following two axioms are satisfied
# &lt;math&gt;\phi(a + b) = \phi(a) + \phi(b)&lt;/math&gt; (Additivity)
# &lt;math&gt;\phi(ab) = \phi(a)\phi(b)&lt;/math&gt; (Multiplicativity)
we could have stated this succinctly as a function which respects the ring structure. It turns out that rings with ring morphisms form a category &lt;math&gt;\textbf{CRing}&lt;/math&gt;. As an important technical note, there is no zero-ring given by a single element in our category. This category has an initial object given by the ring of integers because given a ring morphisms
: &lt;math&gt;\phi:\mathbb{Z} \to R&lt;/math&gt;
the ring morphism axioms forces
:&lt;math&gt;\phi(1) = 1_R&lt;/math&gt;, &lt;math&gt;\phi(-1) = -1_R&lt;/math&gt;, and &lt;math&gt;\phi(n) = \phi\left(\sum_n 1\right) = \sum_n \phi(1)&lt;/math&gt;
Recall that the category of &lt;math&gt;R&lt;/math&gt;-algebras has objects given by ring morphisms &lt;math&gt;R \to S&lt;/math&gt; and morphisms given by commutative diagrams
&lt;blockquote&gt;&lt;math&gt;\begin{matrix}
 &amp;&amp;  S \\
 &amp; \nearrow\\
R &amp;&amp; \downarrow \phi \\
&amp; \searrow \\
&amp;&amp; S'
\end{matrix}&lt;/math&gt;&lt;/blockquote&gt;If we consider only algebras, the category &lt;math&gt;\mathbb{Z}-\textbf{CAlg}&lt;/math&gt; is equivalent to the category &lt;math&gt;\textbf{CRing}&lt;/math&gt;. Note that it is common to consider the categories &lt;math&gt;\mathbb{F}_q-\textbf{CAlg}&lt;/math&gt;, &lt;math&gt;\mathbb{C}-\textbf{CAlg}&lt;/math&gt;, &lt;math&gt;\mathbb{Q}_p-\textbf{CAlg}&lt;/math&gt;. The motivation for why will be readily apparent when considering categories of schemes.

===Ideals===
One of the ways to construct new rings is by taking quotient rings. An ideal of a ring is a subset &lt;math&gt;I \subset R&lt;/math&gt; which is
# An abelian group under addition
# &lt;math&gt;R\cdot I \subset R&lt;/math&gt;
Then, we can take the quotient of abelian groups &lt;math&gt;R/I&lt;/math&gt; and use the multiplicative structure on &lt;math&gt;R&lt;/math&gt; to construct one on &lt;math&gt;R/I&lt;/math&gt;. The second axiom of ideals guarantees that this is well-defined. This is called a '''quotient ring'''. Some typical examples of quotient rings are given by
* &lt;math&gt;\mathbb{Z}/(p)&lt;/math&gt;
* &lt;math&gt;\mathbb{Z}[x]/(x^2 - 5) \cong \mathbb{Z}[\sqrt{5}]&lt;/math&gt;
* &lt;math&gt;\mathbb{Q}[x]/(x^p-1)&lt;/math&gt;
* &lt;math&gt;
\frac{\mathbb{Z}[x_1,\ldots,x_n]}{(f_1,\ldots,f_k)}
&lt;/math&gt;
===Playing with Presentations===
As we have seen, there are many ways to construct polynomial ring; but, another interesting technique for creating new polynomial rings is to attach variables which have relations between them. For example, consider &lt;math&gt;\mathbb{Z}[x,x^2,x^3]&lt;/math&gt;. We can relabel the elements we've attached, so we consider the ring &lt;math&gt;\mathbb{Z}[X,Y,Z]&lt;/math&gt;, but there are a couple relations between these variables: 
:&lt;math&gt;X^2 - Y, XY - Z&lt;/math&gt;
note that these two relations can be used to show others such as &lt;math&gt;XZ - Y^2&lt;/math&gt; and &lt;math&gt;X^3 - Z&lt;/math&gt;. Hence
:&lt;math&gt;\mathbb{Z}[x,x^2,x^3] \cong  \frac{\mathbb{Z}[X,Y,Z]}{(X^2 - Y, XY - Z)}&lt;/math&gt;
Some other examples include
*&lt;math&gt;\mathbb{Z}[x,x^{3/2}] \cong \frac{\mathbb{Z}[X,Y]}{(Y^2 - X^3)} &lt;/math&gt;
*&lt;math&gt;\mathbb{Z}[x^2,xy,y^2] \cong \frac{\mathbb{Z}[X,Y,Z]}{(XZ - Y^2)}&lt;/math&gt;
*&lt;math&gt;\mathbb{Z}[x^3,x^2y,xy^2,y^3] \cong \frac{\mathbb{Z}[X,Y,Z,W]}{(XW - YZ, XZ - Y^2, YW - Z^2)}&lt;/math&gt;
===Prime Ideals===
There are a special class of ideals called '''prime ideals''': an ideal &lt;math&gt;\mathfrak{p}&lt;/math&gt; in a UFD &lt;math&gt;R&lt;/math&gt; is prime if
:&lt;math&gt;xy \in \mathfrak{p} \Leftrightarrow x \in \mathfrak{p} \text{ or } y \in \mathfrak{p}&lt;/math&gt;
For example, &lt;math&gt;(p) \subset \mathbb{Z}&lt;/math&gt; is the first known example of a prime ideal. It should be apparent that &lt;math&gt;(6)&lt;/math&gt; is not a prime ideal since &lt;math&gt; 2\cdot 3 \in (6)&lt;/math&gt; but &lt;math&gt;2,3 \not\in (6)&lt;/math&gt;. Now, given an irreducible polynomial &lt;math&gt;f \in S[x_1,\ldots,x_n]&lt;/math&gt; the ideal &lt;math&gt;(f)&lt;/math&gt; will be prime. A simple non-example of a prime ideal is given by &lt;math&gt;(xy) \subset \mathbb{C}[x,y]&lt;/math&gt;. This can be generalized to &lt;math&gt;(fg) \subset S[x_1,\ldots,x_n]&lt;/math&gt;. Some other examples of prime ideals include
:&lt;math&gt;(x^2 + 1) \subset \mathbb{Q}[x]&lt;/math&gt;
:&lt;math&gt;(x-\alpha) \subset \mathbb{C}[x]&lt;/math&gt;
:&lt;math&gt;(y^2 - x^3 + 1) \subset \mathbb{C}[x,y]&lt;/math&gt;
If you take the quotient ring of a prime ideal in a UFD &lt;math&gt;R&lt;/math&gt; you get an '''integral domain'''. This means your ring has the following multiplicative property:
:&lt;math&gt;xy = 0&lt;/math&gt; if &lt;math&gt;x=0&lt;/math&gt; or &lt;math&gt;y=0&lt;/math&gt;
For example, in
:&lt;math&gt; \frac{\mathbb{C}[x,y]}{(y^2 - x^3)}&lt;/math&gt;
you will never be able to multiply two non-zero elements together to get zero. The two key non-examples of a ring being an integral domain are
:&lt;math&gt;\mathbb{C}[x,y]/(xy)&lt;/math&gt; since &lt;math&gt;xy = 0&lt;/math&gt;
:&lt;math&gt;\mathbb{C}[x]/(x^2)&lt;/math&gt; since &lt;math&gt; x \cdot x = 0&lt;/math&gt;
''In general'', an ideal &lt;math&gt;\mathfrak{p}&lt;/math&gt; of a ring &lt;math&gt;R&lt;/math&gt; is called '''prime''' if &lt;math&gt;R/\mathfrak{p}&lt;/math&gt; is an integral domain. If &lt;math&gt;R/\mathfrak{m}&lt;/math&gt; is also a field, then we call &lt;math&gt;\mathfrak{m}&lt;/math&gt; a '''maximal ideal'''. One useful exercise is to check that for a morphism &lt;math&gt;f:R \to S&lt;/math&gt; and a prime ideal &lt;math&gt;\mathfrak{p}\subset S&lt;/math&gt; the inverse image &lt;math&gt;f^{-1}(\mathfrak{p})&lt;/math&gt; is a prime ideal.  The second example motivates the operation of taking radicals of an ideal. Given an ideal &lt;math&gt;I\subseteq R&lt;/math&gt; we define its radical as&lt;blockquote&gt;&lt;math&gt;\sqrt{I} = \{ f \in R : f^k \in I \text{ for some } r \in \mathbb{N} \}&lt;/math&gt;&lt;/blockquote&gt;For example, the radical of the ideal &lt;math&gt;((x^2 - y + z)^4(xyz - z^2)^5)\subset \mathbb{Z}[x,y,z]&lt;/math&gt; is &lt;math&gt;((x^2 - y + z)(xyz - z^2))&lt;/math&gt;.  Given a quotient ring &lt;math&gt;R/I&lt;/math&gt; we call the ring &lt;math&gt;R/\sqrt{I}&lt;/math&gt; its reduction; sometimes this is denoted &lt;math&gt;(R/I)_{\text{red}}&lt;/math&gt;. We define the '''nilradical''' of a ring &lt;math&gt;R&lt;/math&gt; as &lt;math&gt;\sqrt{(0)}&lt;/math&gt;. The nonzero elements in the nilradical are called '''nilpotents'''.

===Eisenstein's Criterion and Constructing Prime Ideals===
There is a generalization of Eisenstein's criterion for integral domains: given a ring &lt;math&gt;R&lt;/math&gt; and a polynomial &lt;math&gt;f(x) \in R[x]&lt;/math&gt; which can be written as
:&lt;math&gt;f(x) = a_nx^n + a_{n-1}x^{n-1} + \cdots + a_1x + a_0&lt;/math&gt;
then it cannot be written as a product of polynomials if the following conditions are satisfied: Suppose there exists a prime ideal &lt;math&gt;\mathfrak{p}\subset R&lt;/math&gt; such that
:&lt;math&gt;
\begin{align}
a_i \in \mathfrak{p} \text{ for } i \neq n \\
a_n \not\in \mathfrak{p} \\
a_0 \not\in \mathfrak{p}^2
\end{align}
&lt;/math&gt;
then &lt;math&gt;f(x)&lt;/math&gt; cannot be written as a product of polynomials &lt;math&gt;g_1(x)\cdots g_k(x)&lt;/math&gt;.

For example, consider the integral domain &lt;math&gt;\mathbb{C}[x]&lt;/math&gt; and the polynomial &lt;math&gt;f \in \mathbb{C}[x][y]&lt;/math&gt; given by
:&lt;math&gt;f(x,y) = 1\cdot y^3 + 0\cdot y^2 + 0\cdot y + x^3\cdot y^0 = y^3 + x^3&lt;/math&gt;
Using the prime ideal &lt;math&gt;(x-1)\subset \mathbb{C}[x]&lt;/math&gt; we have that &lt;math&gt;a_1,a_2=0 \in (x-1)&lt;/math&gt;, &lt;math&gt;a_3 = 1 \not\in (x-1)&lt;/math&gt;, and &lt;math&gt;a_0 = x^3 \not\in (x-1)^2&lt;/math&gt;. Hence
:&lt;math&gt;(x^3 + y^3) \subset \mathbb{C}[x,y]&lt;/math&gt;
is a prime ideal. This example can be extended to show that
:&lt;math&gt;x_1^{k_1} + \cdots + x_n^{k_n} \in \mathbb{C}[x_1,\ldots,x_n]&lt;/math&gt;
generates a prime ideal.

===Nullstellensatz===
Now we are in the right place to discuss the foundational theorem of algebraic geometry: '''Hilbert's nullstellensatz'''. Here we fix &lt;math&gt;k&lt;/math&gt; as an algebraically closed field.

'''Theorem:''' The maximal ideals of &lt;math&gt;\mathfrak{m}\subset k[x_1,\ldots,x_n]&lt;/math&gt; are in bijection with the set &lt;math&gt;k^n&lt;/math&gt;.

For example, the kernel of &lt;math&gt;\text{ev}_{(1,2)}:\mathbb{C}[x,y] \to \mathbb{C}&lt;/math&gt; is the ideal &lt;math&gt;(x-1,y-2)&lt;/math&gt;. This allows one to interpret quotient rings give by ideals &lt;math&gt;I \subset k[x_1,\ldots,x_n]&lt;/math&gt; as algebraic subsets of &lt;math&gt;k^n&lt;/math&gt; because an evaluation morphism&lt;blockquote&gt;&lt;math&gt;\text{ev}_{(\alpha_1,\ldots,\alpha_n)}:\mathbb{C}[x_1,\ldots,x_n]/I \to \mathbb{C}&lt;/math&gt;&lt;/blockquote&gt;is well-defined only if &lt;math&gt;(x_1-\alpha_1,\ldots,x_n-\alpha_n) \subset k[x_1,\ldots,x_n]/I&lt;/math&gt; is a maximal ideal. For example, consider the following example and non-example:
* &lt;math&gt;\text{ev}_{(1,1)}:\mathbb{C}[x,y]/(y-x^2) \to \mathbb{C}&lt;/math&gt; is a well defined morphism since&lt;math&gt;(x-1,y-1,y^2 - x) = (x-1,y-1,1^2 - 1) = (x-1,y-1)&lt;/math&gt;This implies that &lt;math&gt;(1,1) \in \{ (a,b) \in \mathbb{C}^2 : b^2 - a\}&lt;/math&gt;
* &lt;math&gt;\text{ev}_{(1,2)}:\mathbb{C}[x,y]/(y-x^2) \to \mathbb{C}&lt;/math&gt; is not a well-defined morphism because &lt;math&gt;(x-1,y-2,y^2-x) = (x-1,y-2,4-1) = (1)&lt;/math&gt;; there is no quotient ring &lt;math&gt;R/(1)&lt;/math&gt;. Hence &lt;math&gt;(1,2) \not\in \{ (a,b) \in \mathbb{C}^2 : b^2 - a\}&lt;/math&gt;
Now we can interpret rings which are not integral. For example, we saw that &lt;math&gt;\mathbb{C}[x,y]/(xy)&lt;/math&gt; is not an integral domain. Geometrically, this is the union of the &lt;math&gt;x&lt;/math&gt; and &lt;math&gt;y&lt;/math&gt; axes. The other main case of a non-integral ring is a non-reduced ring. For example, &lt;math&gt;\mathbb{C}[x,y]/(y^3)&lt;/math&gt; is the &lt;math&gt;x&lt;/math&gt;-axis but there is extra algebraic information from the &lt;math&gt;y,y^2&lt;/math&gt; left over. The way you should interpret this ring as is a '''fat''' line.

=== Basic Scheme Theory ===
We can now ''confidently'' define an affine scheme: it is a functor&lt;blockquote&gt;&lt;math&gt;\text{Hom}_\mathbf{CRing}(R,-): \mathbf{CRing} \to \textbf{Sets}&lt;/math&gt;&lt;/blockquote&gt;for some fixed commutative ring &lt;math&gt;R&lt;/math&gt;.

=== Localization ===
The next basic construction in commutative ring theory is '''localization'''. This defines a generalization of inverting the non-zero integers and getting the rational numbers. Let &lt;math&gt;S\subset R&lt;/math&gt; be a multiplicatively closed subset with unity, meaning &lt;math&gt;1 \in S&lt;/math&gt; and &lt;math&gt; s,s' \in S \Rightarrow ss' \in S&lt;/math&gt;. For example, for a fixed element &lt;math&gt;f \in R&lt;/math&gt; consider the subset &lt;math&gt;\{1,s,s^2,s^3,\ldots\}&lt;/math&gt;. We define a commutative ring &lt;math&gt;R[S^{-1}]&lt;/math&gt; as follows. First, consider the set &lt;math&gt;R\times S / \sim&lt;/math&gt;  where&lt;blockquote&gt;&lt;math&gt;(r,s) \sim (r',s') \text{ if there exists } u \in S \text{ such that } u(rs' - r's) =0&lt;/math&gt;&lt;/blockquote&gt;(don't worry, we will given a motivating example for this seemingly random &lt;math&gt;u&lt;/math&gt;). It is an exercise to verify that this indeed defines an equivalence relation — it is standard to write these equivalence classes as &lt;math&gt;r/s&lt;/math&gt;. These equivalence classes have a well-define commutative ring structure given by&lt;blockquote&gt;&lt;math&gt;\frac{r}{s} \cdot \frac{r'}{s'} = \frac{rr'}{ss'} \text{ and } \frac{r}{s} + \frac{r'}{s'} = \frac{rs' + r's}{ss'}&lt;/math&gt;&lt;/blockquote&gt;Some basic examples of localization include
* The subset &lt;math&gt;S = \{1,p,p^2,p^3,\ldots\} \subset \mathbb{Z}&lt;/math&gt; gives the ring &lt;math&gt;\mathbb{Z}[S^{-1}] = \mathbb{Z}[1/p]&lt;/math&gt;. Notice that if we localized by the set &lt;math&gt;T = \{1,p^3,p^6,p^9,\ldots\} \subset \mathbb{Z}&lt;/math&gt; then this gives the ring &lt;math&gt;\mathbb{Z}[1/p^3]&lt;/math&gt;. But, because we could write &lt;math&gt;1/p&lt;/math&gt; as &lt;math&gt;p^2/p^3&lt;/math&gt;, these two rings are isomorphic. For brevity, we could just say that we localized &lt;math&gt;\mathbb{Z}&lt;/math&gt; by &lt;math&gt;p&lt;/math&gt;. Try localizing by some other non-zero integers and see why you find.
* An important geometric example is given by localizing by some non-zero polynomial &lt;math&gt;f = f_1^{i_1}\cdots f_k^{i_k} \in \mathbb{C}[x_1,\ldots,x_n]&lt;/math&gt;. 
* Given an integral domain &lt;math&gt;R&lt;/math&gt;, we can take the set &lt;math&gt;S = R-\{0\}&lt;/math&gt;. Then, &lt;math&gt;R[S^{-1}]&lt;/math&gt; is called the '''field of fractions''' of the integral domain. (It is an exercise to check that this is a field) 
* Given a ring &lt;math&gt;R&lt;/math&gt; and a prime ideal &lt;math&gt;\mathfrak{p}&lt;/math&gt;, we can consider the set &lt;math&gt;S = R -\mathfrak{p}&lt;/math&gt;. This is multiplicatively closed because of the properties of primality of an ideal. The localization of &lt;math&gt;R&lt;/math&gt; by &lt;math&gt;S&lt;/math&gt; is typically denoted &lt;math&gt;R_\mathfrak{p}&lt;/math&gt;. For example, consider &lt;math&gt;(x,y) \subset \mathbb{C}[x,y]&lt;/math&gt;. The localization can be described as
&lt;blockquote&gt;&lt;math&gt;\mathbb{C}[x,y][S^{-1}] =  \mathbb{C}[x,y]_{\mathfrak{p}} = \left\{ \frac{f(x,y)}{g(x,y)} : f,g \in \mathbb{C}[x,y] \text{ and } g(0,0) \neq 0 \right\}&lt;/math&gt;&lt;/blockquote&gt;The last example is special because it motivates a definition: a ring is '''local''' if it has a unique maximal ideal. The pair &lt;math&gt;(R_\mathfrak{p},\mathfrak{p})&lt;/math&gt; is a local ring.

===Basic Module Theory===
A &lt;math&gt;R&lt;/math&gt;-module is defined as an abelian group &lt;math&gt;M&lt;/math&gt; with a fixed ring morphism &lt;math&gt;\phi:R \to \text{End}_{\textbf{Ab}}(M)&lt;/math&gt;. We will use the notation
:&lt;math&gt;r\cdot m := \phi(r)(m)&lt;/math&gt; where &lt;math&gt;r\in R, m \in M&lt;/math&gt;
for the ring action on &lt;math&gt;M&lt;/math&gt;. A morphism of &lt;math&gt;R&lt;/math&gt;-modules &lt;math&gt;\psi:M\to M'&lt;/math&gt; is defined by a commutative diagram
&lt;blockquote&gt;&lt;math&gt;\begin{matrix}
 &amp;&amp; \text{End}_{\textbf{Ab}}(M) \\
 &amp; \nearrow\\
R &amp;&amp; \downarrow \psi \\
&amp; \searrow \\
&amp;&amp; \text{End}_{\textbf{Ab}}(M')
\end{matrix}&lt;/math&gt;&lt;/blockquote&gt;
We can use this construction to build a category of &lt;math&gt;R&lt;/math&gt;-modules which is '''abelian'''. This means that it has a zero object, kernels and cokernels, products and coproducts, and images/co-images agree.
Please note that we've had to enlarge our category of commutative rings to all rings since the endomorphism ring of an abelian group is generally non-commutative; This is one of the only cases where we use non-commutative unital rings in this book. Typical examples of &lt;math&gt;R&lt;/math&gt;-modules includes
* the zero object &lt;math&gt;0&lt;/math&gt;
* ideals &lt;math&gt;I\subset R&lt;/math&gt;
* direct sums, such as &lt;math&gt;M_1\oplus \cdots \oplus M_k&lt;/math&gt;
* a morphism &lt;math&gt;\phi:R\to S&lt;/math&gt; of rings gives the structure of an &lt;math&gt;R&lt;/math&gt;-module on the underlying abelian group of &lt;math&gt;S&lt;/math&gt;
Another useful technique for constructing new modules is taking the cokernel of a morphism &lt;math&gt;\psi:R^n \to R^m&lt;/math&gt;. For example, the cokernel of&lt;blockquote&gt;&lt;math&gt;\mathbb{C}[x,y,z]^{\oplus 2} \xrightarrow{\cdot (x^4 + y^4 + z^4 - 1)\oplus \cdot (x^4 - y^2 + z^2 + 1)} \mathbb{C}[x,y,z]&lt;/math&gt;&lt;/blockquote&gt;is &lt;math&gt;\mathbb{C}[x,y,z]/(x^4 + y^4 + z^4 - 1,x^4 - y^2 + z^2 + 1)&lt;/math&gt;. We can generalize this example using '''exact sequences'''. A sequence of objects in an abelian category
&lt;blockquote&gt;&lt;math&gt;
M_1\xrightarrow{\phi_1}M_2 \xrightarrow{\phi_2} \to \cdots \xrightarrow{\phi_{n-1}} M_n
&lt;/math&gt;
&lt;/blockquote&gt;is called exact if each
:&lt;math&gt;\frac{\text{Ker}(\phi_i)}{\text{Ker}(\phi_{i-1})} \cong 0&lt;/math&gt;
in the last example, we had the exact sequence
:&lt;math&gt; R^{\oplus2} \to R \to M \to 0&lt;/math&gt;
In general, if there is an exact sequence
:&lt;math&gt;R^n \to R^m \to M \to 0&lt;/math&gt;
for finite integers &lt;math&gt;m,n&lt;/math&gt;, then we say that the module is '''of finite-type'''. If there is just a sequence
:&lt;math&gt;R^n \to M \to 0&lt;/math&gt;
then we say that the module is '''finite'''. For example, the module
:&lt;math&gt;k[x_1,x_2,\ldots] \to k \to 0&lt;/math&gt;
is finite but not finite-type since the kernel of the non-trivial morphism is the ideal
:&lt;math&gt;(x_1,x_2,\ldots) \cong \bigoplus_{i=1}^\infty R\cdot x_i&lt;/math&gt;

===Tensor Products===
* construct tensor products for modules
* construct tensor products of algebras
** show that tensor products of integral domains are integral
*** show that &lt;math&gt;k[\underline{x}]/(f(\underline{x})\otimes_k k[\underline{y}]/(g(\underline{y})) \cong k[\underline{x},\underline{y}]/(f(\underline{x}, g(\underline{y}))&lt;/math&gt;
*** show &lt;math&gt;k[\underline{x}]/(f(\underline{x}))\otimes_{k[\underline{x}]}k[\underline{x}]/(g(\underline{x})) \cong k[\underline{x}]/(f(\underline{x}),g(\underline{x}))&lt;/math&gt;

===Finiteness, Chain Conditions===
If we have an &lt;math&gt;R&lt;/math&gt;-algebra &lt;math&gt;R \to S&lt;/math&gt; we say that &lt;math&gt;S&lt;/math&gt; it is a '''finite''' if it is finite as a module. We say that it is '''of finite-type''' if there exists a surjective morphism &lt;math&gt;R[x_1,\ldots,x_n] \to S&lt;/math&gt;, implying that
:&lt;math&gt;S \cong \frac{R[x_1,\ldots,x_n]}{(f_1,\ldots,f_k)}&lt;/math&gt;

There are a couple other notions of &quot;finiteness&quot; which appear in commutative algebra called '''chain conditions'''. We say call a sequence of &lt;math&gt;R&lt;/math&gt;-modules
:&lt;math&gt;M_1\subseteq M_2\subseteq \cdots&lt;/math&gt;
an '''ascending chain''' and
:&lt;math&gt; N_1\supseteq N_2 \supseteq \cdots&lt;/math&gt;
a '''descending chain'''. They satisfy the '''ascending chain condition''' or '''descending chain condition''' if there is some &lt;math&gt;k&lt;/math&gt; such that &lt;math&gt;M_k=M_{k+1}=\cdots&lt;/math&gt;, &lt;math&gt;N_k=N_{k+1}=N_{k+2}=\cdots&lt;/math&gt;. If there exist chains
:&lt;math&gt;M_1\subseteq M_2 \subseteq \cdots&lt;/math&gt; where &lt;math&gt; \cup^\infty_{i=1}M_i = R&lt;/math&gt;
or
:&lt;math&gt;R\supseteq N_2 \supseteq \cdots&lt;/math&gt;
then we say &lt;math&gt;R&lt;/math&gt; is '''Noetherian''' or '''Artinian''', respectively. One can show that every Artinian ring is Noetherian. The basic examples of Noetherian rings include
* Fields
* &lt;math&gt;\mathbb{Z}&lt;/math&gt;
* Finite algebras over fields
* Quotients of Noetherian rings.
A simple non-example is given by the ring &lt;math&gt;k[x_1,x_2,x_3,\ldots]&lt;/math&gt; where &lt;math&gt;k&lt;/math&gt; is a field. There is a fundamental theorem in algebra called '''Hilbert's Basis Theorem''' stating:&lt;blockquote&gt;'''Theorem:''' If &lt;math&gt;R&lt;/math&gt; is Noetherian, then &lt;math&gt;R[x_1,\ldots,x_n]&lt;/math&gt; is Noetherian&lt;/blockquote&gt;Hence all rings of the form&lt;blockquote&gt;&lt;math&gt;\frac{R[x_1,\ldots,x_n]}{(f_1,\ldots,f_k)}&lt;/math&gt;&lt;/blockquote&gt;are Noetherian. Artinian rings are much simpler than Noetherian rings:&lt;blockquote&gt;'''Theorem:''' Every Artin ring is a finite product of Artin local rings.&lt;/blockquote&gt;All we have to analyze is the structure of an Artin local ring &lt;math&gt;(R,\mathfrak{m})&lt;/math&gt;. Notice that we have a descending chain&lt;blockquote&gt;&lt;math&gt;R \supseteq \mathfrak{m} \supseteq \mathfrak{m}^2 \supseteq \mathfrak{m}^3 \supseteq \cdots&lt;/math&gt;&lt;/blockquote&gt;which eventually stabilizes at some &lt;math&gt;\mathfrak{m}^k&lt;/math&gt;; this is the zero ideal &lt;math&gt;(0)&lt;/math&gt;. We can use this to show the underlying &lt;math&gt;R/\mathfrak{m}&lt;/math&gt;-vector space of &lt;math&gt;R&lt;/math&gt; is finite dimensional. Some examples of artin local rings are
* &lt;math&gt;(\mathbb{C}[x]/(x^5), (x))&lt;/math&gt;
* &lt;math&gt;(\mathbb{Q}[x,y]/((x-1)^3,(x-1)^2(y-2),(y-2)^5)), (x-1,y-2))&lt;/math&gt;

=== Integrality ===
Given a morphism of commutative rings &lt;math&gt;R \to R'&lt;/math&gt; we say an element &lt;math&gt;x \in R'&lt;/math&gt; is '''integral''' over &lt;math&gt;R&lt;/math&gt; if there is a monic polynomial &lt;math&gt;f(t) = t^n + a_{n-1}t^{n-1} +\cdot + a_1t + a_0 \in R[t] &lt;/math&gt;and a morphism&lt;blockquote&gt;&lt;math&gt;\frac{R[t]}{f(t)} \to R'&lt;/math&gt;&lt;/blockquote&gt;sending &lt;math&gt;t \mapsto x&lt;/math&gt;. For example, &lt;math&gt;\sqrt{-5} \in \mathbb{Z}[\sqrt{-5}]&lt;/math&gt; is integral over &lt;math&gt;\mathbb{Z}&lt;/math&gt; since&lt;blockquote&gt;&lt;math&gt;\frac{\mathbb{Z}[t]}{(t^2 + 5)} \cong \mathbb{Z}[\sqrt{-5}]&lt;/math&gt;&lt;/blockquote&gt;Adjoining all of the integral elements &lt;math&gt;\{x_i\}&lt;/math&gt; &lt;math&gt;R&lt;/math&gt; is called the '''integral closure of &lt;math&gt;R&lt;/math&gt; in &lt;math&gt;R'&lt;/math&gt;'''.  An integral domain &lt;math&gt;R&lt;/math&gt; is called '''integrally closed''' if every element in its fraction field is integral over &lt;math&gt;R&lt;/math&gt;. For example, we can compute the integral closure of&lt;blockquote&gt;&lt;math&gt;R = \frac{\mathbb{C}[x,y]}{(x^2 - y^3)}&lt;/math&gt;&lt;/blockquote&gt;fairly easily. Since it is isomorphic to the ring &lt;math&gt;\mathbb{C}[x,x^{3/2}]&lt;/math&gt; we should see immediately that &lt;math&gt;x^{1/2}&lt;/math&gt; is not contained in &lt;math&gt;R&lt;/math&gt;. Adjoining this element to &lt;math&gt;R&lt;/math&gt; gives a ring isomorphic to &lt;math&gt;\mathbb{C}[s]&lt;/math&gt;. As an exercise, try and unpack&lt;blockquote&gt;&lt;math&gt;\frac{\mathbb{C}[x,y,z,w]}{(x^2 - y^5 - y^3, z^3 - w^4)}&lt;/math&gt;&lt;/blockquote&gt;TODO:

- hyperelliptic curves

- quotient fields of curves

- https://math.stackexchange.com/questions/2304521/why-is-this-coordinate-ring-integral-over-kx

- rings of integers

== Chapter 0 ==

=== Basic Commutative Algebra ===

==== Structures ====
* tensor products of modules/algebras... localization of modules
* categories of commutative algebras
* support of modules
* graded rings
* colimits and stalks
* limits, completions, p-adics
* valuations - https://en.wikipedia.org/wiki/Valuation_(algebra)#P-adic_valuation_on_a_Dedekind_domain
* dimension
* transcendence degree
* functor formalism
* categorical structures such as pullbacks and pushforwards
* kahler differentials/ basic differential algebra
* smooth algebras/smooth morphisms
* complete intersection/local complete intersection morphisms
* etale algebras/etale morphisms
* galois theory with useful terminology...
* same w/ algebraic number theory terminology...
* basic homological algebra, ext, tor
* koszul complexes
* derived categories
* grothendieck group
* hilbert polynomial
* grobner bases/elimination theory - https://mathoverflow.net/questions/60957/how-to-determine-whether-an-ideal-is-prime-or-not-by-an-algorithm

==== Theorems ====
* Eisenstein's Criterion
* Primary Decomposition
* Noether Normalization
* Going up and down

=== Basic Differential/Complex Geometry ===

==== Constructions ====
* Smooth manifolds
* Morphisms
* Vector Bundles
* Topological K-theory
* de-Rham Cohomology
* Complex manifolds and sheaves
* hodge decomposition of complex manifolds

=== Theorems ===
* Whitney embedding theorem
* Submersion theorem
* Sard's theorem

{{BookCat}}</text>
      <sha1>2iq34ygwtdxtig9vkhje2tyuffo4j91</sha1>
    </revision>
    <revision>
      <id>4669086</id>
      <parentid>4669085</parentid>
      <timestamp>2026-09-06T07:27:06Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669086</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22190" sha1="ar92so9tv1lvcz247phreutf04dhkms" xml:space="preserve">== References ==
# Algebraic Geometry - Hartshorne
# Arithmetic - Serre
# https://people.ucsc.edu/~weissman/Math222A/SerreAnn.pdf
# http://web.mit.edu/18.705/www/12Nts-2up.pdf (for basic commutative algebra)
# https://arxiv.org/pdf/1605.04832.pdf (for more advanced commutative algebra)
# [http://wstein.org/books/ant/ant.pdf Algebraic Number Theory, A Computational Approach] - Stein

== Basic Commutative Algebra ==
===Categories of Commutative Rings and Algebras===
The starting point for this section is the definition of a '''commutative ring''': a unital ring with commutative multiplication. In this book you can assume that all rings are commutative, so we will omit the 'commutative' adjective. The most basic rings include

* &lt;math&gt;\mathbb{Z}&lt;/math&gt;
* &lt;math&gt;\mathbb{Z}/n&lt;/math&gt;
* Fields &lt;math&gt;\mathbb{F}&lt;/math&gt;
* Polynomial rings &lt;math&gt;R[x_1,\ldots,x_n]&lt;/math&gt;

We can relate rings to one another using a '''morphism''' of rings. A function &lt;math&gt;\phi: R \to S&lt;/math&gt; between rings is a morphism of rings if the following two axioms are satisfied
# &lt;math&gt;\phi(a + b) = \phi(a) + \phi(b)&lt;/math&gt; (Additivity)
# &lt;math&gt;\phi(ab) = \phi(a)\phi(b)&lt;/math&gt; (Multiplicativity)
we could have stated this succinctly as a function which respects the ring structure. It turns out that rings with ring morphisms form a category &lt;math&gt;\textbf{CRing}&lt;/math&gt;. As an important technical note, there is no zero-ring given by a single element in our category. This category has an initial object given by the ring of integers because given a ring morphisms
: &lt;math&gt;\phi:\mathbb{Z} \to R&lt;/math&gt;
the ring morphism axioms forces
:&lt;math&gt;\phi(1) = 1_R&lt;/math&gt;, &lt;math&gt;\phi(-1) = -1_R&lt;/math&gt;, and &lt;math&gt;\phi(n) = \phi\left(\sum_n 1\right) = \sum_n \phi(1)&lt;/math&gt;
Recall that the category of &lt;math&gt;R&lt;/math&gt;-algebras has objects given by ring morphisms &lt;math&gt;R \to S&lt;/math&gt; and morphisms given by commutative diagrams
&lt;blockquote&gt;&lt;math&gt;\begin{matrix}
 &amp;&amp;  S \\
 &amp; \nearrow\\
R &amp;&amp; \downarrow \phi \\
&amp; \searrow \\
&amp;&amp; S'
\end{matrix}&lt;/math&gt;&lt;/blockquote&gt;If we consider only algebras, the category &lt;math&gt;\mathbb{Z}-\textbf{CAlg}&lt;/math&gt; is equivalent to the category &lt;math&gt;\textbf{CRing}&lt;/math&gt;. Note that it is common to consider the categories &lt;math&gt;\mathbb{F}_q-\textbf{CAlg}&lt;/math&gt;, &lt;math&gt;\mathbb{C}-\textbf{CAlg}&lt;/math&gt;, &lt;math&gt;\mathbb{Q}_p-\textbf{CAlg}&lt;/math&gt;. The motivation for why will be readily apparent when considering categories of schemes.

===Ideals===
One of the ways to construct new rings is by taking quotient rings. An ideal of a ring is a subset &lt;math&gt;I \subset R&lt;/math&gt; which is
# An abelian group under addition
# &lt;math&gt;R\cdot I \subset R&lt;/math&gt;
Then, we can take the quotient of abelian groups &lt;math&gt;R/I&lt;/math&gt; and use the multiplicative structure on &lt;math&gt;R&lt;/math&gt; to construct one on &lt;math&gt;R/I&lt;/math&gt;. The second axiom of ideals guarantees that this is well-defined. This is called a '''quotient ring'''. Some typical examples of quotient rings are given by
* &lt;math&gt;\mathbb{Z}/(p)&lt;/math&gt;
* &lt;math&gt;\mathbb{Z}[x]/(x^2 - 5) \cong \mathbb{Z}[\sqrt{5}]&lt;/math&gt;
* &lt;math&gt;\mathbb{Q}[x]/(x^p-1)&lt;/math&gt;
* &lt;math&gt;
\frac{\mathbb{Z}[x_1,\ldots,x_n]}{(f_1,\ldots,f_k)}
&lt;/math&gt;
===Playing with Presentations===
As we have seen, there are many ways to construct polynomial ring; but, another interesting technique for creating new polynomial rings is to attach variables which have relations between them. For example, consider &lt;math&gt;\mathbb{Z}[x,x^2,x^3]&lt;/math&gt;. We can relabel the elements we've attached, so we consider the ring &lt;math&gt;\mathbb{Z}[X,Y,Z]&lt;/math&gt;, but there are a couple relations between these variables: 
:&lt;math&gt;X^2 - Y, XY - Z&lt;/math&gt;
note that these two relations can be used to show others such as &lt;math&gt;XZ - Y^2&lt;/math&gt; and &lt;math&gt;X^3 - Z&lt;/math&gt;. Hence
:&lt;math&gt;\mathbb{Z}[x,x^2,x^3] \cong  \frac{\mathbb{Z}[X,Y,Z]}{(X^2 - Y, XY - Z)}&lt;/math&gt;
Some other examples include
*&lt;math&gt;\mathbb{Z}[x,x^{3/2}] \cong \frac{\mathbb{Z}[X,Y]}{(Y^2 - X^3)} &lt;/math&gt;
*&lt;math&gt;\mathbb{Z}[x^2,xy,y^2] \cong \frac{\mathbb{Z}[X,Y,Z]}{(XZ - Y^2)}&lt;/math&gt;
*&lt;math&gt;\mathbb{Z}[x^3,x^2y,xy^2,y^3] \cong \frac{\mathbb{Z}[X,Y,Z,W]}{(XW - YZ, XZ - Y^2, YW - Z^2)}&lt;/math&gt;
===Prime Ideals===
There are a special class of ideals called '''prime ideals''': an ideal &lt;math&gt;\mathfrak{p}&lt;/math&gt; in a UFD &lt;math&gt;R&lt;/math&gt; is prime if
:&lt;math&gt;xy \in \mathfrak{p} \Leftrightarrow x \in \mathfrak{p} \text{ or } y \in \mathfrak{p}&lt;/math&gt;
For example, &lt;math&gt;(p) \subset \mathbb{Z}&lt;/math&gt; is the first known example of a prime ideal. It should be apparent that &lt;math&gt;(6)&lt;/math&gt; is not a prime ideal since &lt;math&gt; 2\cdot 3 \in (6)&lt;/math&gt; but &lt;math&gt;2,3 \not\in (6)&lt;/math&gt;. Now, given an irreducible polynomial &lt;math&gt;f \in S[x_1,\ldots,x_n]&lt;/math&gt; the ideal &lt;math&gt;(f)&lt;/math&gt; will be prime. A simple non-example of a prime ideal is given by &lt;math&gt;(xy) \subset \mathbb{C}[x,y]&lt;/math&gt;. This can be generalized to &lt;math&gt;(fg) \subset S[x_1,\ldots,x_n]&lt;/math&gt;. Some other examples of prime ideals include
:&lt;math&gt;(x^2 + 1) \subset \mathbb{Q}[x]&lt;/math&gt;
:&lt;math&gt;(x-\alpha) \subset \mathbb{C}[x]&lt;/math&gt;
:&lt;math&gt;(y^2 - x^3 + 1) \subset \mathbb{C}[x,y]&lt;/math&gt;
If you take the quotient ring of a prime ideal in a UFD &lt;math&gt;R&lt;/math&gt; you get an '''integral domain'''. This means your ring has the following multiplicative property:
:&lt;math&gt;xy = 0&lt;/math&gt; if &lt;math&gt;x=0&lt;/math&gt; or &lt;math&gt;y=0&lt;/math&gt;
For example, in
:&lt;math&gt; \frac{\mathbb{C}[x,y]}{(y^2 - x^3)}&lt;/math&gt;
you will never be able to multiply two non-zero elements together to get zero. The two key non-examples of a ring being an integral domain are
:&lt;math&gt;\mathbb{C}[x,y]/(xy)&lt;/math&gt; since &lt;math&gt;xy = 0&lt;/math&gt;
:&lt;math&gt;\mathbb{C}[x]/(x^2)&lt;/math&gt; since &lt;math&gt; x \cdot x = 0&lt;/math&gt;
''In general'', an ideal &lt;math&gt;\mathfrak{p}&lt;/math&gt; of a ring &lt;math&gt;R&lt;/math&gt; is called '''prime''' if &lt;math&gt;R/\mathfrak{p}&lt;/math&gt; is an integral domain. If &lt;math&gt;R/\mathfrak{m}&lt;/math&gt; is also a field, then we call &lt;math&gt;\mathfrak{m}&lt;/math&gt; a '''maximal ideal'''. One useful exercise is to check that for a morphism &lt;math&gt;f:R \to S&lt;/math&gt; and a prime ideal &lt;math&gt;\mathfrak{p}\subset S&lt;/math&gt; the inverse image &lt;math&gt;f^{-1}(\mathfrak{p})&lt;/math&gt; is a prime ideal.  The second example motivates the operation of taking radicals of an ideal. Given an ideal &lt;math&gt;I\subseteq R&lt;/math&gt; we define its radical as&lt;blockquote&gt;&lt;math&gt;\sqrt{I} = \{ f \in R : f^k \in I \text{ for some } r \in \mathbb{N} \}&lt;/math&gt;&lt;/blockquote&gt;For example, the radical of the ideal &lt;math&gt;((x^2 - y + z)^4(xyz - z^2)^5)\subset \mathbb{Z}[x,y,z]&lt;/math&gt; is &lt;math&gt;((x^2 - y + z)(xyz - z^2))&lt;/math&gt;.  Given a quotient ring &lt;math&gt;R/I&lt;/math&gt; we call the ring &lt;math&gt;R/\sqrt{I}&lt;/math&gt; its reduction; sometimes this is denoted &lt;math&gt;(R/I)_{\text{red}}&lt;/math&gt;. We define the '''nilradical''' of a ring &lt;math&gt;R&lt;/math&gt; as &lt;math&gt;\sqrt{(0)}&lt;/math&gt;. The nonzero elements in the nilradical are called '''nilpotents'''.

===Eisenstein's Criterion and Constructing Prime Ideals===
There is a generalization of Eisenstein's criterion for integral domains: given a ring &lt;math&gt;R&lt;/math&gt; and a polynomial &lt;math&gt;f(x) \in R[x]&lt;/math&gt; which can be written as
:&lt;math&gt;f(x) = a_nx^n + a_{n-1}x^{n-1} + \cdots + a_1x + a_0&lt;/math&gt;
then it cannot be written as a product of polynomials if the following conditions are satisfied: Suppose there exists a prime ideal &lt;math&gt;\mathfrak{p}\subset R&lt;/math&gt; such that
:&lt;math&gt;
\begin{align}
a_i \in \mathfrak{p} \text{ for } i \neq n \\
a_n \not\in \mathfrak{p} \\
a_0 \not\in \mathfrak{p}^2
\end{align}
&lt;/math&gt;
then &lt;math&gt;f(x)&lt;/math&gt; cannot be written as a product of polynomials &lt;math&gt;g_1(x)\cdots g_k(x)&lt;/math&gt;.

For example, consider the integral domain &lt;math&gt;\mathbb{C}[x]&lt;/math&gt; and the polynomial &lt;math&gt;f \in \mathbb{C}[x][y]&lt;/math&gt; given by
:&lt;math&gt;f(x,y) = 1\cdot y^3 + 0\cdot y^2 + 0\cdot y + x^3\cdot y^0 = y^3 + x^3&lt;/math&gt;
Using the prime ideal &lt;math&gt;(x-1)\subset \mathbb{C}[x]&lt;/math&gt; we have that &lt;math&gt;a_1,a_2=0 \in (x-1)&lt;/math&gt;, &lt;math&gt;a_3 = 1 \not\in (x-1)&lt;/math&gt;, and &lt;math&gt;a_0 = x^3 \not\in (x-1)^2&lt;/math&gt;. Hence
:&lt;math&gt;(x^3 + y^3) \subset \mathbb{C}[x,y]&lt;/math&gt;
is a prime ideal. This example can be extended to show that
:&lt;math&gt;x_1^{k_1} + \cdots + x_n^{k_n} \in \mathbb{C}[x_1,\ldots,x_n]&lt;/math&gt;
generates a prime ideal.

===Nullstellensatz===
Now we are in the right place to discuss the foundational theorem of algebraic geometry: '''Hilbert's nullstellensatz'''. Here we fix &lt;math&gt;k&lt;/math&gt; as an algebraically closed field.

'''Theorem:''' The maximal ideals of &lt;math&gt;\mathfrak{m}\subset k[x_1,\ldots,x_n]&lt;/math&gt; are in bijection with the set &lt;math&gt;k^n&lt;/math&gt;.

For example, the kernel of &lt;math&gt;\text{ev}_{(1,2)}:\mathbb{C}[x,y] \to \mathbb{C}&lt;/math&gt; is the ideal &lt;math&gt;(x-1,y-2)&lt;/math&gt;. This allows one to interpret quotient rings give by ideals &lt;math&gt;I \subset k[x_1,\ldots,x_n]&lt;/math&gt; as algebraic subsets of &lt;math&gt;k^n&lt;/math&gt; because an evaluation morphism&lt;blockquote&gt;&lt;math&gt;\text{ev}_{(\alpha_1,\ldots,\alpha_n)}:\mathbb{C}[x_1,\ldots,x_n]/I \to \mathbb{C}&lt;/math&gt;&lt;/blockquote&gt;is well-defined only if &lt;math&gt;(x_1-\alpha_1,\ldots,x_n-\alpha_n) \subset k[x_1,\ldots,x_n]/I&lt;/math&gt; is a maximal ideal. For example, consider the following example and non-example:
* &lt;math&gt;\text{ev}_{(1,1)}:\mathbb{C}[x,y]/(y-x^2) \to \mathbb{C}&lt;/math&gt; is a well defined morphism since&lt;math&gt;(x-1,y-1,y^2 - x) = (x-1,y-1,1^2 - 1) = (x-1,y-1)&lt;/math&gt;This implies that &lt;math&gt;(1,1) \in \{ (a,b) \in \mathbb{C}^2 : b^2 - a\}&lt;/math&gt;
* &lt;math&gt;\text{ev}_{(1,2)}:\mathbb{C}[x,y]/(y-x^2) \to \mathbb{C}&lt;/math&gt; is not a well-defined morphism because &lt;math&gt;(x-1,y-2,y^2-x) = (x-1,y-2,4-1) = (1)&lt;/math&gt;; there is no quotient ring &lt;math&gt;R/(1)&lt;/math&gt;. Hence &lt;math&gt;(1,2) \not\in \{ (a,b) \in \mathbb{C}^2 : b^2 - a\}&lt;/math&gt;
Now we can interpret rings which are not integral. For example, we saw that &lt;math&gt;\mathbb{C}[x,y]/(xy)&lt;/math&gt; is not an integral domain. Geometrically, this is the union of the &lt;math&gt;x&lt;/math&gt; and &lt;math&gt;y&lt;/math&gt; axes. The other main case of a non-integral ring is a non-reduced ring. For example, &lt;math&gt;\mathbb{C}[x,y]/(y^3)&lt;/math&gt; is the &lt;math&gt;x&lt;/math&gt;-axis but there is extra algebraic information from the &lt;math&gt;y,y^2&lt;/math&gt; left over. The way you should interpret this ring as is a '''fat''' line.

=== Basic Scheme Theory ===
We can now ''confidently'' define an affine scheme: it is a functor&lt;blockquote&gt;&lt;math&gt;\text{Hom}_\mathbf{CRing}(R,-): \mathbf{CRing} \to \textbf{Sets}&lt;/math&gt;&lt;/blockquote&gt;for some fixed commutative ring &lt;math&gt;R&lt;/math&gt;.

=== Localization ===
The next basic construction in commutative ring theory is '''localization'''. This defines a generalization of inverting the non-zero integers and getting the rational numbers. Let &lt;math&gt;S\subset R&lt;/math&gt; be a multiplicatively closed subset with unity, meaning &lt;math&gt;1 \in S&lt;/math&gt; and &lt;math&gt; s,s' \in S \Rightarrow ss' \in S&lt;/math&gt;. For example, for a fixed element &lt;math&gt;f \in R&lt;/math&gt; consider the subset &lt;math&gt;\{1,s,s^2,s^3,\ldots\}&lt;/math&gt;. We define a commutative ring &lt;math&gt;R[S^{-1}]&lt;/math&gt; as follows. First, consider the set &lt;math&gt;R\times S / \sim&lt;/math&gt;  where&lt;blockquote&gt;&lt;math&gt;(r,s) \sim (r',s') \text{ if there exists } u \in S \text{ such that } u(rs' - r's) =0&lt;/math&gt;&lt;/blockquote&gt;(don't worry, we will given a motivating example for this seemingly random &lt;math&gt;u&lt;/math&gt;). It is an exercise to verify that this indeed defines an equivalence relation — it is standard to write these equivalence classes as &lt;math&gt;r/s&lt;/math&gt;. These equivalence classes have a well-define commutative ring structure given by&lt;blockquote&gt;&lt;math&gt;\frac{r}{s} \cdot \frac{r'}{s'} = \frac{rr'}{ss'} \text{ and } \frac{r}{s} + \frac{r'}{s'} = \frac{rs' + r's}{ss'}&lt;/math&gt;&lt;/blockquote&gt;Some basic examples of localization include
* The subset &lt;math&gt;S = \{1,p,p^2,p^3,\ldots\} \subset \mathbb{Z}&lt;/math&gt; gives the ring &lt;math&gt;\mathbb{Z}[S^{-1}] = \mathbb{Z}[1/p]&lt;/math&gt;. Notice that if we localized by the set &lt;math&gt;T = \{1,p^3,p^6,p^9,\ldots\} \subset \mathbb{Z}&lt;/math&gt; then this gives the ring &lt;math&gt;\mathbb{Z}[1/p^3]&lt;/math&gt;. But, because we could write &lt;math&gt;1/p&lt;/math&gt; as &lt;math&gt;p^2/p^3&lt;/math&gt;, these two rings are isomorphic. For brevity, we could just say that we localized &lt;math&gt;\mathbb{Z}&lt;/math&gt; by &lt;math&gt;p&lt;/math&gt;. Try localizing by some other non-zero integers and see why you find.
* An important geometric example is given by localizing by some non-zero polynomial &lt;math&gt;f = f_1^{i_1}\cdots f_k^{i_k} \in \mathbb{C}[x_1,\ldots,x_n]&lt;/math&gt;. 
* Given an integral domain &lt;math&gt;R&lt;/math&gt;, we can take the set &lt;math&gt;S = R-\{0\}&lt;/math&gt;. Then, &lt;math&gt;R[S^{-1}]&lt;/math&gt; is called the '''field of fractions''' of the integral domain. (It is an exercise to check that this is a field) 
* Given a ring &lt;math&gt;R&lt;/math&gt; and a prime ideal &lt;math&gt;\mathfrak{p}&lt;/math&gt;, we can consider the set &lt;math&gt;S = R -\mathfrak{p}&lt;/math&gt;. This is multiplicatively closed because of the properties of primality of an ideal. The localization of &lt;math&gt;R&lt;/math&gt; by &lt;math&gt;S&lt;/math&gt; is typically denoted &lt;math&gt;R_\mathfrak{p}&lt;/math&gt;. For example, consider &lt;math&gt;(x,y) \subset \mathbb{C}[x,y]&lt;/math&gt;. The localization can be described as
&lt;blockquote&gt;&lt;math&gt;\mathbb{C}[x,y][S^{-1}] =  \mathbb{C}[x,y]_{\mathfrak{p}} = \left\{ \frac{f(x,y)}{g(x,y)} : f,g \in \mathbb{C}[x,y] \text{ and } g(0,0) \neq 0 \right\}&lt;/math&gt;&lt;/blockquote&gt;The last example is special because it motivates a definition: a ring is '''local''' if it has a unique maximal ideal. The pair &lt;math&gt;(R_\mathfrak{p},\mathfrak{p})&lt;/math&gt; is a local ring.

===Basic Module Theory===
A &lt;math&gt;R&lt;/math&gt;-module is defined as an abelian group &lt;math&gt;M&lt;/math&gt; with a fixed ring morphism &lt;math&gt;\phi:R \to \text{End}_{\textbf{Ab}}(M)&lt;/math&gt;. We will use the notation
:&lt;math&gt;r\cdot m := \phi(r)(m)&lt;/math&gt; where &lt;math&gt;r\in R, m \in M&lt;/math&gt;
for the ring action on &lt;math&gt;M&lt;/math&gt;. A morphism of &lt;math&gt;R&lt;/math&gt;-modules &lt;math&gt;\psi:M\to M'&lt;/math&gt; is defined by a commutative diagram
&lt;blockquote&gt;&lt;math&gt;\begin{matrix}
 &amp;&amp; \text{End}_{\textbf{Ab}}(M) \\
 &amp; \nearrow\\
R &amp;&amp; \downarrow \psi \\
&amp; \searrow \\
&amp;&amp; \text{End}_{\textbf{Ab}}(M')
\end{matrix}&lt;/math&gt;&lt;/blockquote&gt;
We can use this construction to build a category of &lt;math&gt;R&lt;/math&gt;-modules which is '''abelian'''. This means that it has a zero object, kernels and cokernels, products and coproducts, and images/co-images agree.
Please note that we've had to enlarge our category of commutative rings to all rings since the endomorphism ring of an abelian group is generally non-commutative; This is one of the only cases where we use non-commutative unital rings in this book. Typical examples of &lt;math&gt;R&lt;/math&gt;-modules includes
* the zero object &lt;math&gt;0&lt;/math&gt;
* ideals &lt;math&gt;I\subset R&lt;/math&gt;
* direct sums, such as &lt;math&gt;M_1\oplus \cdots \oplus M_k&lt;/math&gt;
* a morphism &lt;math&gt;\phi:R\to S&lt;/math&gt; of rings gives the structure of an &lt;math&gt;R&lt;/math&gt;-module on the underlying abelian group of &lt;math&gt;S&lt;/math&gt;
Another useful technique for constructing new modules is taking the cokernel of a morphism &lt;math&gt;\psi:R^n \to R^m&lt;/math&gt;. For example, the cokernel of&lt;blockquote&gt;&lt;math&gt;\mathbb{C}[x,y,z]^{\oplus 2} \xrightarrow{\cdot (x^4 + y^4 + z^4 - 1)\oplus \cdot (x^4 - y^2 + z^2 + 1)} \mathbb{C}[x,y,z]&lt;/math&gt;&lt;/blockquote&gt;is &lt;math&gt;\mathbb{C}[x,y,z]/(x^4 + y^4 + z^4 - 1,x^4 - y^2 + z^2 + 1)&lt;/math&gt;. We can generalize this example using '''exact sequences'''. A sequence of objects in an abelian category
&lt;blockquote&gt;&lt;math&gt;
M_1\xrightarrow{\phi_1}M_2 \xrightarrow{\phi_2} \to \cdots \xrightarrow{\phi_{n-1}} M_n
&lt;/math&gt;
&lt;/blockquote&gt;is called exact if each
:&lt;math&gt;\frac{\text{Ker}(\phi_i)}{\text{Ker}(\phi_{i-1})} \cong 0&lt;/math&gt;
in the last example, we had the exact sequence
:&lt;math&gt; R^{\oplus2} \to R \to M \to 0&lt;/math&gt;
In general, if there is an exact sequence
:&lt;math&gt;R^n \to R^m \to M \to 0&lt;/math&gt;
for finite integers &lt;math&gt;m,n&lt;/math&gt;, then we say that the module is '''of finite-type'''. If there is just a sequence
:&lt;math&gt;R^n \to M \to 0&lt;/math&gt;
then we say that the module is '''finite'''. For example, the module
:&lt;math&gt;k[x_1,x_2,\ldots] \to k \to 0&lt;/math&gt;
is finite but not finite-type since the kernel of the non-trivial morphism is the ideal
:&lt;math&gt;(x_1,x_2,\ldots) \cong \bigoplus_{i=1}^\infty R\cdot x_i&lt;/math&gt;

===Tensor Products===
* construct tensor products for modules
* construct tensor products of algebras
** show that tensor products of integral domains are integral
*** show that &lt;math&gt;k[\underline{x}]/(f(\underline{x})\otimes_k k[\underline{y}]/(g(\underline{y})) \cong k[\underline{x},\underline{y}]/(f(\underline{x}, g(\underline{y}))&lt;/math&gt;
*** show &lt;math&gt;k[\underline{x}]/(f(\underline{x}))\otimes_{k[\underline{x}]}k[\underline{x}]/(g(\underline{x})) \cong k[\underline{x}]/(f(\underline{x}),g(\underline{x}))&lt;/math&gt;

===Finiteness, Chain Conditions===
If we have an &lt;math&gt;R&lt;/math&gt;-algebra &lt;math&gt;R \to S&lt;/math&gt; we say that &lt;math&gt;S&lt;/math&gt; it is a '''finite''' if it is finite as a module. We say that it is '''of finite-type''' if there exists a surjective morphism &lt;math&gt;R[x_1,\ldots,x_n] \to S&lt;/math&gt;, implying that
:&lt;math&gt;S \cong \frac{R[x_1,\ldots,x_n]}{(f_1,\ldots,f_k)}&lt;/math&gt;

There are a couple other notions of &quot;finiteness&quot; which appear in commutative algebra called '''chain conditions'''. We say call a sequence of &lt;math&gt;R&lt;/math&gt;-modules
:&lt;math&gt;M_1\subseteq M_2\subseteq \cdots&lt;/math&gt;
an '''ascending chain''' and
:&lt;math&gt; N_1\supseteq N_2 \supseteq \cdots&lt;/math&gt;
a '''descending chain'''. They satisfy the '''ascending chain condition''' or '''descending chain condition''' if there is some &lt;math&gt;k&lt;/math&gt; such that &lt;math&gt;M_k=M_{k+1}=\cdots&lt;/math&gt;, &lt;math&gt;N_k=N_{k+1}=N_{k+2}=\cdots&lt;/math&gt;. If there exist chains
:&lt;math&gt;M_1\subseteq M_2 \subseteq \cdots&lt;/math&gt; where &lt;math&gt; \cup^\infty_{i=1}M_i = R&lt;/math&gt;
or
:&lt;math&gt;R\supseteq N_2 \supseteq \cdots&lt;/math&gt;
then we say &lt;math&gt;R&lt;/math&gt; is '''Noetherian''' or '''Artinian''', respectively. One can show that every Artinian ring is Noetherian. The basic examples of Noetherian rings include
* Fields
* &lt;math&gt;\mathbb{Z}&lt;/math&gt;
* Finite algebras over fields
* Quotients of Noetherian rings.
A simple non-example is given by the ring &lt;math&gt;k[x_1,x_2,x_3,\ldots]&lt;/math&gt; where &lt;math&gt;k&lt;/math&gt; is a field. There is a fundamental theorem in algebra called '''Hilbert's Basis Theorem''' stating:&lt;blockquote&gt;'''Theorem:''' If &lt;math&gt;R&lt;/math&gt; is Noetherian, then &lt;math&gt;R[x_1,\ldots,x_n]&lt;/math&gt; is Noetherian&lt;/blockquote&gt;Hence all rings of the form&lt;blockquote&gt;&lt;math&gt;\frac{R[x_1,\ldots,x_n]}{(f_1,\ldots,f_k)}&lt;/math&gt;&lt;/blockquote&gt;are Noetherian. Artinian rings are much simpler than Noetherian rings:&lt;blockquote&gt;'''Theorem:''' Every Artin ring is a finite product of Artin local rings.&lt;/blockquote&gt;All we have to analyze is the structure of an Artin local ring &lt;math&gt;(R,\mathfrak{m})&lt;/math&gt;. Notice that we have a descending chain&lt;blockquote&gt;&lt;math&gt;R \supseteq \mathfrak{m} \supseteq \mathfrak{m}^2 \supseteq \mathfrak{m}^3 \supseteq \cdots&lt;/math&gt;&lt;/blockquote&gt;which eventually stabilizes at some &lt;math&gt;\mathfrak{m}^k&lt;/math&gt;; this is the zero ideal &lt;math&gt;(0)&lt;/math&gt;. We can use this to show the underlying &lt;math&gt;R/\mathfrak{m}&lt;/math&gt;-vector space of &lt;math&gt;R&lt;/math&gt; is finite dimensional. Some examples of artin local rings are
* &lt;math&gt;(\mathbb{C}[x]/(x^5), (x))&lt;/math&gt;
* &lt;math&gt;(\mathbb{Q}[x,y]/((x-1)^3,(x-1)^2(y-2),(y-2)^5)), (x-1,y-2))&lt;/math&gt;

=== Integrality ===
Given a morphism of commutative rings &lt;math&gt;R \to R'&lt;/math&gt; we say an element &lt;math&gt;x \in R'&lt;/math&gt; is '''integral''' over &lt;math&gt;R&lt;/math&gt; if there is a monic polynomial &lt;math&gt;f(t) = t^n + a_{n-1}t^{n-1} +\cdot + a_1t + a_0 \in R[t] &lt;/math&gt;and a morphism&lt;blockquote&gt;&lt;math&gt;\frac{R[t]}{f(t)} \to R'&lt;/math&gt;&lt;/blockquote&gt;sending &lt;math&gt;t \mapsto x&lt;/math&gt;. For example, &lt;math&gt;\sqrt{-5} \in \mathbb{Z}[\sqrt{-5}]&lt;/math&gt; is integral over &lt;math&gt;\mathbb{Z}&lt;/math&gt; since&lt;blockquote&gt;&lt;math&gt;\frac{\mathbb{Z}[t]}{(t^2 + 5)} \cong \mathbb{Z}[\sqrt{-5}]&lt;/math&gt;&lt;/blockquote&gt;Adjoining all of the integral elements &lt;math&gt;\{x_i\}&lt;/math&gt; &lt;math&gt;R&lt;/math&gt; is called the '''integral closure of''' &lt;math&gt;R&lt;/math&gt; '''in''' &lt;math&gt;R'&lt;/math&gt;.  An integral domain &lt;math&gt;R&lt;/math&gt; is called '''integrally closed''' if every element in its fraction field is integral over &lt;math&gt;R&lt;/math&gt;. For example, we can compute the integral closure of&lt;blockquote&gt;&lt;math&gt;R = \frac{\mathbb{C}[x,y]}{(x^2 - y^3)}&lt;/math&gt;&lt;/blockquote&gt;fairly easily. Since it is isomorphic to the ring &lt;math&gt;\mathbb{C}[x,x^{3/2}]&lt;/math&gt; we should see immediately that &lt;math&gt;x^{1/2}&lt;/math&gt; is not contained in &lt;math&gt;R&lt;/math&gt;. Adjoining this element to &lt;math&gt;R&lt;/math&gt; gives a ring isomorphic to &lt;math&gt;\mathbb{C}[s]&lt;/math&gt;. As an exercise, try and unpack&lt;blockquote&gt;&lt;math&gt;\frac{\mathbb{C}[x,y,z,w]}{(x^2 - y^5 - y^3, z^3 - w^4)}&lt;/math&gt;&lt;/blockquote&gt;TODO:

- hyperelliptic curves

- quotient fields of curves

- https://math.stackexchange.com/questions/2304521/why-is-this-coordinate-ring-integral-over-kx

- rings of integers

== Chapter 0 ==

=== Basic Commutative Algebra ===

==== Structures ====
* tensor products of modules/algebras... localization of modules
* categories of commutative algebras
* support of modules
* graded rings
* colimits and stalks
* limits, completions, p-adics
* valuations - https://en.wikipedia.org/wiki/Valuation_(algebra)#P-adic_valuation_on_a_Dedekind_domain
* dimension
* transcendence degree
* functor formalism
* categorical structures such as pullbacks and pushforwards
* kahler differentials/ basic differential algebra
* smooth algebras/smooth morphisms
* complete intersection/local complete intersection morphisms
* etale algebras/etale morphisms
* galois theory with useful terminology...
* same w/ algebraic number theory terminology...
* basic homological algebra, ext, tor
* koszul complexes
* derived categories
* grothendieck group
* hilbert polynomial
* grobner bases/elimination theory - https://mathoverflow.net/questions/60957/how-to-determine-whether-an-ideal-is-prime-or-not-by-an-algorithm

==== Theorems ====
* Eisenstein's Criterion
* Primary Decomposition
* Noether Normalization
* Going up and down

=== Basic Differential/Complex Geometry ===

==== Constructions ====
* Smooth manifolds
* Morphisms
* Vector Bundles
* Topological K-theory
* de-Rham Cohomology
* Complex manifolds and sheaves
* hodge decomposition of complex manifolds

=== Theorems ===
* Whitney embedding theorem
* Submersion theorem
* Sard's theorem

{{BookCat}}</text>
      <sha1>ar92so9tv1lvcz247phreutf04dhkms</sha1>
    </revision>
  </page>
  <page>
    <title>User:Kaliru/Barnstars</title>
    <ns>2</ns>
    <id>407387</id>
    <revision>
      <id>4669015</id>
      <parentid>3547213</parentid>
      <timestamp>2026-09-05T19:30:59Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669015</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1643" sha1="3uziq77769hw4hujqhgypnftm82jirf" xml:space="preserve">{{User:Kaliru/navbar}}
== Thank you for being one of Wikipedia's top medical contributors! ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
:''please help translate this message into your local language via [https://meta.wikimedia.org/wiki/Wiki_Project_Med/The_Cure_Award meta]''
{| style=&quot;background-color: #fdffe7;{{Text default color}}; border: 1px solid #fceb92;&quot;
|rowspan=&quot;2&quot; style=&quot;vertical-align: middle; padding: 5px;&quot; | [[File:Wiki Project Med Foundation logo.svg|100px]]
|style=&quot;font-size: x-large; padding: 3px 3px 0 3px; height: 1.5em;&quot; |'''The 2018 Cure Award''' 
|-
| style=&quot;vertical-align: middle; padding: 3px;&quot; |In 2018 you were one of the [[W:EN:Wikipedia:WikiProject Medicine/Stats/Top medical editors 2018 (all)|top ~250 medical editors]] across any language of Wikipedia. Thank you from [[m:WikiProject_Med|Wiki Project Med Foundation]] for helping bring free, complete, accurate, up-to-date health information to the public. We really appreciate you and the vital work you do! Wiki Project Med Foundation is a [[meta:user group|user group]] whose mission is to improve our health content. Consider joining '''[[meta:Wiki_Project_Med#People_interested|here]]''', there are no associated costs.
|}

Thanks again :-)  -- [[W:EN:User:Doc James|&lt;span style=&quot;color:#0000f1&quot;&gt;'''Doc James'''&lt;/span&gt;]] along with the rest of the team at '''[[m:WikiProject_Med|Wiki Project Med Foundation]]''' 17:55, 28 சனவரி 2019 (UTC)
&lt;/div&gt;
&lt;!-- Message sent by User:Doc James@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Top_Medical_Editors_2018/other&amp;oldid=18822373 --&gt;</text>
      <sha1>3uziq77769hw4hujqhgypnftm82jirf</sha1>
    </revision>
  </page>
  <page>
    <title>Baroque Macedonia and the Macedonian Revolts/Chapter 3 : The gathering of troops</title>
    <ns>0</ns>
    <id>408710</id>
    <revision>
      <id>4669096</id>
      <parentid>4532896</parentid>
      <timestamp>2026-09-06T10:54:46Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <comment>typo</comment>
      <origin>4669096</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8223" sha1="jq75jpomr5ep9yj43fh98ahqzllk9o2" xml:space="preserve">
=== Chapter 3 ===


'''The gathering of troops'''


The Macedonians had also attempted a revolt back in the mid-16th century and this was one of the
very first revolts ever to occur. The local uprising took place in 1564, it began in the [[wikipedia:Mariovo|Mariovo]] region 
and spread to the Prilep plains and from there to the town of [[wikipedia:Prilep|Prilep]]. Known as the Mariovo and Prilep revolt, it is unknown 
why this revolt began, but it is clear that three peasants and two priests from the Mariovo district started it. No sooner had the trouble 
started when the Sultan, through a [[wikipedia:decree|decree]] dated October 3, 1564, ordered that the leaders of the revolt be put to death 
while the followers were to be sent to serve as oarsmen on Turkish galleys. Before the decree could be enforced, however the perpetrators fled 
causing the Sultan to order another decree for their capture. The [[wikipedia:Mariovo and Prilep rebellion|Mariovo and Prilep rebellion]] was one
that was unsuccessful and the rebellion was suppressed by the Ottoman troops. 
Prilep soon became a place known for demonstrations, when the Ottoman court ruled in favour of a Pasha in a dispute with the peasants. According to a document dated December 1565 a revolt broke out inside the town of Prilep. The situation began when the Prilep court, in settling a dispute between the peasants and Mustafa Pasha, ruled in favour of the Pasha. Later the news hit the streets and more than a thousand rebels from the surrounding villages, armed with garden shovels, and long barrelled muskets assembled and stormed the court. It is unknown how this situation or incident ended. As explained previously the peasants eventually had no chance in further causing trouble as the large Ottoman forces greatly enforced order upon the peasant rebels.

According to historical sources General Piccolomini was currently in the town of [[wikipedia:Nis|Nis]], Ottoman Serbia,
he arrived there on the 24th of September, 1689 in the early hours of the morning. With him was also the Austrian commander, 
[[wikipedia:Louis William, Margrave of Baden-Baden|Louis William, Margrave of Baden-Baden]].
Accompanying the two commanders was Pavle Nestorović who was a Serbian commander that assisted Piccolomini,
during the capture of Nis. Nis was a quite town located in the southern part of Ottoman Serbia, it had a [[wikipedia:garrison|garrison]]
of approximately 40,000 soldiers or most likely over 40,000. Louis William had a total of about 16,000 troops,
most of them were Austrian however there were also Serbian troops. When Louis William learned that there were no 
Ottoman defence positions on Vinik he ordered Pavle to attack. Eventually Pavle was successful and the Battle of
Nis ended with an Austrian victory. Pavle was promoted and later Louis William had decided to leave for 
[[wikipedia:Vidin|Vidin]] while Piccolomini was left to keep an eye on Nis. The next month Piccolomini left for
Ottoman Macedonia, and when this happened the Ottoman troops once again gained possession of the Sanjak of
Nis.

[[File:Musket01.jpg|thumb|A Macedonian soldier or rebel holding a heavy musket, circa 1610.]]


[[File:Maps 09.jpg|thumb|A cartographic map of Central Europe, circa 1806.]]

On the right we see a photo of a Macedonian rebel holding a heavy musket. These types of guns were very popular
during the first half of the 17th century. A musket is a muzzle-loaded long gun that appeared as a smoothbore weapon 
in the early 16th century, at first as a heavier variant of the [[wikipedia:arquebus|arquebus]] capable of penetrating 
heavy armor if fired correctly. Distinguished features of a heavy musket was a very long barrel, the reason for this
extremely long barrel was to gain a good or reasonable range. Evidence of the musket as a type of firearm does not appear 
until 1521, the long-barreled, musket-caliber weapons had been in use as wall-defense weapons in Europe and in other
continents. By 1650 the heavy musket eventually become obsolete due to its size and weight, as a result of this the
musket was improved. By 1690 the wearing of knights armor dramatically decreased, this was probably due to the increased
power of certain types of guns.

There are two sources regarding the arrival of Silvio Piccolomini to the city of Uskup (Skopje). General Piccolomini
arrived in Uskup in late October, 1689. One historical source explains that when General Piccolomini entered Uskup
he was greeted by the people of Uskup, and there was also a fanfare playing at the time, while the other historical
source explains that when he arrived to the city, the city was most likely abandoned and there was only a few people.
When General Piccolomini set out from the Habsburg Empire he had a total of 4,000 soldiers most of them were
cavalry, after the battle of Nis, his armies were reduced as some of them were killed in action or were injured and had
to remain behind. Overall his armies now were a small number, and this greatly affected his abilities to guard or even
defend a large city such as Uskup.

With General Piccolomini in Uskup, what happened to the Ottoman garrison that was stationed in Uskup ? Did they withdraw
from the city of Uskup after witnessing the Austrian armies entering the city, or was the city unguarded and no Ottoman
troops were positioned within the streets of Uskup ? These are just some questions that have puzzled the Macedonian 
historians. The answer to this question is that there were no Ottoman soldiers stationed within Uskup (Skopje) at the
time, because if there was then a fierce battle would break out. There was no armed conflict between the Ottoman troops
and the Austrian cavalry units within Uskup.

While staying in Skopje, Piccolomini started feeling very ill. He was unaware that he had contracted some form of disease.
According to historical accounts, Piccolomini had [[wikipedia:cholera|cholera]] and his health was beginning to deteriorate. Piccolomini had the following symptoms : diarrhea, vomiting, dehydration, and discoloration of the skin. It is unclear how Piccolomini contracted cholera, it was most likely through the drinking of contaminated water or the eating of food that was contaminated with the bacterium. Back in the late 17th Century (1601-1700) the medical knowledge relating to cholera was limited, doctors were uncertain as to what caused the disease, and their current medicines provided no relief or prevention from the bacterium.
 
Piccolomini was beginning to feel very weak due to the cholera, on the 26th of October, 1689 he ordered his armies to burn the city of Skopje. His troops placed gunpowder all around some of the buildings within the centre of Skopje and a fire was started. The [[wikipedia:Skopje fire of 1689|Skopje fire of 1689]] lasted two whole days, burning much of the wooden structures and buildings. The fire later spread towards the Jewish quarter of the city, the Jewish synagogue and a Jewish church was completely destroyed in the fire. However many of the stone buildings remained, but were blackened by the raging fire.
Due to General Piccolomini's health he had decided to disband from his armies, heading to Ottoman Albania.

General Piccolomini's reason for going to Ottoman Albania was so that he can board a ship and head back to Austria. In the cartographic map of Europe which is shown on the right, the Habsburg Empire also known as the Imperial Austrian Empire had access to the [[wikipedia:adriatic sea|adriatic sea]]. It was a small region just north of Ottoman Bosnia where Austria had a number of ports, here the galleons would arrive and unload. The prospects for Austrian arms in Macedonia and Albania looked promising, but a few days later Piccolomini died of the plague and his successor duke Georg Christian Von Holstein was unable to capitalize on the so called &quot; Karposh Uprising &quot; of the Christian peasantry which broke out in Macedonia at about this time.&lt;ref&gt;
Atlas of Southeast Europe : Geopolitics and History. Volume 1: 1521-1699, Author : Hans H.A Hotte. p.15 2015&lt;/ref&gt;
Eventually assistance from the Austrian armies ended and the continuation of the Karposh uprising went until December, 1689.

{{bookcat}}</text>
      <sha1>jq75jpomr5ep9yj43fh98ahqzllk9o2</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Benjamin Shepard</title>
    <ns>3</ns>
    <id>424053</id>
    <revision>
      <id>4669062</id>
      <parentid>3821111</parentid>
      <timestamp>2026-09-06T06:41:10Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669062</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4502" sha1="sadzlv4eazpvdy82xoup3fvdwbqzxyj" xml:space="preserve">== Welcome! ==

&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Benjamin Shepard!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;
--[[User:Mrjulesd|&lt;span style=&quot;color:orange;&quot;&gt;Jules&lt;/span&gt;]]&amp;nbsp;[[User talk:Mrjulesd|(Mrjulesd)]] 09:21, 26 March 2021 (UTC)</text>
      <sha1>sadzlv4eazpvdy82xoup3fvdwbqzxyj</sha1>
    </revision>
  </page>
  <page>
    <title>Template:Unichar/main</title>
    <ns>10</ns>
    <id>425117</id>
    <revision>
      <id>4669091</id>
      <parentid>3839290</parentid>
      <timestamp>2026-09-06T10:06:05Z</timestamp>
      <contributor>
        <username>Warudo</username>
        <id>3310627</id>
      </contributor>
      <comment>Passed the na parameter to /glyph.</comment>
      <origin>4669091</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1039" sha1="gl3feks5qj98q4f5bxop6t5swl9hei0" xml:space="preserve">{{#ifexpr:({{{dval|-1}}}=0) and ({{#ifeq:X{{{hval}}}|X0000 |0 |1}}) |&lt;!--(error triggered if X{{{hval}}} ≠ X0000:)--&gt;{{Error |tag=span |Error using {{tl|unichar}}: Input &quot;{{{hvalinput|}}}&quot; is not a [[hexadecimal]] value.}}
 | {{nowrap|{{{{#ifeq:{{{sans|}}}|y|sans-serif|mono}}|{{Unichar/ulink |ulink={{{ulink|&lt;#salted#&gt;}}} |ulinkdefault=Unicode}}{{{hval|}}}}}&amp;#x20;}}&lt;!--

   --&gt;{{Unichar/glyph |hval={{{hval|}}} |gc={{{gc|&lt;#not a Unicode code point#&gt;}}} |size={{{size}}}
                      |use={{{use|}}} |use2={{{use2|}}} |cwith={{{cwith|}}} |image={{{image|}}} |br={{{br|}}} |na={{{na|}}} }} &lt;!--

   --&gt;{{Unichar/name  |na={{{na|}}} |nlink={{{nlink|&lt;#salted#&gt;}}} |gc={{{gc|}}} }} &lt;!--

   --&gt;{{Unichar/notes |dval={{{dval|}}} |dec={{{dec|}}} |html={{{html|}}}
                      |char_entity={{#ifeq:{{{html|+}}}|{{{html|-}}} |{{#invoke:LoadData|Numcr2namecr|{{{dval|}}}}}}}
                      |note={{{note|}}} |finaltext={{{finaltext|NOTEXT}}} }}
}}&lt;!--

--&gt;&lt;noinclude&gt;{{Documentation|1=Template:Unichar/doc}}&lt;/noinclude&gt;</text>
      <sha1>gl3feks5qj98q4f5bxop6t5swl9hei0</sha1>
    </revision>
  </page>
  <page>
    <title>Writing Adolescent Fiction/Character names/Congolese</title>
    <ns>0</ns>
    <id>434722</id>
    <revision>
      <id>4669090</id>
      <parentid>4612863</parentid>
      <timestamp>2026-09-06T10:02:27Z</timestamp>
      <contributor>
        <username>~2026-48191-33</username>
        <id>3625303</id>
      </contributor>
      <comment>added the name Tshibenji (luba, 178)</comment>
      <origin>4669090</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3617" sha1="tvihmvq25ss4p0pv67j3srrnaewbuab" xml:space="preserve">Like many other African countries, the Congos have many tribes, each of those tribes having their own unique names.

kongo names 

Mavinga, Malanda, Mambwene, Tulunga, Masamba, Luyeye, Teholo, Mambweni, Mambu,Fimpa, Mateta, Tuzolana, Matumona, Matunwene, Malangi, Wasewa, Bukaka ,Mayala, Masukidi, Diawaku, Diakanua, Ndongala, Ndombele, Matondo, Mampasi, Sita, Luzolo, Nsimba, Nzuzi, Landu, Nsakala, Nsukula, Diyamona, Biyavanga, Zola, Nkiluku, Kimwina, Kukiele, Kuyela, Kuma, Kimbangu, Kisolokele, Diasivi, Mamona, Zolana, Batukweme, Wasewa, Nseyila, Nkembo, Nsambu, Siluvagi, Vangu, Nzumba, Nsukula, Mavoka, Bwene, Mbala, Mbunba, Sala, Diasivi, Dialungana, Banzola, Mbala, Mbemba, Bisala, Nsiluvangu, Bueyasa, Makiadi, Makiese, Bukaka, Mayenda, Kiala, Malanga, Manzambi, Ntunga, Mbambi, sela, Mavoka, Sumpi, Mabiala, Makiadi, Lengi, Tezo, Tekasala, Tangi, Kamwanako, Nseka, Manduakila, Teholo, Tezangi, Mbutu, Nsinsani, Maviokele, Diambuana, Lukombo, Lusikila, Luyeye, Nzazi, Vayemba, Yengo, Kiambukuta, Tulunga, Dilu, Kiamwangana, Diwete, Nzomuisi, Senga, Mpaka, Ntalu. 

==Kongo First names==
The kongo tribe makes a difference between first and last names. Most first names are gender neutral.

#Angola
#Angolo
#Kimpa
#Longi
#Luzolo
#Manzambi
#Masa
#Matondo
#Mawete
#Maza
#Mbuetete
#Mfumu
#Mfulutoma
#Miezi
#Muanda
#Mvemba
#Mvembaur
#Namibi
#N'semi
#Ntangu
#Ntinu
#Nzinga
#Nzola
#Sema
#Vita
#Wasakumunua
#Yulu
#Zayi
#Zulu

==Luba names ==

#Babanya
#Badiambila 
#Badibanga
#Badila
#Bakika
#Bakaji
#Bakatupenda
#Bajikijayi
#Balela
#Baloji
#Bambi
#Batubenga
#Beleshayi
#Bende(a)
#Biakabutuka
#Biakupa
#Bikuta
#Bintu
#Bitumba
#Biuma
#Bolayi
#Bulembi
#Buloba
#Diba
#Dibuba
#Dibwe(a)
#Dikasa
#Dikoba
#Ditu
#Ilonda
#Ilunda
#Ilunga
#Kabange(a)
#Kabasele
#Kabasubabo
#Kabatuswila
#Kabedi
#Kabeya
#Kabishi
#Kaboko
#Kabongo (boy's name)
#Kabose
#Kabudi
#Kabula
#Kabundi
#Kabungama
#Kadima
#Kakona
#Kalala
#Kalambayi
#Kalengayi
#Kalombo
#Kalonda
#Kalonji
#Kalwanda
#Kamanda
#Kamudimba
#Kamwanya
#Kambuji
#Kande(a)
#Kanjinga (girl's name)
#Kapela
#Kapeta
#Kapinga
#Kantu
#Kanubantu
#Kapuku
#Kasanda
#Kasanji
#Kasenda
#Kashala
#Kashama
#Kasukupa
#Kasumpata
#Kasusula
#Katanda (boy's name)
#Katuku
#Katuma
#Katumbi
#Kayembe
#Kazadi
#Kazambu
#Kidiaba
#Kimba
#Kitambala
#Kongolo
#Konji
#Luboya
#Lukoji
#Lukusa
#Lusamba
#Lwakanwanga 
#Kasanda
#Mambuyi
#Mampuya
#Mbelu
#Mbuyi
#Mbwaya
#Meji Mwamba
#Mfuni/Mfunyi
#Midibu / Midjibu
#Mikalayi 
#Misenga
#Mpoku
#Mputu
#Mpyana
#Mubiala
#Muboyayi
#Muci
#Mudiayi
#Mudimbe
#Mudingayi
#Mufuta
#Mujanayi
#Mujinga (girl's name)
#Mukeba
#Mukebayi
#Mukendi
#Mukenge
#Mukengeshayi
#Mukinayi 
#Mukoka 
#Mukuna
#Mukunayi
#Mukunyi
#Mukuta
#Mulamba
#Mulanga
#Mulenda
#Mulondo
#Mulongo
#Mulowa
#Mulowayi
#Mulumba
#Mulumbu
#Mulume
#Mumengi
#Muntu/Bantu
#Musanda
#Mushiya
#Musungayi
#Muswama
#Muswamba (wa ba Mbuyi)
#Muteba
#Mutoke
#Mutombo
#Mutshipayi
#Mvidiakuumpa
#Mwambi
#Mwepu
#Mwipatayi
#Ndala
#Ndaye(a)
#Ndomba
#Ndombela
#Nga(lu)lamulume
#Ngalula(mukaji)
#Ngandu
#Ngondu
#Ngoyi
#Nkala
#Nkashama
#Nsanga (Diboko)
#Nsanza
#Ntambwe
#Ntumba
#Ntumpula
#Nzadi
#Shambuyi
#Tshamba
#Tshambwe
#Tshiabu 
#Tshianza
#Tshibamba
#Tshibanda
#Tshibangu
#Tshibelu
#Tshibenji
#Tshibuabua
#Tshidinda Kasapa
#Tshiela (Makasa)
#Tshiende(a)
#Tshika
#Tshikala
#Tshikudimena
#Tshikuta
#Tshikuatakuata
#Tshilanda
#Tshilemba
#Tshilobo
#Tshilombo
#Tshilonga
#Tshimankinda
#Tshimanga
#Tshimpaka
#Tshinabu wa Munda
#Tshintu
#Tshingombe
#Tshinyama Tshiolola
#Tshiomba ou Tshomba
#Tshiowa (Mashi)
#Tshiowela
#Tshipamba
#Tshisekedi
#Tshiswabantu
#Tshiswaka
#Tshituka
#Tshomba
#Tumbishayi
#Tunda wa Munda
#Waku Menga

{{BookCat}}</text>
      <sha1>tvihmvq25ss4p0pv67j3srrnaewbuab</sha1>
    </revision>
  </page>
  <page>
    <title>Maxima/Data structures</title>
    <ns>0</ns>
    <id>438298</id>
    <revision>
      <id>4668961</id>
      <parentid>4668764</parentid>
      <timestamp>2026-09-05T17:26:51Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <comment>Work in progress. Saving Changes.</comment>
      <origin>4668961</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="64544" sha1="pk4i72rglnjn7148qknkvxch5hjzmdb" xml:space="preserve">== Maxima Aggregate Data Structures ==

=== Introduction ===
This book is intended to present some of the essentials of what is called Maxima aggregate data structures. By this it is meant the data types that can be used to refer to the values of expressions using a means of indexing of a single identifier (name) that refers to an aggregate (collection) of expressions as values.

Built-in aggregate data types include: 

* lists
* hashed arrays
* declared arrays
* structures

Each of these has a means of indexing an identifier that names an instance of these data types. 

Please note that it is the case that this means of indexing an identifier for an aggregate data type may be referred to as involving &quot;subscripts&quot; or &quot;sub-scripted variables&quot; or &quot;keys&quot; as used by various computer programming languages, as well as in the context of Maxima documentation and commentary. In this book terms such as &quot;index&quot; or &quot;indices&quot; or &quot;indexed identifiers&quot;  are used instead.

Also all built-in Maxima functions (including packages) for these data types are referred to as ''&quot;operators&quot;'' and not ''&quot;functions&quot;'' as this latter term in general serves better to refer to Maxima function expressions defined by the user -- as in &lt;code&gt;f(x) :=&lt;/code&gt;, &lt;code&gt;g[s] :=&lt;/code&gt; and &lt;code&gt;define ()&lt;/code&gt; as examples.

This section is not intended to be exhaustive. It is intended to provide familiarity with aggregate data types. What is included has been gleaned from various sources, and only a few attributions are provided. Therefore, there is no claim of originality implied. 

=== Lists ===

==== Introduction to Lists ====
Lists are one of the basic buildings block for Maxima and Lisp. Maxima expressions are in general represented as Lisp lists. 

For example, consider the Maxima expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	e+3;
(%o1)	e+3
&lt;/syntaxhighlight&gt;This expression has the form of a Lisp list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i2)	:lisp #$[e+3]$
((MLIST SIMP) ((MPLUS SIMP) 3 $E))
&lt;/syntaxhighlight&gt;An expression in the form of a Lisp list can also be be displayed as a Maxima expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i2)	:lisp (displa '((MLIST SIMP) ((MPLUS SIMP) 3 $E)));
[e+3]
NIL
&lt;/syntaxhighlight&gt;Note that the value of this expression using &lt;code&gt;displa '()&lt;/code&gt; is &lt;code&gt;NIL&lt;/code&gt;, and &lt;code&gt;[e+3]&lt;/code&gt; is simply displayed in Maxima list object form. It is not necessary for the typical uses of Maxima to utilize this insight into the role Lisp lists have as one of the building blocks for Maxima, but it may be useful to have a familiarity with that role. Lists are often used as arguments to many operators, and the values of expressions are often in the form of lists.

==== Some Operators for Lists ====
Lists are created explicitly and list elements referenced using &lt;code&gt;[&lt;/code&gt; and &lt;code&gt;]&lt;/code&gt; to mark the beginning and end, respectively, of an instance of a list object, or to reference the expressions of an existing list object.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i3)	[2,3,4];
(%o3)	[2,3,4]
&lt;/syntaxhighlight&gt;The expression &lt;code&gt;[2,3,4]&lt;/code&gt; creates a Maxima list object. In this case the object itself is not accessible as it was not assigned an identifier unless referenced by the &lt;code&gt;%&lt;/code&gt; , &lt;code&gt;%i&lt;/code&gt; or &lt;code&gt;%o&lt;/code&gt; label.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i4)	%;
(%o4)	[2,3,4]

(%i5)	%o4[2]; /* second expression of list object referenced by index */ 
(%o5)	3
&lt;/syntaxhighlight&gt;That [2,3,4] is a list object can be tested using the &lt;code&gt;listp()&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i6)	listp ([2,3,4]);
(%o6)	true
&lt;/syntaxhighlight&gt;A list object can be assigned an identifier:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i7)	s:[%pi,%e,%phi];
(s)	[%pi,%e,%phi]

(%i8)	listp (s);
(%o8)	true&lt;/syntaxhighlight&gt;

The value of an element of a list can be accessed using the list identifier and brackets with a index value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i9)	s[1];
(%o9)	%pi

(%i10)	s[2];
(%o10)	%e

(%i11)	s[3];
(%o11)	%phi
&lt;/syntaxhighlight&gt;
Invalid index values returns an error:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i12)	s[4];
inpart: invalid index 4 of list or matrix.
-- an error. To debug this try: debugmode(true);
&lt;/syntaxhighlight&gt;
Consider the following relatively long list of integer atoms created explicitly and identified as &lt;code&gt;List_1&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i13)	List_1:[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582,145,2,
	    118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,
	    30,3,484,51,3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,4,
	    484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,5,118,30,5,484,
	    
	    49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177];

(List_1)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,2,1582,203
,3,118,30,3,484,51,3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,
214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177]&lt;/syntaxhighlight&gt;
The number of values of this list can be returned using the &lt;code&gt;length()&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i14)	length (List_1);
(%o14)	105
&lt;/syntaxhighlight&gt;
Create another list identified as &lt;code&gt;List_2&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i15)	List_2 : [6,1455,200,6,1607,205];
(List_2)	[6,1455,200,6,1607,205]

(%i16)	length (List_2);
(%o16)	6
&lt;/syntaxhighlight&gt;
Create a third list identified as &lt;code&gt;List_3&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i17)	List_3 : append (List_1, List_2)$

(%i18)	length (List_3);
(%o19)	111
&lt;/syntaxhighlight&gt;
Note that the &lt;code&gt;'''append ()'''&lt;/code&gt; operator does not affect either of the list arguments &lt;code&gt;List_1&lt;/code&gt; or &lt;code&gt;List&lt;/code&gt;_2. It merely appends &lt;code&gt;List_2&lt;/code&gt; to &lt;code&gt;List_1&lt;/code&gt; and returns a new list, in this case assigned the identifier &lt;code&gt;List_3&lt;/code&gt;.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i20)	length (List_1);
(%o20)  105

(%i21)	length (List_2);
(%o21)  6

(%i22)	length (List_3);
(%o22)	111

(%i23)	List_3;
(%o23)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
         142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
         1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
         75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
         1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
         142,5,1372,174,5,1582,177,6,1455,200,6,1607,205]&lt;/syntaxhighlight&gt;
Values (the last one in this example) can be deleted from a list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i24)	last (List_3);
(%o24)	205

(%i25)	delete (last (List_3), List_3);
(%o25)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
         142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
         1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
         75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
         1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
         142,5,1372,174,5,1582,177,6,1455,200,6,1607]&lt;/syntaxhighlight&gt;
The &lt;code&gt;delete (List_3)&lt;/code&gt; expression creates a new list object using &lt;code&gt;List_3&lt;/code&gt;. &lt;code&gt;List_3&lt;/code&gt; itself is not affected by the &lt;code&gt;'''delete ()'''&lt;/code&gt; operator. Only the resulting list is affected. This is often the case with list operators. An identifier could be used to save the above resulting list if necessary:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* List_3 is the same length */
(%i26)	length(List_3); 
(%o26)	111

/* The last value of List_3 is the same */
(%i27)	List_3[111];
(%o27)	205

(%i28)	last(List_3);
(%o28)	205&lt;/syntaxhighlight&gt;There was only one instance of &lt;code&gt;205&lt;/code&gt; in &lt;code&gt;List_3&lt;/code&gt;, so only that value was deleted from the list of &lt;code&gt;%o25&lt;/code&gt;.  If there are more than one value then the &lt;code&gt;delete ()&lt;/code&gt; operator will remove all of those values from the returned list expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i29)	NewList_3 : delete(118, List_3)$ 

/* all five instances of 118 removed from List_3 as NewList_3 */
(%i30)	length(NewList_3);
(%o30)	106
&lt;/syntaxhighlight&gt;There are operators to refer to instances of list expressions by ordinal number:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i30)	FirstThreeList_3:[first(List_3), second(List_3), third(List_3)];
(FirstThreeList_3)	[1,118,30]
&lt;/syntaxhighlight&gt;Expressions of list objects can e referenced to create a new list object from the first n expressions of a list, the last n expressions of a list, or the rest remaining after n expressions from the beginning or -n expressions from the end of a list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* first three expressions of List_3 */
(%i31)	firstn(List_3,3); 
(%o31)	[1,118,30]

/* same three expressions of List_3 using the rest operator with -108 */
(%i32)	rest(List_3, -108); 
(%o32)	[1,118,30]

/* last three expressions of List_3 */
(%i33)	lastn(List_3,3); 
(%o33)	[6,1607,205]

/* same three expressions of List_3 using the rest operator with 108 */
(%i34)	rest(List_3, 108);
(%o34)	[6,1607,205]&lt;/syntaxhighlight&gt;Some further examples of the &lt;code&gt;'''firstn ()'''&lt;/code&gt;, &lt;code&gt;'''lastn ()'''&lt;/code&gt; and &lt;code&gt;'''rest ()'''&lt;/code&gt; list operators:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* first 63 expressions of List_3 */
(%i35)	firstn (List_3, 63);
(%o35)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,
         1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,
         1372,203,2,1582,203,3,118,30,3,484,51,3,664,75,3,1004,108,3,
         1231,115,3,1372,139,3,1582,140]

/* last 63 expressions of List_3 */
(%i36)	lastn (List_3, 63);
(%o36)	[3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,
         5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,
         1582,177,6,1455,200,6,1607,205]

/* first expressions of List_3 after removing the last 63*/
(%i37)	rest (List_3, -63);
(%o37)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,
         1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,
         1372,203,2,1582,203,3,118,30,3,484,51]
&lt;/syntaxhighlight&gt;Maxima programming expressions can be used with list operators to reference list expressions in various ways. For example, the expression which follows accesses the expressions of a list as lists of three each:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i38)	(L4 : List_4,
	      for i:(-length (List_4)) + 3 thru 0 step 3 do
	             (disp (rest (L4, i)), 
	              L4 : rest (L4, 3)),
	     &quot;&quot;)$

[1,118,30]
[1,484,58]
[1,664,87]
[1,1004,115]
[1,1231,120]
[1,1372,142]
[1,1582,145]
[2,118,33]
[2,484,69]
[2,664,111]
[2,1004,156]
[2,1231,172]
[2,1372,203]
[2,1582,203]
[3,118,30]
[3,484,51]
[3,664,75]
&lt;/syntaxhighlight&gt;List operators can be used as arguments other list operators:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* create a new empty list */
(%i39)	newList4 : [];
(newList4)	[]

/* append the first six &amp; last six expressions of List_4 to the new list */
(%i40)	newList4 : append (newList4, firstn (List_4, 6), lastn (List_4, 6))$

/* the new list now has the 12 appended expressions from List_4 */
(%i41)	newList4;
(%o41)	[1,118,30,1,484,58,3,484,51,3,664,75]
&lt;/syntaxhighlight&gt;

Maxima programming expressions can be used to step through the expressions of lists using list operators to reference &quot;slices&quot; of different lengths:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i42)	L4 : List_4;
(L4)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582
         145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,
         2,1582,203,3,118,30,3,484,51,3,664,75]

(%i43)	length (L4);
(%o43)	51

(%i44)	(L4 : List_4,
         for i : 21 thru 3 step -3 do
	         print (L4 : lastn (L4, i),&quot; &quot;, length (L4)),
	    &quot;&quot;)$

[2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 21

[2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 18

[2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 15

[2,1582,203,3,118,30,3,484,51,3,664,75] 12

[3,118,30,3,484,51,3,664,75] 9

[3,484,51,3,664,75] 6

[3,664,75] 3&lt;/syntaxhighlight&gt;

==== Using the &lt;code&gt;copylist&lt;/code&gt; Operator ====
When an existing list object is assigned to an identifier, a reference to the memory location of the list object is used. This reference to the memory location is transparent from the point of view of the user. However,if this is not  accounted for unintended side effects may occur when assigning another identifier to an existing one that references a list object.

For example, in the expression &lt;code&gt;L4 : List_4&lt;/code&gt; it might be assumed that this results in the list object referenced by &lt;code&gt;List_4&lt;/code&gt; to simply be copied to a new memory location and reference for &lt;code&gt;L4&lt;/code&gt;. This is not the case. Both &lt;code&gt;L4&lt;/code&gt; and &lt;code&gt;List_4&lt;/code&gt; refer to the same list object in memory. Consequently changes to the same list object can be effected by referencing the object using either alias.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i45)	newList4;
(%o45)	[1,118,30,1,484,58,3,484,51,3,664,75]

/* The identifier newList4 refers to a location in memory.
   The colon (:) assignment operator simply creates an alias
   using that same memory reference*/

(%i46)	newList5 :  newList4;
(newList5)	[1,118,30,1,484,58,3,484,51,3,664,75]

/* Two different identifiers for the same memory location and
   therefore the same object. Changes to expressions of the list
   object using either identifier changes the same object in memory */
   
(%i47)	newList5[1] : 99;
(newList5[1])	99

(%i48)	newList4[1];
(%o48)	99

(%i49)	newList4;
(%o49)	[99,118,30,1,484,58,3,484,51,3,664,75]

(%i50)	newList5;
(%o50)	[99,118,30,1,484,58,3,484,51,3,664,75]
&lt;/syntaxhighlight&gt;
This &quot;side effect&quot; is often unwanted. The way to avoid this is by using the &lt;code&gt;copylist ()&lt;/code&gt; operator instead of the assignment operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i51)	newList4 : [1,118,30,1,484,58,3,484,51,3,664,75] ;
(newList4)	[1,118,30,1,484,58,3,484,51,3,664,75]

(%i52)	newList5 : copylist (newList4);
(newList5)	[1,118,30,1,484,58,3,484,51,3,664,75]
 
 /* Same list object expressions, but a different memory reference */

(%i53)	newList5[1] : 99;
(newList5[1])	99

(%i54)	newList4[1];
(%o54)	1
&lt;/syntaxhighlight&gt;
Changes to the values of either list will not affect the other list.
{| class=&quot;wikitable&quot;
|+List Object Operators
|[
|fourth
|rreduce
|-
|]
|fullsetify
|second
|-
|append
|join
|setify
|-
|assoc
|last
|seventh
|-
|cons
|length
|sixth
|-
|copylist
|listarith
|some
|-
|create_list
|listp
|sort
|-
|delete
|lmax
|sublist
|-
|eighth
|lmin
|sublist_indices
|-
|endcons
|lreduce
|tenth
|-
|fifth
|makelist
|third
|-
|first
|member
|tree_reduce
|-
|flatten
|reverse
|xreduce
|}

Refer to the Maximal Manual&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.4.2 Functions and Variables for Lists |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Lists}}&lt;/ref&gt; for more complete description of operators and variables for Maxima lists.

==== Performance Considerations for Lists ====
&lt;blockquote&gt;''&quot;Lists provide efficient ways of appending and removing elements. They can be created without knowing their final dimensions. Lisp provides efficient means of copying and handling lists. Also nested lists do not need to be strictly rectangular. These advantages over declared arrays come with the drawback that the amount of time needed for accessing a random element within a list may be roughly proportional to the element’s distance from its beginning.&quot;''&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.4.3 Performance considerations for Lists |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Lists}}&lt;/ref&gt;&lt;/blockquote&gt;Maxima list objects have many operators for creating, accessing, and changing the expressions of lists. Evaluation times of expressions that involve lists can vary significantly depending on the length of the list objects involved, as well as the nature of any operators used to compose the expressions. This fact might have an influence on the choice of using arrays rather than lists in some cases if evaluation time is a factor to consider. The example expressions that follow involve a list object (identified as &lt;code&gt;s&lt;/code&gt; ) of complex number expressions that has a length of 10,000 and two different user-defined functions:&lt;pre&gt;(%i55) P1(s) := rectform (product(s[i], i, 1, length (s)))$

(%i56) P2(s) := xreduce (lambda ([a, b], rectform (a * b)), s)$

(%i57) s : makelist (random (1.0) + %i*random (1.0), 10^4)$

(%i58)	showtime : true$
Evaluation took 0.0000 seconds (0.0000 elapsed) using 0 bytes.

(%i59) P1(s);
Evaluation took 32.3080 seconds (32.3860 elapsed) using 17944.301 MB.
(%o59) 0.0

(%i60) P2(s);
Evaluation took 0.0620 seconds (0.0620 elapsed) using 8.343 MB.
(%o60) 0.0

(%i61)	showtime : false$
Evaluation took 0.0000 seconds (0.0000 elapsed) using 0 bytes.&lt;/pre&gt;
==Arrays ==
&lt;blockquote&gt;&quot;Maxima's current array/matrix semantics are a mess, I must say, with at least four different kinds of object (hash arrays, explicit lists, explicit matrices, Lisp arrays) supporting subscripting with varying semantics.&quot; &lt;ref&gt;[http://comments.gmane.org/gmane.comp.mathematics.maxima.general/21829 Maxima: Syntax improvements by Stavros Macrakis ]&lt;/ref&gt;
– Stavros Macrakis

&quot;Maxima's concept of arrays, lists, and matrices is pretty confused, since various ideas have accreted in the many years of the project... Yes, this is a mess. Sorry about that. These are all interesting ideas, but there is no unifying framework.&quot;&lt;ref&gt;[http://stackoverflow.com/a/29926692 Maxima: what does Maxima call an “array”? - answer by Robert Dodier]&lt;/ref&gt;

– Robert Dodier&lt;/blockquote&gt;

The various terminology used in the context of arrays undoubtedly can be confusing. For the sake of simplicity and clarity the following categories of array objects are referred to in this book:


Maxima has three array categories :&lt;ref&gt;[http://permalink.gmane.org/gmane.comp.mathematics.maxima.general/13588 the Maxima mailing list &lt;nowiki&gt;: [Maxima] array and matrix? - answer by Robert Dodier&lt;/nowiki&gt;]&lt;/ref&gt;
* Declared arrays 
* Undeclared (hashed) arrays 
* Lisp arrays 

'''''Declared arrays''''' are explicitly created using the &lt;code&gt;array()&lt;/code&gt; operator, and unlike lists, which have only one index and are one-dimensional, declared  arrays can be multi-dimensional  – having one to five indices. The indices for declared array dimensions need not be equal.

Indices for each dimension may be between 0 and the respective declared dimension. Each declared array may be for expressions of a specified type, which can be ''fixnum'' for integers or ''flonum'' for floating-point numbers.

'''''Undeclared (hashed) arrays''''' are created implicitly by assigning an expression to an indexed identifier that does not name an existing list object. An undeclared array (hashed array) can grow dynamically as there is no fixed dimension limit for each index as there is with declared arrays Another difference is that numbers, identifiers, expressions and strings may be used for indices.

Also, there is no fixed limit on the number of dimensions. The only real limitation is practical – the available computer memory and the underlying Lisp environment of the Maxima session. Hashed arrays with only one dimension may be confused with a list object.

It is essential to keep in mind that list objects must always be created before values are assigned or referenced. Assigning an expression to a one-dimensional indexed identifier, that does not reference an existing list, implicitly creates a hashed array.

'''''Lisp arrays''''' are created using the &lt;code&gt;'''make_array ()'''&lt;/code&gt; operator. The array type may be specified as ''any'', ''flonum'', ''fixnum'', or ''hashed''. Lisp array objects may be created as one-dimensional or multi-dimensional as specified by the number of dimension size values used with the &lt;code&gt;'''make_array ()'''&lt;/code&gt; operator. For each  dimension value specified, the associated index value can be a number between 0 to 1 less than the respective dimension value. The same or different values may be used for each specified dimension. the ''hashed'' type does not require any dimensions. Lisp arrays may be used in cases where memory usage and garbage collection are factors.

Examples of use and elaboration upon the technical details for each of these categories of array object types follows.
{| class=&quot;wikitable&quot;
|+Array Operators and Flags
|array
|arraysetapply
|rearray
|-
|arrayapply
|has_key
|remarray
|-
|arrayinfo
|fillarray
|subvar
|-
|arraymake
|listarray
|subvarp
|-
|arrays
|make_array
|use_fast_arrays
|-
|
|
|translate_fast_arrays
|}
=== Declared Arrays ===
Declared arrays must be created before being referenced and are of fixed dimensions.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	array(A1, fixnum, 34,2); 
(%o1)	A1

(%i2)	array(A2, flonum, 35,2);
(%o2)	A2

(%i3)	array(A3, 14,3);
(%o3)	A3

(%i4)	arrayinfo (A1);
(%o4)	[complete,2,[34,2]]

(%i5)	arrayinfo (A2);
(%o5)	[complete,2,[35,2]]

(%i6)	arrayinfo (A3);
(%o6)	[declared,2,[14,3]]
&lt;/syntaxhighlight&gt;
The first expression &lt;code&gt;%i1&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A1&lt;/code&gt;. This array is two-dimensional – the first index may have values from 0 to 34 and the second index may have values from 0 to 2. This array therefore is 35 by 3 in extent. The array type is declared to be &lt;code&gt;fixnum&lt;/code&gt;. As it is, &lt;code&gt;A1&lt;/code&gt; is an not empty array – it has values to reference as will be exemplified below.

Similarly the second expression &lt;code&gt;%i2&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A2&lt;/code&gt;. This array is also two-dimensional – the first index may have values from 0 to 35 and the second index may have values from 0 to 2. This array therefore is 36 by 3 in extent. The array type is declared to be &lt;code&gt;flonum&lt;/code&gt;. As it is, &lt;code&gt;A2&lt;/code&gt; is not an empty array – it also has values to reference as will be exemplified below.

The third expression &lt;code&gt;%i3&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A3&lt;/code&gt;. This array is also two-dimensional – the first index may have values from 0 to 13 and the second index may have values from 0 to 3. This array therefore is 15 by 4 in extent. The array type is not declared. As it is, &lt;code&gt;A3&lt;/code&gt; is an empty array – it has no values to reference as will be exemplified below.

The &lt;code&gt;'''arrayinfo ()'''&lt;/code&gt; operator can be used to return a list object that has values reflecting information about an array. Note that arrays declared without a type will have &lt;code&gt;declared&lt;/code&gt; as a value of the list. Arrays declared with &lt;code&gt;fixnum&lt;/code&gt; or &lt;code&gt;flonum&lt;/code&gt; as the type will have &lt;code&gt;complete&lt;/code&gt; as a value of the list. This technical detail is not well-documented. The returned information list also shows a value for the dimension of the array ( 2 in these examples ) and an inner list with values for the maximum index for each dimension.

A look inside each of these declared arrays provides a clue as to why &lt;code&gt;complete&lt;/code&gt; is returned instead of &lt;code&gt;declared&lt;/code&gt; when the type is specified as &lt;code&gt;fixnum&lt;/code&gt; or &lt;code&gt;flonum&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* This array reference has a value of 0 */
(%i7)	A1[0,0];
(%o7)	0

/* This array reference has a value of 0.0 */
(%i8)	A2[0,0];
(%o8)	0.0

/* This array reference has a value of itself */
(%i9)	A3[0,0];
(%o9)	A3[0,0]&lt;/syntaxhighlight&gt;

In fact, ''all'' values of the array &lt;code&gt;A1&lt;/code&gt; have been assigned 0, and ''all'' values of the array &lt;code&gt;A2&lt;/code&gt; have beenassigned 0.0. However, ''all'' values of the array &lt;code&gt;A3&lt;/code&gt; have been not been assigned any value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i10)	listarray(A1);
(%o10)	[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0]

(%i11)	listarray(A2);
(%o11)	[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]

(%i12)	listarray(A3);
(%o12)	[#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####]&lt;/syntaxhighlight&gt;

Thus, arrays &lt;code&gt;A1&lt;/code&gt; and &lt;code&gt;A2&lt;/code&gt; are &lt;code&gt;complete&lt;/code&gt; in this sense, and array &lt;code&gt;A3&lt;/code&gt; is simply &lt;code&gt;declared&lt;/code&gt;.

It might seem reasonable, that Maxima would complain if a value was assigned to an array that is at odds with the declared type. Such is not the case however. Once an array is declared with a type, Maxima does not enforce any type checking of values assigned to the array. The effect of the type (if any) in the declaration is simply to fill the array with values of #####, 0 or 0.0. Subsequently, those values can be replaced by the assignment of different values that will not be checked for the type of value. One way to enforce type checking is by using predicate operators to check values at the point in time of assignment to arrays. For example, using one or more of:

* numberp (expr)
* floatnump (expr)
* integerp (expr) 
* ratnump (expr)
* stringp (obj)
* listp (expr) 
* featurep (a, f)

and possibly others.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* A1 was declared as type fixnum */
(%i13)	A1[5,2]:3.14159;
(%o13)	3.14159

/* A2 was declared as type flonum */
(%i14)	A2[3,0]:7129;
(%o14)	7129

/* A1 which was declared as type fixnum assigned a string */
(%i15)	A1[4,1]:&quot;a string&quot;;
(%o15)	&quot;a string&quot;

/* A2 which was declared as type flonum assigned a math expression*/
(%i16)	A2[6,1]:3*x^2 + 4*x +10; 
(%o16)	3*x^2+4*x+10
&lt;/syntaxhighlight&gt;

There are other ways to assign values to an array. One way is to read the values from a comma separated (CSV) file  using the &lt;code&gt;'''read_array ()'''&lt;/code&gt; operator from the ''numericalio'' package.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i17) load(numericalio);
(%o17) &quot;/app/plugins/maxima/share/maxima/5.50.0/share/numericalio/numericalio.mac&quot;


&lt;/syntaxhighlight&gt;

Below are of the values of the CSV data file &lt;code&gt;tree_data_nh.csv&lt;/code&gt; :&lt;syntaxhighlight lang=&quot;text&quot;&gt;
1,118,30
1,484,58
1,664,87
1,1004,115
1,1231,120
1,1372,142
1,1582,145
2,118,33
2,484,69
2,664,111
2,1004,156
2,1231,172
2,1372,203
2,1582,203
3,118,30
3,484,51
3,664,75
3,1004,108
3,1231,115
3,1372,139
3,1582,140
4,118,32
4,484,62
4,664,112
4,1004,167
4,1231,179
4,1372,209
4,1582,214
5,118,30
5,484,49
5,664,81
5,1004,125
5,1231,142
5,1372,174
5,1582,177
&lt;/syntaxhighlight&gt;

Note that the following expression assumes that the CSV file is located in the Maxima working directory.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i18)	read_array(&quot;tree_data_nh.csv&quot;, A1, &quot;,&quot;); 
(%o18)	done

(%i19)	 listarray(A1);
(%o19)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,
         1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,
         2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75,3,1004,108,
         3,1231,115,3,1372,139,3,1582,140,4,118,32,4,484,62,4,664,112,
         4,1004,167,4,1231,179,4,1372,209,4,1582,214,5,118,30,5,484,49,
         5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177]
&lt;/syntaxhighlight&gt;
Below are of the values of the CSV data file &lt;code&gt;tree_data.csv&lt;/code&gt;  which has a header row, but is otherwise the same as &lt;code&gt;tree_data_nh.csv&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;text&quot;&gt;
&quot;Tree&quot;,&quot;age&quot;,&quot;circumference&quot;
1,118,30
1,484,58
1,664,87
1,1004,115
1,1231,120
1,1372,142
1,1582,145
2,118,33
2,484,69
2,664,111
2,1004,156
2,1231,172
2,1372,203
2,1582,203
3,118,30
3,484,51
3,664,75
3,1004,108
3,1231,115
3,1372,139
3,1582,140
4,118,32
4,484,62
4,664,112
4,1004,167
4,1231,179
4,1372,209
4,1582,214
5,118,30
5,484,49
5,664,81
5,1004,125
5,1231,142
5,1372,174
5,1582,177
&lt;/syntaxhighlight&gt;&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i20)	read_array(&quot;tree_data.csv&quot;, A2, &quot;,&quot;); 
(%o20)	done

(%i21) listarray(A2);
(%o21) [&quot;Tree&quot;,&quot;age&quot;,&quot;circumference&quot;,1,118,30,1,484,58,1,664,87,1,1004,
        115,1,1231,120,1,1372,142,1,1582,145,2,118,33,2,484,69,2,664,111,
        2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,
        3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
        4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,
        5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,
        5,1582,177]&lt;/syntaxhighlight&gt;The previous values of 0 and 0,0 as well as the assigned values of &lt;code&gt;A1&lt;/code&gt; and &lt;code&gt;A2&lt;/code&gt; have been replaced with the values from the CSV files.

The third array A3 can be used with values from the  dataset.csv file below:&lt;syntaxhighlight lang=&quot;text&quot;&gt;&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;
&quot;Smith&quot;,16753.00,&quot;UK&quot;,&quot;Qtr 3&quot;
&quot;Johnson&quot;,14808.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Williams&quot;,10644.00,&quot;UK&quot;,&quot;Qtr 2&quot;
&quot;Jones&quot;,1390.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Brown&quot;,4865.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Williams&quot;,12438.00,&quot;UK&quot;,&quot;Qtr 1&quot;
&quot;Johnson&quot;,9339.00,&quot;UK&quot;,&quot;Qtr 2&quot;
&quot;Smith&quot;,18919.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Jones&quot;,9213.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Jones&quot;,7433.00,&quot;UK&quot;,&quot;Qtr 1&quot;
&quot;Brown&quot;,3255.00,&quot;USA&quot;,&quot;Qtr 2&quot;
&quot;Williams&quot;,14867.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Williams&quot;,19302.00,&quot;UK&quot;,&quot;Qtr 4&quot;
&quot;Smith&quot;,9698.00,&quot;USA&quot;,&quot;Qtr 1&quot;&lt;/syntaxhighlight&gt;&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i22)	read_array(&quot;dataset.csv&quot;, A3, &quot;,&quot;); 
(%o22)	done

(%i23)	 listarray(A3);
(%o23)	[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;,
         &quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;,
         &quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;,
         &quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;,
         &quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;,
         &quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;,
         &quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;,
         &quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;,
         &quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]&lt;/syntaxhighlight&gt;

Values of the array can be referenced by indices as required for some purpose:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i24)	A3[0,0];
(%o24)	&quot;Last Name&quot;

(%i25)	A3[4,2];
(%o25)	&quot;USA&quot;
&lt;/syntaxhighlight&gt;
A row list object can be created using the &lt;code&gt;'''makelist ()'''&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i26)	row1A3: makelist(A3[0, j], j, 0, 3)$

(%i27)	row1A3;
(%o27)	[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;]

(%i28)	row1A3[1];
(%o28)	&quot;Last Name&quot;

(%i29)	row15A3: makelist(A3[14, j], j, 0, 3)$

(%i30)	row15A3;
(%o30)	[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]

(%i31)	row15A3[2];
(%o31)	9698.0
&lt;/syntaxhighlight&gt;
A list of the indices of the array can be created:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i32)	indices_A3 : arrayinfo(A3)[3];
(indices_A3)	[14,3]
&lt;/syntaxhighlight&gt;
The number of indices of array &lt;code&gt;A3&lt;/code&gt; can also be referenced using the &lt;code&gt;'''length (''')&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i33)	length(arrayinfo(A3)[3]);
(%o33)	2
&lt;/syntaxhighlight&gt;The number of values of the array &lt;code&gt;A3&lt;/code&gt; can be returned using the '''&lt;code&gt;length ()&lt;/code&gt;''' operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i34)	length(listarray(A3));
(%o34)	60
&lt;/syntaxhighlight&gt;
The values of the array &lt;code&gt;A3&lt;/code&gt; can be printed as output using the list of values with a loop programming expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i35)	for i:1 thru length (listarray(A3)) do 
            print('A3[i] ,&quot; = &quot;,  listarray(A3)[i])$

A3[1]&quot; = &quot;&quot;Last Name&quot;
A3[2]&quot; = &quot;&quot;Sales&quot;
A3[3]&quot; = &quot;&quot;County&quot;
A3[4]&quot; = &quot;&quot;Quarter&quot;
A3[5]&quot; = &quot;&quot;Smith&quot;
A3[6]&quot; = &quot;16753.0
A3[7]&quot; = &quot;&quot;UK&quot;
A3[8]&quot; = &quot;&quot;Qtr 3&quot;
A3[9]&quot; = &quot;&quot;Johnson&quot;
A3[10]&quot; = &quot;14808.0
A3[11]&quot; = &quot;&quot;USA&quot;
A3[12]&quot; = &quot;&quot;Qtr 4&quot;
A3[13]&quot; = &quot;&quot;Williams&quot;
A3[14]&quot; = &quot;10644.0
A3[15]&quot; = &quot;&quot;UK&quot;
A3[16]&quot; = &quot;&quot;Qtr 2&quot;
A3[17]&quot; = &quot;&quot;Jones&quot;
A3[18]&quot; = &quot;1390.0
A3[19]&quot; = &quot;&quot;USA&quot;
A3[20]&quot; = &quot;&quot;Qtr 3&quot;
A3[21]&quot; = &quot;&quot;Brown&quot;
A3[22]&quot; = &quot;4865.0
A3[23]&quot; = &quot;&quot;USA&quot;
A3[24]&quot; = &quot;&quot;Qtr 4&quot;
A3[25]&quot; = &quot;&quot;Williams&quot;
A3[26]&quot; = &quot;12438.0
A3[27]&quot; = &quot;&quot;UK&quot;
A3[28]&quot; = &quot;&quot;Qtr 1&quot;
A3[29]&quot; = &quot;&quot;Johnson&quot;
A3[30]&quot; = &quot;9339.0
A3[31]&quot; = &quot;&quot;UK&quot;
A3[32]&quot; = &quot;&quot;Qtr 2&quot;
A3[33]&quot; = &quot;&quot;Smith&quot;
A3[34]&quot; = &quot;18919.0
A3[35]&quot; = &quot;&quot;USA&quot;
A3[36]&quot; = &quot;&quot;Qtr 3&quot;
A3[37]&quot; = &quot;&quot;Jones&quot;
A3[38]&quot; = &quot;9213.0
A3[39]&quot; = &quot;&quot;USA&quot;
A3[40]&quot; = &quot;&quot;Qtr 4&quot;
A3[41]&quot; = &quot;&quot;Jones&quot;
A3[42]&quot; = &quot;7433.0
A3[43]&quot; = &quot;&quot;UK&quot;
A3[44]&quot; = &quot;&quot;Qtr 1&quot;
A3[45]&quot; = &quot;&quot;Brown&quot;
A3[46]&quot; = &quot;3255.0
A3[47]&quot; = &quot;&quot;USA&quot;
A3[48]&quot; = &quot;&quot;Qtr 2&quot;
A3[49]&quot; = &quot;&quot;Williams&quot;
A3[50]&quot; = &quot;14867.0
A3[51]&quot; = &quot;&quot;USA&quot;
A3[52]&quot; = &quot;&quot;Qtr 3&quot;
A3[53]&quot; = &quot;&quot;Williams&quot;
A3[54]&quot; = &quot;19302.0
A3[55]&quot; = &quot;&quot;UK&quot;
A3[56]&quot; = &quot;&quot;Qtr 4&quot;
A3[57]&quot; = &quot;&quot;Smith&quot;
A3[58]&quot; = &quot;9698.0
A3[59]&quot; = &quot;&quot;USA&quot;
A3[60]&quot; = &quot;&quot;Qtr 1&quot;
&lt;/syntaxhighlight&gt;

Maxima treats declared arrays as fixed-sized, and individual values are accessed via indices. There is no built-in &quot;row&quot; object — rows must be extracted manually using the &lt;code&gt;'''makelist ()'''&lt;/code&gt; operator or by looping through values of an array.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i36)	array(rowsA3,15);
(%o36)	rowsA3

(%i37)	arrayinfo(rowsA3);
(%o37)	[declared,1,[15]]

(%i38)	for i:0 thru 14 do
	       (rowsA3[i+1]:makelist(A3[i, j], j, 0, 3),
	        print(&quot;Row &quot;,i+1,&quot;: &quot;,rowsA3[i+1]))$;

&quot;Row &quot;1&quot;: &quot;[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;]
&quot;Row &quot;2&quot;: &quot;[&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;3&quot;: &quot;[&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;4&quot;: &quot;[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;5&quot;: &quot;[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;6&quot;: &quot;[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;7&quot;: &quot;[&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;8&quot;: &quot;[&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;9&quot;: &quot;[&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;10&quot;: &quot;[&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;11&quot;: &quot;[&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;12&quot;: &quot;[&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;13&quot;: &quot;[&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;14&quot;: &quot;[&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;15&quot;: &quot;[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]
&lt;/syntaxhighlight&gt;
Maxima does not have a built-in function like &lt;code&gt;delete&lt;/code&gt; or &lt;code&gt;unset&lt;/code&gt; for removing individual values from arrays using indices. Existing values of an array can be changed by assignment however:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i52)	rowsA3[1]:[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;]$

(%i53)	for i:1 thru 15 do
	    (newRowsA3[i]:rowsA3[i],
	    print(&quot;Row &quot;,i,&quot;: &quot;,newRowsA3[i]))$;

&quot;Row &quot;1&quot;: &quot;[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;2&quot;: &quot;[&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;3&quot;: &quot;[&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;4&quot;: &quot;[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;5&quot;: &quot;[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;6&quot;: &quot;[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;7&quot;: &quot;[&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;8&quot;: &quot;[&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;9&quot;: &quot;[&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;10&quot;: &quot;[&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;11&quot;: &quot;[&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;12&quot;: &quot;[&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;13&quot;: &quot;[&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;14&quot;: &quot;[&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;15&quot;: &quot;[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]&lt;/syntaxhighlight&gt;
The &lt;code&gt;'''arrayapply ()'''&lt;/code&gt; operator can be used a follows to reference values of a declared array:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i39)	arrayapply(rowsA3,[5]);
(%o39)	[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]

(%i40)	arrayapply(A3, [5,1]);
(%o40)	4865.0
&lt;/syntaxhighlight&gt;The operator &lt;code&gt;'''fillarray (A, B)'''&lt;/code&gt; assigns values to array &lt;code&gt;A&lt;/code&gt; from &lt;code&gt;B&lt;/code&gt;, which can be a list or an array.The dimensions of the arrays &lt;code&gt;A&lt;/code&gt; and &lt;code&gt;B&lt;/code&gt; may not be the same. In that case, array &lt;code&gt;A&lt;/code&gt; is filled in &quot;row-major&quot; order. There may not be enough values in &lt;code&gt;B&lt;/code&gt; compared to &lt;code&gt;A&lt;/code&gt;. In that case, the last value of &lt;code&gt;B&lt;/code&gt; is used to for the remaining values of &lt;code&gt;A&lt;/code&gt;. There may be too many values of &lt;code&gt;B&lt;/code&gt; compared to array &lt;code&gt;A&lt;/code&gt;. In that case, the remaining values of &lt;code&gt;B&lt;/code&gt; once &lt;code&gt;A&lt;/code&gt; is filled are not used. The return value of &lt;code&gt;'''fillarray ()'''&lt;/code&gt; is not the filled array &lt;code&gt;A&lt;/code&gt;, but it is the first argument.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* Create a declared array B of type fixnum */
(%i41)	array (B, fixnum, 9);
(%o41)	B

/* list the values of array B */
(%i42)	listarray (B);
(%o42)	[0,0,0,0,0,0,0,0,0,0]

/* fill array B with the values of the list */
(%i43)	fillarray (B, [0,1, 2, 3, 4, 5, 6, 7, 8, 9.0]);
(%o43)	B

/* list the values of array B */
(%i44)	listarray (B);
(%o44)	[0,1,2,3,4,5,6,7,8,9.0]

/* fill array B with the value 1.0 */
(%i45)	fillarray (B, [1.0]);
(%o45)	B

/* list the values of array B */
(%i46)	listarray (B);
(%o46)	[1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0]

/* fill array B with the first 9 values of the list */
(%i47)	fillarray (B, [0,1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12]);
(%o47)	B

/* list the values of array B */
(%i48)	listarray (B);
(%o48)	[0,1,2,3,4,5,6,7,8,9]

/* Create a declared array D of no type */
(%i49)	array (D, 9);
(%o49)	D

/* list the values of array D */
(%i50)	listarray (D);
(%o50)	[#####,#####,#####,#####,#####,#####,#####,#####,#####,#####]

/* fill array D with the value 1.0 */ 
(%i51)	fillarray (D, [1.0]);
(%o51)	D

/* list the values of array D */
(%i52)	listarray (D);
(%o52)	[1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0]

/* Create a declared array E of no type */
(%i53)	array (E, 15);
(%o53)	E

/* fill array E with the values from the newRowsA3 list */ 
(%i54)	fillarray (E, listarray (newRowsA3));
(%o54)	E

/* list the values of array D */
(%i55)	listarray (E);
(%o55)	[[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;],
         [&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;],
         [&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]]

/* remove array E */
(%i56)	remarray (E);
(%o56)	[E]

/*  D is no longer an array */
(%i57)	arrayinfo (E);
arrayinfo: E is not an array.

 -- an error. To debug this try: debugmode(true);&lt;/syntaxhighlight&gt;

If you need to keep the array but remove only one value, you must reconstruct it without that value. The operator &lt;code&gt;'''remarray ()'''&lt;/code&gt; is the typical way to completely remove an array.

The &lt;code&gt;'''rearray (A, dim&lt;sub&gt;1&lt;/sub&gt;, dim&lt;sub&gt;2&lt;/sub&gt; ,…, dim&lt;sub&gt;n&lt;/sub&gt;)'''&lt;/code&gt; operator is used to change the dimensions of an array. The changed array will be filled with the elements of the existing array in row-major order. If the existing array has one or more smaller dimensions, the additional dimension values of the changed array are assigned with a value that depends on the type of the array. If the existing array has one or more larger dimensions, the deficient dimension values of the changed array are lost. The type of the array cannot be changed using this operator. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* list with the values of array B */
(%i58)	listarray(B);
(%o58)	[0,1,2,3,4,5,6,7,8,9]

/* list with information about array B */
(%i59)	arrayinfo(B);
(%o59)	[complete,1,[9]]

/* increase the dimension of array B */
(%i60)	rearray (B, 12);
(%o60)	\#\{Lisp array \[13\]\}

/* list with information about array B with increased dimension */
(%i61)	arrayinfo(B);
(%o61)	[complete,1,[12]]

/* list with the values of array B */
(%i62)	listarray(B);
(%o62)	[0,1,2,3,4,5,6,7,8,9,0,0,0]

/* decrease the dimension of array B */
(%i63)	rearray (B, 6);
(%o63)	\#\{Lisp array \[7\]\}

/* list with information about array B with decreased dimension */
(%i64)	arrayinfo(B);
(%o64)	[complete,1,[6]]

/* list with the values of array B */
(%i65)	listarray(B);
(%o65)	[0,1,2,3,4,5,6]


&lt;/syntaxhighlight&gt;

The &lt;code&gt;'''arraymake ()'''&lt;/code&gt; operator returns a value that is an array reference without evaluation. This operator, in spite of the name, does not &quot;make&quot; an array. It returns this reference as a value whether or not an array exists as an object:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* the arraymake operator returns the unevaluated reference to A */
(%i66)	arraymake (A, [i,j]);
(%o66)	A[i,j]

/* however array A is not an array object*/
(%i67)	arrayinfo (A);
arrayinfo: A is not an array.
 -- an error. To debug this try: debugmode(true);

/* Maxima sees A[j,k] as a reference to an undefined memoizing function */
(%i68)	op (arraymake (A, [i,j]));
(%o68)	A
&lt;/syntaxhighlight&gt;
However, from a practical point of view, this operator is used with existing arrays:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i69)	listarray (newRowsA3);
(%o69)	[[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;],
         [&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;],
         [&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]]

(%i70)	arraymake (newRowsA3, [4]);
(%o70)	newRowsA3[4]

(%i71)	''%;
(%o71)	[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]

(%i72)	arraymake (newRowsA3, [i]);
(%o72)	newRowsA3[i]

(%i73)	''%, i = 6;
(%o73)	[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]

&lt;/syntaxhighlight&gt;
The operator &lt;code&gt;arraymake (x, [i])&lt;/code&gt; constructs the expression &lt;code&gt;x[i]&lt;/code&gt;, but does not evaluate it. 

The operator &lt;code&gt;'''subvar'''&lt;/code&gt; &lt;code&gt;'''(x, i)'''&lt;/code&gt; evaluates the indexed expression &lt;code&gt;x[i]&lt;/code&gt;, and evaluates its arguments. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i74)	listarray(B);
(%o174)	[0,1,2,3,4,5,6]

(%i75)	x : B;
(x)	B

(%i76)	i : 4;
(i)	4

(%i77)	subvar (x, i);
(%o77)	4
&lt;/syntaxhighlight&gt;
The operator &lt;code&gt;'''subvarp (expr)'''&lt;/code&gt; returns a value of &lt;code&gt;true&lt;/code&gt; if &lt;code&gt;expr&lt;/code&gt; is a indexed identifier, and &lt;code&gt;false&lt;/code&gt; otherwise. This operator evaluates the argument &lt;code&gt;expr&lt;/code&gt;.  &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;

(%i78)	z[p];
(%o78)	z[p]

(%i79)	subvarp (z[p]);
(%o79)	true

(%i80)	x[i];
(%o80)	4

(%i81)	subvar (x, i)
(%o81)	4

(%i82)	w : z[p];
(w)	z[p]

(%i83)	subvarp (w);
(%o83)	true


&lt;/syntaxhighlight&gt;
The expression &lt;code&gt;'''arrays'''&lt;/code&gt;  returns a list of allocated arrays: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i84)	arrays;
(%o84)	[A3,A2,A1,rowsA3,newRowsA3,B,D]&lt;/syntaxhighlight&gt;

The operator &lt;code&gt;'''arraysetapply (A, [i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2,&lt;/sub&gt;…,i&lt;sub&gt;n&lt;/sub&gt;], x)'''&lt;/code&gt; assigns the value of expression &lt;code&gt;x&lt;/code&gt; to &lt;code&gt;A&lt;/code&gt;&lt;code&gt;[i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2&lt;/sub&gt;,…,i&lt;sub&gt;n&lt;/sub&gt;]&lt;/code&gt;, where &lt;code&gt;A&lt;/code&gt; is an array and &lt;code&gt;i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2&lt;/sub&gt;,…,i&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt; are integers.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i85)	arraysetapply (newRowsA3, [8], [&quot;George&quot;,20818.0,&quot;UK&quot;,&quot;Qtr 4&quot;]);
(%o85)	[&quot;George&quot;,20818.0,&quot;UK&quot;,&quot;Qtr 4&quot;]&lt;/syntaxhighlight&gt;
=== Undeclared Arrays ===

Maxima declared arrays and Maxima undeclared arrays will likely be the two types of data structures used by most users. Maxima undeclared arrays are also referred to as '''''hashed arrays'''''. For both of these two array types, memory allocation and structure occur &quot;behind the curtain&quot; of the Maxima user level, and &quot;the man behind the curtain&quot; is Lisp.

Of these two types, hashed arrays are the most flexible from the user point of view, all other factors being equal:

* The indices allowed for hashed arrays can be expressions,
* The dimensions of a hashed array are dynamic and not fixed, and
* Hashed arrays are relatively easier to create.
In fact, hashed arrays can be somewhat too easy to create. In the examples of the previous section involving declared arrays, identifiers were used as names for arrays. here is the list of allocated arrays:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i86)	arrays;
(%o86)	[A3,A2,A1,rowsA3,newRowsA3,B,D,my_list,h]&lt;/syntaxhighlight&gt;The array information for array &lt;code&gt;newRowsA3&lt;/code&gt; is shown below:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i87)	arrayinfo(newRowsA3);
(%o87)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15]]
&lt;/syntaxhighlight&gt;So the array &lt;code&gt;newRowsA3&lt;/code&gt; is not a declared array. it was created as part of a loop programming expression repeated below:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i53)	for i : 1 thru 15 do
	    (newRowsA3[i] : rowsA3[i],
	    print(&quot;Row &quot;,i,&quot;: &quot;,newRowsA3[i]))$;&lt;/syntaxhighlight&gt;When the first loop block was executed with i : 1, the assignment expression:

&lt;code&gt;newRowsA3[i] : rowsA3[i]&lt;/code&gt;

created a hashed array named  &lt;code&gt;newRowsA3&lt;/code&gt; and assigned &lt;code&gt;newRowsA3[1]&lt;/code&gt; the value of &lt;code&gt;rowsA3[1]&lt;/code&gt; automatically without any declaration. After that the hashed array dynamically allocated memory for values of the loop identifier i from 2 through 15 with each successive pass in the loop expression. Since hashed arrays are undeclared, and their associated dimensions are not fixed, but rather increase dynamically, expressions can be added to hashed arrays without creating a error message. These added values can be can be any valid Maxima expression, and the value of the indices used are not limited to zero and nonzero integers:  &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i88)	newRowsA3[16] :  [&quot;Maisel&quot;,12785.0,&quot;USA&quot;,&quot;Qtr 2&quot;];
(newRowsA3[16])	[&quot;Maisel&quot;,12785.0,&quot;USA&quot;,&quot;Qtr 2&quot;]

(%i89	arrayinfo(newRowsA3);
(%o89)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15],[16]]

(%i90)	newRowsA3[z]  : 2*sin(y) ^2 + 3*sin(x)^3;
(newRowsA3[z])	2*sin(y)^2+3*sin(B)^3

(%i91)	arrayinfo(newRowsA3);
(%o91)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15],[16],[z]]
&lt;/syntaxhighlight&gt;So one point to glean from this example is that all that is required to create a hashed array is an assignment expression to an indexed identifier, but it does require this assignment. If for some reason, a declared array is intended, but not declared using the &lt;code&gt;array&lt;/code&gt; operator (as in the instance of &lt;code&gt;newRowsA3&lt;/code&gt;), then a hashed array will be created at the first assignment of an expression to an indexed identifier.

This issue can also occur in cases where reference to a list value is intended, but the list has not been created. Lists are one-dimensional objects by definition. A reference using an identifier with a single index intended to be a list with no list existing named by that identifier, can inadvertently create a hashed array.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i91)	Alist[2] : 2*sin(y) ^2 + 3*sin(s)^3;
(Alist[2])	2*sin(y)^2+3*sin(s)^3

(%i92)	listp(Alist);
(%o92)	false

(%i93)	arrayinfo(Alist);
(%o93)	[hashed,1,[2]]
&lt;/syntaxhighlight&gt;The identifier &lt;code&gt;Alist&lt;/code&gt; is a name for a hashed array and not a list.

However, hashed arrays, like declared arrays can, be multi-dimensional: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i94)	a_hashed_array [j,k,l] : [12,s^(1/3), %i];
(%o94)	[12,s^(1/3),%i]

(%i95)	arrayinfo(a_hashed_array);
(%o95)	[hashed,3,[j,k,l]]
&lt;/syntaxhighlight&gt;The &lt;code&gt;array&lt;/code&gt; operator can be used to transform a hashed array into a declared array:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i96)	another_hashed_array[ 0, 2, 3] : 55;
(%o96)	55

(%i97)	array (another_hashed_array, 2, 4, 5);
(%o97)	another_hashed_array

(%i98)	arrayinfo(another_hashed_array);
(%o98)	[declared,3,[2,4,5]]
&lt;/syntaxhighlight&gt;From the user point of view, hashed arrays and declared arrays typically can be used for the same purpose. If dynamic dimensions or index expression flexibility are factors, then hashed arrays are likely to be a better choice. Many of the operators that can use declared arrays as arguments, may also be used with hashed arrays.

However, it should be noted at this point, that merely using a indexed identifier alone without an assignment, will not create a hashed array. Instead, Maxima interprets an expression so composed as an identifier for an undefined memoizing function, which is the topic of the next section.

==== Memoizing Functions ====
Assignment using an indexed identifier implicitly creates an undeclared (hashed) array. However, entering an expression that is an unassigned indexed identifier, from the point of view of Maxima, creates the identifier of a &quot;memoizing&quot; function. Memoizing functions are technically not an array topic, as these functions fall under the category of function definition. These functions have one foot in the function category and the other foot in the array category.

Memoizing functions are defined in a manner similar to other user-defined functions, for example:

&lt;code&gt;f(x, y, z) := x^2 + y^2 + z^2;&lt;/code&gt;

But instead of the arguments being enclosed in parentheses, they are enclosed using brackets:

&lt;code&gt;f[x, y, z] := x^2 + y^2 + z^2;&lt;/code&gt;

However, memoizing functions may be referred to as ''array functions,'' and it is the case that these functions from the point of view of aggregate data structures are hashed arrays. So these are mentioned and exemplified here for that reason:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* reference an indexed identifier h without assignment */
(%i99)	h[x];
(%o99)	h[x]

/* check identifier h as an array */
(%i100)	arrayinfo (h);
arrayinfo: h is not an array.
  -- an error. To debug this try: debugmode(true);
  
/* check identifier h as a function */
(%i101)	op(h[x]);
(%o101)	h

/* define h[x] as a function */
(%i102)	h[x] := 5*x^3 + sin(x);
(h[x])	h[x]:=5*x^3+sin(x)

/* check identifier h[x] as a function */
(%i103)	op(h[x]);
(%o103)	&quot;+&quot;

/* check identifier h as an array */
(%i104)	arrayinfo (h);
(%o104)	[hashed,1,[x]]

/* check the value of identifier h[x] */
(%i105)	h[x];
(%o105)	sin(x)+5*x^3

/* evaluate identifier h[x] with the argument 3*%pi */
(%i106)	h[3*%pi];
(%o106)	135*%pi^3

/* list the values of identifier h as an array */
(%i107)	listarray(h);
(%o107)	[135*%pi^3,sin(x)+5*x^3]

/* check identifier h as an array */
(%i108)	arrayinfo (h);
(%o108)	[hashed,1,[3*%pi],[x]]&lt;/syntaxhighlight&gt;A defined memoizing function stores its value the ''first time'' it is referenced with arguments, and returns the stored value, without evaluation, when the same arguments are used with that function subsequently. The stored value is &quot;frozen&quot; after the initial evaluation. Thus, it behaves like a hashed array. The arguments of a memoizing function also serve as indices of the associated hashed array.

=== Lisp Arrays ===
Lisp arrays are created using the &lt;code&gt;make_array (type, dim&lt;sub&gt;1&lt;/sub&gt;, dim&lt;sub&gt;2&lt;/sub&gt;, …, dim&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt; operator. Perhaps a better name for this operator would be &lt;code&gt;make_lisp_array ()&lt;/code&gt;, which admittedly is a longer name.

This operator creates and has a return value of a Lisp array. The array type may be &lt;code&gt;any&lt;/code&gt;, &lt;code&gt;flonum&lt;/code&gt;, &lt;code&gt;fixnum&lt;/code&gt;, or  &lt;code&gt;hashed&lt;/code&gt; . The &lt;code&gt;functional&lt;/code&gt; type referred to in the Maxima Manual appears to have been deprecated, and may result in an error message if used. There can be ''n'' indices, and where the associated indices can be a value from ''0'' to ''dim&lt;sub&gt;i&lt;/sub&gt; -1'', and ''i'' can have a value of one of 1 to n inclusive.

This operator can be used as an alternative to the &lt;code&gt;array ()&lt;/code&gt; operator. The advantage of using &lt;code&gt;make_array()&lt;/code&gt; is that the return value of &lt;code&gt;make_array()&lt;/code&gt; ''does not have a name''. Once the Maxima identifier that is assigned to the array return value is no longer assigned, the array memory allocation is released, and the allocated memory can be garbage collected. What it is being referred to that Lisp arrays created using &lt;code&gt;make_array()&lt;/code&gt; do not have names? &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* create a undeclared Maxima hashed array */
(%i109)	arrayA1 [1] : 55;  
(%o109)	55

/* check the information about this undeclared Maxima hashed array */
(%i110)	arrayinfo (arrayA1);
(%o110)	[hashed,1,[1]]

/* check the value of this undeclared Maxima hashed array */
(%i111)	arrayA1;
(%o111)	arrayA1     /* the name */

/* create a Lisp hashed array */
(%i112)	arrayA2 : make_array (hashed);
(arrayA2)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 1 {1202987DC3}&gt;&quot;

/* check the information about this Lisp hashed array */
(%i113)	arrayinfo (arrayA2);
(%o113)	[hash_table,1]

/* check the value of this Lisp hashed array */
(%i114)	arrayA2;
(%o114)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 1 {1202987DC3}&gt;&quot; /* no name */

(%i115)	listarray (arrayA2);
(%o115)	[]                     /* this hashed array is empty */
&lt;/syntaxhighlight&gt;So Lisp arrays do not have a name as a value. So, Maxima identifiers assigned to a Lisp array have no name for the array as a value. These identifiers have the reference to the array itself as a value, Lisp hashed arrays created using &lt;code&gt;make_array()&lt;/code&gt; with the hashed type specified, do not use dimensions. Lisp hashed arrays are often referred to as '''''hashed tables''''', and their indices are called '''''keys'''''.

An example of a Lisp array with the type &lt;code&gt;any&lt;/code&gt; follows:

&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* make a Lisp 3 by 4 array of type any */
(%i116)	arrayA3 : make_array (any, 3,4);
(arrayA3)	\#\{Lisp array \[3\\,4\]\}

(%i117)	arrayinfo (arrayA3);
(%o117)	[declared,2,[2,3]]

(%i118)	listarray(arrayA3);
(%o118)	[false,false,false,false,false,false,false,false,false,false,false,false]

(%i119)	arrayA3[1,1] : &quot;a string&quot; ;
(%o119)	&quot;a string&quot;

(%i120)	listarray(arrayA3);
(%o120)	[false,false,false,false,false,&quot;a string&quot;,
         false,false,false,false,false,false]
&lt;/syntaxhighlight&gt;Contrary to statements made in some sources, type checking is is not accomplished automatically, and will not cause Maxima to return an error message, as the Lisp array with the type &lt;code&gt;fixnum&lt;/code&gt; which follows is an exemplifies:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i121)	arrayA4 : make_array (fixnum, 3,4);
(arrayA4)	\#\{Lisp array \[3\\,4\]\}

(%i122)	arrayinfo (arrayA4);
(%o122)	[declared,2,[2,3]]

(%i123)	listarray (arrayA4);
(%o123)	[0,0,0,0,0,0,0,0,0,0,0,0]

(%i124)	arrayA4[0,2] : 3.14159;
(%o124)	3.14159

(%i125)	arrayA4[0,0] : &quot;a string&quot;;
(%o125)	&quot;a string&quot;

/* value types not checked and no error message */
(%i126)	listarray (arrayA4);
(%o126)	[&quot;a string&quot;,0,3.14159,0,0,0,0,0,0,0,0,0]&lt;/syntaxhighlight&gt;As was the case with declared arrays, there is no type checking and no error messages associated with assigned values of the array based on the declared type. The declared array type simply determines initial fill values, if any.

Hashed arrays and Lisp hash tables have an operator in common:

&lt;code&gt;has_key&lt;/code&gt; &lt;code&gt;(A, L)&lt;/code&gt;

This expression has a a value of &lt;code&gt;true&lt;/code&gt;, if the hashed array or Lisp hash table &lt;code&gt;A&lt;/code&gt; has the key (index) or keys (indices) of the list object &lt;code&gt;L&lt;/code&gt;.  Otherwise the expression has a value of &lt;code&gt;false&lt;/code&gt;.

The array &lt;code&gt;A&lt;/code&gt; must be a hashed (undeclared) array, a Lisp hash table value returned by the &lt;code&gt;make_array&lt;/code&gt; operator, or created as an undeclared array with &lt;code&gt;use_fast_arrays&lt;/code&gt; assigned the value &lt;code&gt;true&lt;/code&gt;.

If array A has only one key, that key must be the value of a list.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i127)	arrayinfo (newRowsA3);
(%o127)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],
                  [11],[12],[13],[14],[15],[16],[z]]

(%i128)	has_key (newRowsA3, [z]);
(%o128)	true

(%i129)	has_key (newRowsA3, [3]);
(%o129)	true

(%i130)	has_key(newRowsA3, [0]);
(%o130)	false

(%i131)	lisp_Array_1 [x];
(%o131)	3*x^2

(%i132)	arrayinfo (lisp_Array_1);
(%o132)	[hash_table,1,x]

(%i133)	has_key (lisp_Array_1, [x]);
(%o133)	true

(%i134)	has_key (lisp_Array_1, [y]);
(%o134)	false
&lt;/syntaxhighlight&gt;

=== Arrays and Features ===
Maxima arrays can be assigned features in a manner similar to other identifiers:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i135)	array (a6,fixnum, 5);
(%o135)	a6

(%i136)	arrayinfo (a6);
(%o136)	[complete,1,[5]]

(%i137)	declare (a6, [real, noninteger]);
(%o137)	done

(%i138)	featurep (a6, real);
(%o138)	true

(%i139)	featurep (a6, noninteger);
(%o139)	true

(%i140)	a6[2] : 2;
(a6[2])	2

(%i141)	listarray (a6);
(%o141)	[0,0,2,0,0,0]
&lt;/syntaxhighlight&gt;However, once again, declaring an array to have one or more features does not result in type checking of values assigned to an array. Perhaps the best way to ensure types of values assigned to arrays is type-checking of expressions using predicate operators prior to assignment to arrays. 

=== Array Memory Storage Considerations ===

The following from the Maxima Manual&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.5.1 - Functions and Variables for Arrays |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Functions-and-Variables-for-Arrays}}&lt;/ref&gt; is quoted here for the purpose of establishing the context of that which follows:&lt;blockquote&gt;''&quot;Option variable: use_fast_arrays ¶''

''Default value: false''

''When use_fast_arrays is true, arrays declared by array are values instead of properties, and undeclared arrays (hashed arrays) are implemented as Lisp hashed arrays.''

''When use_fast_arrays is false, arrays declared by array are properties, and undeclared arrays are implemented with Maxima’s own hashed array implementation.''

''Note that the code use_fast_arrays switches to is not necessarily faster than the default one; Arrays created by make_array are not affected by use_fast_arrays.&quot;''&lt;/blockquote&gt;
This Maxima Manual entry requires some elaboration in order to have a sufficient understanding of the effect of the &lt;code&gt;'''use_fast_arrays'''&lt;/code&gt; &quot;flag&quot; – referred to as an &quot;Option Variable&quot; in the above quotation.

The first point to note is that the default value of this flag is &lt;code&gt;false&lt;/code&gt;. So, if users take no action to assign this flag to the value &lt;code&gt;true&lt;/code&gt;, then declared arrays created using the &lt;code&gt;array()&lt;/code&gt; operator  are treated as ''properties'' bound to a symbol, and behave in the manner previously described. Likewise undeclared arrays are a Maxima array implementation, and behave as legacy property hash tables, and these also behave as previously described.

If action is taken to enter an expression that assigns the value &lt;code&gt;true&lt;/code&gt; to this flag, then Maxima treat arrays as standard Lisp ''values'' rather than object properties:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i142)	use_fast_arrays;
(%o142)	false

(%i143)	array (A1,fixnum, 10);
(%o143)	A1

(%i144)	arrayinfo (A1);
(%o144)	[complete,1,[10]]

(%i145)	H1[1] : 1729;
(H1[1])	1729

(%i146)	arrayinfo (H1);
(%o146)	[hashed,1,[1]]

(%i147)	use_fast_arrays : true;
(use_fast_arrays)	true

(%i148)	array (A2, fixnum, 10);
(%o148)	\#\{Lisp array \[11\]\}

(%i149)	A2;
(%o149)	\#\{Lisp array \[11\]\}

(%i150)	H2[1] : 1729;
(H2[1])	1729

(%i151)	H2;
(%o151)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 2 {1203AD15A3}&gt;&quot;

(%i152)	arrayinfo (H2);
(%o152)	[hash_table,1,1]
&lt;/syntaxhighlight&gt; The &lt;code&gt;use_fast_arrays&lt;/code&gt; flag has no effect on arrays created using the &lt;code&gt;make_array ()&lt;/code&gt; operator.

Note the following:

* Assigning &lt;code&gt;use_fast_arrays&lt;/code&gt; &lt;code&gt;: true&lt;/code&gt; does not speed up execution for all operations. It primarily optimizes memory footprint by minimizing cell allocations.  The main benefit is optimization of memory footprints and structural representation inside Lisp.
* If compiling Maxima expressions to native Lisp using the &lt;code&gt;translate&lt;/code&gt; &lt;code&gt;()&lt;/code&gt; operator, pair this flag with &lt;code&gt;translate_fast_arrays&lt;/code&gt; &lt;code&gt;: true&lt;/code&gt;. This flag instructs the translator to compile arrays as value-based.

=== Structures ===
Structures, although not an array data type is an aggregation data type.  By &quot;aggregation&quot; it is meant a data type that references other data types by reference to a name and some method of accessing individual values of instances of that aggregation by means of indices used to reference values individually.

Thus, as has been previously described for example lists, hashed arrays, Lisp arrays, and declared arrays are all aggregation data types with syntactical means to refer to individual values of a named aggregation instance by way of indices, which are sometimes also referred to as subscripts or keys.

As examples:

* An existing '''list''' named &lt;code&gt;L1&lt;/code&gt; has values that can be accessed as &lt;code&gt;L1[1]&lt;/code&gt;, &lt;code&gt;L[2]&lt;/code&gt;, &lt;code&gt;L[3]&lt;/code&gt;, and so forth
* An existing '''hashed array''' with two indices (&quot;2D&quot;) named &lt;code&gt;ha&lt;/code&gt; has values that can accessed as &lt;code&gt;ha[1,1&lt;/code&gt;], &lt;code&gt;ha[1,2]&lt;/code&gt;,..., &lt;code&gt;ha[2,1]&lt;/code&gt;, &lt;code&gt;ha[2,2]&lt;/code&gt;, and  so forth.
* An existing '''declared array''' with three indices (&quot;3D&quot;) named &lt;code&gt;da&lt;/code&gt; has values that can be accessed as &lt;code&gt;da[1,1,1]&lt;/code&gt;, &lt;code&gt;da[1,1,2]&lt;/code&gt;,...,&lt;code&gt;da [2,1,1]&lt;/code&gt;, ..., &lt;code&gt;da[3,1,1]&lt;/code&gt;, and so forth.

What makes the Maxima structure data type different from these array data types is the form of definition used and the means of accessing values of an instance of this type of aggregation. The Maxima structure data type seems to be the closest type of data that resembles an object in some other general-purpose programming languages.

The structure type of data allows the creation of named entities with attributes, and named instances of those entities and the assignment of values to those attributes. Thus the Maxima structure data type is used to define custom, named composite data types that group related fields together under a single identifier. Structures enhance code organization and readability, especially when modeling real-world entities in symbolic computations. They are useful for managing complex data in programs involving algebraic manipulations, simulations, or data modeling.  

Structures are created using the &lt;code&gt;defstruct&lt;/code&gt; operator, which defines a template with named attributes. Once defined, instances of the structure are created using the &lt;code&gt;new&lt;/code&gt; operator, and attributes are accessed via the &lt;code&gt;@&lt;/code&gt; operator. 

So in the interest of taking advantage of this information, consider a well-defined set of people. The people of this set may have many diverse attributes that might be of interest - name, age ,and city of residence as examples. A class of people of the set of interest with these attributes can be defined as follows: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i153)	defstruct (person (name, age, city));
(%o153)	[person(name,age,city)]

(%i54) structures;
(%o154)                      [person(name, age, city)]

(%i155)	p : new (person (&quot;Alice&quot;, 30, &quot;New York&quot;));
(p)	person(name=&quot;Alice&quot;,age=30,city=&quot;New York&quot;)

(%i156)	p@name;
(%o156)	&quot;Alice&quot;

(%i157)	p@city;
(%o157)	&quot;New York&quot;

(%i158)	kill(p@city);
(%o158)	done

/* If the attribute a in x has not been assigned a value, or the value
   has been &quot;killed,&quot; then x@a evaluates to itself */

(%i159)	p@city;
(%o159)	p@city

(%i160)	p;
(%o160)	person(name=&quot;Alice&quot;,age=30,city)

(%i161)	p@city : &quot;Rochester&quot;;
(%o161)	&quot;Rochester&quot;

(%i162)	p;
(%o162)	person(name=&quot;Alice&quot;,age=30,city=&quot;Rochester&quot;)

(%i163) defstruct (sales(LastName, Sales , Country , Quarter) );
(%o163)             [sales(LastName, Sales, Country, Quarter)]

(%i164) structures;
(%o164) [person(name, age, city), sales(LastName, Sales, Country, Quarter)]

(%i165) s : new (sales (&quot;Smith&quot;,16753.00,&quot;UK&quot;,&quot;Qtr 3&quot;));
(%o165) sales(LastName=Smith, Sales=16753.0, Country=UK, Quarter=Qtr 3)

(%i166) s@Sales;
(%o166)                              16753.0

(%i167) s@Sales : 17375.0;
(%o167)                              17375.0

(%i168) s;
(%o168) sales(LastName=Smith, Sales=17375.0, Country=UK, Quarter=Qtr 3)&lt;/syntaxhighlight&gt;{{Bookcat}}</text>
      <sha1>pk4i72rglnjn7148qknkvxch5hjzmdb</sha1>
    </revision>
    <revision>
      <id>4668963</id>
      <parentid>4668961</parentid>
      <timestamp>2026-09-05T17:31:26Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <minor />
      <comment>/* Introduction */</comment>
      <origin>4668963</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="64547" sha1="plwzzicy0cex5uj57qssmeqzbudm74e" xml:space="preserve">== Maxima Aggregate Data Structures ==

=== Introduction ===
This section is intended to present some of the essentials of what is called Maxima aggregate data structures. By this it is meant the data types that can be used to refer to the values of expressions using a means of indexing of a single identifier (name) that refers to an aggregate (collection) of expressions as values.

Built-in aggregate data types include: 

* lists
* hashed arrays
* declared arrays
* structures

Each of these has a means of indexing an identifier that names an instance of these data types. 

Please note that it is the case that this means of indexing an identifier for an aggregate data type may be referred to as involving &quot;subscripts&quot; or &quot;sub-scripted variables&quot; or &quot;keys&quot; as used by various computer programming languages, as well as in the context of Maxima documentation and commentary. In this book terms such as &quot;index&quot; or &quot;indices&quot; or &quot;indexed identifiers&quot;  are used instead.

Also all built-in Maxima functions (including packages) for these data types are referred to as ''&quot;operators&quot;'' and not ''&quot;functions&quot;'' as this latter term in general serves better to refer to Maxima function expressions defined by the user -- as in &lt;code&gt;f(x) :=&lt;/code&gt;, &lt;code&gt;g[s] :=&lt;/code&gt; and &lt;code&gt;define ()&lt;/code&gt; as examples.

This section is not intended to be exhaustive. It is intended to provide familiarity with aggregate data types. What is included has been gleaned from various sources, and only a few attributions are provided. Therefore, there is no claim of originality implied. 

=== Lists ===

==== Introduction to Lists ====
Lists are one of the basic buildings block for Maxima and Lisp. Maxima expressions are in general represented as Lisp lists. 

For example, consider the Maxima expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	e+3;
(%o1)	e+3
&lt;/syntaxhighlight&gt;This expression has the form of a Lisp list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i2)	:lisp #$[e+3]$
((MLIST SIMP) ((MPLUS SIMP) 3 $E))
&lt;/syntaxhighlight&gt;An expression in the form of a Lisp list can also be be displayed as a Maxima expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i2)	:lisp (displa '((MLIST SIMP) ((MPLUS SIMP) 3 $E)));
[e+3]
NIL
&lt;/syntaxhighlight&gt;Note that the value of this expression using &lt;code&gt;displa '()&lt;/code&gt; is &lt;code&gt;NIL&lt;/code&gt;, and &lt;code&gt;[e+3]&lt;/code&gt; is simply displayed in Maxima list object form. It is not necessary for the typical uses of Maxima to utilize this insight into the role Lisp lists have as one of the building blocks for Maxima, but it may be useful to have a familiarity with that role. Lists are often used as arguments to many operators, and the values of expressions are often in the form of lists.

==== Some Operators for Lists ====
Lists are created explicitly and list elements referenced using &lt;code&gt;[&lt;/code&gt; and &lt;code&gt;]&lt;/code&gt; to mark the beginning and end, respectively, of an instance of a list object, or to reference the expressions of an existing list object.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i3)	[2,3,4];
(%o3)	[2,3,4]
&lt;/syntaxhighlight&gt;The expression &lt;code&gt;[2,3,4]&lt;/code&gt; creates a Maxima list object. In this case the object itself is not accessible as it was not assigned an identifier unless referenced by the &lt;code&gt;%&lt;/code&gt; , &lt;code&gt;%i&lt;/code&gt; or &lt;code&gt;%o&lt;/code&gt; label.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i4)	%;
(%o4)	[2,3,4]

(%i5)	%o4[2]; /* second expression of list object referenced by index */ 
(%o5)	3
&lt;/syntaxhighlight&gt;That [2,3,4] is a list object can be tested using the &lt;code&gt;listp()&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i6)	listp ([2,3,4]);
(%o6)	true
&lt;/syntaxhighlight&gt;A list object can be assigned an identifier:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i7)	s:[%pi,%e,%phi];
(s)	[%pi,%e,%phi]

(%i8)	listp (s);
(%o8)	true&lt;/syntaxhighlight&gt;

The value of an element of a list can be accessed using the list identifier and brackets with a index value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i9)	s[1];
(%o9)	%pi

(%i10)	s[2];
(%o10)	%e

(%i11)	s[3];
(%o11)	%phi
&lt;/syntaxhighlight&gt;
Invalid index values returns an error:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i12)	s[4];
inpart: invalid index 4 of list or matrix.
-- an error. To debug this try: debugmode(true);
&lt;/syntaxhighlight&gt;
Consider the following relatively long list of integer atoms created explicitly and identified as &lt;code&gt;List_1&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i13)	List_1:[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582,145,2,
	    118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,
	    30,3,484,51,3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,4,
	    484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,5,118,30,5,484,
	    
	    49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177];

(List_1)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,2,1582,203
,3,118,30,3,484,51,3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,
214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177]&lt;/syntaxhighlight&gt;
The number of values of this list can be returned using the &lt;code&gt;length()&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i14)	length (List_1);
(%o14)	105
&lt;/syntaxhighlight&gt;
Create another list identified as &lt;code&gt;List_2&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i15)	List_2 : [6,1455,200,6,1607,205];
(List_2)	[6,1455,200,6,1607,205]

(%i16)	length (List_2);
(%o16)	6
&lt;/syntaxhighlight&gt;
Create a third list identified as &lt;code&gt;List_3&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i17)	List_3 : append (List_1, List_2)$

(%i18)	length (List_3);
(%o19)	111
&lt;/syntaxhighlight&gt;
Note that the &lt;code&gt;'''append ()'''&lt;/code&gt; operator does not affect either of the list arguments &lt;code&gt;List_1&lt;/code&gt; or &lt;code&gt;List&lt;/code&gt;_2. It merely appends &lt;code&gt;List_2&lt;/code&gt; to &lt;code&gt;List_1&lt;/code&gt; and returns a new list, in this case assigned the identifier &lt;code&gt;List_3&lt;/code&gt;.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i20)	length (List_1);
(%o20)  105

(%i21)	length (List_2);
(%o21)  6

(%i22)	length (List_3);
(%o22)	111

(%i23)	List_3;
(%o23)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
         142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
         1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
         75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
         1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
         142,5,1372,174,5,1582,177,6,1455,200,6,1607,205]&lt;/syntaxhighlight&gt;
Values (the last one in this example) can be deleted from a list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i24)	last (List_3);
(%o24)	205

(%i25)	delete (last (List_3), List_3);
(%o25)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
         142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
         1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
         75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
         1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
         142,5,1372,174,5,1582,177,6,1455,200,6,1607]&lt;/syntaxhighlight&gt;
The &lt;code&gt;delete (List_3)&lt;/code&gt; expression creates a new list object using &lt;code&gt;List_3&lt;/code&gt;. &lt;code&gt;List_3&lt;/code&gt; itself is not affected by the &lt;code&gt;'''delete ()'''&lt;/code&gt; operator. Only the resulting list is affected. This is often the case with list operators. An identifier could be used to save the above resulting list if necessary:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* List_3 is the same length */
(%i26)	length(List_3); 
(%o26)	111

/* The last value of List_3 is the same */
(%i27)	List_3[111];
(%o27)	205

(%i28)	last(List_3);
(%o28)	205&lt;/syntaxhighlight&gt;There was only one instance of &lt;code&gt;205&lt;/code&gt; in &lt;code&gt;List_3&lt;/code&gt;, so only that value was deleted from the list of &lt;code&gt;%o25&lt;/code&gt;.  If there are more than one value then the &lt;code&gt;delete ()&lt;/code&gt; operator will remove all of those values from the returned list expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i29)	NewList_3 : delete(118, List_3)$ 

/* all five instances of 118 removed from List_3 as NewList_3 */
(%i30)	length(NewList_3);
(%o30)	106
&lt;/syntaxhighlight&gt;There are operators to refer to instances of list expressions by ordinal number:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i30)	FirstThreeList_3:[first(List_3), second(List_3), third(List_3)];
(FirstThreeList_3)	[1,118,30]
&lt;/syntaxhighlight&gt;Expressions of list objects can e referenced to create a new list object from the first n expressions of a list, the last n expressions of a list, or the rest remaining after n expressions from the beginning or -n expressions from the end of a list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* first three expressions of List_3 */
(%i31)	firstn(List_3,3); 
(%o31)	[1,118,30]

/* same three expressions of List_3 using the rest operator with -108 */
(%i32)	rest(List_3, -108); 
(%o32)	[1,118,30]

/* last three expressions of List_3 */
(%i33)	lastn(List_3,3); 
(%o33)	[6,1607,205]

/* same three expressions of List_3 using the rest operator with 108 */
(%i34)	rest(List_3, 108);
(%o34)	[6,1607,205]&lt;/syntaxhighlight&gt;Some further examples of the &lt;code&gt;'''firstn ()'''&lt;/code&gt;, &lt;code&gt;'''lastn ()'''&lt;/code&gt; and &lt;code&gt;'''rest ()'''&lt;/code&gt; list operators:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* first 63 expressions of List_3 */
(%i35)	firstn (List_3, 63);
(%o35)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,
         1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,
         1372,203,2,1582,203,3,118,30,3,484,51,3,664,75,3,1004,108,3,
         1231,115,3,1372,139,3,1582,140]

/* last 63 expressions of List_3 */
(%i36)	lastn (List_3, 63);
(%o36)	[3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,
         5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,
         1582,177,6,1455,200,6,1607,205]

/* first expressions of List_3 after removing the last 63*/
(%i37)	rest (List_3, -63);
(%o37)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,
         1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,
         1372,203,2,1582,203,3,118,30,3,484,51]
&lt;/syntaxhighlight&gt;Maxima programming expressions can be used with list operators to reference list expressions in various ways. For example, the expression which follows accesses the expressions of a list as lists of three each:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i38)	(L4 : List_4,
	      for i:(-length (List_4)) + 3 thru 0 step 3 do
	             (disp (rest (L4, i)), 
	              L4 : rest (L4, 3)),
	     &quot;&quot;)$

[1,118,30]
[1,484,58]
[1,664,87]
[1,1004,115]
[1,1231,120]
[1,1372,142]
[1,1582,145]
[2,118,33]
[2,484,69]
[2,664,111]
[2,1004,156]
[2,1231,172]
[2,1372,203]
[2,1582,203]
[3,118,30]
[3,484,51]
[3,664,75]
&lt;/syntaxhighlight&gt;List operators can be used as arguments other list operators:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* create a new empty list */
(%i39)	newList4 : [];
(newList4)	[]

/* append the first six &amp; last six expressions of List_4 to the new list */
(%i40)	newList4 : append (newList4, firstn (List_4, 6), lastn (List_4, 6))$

/* the new list now has the 12 appended expressions from List_4 */
(%i41)	newList4;
(%o41)	[1,118,30,1,484,58,3,484,51,3,664,75]
&lt;/syntaxhighlight&gt;

Maxima programming expressions can be used to step through the expressions of lists using list operators to reference &quot;slices&quot; of different lengths:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i42)	L4 : List_4;
(L4)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582
         145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,
         2,1582,203,3,118,30,3,484,51,3,664,75]

(%i43)	length (L4);
(%o43)	51

(%i44)	(L4 : List_4,
         for i : 21 thru 3 step -3 do
	         print (L4 : lastn (L4, i),&quot; &quot;, length (L4)),
	    &quot;&quot;)$

[2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 21

[2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 18

[2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 15

[2,1582,203,3,118,30,3,484,51,3,664,75] 12

[3,118,30,3,484,51,3,664,75] 9

[3,484,51,3,664,75] 6

[3,664,75] 3&lt;/syntaxhighlight&gt;

==== Using the &lt;code&gt;copylist&lt;/code&gt; Operator ====
When an existing list object is assigned to an identifier, a reference to the memory location of the list object is used. This reference to the memory location is transparent from the point of view of the user. However,if this is not  accounted for unintended side effects may occur when assigning another identifier to an existing one that references a list object.

For example, in the expression &lt;code&gt;L4 : List_4&lt;/code&gt; it might be assumed that this results in the list object referenced by &lt;code&gt;List_4&lt;/code&gt; to simply be copied to a new memory location and reference for &lt;code&gt;L4&lt;/code&gt;. This is not the case. Both &lt;code&gt;L4&lt;/code&gt; and &lt;code&gt;List_4&lt;/code&gt; refer to the same list object in memory. Consequently changes to the same list object can be effected by referencing the object using either alias.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i45)	newList4;
(%o45)	[1,118,30,1,484,58,3,484,51,3,664,75]

/* The identifier newList4 refers to a location in memory.
   The colon (:) assignment operator simply creates an alias
   using that same memory reference*/

(%i46)	newList5 :  newList4;
(newList5)	[1,118,30,1,484,58,3,484,51,3,664,75]

/* Two different identifiers for the same memory location and
   therefore the same object. Changes to expressions of the list
   object using either identifier changes the same object in memory */
   
(%i47)	newList5[1] : 99;
(newList5[1])	99

(%i48)	newList4[1];
(%o48)	99

(%i49)	newList4;
(%o49)	[99,118,30,1,484,58,3,484,51,3,664,75]

(%i50)	newList5;
(%o50)	[99,118,30,1,484,58,3,484,51,3,664,75]
&lt;/syntaxhighlight&gt;
This &quot;side effect&quot; is often unwanted. The way to avoid this is by using the &lt;code&gt;copylist ()&lt;/code&gt; operator instead of the assignment operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i51)	newList4 : [1,118,30,1,484,58,3,484,51,3,664,75] ;
(newList4)	[1,118,30,1,484,58,3,484,51,3,664,75]

(%i52)	newList5 : copylist (newList4);
(newList5)	[1,118,30,1,484,58,3,484,51,3,664,75]
 
 /* Same list object expressions, but a different memory reference */

(%i53)	newList5[1] : 99;
(newList5[1])	99

(%i54)	newList4[1];
(%o54)	1
&lt;/syntaxhighlight&gt;
Changes to the values of either list will not affect the other list.
{| class=&quot;wikitable&quot;
|+List Object Operators
|[
|fourth
|rreduce
|-
|]
|fullsetify
|second
|-
|append
|join
|setify
|-
|assoc
|last
|seventh
|-
|cons
|length
|sixth
|-
|copylist
|listarith
|some
|-
|create_list
|listp
|sort
|-
|delete
|lmax
|sublist
|-
|eighth
|lmin
|sublist_indices
|-
|endcons
|lreduce
|tenth
|-
|fifth
|makelist
|third
|-
|first
|member
|tree_reduce
|-
|flatten
|reverse
|xreduce
|}

Refer to the Maximal Manual&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.4.2 Functions and Variables for Lists |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Lists}}&lt;/ref&gt; for more complete description of operators and variables for Maxima lists.

==== Performance Considerations for Lists ====
&lt;blockquote&gt;''&quot;Lists provide efficient ways of appending and removing elements. They can be created without knowing their final dimensions. Lisp provides efficient means of copying and handling lists. Also nested lists do not need to be strictly rectangular. These advantages over declared arrays come with the drawback that the amount of time needed for accessing a random element within a list may be roughly proportional to the element’s distance from its beginning.&quot;''&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.4.3 Performance considerations for Lists |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Lists}}&lt;/ref&gt;&lt;/blockquote&gt;Maxima list objects have many operators for creating, accessing, and changing the expressions of lists. Evaluation times of expressions that involve lists can vary significantly depending on the length of the list objects involved, as well as the nature of any operators used to compose the expressions. This fact might have an influence on the choice of using arrays rather than lists in some cases if evaluation time is a factor to consider. The example expressions that follow involve a list object (identified as &lt;code&gt;s&lt;/code&gt; ) of complex number expressions that has a length of 10,000 and two different user-defined functions:&lt;pre&gt;(%i55) P1(s) := rectform (product(s[i], i, 1, length (s)))$

(%i56) P2(s) := xreduce (lambda ([a, b], rectform (a * b)), s)$

(%i57) s : makelist (random (1.0) + %i*random (1.0), 10^4)$

(%i58)	showtime : true$
Evaluation took 0.0000 seconds (0.0000 elapsed) using 0 bytes.

(%i59) P1(s);
Evaluation took 32.3080 seconds (32.3860 elapsed) using 17944.301 MB.
(%o59) 0.0

(%i60) P2(s);
Evaluation took 0.0620 seconds (0.0620 elapsed) using 8.343 MB.
(%o60) 0.0

(%i61)	showtime : false$
Evaluation took 0.0000 seconds (0.0000 elapsed) using 0 bytes.&lt;/pre&gt;
==Arrays ==
&lt;blockquote&gt;&quot;Maxima's current array/matrix semantics are a mess, I must say, with at least four different kinds of object (hash arrays, explicit lists, explicit matrices, Lisp arrays) supporting subscripting with varying semantics.&quot; &lt;ref&gt;[http://comments.gmane.org/gmane.comp.mathematics.maxima.general/21829 Maxima: Syntax improvements by Stavros Macrakis ]&lt;/ref&gt;
– Stavros Macrakis

&quot;Maxima's concept of arrays, lists, and matrices is pretty confused, since various ideas have accreted in the many years of the project... Yes, this is a mess. Sorry about that. These are all interesting ideas, but there is no unifying framework.&quot;&lt;ref&gt;[http://stackoverflow.com/a/29926692 Maxima: what does Maxima call an “array”? - answer by Robert Dodier]&lt;/ref&gt;

– Robert Dodier&lt;/blockquote&gt;

The various terminology used in the context of arrays undoubtedly can be confusing. For the sake of simplicity and clarity the following categories of array objects are referred to in this book:


Maxima has three array categories :&lt;ref&gt;[http://permalink.gmane.org/gmane.comp.mathematics.maxima.general/13588 the Maxima mailing list &lt;nowiki&gt;: [Maxima] array and matrix? - answer by Robert Dodier&lt;/nowiki&gt;]&lt;/ref&gt;
* Declared arrays 
* Undeclared (hashed) arrays 
* Lisp arrays 

'''''Declared arrays''''' are explicitly created using the &lt;code&gt;array()&lt;/code&gt; operator, and unlike lists, which have only one index and are one-dimensional, declared  arrays can be multi-dimensional  – having one to five indices. The indices for declared array dimensions need not be equal.

Indices for each dimension may be between 0 and the respective declared dimension. Each declared array may be for expressions of a specified type, which can be ''fixnum'' for integers or ''flonum'' for floating-point numbers.

'''''Undeclared (hashed) arrays''''' are created implicitly by assigning an expression to an indexed identifier that does not name an existing list object. An undeclared array (hashed array) can grow dynamically as there is no fixed dimension limit for each index as there is with declared arrays Another difference is that numbers, identifiers, expressions and strings may be used for indices.

Also, there is no fixed limit on the number of dimensions. The only real limitation is practical – the available computer memory and the underlying Lisp environment of the Maxima session. Hashed arrays with only one dimension may be confused with a list object.

It is essential to keep in mind that list objects must always be created before values are assigned or referenced. Assigning an expression to a one-dimensional indexed identifier, that does not reference an existing list, implicitly creates a hashed array.

'''''Lisp arrays''''' are created using the &lt;code&gt;'''make_array ()'''&lt;/code&gt; operator. The array type may be specified as ''any'', ''flonum'', ''fixnum'', or ''hashed''. Lisp array objects may be created as one-dimensional or multi-dimensional as specified by the number of dimension size values used with the &lt;code&gt;'''make_array ()'''&lt;/code&gt; operator. For each  dimension value specified, the associated index value can be a number between 0 to 1 less than the respective dimension value. The same or different values may be used for each specified dimension. the ''hashed'' type does not require any dimensions. Lisp arrays may be used in cases where memory usage and garbage collection are factors.

Examples of use and elaboration upon the technical details for each of these categories of array object types follows.
{| class=&quot;wikitable&quot;
|+Array Operators and Flags
|array
|arraysetapply
|rearray
|-
|arrayapply
|has_key
|remarray
|-
|arrayinfo
|fillarray
|subvar
|-
|arraymake
|listarray
|subvarp
|-
|arrays
|make_array
|use_fast_arrays
|-
|
|
|translate_fast_arrays
|}
=== Declared Arrays ===
Declared arrays must be created before being referenced and are of fixed dimensions.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	array(A1, fixnum, 34,2); 
(%o1)	A1

(%i2)	array(A2, flonum, 35,2);
(%o2)	A2

(%i3)	array(A3, 14,3);
(%o3)	A3

(%i4)	arrayinfo (A1);
(%o4)	[complete,2,[34,2]]

(%i5)	arrayinfo (A2);
(%o5)	[complete,2,[35,2]]

(%i6)	arrayinfo (A3);
(%o6)	[declared,2,[14,3]]
&lt;/syntaxhighlight&gt;
The first expression &lt;code&gt;%i1&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A1&lt;/code&gt;. This array is two-dimensional – the first index may have values from 0 to 34 and the second index may have values from 0 to 2. This array therefore is 35 by 3 in extent. The array type is declared to be &lt;code&gt;fixnum&lt;/code&gt;. As it is, &lt;code&gt;A1&lt;/code&gt; is an not empty array – it has values to reference as will be exemplified below.

Similarly the second expression &lt;code&gt;%i2&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A2&lt;/code&gt;. This array is also two-dimensional – the first index may have values from 0 to 35 and the second index may have values from 0 to 2. This array therefore is 36 by 3 in extent. The array type is declared to be &lt;code&gt;flonum&lt;/code&gt;. As it is, &lt;code&gt;A2&lt;/code&gt; is not an empty array – it also has values to reference as will be exemplified below.

The third expression &lt;code&gt;%i3&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A3&lt;/code&gt;. This array is also two-dimensional – the first index may have values from 0 to 13 and the second index may have values from 0 to 3. This array therefore is 15 by 4 in extent. The array type is not declared. As it is, &lt;code&gt;A3&lt;/code&gt; is an empty array – it has no values to reference as will be exemplified below.

The &lt;code&gt;'''arrayinfo ()'''&lt;/code&gt; operator can be used to return a list object that has values reflecting information about an array. Note that arrays declared without a type will have &lt;code&gt;declared&lt;/code&gt; as a value of the list. Arrays declared with &lt;code&gt;fixnum&lt;/code&gt; or &lt;code&gt;flonum&lt;/code&gt; as the type will have &lt;code&gt;complete&lt;/code&gt; as a value of the list. This technical detail is not well-documented. The returned information list also shows a value for the dimension of the array ( 2 in these examples ) and an inner list with values for the maximum index for each dimension.

A look inside each of these declared arrays provides a clue as to why &lt;code&gt;complete&lt;/code&gt; is returned instead of &lt;code&gt;declared&lt;/code&gt; when the type is specified as &lt;code&gt;fixnum&lt;/code&gt; or &lt;code&gt;flonum&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* This array reference has a value of 0 */
(%i7)	A1[0,0];
(%o7)	0

/* This array reference has a value of 0.0 */
(%i8)	A2[0,0];
(%o8)	0.0

/* This array reference has a value of itself */
(%i9)	A3[0,0];
(%o9)	A3[0,0]&lt;/syntaxhighlight&gt;

In fact, ''all'' values of the array &lt;code&gt;A1&lt;/code&gt; have been assigned 0, and ''all'' values of the array &lt;code&gt;A2&lt;/code&gt; have beenassigned 0.0. However, ''all'' values of the array &lt;code&gt;A3&lt;/code&gt; have been not been assigned any value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i10)	listarray(A1);
(%o10)	[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0]

(%i11)	listarray(A2);
(%o11)	[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]

(%i12)	listarray(A3);
(%o12)	[#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####]&lt;/syntaxhighlight&gt;

Thus, arrays &lt;code&gt;A1&lt;/code&gt; and &lt;code&gt;A2&lt;/code&gt; are &lt;code&gt;complete&lt;/code&gt; in this sense, and array &lt;code&gt;A3&lt;/code&gt; is simply &lt;code&gt;declared&lt;/code&gt;.

It might seem reasonable, that Maxima would complain if a value was assigned to an array that is at odds with the declared type. Such is not the case however. Once an array is declared with a type, Maxima does not enforce any type checking of values assigned to the array. The effect of the type (if any) in the declaration is simply to fill the array with values of #####, 0 or 0.0. Subsequently, those values can be replaced by the assignment of different values that will not be checked for the type of value. One way to enforce type checking is by using predicate operators to check values at the point in time of assignment to arrays. For example, using one or more of:

* numberp (expr)
* floatnump (expr)
* integerp (expr) 
* ratnump (expr)
* stringp (obj)
* listp (expr) 
* featurep (a, f)

and possibly others.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* A1 was declared as type fixnum */
(%i13)	A1[5,2]:3.14159;
(%o13)	3.14159

/* A2 was declared as type flonum */
(%i14)	A2[3,0]:7129;
(%o14)	7129

/* A1 which was declared as type fixnum assigned a string */
(%i15)	A1[4,1]:&quot;a string&quot;;
(%o15)	&quot;a string&quot;

/* A2 which was declared as type flonum assigned a math expression*/
(%i16)	A2[6,1]:3*x^2 + 4*x +10; 
(%o16)	3*x^2+4*x+10
&lt;/syntaxhighlight&gt;

There are other ways to assign values to an array. One way is to read the values from a comma separated (CSV) file  using the &lt;code&gt;'''read_array ()'''&lt;/code&gt; operator from the ''numericalio'' package.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i17) load(numericalio);
(%o17) &quot;/app/plugins/maxima/share/maxima/5.50.0/share/numericalio/numericalio.mac&quot;


&lt;/syntaxhighlight&gt;

Below are of the values of the CSV data file &lt;code&gt;tree_data_nh.csv&lt;/code&gt; :&lt;syntaxhighlight lang=&quot;text&quot;&gt;
1,118,30
1,484,58
1,664,87
1,1004,115
1,1231,120
1,1372,142
1,1582,145
2,118,33
2,484,69
2,664,111
2,1004,156
2,1231,172
2,1372,203
2,1582,203
3,118,30
3,484,51
3,664,75
3,1004,108
3,1231,115
3,1372,139
3,1582,140
4,118,32
4,484,62
4,664,112
4,1004,167
4,1231,179
4,1372,209
4,1582,214
5,118,30
5,484,49
5,664,81
5,1004,125
5,1231,142
5,1372,174
5,1582,177
&lt;/syntaxhighlight&gt;

Note that the following expression assumes that the CSV file is located in the Maxima working directory.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i18)	read_array(&quot;tree_data_nh.csv&quot;, A1, &quot;,&quot;); 
(%o18)	done

(%i19)	 listarray(A1);
(%o19)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,
         1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,
         2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75,3,1004,108,
         3,1231,115,3,1372,139,3,1582,140,4,118,32,4,484,62,4,664,112,
         4,1004,167,4,1231,179,4,1372,209,4,1582,214,5,118,30,5,484,49,
         5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177]
&lt;/syntaxhighlight&gt;
Below are of the values of the CSV data file &lt;code&gt;tree_data.csv&lt;/code&gt;  which has a header row, but is otherwise the same as &lt;code&gt;tree_data_nh.csv&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;text&quot;&gt;
&quot;Tree&quot;,&quot;age&quot;,&quot;circumference&quot;
1,118,30
1,484,58
1,664,87
1,1004,115
1,1231,120
1,1372,142
1,1582,145
2,118,33
2,484,69
2,664,111
2,1004,156
2,1231,172
2,1372,203
2,1582,203
3,118,30
3,484,51
3,664,75
3,1004,108
3,1231,115
3,1372,139
3,1582,140
4,118,32
4,484,62
4,664,112
4,1004,167
4,1231,179
4,1372,209
4,1582,214
5,118,30
5,484,49
5,664,81
5,1004,125
5,1231,142
5,1372,174
5,1582,177
&lt;/syntaxhighlight&gt;&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i20)	read_array(&quot;tree_data.csv&quot;, A2, &quot;,&quot;); 
(%o20)	done

(%i21) listarray(A2);
(%o21) [&quot;Tree&quot;,&quot;age&quot;,&quot;circumference&quot;,1,118,30,1,484,58,1,664,87,1,1004,
        115,1,1231,120,1,1372,142,1,1582,145,2,118,33,2,484,69,2,664,111,
        2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,
        3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
        4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,
        5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,
        5,1582,177]&lt;/syntaxhighlight&gt;The previous values of 0 and 0,0 as well as the assigned values of &lt;code&gt;A1&lt;/code&gt; and &lt;code&gt;A2&lt;/code&gt; have been replaced with the values from the CSV files.

The third array A3 can be used with values from the  dataset.csv file below:&lt;syntaxhighlight lang=&quot;text&quot;&gt;&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;
&quot;Smith&quot;,16753.00,&quot;UK&quot;,&quot;Qtr 3&quot;
&quot;Johnson&quot;,14808.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Williams&quot;,10644.00,&quot;UK&quot;,&quot;Qtr 2&quot;
&quot;Jones&quot;,1390.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Brown&quot;,4865.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Williams&quot;,12438.00,&quot;UK&quot;,&quot;Qtr 1&quot;
&quot;Johnson&quot;,9339.00,&quot;UK&quot;,&quot;Qtr 2&quot;
&quot;Smith&quot;,18919.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Jones&quot;,9213.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Jones&quot;,7433.00,&quot;UK&quot;,&quot;Qtr 1&quot;
&quot;Brown&quot;,3255.00,&quot;USA&quot;,&quot;Qtr 2&quot;
&quot;Williams&quot;,14867.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Williams&quot;,19302.00,&quot;UK&quot;,&quot;Qtr 4&quot;
&quot;Smith&quot;,9698.00,&quot;USA&quot;,&quot;Qtr 1&quot;&lt;/syntaxhighlight&gt;&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i22)	read_array(&quot;dataset.csv&quot;, A3, &quot;,&quot;); 
(%o22)	done

(%i23)	 listarray(A3);
(%o23)	[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;,
         &quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;,
         &quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;,
         &quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;,
         &quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;,
         &quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;,
         &quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;,
         &quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;,
         &quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]&lt;/syntaxhighlight&gt;

Values of the array can be referenced by indices as required for some purpose:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i24)	A3[0,0];
(%o24)	&quot;Last Name&quot;

(%i25)	A3[4,2];
(%o25)	&quot;USA&quot;
&lt;/syntaxhighlight&gt;
A row list object can be created using the &lt;code&gt;'''makelist ()'''&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i26)	row1A3: makelist(A3[0, j], j, 0, 3)$

(%i27)	row1A3;
(%o27)	[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;]

(%i28)	row1A3[1];
(%o28)	&quot;Last Name&quot;

(%i29)	row15A3: makelist(A3[14, j], j, 0, 3)$

(%i30)	row15A3;
(%o30)	[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]

(%i31)	row15A3[2];
(%o31)	9698.0
&lt;/syntaxhighlight&gt;
A list of the indices of the array can be created:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i32)	indices_A3 : arrayinfo(A3)[3];
(indices_A3)	[14,3]
&lt;/syntaxhighlight&gt;
The number of indices of array &lt;code&gt;A3&lt;/code&gt; can also be referenced using the &lt;code&gt;'''length (''')&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i33)	length(arrayinfo(A3)[3]);
(%o33)	2
&lt;/syntaxhighlight&gt;The number of values of the array &lt;code&gt;A3&lt;/code&gt; can be returned using the '''&lt;code&gt;length ()&lt;/code&gt;''' operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i34)	length(listarray(A3));
(%o34)	60
&lt;/syntaxhighlight&gt;
The values of the array &lt;code&gt;A3&lt;/code&gt; can be printed as output using the list of values with a loop programming expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i35)	for i:1 thru length (listarray(A3)) do 
            print('A3[i] ,&quot; = &quot;,  listarray(A3)[i])$

A3[1]&quot; = &quot;&quot;Last Name&quot;
A3[2]&quot; = &quot;&quot;Sales&quot;
A3[3]&quot; = &quot;&quot;County&quot;
A3[4]&quot; = &quot;&quot;Quarter&quot;
A3[5]&quot; = &quot;&quot;Smith&quot;
A3[6]&quot; = &quot;16753.0
A3[7]&quot; = &quot;&quot;UK&quot;
A3[8]&quot; = &quot;&quot;Qtr 3&quot;
A3[9]&quot; = &quot;&quot;Johnson&quot;
A3[10]&quot; = &quot;14808.0
A3[11]&quot; = &quot;&quot;USA&quot;
A3[12]&quot; = &quot;&quot;Qtr 4&quot;
A3[13]&quot; = &quot;&quot;Williams&quot;
A3[14]&quot; = &quot;10644.0
A3[15]&quot; = &quot;&quot;UK&quot;
A3[16]&quot; = &quot;&quot;Qtr 2&quot;
A3[17]&quot; = &quot;&quot;Jones&quot;
A3[18]&quot; = &quot;1390.0
A3[19]&quot; = &quot;&quot;USA&quot;
A3[20]&quot; = &quot;&quot;Qtr 3&quot;
A3[21]&quot; = &quot;&quot;Brown&quot;
A3[22]&quot; = &quot;4865.0
A3[23]&quot; = &quot;&quot;USA&quot;
A3[24]&quot; = &quot;&quot;Qtr 4&quot;
A3[25]&quot; = &quot;&quot;Williams&quot;
A3[26]&quot; = &quot;12438.0
A3[27]&quot; = &quot;&quot;UK&quot;
A3[28]&quot; = &quot;&quot;Qtr 1&quot;
A3[29]&quot; = &quot;&quot;Johnson&quot;
A3[30]&quot; = &quot;9339.0
A3[31]&quot; = &quot;&quot;UK&quot;
A3[32]&quot; = &quot;&quot;Qtr 2&quot;
A3[33]&quot; = &quot;&quot;Smith&quot;
A3[34]&quot; = &quot;18919.0
A3[35]&quot; = &quot;&quot;USA&quot;
A3[36]&quot; = &quot;&quot;Qtr 3&quot;
A3[37]&quot; = &quot;&quot;Jones&quot;
A3[38]&quot; = &quot;9213.0
A3[39]&quot; = &quot;&quot;USA&quot;
A3[40]&quot; = &quot;&quot;Qtr 4&quot;
A3[41]&quot; = &quot;&quot;Jones&quot;
A3[42]&quot; = &quot;7433.0
A3[43]&quot; = &quot;&quot;UK&quot;
A3[44]&quot; = &quot;&quot;Qtr 1&quot;
A3[45]&quot; = &quot;&quot;Brown&quot;
A3[46]&quot; = &quot;3255.0
A3[47]&quot; = &quot;&quot;USA&quot;
A3[48]&quot; = &quot;&quot;Qtr 2&quot;
A3[49]&quot; = &quot;&quot;Williams&quot;
A3[50]&quot; = &quot;14867.0
A3[51]&quot; = &quot;&quot;USA&quot;
A3[52]&quot; = &quot;&quot;Qtr 3&quot;
A3[53]&quot; = &quot;&quot;Williams&quot;
A3[54]&quot; = &quot;19302.0
A3[55]&quot; = &quot;&quot;UK&quot;
A3[56]&quot; = &quot;&quot;Qtr 4&quot;
A3[57]&quot; = &quot;&quot;Smith&quot;
A3[58]&quot; = &quot;9698.0
A3[59]&quot; = &quot;&quot;USA&quot;
A3[60]&quot; = &quot;&quot;Qtr 1&quot;
&lt;/syntaxhighlight&gt;

Maxima treats declared arrays as fixed-sized, and individual values are accessed via indices. There is no built-in &quot;row&quot; object — rows must be extracted manually using the &lt;code&gt;'''makelist ()'''&lt;/code&gt; operator or by looping through values of an array.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i36)	array(rowsA3,15);
(%o36)	rowsA3

(%i37)	arrayinfo(rowsA3);
(%o37)	[declared,1,[15]]

(%i38)	for i:0 thru 14 do
	       (rowsA3[i+1]:makelist(A3[i, j], j, 0, 3),
	        print(&quot;Row &quot;,i+1,&quot;: &quot;,rowsA3[i+1]))$;

&quot;Row &quot;1&quot;: &quot;[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;]
&quot;Row &quot;2&quot;: &quot;[&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;3&quot;: &quot;[&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;4&quot;: &quot;[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;5&quot;: &quot;[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;6&quot;: &quot;[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;7&quot;: &quot;[&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;8&quot;: &quot;[&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;9&quot;: &quot;[&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;10&quot;: &quot;[&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;11&quot;: &quot;[&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;12&quot;: &quot;[&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;13&quot;: &quot;[&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;14&quot;: &quot;[&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;15&quot;: &quot;[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]
&lt;/syntaxhighlight&gt;
Maxima does not have a built-in function like &lt;code&gt;delete&lt;/code&gt; or &lt;code&gt;unset&lt;/code&gt; for removing individual values from arrays using indices. Existing values of an array can be changed by assignment however:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i52)	rowsA3[1]:[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;]$

(%i53)	for i:1 thru 15 do
	    (newRowsA3[i]:rowsA3[i],
	    print(&quot;Row &quot;,i,&quot;: &quot;,newRowsA3[i]))$;

&quot;Row &quot;1&quot;: &quot;[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;2&quot;: &quot;[&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;3&quot;: &quot;[&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;4&quot;: &quot;[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;5&quot;: &quot;[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;6&quot;: &quot;[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;7&quot;: &quot;[&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;8&quot;: &quot;[&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;9&quot;: &quot;[&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;10&quot;: &quot;[&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;11&quot;: &quot;[&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;12&quot;: &quot;[&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;13&quot;: &quot;[&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;14&quot;: &quot;[&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;15&quot;: &quot;[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]&lt;/syntaxhighlight&gt;
The &lt;code&gt;'''arrayapply ()'''&lt;/code&gt; operator can be used a follows to reference values of a declared array:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i39)	arrayapply(rowsA3,[5]);
(%o39)	[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]

(%i40)	arrayapply(A3, [5,1]);
(%o40)	4865.0
&lt;/syntaxhighlight&gt;The operator &lt;code&gt;'''fillarray (A, B)'''&lt;/code&gt; assigns values to array &lt;code&gt;A&lt;/code&gt; from &lt;code&gt;B&lt;/code&gt;, which can be a list or an array.The dimensions of the arrays &lt;code&gt;A&lt;/code&gt; and &lt;code&gt;B&lt;/code&gt; may not be the same. In that case, array &lt;code&gt;A&lt;/code&gt; is filled in &quot;row-major&quot; order. There may not be enough values in &lt;code&gt;B&lt;/code&gt; compared to &lt;code&gt;A&lt;/code&gt;. In that case, the last value of &lt;code&gt;B&lt;/code&gt; is used to for the remaining values of &lt;code&gt;A&lt;/code&gt;. There may be too many values of &lt;code&gt;B&lt;/code&gt; compared to array &lt;code&gt;A&lt;/code&gt;. In that case, the remaining values of &lt;code&gt;B&lt;/code&gt; once &lt;code&gt;A&lt;/code&gt; is filled are not used. The return value of &lt;code&gt;'''fillarray ()'''&lt;/code&gt; is not the filled array &lt;code&gt;A&lt;/code&gt;, but it is the first argument.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* Create a declared array B of type fixnum */
(%i41)	array (B, fixnum, 9);
(%o41)	B

/* list the values of array B */
(%i42)	listarray (B);
(%o42)	[0,0,0,0,0,0,0,0,0,0]

/* fill array B with the values of the list */
(%i43)	fillarray (B, [0,1, 2, 3, 4, 5, 6, 7, 8, 9.0]);
(%o43)	B

/* list the values of array B */
(%i44)	listarray (B);
(%o44)	[0,1,2,3,4,5,6,7,8,9.0]

/* fill array B with the value 1.0 */
(%i45)	fillarray (B, [1.0]);
(%o45)	B

/* list the values of array B */
(%i46)	listarray (B);
(%o46)	[1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0]

/* fill array B with the first 9 values of the list */
(%i47)	fillarray (B, [0,1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12]);
(%o47)	B

/* list the values of array B */
(%i48)	listarray (B);
(%o48)	[0,1,2,3,4,5,6,7,8,9]

/* Create a declared array D of no type */
(%i49)	array (D, 9);
(%o49)	D

/* list the values of array D */
(%i50)	listarray (D);
(%o50)	[#####,#####,#####,#####,#####,#####,#####,#####,#####,#####]

/* fill array D with the value 1.0 */ 
(%i51)	fillarray (D, [1.0]);
(%o51)	D

/* list the values of array D */
(%i52)	listarray (D);
(%o52)	[1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0]

/* Create a declared array E of no type */
(%i53)	array (E, 15);
(%o53)	E

/* fill array E with the values from the newRowsA3 list */ 
(%i54)	fillarray (E, listarray (newRowsA3));
(%o54)	E

/* list the values of array D */
(%i55)	listarray (E);
(%o55)	[[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;],
         [&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;],
         [&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]]

/* remove array E */
(%i56)	remarray (E);
(%o56)	[E]

/*  D is no longer an array */
(%i57)	arrayinfo (E);
arrayinfo: E is not an array.

 -- an error. To debug this try: debugmode(true);&lt;/syntaxhighlight&gt;

If you need to keep the array but remove only one value, you must reconstruct it without that value. The operator &lt;code&gt;'''remarray ()'''&lt;/code&gt; is the typical way to completely remove an array.

The &lt;code&gt;'''rearray (A, dim&lt;sub&gt;1&lt;/sub&gt;, dim&lt;sub&gt;2&lt;/sub&gt; ,…, dim&lt;sub&gt;n&lt;/sub&gt;)'''&lt;/code&gt; operator is used to change the dimensions of an array. The changed array will be filled with the elements of the existing array in row-major order. If the existing array has one or more smaller dimensions, the additional dimension values of the changed array are assigned with a value that depends on the type of the array. If the existing array has one or more larger dimensions, the deficient dimension values of the changed array are lost. The type of the array cannot be changed using this operator. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* list with the values of array B */
(%i58)	listarray(B);
(%o58)	[0,1,2,3,4,5,6,7,8,9]

/* list with information about array B */
(%i59)	arrayinfo(B);
(%o59)	[complete,1,[9]]

/* increase the dimension of array B */
(%i60)	rearray (B, 12);
(%o60)	\#\{Lisp array \[13\]\}

/* list with information about array B with increased dimension */
(%i61)	arrayinfo(B);
(%o61)	[complete,1,[12]]

/* list with the values of array B */
(%i62)	listarray(B);
(%o62)	[0,1,2,3,4,5,6,7,8,9,0,0,0]

/* decrease the dimension of array B */
(%i63)	rearray (B, 6);
(%o63)	\#\{Lisp array \[7\]\}

/* list with information about array B with decreased dimension */
(%i64)	arrayinfo(B);
(%o64)	[complete,1,[6]]

/* list with the values of array B */
(%i65)	listarray(B);
(%o65)	[0,1,2,3,4,5,6]


&lt;/syntaxhighlight&gt;

The &lt;code&gt;'''arraymake ()'''&lt;/code&gt; operator returns a value that is an array reference without evaluation. This operator, in spite of the name, does not &quot;make&quot; an array. It returns this reference as a value whether or not an array exists as an object:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* the arraymake operator returns the unevaluated reference to A */
(%i66)	arraymake (A, [i,j]);
(%o66)	A[i,j]

/* however array A is not an array object*/
(%i67)	arrayinfo (A);
arrayinfo: A is not an array.
 -- an error. To debug this try: debugmode(true);

/* Maxima sees A[j,k] as a reference to an undefined memoizing function */
(%i68)	op (arraymake (A, [i,j]));
(%o68)	A
&lt;/syntaxhighlight&gt;
However, from a practical point of view, this operator is used with existing arrays:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i69)	listarray (newRowsA3);
(%o69)	[[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;],
         [&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;],
         [&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]]

(%i70)	arraymake (newRowsA3, [4]);
(%o70)	newRowsA3[4]

(%i71)	''%;
(%o71)	[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]

(%i72)	arraymake (newRowsA3, [i]);
(%o72)	newRowsA3[i]

(%i73)	''%, i = 6;
(%o73)	[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]

&lt;/syntaxhighlight&gt;
The operator &lt;code&gt;arraymake (x, [i])&lt;/code&gt; constructs the expression &lt;code&gt;x[i]&lt;/code&gt;, but does not evaluate it. 

The operator &lt;code&gt;'''subvar'''&lt;/code&gt; &lt;code&gt;'''(x, i)'''&lt;/code&gt; evaluates the indexed expression &lt;code&gt;x[i]&lt;/code&gt;, and evaluates its arguments. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i74)	listarray(B);
(%o174)	[0,1,2,3,4,5,6]

(%i75)	x : B;
(x)	B

(%i76)	i : 4;
(i)	4

(%i77)	subvar (x, i);
(%o77)	4
&lt;/syntaxhighlight&gt;
The operator &lt;code&gt;'''subvarp (expr)'''&lt;/code&gt; returns a value of &lt;code&gt;true&lt;/code&gt; if &lt;code&gt;expr&lt;/code&gt; is a indexed identifier, and &lt;code&gt;false&lt;/code&gt; otherwise. This operator evaluates the argument &lt;code&gt;expr&lt;/code&gt;.  &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;

(%i78)	z[p];
(%o78)	z[p]

(%i79)	subvarp (z[p]);
(%o79)	true

(%i80)	x[i];
(%o80)	4

(%i81)	subvar (x, i)
(%o81)	4

(%i82)	w : z[p];
(w)	z[p]

(%i83)	subvarp (w);
(%o83)	true


&lt;/syntaxhighlight&gt;
The expression &lt;code&gt;'''arrays'''&lt;/code&gt;  returns a list of allocated arrays: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i84)	arrays;
(%o84)	[A3,A2,A1,rowsA3,newRowsA3,B,D]&lt;/syntaxhighlight&gt;

The operator &lt;code&gt;'''arraysetapply (A, [i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2,&lt;/sub&gt;…,i&lt;sub&gt;n&lt;/sub&gt;], x)'''&lt;/code&gt; assigns the value of expression &lt;code&gt;x&lt;/code&gt; to &lt;code&gt;A&lt;/code&gt;&lt;code&gt;[i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2&lt;/sub&gt;,…,i&lt;sub&gt;n&lt;/sub&gt;]&lt;/code&gt;, where &lt;code&gt;A&lt;/code&gt; is an array and &lt;code&gt;i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2&lt;/sub&gt;,…,i&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt; are integers.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i85)	arraysetapply (newRowsA3, [8], [&quot;George&quot;,20818.0,&quot;UK&quot;,&quot;Qtr 4&quot;]);
(%o85)	[&quot;George&quot;,20818.0,&quot;UK&quot;,&quot;Qtr 4&quot;]&lt;/syntaxhighlight&gt;
=== Undeclared Arrays ===

Maxima declared arrays and Maxima undeclared arrays will likely be the two types of data structures used by most users. Maxima undeclared arrays are also referred to as '''''hashed arrays'''''. For both of these two array types, memory allocation and structure occur &quot;behind the curtain&quot; of the Maxima user level, and &quot;the man behind the curtain&quot; is Lisp.

Of these two types, hashed arrays are the most flexible from the user point of view, all other factors being equal:

* The indices allowed for hashed arrays can be expressions,
* The dimensions of a hashed array are dynamic and not fixed, and
* Hashed arrays are relatively easier to create.
In fact, hashed arrays can be somewhat too easy to create. In the examples of the previous section involving declared arrays, identifiers were used as names for arrays. here is the list of allocated arrays:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i86)	arrays;
(%o86)	[A3,A2,A1,rowsA3,newRowsA3,B,D,my_list,h]&lt;/syntaxhighlight&gt;The array information for array &lt;code&gt;newRowsA3&lt;/code&gt; is shown below:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i87)	arrayinfo(newRowsA3);
(%o87)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15]]
&lt;/syntaxhighlight&gt;So the array &lt;code&gt;newRowsA3&lt;/code&gt; is not a declared array. it was created as part of a loop programming expression repeated below:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i53)	for i : 1 thru 15 do
	    (newRowsA3[i] : rowsA3[i],
	    print(&quot;Row &quot;,i,&quot;: &quot;,newRowsA3[i]))$;&lt;/syntaxhighlight&gt;When the first loop block was executed with i : 1, the assignment expression:

&lt;code&gt;newRowsA3[i] : rowsA3[i]&lt;/code&gt;

created a hashed array named  &lt;code&gt;newRowsA3&lt;/code&gt; and assigned &lt;code&gt;newRowsA3[1]&lt;/code&gt; the value of &lt;code&gt;rowsA3[1]&lt;/code&gt; automatically without any declaration. After that the hashed array dynamically allocated memory for values of the loop identifier i from 2 through 15 with each successive pass in the loop expression. Since hashed arrays are undeclared, and their associated dimensions are not fixed, but rather increase dynamically, expressions can be added to hashed arrays without creating a error message. These added values can be can be any valid Maxima expression, and the value of the indices used are not limited to zero and nonzero integers:  &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i88)	newRowsA3[16] :  [&quot;Maisel&quot;,12785.0,&quot;USA&quot;,&quot;Qtr 2&quot;];
(newRowsA3[16])	[&quot;Maisel&quot;,12785.0,&quot;USA&quot;,&quot;Qtr 2&quot;]

(%i89	arrayinfo(newRowsA3);
(%o89)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15],[16]]

(%i90)	newRowsA3[z]  : 2*sin(y) ^2 + 3*sin(x)^3;
(newRowsA3[z])	2*sin(y)^2+3*sin(B)^3

(%i91)	arrayinfo(newRowsA3);
(%o91)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15],[16],[z]]
&lt;/syntaxhighlight&gt;So one point to glean from this example is that all that is required to create a hashed array is an assignment expression to an indexed identifier, but it does require this assignment. If for some reason, a declared array is intended, but not declared using the &lt;code&gt;array&lt;/code&gt; operator (as in the instance of &lt;code&gt;newRowsA3&lt;/code&gt;), then a hashed array will be created at the first assignment of an expression to an indexed identifier.

This issue can also occur in cases where reference to a list value is intended, but the list has not been created. Lists are one-dimensional objects by definition. A reference using an identifier with a single index intended to be a list with no list existing named by that identifier, can inadvertently create a hashed array.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i91)	Alist[2] : 2*sin(y) ^2 + 3*sin(s)^3;
(Alist[2])	2*sin(y)^2+3*sin(s)^3

(%i92)	listp(Alist);
(%o92)	false

(%i93)	arrayinfo(Alist);
(%o93)	[hashed,1,[2]]
&lt;/syntaxhighlight&gt;The identifier &lt;code&gt;Alist&lt;/code&gt; is a name for a hashed array and not a list.

However, hashed arrays, like declared arrays can, be multi-dimensional: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i94)	a_hashed_array [j,k,l] : [12,s^(1/3), %i];
(%o94)	[12,s^(1/3),%i]

(%i95)	arrayinfo(a_hashed_array);
(%o95)	[hashed,3,[j,k,l]]
&lt;/syntaxhighlight&gt;The &lt;code&gt;array&lt;/code&gt; operator can be used to transform a hashed array into a declared array:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i96)	another_hashed_array[ 0, 2, 3] : 55;
(%o96)	55

(%i97)	array (another_hashed_array, 2, 4, 5);
(%o97)	another_hashed_array

(%i98)	arrayinfo(another_hashed_array);
(%o98)	[declared,3,[2,4,5]]
&lt;/syntaxhighlight&gt;From the user point of view, hashed arrays and declared arrays typically can be used for the same purpose. If dynamic dimensions or index expression flexibility are factors, then hashed arrays are likely to be a better choice. Many of the operators that can use declared arrays as arguments, may also be used with hashed arrays.

However, it should be noted at this point, that merely using a indexed identifier alone without an assignment, will not create a hashed array. Instead, Maxima interprets an expression so composed as an identifier for an undefined memoizing function, which is the topic of the next section.

==== Memoizing Functions ====
Assignment using an indexed identifier implicitly creates an undeclared (hashed) array. However, entering an expression that is an unassigned indexed identifier, from the point of view of Maxima, creates the identifier of a &quot;memoizing&quot; function. Memoizing functions are technically not an array topic, as these functions fall under the category of function definition. These functions have one foot in the function category and the other foot in the array category.

Memoizing functions are defined in a manner similar to other user-defined functions, for example:

&lt;code&gt;f(x, y, z) := x^2 + y^2 + z^2;&lt;/code&gt;

But instead of the arguments being enclosed in parentheses, they are enclosed using brackets:

&lt;code&gt;f[x, y, z] := x^2 + y^2 + z^2;&lt;/code&gt;

However, memoizing functions may be referred to as ''array functions,'' and it is the case that these functions from the point of view of aggregate data structures are hashed arrays. So these are mentioned and exemplified here for that reason:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* reference an indexed identifier h without assignment */
(%i99)	h[x];
(%o99)	h[x]

/* check identifier h as an array */
(%i100)	arrayinfo (h);
arrayinfo: h is not an array.
  -- an error. To debug this try: debugmode(true);
  
/* check identifier h as a function */
(%i101)	op(h[x]);
(%o101)	h

/* define h[x] as a function */
(%i102)	h[x] := 5*x^3 + sin(x);
(h[x])	h[x]:=5*x^3+sin(x)

/* check identifier h[x] as a function */
(%i103)	op(h[x]);
(%o103)	&quot;+&quot;

/* check identifier h as an array */
(%i104)	arrayinfo (h);
(%o104)	[hashed,1,[x]]

/* check the value of identifier h[x] */
(%i105)	h[x];
(%o105)	sin(x)+5*x^3

/* evaluate identifier h[x] with the argument 3*%pi */
(%i106)	h[3*%pi];
(%o106)	135*%pi^3

/* list the values of identifier h as an array */
(%i107)	listarray(h);
(%o107)	[135*%pi^3,sin(x)+5*x^3]

/* check identifier h as an array */
(%i108)	arrayinfo (h);
(%o108)	[hashed,1,[3*%pi],[x]]&lt;/syntaxhighlight&gt;A defined memoizing function stores its value the ''first time'' it is referenced with arguments, and returns the stored value, without evaluation, when the same arguments are used with that function subsequently. The stored value is &quot;frozen&quot; after the initial evaluation. Thus, it behaves like a hashed array. The arguments of a memoizing function also serve as indices of the associated hashed array.

=== Lisp Arrays ===
Lisp arrays are created using the &lt;code&gt;make_array (type, dim&lt;sub&gt;1&lt;/sub&gt;, dim&lt;sub&gt;2&lt;/sub&gt;, …, dim&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt; operator. Perhaps a better name for this operator would be &lt;code&gt;make_lisp_array ()&lt;/code&gt;, which admittedly is a longer name.

This operator creates and has a return value of a Lisp array. The array type may be &lt;code&gt;any&lt;/code&gt;, &lt;code&gt;flonum&lt;/code&gt;, &lt;code&gt;fixnum&lt;/code&gt;, or  &lt;code&gt;hashed&lt;/code&gt; . The &lt;code&gt;functional&lt;/code&gt; type referred to in the Maxima Manual appears to have been deprecated, and may result in an error message if used. There can be ''n'' indices, and where the associated indices can be a value from ''0'' to ''dim&lt;sub&gt;i&lt;/sub&gt; -1'', and ''i'' can have a value of one of 1 to n inclusive.

This operator can be used as an alternative to the &lt;code&gt;array ()&lt;/code&gt; operator. The advantage of using &lt;code&gt;make_array()&lt;/code&gt; is that the return value of &lt;code&gt;make_array()&lt;/code&gt; ''does not have a name''. Once the Maxima identifier that is assigned to the array return value is no longer assigned, the array memory allocation is released, and the allocated memory can be garbage collected. What it is being referred to that Lisp arrays created using &lt;code&gt;make_array()&lt;/code&gt; do not have names? &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* create a undeclared Maxima hashed array */
(%i109)	arrayA1 [1] : 55;  
(%o109)	55

/* check the information about this undeclared Maxima hashed array */
(%i110)	arrayinfo (arrayA1);
(%o110)	[hashed,1,[1]]

/* check the value of this undeclared Maxima hashed array */
(%i111)	arrayA1;
(%o111)	arrayA1     /* the name */

/* create a Lisp hashed array */
(%i112)	arrayA2 : make_array (hashed);
(arrayA2)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 1 {1202987DC3}&gt;&quot;

/* check the information about this Lisp hashed array */
(%i113)	arrayinfo (arrayA2);
(%o113)	[hash_table,1]

/* check the value of this Lisp hashed array */
(%i114)	arrayA2;
(%o114)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 1 {1202987DC3}&gt;&quot; /* no name */

(%i115)	listarray (arrayA2);
(%o115)	[]                     /* this hashed array is empty */
&lt;/syntaxhighlight&gt;So Lisp arrays do not have a name as a value. So, Maxima identifiers assigned to a Lisp array have no name for the array as a value. These identifiers have the reference to the array itself as a value, Lisp hashed arrays created using &lt;code&gt;make_array()&lt;/code&gt; with the hashed type specified, do not use dimensions. Lisp hashed arrays are often referred to as '''''hashed tables''''', and their indices are called '''''keys'''''.

An example of a Lisp array with the type &lt;code&gt;any&lt;/code&gt; follows:

&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* make a Lisp 3 by 4 array of type any */
(%i116)	arrayA3 : make_array (any, 3,4);
(arrayA3)	\#\{Lisp array \[3\\,4\]\}

(%i117)	arrayinfo (arrayA3);
(%o117)	[declared,2,[2,3]]

(%i118)	listarray(arrayA3);
(%o118)	[false,false,false,false,false,false,false,false,false,false,false,false]

(%i119)	arrayA3[1,1] : &quot;a string&quot; ;
(%o119)	&quot;a string&quot;

(%i120)	listarray(arrayA3);
(%o120)	[false,false,false,false,false,&quot;a string&quot;,
         false,false,false,false,false,false]
&lt;/syntaxhighlight&gt;Contrary to statements made in some sources, type checking is is not accomplished automatically, and will not cause Maxima to return an error message, as the Lisp array with the type &lt;code&gt;fixnum&lt;/code&gt; which follows is an exemplifies:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i121)	arrayA4 : make_array (fixnum, 3,4);
(arrayA4)	\#\{Lisp array \[3\\,4\]\}

(%i122)	arrayinfo (arrayA4);
(%o122)	[declared,2,[2,3]]

(%i123)	listarray (arrayA4);
(%o123)	[0,0,0,0,0,0,0,0,0,0,0,0]

(%i124)	arrayA4[0,2] : 3.14159;
(%o124)	3.14159

(%i125)	arrayA4[0,0] : &quot;a string&quot;;
(%o125)	&quot;a string&quot;

/* value types not checked and no error message */
(%i126)	listarray (arrayA4);
(%o126)	[&quot;a string&quot;,0,3.14159,0,0,0,0,0,0,0,0,0]&lt;/syntaxhighlight&gt;As was the case with declared arrays, there is no type checking and no error messages associated with assigned values of the array based on the declared type. The declared array type simply determines initial fill values, if any.

Hashed arrays and Lisp hash tables have an operator in common:

&lt;code&gt;has_key&lt;/code&gt; &lt;code&gt;(A, L)&lt;/code&gt;

This expression has a a value of &lt;code&gt;true&lt;/code&gt;, if the hashed array or Lisp hash table &lt;code&gt;A&lt;/code&gt; has the key (index) or keys (indices) of the list object &lt;code&gt;L&lt;/code&gt;.  Otherwise the expression has a value of &lt;code&gt;false&lt;/code&gt;.

The array &lt;code&gt;A&lt;/code&gt; must be a hashed (undeclared) array, a Lisp hash table value returned by the &lt;code&gt;make_array&lt;/code&gt; operator, or created as an undeclared array with &lt;code&gt;use_fast_arrays&lt;/code&gt; assigned the value &lt;code&gt;true&lt;/code&gt;.

If array A has only one key, that key must be the value of a list.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i127)	arrayinfo (newRowsA3);
(%o127)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],
                  [11],[12],[13],[14],[15],[16],[z]]

(%i128)	has_key (newRowsA3, [z]);
(%o128)	true

(%i129)	has_key (newRowsA3, [3]);
(%o129)	true

(%i130)	has_key(newRowsA3, [0]);
(%o130)	false

(%i131)	lisp_Array_1 [x];
(%o131)	3*x^2

(%i132)	arrayinfo (lisp_Array_1);
(%o132)	[hash_table,1,x]

(%i133)	has_key (lisp_Array_1, [x]);
(%o133)	true

(%i134)	has_key (lisp_Array_1, [y]);
(%o134)	false
&lt;/syntaxhighlight&gt;

=== Arrays and Features ===
Maxima arrays can be assigned features in a manner similar to other identifiers:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i135)	array (a6,fixnum, 5);
(%o135)	a6

(%i136)	arrayinfo (a6);
(%o136)	[complete,1,[5]]

(%i137)	declare (a6, [real, noninteger]);
(%o137)	done

(%i138)	featurep (a6, real);
(%o138)	true

(%i139)	featurep (a6, noninteger);
(%o139)	true

(%i140)	a6[2] : 2;
(a6[2])	2

(%i141)	listarray (a6);
(%o141)	[0,0,2,0,0,0]
&lt;/syntaxhighlight&gt;However, once again, declaring an array to have one or more features does not result in type checking of values assigned to an array. Perhaps the best way to ensure types of values assigned to arrays is type-checking of expressions using predicate operators prior to assignment to arrays. 

=== Array Memory Storage Considerations ===

The following from the Maxima Manual&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.5.1 - Functions and Variables for Arrays |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Functions-and-Variables-for-Arrays}}&lt;/ref&gt; is quoted here for the purpose of establishing the context of that which follows:&lt;blockquote&gt;''&quot;Option variable: use_fast_arrays ¶''

''Default value: false''

''When use_fast_arrays is true, arrays declared by array are values instead of properties, and undeclared arrays (hashed arrays) are implemented as Lisp hashed arrays.''

''When use_fast_arrays is false, arrays declared by array are properties, and undeclared arrays are implemented with Maxima’s own hashed array implementation.''

''Note that the code use_fast_arrays switches to is not necessarily faster than the default one; Arrays created by make_array are not affected by use_fast_arrays.&quot;''&lt;/blockquote&gt;
This Maxima Manual entry requires some elaboration in order to have a sufficient understanding of the effect of the &lt;code&gt;'''use_fast_arrays'''&lt;/code&gt; &quot;flag&quot; – referred to as an &quot;Option Variable&quot; in the above quotation.

The first point to note is that the default value of this flag is &lt;code&gt;false&lt;/code&gt;. So, if users take no action to assign this flag to the value &lt;code&gt;true&lt;/code&gt;, then declared arrays created using the &lt;code&gt;array()&lt;/code&gt; operator  are treated as ''properties'' bound to a symbol, and behave in the manner previously described. Likewise undeclared arrays are a Maxima array implementation, and behave as legacy property hash tables, and these also behave as previously described.

If action is taken to enter an expression that assigns the value &lt;code&gt;true&lt;/code&gt; to this flag, then Maxima treat arrays as standard Lisp ''values'' rather than object properties:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i142)	use_fast_arrays;
(%o142)	false

(%i143)	array (A1,fixnum, 10);
(%o143)	A1

(%i144)	arrayinfo (A1);
(%o144)	[complete,1,[10]]

(%i145)	H1[1] : 1729;
(H1[1])	1729

(%i146)	arrayinfo (H1);
(%o146)	[hashed,1,[1]]

(%i147)	use_fast_arrays : true;
(use_fast_arrays)	true

(%i148)	array (A2, fixnum, 10);
(%o148)	\#\{Lisp array \[11\]\}

(%i149)	A2;
(%o149)	\#\{Lisp array \[11\]\}

(%i150)	H2[1] : 1729;
(H2[1])	1729

(%i151)	H2;
(%o151)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 2 {1203AD15A3}&gt;&quot;

(%i152)	arrayinfo (H2);
(%o152)	[hash_table,1,1]
&lt;/syntaxhighlight&gt; The &lt;code&gt;use_fast_arrays&lt;/code&gt; flag has no effect on arrays created using the &lt;code&gt;make_array ()&lt;/code&gt; operator.

Note the following:

* Assigning &lt;code&gt;use_fast_arrays&lt;/code&gt; &lt;code&gt;: true&lt;/code&gt; does not speed up execution for all operations. It primarily optimizes memory footprint by minimizing cell allocations.  The main benefit is optimization of memory footprints and structural representation inside Lisp.
* If compiling Maxima expressions to native Lisp using the &lt;code&gt;translate&lt;/code&gt; &lt;code&gt;()&lt;/code&gt; operator, pair this flag with &lt;code&gt;translate_fast_arrays&lt;/code&gt; &lt;code&gt;: true&lt;/code&gt;. This flag instructs the translator to compile arrays as value-based.

=== Structures ===
Structures, although not an array data type is an aggregation data type.  By &quot;aggregation&quot; it is meant a data type that references other data types by reference to a name and some method of accessing individual values of instances of that aggregation by means of indices used to reference values individually.

Thus, as has been previously described for example lists, hashed arrays, Lisp arrays, and declared arrays are all aggregation data types with syntactical means to refer to individual values of a named aggregation instance by way of indices, which are sometimes also referred to as subscripts or keys.

As examples:

* An existing '''list''' named &lt;code&gt;L1&lt;/code&gt; has values that can be accessed as &lt;code&gt;L1[1]&lt;/code&gt;, &lt;code&gt;L[2]&lt;/code&gt;, &lt;code&gt;L[3]&lt;/code&gt;, and so forth
* An existing '''hashed array''' with two indices (&quot;2D&quot;) named &lt;code&gt;ha&lt;/code&gt; has values that can accessed as &lt;code&gt;ha[1,1&lt;/code&gt;], &lt;code&gt;ha[1,2]&lt;/code&gt;,..., &lt;code&gt;ha[2,1]&lt;/code&gt;, &lt;code&gt;ha[2,2]&lt;/code&gt;, and  so forth.
* An existing '''declared array''' with three indices (&quot;3D&quot;) named &lt;code&gt;da&lt;/code&gt; has values that can be accessed as &lt;code&gt;da[1,1,1]&lt;/code&gt;, &lt;code&gt;da[1,1,2]&lt;/code&gt;,...,&lt;code&gt;da [2,1,1]&lt;/code&gt;, ..., &lt;code&gt;da[3,1,1]&lt;/code&gt;, and so forth.

What makes the Maxima structure data type different from these array data types is the form of definition used and the means of accessing values of an instance of this type of aggregation. The Maxima structure data type seems to be the closest type of data that resembles an object in some other general-purpose programming languages.

The structure type of data allows the creation of named entities with attributes, and named instances of those entities and the assignment of values to those attributes. Thus the Maxima structure data type is used to define custom, named composite data types that group related fields together under a single identifier. Structures enhance code organization and readability, especially when modeling real-world entities in symbolic computations. They are useful for managing complex data in programs involving algebraic manipulations, simulations, or data modeling.  

Structures are created using the &lt;code&gt;defstruct&lt;/code&gt; operator, which defines a template with named attributes. Once defined, instances of the structure are created using the &lt;code&gt;new&lt;/code&gt; operator, and attributes are accessed via the &lt;code&gt;@&lt;/code&gt; operator. 

So in the interest of taking advantage of this information, consider a well-defined set of people. The people of this set may have many diverse attributes that might be of interest - name, age ,and city of residence as examples. A class of people of the set of interest with these attributes can be defined as follows: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i153)	defstruct (person (name, age, city));
(%o153)	[person(name,age,city)]

(%i54) structures;
(%o154)                      [person(name, age, city)]

(%i155)	p : new (person (&quot;Alice&quot;, 30, &quot;New York&quot;));
(p)	person(name=&quot;Alice&quot;,age=30,city=&quot;New York&quot;)

(%i156)	p@name;
(%o156)	&quot;Alice&quot;

(%i157)	p@city;
(%o157)	&quot;New York&quot;

(%i158)	kill(p@city);
(%o158)	done

/* If the attribute a in x has not been assigned a value, or the value
   has been &quot;killed,&quot; then x@a evaluates to itself */

(%i159)	p@city;
(%o159)	p@city

(%i160)	p;
(%o160)	person(name=&quot;Alice&quot;,age=30,city)

(%i161)	p@city : &quot;Rochester&quot;;
(%o161)	&quot;Rochester&quot;

(%i162)	p;
(%o162)	person(name=&quot;Alice&quot;,age=30,city=&quot;Rochester&quot;)

(%i163) defstruct (sales(LastName, Sales , Country , Quarter) );
(%o163)             [sales(LastName, Sales, Country, Quarter)]

(%i164) structures;
(%o164) [person(name, age, city), sales(LastName, Sales, Country, Quarter)]

(%i165) s : new (sales (&quot;Smith&quot;,16753.00,&quot;UK&quot;,&quot;Qtr 3&quot;));
(%o165) sales(LastName=Smith, Sales=16753.0, Country=UK, Quarter=Qtr 3)

(%i166) s@Sales;
(%o166)                              16753.0

(%i167) s@Sales : 17375.0;
(%o167)                              17375.0

(%i168) s;
(%o168) sales(LastName=Smith, Sales=17375.0, Country=UK, Quarter=Qtr 3)&lt;/syntaxhighlight&gt;{{Bookcat}}</text>
      <sha1>plwzzicy0cex5uj57qssmeqzbudm74e</sha1>
    </revision>
    <revision>
      <id>4668964</id>
      <parentid>4668963</parentid>
      <timestamp>2026-09-05T17:31:50Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <minor />
      <comment>/* Introduction */</comment>
      <origin>4668964</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="64548" sha1="4q7c2qaqaebf08cisqd7o7z9wlhxkxx" xml:space="preserve">== Maxima Aggregate Data Structures ==

=== Introduction ===
This section is intended to present some of the essentials of what are called Maxima aggregate data structures. By this it is meant the data types that can be used to refer to the values of expressions using a means of indexing of a single identifier (name) that refers to an aggregate (collection) of expressions as values.

Built-in aggregate data types include: 

* lists
* hashed arrays
* declared arrays
* structures

Each of these has a means of indexing an identifier that names an instance of these data types. 

Please note that it is the case that this means of indexing an identifier for an aggregate data type may be referred to as involving &quot;subscripts&quot; or &quot;sub-scripted variables&quot; or &quot;keys&quot; as used by various computer programming languages, as well as in the context of Maxima documentation and commentary. In this book terms such as &quot;index&quot; or &quot;indices&quot; or &quot;indexed identifiers&quot;  are used instead.

Also all built-in Maxima functions (including packages) for these data types are referred to as ''&quot;operators&quot;'' and not ''&quot;functions&quot;'' as this latter term in general serves better to refer to Maxima function expressions defined by the user -- as in &lt;code&gt;f(x) :=&lt;/code&gt;, &lt;code&gt;g[s] :=&lt;/code&gt; and &lt;code&gt;define ()&lt;/code&gt; as examples.

This section is not intended to be exhaustive. It is intended to provide familiarity with aggregate data types. What is included has been gleaned from various sources, and only a few attributions are provided. Therefore, there is no claim of originality implied. 

=== Lists ===

==== Introduction to Lists ====
Lists are one of the basic buildings block for Maxima and Lisp. Maxima expressions are in general represented as Lisp lists. 

For example, consider the Maxima expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	e+3;
(%o1)	e+3
&lt;/syntaxhighlight&gt;This expression has the form of a Lisp list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i2)	:lisp #$[e+3]$
((MLIST SIMP) ((MPLUS SIMP) 3 $E))
&lt;/syntaxhighlight&gt;An expression in the form of a Lisp list can also be be displayed as a Maxima expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i2)	:lisp (displa '((MLIST SIMP) ((MPLUS SIMP) 3 $E)));
[e+3]
NIL
&lt;/syntaxhighlight&gt;Note that the value of this expression using &lt;code&gt;displa '()&lt;/code&gt; is &lt;code&gt;NIL&lt;/code&gt;, and &lt;code&gt;[e+3]&lt;/code&gt; is simply displayed in Maxima list object form. It is not necessary for the typical uses of Maxima to utilize this insight into the role Lisp lists have as one of the building blocks for Maxima, but it may be useful to have a familiarity with that role. Lists are often used as arguments to many operators, and the values of expressions are often in the form of lists.

==== Some Operators for Lists ====
Lists are created explicitly and list elements referenced using &lt;code&gt;[&lt;/code&gt; and &lt;code&gt;]&lt;/code&gt; to mark the beginning and end, respectively, of an instance of a list object, or to reference the expressions of an existing list object.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i3)	[2,3,4];
(%o3)	[2,3,4]
&lt;/syntaxhighlight&gt;The expression &lt;code&gt;[2,3,4]&lt;/code&gt; creates a Maxima list object. In this case the object itself is not accessible as it was not assigned an identifier unless referenced by the &lt;code&gt;%&lt;/code&gt; , &lt;code&gt;%i&lt;/code&gt; or &lt;code&gt;%o&lt;/code&gt; label.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i4)	%;
(%o4)	[2,3,4]

(%i5)	%o4[2]; /* second expression of list object referenced by index */ 
(%o5)	3
&lt;/syntaxhighlight&gt;That [2,3,4] is a list object can be tested using the &lt;code&gt;listp()&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i6)	listp ([2,3,4]);
(%o6)	true
&lt;/syntaxhighlight&gt;A list object can be assigned an identifier:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i7)	s:[%pi,%e,%phi];
(s)	[%pi,%e,%phi]

(%i8)	listp (s);
(%o8)	true&lt;/syntaxhighlight&gt;

The value of an element of a list can be accessed using the list identifier and brackets with a index value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i9)	s[1];
(%o9)	%pi

(%i10)	s[2];
(%o10)	%e

(%i11)	s[3];
(%o11)	%phi
&lt;/syntaxhighlight&gt;
Invalid index values returns an error:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i12)	s[4];
inpart: invalid index 4 of list or matrix.
-- an error. To debug this try: debugmode(true);
&lt;/syntaxhighlight&gt;
Consider the following relatively long list of integer atoms created explicitly and identified as &lt;code&gt;List_1&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i13)	List_1:[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582,145,2,
	    118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,
	    30,3,484,51,3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,4,
	    484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,5,118,30,5,484,
	    
	    49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177];

(List_1)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,2,1582,203
,3,118,30,3,484,51,3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,
214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177]&lt;/syntaxhighlight&gt;
The number of values of this list can be returned using the &lt;code&gt;length()&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i14)	length (List_1);
(%o14)	105
&lt;/syntaxhighlight&gt;
Create another list identified as &lt;code&gt;List_2&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i15)	List_2 : [6,1455,200,6,1607,205];
(List_2)	[6,1455,200,6,1607,205]

(%i16)	length (List_2);
(%o16)	6
&lt;/syntaxhighlight&gt;
Create a third list identified as &lt;code&gt;List_3&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i17)	List_3 : append (List_1, List_2)$

(%i18)	length (List_3);
(%o19)	111
&lt;/syntaxhighlight&gt;
Note that the &lt;code&gt;'''append ()'''&lt;/code&gt; operator does not affect either of the list arguments &lt;code&gt;List_1&lt;/code&gt; or &lt;code&gt;List&lt;/code&gt;_2. It merely appends &lt;code&gt;List_2&lt;/code&gt; to &lt;code&gt;List_1&lt;/code&gt; and returns a new list, in this case assigned the identifier &lt;code&gt;List_3&lt;/code&gt;.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i20)	length (List_1);
(%o20)  105

(%i21)	length (List_2);
(%o21)  6

(%i22)	length (List_3);
(%o22)	111

(%i23)	List_3;
(%o23)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
         142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
         1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
         75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
         1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
         142,5,1372,174,5,1582,177,6,1455,200,6,1607,205]&lt;/syntaxhighlight&gt;
Values (the last one in this example) can be deleted from a list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i24)	last (List_3);
(%o24)	205

(%i25)	delete (last (List_3), List_3);
(%o25)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
         142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
         1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
         75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
         1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
         142,5,1372,174,5,1582,177,6,1455,200,6,1607]&lt;/syntaxhighlight&gt;
The &lt;code&gt;delete (List_3)&lt;/code&gt; expression creates a new list object using &lt;code&gt;List_3&lt;/code&gt;. &lt;code&gt;List_3&lt;/code&gt; itself is not affected by the &lt;code&gt;'''delete ()'''&lt;/code&gt; operator. Only the resulting list is affected. This is often the case with list operators. An identifier could be used to save the above resulting list if necessary:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* List_3 is the same length */
(%i26)	length(List_3); 
(%o26)	111

/* The last value of List_3 is the same */
(%i27)	List_3[111];
(%o27)	205

(%i28)	last(List_3);
(%o28)	205&lt;/syntaxhighlight&gt;There was only one instance of &lt;code&gt;205&lt;/code&gt; in &lt;code&gt;List_3&lt;/code&gt;, so only that value was deleted from the list of &lt;code&gt;%o25&lt;/code&gt;.  If there are more than one value then the &lt;code&gt;delete ()&lt;/code&gt; operator will remove all of those values from the returned list expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i29)	NewList_3 : delete(118, List_3)$ 

/* all five instances of 118 removed from List_3 as NewList_3 */
(%i30)	length(NewList_3);
(%o30)	106
&lt;/syntaxhighlight&gt;There are operators to refer to instances of list expressions by ordinal number:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i30)	FirstThreeList_3:[first(List_3), second(List_3), third(List_3)];
(FirstThreeList_3)	[1,118,30]
&lt;/syntaxhighlight&gt;Expressions of list objects can e referenced to create a new list object from the first n expressions of a list, the last n expressions of a list, or the rest remaining after n expressions from the beginning or -n expressions from the end of a list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* first three expressions of List_3 */
(%i31)	firstn(List_3,3); 
(%o31)	[1,118,30]

/* same three expressions of List_3 using the rest operator with -108 */
(%i32)	rest(List_3, -108); 
(%o32)	[1,118,30]

/* last three expressions of List_3 */
(%i33)	lastn(List_3,3); 
(%o33)	[6,1607,205]

/* same three expressions of List_3 using the rest operator with 108 */
(%i34)	rest(List_3, 108);
(%o34)	[6,1607,205]&lt;/syntaxhighlight&gt;Some further examples of the &lt;code&gt;'''firstn ()'''&lt;/code&gt;, &lt;code&gt;'''lastn ()'''&lt;/code&gt; and &lt;code&gt;'''rest ()'''&lt;/code&gt; list operators:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* first 63 expressions of List_3 */
(%i35)	firstn (List_3, 63);
(%o35)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,
         1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,
         1372,203,2,1582,203,3,118,30,3,484,51,3,664,75,3,1004,108,3,
         1231,115,3,1372,139,3,1582,140]

/* last 63 expressions of List_3 */
(%i36)	lastn (List_3, 63);
(%o36)	[3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,
         5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,
         1582,177,6,1455,200,6,1607,205]

/* first expressions of List_3 after removing the last 63*/
(%i37)	rest (List_3, -63);
(%o37)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,
         1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,
         1372,203,2,1582,203,3,118,30,3,484,51]
&lt;/syntaxhighlight&gt;Maxima programming expressions can be used with list operators to reference list expressions in various ways. For example, the expression which follows accesses the expressions of a list as lists of three each:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i38)	(L4 : List_4,
	      for i:(-length (List_4)) + 3 thru 0 step 3 do
	             (disp (rest (L4, i)), 
	              L4 : rest (L4, 3)),
	     &quot;&quot;)$

[1,118,30]
[1,484,58]
[1,664,87]
[1,1004,115]
[1,1231,120]
[1,1372,142]
[1,1582,145]
[2,118,33]
[2,484,69]
[2,664,111]
[2,1004,156]
[2,1231,172]
[2,1372,203]
[2,1582,203]
[3,118,30]
[3,484,51]
[3,664,75]
&lt;/syntaxhighlight&gt;List operators can be used as arguments other list operators:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* create a new empty list */
(%i39)	newList4 : [];
(newList4)	[]

/* append the first six &amp; last six expressions of List_4 to the new list */
(%i40)	newList4 : append (newList4, firstn (List_4, 6), lastn (List_4, 6))$

/* the new list now has the 12 appended expressions from List_4 */
(%i41)	newList4;
(%o41)	[1,118,30,1,484,58,3,484,51,3,664,75]
&lt;/syntaxhighlight&gt;

Maxima programming expressions can be used to step through the expressions of lists using list operators to reference &quot;slices&quot; of different lengths:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i42)	L4 : List_4;
(L4)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582
         145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,
         2,1582,203,3,118,30,3,484,51,3,664,75]

(%i43)	length (L4);
(%o43)	51

(%i44)	(L4 : List_4,
         for i : 21 thru 3 step -3 do
	         print (L4 : lastn (L4, i),&quot; &quot;, length (L4)),
	    &quot;&quot;)$

[2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 21

[2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 18

[2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 15

[2,1582,203,3,118,30,3,484,51,3,664,75] 12

[3,118,30,3,484,51,3,664,75] 9

[3,484,51,3,664,75] 6

[3,664,75] 3&lt;/syntaxhighlight&gt;

==== Using the &lt;code&gt;copylist&lt;/code&gt; Operator ====
When an existing list object is assigned to an identifier, a reference to the memory location of the list object is used. This reference to the memory location is transparent from the point of view of the user. However,if this is not  accounted for unintended side effects may occur when assigning another identifier to an existing one that references a list object.

For example, in the expression &lt;code&gt;L4 : List_4&lt;/code&gt; it might be assumed that this results in the list object referenced by &lt;code&gt;List_4&lt;/code&gt; to simply be copied to a new memory location and reference for &lt;code&gt;L4&lt;/code&gt;. This is not the case. Both &lt;code&gt;L4&lt;/code&gt; and &lt;code&gt;List_4&lt;/code&gt; refer to the same list object in memory. Consequently changes to the same list object can be effected by referencing the object using either alias.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i45)	newList4;
(%o45)	[1,118,30,1,484,58,3,484,51,3,664,75]

/* The identifier newList4 refers to a location in memory.
   The colon (:) assignment operator simply creates an alias
   using that same memory reference*/

(%i46)	newList5 :  newList4;
(newList5)	[1,118,30,1,484,58,3,484,51,3,664,75]

/* Two different identifiers for the same memory location and
   therefore the same object. Changes to expressions of the list
   object using either identifier changes the same object in memory */
   
(%i47)	newList5[1] : 99;
(newList5[1])	99

(%i48)	newList4[1];
(%o48)	99

(%i49)	newList4;
(%o49)	[99,118,30,1,484,58,3,484,51,3,664,75]

(%i50)	newList5;
(%o50)	[99,118,30,1,484,58,3,484,51,3,664,75]
&lt;/syntaxhighlight&gt;
This &quot;side effect&quot; is often unwanted. The way to avoid this is by using the &lt;code&gt;copylist ()&lt;/code&gt; operator instead of the assignment operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i51)	newList4 : [1,118,30,1,484,58,3,484,51,3,664,75] ;
(newList4)	[1,118,30,1,484,58,3,484,51,3,664,75]

(%i52)	newList5 : copylist (newList4);
(newList5)	[1,118,30,1,484,58,3,484,51,3,664,75]
 
 /* Same list object expressions, but a different memory reference */

(%i53)	newList5[1] : 99;
(newList5[1])	99

(%i54)	newList4[1];
(%o54)	1
&lt;/syntaxhighlight&gt;
Changes to the values of either list will not affect the other list.
{| class=&quot;wikitable&quot;
|+List Object Operators
|[
|fourth
|rreduce
|-
|]
|fullsetify
|second
|-
|append
|join
|setify
|-
|assoc
|last
|seventh
|-
|cons
|length
|sixth
|-
|copylist
|listarith
|some
|-
|create_list
|listp
|sort
|-
|delete
|lmax
|sublist
|-
|eighth
|lmin
|sublist_indices
|-
|endcons
|lreduce
|tenth
|-
|fifth
|makelist
|third
|-
|first
|member
|tree_reduce
|-
|flatten
|reverse
|xreduce
|}

Refer to the Maximal Manual&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.4.2 Functions and Variables for Lists |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Lists}}&lt;/ref&gt; for more complete description of operators and variables for Maxima lists.

==== Performance Considerations for Lists ====
&lt;blockquote&gt;''&quot;Lists provide efficient ways of appending and removing elements. They can be created without knowing their final dimensions. Lisp provides efficient means of copying and handling lists. Also nested lists do not need to be strictly rectangular. These advantages over declared arrays come with the drawback that the amount of time needed for accessing a random element within a list may be roughly proportional to the element’s distance from its beginning.&quot;''&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.4.3 Performance considerations for Lists |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Lists}}&lt;/ref&gt;&lt;/blockquote&gt;Maxima list objects have many operators for creating, accessing, and changing the expressions of lists. Evaluation times of expressions that involve lists can vary significantly depending on the length of the list objects involved, as well as the nature of any operators used to compose the expressions. This fact might have an influence on the choice of using arrays rather than lists in some cases if evaluation time is a factor to consider. The example expressions that follow involve a list object (identified as &lt;code&gt;s&lt;/code&gt; ) of complex number expressions that has a length of 10,000 and two different user-defined functions:&lt;pre&gt;(%i55) P1(s) := rectform (product(s[i], i, 1, length (s)))$

(%i56) P2(s) := xreduce (lambda ([a, b], rectform (a * b)), s)$

(%i57) s : makelist (random (1.0) + %i*random (1.0), 10^4)$

(%i58)	showtime : true$
Evaluation took 0.0000 seconds (0.0000 elapsed) using 0 bytes.

(%i59) P1(s);
Evaluation took 32.3080 seconds (32.3860 elapsed) using 17944.301 MB.
(%o59) 0.0

(%i60) P2(s);
Evaluation took 0.0620 seconds (0.0620 elapsed) using 8.343 MB.
(%o60) 0.0

(%i61)	showtime : false$
Evaluation took 0.0000 seconds (0.0000 elapsed) using 0 bytes.&lt;/pre&gt;
==Arrays ==
&lt;blockquote&gt;&quot;Maxima's current array/matrix semantics are a mess, I must say, with at least four different kinds of object (hash arrays, explicit lists, explicit matrices, Lisp arrays) supporting subscripting with varying semantics.&quot; &lt;ref&gt;[http://comments.gmane.org/gmane.comp.mathematics.maxima.general/21829 Maxima: Syntax improvements by Stavros Macrakis ]&lt;/ref&gt;
– Stavros Macrakis

&quot;Maxima's concept of arrays, lists, and matrices is pretty confused, since various ideas have accreted in the many years of the project... Yes, this is a mess. Sorry about that. These are all interesting ideas, but there is no unifying framework.&quot;&lt;ref&gt;[http://stackoverflow.com/a/29926692 Maxima: what does Maxima call an “array”? - answer by Robert Dodier]&lt;/ref&gt;

– Robert Dodier&lt;/blockquote&gt;

The various terminology used in the context of arrays undoubtedly can be confusing. For the sake of simplicity and clarity the following categories of array objects are referred to in this book:


Maxima has three array categories :&lt;ref&gt;[http://permalink.gmane.org/gmane.comp.mathematics.maxima.general/13588 the Maxima mailing list &lt;nowiki&gt;: [Maxima] array and matrix? - answer by Robert Dodier&lt;/nowiki&gt;]&lt;/ref&gt;
* Declared arrays 
* Undeclared (hashed) arrays 
* Lisp arrays 

'''''Declared arrays''''' are explicitly created using the &lt;code&gt;array()&lt;/code&gt; operator, and unlike lists, which have only one index and are one-dimensional, declared  arrays can be multi-dimensional  – having one to five indices. The indices for declared array dimensions need not be equal.

Indices for each dimension may be between 0 and the respective declared dimension. Each declared array may be for expressions of a specified type, which can be ''fixnum'' for integers or ''flonum'' for floating-point numbers.

'''''Undeclared (hashed) arrays''''' are created implicitly by assigning an expression to an indexed identifier that does not name an existing list object. An undeclared array (hashed array) can grow dynamically as there is no fixed dimension limit for each index as there is with declared arrays Another difference is that numbers, identifiers, expressions and strings may be used for indices.

Also, there is no fixed limit on the number of dimensions. The only real limitation is practical – the available computer memory and the underlying Lisp environment of the Maxima session. Hashed arrays with only one dimension may be confused with a list object.

It is essential to keep in mind that list objects must always be created before values are assigned or referenced. Assigning an expression to a one-dimensional indexed identifier, that does not reference an existing list, implicitly creates a hashed array.

'''''Lisp arrays''''' are created using the &lt;code&gt;'''make_array ()'''&lt;/code&gt; operator. The array type may be specified as ''any'', ''flonum'', ''fixnum'', or ''hashed''. Lisp array objects may be created as one-dimensional or multi-dimensional as specified by the number of dimension size values used with the &lt;code&gt;'''make_array ()'''&lt;/code&gt; operator. For each  dimension value specified, the associated index value can be a number between 0 to 1 less than the respective dimension value. The same or different values may be used for each specified dimension. the ''hashed'' type does not require any dimensions. Lisp arrays may be used in cases where memory usage and garbage collection are factors.

Examples of use and elaboration upon the technical details for each of these categories of array object types follows.
{| class=&quot;wikitable&quot;
|+Array Operators and Flags
|array
|arraysetapply
|rearray
|-
|arrayapply
|has_key
|remarray
|-
|arrayinfo
|fillarray
|subvar
|-
|arraymake
|listarray
|subvarp
|-
|arrays
|make_array
|use_fast_arrays
|-
|
|
|translate_fast_arrays
|}
=== Declared Arrays ===
Declared arrays must be created before being referenced and are of fixed dimensions.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	array(A1, fixnum, 34,2); 
(%o1)	A1

(%i2)	array(A2, flonum, 35,2);
(%o2)	A2

(%i3)	array(A3, 14,3);
(%o3)	A3

(%i4)	arrayinfo (A1);
(%o4)	[complete,2,[34,2]]

(%i5)	arrayinfo (A2);
(%o5)	[complete,2,[35,2]]

(%i6)	arrayinfo (A3);
(%o6)	[declared,2,[14,3]]
&lt;/syntaxhighlight&gt;
The first expression &lt;code&gt;%i1&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A1&lt;/code&gt;. This array is two-dimensional – the first index may have values from 0 to 34 and the second index may have values from 0 to 2. This array therefore is 35 by 3 in extent. The array type is declared to be &lt;code&gt;fixnum&lt;/code&gt;. As it is, &lt;code&gt;A1&lt;/code&gt; is an not empty array – it has values to reference as will be exemplified below.

Similarly the second expression &lt;code&gt;%i2&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A2&lt;/code&gt;. This array is also two-dimensional – the first index may have values from 0 to 35 and the second index may have values from 0 to 2. This array therefore is 36 by 3 in extent. The array type is declared to be &lt;code&gt;flonum&lt;/code&gt;. As it is, &lt;code&gt;A2&lt;/code&gt; is not an empty array – it also has values to reference as will be exemplified below.

The third expression &lt;code&gt;%i3&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A3&lt;/code&gt;. This array is also two-dimensional – the first index may have values from 0 to 13 and the second index may have values from 0 to 3. This array therefore is 15 by 4 in extent. The array type is not declared. As it is, &lt;code&gt;A3&lt;/code&gt; is an empty array – it has no values to reference as will be exemplified below.

The &lt;code&gt;'''arrayinfo ()'''&lt;/code&gt; operator can be used to return a list object that has values reflecting information about an array. Note that arrays declared without a type will have &lt;code&gt;declared&lt;/code&gt; as a value of the list. Arrays declared with &lt;code&gt;fixnum&lt;/code&gt; or &lt;code&gt;flonum&lt;/code&gt; as the type will have &lt;code&gt;complete&lt;/code&gt; as a value of the list. This technical detail is not well-documented. The returned information list also shows a value for the dimension of the array ( 2 in these examples ) and an inner list with values for the maximum index for each dimension.

A look inside each of these declared arrays provides a clue as to why &lt;code&gt;complete&lt;/code&gt; is returned instead of &lt;code&gt;declared&lt;/code&gt; when the type is specified as &lt;code&gt;fixnum&lt;/code&gt; or &lt;code&gt;flonum&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* This array reference has a value of 0 */
(%i7)	A1[0,0];
(%o7)	0

/* This array reference has a value of 0.0 */
(%i8)	A2[0,0];
(%o8)	0.0

/* This array reference has a value of itself */
(%i9)	A3[0,0];
(%o9)	A3[0,0]&lt;/syntaxhighlight&gt;

In fact, ''all'' values of the array &lt;code&gt;A1&lt;/code&gt; have been assigned 0, and ''all'' values of the array &lt;code&gt;A2&lt;/code&gt; have beenassigned 0.0. However, ''all'' values of the array &lt;code&gt;A3&lt;/code&gt; have been not been assigned any value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i10)	listarray(A1);
(%o10)	[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0]

(%i11)	listarray(A2);
(%o11)	[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]

(%i12)	listarray(A3);
(%o12)	[#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####]&lt;/syntaxhighlight&gt;

Thus, arrays &lt;code&gt;A1&lt;/code&gt; and &lt;code&gt;A2&lt;/code&gt; are &lt;code&gt;complete&lt;/code&gt; in this sense, and array &lt;code&gt;A3&lt;/code&gt; is simply &lt;code&gt;declared&lt;/code&gt;.

It might seem reasonable, that Maxima would complain if a value was assigned to an array that is at odds with the declared type. Such is not the case however. Once an array is declared with a type, Maxima does not enforce any type checking of values assigned to the array. The effect of the type (if any) in the declaration is simply to fill the array with values of #####, 0 or 0.0. Subsequently, those values can be replaced by the assignment of different values that will not be checked for the type of value. One way to enforce type checking is by using predicate operators to check values at the point in time of assignment to arrays. For example, using one or more of:

* numberp (expr)
* floatnump (expr)
* integerp (expr) 
* ratnump (expr)
* stringp (obj)
* listp (expr) 
* featurep (a, f)

and possibly others.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* A1 was declared as type fixnum */
(%i13)	A1[5,2]:3.14159;
(%o13)	3.14159

/* A2 was declared as type flonum */
(%i14)	A2[3,0]:7129;
(%o14)	7129

/* A1 which was declared as type fixnum assigned a string */
(%i15)	A1[4,1]:&quot;a string&quot;;
(%o15)	&quot;a string&quot;

/* A2 which was declared as type flonum assigned a math expression*/
(%i16)	A2[6,1]:3*x^2 + 4*x +10; 
(%o16)	3*x^2+4*x+10
&lt;/syntaxhighlight&gt;

There are other ways to assign values to an array. One way is to read the values from a comma separated (CSV) file  using the &lt;code&gt;'''read_array ()'''&lt;/code&gt; operator from the ''numericalio'' package.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i17) load(numericalio);
(%o17) &quot;/app/plugins/maxima/share/maxima/5.50.0/share/numericalio/numericalio.mac&quot;


&lt;/syntaxhighlight&gt;

Below are of the values of the CSV data file &lt;code&gt;tree_data_nh.csv&lt;/code&gt; :&lt;syntaxhighlight lang=&quot;text&quot;&gt;
1,118,30
1,484,58
1,664,87
1,1004,115
1,1231,120
1,1372,142
1,1582,145
2,118,33
2,484,69
2,664,111
2,1004,156
2,1231,172
2,1372,203
2,1582,203
3,118,30
3,484,51
3,664,75
3,1004,108
3,1231,115
3,1372,139
3,1582,140
4,118,32
4,484,62
4,664,112
4,1004,167
4,1231,179
4,1372,209
4,1582,214
5,118,30
5,484,49
5,664,81
5,1004,125
5,1231,142
5,1372,174
5,1582,177
&lt;/syntaxhighlight&gt;

Note that the following expression assumes that the CSV file is located in the Maxima working directory.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i18)	read_array(&quot;tree_data_nh.csv&quot;, A1, &quot;,&quot;); 
(%o18)	done

(%i19)	 listarray(A1);
(%o19)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,
         1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,
         2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75,3,1004,108,
         3,1231,115,3,1372,139,3,1582,140,4,118,32,4,484,62,4,664,112,
         4,1004,167,4,1231,179,4,1372,209,4,1582,214,5,118,30,5,484,49,
         5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177]
&lt;/syntaxhighlight&gt;
Below are of the values of the CSV data file &lt;code&gt;tree_data.csv&lt;/code&gt;  which has a header row, but is otherwise the same as &lt;code&gt;tree_data_nh.csv&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;text&quot;&gt;
&quot;Tree&quot;,&quot;age&quot;,&quot;circumference&quot;
1,118,30
1,484,58
1,664,87
1,1004,115
1,1231,120
1,1372,142
1,1582,145
2,118,33
2,484,69
2,664,111
2,1004,156
2,1231,172
2,1372,203
2,1582,203
3,118,30
3,484,51
3,664,75
3,1004,108
3,1231,115
3,1372,139
3,1582,140
4,118,32
4,484,62
4,664,112
4,1004,167
4,1231,179
4,1372,209
4,1582,214
5,118,30
5,484,49
5,664,81
5,1004,125
5,1231,142
5,1372,174
5,1582,177
&lt;/syntaxhighlight&gt;&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i20)	read_array(&quot;tree_data.csv&quot;, A2, &quot;,&quot;); 
(%o20)	done

(%i21) listarray(A2);
(%o21) [&quot;Tree&quot;,&quot;age&quot;,&quot;circumference&quot;,1,118,30,1,484,58,1,664,87,1,1004,
        115,1,1231,120,1,1372,142,1,1582,145,2,118,33,2,484,69,2,664,111,
        2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,
        3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
        4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,
        5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,
        5,1582,177]&lt;/syntaxhighlight&gt;The previous values of 0 and 0,0 as well as the assigned values of &lt;code&gt;A1&lt;/code&gt; and &lt;code&gt;A2&lt;/code&gt; have been replaced with the values from the CSV files.

The third array A3 can be used with values from the  dataset.csv file below:&lt;syntaxhighlight lang=&quot;text&quot;&gt;&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;
&quot;Smith&quot;,16753.00,&quot;UK&quot;,&quot;Qtr 3&quot;
&quot;Johnson&quot;,14808.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Williams&quot;,10644.00,&quot;UK&quot;,&quot;Qtr 2&quot;
&quot;Jones&quot;,1390.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Brown&quot;,4865.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Williams&quot;,12438.00,&quot;UK&quot;,&quot;Qtr 1&quot;
&quot;Johnson&quot;,9339.00,&quot;UK&quot;,&quot;Qtr 2&quot;
&quot;Smith&quot;,18919.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Jones&quot;,9213.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Jones&quot;,7433.00,&quot;UK&quot;,&quot;Qtr 1&quot;
&quot;Brown&quot;,3255.00,&quot;USA&quot;,&quot;Qtr 2&quot;
&quot;Williams&quot;,14867.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Williams&quot;,19302.00,&quot;UK&quot;,&quot;Qtr 4&quot;
&quot;Smith&quot;,9698.00,&quot;USA&quot;,&quot;Qtr 1&quot;&lt;/syntaxhighlight&gt;&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i22)	read_array(&quot;dataset.csv&quot;, A3, &quot;,&quot;); 
(%o22)	done

(%i23)	 listarray(A3);
(%o23)	[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;,
         &quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;,
         &quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;,
         &quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;,
         &quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;,
         &quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;,
         &quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;,
         &quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;,
         &quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]&lt;/syntaxhighlight&gt;

Values of the array can be referenced by indices as required for some purpose:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i24)	A3[0,0];
(%o24)	&quot;Last Name&quot;

(%i25)	A3[4,2];
(%o25)	&quot;USA&quot;
&lt;/syntaxhighlight&gt;
A row list object can be created using the &lt;code&gt;'''makelist ()'''&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i26)	row1A3: makelist(A3[0, j], j, 0, 3)$

(%i27)	row1A3;
(%o27)	[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;]

(%i28)	row1A3[1];
(%o28)	&quot;Last Name&quot;

(%i29)	row15A3: makelist(A3[14, j], j, 0, 3)$

(%i30)	row15A3;
(%o30)	[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]

(%i31)	row15A3[2];
(%o31)	9698.0
&lt;/syntaxhighlight&gt;
A list of the indices of the array can be created:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i32)	indices_A3 : arrayinfo(A3)[3];
(indices_A3)	[14,3]
&lt;/syntaxhighlight&gt;
The number of indices of array &lt;code&gt;A3&lt;/code&gt; can also be referenced using the &lt;code&gt;'''length (''')&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i33)	length(arrayinfo(A3)[3]);
(%o33)	2
&lt;/syntaxhighlight&gt;The number of values of the array &lt;code&gt;A3&lt;/code&gt; can be returned using the '''&lt;code&gt;length ()&lt;/code&gt;''' operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i34)	length(listarray(A3));
(%o34)	60
&lt;/syntaxhighlight&gt;
The values of the array &lt;code&gt;A3&lt;/code&gt; can be printed as output using the list of values with a loop programming expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i35)	for i:1 thru length (listarray(A3)) do 
            print('A3[i] ,&quot; = &quot;,  listarray(A3)[i])$

A3[1]&quot; = &quot;&quot;Last Name&quot;
A3[2]&quot; = &quot;&quot;Sales&quot;
A3[3]&quot; = &quot;&quot;County&quot;
A3[4]&quot; = &quot;&quot;Quarter&quot;
A3[5]&quot; = &quot;&quot;Smith&quot;
A3[6]&quot; = &quot;16753.0
A3[7]&quot; = &quot;&quot;UK&quot;
A3[8]&quot; = &quot;&quot;Qtr 3&quot;
A3[9]&quot; = &quot;&quot;Johnson&quot;
A3[10]&quot; = &quot;14808.0
A3[11]&quot; = &quot;&quot;USA&quot;
A3[12]&quot; = &quot;&quot;Qtr 4&quot;
A3[13]&quot; = &quot;&quot;Williams&quot;
A3[14]&quot; = &quot;10644.0
A3[15]&quot; = &quot;&quot;UK&quot;
A3[16]&quot; = &quot;&quot;Qtr 2&quot;
A3[17]&quot; = &quot;&quot;Jones&quot;
A3[18]&quot; = &quot;1390.0
A3[19]&quot; = &quot;&quot;USA&quot;
A3[20]&quot; = &quot;&quot;Qtr 3&quot;
A3[21]&quot; = &quot;&quot;Brown&quot;
A3[22]&quot; = &quot;4865.0
A3[23]&quot; = &quot;&quot;USA&quot;
A3[24]&quot; = &quot;&quot;Qtr 4&quot;
A3[25]&quot; = &quot;&quot;Williams&quot;
A3[26]&quot; = &quot;12438.0
A3[27]&quot; = &quot;&quot;UK&quot;
A3[28]&quot; = &quot;&quot;Qtr 1&quot;
A3[29]&quot; = &quot;&quot;Johnson&quot;
A3[30]&quot; = &quot;9339.0
A3[31]&quot; = &quot;&quot;UK&quot;
A3[32]&quot; = &quot;&quot;Qtr 2&quot;
A3[33]&quot; = &quot;&quot;Smith&quot;
A3[34]&quot; = &quot;18919.0
A3[35]&quot; = &quot;&quot;USA&quot;
A3[36]&quot; = &quot;&quot;Qtr 3&quot;
A3[37]&quot; = &quot;&quot;Jones&quot;
A3[38]&quot; = &quot;9213.0
A3[39]&quot; = &quot;&quot;USA&quot;
A3[40]&quot; = &quot;&quot;Qtr 4&quot;
A3[41]&quot; = &quot;&quot;Jones&quot;
A3[42]&quot; = &quot;7433.0
A3[43]&quot; = &quot;&quot;UK&quot;
A3[44]&quot; = &quot;&quot;Qtr 1&quot;
A3[45]&quot; = &quot;&quot;Brown&quot;
A3[46]&quot; = &quot;3255.0
A3[47]&quot; = &quot;&quot;USA&quot;
A3[48]&quot; = &quot;&quot;Qtr 2&quot;
A3[49]&quot; = &quot;&quot;Williams&quot;
A3[50]&quot; = &quot;14867.0
A3[51]&quot; = &quot;&quot;USA&quot;
A3[52]&quot; = &quot;&quot;Qtr 3&quot;
A3[53]&quot; = &quot;&quot;Williams&quot;
A3[54]&quot; = &quot;19302.0
A3[55]&quot; = &quot;&quot;UK&quot;
A3[56]&quot; = &quot;&quot;Qtr 4&quot;
A3[57]&quot; = &quot;&quot;Smith&quot;
A3[58]&quot; = &quot;9698.0
A3[59]&quot; = &quot;&quot;USA&quot;
A3[60]&quot; = &quot;&quot;Qtr 1&quot;
&lt;/syntaxhighlight&gt;

Maxima treats declared arrays as fixed-sized, and individual values are accessed via indices. There is no built-in &quot;row&quot; object — rows must be extracted manually using the &lt;code&gt;'''makelist ()'''&lt;/code&gt; operator or by looping through values of an array.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i36)	array(rowsA3,15);
(%o36)	rowsA3

(%i37)	arrayinfo(rowsA3);
(%o37)	[declared,1,[15]]

(%i38)	for i:0 thru 14 do
	       (rowsA3[i+1]:makelist(A3[i, j], j, 0, 3),
	        print(&quot;Row &quot;,i+1,&quot;: &quot;,rowsA3[i+1]))$;

&quot;Row &quot;1&quot;: &quot;[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;]
&quot;Row &quot;2&quot;: &quot;[&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;3&quot;: &quot;[&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;4&quot;: &quot;[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;5&quot;: &quot;[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;6&quot;: &quot;[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;7&quot;: &quot;[&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;8&quot;: &quot;[&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;9&quot;: &quot;[&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;10&quot;: &quot;[&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;11&quot;: &quot;[&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;12&quot;: &quot;[&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;13&quot;: &quot;[&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;14&quot;: &quot;[&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;15&quot;: &quot;[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]
&lt;/syntaxhighlight&gt;
Maxima does not have a built-in function like &lt;code&gt;delete&lt;/code&gt; or &lt;code&gt;unset&lt;/code&gt; for removing individual values from arrays using indices. Existing values of an array can be changed by assignment however:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i52)	rowsA3[1]:[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;]$

(%i53)	for i:1 thru 15 do
	    (newRowsA3[i]:rowsA3[i],
	    print(&quot;Row &quot;,i,&quot;: &quot;,newRowsA3[i]))$;

&quot;Row &quot;1&quot;: &quot;[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;2&quot;: &quot;[&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;3&quot;: &quot;[&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;4&quot;: &quot;[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;5&quot;: &quot;[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;6&quot;: &quot;[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;7&quot;: &quot;[&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;8&quot;: &quot;[&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;9&quot;: &quot;[&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;10&quot;: &quot;[&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;11&quot;: &quot;[&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;12&quot;: &quot;[&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;13&quot;: &quot;[&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;14&quot;: &quot;[&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;15&quot;: &quot;[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]&lt;/syntaxhighlight&gt;
The &lt;code&gt;'''arrayapply ()'''&lt;/code&gt; operator can be used a follows to reference values of a declared array:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i39)	arrayapply(rowsA3,[5]);
(%o39)	[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]

(%i40)	arrayapply(A3, [5,1]);
(%o40)	4865.0
&lt;/syntaxhighlight&gt;The operator &lt;code&gt;'''fillarray (A, B)'''&lt;/code&gt; assigns values to array &lt;code&gt;A&lt;/code&gt; from &lt;code&gt;B&lt;/code&gt;, which can be a list or an array.The dimensions of the arrays &lt;code&gt;A&lt;/code&gt; and &lt;code&gt;B&lt;/code&gt; may not be the same. In that case, array &lt;code&gt;A&lt;/code&gt; is filled in &quot;row-major&quot; order. There may not be enough values in &lt;code&gt;B&lt;/code&gt; compared to &lt;code&gt;A&lt;/code&gt;. In that case, the last value of &lt;code&gt;B&lt;/code&gt; is used to for the remaining values of &lt;code&gt;A&lt;/code&gt;. There may be too many values of &lt;code&gt;B&lt;/code&gt; compared to array &lt;code&gt;A&lt;/code&gt;. In that case, the remaining values of &lt;code&gt;B&lt;/code&gt; once &lt;code&gt;A&lt;/code&gt; is filled are not used. The return value of &lt;code&gt;'''fillarray ()'''&lt;/code&gt; is not the filled array &lt;code&gt;A&lt;/code&gt;, but it is the first argument.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* Create a declared array B of type fixnum */
(%i41)	array (B, fixnum, 9);
(%o41)	B

/* list the values of array B */
(%i42)	listarray (B);
(%o42)	[0,0,0,0,0,0,0,0,0,0]

/* fill array B with the values of the list */
(%i43)	fillarray (B, [0,1, 2, 3, 4, 5, 6, 7, 8, 9.0]);
(%o43)	B

/* list the values of array B */
(%i44)	listarray (B);
(%o44)	[0,1,2,3,4,5,6,7,8,9.0]

/* fill array B with the value 1.0 */
(%i45)	fillarray (B, [1.0]);
(%o45)	B

/* list the values of array B */
(%i46)	listarray (B);
(%o46)	[1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0]

/* fill array B with the first 9 values of the list */
(%i47)	fillarray (B, [0,1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12]);
(%o47)	B

/* list the values of array B */
(%i48)	listarray (B);
(%o48)	[0,1,2,3,4,5,6,7,8,9]

/* Create a declared array D of no type */
(%i49)	array (D, 9);
(%o49)	D

/* list the values of array D */
(%i50)	listarray (D);
(%o50)	[#####,#####,#####,#####,#####,#####,#####,#####,#####,#####]

/* fill array D with the value 1.0 */ 
(%i51)	fillarray (D, [1.0]);
(%o51)	D

/* list the values of array D */
(%i52)	listarray (D);
(%o52)	[1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0]

/* Create a declared array E of no type */
(%i53)	array (E, 15);
(%o53)	E

/* fill array E with the values from the newRowsA3 list */ 
(%i54)	fillarray (E, listarray (newRowsA3));
(%o54)	E

/* list the values of array D */
(%i55)	listarray (E);
(%o55)	[[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;],
         [&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;],
         [&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]]

/* remove array E */
(%i56)	remarray (E);
(%o56)	[E]

/*  D is no longer an array */
(%i57)	arrayinfo (E);
arrayinfo: E is not an array.

 -- an error. To debug this try: debugmode(true);&lt;/syntaxhighlight&gt;

If you need to keep the array but remove only one value, you must reconstruct it without that value. The operator &lt;code&gt;'''remarray ()'''&lt;/code&gt; is the typical way to completely remove an array.

The &lt;code&gt;'''rearray (A, dim&lt;sub&gt;1&lt;/sub&gt;, dim&lt;sub&gt;2&lt;/sub&gt; ,…, dim&lt;sub&gt;n&lt;/sub&gt;)'''&lt;/code&gt; operator is used to change the dimensions of an array. The changed array will be filled with the elements of the existing array in row-major order. If the existing array has one or more smaller dimensions, the additional dimension values of the changed array are assigned with a value that depends on the type of the array. If the existing array has one or more larger dimensions, the deficient dimension values of the changed array are lost. The type of the array cannot be changed using this operator. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* list with the values of array B */
(%i58)	listarray(B);
(%o58)	[0,1,2,3,4,5,6,7,8,9]

/* list with information about array B */
(%i59)	arrayinfo(B);
(%o59)	[complete,1,[9]]

/* increase the dimension of array B */
(%i60)	rearray (B, 12);
(%o60)	\#\{Lisp array \[13\]\}

/* list with information about array B with increased dimension */
(%i61)	arrayinfo(B);
(%o61)	[complete,1,[12]]

/* list with the values of array B */
(%i62)	listarray(B);
(%o62)	[0,1,2,3,4,5,6,7,8,9,0,0,0]

/* decrease the dimension of array B */
(%i63)	rearray (B, 6);
(%o63)	\#\{Lisp array \[7\]\}

/* list with information about array B with decreased dimension */
(%i64)	arrayinfo(B);
(%o64)	[complete,1,[6]]

/* list with the values of array B */
(%i65)	listarray(B);
(%o65)	[0,1,2,3,4,5,6]


&lt;/syntaxhighlight&gt;

The &lt;code&gt;'''arraymake ()'''&lt;/code&gt; operator returns a value that is an array reference without evaluation. This operator, in spite of the name, does not &quot;make&quot; an array. It returns this reference as a value whether or not an array exists as an object:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* the arraymake operator returns the unevaluated reference to A */
(%i66)	arraymake (A, [i,j]);
(%o66)	A[i,j]

/* however array A is not an array object*/
(%i67)	arrayinfo (A);
arrayinfo: A is not an array.
 -- an error. To debug this try: debugmode(true);

/* Maxima sees A[j,k] as a reference to an undefined memoizing function */
(%i68)	op (arraymake (A, [i,j]));
(%o68)	A
&lt;/syntaxhighlight&gt;
However, from a practical point of view, this operator is used with existing arrays:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i69)	listarray (newRowsA3);
(%o69)	[[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;],
         [&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;],
         [&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]]

(%i70)	arraymake (newRowsA3, [4]);
(%o70)	newRowsA3[4]

(%i71)	''%;
(%o71)	[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]

(%i72)	arraymake (newRowsA3, [i]);
(%o72)	newRowsA3[i]

(%i73)	''%, i = 6;
(%o73)	[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]

&lt;/syntaxhighlight&gt;
The operator &lt;code&gt;arraymake (x, [i])&lt;/code&gt; constructs the expression &lt;code&gt;x[i]&lt;/code&gt;, but does not evaluate it. 

The operator &lt;code&gt;'''subvar'''&lt;/code&gt; &lt;code&gt;'''(x, i)'''&lt;/code&gt; evaluates the indexed expression &lt;code&gt;x[i]&lt;/code&gt;, and evaluates its arguments. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i74)	listarray(B);
(%o174)	[0,1,2,3,4,5,6]

(%i75)	x : B;
(x)	B

(%i76)	i : 4;
(i)	4

(%i77)	subvar (x, i);
(%o77)	4
&lt;/syntaxhighlight&gt;
The operator &lt;code&gt;'''subvarp (expr)'''&lt;/code&gt; returns a value of &lt;code&gt;true&lt;/code&gt; if &lt;code&gt;expr&lt;/code&gt; is a indexed identifier, and &lt;code&gt;false&lt;/code&gt; otherwise. This operator evaluates the argument &lt;code&gt;expr&lt;/code&gt;.  &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;

(%i78)	z[p];
(%o78)	z[p]

(%i79)	subvarp (z[p]);
(%o79)	true

(%i80)	x[i];
(%o80)	4

(%i81)	subvar (x, i)
(%o81)	4

(%i82)	w : z[p];
(w)	z[p]

(%i83)	subvarp (w);
(%o83)	true


&lt;/syntaxhighlight&gt;
The expression &lt;code&gt;'''arrays'''&lt;/code&gt;  returns a list of allocated arrays: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i84)	arrays;
(%o84)	[A3,A2,A1,rowsA3,newRowsA3,B,D]&lt;/syntaxhighlight&gt;

The operator &lt;code&gt;'''arraysetapply (A, [i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2,&lt;/sub&gt;…,i&lt;sub&gt;n&lt;/sub&gt;], x)'''&lt;/code&gt; assigns the value of expression &lt;code&gt;x&lt;/code&gt; to &lt;code&gt;A&lt;/code&gt;&lt;code&gt;[i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2&lt;/sub&gt;,…,i&lt;sub&gt;n&lt;/sub&gt;]&lt;/code&gt;, where &lt;code&gt;A&lt;/code&gt; is an array and &lt;code&gt;i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2&lt;/sub&gt;,…,i&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt; are integers.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i85)	arraysetapply (newRowsA3, [8], [&quot;George&quot;,20818.0,&quot;UK&quot;,&quot;Qtr 4&quot;]);
(%o85)	[&quot;George&quot;,20818.0,&quot;UK&quot;,&quot;Qtr 4&quot;]&lt;/syntaxhighlight&gt;
=== Undeclared Arrays ===

Maxima declared arrays and Maxima undeclared arrays will likely be the two types of data structures used by most users. Maxima undeclared arrays are also referred to as '''''hashed arrays'''''. For both of these two array types, memory allocation and structure occur &quot;behind the curtain&quot; of the Maxima user level, and &quot;the man behind the curtain&quot; is Lisp.

Of these two types, hashed arrays are the most flexible from the user point of view, all other factors being equal:

* The indices allowed for hashed arrays can be expressions,
* The dimensions of a hashed array are dynamic and not fixed, and
* Hashed arrays are relatively easier to create.
In fact, hashed arrays can be somewhat too easy to create. In the examples of the previous section involving declared arrays, identifiers were used as names for arrays. here is the list of allocated arrays:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i86)	arrays;
(%o86)	[A3,A2,A1,rowsA3,newRowsA3,B,D,my_list,h]&lt;/syntaxhighlight&gt;The array information for array &lt;code&gt;newRowsA3&lt;/code&gt; is shown below:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i87)	arrayinfo(newRowsA3);
(%o87)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15]]
&lt;/syntaxhighlight&gt;So the array &lt;code&gt;newRowsA3&lt;/code&gt; is not a declared array. it was created as part of a loop programming expression repeated below:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i53)	for i : 1 thru 15 do
	    (newRowsA3[i] : rowsA3[i],
	    print(&quot;Row &quot;,i,&quot;: &quot;,newRowsA3[i]))$;&lt;/syntaxhighlight&gt;When the first loop block was executed with i : 1, the assignment expression:

&lt;code&gt;newRowsA3[i] : rowsA3[i]&lt;/code&gt;

created a hashed array named  &lt;code&gt;newRowsA3&lt;/code&gt; and assigned &lt;code&gt;newRowsA3[1]&lt;/code&gt; the value of &lt;code&gt;rowsA3[1]&lt;/code&gt; automatically without any declaration. After that the hashed array dynamically allocated memory for values of the loop identifier i from 2 through 15 with each successive pass in the loop expression. Since hashed arrays are undeclared, and their associated dimensions are not fixed, but rather increase dynamically, expressions can be added to hashed arrays without creating a error message. These added values can be can be any valid Maxima expression, and the value of the indices used are not limited to zero and nonzero integers:  &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i88)	newRowsA3[16] :  [&quot;Maisel&quot;,12785.0,&quot;USA&quot;,&quot;Qtr 2&quot;];
(newRowsA3[16])	[&quot;Maisel&quot;,12785.0,&quot;USA&quot;,&quot;Qtr 2&quot;]

(%i89	arrayinfo(newRowsA3);
(%o89)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15],[16]]

(%i90)	newRowsA3[z]  : 2*sin(y) ^2 + 3*sin(x)^3;
(newRowsA3[z])	2*sin(y)^2+3*sin(B)^3

(%i91)	arrayinfo(newRowsA3);
(%o91)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15],[16],[z]]
&lt;/syntaxhighlight&gt;So one point to glean from this example is that all that is required to create a hashed array is an assignment expression to an indexed identifier, but it does require this assignment. If for some reason, a declared array is intended, but not declared using the &lt;code&gt;array&lt;/code&gt; operator (as in the instance of &lt;code&gt;newRowsA3&lt;/code&gt;), then a hashed array will be created at the first assignment of an expression to an indexed identifier.

This issue can also occur in cases where reference to a list value is intended, but the list has not been created. Lists are one-dimensional objects by definition. A reference using an identifier with a single index intended to be a list with no list existing named by that identifier, can inadvertently create a hashed array.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i91)	Alist[2] : 2*sin(y) ^2 + 3*sin(s)^3;
(Alist[2])	2*sin(y)^2+3*sin(s)^3

(%i92)	listp(Alist);
(%o92)	false

(%i93)	arrayinfo(Alist);
(%o93)	[hashed,1,[2]]
&lt;/syntaxhighlight&gt;The identifier &lt;code&gt;Alist&lt;/code&gt; is a name for a hashed array and not a list.

However, hashed arrays, like declared arrays can, be multi-dimensional: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i94)	a_hashed_array [j,k,l] : [12,s^(1/3), %i];
(%o94)	[12,s^(1/3),%i]

(%i95)	arrayinfo(a_hashed_array);
(%o95)	[hashed,3,[j,k,l]]
&lt;/syntaxhighlight&gt;The &lt;code&gt;array&lt;/code&gt; operator can be used to transform a hashed array into a declared array:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i96)	another_hashed_array[ 0, 2, 3] : 55;
(%o96)	55

(%i97)	array (another_hashed_array, 2, 4, 5);
(%o97)	another_hashed_array

(%i98)	arrayinfo(another_hashed_array);
(%o98)	[declared,3,[2,4,5]]
&lt;/syntaxhighlight&gt;From the user point of view, hashed arrays and declared arrays typically can be used for the same purpose. If dynamic dimensions or index expression flexibility are factors, then hashed arrays are likely to be a better choice. Many of the operators that can use declared arrays as arguments, may also be used with hashed arrays.

However, it should be noted at this point, that merely using a indexed identifier alone without an assignment, will not create a hashed array. Instead, Maxima interprets an expression so composed as an identifier for an undefined memoizing function, which is the topic of the next section.

==== Memoizing Functions ====
Assignment using an indexed identifier implicitly creates an undeclared (hashed) array. However, entering an expression that is an unassigned indexed identifier, from the point of view of Maxima, creates the identifier of a &quot;memoizing&quot; function. Memoizing functions are technically not an array topic, as these functions fall under the category of function definition. These functions have one foot in the function category and the other foot in the array category.

Memoizing functions are defined in a manner similar to other user-defined functions, for example:

&lt;code&gt;f(x, y, z) := x^2 + y^2 + z^2;&lt;/code&gt;

But instead of the arguments being enclosed in parentheses, they are enclosed using brackets:

&lt;code&gt;f[x, y, z] := x^2 + y^2 + z^2;&lt;/code&gt;

However, memoizing functions may be referred to as ''array functions,'' and it is the case that these functions from the point of view of aggregate data structures are hashed arrays. So these are mentioned and exemplified here for that reason:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* reference an indexed identifier h without assignment */
(%i99)	h[x];
(%o99)	h[x]

/* check identifier h as an array */
(%i100)	arrayinfo (h);
arrayinfo: h is not an array.
  -- an error. To debug this try: debugmode(true);
  
/* check identifier h as a function */
(%i101)	op(h[x]);
(%o101)	h

/* define h[x] as a function */
(%i102)	h[x] := 5*x^3 + sin(x);
(h[x])	h[x]:=5*x^3+sin(x)

/* check identifier h[x] as a function */
(%i103)	op(h[x]);
(%o103)	&quot;+&quot;

/* check identifier h as an array */
(%i104)	arrayinfo (h);
(%o104)	[hashed,1,[x]]

/* check the value of identifier h[x] */
(%i105)	h[x];
(%o105)	sin(x)+5*x^3

/* evaluate identifier h[x] with the argument 3*%pi */
(%i106)	h[3*%pi];
(%o106)	135*%pi^3

/* list the values of identifier h as an array */
(%i107)	listarray(h);
(%o107)	[135*%pi^3,sin(x)+5*x^3]

/* check identifier h as an array */
(%i108)	arrayinfo (h);
(%o108)	[hashed,1,[3*%pi],[x]]&lt;/syntaxhighlight&gt;A defined memoizing function stores its value the ''first time'' it is referenced with arguments, and returns the stored value, without evaluation, when the same arguments are used with that function subsequently. The stored value is &quot;frozen&quot; after the initial evaluation. Thus, it behaves like a hashed array. The arguments of a memoizing function also serve as indices of the associated hashed array.

=== Lisp Arrays ===
Lisp arrays are created using the &lt;code&gt;make_array (type, dim&lt;sub&gt;1&lt;/sub&gt;, dim&lt;sub&gt;2&lt;/sub&gt;, …, dim&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt; operator. Perhaps a better name for this operator would be &lt;code&gt;make_lisp_array ()&lt;/code&gt;, which admittedly is a longer name.

This operator creates and has a return value of a Lisp array. The array type may be &lt;code&gt;any&lt;/code&gt;, &lt;code&gt;flonum&lt;/code&gt;, &lt;code&gt;fixnum&lt;/code&gt;, or  &lt;code&gt;hashed&lt;/code&gt; . The &lt;code&gt;functional&lt;/code&gt; type referred to in the Maxima Manual appears to have been deprecated, and may result in an error message if used. There can be ''n'' indices, and where the associated indices can be a value from ''0'' to ''dim&lt;sub&gt;i&lt;/sub&gt; -1'', and ''i'' can have a value of one of 1 to n inclusive.

This operator can be used as an alternative to the &lt;code&gt;array ()&lt;/code&gt; operator. The advantage of using &lt;code&gt;make_array()&lt;/code&gt; is that the return value of &lt;code&gt;make_array()&lt;/code&gt; ''does not have a name''. Once the Maxima identifier that is assigned to the array return value is no longer assigned, the array memory allocation is released, and the allocated memory can be garbage collected. What it is being referred to that Lisp arrays created using &lt;code&gt;make_array()&lt;/code&gt; do not have names? &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* create a undeclared Maxima hashed array */
(%i109)	arrayA1 [1] : 55;  
(%o109)	55

/* check the information about this undeclared Maxima hashed array */
(%i110)	arrayinfo (arrayA1);
(%o110)	[hashed,1,[1]]

/* check the value of this undeclared Maxima hashed array */
(%i111)	arrayA1;
(%o111)	arrayA1     /* the name */

/* create a Lisp hashed array */
(%i112)	arrayA2 : make_array (hashed);
(arrayA2)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 1 {1202987DC3}&gt;&quot;

/* check the information about this Lisp hashed array */
(%i113)	arrayinfo (arrayA2);
(%o113)	[hash_table,1]

/* check the value of this Lisp hashed array */
(%i114)	arrayA2;
(%o114)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 1 {1202987DC3}&gt;&quot; /* no name */

(%i115)	listarray (arrayA2);
(%o115)	[]                     /* this hashed array is empty */
&lt;/syntaxhighlight&gt;So Lisp arrays do not have a name as a value. So, Maxima identifiers assigned to a Lisp array have no name for the array as a value. These identifiers have the reference to the array itself as a value, Lisp hashed arrays created using &lt;code&gt;make_array()&lt;/code&gt; with the hashed type specified, do not use dimensions. Lisp hashed arrays are often referred to as '''''hashed tables''''', and their indices are called '''''keys'''''.

An example of a Lisp array with the type &lt;code&gt;any&lt;/code&gt; follows:

&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* make a Lisp 3 by 4 array of type any */
(%i116)	arrayA3 : make_array (any, 3,4);
(arrayA3)	\#\{Lisp array \[3\\,4\]\}

(%i117)	arrayinfo (arrayA3);
(%o117)	[declared,2,[2,3]]

(%i118)	listarray(arrayA3);
(%o118)	[false,false,false,false,false,false,false,false,false,false,false,false]

(%i119)	arrayA3[1,1] : &quot;a string&quot; ;
(%o119)	&quot;a string&quot;

(%i120)	listarray(arrayA3);
(%o120)	[false,false,false,false,false,&quot;a string&quot;,
         false,false,false,false,false,false]
&lt;/syntaxhighlight&gt;Contrary to statements made in some sources, type checking is is not accomplished automatically, and will not cause Maxima to return an error message, as the Lisp array with the type &lt;code&gt;fixnum&lt;/code&gt; which follows is an exemplifies:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i121)	arrayA4 : make_array (fixnum, 3,4);
(arrayA4)	\#\{Lisp array \[3\\,4\]\}

(%i122)	arrayinfo (arrayA4);
(%o122)	[declared,2,[2,3]]

(%i123)	listarray (arrayA4);
(%o123)	[0,0,0,0,0,0,0,0,0,0,0,0]

(%i124)	arrayA4[0,2] : 3.14159;
(%o124)	3.14159

(%i125)	arrayA4[0,0] : &quot;a string&quot;;
(%o125)	&quot;a string&quot;

/* value types not checked and no error message */
(%i126)	listarray (arrayA4);
(%o126)	[&quot;a string&quot;,0,3.14159,0,0,0,0,0,0,0,0,0]&lt;/syntaxhighlight&gt;As was the case with declared arrays, there is no type checking and no error messages associated with assigned values of the array based on the declared type. The declared array type simply determines initial fill values, if any.

Hashed arrays and Lisp hash tables have an operator in common:

&lt;code&gt;has_key&lt;/code&gt; &lt;code&gt;(A, L)&lt;/code&gt;

This expression has a a value of &lt;code&gt;true&lt;/code&gt;, if the hashed array or Lisp hash table &lt;code&gt;A&lt;/code&gt; has the key (index) or keys (indices) of the list object &lt;code&gt;L&lt;/code&gt;.  Otherwise the expression has a value of &lt;code&gt;false&lt;/code&gt;.

The array &lt;code&gt;A&lt;/code&gt; must be a hashed (undeclared) array, a Lisp hash table value returned by the &lt;code&gt;make_array&lt;/code&gt; operator, or created as an undeclared array with &lt;code&gt;use_fast_arrays&lt;/code&gt; assigned the value &lt;code&gt;true&lt;/code&gt;.

If array A has only one key, that key must be the value of a list.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i127)	arrayinfo (newRowsA3);
(%o127)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],
                  [11],[12],[13],[14],[15],[16],[z]]

(%i128)	has_key (newRowsA3, [z]);
(%o128)	true

(%i129)	has_key (newRowsA3, [3]);
(%o129)	true

(%i130)	has_key(newRowsA3, [0]);
(%o130)	false

(%i131)	lisp_Array_1 [x];
(%o131)	3*x^2

(%i132)	arrayinfo (lisp_Array_1);
(%o132)	[hash_table,1,x]

(%i133)	has_key (lisp_Array_1, [x]);
(%o133)	true

(%i134)	has_key (lisp_Array_1, [y]);
(%o134)	false
&lt;/syntaxhighlight&gt;

=== Arrays and Features ===
Maxima arrays can be assigned features in a manner similar to other identifiers:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i135)	array (a6,fixnum, 5);
(%o135)	a6

(%i136)	arrayinfo (a6);
(%o136)	[complete,1,[5]]

(%i137)	declare (a6, [real, noninteger]);
(%o137)	done

(%i138)	featurep (a6, real);
(%o138)	true

(%i139)	featurep (a6, noninteger);
(%o139)	true

(%i140)	a6[2] : 2;
(a6[2])	2

(%i141)	listarray (a6);
(%o141)	[0,0,2,0,0,0]
&lt;/syntaxhighlight&gt;However, once again, declaring an array to have one or more features does not result in type checking of values assigned to an array. Perhaps the best way to ensure types of values assigned to arrays is type-checking of expressions using predicate operators prior to assignment to arrays. 

=== Array Memory Storage Considerations ===

The following from the Maxima Manual&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.5.1 - Functions and Variables for Arrays |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Functions-and-Variables-for-Arrays}}&lt;/ref&gt; is quoted here for the purpose of establishing the context of that which follows:&lt;blockquote&gt;''&quot;Option variable: use_fast_arrays ¶''

''Default value: false''

''When use_fast_arrays is true, arrays declared by array are values instead of properties, and undeclared arrays (hashed arrays) are implemented as Lisp hashed arrays.''

''When use_fast_arrays is false, arrays declared by array are properties, and undeclared arrays are implemented with Maxima’s own hashed array implementation.''

''Note that the code use_fast_arrays switches to is not necessarily faster than the default one; Arrays created by make_array are not affected by use_fast_arrays.&quot;''&lt;/blockquote&gt;
This Maxima Manual entry requires some elaboration in order to have a sufficient understanding of the effect of the &lt;code&gt;'''use_fast_arrays'''&lt;/code&gt; &quot;flag&quot; – referred to as an &quot;Option Variable&quot; in the above quotation.

The first point to note is that the default value of this flag is &lt;code&gt;false&lt;/code&gt;. So, if users take no action to assign this flag to the value &lt;code&gt;true&lt;/code&gt;, then declared arrays created using the &lt;code&gt;array()&lt;/code&gt; operator  are treated as ''properties'' bound to a symbol, and behave in the manner previously described. Likewise undeclared arrays are a Maxima array implementation, and behave as legacy property hash tables, and these also behave as previously described.

If action is taken to enter an expression that assigns the value &lt;code&gt;true&lt;/code&gt; to this flag, then Maxima treat arrays as standard Lisp ''values'' rather than object properties:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i142)	use_fast_arrays;
(%o142)	false

(%i143)	array (A1,fixnum, 10);
(%o143)	A1

(%i144)	arrayinfo (A1);
(%o144)	[complete,1,[10]]

(%i145)	H1[1] : 1729;
(H1[1])	1729

(%i146)	arrayinfo (H1);
(%o146)	[hashed,1,[1]]

(%i147)	use_fast_arrays : true;
(use_fast_arrays)	true

(%i148)	array (A2, fixnum, 10);
(%o148)	\#\{Lisp array \[11\]\}

(%i149)	A2;
(%o149)	\#\{Lisp array \[11\]\}

(%i150)	H2[1] : 1729;
(H2[1])	1729

(%i151)	H2;
(%o151)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 2 {1203AD15A3}&gt;&quot;

(%i152)	arrayinfo (H2);
(%o152)	[hash_table,1,1]
&lt;/syntaxhighlight&gt; The &lt;code&gt;use_fast_arrays&lt;/code&gt; flag has no effect on arrays created using the &lt;code&gt;make_array ()&lt;/code&gt; operator.

Note the following:

* Assigning &lt;code&gt;use_fast_arrays&lt;/code&gt; &lt;code&gt;: true&lt;/code&gt; does not speed up execution for all operations. It primarily optimizes memory footprint by minimizing cell allocations.  The main benefit is optimization of memory footprints and structural representation inside Lisp.
* If compiling Maxima expressions to native Lisp using the &lt;code&gt;translate&lt;/code&gt; &lt;code&gt;()&lt;/code&gt; operator, pair this flag with &lt;code&gt;translate_fast_arrays&lt;/code&gt; &lt;code&gt;: true&lt;/code&gt;. This flag instructs the translator to compile arrays as value-based.

=== Structures ===
Structures, although not an array data type is an aggregation data type.  By &quot;aggregation&quot; it is meant a data type that references other data types by reference to a name and some method of accessing individual values of instances of that aggregation by means of indices used to reference values individually.

Thus, as has been previously described for example lists, hashed arrays, Lisp arrays, and declared arrays are all aggregation data types with syntactical means to refer to individual values of a named aggregation instance by way of indices, which are sometimes also referred to as subscripts or keys.

As examples:

* An existing '''list''' named &lt;code&gt;L1&lt;/code&gt; has values that can be accessed as &lt;code&gt;L1[1]&lt;/code&gt;, &lt;code&gt;L[2]&lt;/code&gt;, &lt;code&gt;L[3]&lt;/code&gt;, and so forth
* An existing '''hashed array''' with two indices (&quot;2D&quot;) named &lt;code&gt;ha&lt;/code&gt; has values that can accessed as &lt;code&gt;ha[1,1&lt;/code&gt;], &lt;code&gt;ha[1,2]&lt;/code&gt;,..., &lt;code&gt;ha[2,1]&lt;/code&gt;, &lt;code&gt;ha[2,2]&lt;/code&gt;, and  so forth.
* An existing '''declared array''' with three indices (&quot;3D&quot;) named &lt;code&gt;da&lt;/code&gt; has values that can be accessed as &lt;code&gt;da[1,1,1]&lt;/code&gt;, &lt;code&gt;da[1,1,2]&lt;/code&gt;,...,&lt;code&gt;da [2,1,1]&lt;/code&gt;, ..., &lt;code&gt;da[3,1,1]&lt;/code&gt;, and so forth.

What makes the Maxima structure data type different from these array data types is the form of definition used and the means of accessing values of an instance of this type of aggregation. The Maxima structure data type seems to be the closest type of data that resembles an object in some other general-purpose programming languages.

The structure type of data allows the creation of named entities with attributes, and named instances of those entities and the assignment of values to those attributes. Thus the Maxima structure data type is used to define custom, named composite data types that group related fields together under a single identifier. Structures enhance code organization and readability, especially when modeling real-world entities in symbolic computations. They are useful for managing complex data in programs involving algebraic manipulations, simulations, or data modeling.  

Structures are created using the &lt;code&gt;defstruct&lt;/code&gt; operator, which defines a template with named attributes. Once defined, instances of the structure are created using the &lt;code&gt;new&lt;/code&gt; operator, and attributes are accessed via the &lt;code&gt;@&lt;/code&gt; operator. 

So in the interest of taking advantage of this information, consider a well-defined set of people. The people of this set may have many diverse attributes that might be of interest - name, age ,and city of residence as examples. A class of people of the set of interest with these attributes can be defined as follows: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i153)	defstruct (person (name, age, city));
(%o153)	[person(name,age,city)]

(%i54) structures;
(%o154)                      [person(name, age, city)]

(%i155)	p : new (person (&quot;Alice&quot;, 30, &quot;New York&quot;));
(p)	person(name=&quot;Alice&quot;,age=30,city=&quot;New York&quot;)

(%i156)	p@name;
(%o156)	&quot;Alice&quot;

(%i157)	p@city;
(%o157)	&quot;New York&quot;

(%i158)	kill(p@city);
(%o158)	done

/* If the attribute a in x has not been assigned a value, or the value
   has been &quot;killed,&quot; then x@a evaluates to itself */

(%i159)	p@city;
(%o159)	p@city

(%i160)	p;
(%o160)	person(name=&quot;Alice&quot;,age=30,city)

(%i161)	p@city : &quot;Rochester&quot;;
(%o161)	&quot;Rochester&quot;

(%i162)	p;
(%o162)	person(name=&quot;Alice&quot;,age=30,city=&quot;Rochester&quot;)

(%i163) defstruct (sales(LastName, Sales , Country , Quarter) );
(%o163)             [sales(LastName, Sales, Country, Quarter)]

(%i164) structures;
(%o164) [person(name, age, city), sales(LastName, Sales, Country, Quarter)]

(%i165) s : new (sales (&quot;Smith&quot;,16753.00,&quot;UK&quot;,&quot;Qtr 3&quot;));
(%o165) sales(LastName=Smith, Sales=16753.0, Country=UK, Quarter=Qtr 3)

(%i166) s@Sales;
(%o166)                              16753.0

(%i167) s@Sales : 17375.0;
(%o167)                              17375.0

(%i168) s;
(%o168) sales(LastName=Smith, Sales=17375.0, Country=UK, Quarter=Qtr 3)&lt;/syntaxhighlight&gt;{{Bookcat}}</text>
      <sha1>4q7c2qaqaebf08cisqd7o7z9wlhxkxx</sha1>
    </revision>
    <revision>
      <id>4668966</id>
      <parentid>4668964</parentid>
      <timestamp>2026-09-05T17:33:30Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <minor />
      <comment>/* Introduction */</comment>
      <origin>4668966</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="64575" sha1="m8lenlneqjznbdxktwfrp17erygjika" xml:space="preserve">== Maxima Aggregate Data Structures ==

=== Introduction ===
This section is intended to present some of the essentials of what are called Maxima aggregate data structures. By this it is meant the data types that can be used to refer to the values of expressions using a means of indexing of a single identifier (name) that refers to an aggregate (collection) of expressions as values.

Built-in aggregate data types include: 

* lists
* declared arrays
* hashed (undeclared) arrays
* Lisp arrays
* structures

Each of these has a means of indexing an identifier that names an instance of these data types. 

Please note that it is the case that this means of indexing an identifier for an aggregate data type may be referred to as involving &quot;subscripts&quot; or &quot;sub-scripted variables&quot; or &quot;keys&quot; as used by various computer programming languages, as well as in the context of Maxima documentation and commentary. In this book terms such as &quot;index&quot; or &quot;indices&quot; or &quot;indexed identifiers&quot;  are used instead.

Also all built-in Maxima functions (including packages) for these data types are referred to as ''&quot;operators&quot;'' and not ''&quot;functions&quot;'' as this latter term in general serves better to refer to Maxima function expressions defined by the user -- as in &lt;code&gt;f(x) :=&lt;/code&gt;, &lt;code&gt;g[s] :=&lt;/code&gt; and &lt;code&gt;define ()&lt;/code&gt; as examples.

This section is not intended to be exhaustive. It is intended to provide familiarity with aggregate data types. What is included has been gleaned from various sources, and only a few attributions are provided. Therefore, there is no claim of originality implied. 

=== Lists ===

==== Introduction to Lists ====
Lists are one of the basic buildings block for Maxima and Lisp. Maxima expressions are in general represented as Lisp lists. 

For example, consider the Maxima expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	e+3;
(%o1)	e+3
&lt;/syntaxhighlight&gt;This expression has the form of a Lisp list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i2)	:lisp #$[e+3]$
((MLIST SIMP) ((MPLUS SIMP) 3 $E))
&lt;/syntaxhighlight&gt;An expression in the form of a Lisp list can also be be displayed as a Maxima expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i2)	:lisp (displa '((MLIST SIMP) ((MPLUS SIMP) 3 $E)));
[e+3]
NIL
&lt;/syntaxhighlight&gt;Note that the value of this expression using &lt;code&gt;displa '()&lt;/code&gt; is &lt;code&gt;NIL&lt;/code&gt;, and &lt;code&gt;[e+3]&lt;/code&gt; is simply displayed in Maxima list object form. It is not necessary for the typical uses of Maxima to utilize this insight into the role Lisp lists have as one of the building blocks for Maxima, but it may be useful to have a familiarity with that role. Lists are often used as arguments to many operators, and the values of expressions are often in the form of lists.

==== Some Operators for Lists ====
Lists are created explicitly and list elements referenced using &lt;code&gt;[&lt;/code&gt; and &lt;code&gt;]&lt;/code&gt; to mark the beginning and end, respectively, of an instance of a list object, or to reference the expressions of an existing list object.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i3)	[2,3,4];
(%o3)	[2,3,4]
&lt;/syntaxhighlight&gt;The expression &lt;code&gt;[2,3,4]&lt;/code&gt; creates a Maxima list object. In this case the object itself is not accessible as it was not assigned an identifier unless referenced by the &lt;code&gt;%&lt;/code&gt; , &lt;code&gt;%i&lt;/code&gt; or &lt;code&gt;%o&lt;/code&gt; label.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i4)	%;
(%o4)	[2,3,4]

(%i5)	%o4[2]; /* second expression of list object referenced by index */ 
(%o5)	3
&lt;/syntaxhighlight&gt;That [2,3,4] is a list object can be tested using the &lt;code&gt;listp()&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i6)	listp ([2,3,4]);
(%o6)	true
&lt;/syntaxhighlight&gt;A list object can be assigned an identifier:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i7)	s:[%pi,%e,%phi];
(s)	[%pi,%e,%phi]

(%i8)	listp (s);
(%o8)	true&lt;/syntaxhighlight&gt;

The value of an element of a list can be accessed using the list identifier and brackets with a index value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i9)	s[1];
(%o9)	%pi

(%i10)	s[2];
(%o10)	%e

(%i11)	s[3];
(%o11)	%phi
&lt;/syntaxhighlight&gt;
Invalid index values returns an error:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i12)	s[4];
inpart: invalid index 4 of list or matrix.
-- an error. To debug this try: debugmode(true);
&lt;/syntaxhighlight&gt;
Consider the following relatively long list of integer atoms created explicitly and identified as &lt;code&gt;List_1&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i13)	List_1:[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582,145,2,
	    118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,
	    30,3,484,51,3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,4,
	    484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,5,118,30,5,484,
	    
	    49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177];

(List_1)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,2,1582,203
,3,118,30,3,484,51,3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,
214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177]&lt;/syntaxhighlight&gt;
The number of values of this list can be returned using the &lt;code&gt;length()&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i14)	length (List_1);
(%o14)	105
&lt;/syntaxhighlight&gt;
Create another list identified as &lt;code&gt;List_2&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i15)	List_2 : [6,1455,200,6,1607,205];
(List_2)	[6,1455,200,6,1607,205]

(%i16)	length (List_2);
(%o16)	6
&lt;/syntaxhighlight&gt;
Create a third list identified as &lt;code&gt;List_3&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i17)	List_3 : append (List_1, List_2)$

(%i18)	length (List_3);
(%o19)	111
&lt;/syntaxhighlight&gt;
Note that the &lt;code&gt;'''append ()'''&lt;/code&gt; operator does not affect either of the list arguments &lt;code&gt;List_1&lt;/code&gt; or &lt;code&gt;List&lt;/code&gt;_2. It merely appends &lt;code&gt;List_2&lt;/code&gt; to &lt;code&gt;List_1&lt;/code&gt; and returns a new list, in this case assigned the identifier &lt;code&gt;List_3&lt;/code&gt;.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i20)	length (List_1);
(%o20)  105

(%i21)	length (List_2);
(%o21)  6

(%i22)	length (List_3);
(%o22)	111

(%i23)	List_3;
(%o23)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
         142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
         1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
         75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
         1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
         142,5,1372,174,5,1582,177,6,1455,200,6,1607,205]&lt;/syntaxhighlight&gt;
Values (the last one in this example) can be deleted from a list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i24)	last (List_3);
(%o24)	205

(%i25)	delete (last (List_3), List_3);
(%o25)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
         142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
         1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
         75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
         1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
         142,5,1372,174,5,1582,177,6,1455,200,6,1607]&lt;/syntaxhighlight&gt;
The &lt;code&gt;delete (List_3)&lt;/code&gt; expression creates a new list object using &lt;code&gt;List_3&lt;/code&gt;. &lt;code&gt;List_3&lt;/code&gt; itself is not affected by the &lt;code&gt;'''delete ()'''&lt;/code&gt; operator. Only the resulting list is affected. This is often the case with list operators. An identifier could be used to save the above resulting list if necessary:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* List_3 is the same length */
(%i26)	length(List_3); 
(%o26)	111

/* The last value of List_3 is the same */
(%i27)	List_3[111];
(%o27)	205

(%i28)	last(List_3);
(%o28)	205&lt;/syntaxhighlight&gt;There was only one instance of &lt;code&gt;205&lt;/code&gt; in &lt;code&gt;List_3&lt;/code&gt;, so only that value was deleted from the list of &lt;code&gt;%o25&lt;/code&gt;.  If there are more than one value then the &lt;code&gt;delete ()&lt;/code&gt; operator will remove all of those values from the returned list expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i29)	NewList_3 : delete(118, List_3)$ 

/* all five instances of 118 removed from List_3 as NewList_3 */
(%i30)	length(NewList_3);
(%o30)	106
&lt;/syntaxhighlight&gt;There are operators to refer to instances of list expressions by ordinal number:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i30)	FirstThreeList_3:[first(List_3), second(List_3), third(List_3)];
(FirstThreeList_3)	[1,118,30]
&lt;/syntaxhighlight&gt;Expressions of list objects can e referenced to create a new list object from the first n expressions of a list, the last n expressions of a list, or the rest remaining after n expressions from the beginning or -n expressions from the end of a list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* first three expressions of List_3 */
(%i31)	firstn(List_3,3); 
(%o31)	[1,118,30]

/* same three expressions of List_3 using the rest operator with -108 */
(%i32)	rest(List_3, -108); 
(%o32)	[1,118,30]

/* last three expressions of List_3 */
(%i33)	lastn(List_3,3); 
(%o33)	[6,1607,205]

/* same three expressions of List_3 using the rest operator with 108 */
(%i34)	rest(List_3, 108);
(%o34)	[6,1607,205]&lt;/syntaxhighlight&gt;Some further examples of the &lt;code&gt;'''firstn ()'''&lt;/code&gt;, &lt;code&gt;'''lastn ()'''&lt;/code&gt; and &lt;code&gt;'''rest ()'''&lt;/code&gt; list operators:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* first 63 expressions of List_3 */
(%i35)	firstn (List_3, 63);
(%o35)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,
         1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,
         1372,203,2,1582,203,3,118,30,3,484,51,3,664,75,3,1004,108,3,
         1231,115,3,1372,139,3,1582,140]

/* last 63 expressions of List_3 */
(%i36)	lastn (List_3, 63);
(%o36)	[3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,
         5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,
         1582,177,6,1455,200,6,1607,205]

/* first expressions of List_3 after removing the last 63*/
(%i37)	rest (List_3, -63);
(%o37)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,
         1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,
         1372,203,2,1582,203,3,118,30,3,484,51]
&lt;/syntaxhighlight&gt;Maxima programming expressions can be used with list operators to reference list expressions in various ways. For example, the expression which follows accesses the expressions of a list as lists of three each:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i38)	(L4 : List_4,
	      for i:(-length (List_4)) + 3 thru 0 step 3 do
	             (disp (rest (L4, i)), 
	              L4 : rest (L4, 3)),
	     &quot;&quot;)$

[1,118,30]
[1,484,58]
[1,664,87]
[1,1004,115]
[1,1231,120]
[1,1372,142]
[1,1582,145]
[2,118,33]
[2,484,69]
[2,664,111]
[2,1004,156]
[2,1231,172]
[2,1372,203]
[2,1582,203]
[3,118,30]
[3,484,51]
[3,664,75]
&lt;/syntaxhighlight&gt;List operators can be used as arguments other list operators:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* create a new empty list */
(%i39)	newList4 : [];
(newList4)	[]

/* append the first six &amp; last six expressions of List_4 to the new list */
(%i40)	newList4 : append (newList4, firstn (List_4, 6), lastn (List_4, 6))$

/* the new list now has the 12 appended expressions from List_4 */
(%i41)	newList4;
(%o41)	[1,118,30,1,484,58,3,484,51,3,664,75]
&lt;/syntaxhighlight&gt;

Maxima programming expressions can be used to step through the expressions of lists using list operators to reference &quot;slices&quot; of different lengths:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i42)	L4 : List_4;
(L4)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582
         145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,
         2,1582,203,3,118,30,3,484,51,3,664,75]

(%i43)	length (L4);
(%o43)	51

(%i44)	(L4 : List_4,
         for i : 21 thru 3 step -3 do
	         print (L4 : lastn (L4, i),&quot; &quot;, length (L4)),
	    &quot;&quot;)$

[2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 21

[2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 18

[2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 15

[2,1582,203,3,118,30,3,484,51,3,664,75] 12

[3,118,30,3,484,51,3,664,75] 9

[3,484,51,3,664,75] 6

[3,664,75] 3&lt;/syntaxhighlight&gt;

==== Using the &lt;code&gt;copylist&lt;/code&gt; Operator ====
When an existing list object is assigned to an identifier, a reference to the memory location of the list object is used. This reference to the memory location is transparent from the point of view of the user. However,if this is not  accounted for unintended side effects may occur when assigning another identifier to an existing one that references a list object.

For example, in the expression &lt;code&gt;L4 : List_4&lt;/code&gt; it might be assumed that this results in the list object referenced by &lt;code&gt;List_4&lt;/code&gt; to simply be copied to a new memory location and reference for &lt;code&gt;L4&lt;/code&gt;. This is not the case. Both &lt;code&gt;L4&lt;/code&gt; and &lt;code&gt;List_4&lt;/code&gt; refer to the same list object in memory. Consequently changes to the same list object can be effected by referencing the object using either alias.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i45)	newList4;
(%o45)	[1,118,30,1,484,58,3,484,51,3,664,75]

/* The identifier newList4 refers to a location in memory.
   The colon (:) assignment operator simply creates an alias
   using that same memory reference*/

(%i46)	newList5 :  newList4;
(newList5)	[1,118,30,1,484,58,3,484,51,3,664,75]

/* Two different identifiers for the same memory location and
   therefore the same object. Changes to expressions of the list
   object using either identifier changes the same object in memory */
   
(%i47)	newList5[1] : 99;
(newList5[1])	99

(%i48)	newList4[1];
(%o48)	99

(%i49)	newList4;
(%o49)	[99,118,30,1,484,58,3,484,51,3,664,75]

(%i50)	newList5;
(%o50)	[99,118,30,1,484,58,3,484,51,3,664,75]
&lt;/syntaxhighlight&gt;
This &quot;side effect&quot; is often unwanted. The way to avoid this is by using the &lt;code&gt;copylist ()&lt;/code&gt; operator instead of the assignment operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i51)	newList4 : [1,118,30,1,484,58,3,484,51,3,664,75] ;
(newList4)	[1,118,30,1,484,58,3,484,51,3,664,75]

(%i52)	newList5 : copylist (newList4);
(newList5)	[1,118,30,1,484,58,3,484,51,3,664,75]
 
 /* Same list object expressions, but a different memory reference */

(%i53)	newList5[1] : 99;
(newList5[1])	99

(%i54)	newList4[1];
(%o54)	1
&lt;/syntaxhighlight&gt;
Changes to the values of either list will not affect the other list.
{| class=&quot;wikitable&quot;
|+List Object Operators
|[
|fourth
|rreduce
|-
|]
|fullsetify
|second
|-
|append
|join
|setify
|-
|assoc
|last
|seventh
|-
|cons
|length
|sixth
|-
|copylist
|listarith
|some
|-
|create_list
|listp
|sort
|-
|delete
|lmax
|sublist
|-
|eighth
|lmin
|sublist_indices
|-
|endcons
|lreduce
|tenth
|-
|fifth
|makelist
|third
|-
|first
|member
|tree_reduce
|-
|flatten
|reverse
|xreduce
|}

Refer to the Maximal Manual&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.4.2 Functions and Variables for Lists |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Lists}}&lt;/ref&gt; for more complete description of operators and variables for Maxima lists.

==== Performance Considerations for Lists ====
&lt;blockquote&gt;''&quot;Lists provide efficient ways of appending and removing elements. They can be created without knowing their final dimensions. Lisp provides efficient means of copying and handling lists. Also nested lists do not need to be strictly rectangular. These advantages over declared arrays come with the drawback that the amount of time needed for accessing a random element within a list may be roughly proportional to the element’s distance from its beginning.&quot;''&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.4.3 Performance considerations for Lists |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Lists}}&lt;/ref&gt;&lt;/blockquote&gt;Maxima list objects have many operators for creating, accessing, and changing the expressions of lists. Evaluation times of expressions that involve lists can vary significantly depending on the length of the list objects involved, as well as the nature of any operators used to compose the expressions. This fact might have an influence on the choice of using arrays rather than lists in some cases if evaluation time is a factor to consider. The example expressions that follow involve a list object (identified as &lt;code&gt;s&lt;/code&gt; ) of complex number expressions that has a length of 10,000 and two different user-defined functions:&lt;pre&gt;(%i55) P1(s) := rectform (product(s[i], i, 1, length (s)))$

(%i56) P2(s) := xreduce (lambda ([a, b], rectform (a * b)), s)$

(%i57) s : makelist (random (1.0) + %i*random (1.0), 10^4)$

(%i58)	showtime : true$
Evaluation took 0.0000 seconds (0.0000 elapsed) using 0 bytes.

(%i59) P1(s);
Evaluation took 32.3080 seconds (32.3860 elapsed) using 17944.301 MB.
(%o59) 0.0

(%i60) P2(s);
Evaluation took 0.0620 seconds (0.0620 elapsed) using 8.343 MB.
(%o60) 0.0

(%i61)	showtime : false$
Evaluation took 0.0000 seconds (0.0000 elapsed) using 0 bytes.&lt;/pre&gt;
==Arrays ==
&lt;blockquote&gt;&quot;Maxima's current array/matrix semantics are a mess, I must say, with at least four different kinds of object (hash arrays, explicit lists, explicit matrices, Lisp arrays) supporting subscripting with varying semantics.&quot; &lt;ref&gt;[http://comments.gmane.org/gmane.comp.mathematics.maxima.general/21829 Maxima: Syntax improvements by Stavros Macrakis ]&lt;/ref&gt;
– Stavros Macrakis

&quot;Maxima's concept of arrays, lists, and matrices is pretty confused, since various ideas have accreted in the many years of the project... Yes, this is a mess. Sorry about that. These are all interesting ideas, but there is no unifying framework.&quot;&lt;ref&gt;[http://stackoverflow.com/a/29926692 Maxima: what does Maxima call an “array”? - answer by Robert Dodier]&lt;/ref&gt;

– Robert Dodier&lt;/blockquote&gt;

The various terminology used in the context of arrays undoubtedly can be confusing. For the sake of simplicity and clarity the following categories of array objects are referred to in this book:


Maxima has three array categories :&lt;ref&gt;[http://permalink.gmane.org/gmane.comp.mathematics.maxima.general/13588 the Maxima mailing list &lt;nowiki&gt;: [Maxima] array and matrix? - answer by Robert Dodier&lt;/nowiki&gt;]&lt;/ref&gt;
* Declared arrays 
* Undeclared (hashed) arrays 
* Lisp arrays 

'''''Declared arrays''''' are explicitly created using the &lt;code&gt;array()&lt;/code&gt; operator, and unlike lists, which have only one index and are one-dimensional, declared  arrays can be multi-dimensional  – having one to five indices. The indices for declared array dimensions need not be equal.

Indices for each dimension may be between 0 and the respective declared dimension. Each declared array may be for expressions of a specified type, which can be ''fixnum'' for integers or ''flonum'' for floating-point numbers.

'''''Undeclared (hashed) arrays''''' are created implicitly by assigning an expression to an indexed identifier that does not name an existing list object. An undeclared array (hashed array) can grow dynamically as there is no fixed dimension limit for each index as there is with declared arrays Another difference is that numbers, identifiers, expressions and strings may be used for indices.

Also, there is no fixed limit on the number of dimensions. The only real limitation is practical – the available computer memory and the underlying Lisp environment of the Maxima session. Hashed arrays with only one dimension may be confused with a list object.

It is essential to keep in mind that list objects must always be created before values are assigned or referenced. Assigning an expression to a one-dimensional indexed identifier, that does not reference an existing list, implicitly creates a hashed array.

'''''Lisp arrays''''' are created using the &lt;code&gt;'''make_array ()'''&lt;/code&gt; operator. The array type may be specified as ''any'', ''flonum'', ''fixnum'', or ''hashed''. Lisp array objects may be created as one-dimensional or multi-dimensional as specified by the number of dimension size values used with the &lt;code&gt;'''make_array ()'''&lt;/code&gt; operator. For each  dimension value specified, the associated index value can be a number between 0 to 1 less than the respective dimension value. The same or different values may be used for each specified dimension. the ''hashed'' type does not require any dimensions. Lisp arrays may be used in cases where memory usage and garbage collection are factors.

Examples of use and elaboration upon the technical details for each of these categories of array object types follows.
{| class=&quot;wikitable&quot;
|+Array Operators and Flags
|array
|arraysetapply
|rearray
|-
|arrayapply
|has_key
|remarray
|-
|arrayinfo
|fillarray
|subvar
|-
|arraymake
|listarray
|subvarp
|-
|arrays
|make_array
|use_fast_arrays
|-
|
|
|translate_fast_arrays
|}
=== Declared Arrays ===
Declared arrays must be created before being referenced and are of fixed dimensions.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	array(A1, fixnum, 34,2); 
(%o1)	A1

(%i2)	array(A2, flonum, 35,2);
(%o2)	A2

(%i3)	array(A3, 14,3);
(%o3)	A3

(%i4)	arrayinfo (A1);
(%o4)	[complete,2,[34,2]]

(%i5)	arrayinfo (A2);
(%o5)	[complete,2,[35,2]]

(%i6)	arrayinfo (A3);
(%o6)	[declared,2,[14,3]]
&lt;/syntaxhighlight&gt;
The first expression &lt;code&gt;%i1&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A1&lt;/code&gt;. This array is two-dimensional – the first index may have values from 0 to 34 and the second index may have values from 0 to 2. This array therefore is 35 by 3 in extent. The array type is declared to be &lt;code&gt;fixnum&lt;/code&gt;. As it is, &lt;code&gt;A1&lt;/code&gt; is an not empty array – it has values to reference as will be exemplified below.

Similarly the second expression &lt;code&gt;%i2&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A2&lt;/code&gt;. This array is also two-dimensional – the first index may have values from 0 to 35 and the second index may have values from 0 to 2. This array therefore is 36 by 3 in extent. The array type is declared to be &lt;code&gt;flonum&lt;/code&gt;. As it is, &lt;code&gt;A2&lt;/code&gt; is not an empty array – it also has values to reference as will be exemplified below.

The third expression &lt;code&gt;%i3&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A3&lt;/code&gt;. This array is also two-dimensional – the first index may have values from 0 to 13 and the second index may have values from 0 to 3. This array therefore is 15 by 4 in extent. The array type is not declared. As it is, &lt;code&gt;A3&lt;/code&gt; is an empty array – it has no values to reference as will be exemplified below.

The &lt;code&gt;'''arrayinfo ()'''&lt;/code&gt; operator can be used to return a list object that has values reflecting information about an array. Note that arrays declared without a type will have &lt;code&gt;declared&lt;/code&gt; as a value of the list. Arrays declared with &lt;code&gt;fixnum&lt;/code&gt; or &lt;code&gt;flonum&lt;/code&gt; as the type will have &lt;code&gt;complete&lt;/code&gt; as a value of the list. This technical detail is not well-documented. The returned information list also shows a value for the dimension of the array ( 2 in these examples ) and an inner list with values for the maximum index for each dimension.

A look inside each of these declared arrays provides a clue as to why &lt;code&gt;complete&lt;/code&gt; is returned instead of &lt;code&gt;declared&lt;/code&gt; when the type is specified as &lt;code&gt;fixnum&lt;/code&gt; or &lt;code&gt;flonum&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* This array reference has a value of 0 */
(%i7)	A1[0,0];
(%o7)	0

/* This array reference has a value of 0.0 */
(%i8)	A2[0,0];
(%o8)	0.0

/* This array reference has a value of itself */
(%i9)	A3[0,0];
(%o9)	A3[0,0]&lt;/syntaxhighlight&gt;

In fact, ''all'' values of the array &lt;code&gt;A1&lt;/code&gt; have been assigned 0, and ''all'' values of the array &lt;code&gt;A2&lt;/code&gt; have beenassigned 0.0. However, ''all'' values of the array &lt;code&gt;A3&lt;/code&gt; have been not been assigned any value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i10)	listarray(A1);
(%o10)	[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0]

(%i11)	listarray(A2);
(%o11)	[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]

(%i12)	listarray(A3);
(%o12)	[#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####]&lt;/syntaxhighlight&gt;

Thus, arrays &lt;code&gt;A1&lt;/code&gt; and &lt;code&gt;A2&lt;/code&gt; are &lt;code&gt;complete&lt;/code&gt; in this sense, and array &lt;code&gt;A3&lt;/code&gt; is simply &lt;code&gt;declared&lt;/code&gt;.

It might seem reasonable, that Maxima would complain if a value was assigned to an array that is at odds with the declared type. Such is not the case however. Once an array is declared with a type, Maxima does not enforce any type checking of values assigned to the array. The effect of the type (if any) in the declaration is simply to fill the array with values of #####, 0 or 0.0. Subsequently, those values can be replaced by the assignment of different values that will not be checked for the type of value. One way to enforce type checking is by using predicate operators to check values at the point in time of assignment to arrays. For example, using one or more of:

* numberp (expr)
* floatnump (expr)
* integerp (expr) 
* ratnump (expr)
* stringp (obj)
* listp (expr) 
* featurep (a, f)

and possibly others.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* A1 was declared as type fixnum */
(%i13)	A1[5,2]:3.14159;
(%o13)	3.14159

/* A2 was declared as type flonum */
(%i14)	A2[3,0]:7129;
(%o14)	7129

/* A1 which was declared as type fixnum assigned a string */
(%i15)	A1[4,1]:&quot;a string&quot;;
(%o15)	&quot;a string&quot;

/* A2 which was declared as type flonum assigned a math expression*/
(%i16)	A2[6,1]:3*x^2 + 4*x +10; 
(%o16)	3*x^2+4*x+10
&lt;/syntaxhighlight&gt;

There are other ways to assign values to an array. One way is to read the values from a comma separated (CSV) file  using the &lt;code&gt;'''read_array ()'''&lt;/code&gt; operator from the ''numericalio'' package.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i17) load(numericalio);
(%o17) &quot;/app/plugins/maxima/share/maxima/5.50.0/share/numericalio/numericalio.mac&quot;


&lt;/syntaxhighlight&gt;

Below are of the values of the CSV data file &lt;code&gt;tree_data_nh.csv&lt;/code&gt; :&lt;syntaxhighlight lang=&quot;text&quot;&gt;
1,118,30
1,484,58
1,664,87
1,1004,115
1,1231,120
1,1372,142
1,1582,145
2,118,33
2,484,69
2,664,111
2,1004,156
2,1231,172
2,1372,203
2,1582,203
3,118,30
3,484,51
3,664,75
3,1004,108
3,1231,115
3,1372,139
3,1582,140
4,118,32
4,484,62
4,664,112
4,1004,167
4,1231,179
4,1372,209
4,1582,214
5,118,30
5,484,49
5,664,81
5,1004,125
5,1231,142
5,1372,174
5,1582,177
&lt;/syntaxhighlight&gt;

Note that the following expression assumes that the CSV file is located in the Maxima working directory.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i18)	read_array(&quot;tree_data_nh.csv&quot;, A1, &quot;,&quot;); 
(%o18)	done

(%i19)	 listarray(A1);
(%o19)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,
         1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,
         2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75,3,1004,108,
         3,1231,115,3,1372,139,3,1582,140,4,118,32,4,484,62,4,664,112,
         4,1004,167,4,1231,179,4,1372,209,4,1582,214,5,118,30,5,484,49,
         5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177]
&lt;/syntaxhighlight&gt;
Below are of the values of the CSV data file &lt;code&gt;tree_data.csv&lt;/code&gt;  which has a header row, but is otherwise the same as &lt;code&gt;tree_data_nh.csv&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;text&quot;&gt;
&quot;Tree&quot;,&quot;age&quot;,&quot;circumference&quot;
1,118,30
1,484,58
1,664,87
1,1004,115
1,1231,120
1,1372,142
1,1582,145
2,118,33
2,484,69
2,664,111
2,1004,156
2,1231,172
2,1372,203
2,1582,203
3,118,30
3,484,51
3,664,75
3,1004,108
3,1231,115
3,1372,139
3,1582,140
4,118,32
4,484,62
4,664,112
4,1004,167
4,1231,179
4,1372,209
4,1582,214
5,118,30
5,484,49
5,664,81
5,1004,125
5,1231,142
5,1372,174
5,1582,177
&lt;/syntaxhighlight&gt;&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i20)	read_array(&quot;tree_data.csv&quot;, A2, &quot;,&quot;); 
(%o20)	done

(%i21) listarray(A2);
(%o21) [&quot;Tree&quot;,&quot;age&quot;,&quot;circumference&quot;,1,118,30,1,484,58,1,664,87,1,1004,
        115,1,1231,120,1,1372,142,1,1582,145,2,118,33,2,484,69,2,664,111,
        2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,
        3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
        4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,
        5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,
        5,1582,177]&lt;/syntaxhighlight&gt;The previous values of 0 and 0,0 as well as the assigned values of &lt;code&gt;A1&lt;/code&gt; and &lt;code&gt;A2&lt;/code&gt; have been replaced with the values from the CSV files.

The third array A3 can be used with values from the  dataset.csv file below:&lt;syntaxhighlight lang=&quot;text&quot;&gt;&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;
&quot;Smith&quot;,16753.00,&quot;UK&quot;,&quot;Qtr 3&quot;
&quot;Johnson&quot;,14808.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Williams&quot;,10644.00,&quot;UK&quot;,&quot;Qtr 2&quot;
&quot;Jones&quot;,1390.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Brown&quot;,4865.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Williams&quot;,12438.00,&quot;UK&quot;,&quot;Qtr 1&quot;
&quot;Johnson&quot;,9339.00,&quot;UK&quot;,&quot;Qtr 2&quot;
&quot;Smith&quot;,18919.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Jones&quot;,9213.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Jones&quot;,7433.00,&quot;UK&quot;,&quot;Qtr 1&quot;
&quot;Brown&quot;,3255.00,&quot;USA&quot;,&quot;Qtr 2&quot;
&quot;Williams&quot;,14867.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Williams&quot;,19302.00,&quot;UK&quot;,&quot;Qtr 4&quot;
&quot;Smith&quot;,9698.00,&quot;USA&quot;,&quot;Qtr 1&quot;&lt;/syntaxhighlight&gt;&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i22)	read_array(&quot;dataset.csv&quot;, A3, &quot;,&quot;); 
(%o22)	done

(%i23)	 listarray(A3);
(%o23)	[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;,
         &quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;,
         &quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;,
         &quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;,
         &quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;,
         &quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;,
         &quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;,
         &quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;,
         &quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]&lt;/syntaxhighlight&gt;

Values of the array can be referenced by indices as required for some purpose:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i24)	A3[0,0];
(%o24)	&quot;Last Name&quot;

(%i25)	A3[4,2];
(%o25)	&quot;USA&quot;
&lt;/syntaxhighlight&gt;
A row list object can be created using the &lt;code&gt;'''makelist ()'''&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i26)	row1A3: makelist(A3[0, j], j, 0, 3)$

(%i27)	row1A3;
(%o27)	[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;]

(%i28)	row1A3[1];
(%o28)	&quot;Last Name&quot;

(%i29)	row15A3: makelist(A3[14, j], j, 0, 3)$

(%i30)	row15A3;
(%o30)	[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]

(%i31)	row15A3[2];
(%o31)	9698.0
&lt;/syntaxhighlight&gt;
A list of the indices of the array can be created:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i32)	indices_A3 : arrayinfo(A3)[3];
(indices_A3)	[14,3]
&lt;/syntaxhighlight&gt;
The number of indices of array &lt;code&gt;A3&lt;/code&gt; can also be referenced using the &lt;code&gt;'''length (''')&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i33)	length(arrayinfo(A3)[3]);
(%o33)	2
&lt;/syntaxhighlight&gt;The number of values of the array &lt;code&gt;A3&lt;/code&gt; can be returned using the '''&lt;code&gt;length ()&lt;/code&gt;''' operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i34)	length(listarray(A3));
(%o34)	60
&lt;/syntaxhighlight&gt;
The values of the array &lt;code&gt;A3&lt;/code&gt; can be printed as output using the list of values with a loop programming expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i35)	for i:1 thru length (listarray(A3)) do 
            print('A3[i] ,&quot; = &quot;,  listarray(A3)[i])$

A3[1]&quot; = &quot;&quot;Last Name&quot;
A3[2]&quot; = &quot;&quot;Sales&quot;
A3[3]&quot; = &quot;&quot;County&quot;
A3[4]&quot; = &quot;&quot;Quarter&quot;
A3[5]&quot; = &quot;&quot;Smith&quot;
A3[6]&quot; = &quot;16753.0
A3[7]&quot; = &quot;&quot;UK&quot;
A3[8]&quot; = &quot;&quot;Qtr 3&quot;
A3[9]&quot; = &quot;&quot;Johnson&quot;
A3[10]&quot; = &quot;14808.0
A3[11]&quot; = &quot;&quot;USA&quot;
A3[12]&quot; = &quot;&quot;Qtr 4&quot;
A3[13]&quot; = &quot;&quot;Williams&quot;
A3[14]&quot; = &quot;10644.0
A3[15]&quot; = &quot;&quot;UK&quot;
A3[16]&quot; = &quot;&quot;Qtr 2&quot;
A3[17]&quot; = &quot;&quot;Jones&quot;
A3[18]&quot; = &quot;1390.0
A3[19]&quot; = &quot;&quot;USA&quot;
A3[20]&quot; = &quot;&quot;Qtr 3&quot;
A3[21]&quot; = &quot;&quot;Brown&quot;
A3[22]&quot; = &quot;4865.0
A3[23]&quot; = &quot;&quot;USA&quot;
A3[24]&quot; = &quot;&quot;Qtr 4&quot;
A3[25]&quot; = &quot;&quot;Williams&quot;
A3[26]&quot; = &quot;12438.0
A3[27]&quot; = &quot;&quot;UK&quot;
A3[28]&quot; = &quot;&quot;Qtr 1&quot;
A3[29]&quot; = &quot;&quot;Johnson&quot;
A3[30]&quot; = &quot;9339.0
A3[31]&quot; = &quot;&quot;UK&quot;
A3[32]&quot; = &quot;&quot;Qtr 2&quot;
A3[33]&quot; = &quot;&quot;Smith&quot;
A3[34]&quot; = &quot;18919.0
A3[35]&quot; = &quot;&quot;USA&quot;
A3[36]&quot; = &quot;&quot;Qtr 3&quot;
A3[37]&quot; = &quot;&quot;Jones&quot;
A3[38]&quot; = &quot;9213.0
A3[39]&quot; = &quot;&quot;USA&quot;
A3[40]&quot; = &quot;&quot;Qtr 4&quot;
A3[41]&quot; = &quot;&quot;Jones&quot;
A3[42]&quot; = &quot;7433.0
A3[43]&quot; = &quot;&quot;UK&quot;
A3[44]&quot; = &quot;&quot;Qtr 1&quot;
A3[45]&quot; = &quot;&quot;Brown&quot;
A3[46]&quot; = &quot;3255.0
A3[47]&quot; = &quot;&quot;USA&quot;
A3[48]&quot; = &quot;&quot;Qtr 2&quot;
A3[49]&quot; = &quot;&quot;Williams&quot;
A3[50]&quot; = &quot;14867.0
A3[51]&quot; = &quot;&quot;USA&quot;
A3[52]&quot; = &quot;&quot;Qtr 3&quot;
A3[53]&quot; = &quot;&quot;Williams&quot;
A3[54]&quot; = &quot;19302.0
A3[55]&quot; = &quot;&quot;UK&quot;
A3[56]&quot; = &quot;&quot;Qtr 4&quot;
A3[57]&quot; = &quot;&quot;Smith&quot;
A3[58]&quot; = &quot;9698.0
A3[59]&quot; = &quot;&quot;USA&quot;
A3[60]&quot; = &quot;&quot;Qtr 1&quot;
&lt;/syntaxhighlight&gt;

Maxima treats declared arrays as fixed-sized, and individual values are accessed via indices. There is no built-in &quot;row&quot; object — rows must be extracted manually using the &lt;code&gt;'''makelist ()'''&lt;/code&gt; operator or by looping through values of an array.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i36)	array(rowsA3,15);
(%o36)	rowsA3

(%i37)	arrayinfo(rowsA3);
(%o37)	[declared,1,[15]]

(%i38)	for i:0 thru 14 do
	       (rowsA3[i+1]:makelist(A3[i, j], j, 0, 3),
	        print(&quot;Row &quot;,i+1,&quot;: &quot;,rowsA3[i+1]))$;

&quot;Row &quot;1&quot;: &quot;[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;]
&quot;Row &quot;2&quot;: &quot;[&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;3&quot;: &quot;[&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;4&quot;: &quot;[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;5&quot;: &quot;[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;6&quot;: &quot;[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;7&quot;: &quot;[&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;8&quot;: &quot;[&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;9&quot;: &quot;[&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;10&quot;: &quot;[&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;11&quot;: &quot;[&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;12&quot;: &quot;[&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;13&quot;: &quot;[&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;14&quot;: &quot;[&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;15&quot;: &quot;[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]
&lt;/syntaxhighlight&gt;
Maxima does not have a built-in function like &lt;code&gt;delete&lt;/code&gt; or &lt;code&gt;unset&lt;/code&gt; for removing individual values from arrays using indices. Existing values of an array can be changed by assignment however:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i52)	rowsA3[1]:[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;]$

(%i53)	for i:1 thru 15 do
	    (newRowsA3[i]:rowsA3[i],
	    print(&quot;Row &quot;,i,&quot;: &quot;,newRowsA3[i]))$;

&quot;Row &quot;1&quot;: &quot;[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;2&quot;: &quot;[&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;3&quot;: &quot;[&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;4&quot;: &quot;[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;5&quot;: &quot;[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;6&quot;: &quot;[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;7&quot;: &quot;[&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;8&quot;: &quot;[&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;9&quot;: &quot;[&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;10&quot;: &quot;[&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;11&quot;: &quot;[&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;12&quot;: &quot;[&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;13&quot;: &quot;[&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;14&quot;: &quot;[&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;15&quot;: &quot;[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]&lt;/syntaxhighlight&gt;
The &lt;code&gt;'''arrayapply ()'''&lt;/code&gt; operator can be used a follows to reference values of a declared array:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i39)	arrayapply(rowsA3,[5]);
(%o39)	[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]

(%i40)	arrayapply(A3, [5,1]);
(%o40)	4865.0
&lt;/syntaxhighlight&gt;The operator &lt;code&gt;'''fillarray (A, B)'''&lt;/code&gt; assigns values to array &lt;code&gt;A&lt;/code&gt; from &lt;code&gt;B&lt;/code&gt;, which can be a list or an array.The dimensions of the arrays &lt;code&gt;A&lt;/code&gt; and &lt;code&gt;B&lt;/code&gt; may not be the same. In that case, array &lt;code&gt;A&lt;/code&gt; is filled in &quot;row-major&quot; order. There may not be enough values in &lt;code&gt;B&lt;/code&gt; compared to &lt;code&gt;A&lt;/code&gt;. In that case, the last value of &lt;code&gt;B&lt;/code&gt; is used to for the remaining values of &lt;code&gt;A&lt;/code&gt;. There may be too many values of &lt;code&gt;B&lt;/code&gt; compared to array &lt;code&gt;A&lt;/code&gt;. In that case, the remaining values of &lt;code&gt;B&lt;/code&gt; once &lt;code&gt;A&lt;/code&gt; is filled are not used. The return value of &lt;code&gt;'''fillarray ()'''&lt;/code&gt; is not the filled array &lt;code&gt;A&lt;/code&gt;, but it is the first argument.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* Create a declared array B of type fixnum */
(%i41)	array (B, fixnum, 9);
(%o41)	B

/* list the values of array B */
(%i42)	listarray (B);
(%o42)	[0,0,0,0,0,0,0,0,0,0]

/* fill array B with the values of the list */
(%i43)	fillarray (B, [0,1, 2, 3, 4, 5, 6, 7, 8, 9.0]);
(%o43)	B

/* list the values of array B */
(%i44)	listarray (B);
(%o44)	[0,1,2,3,4,5,6,7,8,9.0]

/* fill array B with the value 1.0 */
(%i45)	fillarray (B, [1.0]);
(%o45)	B

/* list the values of array B */
(%i46)	listarray (B);
(%o46)	[1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0]

/* fill array B with the first 9 values of the list */
(%i47)	fillarray (B, [0,1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12]);
(%o47)	B

/* list the values of array B */
(%i48)	listarray (B);
(%o48)	[0,1,2,3,4,5,6,7,8,9]

/* Create a declared array D of no type */
(%i49)	array (D, 9);
(%o49)	D

/* list the values of array D */
(%i50)	listarray (D);
(%o50)	[#####,#####,#####,#####,#####,#####,#####,#####,#####,#####]

/* fill array D with the value 1.0 */ 
(%i51)	fillarray (D, [1.0]);
(%o51)	D

/* list the values of array D */
(%i52)	listarray (D);
(%o52)	[1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0]

/* Create a declared array E of no type */
(%i53)	array (E, 15);
(%o53)	E

/* fill array E with the values from the newRowsA3 list */ 
(%i54)	fillarray (E, listarray (newRowsA3));
(%o54)	E

/* list the values of array D */
(%i55)	listarray (E);
(%o55)	[[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;],
         [&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;],
         [&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]]

/* remove array E */
(%i56)	remarray (E);
(%o56)	[E]

/*  D is no longer an array */
(%i57)	arrayinfo (E);
arrayinfo: E is not an array.

 -- an error. To debug this try: debugmode(true);&lt;/syntaxhighlight&gt;

If you need to keep the array but remove only one value, you must reconstruct it without that value. The operator &lt;code&gt;'''remarray ()'''&lt;/code&gt; is the typical way to completely remove an array.

The &lt;code&gt;'''rearray (A, dim&lt;sub&gt;1&lt;/sub&gt;, dim&lt;sub&gt;2&lt;/sub&gt; ,…, dim&lt;sub&gt;n&lt;/sub&gt;)'''&lt;/code&gt; operator is used to change the dimensions of an array. The changed array will be filled with the elements of the existing array in row-major order. If the existing array has one or more smaller dimensions, the additional dimension values of the changed array are assigned with a value that depends on the type of the array. If the existing array has one or more larger dimensions, the deficient dimension values of the changed array are lost. The type of the array cannot be changed using this operator. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* list with the values of array B */
(%i58)	listarray(B);
(%o58)	[0,1,2,3,4,5,6,7,8,9]

/* list with information about array B */
(%i59)	arrayinfo(B);
(%o59)	[complete,1,[9]]

/* increase the dimension of array B */
(%i60)	rearray (B, 12);
(%o60)	\#\{Lisp array \[13\]\}

/* list with information about array B with increased dimension */
(%i61)	arrayinfo(B);
(%o61)	[complete,1,[12]]

/* list with the values of array B */
(%i62)	listarray(B);
(%o62)	[0,1,2,3,4,5,6,7,8,9,0,0,0]

/* decrease the dimension of array B */
(%i63)	rearray (B, 6);
(%o63)	\#\{Lisp array \[7\]\}

/* list with information about array B with decreased dimension */
(%i64)	arrayinfo(B);
(%o64)	[complete,1,[6]]

/* list with the values of array B */
(%i65)	listarray(B);
(%o65)	[0,1,2,3,4,5,6]


&lt;/syntaxhighlight&gt;

The &lt;code&gt;'''arraymake ()'''&lt;/code&gt; operator returns a value that is an array reference without evaluation. This operator, in spite of the name, does not &quot;make&quot; an array. It returns this reference as a value whether or not an array exists as an object:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* the arraymake operator returns the unevaluated reference to A */
(%i66)	arraymake (A, [i,j]);
(%o66)	A[i,j]

/* however array A is not an array object*/
(%i67)	arrayinfo (A);
arrayinfo: A is not an array.
 -- an error. To debug this try: debugmode(true);

/* Maxima sees A[j,k] as a reference to an undefined memoizing function */
(%i68)	op (arraymake (A, [i,j]));
(%o68)	A
&lt;/syntaxhighlight&gt;
However, from a practical point of view, this operator is used with existing arrays:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i69)	listarray (newRowsA3);
(%o69)	[[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;],
         [&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;],
         [&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]]

(%i70)	arraymake (newRowsA3, [4]);
(%o70)	newRowsA3[4]

(%i71)	''%;
(%o71)	[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]

(%i72)	arraymake (newRowsA3, [i]);
(%o72)	newRowsA3[i]

(%i73)	''%, i = 6;
(%o73)	[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]

&lt;/syntaxhighlight&gt;
The operator &lt;code&gt;arraymake (x, [i])&lt;/code&gt; constructs the expression &lt;code&gt;x[i]&lt;/code&gt;, but does not evaluate it. 

The operator &lt;code&gt;'''subvar'''&lt;/code&gt; &lt;code&gt;'''(x, i)'''&lt;/code&gt; evaluates the indexed expression &lt;code&gt;x[i]&lt;/code&gt;, and evaluates its arguments. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i74)	listarray(B);
(%o174)	[0,1,2,3,4,5,6]

(%i75)	x : B;
(x)	B

(%i76)	i : 4;
(i)	4

(%i77)	subvar (x, i);
(%o77)	4
&lt;/syntaxhighlight&gt;
The operator &lt;code&gt;'''subvarp (expr)'''&lt;/code&gt; returns a value of &lt;code&gt;true&lt;/code&gt; if &lt;code&gt;expr&lt;/code&gt; is a indexed identifier, and &lt;code&gt;false&lt;/code&gt; otherwise. This operator evaluates the argument &lt;code&gt;expr&lt;/code&gt;.  &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;

(%i78)	z[p];
(%o78)	z[p]

(%i79)	subvarp (z[p]);
(%o79)	true

(%i80)	x[i];
(%o80)	4

(%i81)	subvar (x, i)
(%o81)	4

(%i82)	w : z[p];
(w)	z[p]

(%i83)	subvarp (w);
(%o83)	true


&lt;/syntaxhighlight&gt;
The expression &lt;code&gt;'''arrays'''&lt;/code&gt;  returns a list of allocated arrays: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i84)	arrays;
(%o84)	[A3,A2,A1,rowsA3,newRowsA3,B,D]&lt;/syntaxhighlight&gt;

The operator &lt;code&gt;'''arraysetapply (A, [i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2,&lt;/sub&gt;…,i&lt;sub&gt;n&lt;/sub&gt;], x)'''&lt;/code&gt; assigns the value of expression &lt;code&gt;x&lt;/code&gt; to &lt;code&gt;A&lt;/code&gt;&lt;code&gt;[i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2&lt;/sub&gt;,…,i&lt;sub&gt;n&lt;/sub&gt;]&lt;/code&gt;, where &lt;code&gt;A&lt;/code&gt; is an array and &lt;code&gt;i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2&lt;/sub&gt;,…,i&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt; are integers.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i85)	arraysetapply (newRowsA3, [8], [&quot;George&quot;,20818.0,&quot;UK&quot;,&quot;Qtr 4&quot;]);
(%o85)	[&quot;George&quot;,20818.0,&quot;UK&quot;,&quot;Qtr 4&quot;]&lt;/syntaxhighlight&gt;
=== Undeclared Arrays ===

Maxima declared arrays and Maxima undeclared arrays will likely be the two types of data structures used by most users. Maxima undeclared arrays are also referred to as '''''hashed arrays'''''. For both of these two array types, memory allocation and structure occur &quot;behind the curtain&quot; of the Maxima user level, and &quot;the man behind the curtain&quot; is Lisp.

Of these two types, hashed arrays are the most flexible from the user point of view, all other factors being equal:

* The indices allowed for hashed arrays can be expressions,
* The dimensions of a hashed array are dynamic and not fixed, and
* Hashed arrays are relatively easier to create.
In fact, hashed arrays can be somewhat too easy to create. In the examples of the previous section involving declared arrays, identifiers were used as names for arrays. here is the list of allocated arrays:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i86)	arrays;
(%o86)	[A3,A2,A1,rowsA3,newRowsA3,B,D,my_list,h]&lt;/syntaxhighlight&gt;The array information for array &lt;code&gt;newRowsA3&lt;/code&gt; is shown below:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i87)	arrayinfo(newRowsA3);
(%o87)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15]]
&lt;/syntaxhighlight&gt;So the array &lt;code&gt;newRowsA3&lt;/code&gt; is not a declared array. it was created as part of a loop programming expression repeated below:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i53)	for i : 1 thru 15 do
	    (newRowsA3[i] : rowsA3[i],
	    print(&quot;Row &quot;,i,&quot;: &quot;,newRowsA3[i]))$;&lt;/syntaxhighlight&gt;When the first loop block was executed with i : 1, the assignment expression:

&lt;code&gt;newRowsA3[i] : rowsA3[i]&lt;/code&gt;

created a hashed array named  &lt;code&gt;newRowsA3&lt;/code&gt; and assigned &lt;code&gt;newRowsA3[1]&lt;/code&gt; the value of &lt;code&gt;rowsA3[1]&lt;/code&gt; automatically without any declaration. After that the hashed array dynamically allocated memory for values of the loop identifier i from 2 through 15 with each successive pass in the loop expression. Since hashed arrays are undeclared, and their associated dimensions are not fixed, but rather increase dynamically, expressions can be added to hashed arrays without creating a error message. These added values can be can be any valid Maxima expression, and the value of the indices used are not limited to zero and nonzero integers:  &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i88)	newRowsA3[16] :  [&quot;Maisel&quot;,12785.0,&quot;USA&quot;,&quot;Qtr 2&quot;];
(newRowsA3[16])	[&quot;Maisel&quot;,12785.0,&quot;USA&quot;,&quot;Qtr 2&quot;]

(%i89	arrayinfo(newRowsA3);
(%o89)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15],[16]]

(%i90)	newRowsA3[z]  : 2*sin(y) ^2 + 3*sin(x)^3;
(newRowsA3[z])	2*sin(y)^2+3*sin(B)^3

(%i91)	arrayinfo(newRowsA3);
(%o91)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15],[16],[z]]
&lt;/syntaxhighlight&gt;So one point to glean from this example is that all that is required to create a hashed array is an assignment expression to an indexed identifier, but it does require this assignment. If for some reason, a declared array is intended, but not declared using the &lt;code&gt;array&lt;/code&gt; operator (as in the instance of &lt;code&gt;newRowsA3&lt;/code&gt;), then a hashed array will be created at the first assignment of an expression to an indexed identifier.

This issue can also occur in cases where reference to a list value is intended, but the list has not been created. Lists are one-dimensional objects by definition. A reference using an identifier with a single index intended to be a list with no list existing named by that identifier, can inadvertently create a hashed array.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i91)	Alist[2] : 2*sin(y) ^2 + 3*sin(s)^3;
(Alist[2])	2*sin(y)^2+3*sin(s)^3

(%i92)	listp(Alist);
(%o92)	false

(%i93)	arrayinfo(Alist);
(%o93)	[hashed,1,[2]]
&lt;/syntaxhighlight&gt;The identifier &lt;code&gt;Alist&lt;/code&gt; is a name for a hashed array and not a list.

However, hashed arrays, like declared arrays can, be multi-dimensional: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i94)	a_hashed_array [j,k,l] : [12,s^(1/3), %i];
(%o94)	[12,s^(1/3),%i]

(%i95)	arrayinfo(a_hashed_array);
(%o95)	[hashed,3,[j,k,l]]
&lt;/syntaxhighlight&gt;The &lt;code&gt;array&lt;/code&gt; operator can be used to transform a hashed array into a declared array:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i96)	another_hashed_array[ 0, 2, 3] : 55;
(%o96)	55

(%i97)	array (another_hashed_array, 2, 4, 5);
(%o97)	another_hashed_array

(%i98)	arrayinfo(another_hashed_array);
(%o98)	[declared,3,[2,4,5]]
&lt;/syntaxhighlight&gt;From the user point of view, hashed arrays and declared arrays typically can be used for the same purpose. If dynamic dimensions or index expression flexibility are factors, then hashed arrays are likely to be a better choice. Many of the operators that can use declared arrays as arguments, may also be used with hashed arrays.

However, it should be noted at this point, that merely using a indexed identifier alone without an assignment, will not create a hashed array. Instead, Maxima interprets an expression so composed as an identifier for an undefined memoizing function, which is the topic of the next section.

==== Memoizing Functions ====
Assignment using an indexed identifier implicitly creates an undeclared (hashed) array. However, entering an expression that is an unassigned indexed identifier, from the point of view of Maxima, creates the identifier of a &quot;memoizing&quot; function. Memoizing functions are technically not an array topic, as these functions fall under the category of function definition. These functions have one foot in the function category and the other foot in the array category.

Memoizing functions are defined in a manner similar to other user-defined functions, for example:

&lt;code&gt;f(x, y, z) := x^2 + y^2 + z^2;&lt;/code&gt;

But instead of the arguments being enclosed in parentheses, they are enclosed using brackets:

&lt;code&gt;f[x, y, z] := x^2 + y^2 + z^2;&lt;/code&gt;

However, memoizing functions may be referred to as ''array functions,'' and it is the case that these functions from the point of view of aggregate data structures are hashed arrays. So these are mentioned and exemplified here for that reason:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* reference an indexed identifier h without assignment */
(%i99)	h[x];
(%o99)	h[x]

/* check identifier h as an array */
(%i100)	arrayinfo (h);
arrayinfo: h is not an array.
  -- an error. To debug this try: debugmode(true);
  
/* check identifier h as a function */
(%i101)	op(h[x]);
(%o101)	h

/* define h[x] as a function */
(%i102)	h[x] := 5*x^3 + sin(x);
(h[x])	h[x]:=5*x^3+sin(x)

/* check identifier h[x] as a function */
(%i103)	op(h[x]);
(%o103)	&quot;+&quot;

/* check identifier h as an array */
(%i104)	arrayinfo (h);
(%o104)	[hashed,1,[x]]

/* check the value of identifier h[x] */
(%i105)	h[x];
(%o105)	sin(x)+5*x^3

/* evaluate identifier h[x] with the argument 3*%pi */
(%i106)	h[3*%pi];
(%o106)	135*%pi^3

/* list the values of identifier h as an array */
(%i107)	listarray(h);
(%o107)	[135*%pi^3,sin(x)+5*x^3]

/* check identifier h as an array */
(%i108)	arrayinfo (h);
(%o108)	[hashed,1,[3*%pi],[x]]&lt;/syntaxhighlight&gt;A defined memoizing function stores its value the ''first time'' it is referenced with arguments, and returns the stored value, without evaluation, when the same arguments are used with that function subsequently. The stored value is &quot;frozen&quot; after the initial evaluation. Thus, it behaves like a hashed array. The arguments of a memoizing function also serve as indices of the associated hashed array.

=== Lisp Arrays ===
Lisp arrays are created using the &lt;code&gt;make_array (type, dim&lt;sub&gt;1&lt;/sub&gt;, dim&lt;sub&gt;2&lt;/sub&gt;, …, dim&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt; operator. Perhaps a better name for this operator would be &lt;code&gt;make_lisp_array ()&lt;/code&gt;, which admittedly is a longer name.

This operator creates and has a return value of a Lisp array. The array type may be &lt;code&gt;any&lt;/code&gt;, &lt;code&gt;flonum&lt;/code&gt;, &lt;code&gt;fixnum&lt;/code&gt;, or  &lt;code&gt;hashed&lt;/code&gt; . The &lt;code&gt;functional&lt;/code&gt; type referred to in the Maxima Manual appears to have been deprecated, and may result in an error message if used. There can be ''n'' indices, and where the associated indices can be a value from ''0'' to ''dim&lt;sub&gt;i&lt;/sub&gt; -1'', and ''i'' can have a value of one of 1 to n inclusive.

This operator can be used as an alternative to the &lt;code&gt;array ()&lt;/code&gt; operator. The advantage of using &lt;code&gt;make_array()&lt;/code&gt; is that the return value of &lt;code&gt;make_array()&lt;/code&gt; ''does not have a name''. Once the Maxima identifier that is assigned to the array return value is no longer assigned, the array memory allocation is released, and the allocated memory can be garbage collected. What it is being referred to that Lisp arrays created using &lt;code&gt;make_array()&lt;/code&gt; do not have names? &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* create a undeclared Maxima hashed array */
(%i109)	arrayA1 [1] : 55;  
(%o109)	55

/* check the information about this undeclared Maxima hashed array */
(%i110)	arrayinfo (arrayA1);
(%o110)	[hashed,1,[1]]

/* check the value of this undeclared Maxima hashed array */
(%i111)	arrayA1;
(%o111)	arrayA1     /* the name */

/* create a Lisp hashed array */
(%i112)	arrayA2 : make_array (hashed);
(arrayA2)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 1 {1202987DC3}&gt;&quot;

/* check the information about this Lisp hashed array */
(%i113)	arrayinfo (arrayA2);
(%o113)	[hash_table,1]

/* check the value of this Lisp hashed array */
(%i114)	arrayA2;
(%o114)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 1 {1202987DC3}&gt;&quot; /* no name */

(%i115)	listarray (arrayA2);
(%o115)	[]                     /* this hashed array is empty */
&lt;/syntaxhighlight&gt;So Lisp arrays do not have a name as a value. So, Maxima identifiers assigned to a Lisp array have no name for the array as a value. These identifiers have the reference to the array itself as a value, Lisp hashed arrays created using &lt;code&gt;make_array()&lt;/code&gt; with the hashed type specified, do not use dimensions. Lisp hashed arrays are often referred to as '''''hashed tables''''', and their indices are called '''''keys'''''.

An example of a Lisp array with the type &lt;code&gt;any&lt;/code&gt; follows:

&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* make a Lisp 3 by 4 array of type any */
(%i116)	arrayA3 : make_array (any, 3,4);
(arrayA3)	\#\{Lisp array \[3\\,4\]\}

(%i117)	arrayinfo (arrayA3);
(%o117)	[declared,2,[2,3]]

(%i118)	listarray(arrayA3);
(%o118)	[false,false,false,false,false,false,false,false,false,false,false,false]

(%i119)	arrayA3[1,1] : &quot;a string&quot; ;
(%o119)	&quot;a string&quot;

(%i120)	listarray(arrayA3);
(%o120)	[false,false,false,false,false,&quot;a string&quot;,
         false,false,false,false,false,false]
&lt;/syntaxhighlight&gt;Contrary to statements made in some sources, type checking is is not accomplished automatically, and will not cause Maxima to return an error message, as the Lisp array with the type &lt;code&gt;fixnum&lt;/code&gt; which follows is an exemplifies:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i121)	arrayA4 : make_array (fixnum, 3,4);
(arrayA4)	\#\{Lisp array \[3\\,4\]\}

(%i122)	arrayinfo (arrayA4);
(%o122)	[declared,2,[2,3]]

(%i123)	listarray (arrayA4);
(%o123)	[0,0,0,0,0,0,0,0,0,0,0,0]

(%i124)	arrayA4[0,2] : 3.14159;
(%o124)	3.14159

(%i125)	arrayA4[0,0] : &quot;a string&quot;;
(%o125)	&quot;a string&quot;

/* value types not checked and no error message */
(%i126)	listarray (arrayA4);
(%o126)	[&quot;a string&quot;,0,3.14159,0,0,0,0,0,0,0,0,0]&lt;/syntaxhighlight&gt;As was the case with declared arrays, there is no type checking and no error messages associated with assigned values of the array based on the declared type. The declared array type simply determines initial fill values, if any.

Hashed arrays and Lisp hash tables have an operator in common:

&lt;code&gt;has_key&lt;/code&gt; &lt;code&gt;(A, L)&lt;/code&gt;

This expression has a a value of &lt;code&gt;true&lt;/code&gt;, if the hashed array or Lisp hash table &lt;code&gt;A&lt;/code&gt; has the key (index) or keys (indices) of the list object &lt;code&gt;L&lt;/code&gt;.  Otherwise the expression has a value of &lt;code&gt;false&lt;/code&gt;.

The array &lt;code&gt;A&lt;/code&gt; must be a hashed (undeclared) array, a Lisp hash table value returned by the &lt;code&gt;make_array&lt;/code&gt; operator, or created as an undeclared array with &lt;code&gt;use_fast_arrays&lt;/code&gt; assigned the value &lt;code&gt;true&lt;/code&gt;.

If array A has only one key, that key must be the value of a list.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i127)	arrayinfo (newRowsA3);
(%o127)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],
                  [11],[12],[13],[14],[15],[16],[z]]

(%i128)	has_key (newRowsA3, [z]);
(%o128)	true

(%i129)	has_key (newRowsA3, [3]);
(%o129)	true

(%i130)	has_key(newRowsA3, [0]);
(%o130)	false

(%i131)	lisp_Array_1 [x];
(%o131)	3*x^2

(%i132)	arrayinfo (lisp_Array_1);
(%o132)	[hash_table,1,x]

(%i133)	has_key (lisp_Array_1, [x]);
(%o133)	true

(%i134)	has_key (lisp_Array_1, [y]);
(%o134)	false
&lt;/syntaxhighlight&gt;

=== Arrays and Features ===
Maxima arrays can be assigned features in a manner similar to other identifiers:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i135)	array (a6,fixnum, 5);
(%o135)	a6

(%i136)	arrayinfo (a6);
(%o136)	[complete,1,[5]]

(%i137)	declare (a6, [real, noninteger]);
(%o137)	done

(%i138)	featurep (a6, real);
(%o138)	true

(%i139)	featurep (a6, noninteger);
(%o139)	true

(%i140)	a6[2] : 2;
(a6[2])	2

(%i141)	listarray (a6);
(%o141)	[0,0,2,0,0,0]
&lt;/syntaxhighlight&gt;However, once again, declaring an array to have one or more features does not result in type checking of values assigned to an array. Perhaps the best way to ensure types of values assigned to arrays is type-checking of expressions using predicate operators prior to assignment to arrays. 

=== Array Memory Storage Considerations ===

The following from the Maxima Manual&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.5.1 - Functions and Variables for Arrays |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Functions-and-Variables-for-Arrays}}&lt;/ref&gt; is quoted here for the purpose of establishing the context of that which follows:&lt;blockquote&gt;''&quot;Option variable: use_fast_arrays ¶''

''Default value: false''

''When use_fast_arrays is true, arrays declared by array are values instead of properties, and undeclared arrays (hashed arrays) are implemented as Lisp hashed arrays.''

''When use_fast_arrays is false, arrays declared by array are properties, and undeclared arrays are implemented with Maxima’s own hashed array implementation.''

''Note that the code use_fast_arrays switches to is not necessarily faster than the default one; Arrays created by make_array are not affected by use_fast_arrays.&quot;''&lt;/blockquote&gt;
This Maxima Manual entry requires some elaboration in order to have a sufficient understanding of the effect of the &lt;code&gt;'''use_fast_arrays'''&lt;/code&gt; &quot;flag&quot; – referred to as an &quot;Option Variable&quot; in the above quotation.

The first point to note is that the default value of this flag is &lt;code&gt;false&lt;/code&gt;. So, if users take no action to assign this flag to the value &lt;code&gt;true&lt;/code&gt;, then declared arrays created using the &lt;code&gt;array()&lt;/code&gt; operator  are treated as ''properties'' bound to a symbol, and behave in the manner previously described. Likewise undeclared arrays are a Maxima array implementation, and behave as legacy property hash tables, and these also behave as previously described.

If action is taken to enter an expression that assigns the value &lt;code&gt;true&lt;/code&gt; to this flag, then Maxima treat arrays as standard Lisp ''values'' rather than object properties:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i142)	use_fast_arrays;
(%o142)	false

(%i143)	array (A1,fixnum, 10);
(%o143)	A1

(%i144)	arrayinfo (A1);
(%o144)	[complete,1,[10]]

(%i145)	H1[1] : 1729;
(H1[1])	1729

(%i146)	arrayinfo (H1);
(%o146)	[hashed,1,[1]]

(%i147)	use_fast_arrays : true;
(use_fast_arrays)	true

(%i148)	array (A2, fixnum, 10);
(%o148)	\#\{Lisp array \[11\]\}

(%i149)	A2;
(%o149)	\#\{Lisp array \[11\]\}

(%i150)	H2[1] : 1729;
(H2[1])	1729

(%i151)	H2;
(%o151)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 2 {1203AD15A3}&gt;&quot;

(%i152)	arrayinfo (H2);
(%o152)	[hash_table,1,1]
&lt;/syntaxhighlight&gt; The &lt;code&gt;use_fast_arrays&lt;/code&gt; flag has no effect on arrays created using the &lt;code&gt;make_array ()&lt;/code&gt; operator.

Note the following:

* Assigning &lt;code&gt;use_fast_arrays&lt;/code&gt; &lt;code&gt;: true&lt;/code&gt; does not speed up execution for all operations. It primarily optimizes memory footprint by minimizing cell allocations.  The main benefit is optimization of memory footprints and structural representation inside Lisp.
* If compiling Maxima expressions to native Lisp using the &lt;code&gt;translate&lt;/code&gt; &lt;code&gt;()&lt;/code&gt; operator, pair this flag with &lt;code&gt;translate_fast_arrays&lt;/code&gt; &lt;code&gt;: true&lt;/code&gt;. This flag instructs the translator to compile arrays as value-based.

=== Structures ===
Structures, although not an array data type is an aggregation data type.  By &quot;aggregation&quot; it is meant a data type that references other data types by reference to a name and some method of accessing individual values of instances of that aggregation by means of indices used to reference values individually.

Thus, as has been previously described for example lists, hashed arrays, Lisp arrays, and declared arrays are all aggregation data types with syntactical means to refer to individual values of a named aggregation instance by way of indices, which are sometimes also referred to as subscripts or keys.

As examples:

* An existing '''list''' named &lt;code&gt;L1&lt;/code&gt; has values that can be accessed as &lt;code&gt;L1[1]&lt;/code&gt;, &lt;code&gt;L[2]&lt;/code&gt;, &lt;code&gt;L[3]&lt;/code&gt;, and so forth
* An existing '''hashed array''' with two indices (&quot;2D&quot;) named &lt;code&gt;ha&lt;/code&gt; has values that can accessed as &lt;code&gt;ha[1,1&lt;/code&gt;], &lt;code&gt;ha[1,2]&lt;/code&gt;,..., &lt;code&gt;ha[2,1]&lt;/code&gt;, &lt;code&gt;ha[2,2]&lt;/code&gt;, and  so forth.
* An existing '''declared array''' with three indices (&quot;3D&quot;) named &lt;code&gt;da&lt;/code&gt; has values that can be accessed as &lt;code&gt;da[1,1,1]&lt;/code&gt;, &lt;code&gt;da[1,1,2]&lt;/code&gt;,...,&lt;code&gt;da [2,1,1]&lt;/code&gt;, ..., &lt;code&gt;da[3,1,1]&lt;/code&gt;, and so forth.

What makes the Maxima structure data type different from these array data types is the form of definition used and the means of accessing values of an instance of this type of aggregation. The Maxima structure data type seems to be the closest type of data that resembles an object in some other general-purpose programming languages.

The structure type of data allows the creation of named entities with attributes, and named instances of those entities and the assignment of values to those attributes. Thus the Maxima structure data type is used to define custom, named composite data types that group related fields together under a single identifier. Structures enhance code organization and readability, especially when modeling real-world entities in symbolic computations. They are useful for managing complex data in programs involving algebraic manipulations, simulations, or data modeling.  

Structures are created using the &lt;code&gt;defstruct&lt;/code&gt; operator, which defines a template with named attributes. Once defined, instances of the structure are created using the &lt;code&gt;new&lt;/code&gt; operator, and attributes are accessed via the &lt;code&gt;@&lt;/code&gt; operator. 

So in the interest of taking advantage of this information, consider a well-defined set of people. The people of this set may have many diverse attributes that might be of interest - name, age ,and city of residence as examples. A class of people of the set of interest with these attributes can be defined as follows: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i153)	defstruct (person (name, age, city));
(%o153)	[person(name,age,city)]

(%i54) structures;
(%o154)                      [person(name, age, city)]

(%i155)	p : new (person (&quot;Alice&quot;, 30, &quot;New York&quot;));
(p)	person(name=&quot;Alice&quot;,age=30,city=&quot;New York&quot;)

(%i156)	p@name;
(%o156)	&quot;Alice&quot;

(%i157)	p@city;
(%o157)	&quot;New York&quot;

(%i158)	kill(p@city);
(%o158)	done

/* If the attribute a in x has not been assigned a value, or the value
   has been &quot;killed,&quot; then x@a evaluates to itself */

(%i159)	p@city;
(%o159)	p@city

(%i160)	p;
(%o160)	person(name=&quot;Alice&quot;,age=30,city)

(%i161)	p@city : &quot;Rochester&quot;;
(%o161)	&quot;Rochester&quot;

(%i162)	p;
(%o162)	person(name=&quot;Alice&quot;,age=30,city=&quot;Rochester&quot;)

(%i163) defstruct (sales(LastName, Sales , Country , Quarter) );
(%o163)             [sales(LastName, Sales, Country, Quarter)]

(%i164) structures;
(%o164) [person(name, age, city), sales(LastName, Sales, Country, Quarter)]

(%i165) s : new (sales (&quot;Smith&quot;,16753.00,&quot;UK&quot;,&quot;Qtr 3&quot;));
(%o165) sales(LastName=Smith, Sales=16753.0, Country=UK, Quarter=Qtr 3)

(%i166) s@Sales;
(%o166)                              16753.0

(%i167) s@Sales : 17375.0;
(%o167)                              17375.0

(%i168) s;
(%o168) sales(LastName=Smith, Sales=17375.0, Country=UK, Quarter=Qtr 3)&lt;/syntaxhighlight&gt;{{Bookcat}}</text>
      <sha1>m8lenlneqjznbdxktwfrp17erygjika</sha1>
    </revision>
    <revision>
      <id>4669041</id>
      <parentid>4668966</parentid>
      <timestamp>2026-09-06T03:02:00Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <comment>Work in progress. Saving Changes.</comment>
      <origin>4669041</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="64944" sha1="4s7gwbtjumlc6ybqweoczqsasfl5tv2" xml:space="preserve">== Maxima Aggregate Data Structures ==

=== Introduction ===
This section is intended to present some of the essentials of what are called Maxima aggregate data structures. By this it is meant the data types that can be used to refer to the values of expressions using a means of indexing of a single identifier (name) that refers to an aggregate (collection) of expressions as values.

Built-in aggregate data types include: 

* lists
* declared arrays
* hashed (undeclared) arrays
* Lisp arrays
* structures

Each of these has a means of indexing an identifier that names an instance of these data types. 

Please note that it is the case that this means of indexing an identifier for an aggregate data type may be referred to as involving &quot;subscripts&quot; or &quot;sub-scripted variables&quot; or &quot;keys&quot; as used by various computer programming languages, as well as in the context of Maxima documentation and commentary. In this book terms such as &quot;index&quot; or &quot;indices&quot; or &quot;indexed identifiers&quot;  are used instead.

Also all built-in Maxima functions (including packages) for these data types are referred to as ''&quot;operators&quot;'' and not ''&quot;functions&quot;'' as this latter term in general serves better to refer to Maxima function expressions defined by the user -- as in &lt;code&gt;f(x) :=&lt;/code&gt;, &lt;code&gt;g[s] :=&lt;/code&gt; and &lt;code&gt;define ()&lt;/code&gt; as examples.

This section is not intended to be exhaustive. It is intended to provide familiarity with aggregate data types. What is included has been gleaned from various sources, and only a few attributions are provided. Therefore, there is no claim of originality implied. 

=== Lists ===

==== Introduction to Lists ====
Lists are one of the basic buildings block for Maxima and Lisp. Maxima expressions are in general represented as Lisp lists. 

For example, consider the Maxima expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	e+3;
(%o1)	e+3
&lt;/syntaxhighlight&gt;This expression has the form of a Lisp list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i2)	:lisp #$[e+3]$
((MLIST SIMP) ((MPLUS SIMP) 3 $E))
&lt;/syntaxhighlight&gt;An expression in the form of a Lisp list can also be be displayed as a Maxima expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i2)	:lisp (displa '((MLIST SIMP) ((MPLUS SIMP) 3 $E)));
[e+3]
NIL
&lt;/syntaxhighlight&gt;Note that the value of this expression using &lt;code&gt;displa '()&lt;/code&gt; is &lt;code&gt;NIL&lt;/code&gt;, and &lt;code&gt;[e+3]&lt;/code&gt; is simply displayed in Maxima list object form. It is not necessary for the typical uses of Maxima to utilize this insight into the role Lisp lists have as one of the building blocks for Maxima, but it may be useful to have a familiarity with that role. Lists are often used as arguments to many operators, and the values of expressions are often in the form of lists.

==== Some Operators for Lists ====
Lists are created explicitly and list elements referenced using &lt;code&gt;[&lt;/code&gt; and &lt;code&gt;]&lt;/code&gt; to mark the beginning and end, respectively, of an instance of a list object, or to reference the expressions of an existing list object.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i3)	[2,3,4];
(%o3)	[2,3,4]
&lt;/syntaxhighlight&gt;The expression &lt;code&gt;[2,3,4]&lt;/code&gt; creates a Maxima list object. In this case the object itself is not accessible as it was not assigned an identifier unless referenced by the &lt;code&gt;%&lt;/code&gt; , &lt;code&gt;%i&lt;/code&gt; or &lt;code&gt;%o&lt;/code&gt; label.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i4)	%;
(%o4)	[2,3,4]

(%i5)	%o4[2]; /* second expression of list object referenced by index */ 
(%o5)	3
&lt;/syntaxhighlight&gt;That [2,3,4] is a list object can be tested using the &lt;code&gt;listp()&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i6)	listp ([2,3,4]);
(%o6)	true
&lt;/syntaxhighlight&gt;A list object can be assigned an identifier:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i7)	s : [%pi,%e,%phi];
(s)	[%pi,%e,%phi]

(%i8)	listp (s);
(%o8)	true&lt;/syntaxhighlight&gt;

The value of an element of a list can be accessed using the list identifier and brackets with a index value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i9)	s[1];
(%o9)	%pi

(%i10)	s[2];
(%o10)	%e

(%i11)	s[3];
(%o11)	%phi
&lt;/syntaxhighlight&gt;
Invalid index values returns an error:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i12)	s[4];
inpart: invalid index 4 of list or matrix.
-- an error. To debug this try: debugmode(true);
&lt;/syntaxhighlight&gt;
Consider the following relatively long list of integer atoms created explicitly and identified as &lt;code&gt;List_1&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i13)	List_1 : [1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
                  142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
                  1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
                  75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
                  4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
                  1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
                  142,5,1372,174,5,1582,177];

(List_1)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
             142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
             1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
             75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
             4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
             1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
             142,5,1372,174,5,1582,177]&lt;/syntaxhighlight&gt;
The number of values of this list can be returned using the &lt;code&gt;length()&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i14)	length (List_1);
(%o14)	105
&lt;/syntaxhighlight&gt;
Create another list identified as &lt;code&gt;List_2&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i15)	List_2 : [6,1455,200,6,1607,205];
(List_2)	[6,1455,200,6,1607,205]

(%i16)	length (List_2);
(%o16)	6
&lt;/syntaxhighlight&gt;
Create a third list identified as &lt;code&gt;List_3&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i17)	List_3 : append (List_1, List_2)$

(%i18)	length (List_3);
(%o19)	111
&lt;/syntaxhighlight&gt;
Note that the &lt;code&gt;'''append ()'''&lt;/code&gt; operator does not affect either of the list arguments &lt;code&gt;List_1&lt;/code&gt; or &lt;code&gt;List&lt;/code&gt;_2. It merely appends &lt;code&gt;List_2&lt;/code&gt; to &lt;code&gt;List_1&lt;/code&gt; and returns a new list, in this case assigned the identifier &lt;code&gt;List_3&lt;/code&gt;.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i20)	length (List_1);
(%o20)  105

(%i21)	length (List_2);
(%o21)  6

(%i22)	length (List_3);
(%o22)	111

(%i23)	List_3;
(%o23)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
         142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
         1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
         75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
         1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
         142,5,1372,174,5,1582,177,6,1455,200,6,1607,205]&lt;/syntaxhighlight&gt;
Values (only the last one in this example) can be deleted from a list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i24)	last (List_3);
(%o24)	205

(%i25)	delete (last (List_3), List_3);
(%o25)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,
         142,1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,
         1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,
         75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,
         1582,214,5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,
         142,5,1372,174,5,1582,177,6,1455,200,6,1607]&lt;/syntaxhighlight&gt;
The &lt;code&gt;delete (List_3)&lt;/code&gt; expression creates a new list object using &lt;code&gt;List_3&lt;/code&gt;. &lt;code&gt;List_3&lt;/code&gt; itself is not affected by the &lt;code&gt;'''delete ()'''&lt;/code&gt; operator. Only the resulting list is affected. This is often the case with list operators. An identifier could be used to save the above resulting list if necessary:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* List_3 is the same length */
(%i26)	length(List_3); 
(%o26)	111

/* The last value of List_3 is the same */
(%i27)	List_3[111];
(%o27)	205

(%i28)	last(List_3);
(%o28)	205&lt;/syntaxhighlight&gt;There was only one instance of &lt;code&gt;205&lt;/code&gt; in &lt;code&gt;List_3&lt;/code&gt;, so only that value was deleted from the list of &lt;code&gt;%o25&lt;/code&gt;.  If there are more than one value then the &lt;code&gt;delete ()&lt;/code&gt; operator will remove all of those values from the returned list expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i29)	NewList_3 : delete(118, List_3)$ 

/* all five instances of 118 removed from List_3 as NewList_3 */
(%i30)	length(NewList_3);
(%o30)	106
&lt;/syntaxhighlight&gt;There are operators to refer to instances of list expressions by ordinal number. Here are few examples:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i30)	FirstThreeList_3:[first(List_3), second(List_3), third(List_3)];
(FirstThreeList_3)	[1,118,30]
&lt;/syntaxhighlight&gt;Expressions of list objects can be referenced to create a new list object from the first ''n'' expressions of a list, the last ''n'' expressions of a list, or the rest remaining after ''n'' expressions from the beginning or ''-n'' expressions from the end of a list:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* first three expressions of List_3 */
(%i31)	firstn(List_3,3); 
(%o31)	[1,118,30]

/* same three expressions of List_3 using the rest operator with -108 */
(%i32)	rest(List_3, -108); 
(%o32)	[1,118,30]

/* last three expressions of List_3 */
(%i33)	lastn(List_3,3); 
(%o33)	[6,1607,205]

/* same three expressions of List_3 using the rest operator with 108 */
(%i34)	rest(List_3, 108);
(%o34)	[6,1607,205]&lt;/syntaxhighlight&gt;Some further examples of the &lt;code&gt;'''firstn ()'''&lt;/code&gt;, &lt;code&gt;'''lastn ()'''&lt;/code&gt; and &lt;code&gt;'''rest ()'''&lt;/code&gt; list operators:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* first 63 expressions of List_3 */
(%i35)	firstn (List_3, 63);
(%o35)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,
         1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,
         1372,203,2,1582,203,3,118,30,3,484,51,3,664,75,3,1004,108,3,
         1231,115,3,1372,139,3,1582,140]

/* last 63 expressions of List_3 */
(%i36)	lastn (List_3, 63);
(%o36)	[3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
         4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,
         5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,5,
         1582,177,6,1455,200,6,1607,205]

/* first expressions of List_3 after removing the last 63*/
(%i37)	rest (List_3, -63);
(%o37)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,
         1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,
         1372,203,2,1582,203,3,118,30,3,484,51]
&lt;/syntaxhighlight&gt;Maxima programming expressions can be used with list operators to reference list expressions in various ways. For example, the expression which follows accesses the expressions of a list as lists of three each:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i38)	(L4 : List_4,
	      for i:(-length (List_4)) + 3 thru 0 step 3 do
	             (disp (rest (L4, i)), 
	              L4 : rest (L4, 3)),
	     &quot;&quot;)$

[1,118,30]
[1,484,58]
[1,664,87]
[1,1004,115]
[1,1231,120]
[1,1372,142]
[1,1582,145]
[2,118,33]
[2,484,69]
[2,664,111]
[2,1004,156]
[2,1231,172]
[2,1372,203]
[2,1582,203]
[3,118,30]
[3,484,51]
[3,664,75]
&lt;/syntaxhighlight&gt;List operators can be used as arguments of other list operators:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* create a new empty list */
(%i39)	newList4 : [];
(newList4)	[]

/* append the first six &amp; last six expressions of List_4 to the new list */
(%i40)	newList4 : append (newList4, firstn (List_4, 6), lastn (List_4, 6))$

/* the new list now has the 12 appended expressions from List_4 */
(%i41)	newList4;
(%o41)	[1,118,30,1,484,58,3,484,51,3,664,75]
&lt;/syntaxhighlight&gt;

Maxima programming expressions can be used to step through the expressions of lists using list operators to reference &quot;slices&quot; of different lengths:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i42)	L4 : List_4;
(L4)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,1,1582
         145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,2,1372,203,
         2,1582,203,3,118,30,3,484,51,3,664,75]

(%i43)	length (L4);
(%o43)	51

(%i44)	(L4 : List_4,
         for i : 21 thru 3 step -3 do
	         print (L4 : lastn (L4, i),&quot; &quot;, length (L4)),
	    &quot;&quot;)$

[2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 21

[2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 18

[2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75] 15

[2,1582,203,3,118,30,3,484,51,3,664,75] 12

[3,118,30,3,484,51,3,664,75] 9

[3,484,51,3,664,75] 6

[3,664,75] 3&lt;/syntaxhighlight&gt;

==== Using the &lt;code&gt;copylist&lt;/code&gt; Operator ====
When an existing list object is assigned to an identifier, a reference to the memory location of the list object is used. This reference to the memory location is transparent from the point of view of the user. However, if this is not accounted for, unintended side effects may occur when assigning another identifier to an existing one that references a list object.

For example, in the expression &lt;code&gt;L4 : List_4&lt;/code&gt; it might be assumed that this results in the list object referenced by &lt;code&gt;List_4&lt;/code&gt; to simply be copied to a new memory location and reference for &lt;code&gt;L4&lt;/code&gt;. This is not the case. Both &lt;code&gt;L4&lt;/code&gt; and &lt;code&gt;List_4&lt;/code&gt; refer to the same list object in memory. Consequently, changes to the same list object can be effected by referencing the object using either alias.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i45)	newList4;
(%o45)	[1,118,30,1,484,58,3,484,51,3,664,75]

/* The identifier newList4 refers to a location in memory.
   The colon (:) assignment operator simply creates an alias
   using that same memory reference*/

(%i46)	newList5 : newList4;
(newList5)	[1,118,30,1,484,58,3,484,51,3,664,75]

/* Two different identifiers for the same memory location and
   therefore the same object. Changes to expressions of the list
   object using either identifier changes the same object in memory */
   
(%i47)	newList5[1] : 99;
(newList5[1])	99

(%i48)	newList4[1];
(%o48)	99

(%i49)	newList4;
(%o49)	[99,118,30,1,484,58,3,484,51,3,664,75]

(%i50)	newList5;
(%o50)	[99,118,30,1,484,58,3,484,51,3,664,75]
&lt;/syntaxhighlight&gt;
This &quot;side effect&quot; is often unwanted. The way to avoid this is by using the &lt;code&gt;copylist ()&lt;/code&gt; operator instead of the assignment operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i51)	newList4 : [1,118,30,1,484,58,3,484,51,3,664,75] ;
(newList4)	[1,118,30,1,484,58,3,484,51,3,664,75]

(%i52)	newList5 : copylist (newList4);
(newList5)	[1,118,30,1,484,58,3,484,51,3,664,75]
 
 /* Same list object expressions, but a different memory reference */

(%i53)	newList5[1] : 99;
(newList5[1])	99

(%i54)	newList4[1];
(%o54)	1
&lt;/syntaxhighlight&gt;
Changes to the values of either list will not affect the other list.
{| class=&quot;wikitable&quot;
|+List Object Operators
|[
|fourth
|rreduce
|-
|]
|fullsetify
|second
|-
|append
|join
|setify
|-
|assoc
|last
|seventh
|-
|cons
|length
|sixth
|-
|copylist
|listarith
|some
|-
|create_list
|listp
|sort
|-
|delete
|lmax
|sublist
|-
|eighth
|lmin
|sublist_indices
|-
|endcons
|lreduce
|tenth
|-
|fifth
|makelist
|third
|-
|first
|member
|tree_reduce
|-
|flatten
|reverse
|xreduce
|}

Refer to the Maximal Manual&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.4.2 Functions and Variables for Lists |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Lists}}&lt;/ref&gt; for more complete description of operators and variables for Maxima lists.

==== Performance Considerations for Lists ====
&lt;blockquote&gt;''&quot;Lists provide efficient ways of appending and removing elements. They can be created without knowing their final dimensions. Lisp provides efficient means of copying and handling lists. Also nested lists do not need to be strictly rectangular. These advantages over declared arrays come with the drawback that the amount of time needed for accessing a random element within a list may be roughly proportional to the element’s distance from its beginning.&quot;''&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.4.3 Performance considerations for Lists |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Lists}}&lt;/ref&gt;&lt;/blockquote&gt;Maxima list objects have many operators for creating, accessing, and changing the expressions of lists. Evaluation times of expressions that involve lists can vary significantly depending on the length of the list objects involved, as well as the nature of any operators used to compose the expressions. This fact might have an influence on the choice of using arrays rather than lists in some cases if evaluation time is a factor to consider. The example expressions that follow involve a list object (identified as &lt;code&gt;s&lt;/code&gt; ) of complex number expressions that has a length of 10,000 and two different user-defined functions:&lt;pre&gt;(%i55) P1(s) := rectform (product(s[i], i, 1, length (s)))$

(%i56) P2(s) := xreduce (lambda ([a, b], rectform (a * b)), s)$

(%i57) s : makelist (random (1.0) + %i*random (1.0), 10^4)$

(%i58)	showtime : true$
Evaluation took 0.0000 seconds (0.0000 elapsed) using 0 bytes.

(%i59) P1(s);
Evaluation took 32.3080 seconds (32.3860 elapsed) using 17944.301 MB.
(%o59) 0.0

(%i60) P2(s);
Evaluation took 0.0620 seconds (0.0620 elapsed) using 8.343 MB.
(%o60) 0.0

(%i61)	showtime : false$
Evaluation took 0.0000 seconds (0.0000 elapsed) using 0 bytes.&lt;/pre&gt;
==Arrays ==
&lt;blockquote&gt;&quot;Maxima's current array/matrix semantics are a mess, I must say, with at least four different kinds of object (hash arrays, explicit lists, explicit matrices, Lisp arrays) supporting subscripting with varying semantics.&quot; &lt;ref&gt;[http://comments.gmane.org/gmane.comp.mathematics.maxima.general/21829 Maxima: Syntax improvements by Stavros Macrakis ]&lt;/ref&gt;
– Stavros Macrakis

&quot;Maxima's concept of arrays, lists, and matrices is pretty confused, since various ideas have accreted in the many years of the project... Yes, this is a mess. Sorry about that. These are all interesting ideas, but there is no unifying framework.&quot;&lt;ref&gt;[http://stackoverflow.com/a/29926692 Maxima: what does Maxima call an “array”? - answer by Robert Dodier]&lt;/ref&gt;

– Robert Dodier&lt;/blockquote&gt;

The various terminology used in the context of arrays undoubtedly can be confusing. For the sake of simplicity and clarity the following categories of array objects are referred to in this book:


Maxima has three array categories :&lt;ref&gt;[http://permalink.gmane.org/gmane.comp.mathematics.maxima.general/13588 the Maxima mailing list &lt;nowiki&gt;: [Maxima] array and matrix? - answer by Robert Dodier&lt;/nowiki&gt;]&lt;/ref&gt;
* Declared arrays 
* Undeclared (hashed) arrays 
* Lisp arrays 

'''''Declared arrays''''' are explicitly created using the &lt;code&gt;array()&lt;/code&gt; operator, and unlike lists, which have only one index and are one-dimensional, declared  arrays can be multi-dimensional  – having one to five indices. The indices for declared array dimensions need not be equal.

Indices for each dimension may be between 0 and the respective declared dimension. Each declared array may be be declared with a specified type, which can be ''&lt;code&gt;fixnum&lt;/code&gt;'' for integers or ''&lt;code&gt;flonum&lt;/code&gt;'' for floating-point numbers.

'''''Undeclared (hashed) arrays''''' are created implicitly by assigning an expression to an indexed identifier that does not name an existing list object. An undeclared array (hashed array) can grow dynamically as there is no fixed dimension limit for each index as there is with declared arrays Another difference is that numbers, identifiers, expressions and strings may be used for indices.

Also, there is no fixed limit on the number of dimensions. The only real limitation is practical – the available computer memory and the underlying Lisp environment of the Maxima session. Hashed arrays with only one dimension may be confused with a list object.

It is essential to keep in mind that list objects must always be created before values are assigned or referenced. Assigning an expression to a one-dimensional indexed identifier, that does not reference an existing list, implicitly creates a hashed array.

'''''Lisp arrays''''' are created using the &lt;code&gt;'''make_array ()'''&lt;/code&gt; operator. The array type may be specified as ''any'', ''&lt;code&gt;flonum&lt;/code&gt;'', ''&lt;code&gt;fixnum&lt;/code&gt;'', or ''&lt;code&gt;hashed&lt;/code&gt;''. Lisp array objects may be created as one-dimensional or multi-dimensional as specified by the number of dimension size values used with the &lt;code&gt;'''make_array ()'''&lt;/code&gt; operator. For each  dimension value specified, the associated index value can be a number between 0 to 1 less than the respective dimension value. The same or different values may be used for each specified dimension. The ''&lt;code&gt;hashed&lt;/code&gt;'' type does not require any dimensions. Lisp arrays may be used in cases where memory usage and garbage collection are factors.

Examples of use and elaboration upon the technical details for each of these categories of array object types follows.
{| class=&quot;wikitable&quot;
|+Array Operators and Flags
|array
|arraysetapply
|rearray
|-
|arrayapply
|has_key
|remarray
|-
|arrayinfo
|fillarray
|subvar
|-
|arraymake
|listarray
|subvarp
|-
|arrays
|make_array
|use_fast_arrays
|-
|
|
|translate_fast_arrays
|}
=== Declared Arrays ===
Declared arrays must be created before being referenced and are of fixed dimensions.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	array (A1, fixnum, 34,2); 
(%o1)	A1

(%i2)	array (A2, flonum, 35,2);
(%o2)	A2

(%i3)	array (A3, 14,3);
(%o3)	A3

(%i4)	arrayinfo (A1);
(%o4)	[complete,2,[34,2]]

(%i5)	arrayinfo (A2);
(%o5)	[complete,2,[35,2]]

(%i6)	arrayinfo (A3);
(%o6)	[declared,2,[14,3]]
&lt;/syntaxhighlight&gt;
The first expression &lt;code&gt;%i1&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A1&lt;/code&gt;. This array is two-dimensional – the first index may have values from 0 to 34 and the second index may have values from 0 to 2. This array therefore is 35 by 3 in extent. The array type is declared to be &lt;code&gt;fixnum&lt;/code&gt;. As it is, &lt;code&gt;A1&lt;/code&gt; is an not empty array – it has values to reference as will be exemplified below.

Similarly the second expression &lt;code&gt;%i2&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A2&lt;/code&gt;. This array is also two-dimensional – the first index may have values from 0 to 35 and the second index may have values from 0 to 2. This array therefore is 36 by 3 in extent. The array type is declared to be &lt;code&gt;flonum&lt;/code&gt;. As it is, &lt;code&gt;A2&lt;/code&gt; is not an empty array – it also has values to reference as will be exemplified below.

The third expression &lt;code&gt;%i3&lt;/code&gt; creates a declared array object named using the identifier &lt;code&gt;A3&lt;/code&gt;. This array is also two-dimensional – the first index may have values from 0 to 13 and the second index may have values from 0 to 3. This array therefore is 15 by 4 in extent. The array type is not declared. As it is, &lt;code&gt;A3&lt;/code&gt; is an empty array – it has no values to reference as will be exemplified below.

The &lt;code&gt;'''arrayinfo ()'''&lt;/code&gt; operator can be used to return a list object that has values reflecting information about an array. Note that arrays declared without a type will have &lt;code&gt;declared&lt;/code&gt; as a value of the list. Arrays declared with &lt;code&gt;fixnum&lt;/code&gt; or &lt;code&gt;flonum&lt;/code&gt; as the type will have &lt;code&gt;complete&lt;/code&gt; as a value of the list. This technical detail is not well-documented. The returned information list also shows a value for the dimension of the array ( 2 in these examples ) and an inner list with values for the maximum index for each dimension.

A look inside each of these declared arrays provides a clue as to why &lt;code&gt;complete&lt;/code&gt; is returned instead of &lt;code&gt;declared&lt;/code&gt; when the type is specified as &lt;code&gt;fixnum&lt;/code&gt; or &lt;code&gt;flonum&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* This array reference has a value of 0 */
(%i7)	A1[0,0];
(%o7)	0

/* This array reference has a value of 0.0 */
(%i8)	A2[0,0];
(%o8)	0.0

/* This array reference has a value of itself */
(%i9)	A3[0,0];
(%o9)	A3[0,0]&lt;/syntaxhighlight&gt;

In fact, ''all'' values of the array &lt;code&gt;A1&lt;/code&gt; have been assigned 0, and ''all'' values of the array &lt;code&gt;A2&lt;/code&gt; have beenassigned 0.0. However, ''all'' values of the array &lt;code&gt;A3&lt;/code&gt; have been not been assigned any value.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i10)	listarray (A1);
(%o10)	[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
         0,0,0,0,0,0,0,0,0]

(%i11)	listarray (A2);
(%o11)	[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,
         0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]

(%i12)	listarray (A3);
(%o12)	[#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####,#####,#####,#####,#####,#####,#####,
         #####,#####,#####,#####,#####]&lt;/syntaxhighlight&gt;

Thus, arrays &lt;code&gt;A1&lt;/code&gt; and &lt;code&gt;A2&lt;/code&gt; are &lt;code&gt;complete&lt;/code&gt; in this sense, and array &lt;code&gt;A3&lt;/code&gt; is simply &lt;code&gt;declared&lt;/code&gt;.

It might seem reasonable, that Maxima would complain if a value was assigned to an array that is at odds with the declared type. Such is not the case however. Once an array is declared with a type, Maxima does not enforce any type checking of values assigned to the array.

The effect of the type (if any) in the declaration is simply to fill the array with values of #####, 0 or 0.0. Subsequently, those values can be replaced by the assignment of different values that will not be checked for the type of value. One way to enforce type checking is by using predicate operators to check values at the point in time of assignment to arrays. For example, using one or more of:

* numberp (expr)
* floatnump (expr)
* integerp (expr) 
* ratnump (expr)
* stringp (obj)
* listp (expr) 
* featurep (a, f)

and possibly others.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* A1 was declared as type fixnum */
(%i13)	A1[5,2]:3.14159;
(%o13)	3.14159

/* A2 was declared as type flonum */
(%i14)	A2[3,0]:7129;
(%o14)	7129

/* A1 which was declared as type fixnum assigned a string */
(%i15)	A1[4,1]:&quot;a string&quot;;
(%o15)	&quot;a string&quot;

/* A2 which was declared as type flonum assigned a math expression*/
(%i16)	A2[6,1]:3*x^2 + 4*x +10; 
(%o16)	3*x^2+4*x+10
&lt;/syntaxhighlight&gt;

There are other ways to assign values to an array. One way is to read the values from a comma separated (CSV) file  using the &lt;code&gt;'''read_array ()'''&lt;/code&gt; operator from the ''numericalio'' package.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i17) load (numericalio);
(%o17) &quot;/app/plugins/maxima/share/maxima/5.50.0/share/numericalio/numericalio.mac&quot;


&lt;/syntaxhighlight&gt;

Below are of the values of the CSV data file &lt;code&gt;tree_data_nh.csv&lt;/code&gt; :&lt;syntaxhighlight lang=&quot;text&quot;&gt;
1,118,30
1,484,58
1,664,87
1,1004,115
1,1231,120
1,1372,142
1,1582,145
2,118,33
2,484,69
2,664,111
2,1004,156
2,1231,172
2,1372,203
2,1582,203
3,118,30
3,484,51
3,664,75
3,1004,108
3,1231,115
3,1372,139
3,1582,140
4,118,32
4,484,62
4,664,112
4,1004,167
4,1231,179
4,1372,209
4,1582,214
5,118,30
5,484,49
5,664,81
5,1004,125
5,1231,142
5,1372,174
5,1582,177
&lt;/syntaxhighlight&gt;

Note that the following expression assumes that the CSV file is located in the Maxima working directory.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i18)	read_array(&quot;tree_data_nh.csv&quot;, A1, &quot;,&quot;); 
(%o18)	done

(%i19)	 listarray(A1);
(%o19)	[1,118,30,1,484,58,1,664,87,1,1004,115,1,1231,120,1,1372,142,
         1,1582,145,2,118,33,2,484,69,2,664,111,2,1004,156,2,1231,172,
         2,1372,203,2,1582,203,3,118,30,3,484,51,3,664,75,3,1004,108,
         3,1231,115,3,1372,139,3,1582,140,4,118,32,4,484,62,4,664,112,
         4,1004,167,4,1231,179,4,1372,209,4,1582,214,5,118,30,5,484,49,
         5,664,81,5,1004,125,5,1231,142,5,1372,174,5,1582,177]
&lt;/syntaxhighlight&gt;
Below are of the values of the CSV data file &lt;code&gt;tree_data.csv&lt;/code&gt;  which has a header row, but is otherwise the same as &lt;code&gt;tree_data_nh.csv&lt;/code&gt;:&lt;syntaxhighlight lang=&quot;text&quot;&gt;
&quot;Tree&quot;,&quot;age&quot;,&quot;circumference&quot;
1,118,30
1,484,58
1,664,87
1,1004,115
1,1231,120
1,1372,142
1,1582,145
2,118,33
2,484,69
2,664,111
2,1004,156
2,1231,172
2,1372,203
2,1582,203
3,118,30
3,484,51
3,664,75
3,1004,108
3,1231,115
3,1372,139
3,1582,140
4,118,32
4,484,62
4,664,112
4,1004,167
4,1231,179
4,1372,209
4,1582,214
5,118,30
5,484,49
5,664,81
5,1004,125
5,1231,142
5,1372,174
5,1582,177
&lt;/syntaxhighlight&gt;&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i20)	read_array (&quot;tree_data.csv&quot;, A2, &quot;,&quot;); 
(%o20)	done

(%i21) listarray (A2);
(%o21) [&quot;Tree&quot;,&quot;age&quot;,&quot;circumference&quot;,1,118,30,1,484,58,1,664,87,1,1004,
        115,1,1231,120,1,1372,142,1,1582,145,2,118,33,2,484,69,2,664,111,
        2,1004,156,2,1231,172,2,1372,203,2,1582,203,3,118,30,3,484,51,
        3,664,75,3,1004,108,3,1231,115,3,1372,139,3,1582,140,4,118,32,
        4,484,62,4,664,112,4,1004,167,4,1231,179,4,1372,209,4,1582,214,
        5,118,30,5,484,49,5,664,81,5,1004,125,5,1231,142,5,1372,174,
        5,1582,177]&lt;/syntaxhighlight&gt;The previous values of 0 and 0,0 as well as the assigned values of &lt;code&gt;A1&lt;/code&gt; and &lt;code&gt;A2&lt;/code&gt; have been replaced with the values from the CSV files.

The third array &lt;code&gt;A3&lt;/code&gt; can be used with values from the  &lt;code&gt;dataset.csv&lt;/code&gt; file below:&lt;syntaxhighlight lang=&quot;text&quot;&gt;&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;
&quot;Smith&quot;,16753.00,&quot;UK&quot;,&quot;Qtr 3&quot;
&quot;Johnson&quot;,14808.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Williams&quot;,10644.00,&quot;UK&quot;,&quot;Qtr 2&quot;
&quot;Jones&quot;,1390.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Brown&quot;,4865.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Williams&quot;,12438.00,&quot;UK&quot;,&quot;Qtr 1&quot;
&quot;Johnson&quot;,9339.00,&quot;UK&quot;,&quot;Qtr 2&quot;
&quot;Smith&quot;,18919.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Jones&quot;,9213.00,&quot;USA&quot;,&quot;Qtr 4&quot;
&quot;Jones&quot;,7433.00,&quot;UK&quot;,&quot;Qtr 1&quot;
&quot;Brown&quot;,3255.00,&quot;USA&quot;,&quot;Qtr 2&quot;
&quot;Williams&quot;,14867.00,&quot;USA&quot;,&quot;Qtr 3&quot;
&quot;Williams&quot;,19302.00,&quot;UK&quot;,&quot;Qtr 4&quot;
&quot;Smith&quot;,9698.00,&quot;USA&quot;,&quot;Qtr 1&quot;&lt;/syntaxhighlight&gt;&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i22)	read_array (&quot;dataset.csv&quot;, A3, &quot;,&quot;); 
(%o22)	done

(%i23)	 listarray (A3);
(%o23)	[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;,
         &quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;,
         &quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;,
         &quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;,
         &quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;,
         &quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;,
         &quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;,
         &quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;,
         &quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;,
         &quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;,
         &quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]&lt;/syntaxhighlight&gt;

Values of the array can be referenced by indices as required for some purpose:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i24)	A3[0,0];
(%o24)	&quot;Last Name&quot;

(%i25)	A3[4,2];
(%o25)	&quot;USA&quot;
&lt;/syntaxhighlight&gt;
A row list object can be created using the &lt;code&gt;'''makelist ()'''&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i26)	row1A3: makelist (A3[0, j], j, 0, 3)$

(%i27)	row1A3;
(%o27)	[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;]

(%i28)	row1A3[1];
(%o28)	&quot;Last Name&quot;

(%i29)	row15A3: makelist (A3[14, j], j, 0, 3)$

(%i30)	row15A3;
(%o30)	[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]

(%i31)	row15A3[2];
(%o31)	9698.0
&lt;/syntaxhighlight&gt;
A list of the indices of the array can be created:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i32)	indices_A3 : arrayinfo (A3)[3];
(indices_A3)	[14,3]
&lt;/syntaxhighlight&gt;
The number of indices of array &lt;code&gt;A3&lt;/code&gt; can also be referenced using the &lt;code&gt;'''length (''')&lt;/code&gt; operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i33)	length (arrayinfo(A3)[3]);
(%o33)	2
&lt;/syntaxhighlight&gt;The number of values of the array &lt;code&gt;A3&lt;/code&gt; can be returned using the '''&lt;code&gt;length ()&lt;/code&gt;''' operator:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i34)	length (listarray (A3));
(%o34)	60
&lt;/syntaxhighlight&gt;
The values of the array &lt;code&gt;A3&lt;/code&gt; can be printed as output using the list of values with a loop programming expression:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i35)	for i : 1 thru length (listarray (A3)) do 
            print ('A3[i] ,&quot; = &quot;,  listarray (A3)[i])$

A3[1]&quot; = &quot;&quot;Last Name&quot;
A3[2]&quot; = &quot;&quot;Sales&quot;
A3[3]&quot; = &quot;&quot;County&quot;
A3[4]&quot; = &quot;&quot;Quarter&quot;
A3[5]&quot; = &quot;&quot;Smith&quot;
A3[6]&quot; = &quot;16753.0
A3[7]&quot; = &quot;&quot;UK&quot;
A3[8]&quot; = &quot;&quot;Qtr 3&quot;
A3[9]&quot; = &quot;&quot;Johnson&quot;
A3[10]&quot; = &quot;14808.0
A3[11]&quot; = &quot;&quot;USA&quot;
A3[12]&quot; = &quot;&quot;Qtr 4&quot;
A3[13]&quot; = &quot;&quot;Williams&quot;
A3[14]&quot; = &quot;10644.0
A3[15]&quot; = &quot;&quot;UK&quot;
A3[16]&quot; = &quot;&quot;Qtr 2&quot;
A3[17]&quot; = &quot;&quot;Jones&quot;
A3[18]&quot; = &quot;1390.0
A3[19]&quot; = &quot;&quot;USA&quot;
A3[20]&quot; = &quot;&quot;Qtr 3&quot;
A3[21]&quot; = &quot;&quot;Brown&quot;
A3[22]&quot; = &quot;4865.0
A3[23]&quot; = &quot;&quot;USA&quot;
A3[24]&quot; = &quot;&quot;Qtr 4&quot;
A3[25]&quot; = &quot;&quot;Williams&quot;
A3[26]&quot; = &quot;12438.0
A3[27]&quot; = &quot;&quot;UK&quot;
A3[28]&quot; = &quot;&quot;Qtr 1&quot;
A3[29]&quot; = &quot;&quot;Johnson&quot;
A3[30]&quot; = &quot;9339.0
A3[31]&quot; = &quot;&quot;UK&quot;
A3[32]&quot; = &quot;&quot;Qtr 2&quot;
A3[33]&quot; = &quot;&quot;Smith&quot;
A3[34]&quot; = &quot;18919.0
A3[35]&quot; = &quot;&quot;USA&quot;
A3[36]&quot; = &quot;&quot;Qtr 3&quot;
A3[37]&quot; = &quot;&quot;Jones&quot;
A3[38]&quot; = &quot;9213.0
A3[39]&quot; = &quot;&quot;USA&quot;
A3[40]&quot; = &quot;&quot;Qtr 4&quot;
A3[41]&quot; = &quot;&quot;Jones&quot;
A3[42]&quot; = &quot;7433.0
A3[43]&quot; = &quot;&quot;UK&quot;
A3[44]&quot; = &quot;&quot;Qtr 1&quot;
A3[45]&quot; = &quot;&quot;Brown&quot;
A3[46]&quot; = &quot;3255.0
A3[47]&quot; = &quot;&quot;USA&quot;
A3[48]&quot; = &quot;&quot;Qtr 2&quot;
A3[49]&quot; = &quot;&quot;Williams&quot;
A3[50]&quot; = &quot;14867.0
A3[51]&quot; = &quot;&quot;USA&quot;
A3[52]&quot; = &quot;&quot;Qtr 3&quot;
A3[53]&quot; = &quot;&quot;Williams&quot;
A3[54]&quot; = &quot;19302.0
A3[55]&quot; = &quot;&quot;UK&quot;
A3[56]&quot; = &quot;&quot;Qtr 4&quot;
A3[57]&quot; = &quot;&quot;Smith&quot;
A3[58]&quot; = &quot;9698.0
A3[59]&quot; = &quot;&quot;USA&quot;
A3[60]&quot; = &quot;&quot;Qtr 1&quot;
&lt;/syntaxhighlight&gt;

Maxima treats declared arrays as fixed-sized, and individual values are accessed via indices. There is no built-in &quot;row&quot; object — rows must be extracted manually using the &lt;code&gt;'''makelist ()'''&lt;/code&gt; operator or by looping through values of an array.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i36)	array (rowsA3,15);
(%o36)	rowsA3

(%i37)	arrayinfo (rowsA3);
(%o37)	[declared,1,[15]]

(%i38)	for i : 0 thru 14 do
	       (rowsA3[i+1] : makelist (A3[i, j], j, 0, 3),
	        print (&quot;Row &quot;,i+1,&quot;: &quot;,rowsA3[i+1]))$;

&quot;Row &quot;1&quot;: &quot;[&quot;Last Name&quot;,&quot;Sales&quot;,&quot;Country&quot;,&quot;Quarter&quot;]
&quot;Row &quot;2&quot;: &quot;[&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;3&quot;: &quot;[&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;4&quot;: &quot;[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;5&quot;: &quot;[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;6&quot;: &quot;[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;7&quot;: &quot;[&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;8&quot;: &quot;[&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;9&quot;: &quot;[&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;10&quot;: &quot;[&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;11&quot;: &quot;[&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;12&quot;: &quot;[&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;13&quot;: &quot;[&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;14&quot;: &quot;[&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;15&quot;: &quot;[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]
&lt;/syntaxhighlight&gt;
Maxima does not have a built-in function like &lt;code&gt;delete&lt;/code&gt; or &lt;code&gt;unset&lt;/code&gt; for removing individual values from arrays using indices. Existing values of an array can be changed by assignment however:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i52)	rowsA3[1] : [&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;]$

(%i53)	for i : 1 thru 15 do
	    (newRowsA3[i] : rowsA3[i],
	    print (&quot;Row &quot;,i,&quot;: &quot;,newRowsA3[i]))$;

&quot;Row &quot;1&quot;: &quot;[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;2&quot;: &quot;[&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;3&quot;: &quot;[&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;4&quot;: &quot;[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;5&quot;: &quot;[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;6&quot;: &quot;[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;7&quot;: &quot;[&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;8&quot;: &quot;[&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;9&quot;: &quot;[&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;10&quot;: &quot;[&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;11&quot;: &quot;[&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;]
&quot;Row &quot;12&quot;: &quot;[&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;]
&quot;Row &quot;13&quot;: &quot;[&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;]
&quot;Row &quot;14&quot;: &quot;[&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;]
&quot;Row &quot;15&quot;: &quot;[&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]&lt;/syntaxhighlight&gt;
The &lt;code&gt;'''arrayapply ()'''&lt;/code&gt; operator can be used a follows to reference values of a declared array:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i39)	arrayapply (rowsA3,[5]);
(%o39)	[&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;]

(%i40)	arrayapply (A3, [5,1]);
(%o40)	4865.0
&lt;/syntaxhighlight&gt;The operator &lt;code&gt;'''fillarray (A, B)'''&lt;/code&gt; assigns values to array &lt;code&gt;A&lt;/code&gt; from &lt;code&gt;B&lt;/code&gt;, which can be a list or an array. The dimensions of the arrays &lt;code&gt;A&lt;/code&gt; and &lt;code&gt;B&lt;/code&gt; may not be the same. In that case, array &lt;code&gt;A&lt;/code&gt; is filled in &quot;row-major&quot; order. There may not be enough values in &lt;code&gt;B&lt;/code&gt; compared to &lt;code&gt;A&lt;/code&gt;. In that case, the last value of &lt;code&gt;B&lt;/code&gt; is used to for the remaining values of &lt;code&gt;A&lt;/code&gt;. There may be too many values of &lt;code&gt;B&lt;/code&gt; compared to array &lt;code&gt;A&lt;/code&gt;. In that case, the remaining values of &lt;code&gt;B&lt;/code&gt; once &lt;code&gt;A&lt;/code&gt; is filled are not used. The return value of &lt;code&gt;'''fillarray ()'''&lt;/code&gt; is not the filled array &lt;code&gt;A&lt;/code&gt;, but it is the first argument.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* Create a declared array B of type fixnum */
(%i41)	array (B, fixnum, 9);
(%o41)	B

/* list the values of array B */
(%i42)	listarray (B);
(%o42)	[0,0,0,0,0,0,0,0,0,0]

/* fill array B with the values of the list */
(%i43)	fillarray (B, [0,1, 2, 3, 4, 5, 6, 7, 8, 9.0]);
(%o43)	B

/* list the values of array B */
(%i44)	listarray (B);
(%o44)	[0,1,2,3,4,5,6,7,8,9.0]

/* fill array B with the value 1.0 */
(%i45)	fillarray (B, [1.0]);
(%o45)	B

/* list the values of array B */
(%i46)	listarray (B);
(%o46)	[1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0]

/* fill array B with the first 9 values of the list */
(%i47)	fillarray (B, [0,1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12]);
(%o47)	B

/* list the values of array B */
(%i48)	listarray (B);
(%o48)	[0,1,2,3,4,5,6,7,8,9]

/* Create a declared array D of no type */
(%i49)	array (D, 9);
(%o49)	D

/* list the values of array D */
(%i50)	listarray (D);
(%o50)	[#####,#####,#####,#####,#####,#####,#####,#####,#####,#####]

/* fill array D with the value 1.0 */ 
(%i51)	fillarray (D, [1.0]);
(%o51)	D

/* list the values of array D */
(%i52)	listarray (D);
(%o52)	[1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0]

/* Create a declared array E of no type */
(%i53)	array (E, 15);
(%o53)	E

/* fill array E with the values from the newRowsA3 list */ 
(%i54)	fillarray (E, listarray (newRowsA3));
(%o54)	E

/* list the values of array D */
(%i55)	listarray (E);
(%o55)	[[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;],
         [&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;],
         [&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]]

/* remove array E */
(%i56)	remarray (E);
(%o56)	[E]

/*  E is no longer an array */
(%i57)	arrayinfo (E);
arrayinfo: E is not an array.

 -- an error. To debug this try: debugmode(true);&lt;/syntaxhighlight&gt;

If you need to keep the array but remove only one value, you must reconstruct it without that value. The operator &lt;code&gt;'''remarray ()'''&lt;/code&gt; is the typical way to completely remove an array.

The &lt;code&gt;'''rearray (A, dim&lt;sub&gt;1&lt;/sub&gt;, dim&lt;sub&gt;2&lt;/sub&gt; ,…, dim&lt;sub&gt;n&lt;/sub&gt;)'''&lt;/code&gt; operator is used to change the dimensions of an array. The changed array will be filled with the elements of the existing array in row-major order. If the existing array has one or more smaller dimensions, the additional dimension values of the changed array are assigned with a value that depends on the type of the array. If the existing array has one or more larger dimensions, the deficient dimension values of the changed array are lost. The type of the array cannot be changed using this operator. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* list with the values of array B */
(%i58)	listarray (B);
(%o58)	[0,1,2,3,4,5,6,7,8,9]

/* list with information about array B */
(%i59)	arrayinfo (B);
(%o59)	[complete,1,[9]]

/* increase the dimension of array B */
(%i60)	rearray (B, 12);
(%o60)	\#\{Lisp array \[13\]\}

/* list with information about array B with increased dimension */
(%i61)	arrayinfo (B);
(%o61)	[complete,1,[12]]

/* list with the values of array B */
(%i62)	listarray (B);
(%o62)	[0,1,2,3,4,5,6,7,8,9,0,0,0]

/* decrease the dimension of array B */
(%i63)	rearray (B, 6);
(%o63)	\#\{Lisp array \[7\]\}

/* list with information about array B with decreased dimension */
(%i64)	arrayinfo (B);
(%o64)	[complete,1,[6]]

/* list with the values of array B */
(%i65)	listarray (B);
(%o65)	[0,1,2,3,4,5,6]


&lt;/syntaxhighlight&gt;

The &lt;code&gt;'''arraymake ()'''&lt;/code&gt; operator returns a value that is an array reference without evaluation. This operator, in spite of the name, does not &quot;make&quot; an array. It returns this reference as a value whether or not an array exists as an object:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* the arraymake operator returns the unevaluated reference to A */
(%i66)	arraymake (A, [i,j]);
(%o66)	A[i,j]

/* however array A is not an array object*/
(%i67)	arrayinfo (A);
arrayinfo: A is not an array.
 -- an error. To debug this try: debugmode(true);

/* Maxima sees A[j,k] as a reference to an undefined memoizing function */
(%i68)	op (arraymake (A, [i,j]));
(%o68)	A
&lt;/syntaxhighlight&gt;
However, from a practical point of view, this operator is used with existing arrays:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i69)	listarray (newRowsA3);
(%o69)	[[&quot;Solomon&quot;,1045.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,16753.0,&quot;UK&quot;,&quot;Qtr 3&quot;],
         [&quot;Johnson&quot;,14808.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Jones&quot;,1390.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Williams&quot;,12438.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Johnson&quot;,9339.0,&quot;UK&quot;,&quot;Qtr 2&quot;],
         [&quot;Smith&quot;,18919.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Jones&quot;,9213.0,&quot;USA&quot;,&quot;Qtr 4&quot;],
         [&quot;Jones&quot;,7433.0,&quot;UK&quot;,&quot;Qtr 1&quot;],
         [&quot;Brown&quot;,3255.0,&quot;USA&quot;,&quot;Qtr 2&quot;],
         [&quot;Williams&quot;,14867.0,&quot;USA&quot;,&quot;Qtr 3&quot;],
         [&quot;Williams&quot;,19302.0,&quot;UK&quot;,&quot;Qtr 4&quot;],
         [&quot;Smith&quot;,9698.0,&quot;USA&quot;,&quot;Qtr 1&quot;]]

(%i70)	arraymake (newRowsA3, [4]);
(%o70)	newRowsA3[4]

(%i71)	''%;
(%o71)	[&quot;Williams&quot;,10644.0,&quot;UK&quot;,&quot;Qtr 2&quot;]

(%i72)	arraymake (newRowsA3, [i]);
(%o72)	newRowsA3[i]

(%i73)	''%, i = 6;
(%o73)	[&quot;Brown&quot;,4865.0,&quot;USA&quot;,&quot;Qtr 4&quot;]

&lt;/syntaxhighlight&gt;
The operator &lt;code&gt;arraymake (x, [i])&lt;/code&gt; constructs the expression &lt;code&gt;x[i]&lt;/code&gt;, but does not evaluate it. 

The operator &lt;code&gt;'''subvar'''&lt;/code&gt; &lt;code&gt;'''(x, i)'''&lt;/code&gt; evaluates the indexed expression &lt;code&gt;x[i]&lt;/code&gt;, and evaluates its arguments. &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i74)	listarray (B);
(%o174)	[0,1,2,3,4,5,6]

(%i75)	x : B;
(x)	B

(%i76)	i : 4;
(i)	4

(%i77)	subvar (x, i);
(%o77)	4
&lt;/syntaxhighlight&gt;
The operator &lt;code&gt;'''subvarp (expr)'''&lt;/code&gt; returns a value of &lt;code&gt;true&lt;/code&gt; if &lt;code&gt;expr&lt;/code&gt; is a indexed identifier, and &lt;code&gt;false&lt;/code&gt; otherwise. This operator evaluates the argument &lt;code&gt;expr&lt;/code&gt;.  &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;

(%i78)	z[p];
(%o78)	z[p]

(%i79)	subvarp (z[p]);
(%o79)	true

(%i80)	x[i];
(%o80)	4

(%i81)	subvar (x, i)
(%o81)	4

(%i82)	w : z[p];
(w)	z[p]

(%i83)	subvarp (w);
(%o83)	true


&lt;/syntaxhighlight&gt;
The expression &lt;code&gt;'''arrays'''&lt;/code&gt;  returns a list of allocated arrays: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i84)	arrays;
(%o84)	[A3,A2,A1,rowsA3,newRowsA3,B,D]&lt;/syntaxhighlight&gt;

The operator &lt;code&gt;'''arraysetapply (A, [i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2,&lt;/sub&gt;…,i&lt;sub&gt;n&lt;/sub&gt;], x)'''&lt;/code&gt; assigns the value of expression &lt;code&gt;x&lt;/code&gt; to &lt;code&gt;A&lt;/code&gt;&lt;code&gt;[i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2&lt;/sub&gt;,…,i&lt;sub&gt;n&lt;/sub&gt;]&lt;/code&gt;, where &lt;code&gt;A&lt;/code&gt; is an array and &lt;code&gt;i&lt;sub&gt;1&lt;/sub&gt;,i&lt;sub&gt;2&lt;/sub&gt;,…,i&lt;sub&gt;n&lt;/sub&gt;&lt;/code&gt; are integers.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i85)	arraysetapply (newRowsA3, [8], [&quot;George&quot;,20818.0,&quot;UK&quot;,&quot;Qtr 4&quot;]);
(%o85)	[&quot;George&quot;,20818.0,&quot;UK&quot;,&quot;Qtr 4&quot;]&lt;/syntaxhighlight&gt;
=== Undeclared Arrays ===

Maxima declared arrays and Maxima undeclared arrays will likely be the two types of data structures used by most users. Maxima undeclared arrays are also referred to as '''''hashed arrays'''''. For both of these two array types, memory allocation and structure occur &quot;behind the curtain&quot; of the Maxima user level, and &quot;the man behind the curtain&quot; is Lisp.

Of these two types, hashed arrays are the most flexible from the user point of view, all other factors being equal:

* The indices allowed for hashed arrays can be expressions,
* The dimensions of a hashed array are dynamic and not fixed, and
* Hashed arrays are relatively easier to create.
In fact, hashed arrays can be somewhat too easy to create. In the examples of the previous section involving declared arrays, identifiers were used as names for arrays. here is the list of allocated arrays:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i86)	arrays;
(%o86)	[A3,A2,A1,rowsA3,newRowsA3,B,D,my_list,h]&lt;/syntaxhighlight&gt;The array information for array &lt;code&gt;newRowsA3&lt;/code&gt; is shown below:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i87)	arrayinfo(newRowsA3);
(%o87)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15]]
&lt;/syntaxhighlight&gt;So the array &lt;code&gt;newRowsA3&lt;/code&gt; is not a declared array. it was created as part of a loop programming expression repeated below:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i53)	for i : 1 thru 15 do
	    (newRowsA3[i] : rowsA3[i],
	    print(&quot;Row &quot;,i,&quot;: &quot;,newRowsA3[i]))$;&lt;/syntaxhighlight&gt;When the first loop block was executed with i : 1, the assignment expression:

&lt;code&gt;newRowsA3[i] : rowsA3[i]&lt;/code&gt;

created a hashed array named  &lt;code&gt;newRowsA3&lt;/code&gt; and assigned &lt;code&gt;newRowsA3[1]&lt;/code&gt; the value of &lt;code&gt;rowsA3[1]&lt;/code&gt; automatically without any declaration. After that the hashed array dynamically allocated memory for values of the loop identifier i from 2 through 15 with each successive pass in the loop expression. Since hashed arrays are undeclared, and their associated dimensions are not fixed, but rather increase dynamically, expressions can be added to hashed arrays without creating a error message. These added values can be can be any valid Maxima expression, and the value of the indices used are not limited to zero and nonzero integers:  &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i88)	newRowsA3[16] :  [&quot;Maisel&quot;,12785.0,&quot;USA&quot;,&quot;Qtr 2&quot;];
(newRowsA3[16])	[&quot;Maisel&quot;,12785.0,&quot;USA&quot;,&quot;Qtr 2&quot;]

(%i89	arrayinfo(newRowsA3);
(%o89)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15],[16]]

(%i90)	newRowsA3[z]  : 2*sin(y) ^2 + 3*sin(x)^3;
(newRowsA3[z])	2*sin(y)^2+3*sin(B)^3

(%i91)	arrayinfo(newRowsA3);
(%o91)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],[11],[12],[13],[14],[15],[16],[z]]
&lt;/syntaxhighlight&gt;So one point to glean from this example is that all that is required to create a hashed array is an assignment expression to an indexed identifier, but it does require this assignment. If for some reason, a declared array is intended, but not declared using the &lt;code&gt;array&lt;/code&gt; operator (as in the instance of &lt;code&gt;newRowsA3&lt;/code&gt;), then a hashed array will be created at the first assignment of an expression to an indexed identifier.

This issue can also occur in cases where reference to a list value is intended, but the list has not been created. Lists are one-dimensional objects by definition. A reference using an identifier with a single index intended to be a list with no list existing named by that identifier, can inadvertently create a hashed array.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i91)	Alist[2] : 2*sin(y) ^2 + 3*sin(s)^3;
(Alist[2])	2*sin(y)^2+3*sin(s)^3

(%i92)	listp(Alist);
(%o92)	false

(%i93)	arrayinfo(Alist);
(%o93)	[hashed,1,[2]]
&lt;/syntaxhighlight&gt;The identifier &lt;code&gt;Alist&lt;/code&gt; is a name for a hashed array and not a list.

However, hashed arrays, like declared arrays can, be multi-dimensional: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i94)	a_hashed_array [j,k,l] : [12,s^(1/3), %i];
(%o94)	[12,s^(1/3),%i]

(%i95)	arrayinfo(a_hashed_array);
(%o95)	[hashed,3,[j,k,l]]
&lt;/syntaxhighlight&gt;The &lt;code&gt;array&lt;/code&gt; operator can be used to transform a hashed array into a declared array:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i96)	another_hashed_array[ 0, 2, 3] : 55;
(%o96)	55

(%i97)	array (another_hashed_array, 2, 4, 5);
(%o97)	another_hashed_array

(%i98)	arrayinfo(another_hashed_array);
(%o98)	[declared,3,[2,4,5]]
&lt;/syntaxhighlight&gt;From the user point of view, hashed arrays and declared arrays typically can be used for the same purpose. If dynamic dimensions or index expression flexibility are factors, then hashed arrays are likely to be a better choice. Many of the operators that can use declared arrays as arguments, may also be used with hashed arrays.

However, it should be noted at this point, that merely using a indexed identifier alone without an assignment, will not create a hashed array. Instead, Maxima interprets an expression so composed as an identifier for an undefined memoizing function, which is the topic of the next section.

==== Memoizing Functions ====
Assignment using an indexed identifier implicitly creates an undeclared (hashed) array. However, entering an expression that is an unassigned indexed identifier, from the point of view of Maxima, creates the identifier of a &quot;memoizing&quot; function. Memoizing functions are technically not an array topic, as these functions fall under the category of function definition. These functions have one foot in the function category and the other foot in the array category.

Memoizing functions are defined in a manner similar to other user-defined functions, for example:

&lt;code&gt;f(x, y, z) := x^2 + y^2 + z^2;&lt;/code&gt;

But instead of the arguments being enclosed in parentheses, they are enclosed using brackets:

&lt;code&gt;f[x, y, z] := x^2 + y^2 + z^2;&lt;/code&gt;

However, memoizing functions may be referred to as ''array functions,'' and it is the case that these functions from the point of view of aggregate data structures are hashed arrays. So these are mentioned and exemplified here for that reason:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;/* reference an indexed identifier h without assignment */
(%i99)	h[x];
(%o99)	h[x]

/* check identifier h as an array */
(%i100)	arrayinfo (h);
arrayinfo: h is not an array.
  -- an error. To debug this try: debugmode(true);
  
/* check identifier h as a function */
(%i101)	op(h[x]);
(%o101)	h

/* define h[x] as a function */
(%i102)	h[x] := 5*x^3 + sin(x);
(h[x])	h[x]:=5*x^3+sin(x)

/* check identifier h[x] as a function */
(%i103)	op(h[x]);
(%o103)	&quot;+&quot;

/* check identifier h as an array */
(%i104)	arrayinfo (h);
(%o104)	[hashed,1,[x]]

/* check the value of identifier h[x] */
(%i105)	h[x];
(%o105)	sin(x)+5*x^3

/* evaluate identifier h[x] with the argument 3*%pi */
(%i106)	h[3*%pi];
(%o106)	135*%pi^3

/* list the values of identifier h as an array */
(%i107)	listarray(h);
(%o107)	[135*%pi^3,sin(x)+5*x^3]

/* check identifier h as an array */
(%i108)	arrayinfo (h);
(%o108)	[hashed,1,[3*%pi],[x]]&lt;/syntaxhighlight&gt;A defined memoizing function stores its value the ''first time'' it is referenced with arguments, and returns the stored value, without evaluation, when the same arguments are used with that function subsequently. The stored value is &quot;frozen&quot; after the initial evaluation. Thus, it behaves like a hashed array. The arguments of a memoizing function also serve as indices of the associated hashed array.

=== Lisp Arrays ===
Lisp arrays are created using the &lt;code&gt;make_array (type, dim&lt;sub&gt;1&lt;/sub&gt;, dim&lt;sub&gt;2&lt;/sub&gt;, …, dim&lt;sub&gt;n&lt;/sub&gt;)&lt;/code&gt; operator. Perhaps a better name for this operator would be &lt;code&gt;make_lisp_array ()&lt;/code&gt;, which admittedly is a longer name.

This operator creates and has a return value of a Lisp array. The array type may be &lt;code&gt;any&lt;/code&gt;, &lt;code&gt;flonum&lt;/code&gt;, &lt;code&gt;fixnum&lt;/code&gt;, or  &lt;code&gt;hashed&lt;/code&gt; . The &lt;code&gt;functional&lt;/code&gt; type referred to in the Maxima Manual appears to have been deprecated, and may result in an error message if used. There can be ''n'' indices, and where the associated indices can be a value from ''0'' to ''dim&lt;sub&gt;i&lt;/sub&gt; -1'', and ''i'' can have a value of one of 1 to n inclusive.

This operator can be used as an alternative to the &lt;code&gt;array ()&lt;/code&gt; operator. The advantage of using &lt;code&gt;make_array()&lt;/code&gt; is that the return value of &lt;code&gt;make_array()&lt;/code&gt; ''does not have a name''. Once the Maxima identifier that is assigned to the array return value is no longer assigned, the array memory allocation is released, and the allocated memory can be garbage collected. What it is being referred to that Lisp arrays created using &lt;code&gt;make_array()&lt;/code&gt; do not have names? &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* create a undeclared Maxima hashed array */
(%i109)	arrayA1 [1] : 55;  
(%o109)	55

/* check the information about this undeclared Maxima hashed array */
(%i110)	arrayinfo (arrayA1);
(%o110)	[hashed,1,[1]]

/* check the value of this undeclared Maxima hashed array */
(%i111)	arrayA1;
(%o111)	arrayA1     /* the name */

/* create a Lisp hashed array */
(%i112)	arrayA2 : make_array (hashed);
(arrayA2)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 1 {1202987DC3}&gt;&quot;

/* check the information about this Lisp hashed array */
(%i113)	arrayinfo (arrayA2);
(%o113)	[hash_table,1]

/* check the value of this Lisp hashed array */
(%i114)	arrayA2;
(%o114)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 1 {1202987DC3}&gt;&quot; /* no name */

(%i115)	listarray (arrayA2);
(%o115)	[]                     /* this hashed array is empty */
&lt;/syntaxhighlight&gt;So Lisp arrays do not have a name as a value. So, Maxima identifiers assigned to a Lisp array have no name for the array as a value. These identifiers have the reference to the array itself as a value, Lisp hashed arrays created using &lt;code&gt;make_array()&lt;/code&gt; with the hashed type specified, do not use dimensions. Lisp hashed arrays are often referred to as '''''hashed tables''''', and their indices are called '''''keys'''''.

An example of a Lisp array with the type &lt;code&gt;any&lt;/code&gt; follows:

&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* make a Lisp 3 by 4 array of type any */
(%i116)	arrayA3 : make_array (any, 3,4);
(arrayA3)	\#\{Lisp array \[3\\,4\]\}

(%i117)	arrayinfo (arrayA3);
(%o117)	[declared,2,[2,3]]

(%i118)	listarray(arrayA3);
(%o118)	[false,false,false,false,false,false,false,false,false,false,false,false]

(%i119)	arrayA3[1,1] : &quot;a string&quot; ;
(%o119)	&quot;a string&quot;

(%i120)	listarray(arrayA3);
(%o120)	[false,false,false,false,false,&quot;a string&quot;,
         false,false,false,false,false,false]
&lt;/syntaxhighlight&gt;Contrary to statements made in some sources, type checking is is not accomplished automatically, and will not cause Maxima to return an error message, as the Lisp array with the type &lt;code&gt;fixnum&lt;/code&gt; which follows is an exemplifies:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i121)	arrayA4 : make_array (fixnum, 3,4);
(arrayA4)	\#\{Lisp array \[3\\,4\]\}

(%i122)	arrayinfo (arrayA4);
(%o122)	[declared,2,[2,3]]

(%i123)	listarray (arrayA4);
(%o123)	[0,0,0,0,0,0,0,0,0,0,0,0]

(%i124)	arrayA4[0,2] : 3.14159;
(%o124)	3.14159

(%i125)	arrayA4[0,0] : &quot;a string&quot;;
(%o125)	&quot;a string&quot;

/* value types not checked and no error message */
(%i126)	listarray (arrayA4);
(%o126)	[&quot;a string&quot;,0,3.14159,0,0,0,0,0,0,0,0,0]&lt;/syntaxhighlight&gt;As was the case with declared arrays, there is no type checking and no error messages associated with assigned values of the array based on the declared type. The declared array type simply determines initial fill values, if any.

Hashed arrays and Lisp hash tables have an operator in common:

&lt;code&gt;has_key&lt;/code&gt; &lt;code&gt;(A, L)&lt;/code&gt;

This expression has a a value of &lt;code&gt;true&lt;/code&gt;, if the hashed array or Lisp hash table &lt;code&gt;A&lt;/code&gt; has the key (index) or keys (indices) of the list object &lt;code&gt;L&lt;/code&gt;.  Otherwise the expression has a value of &lt;code&gt;false&lt;/code&gt;.

The array &lt;code&gt;A&lt;/code&gt; must be a hashed (undeclared) array, a Lisp hash table value returned by the &lt;code&gt;make_array&lt;/code&gt; operator, or created as an undeclared array with &lt;code&gt;use_fast_arrays&lt;/code&gt; assigned the value &lt;code&gt;true&lt;/code&gt;.

If array A has only one key, that key must be the value of a list.&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i127)	arrayinfo (newRowsA3);
(%o127)	[hashed,1,[1],[2],[3],[4],[5],[6],[7],[8],[9],[10],
                  [11],[12],[13],[14],[15],[16],[z]]

(%i128)	has_key (newRowsA3, [z]);
(%o128)	true

(%i129)	has_key (newRowsA3, [3]);
(%o129)	true

(%i130)	has_key(newRowsA3, [0]);
(%o130)	false

(%i131)	lisp_Array_1 [x];
(%o131)	3*x^2

(%i132)	arrayinfo (lisp_Array_1);
(%o132)	[hash_table,1,x]

(%i133)	has_key (lisp_Array_1, [x]);
(%o133)	true

(%i134)	has_key (lisp_Array_1, [y]);
(%o134)	false
&lt;/syntaxhighlight&gt;

=== Arrays and Features ===
Maxima arrays can be assigned features in a manner similar to other identifiers:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i135)	array (a6,fixnum, 5);
(%o135)	a6

(%i136)	arrayinfo (a6);
(%o136)	[complete,1,[5]]

(%i137)	declare (a6, [real, noninteger]);
(%o137)	done

(%i138)	featurep (a6, real);
(%o138)	true

(%i139)	featurep (a6, noninteger);
(%o139)	true

(%i140)	a6[2] : 2;
(a6[2])	2

(%i141)	listarray (a6);
(%o141)	[0,0,2,0,0,0]
&lt;/syntaxhighlight&gt;However, once again, declaring an array to have one or more features does not result in type checking of values assigned to an array. Perhaps the best way to ensure types of values assigned to arrays is type-checking of expressions using predicate operators prior to assignment to arrays. 

=== Array Memory Storage Considerations ===

The following from the Maxima Manual&lt;ref&gt;{{Cite web |title=Maxima Manual Section 7.5.1 - Functions and Variables for Arrays |url=https://maxima.sourceforge.io/docs/manual/Data-Types-and-Structures.html#Functions-and-Variables-for-Arrays}}&lt;/ref&gt; is quoted here for the purpose of establishing the context of that which follows:&lt;blockquote&gt;''&quot;Option variable: use_fast_arrays ¶''

''Default value: false''

''When use_fast_arrays is true, arrays declared by array are values instead of properties, and undeclared arrays (hashed arrays) are implemented as Lisp hashed arrays.''

''When use_fast_arrays is false, arrays declared by array are properties, and undeclared arrays are implemented with Maxima’s own hashed array implementation.''

''Note that the code use_fast_arrays switches to is not necessarily faster than the default one; Arrays created by make_array are not affected by use_fast_arrays.&quot;''&lt;/blockquote&gt;
This Maxima Manual entry requires some elaboration in order to have a sufficient understanding of the effect of the &lt;code&gt;'''use_fast_arrays'''&lt;/code&gt; &quot;flag&quot; – referred to as an &quot;Option Variable&quot; in the above quotation.

The first point to note is that the default value of this flag is &lt;code&gt;false&lt;/code&gt;. So, if users take no action to assign this flag to the value &lt;code&gt;true&lt;/code&gt;, then declared arrays created using the &lt;code&gt;array()&lt;/code&gt; operator  are treated as ''properties'' bound to a symbol, and behave in the manner previously described. Likewise undeclared arrays are a Maxima array implementation, and behave as legacy property hash tables, and these also behave as previously described.

If action is taken to enter an expression that assigns the value &lt;code&gt;true&lt;/code&gt; to this flag, then Maxima treat arrays as standard Lisp ''values'' rather than object properties:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i142)	use_fast_arrays;
(%o142)	false

(%i143)	array (A1,fixnum, 10);
(%o143)	A1

(%i144)	arrayinfo (A1);
(%o144)	[complete,1,[10]]

(%i145)	H1[1] : 1729;
(H1[1])	1729

(%i146)	arrayinfo (H1);
(%o146)	[hashed,1,[1]]

(%i147)	use_fast_arrays : true;
(use_fast_arrays)	true

(%i148)	array (A2, fixnum, 10);
(%o148)	\#\{Lisp array \[11\]\}

(%i149)	A2;
(%o149)	\#\{Lisp array \[11\]\}

(%i150)	H2[1] : 1729;
(H2[1])	1729

(%i151)	H2;
(%o151)	&quot;#&lt;HASH-TABLE :TEST EQUAL :COUNT 2 {1203AD15A3}&gt;&quot;

(%i152)	arrayinfo (H2);
(%o152)	[hash_table,1,1]
&lt;/syntaxhighlight&gt; The &lt;code&gt;use_fast_arrays&lt;/code&gt; flag has no effect on arrays created using the &lt;code&gt;make_array ()&lt;/code&gt; operator.

Note the following:

* Assigning &lt;code&gt;use_fast_arrays&lt;/code&gt; &lt;code&gt;: true&lt;/code&gt; does not speed up execution for all operations. It primarily optimizes memory footprint by minimizing cell allocations.  The main benefit is optimization of memory footprints and structural representation inside Lisp.
* If compiling Maxima expressions to native Lisp using the &lt;code&gt;translate&lt;/code&gt; &lt;code&gt;()&lt;/code&gt; operator, pair this flag with &lt;code&gt;translate_fast_arrays&lt;/code&gt; &lt;code&gt;: true&lt;/code&gt;. This flag instructs the translator to compile arrays as value-based.

=== Structures ===
Structures, although not an array data type is an aggregation data type.  By &quot;aggregation&quot; it is meant a data type that references other data types by reference to a name and some method of accessing individual values of instances of that aggregation by means of indices used to reference values individually.

Thus, as has been previously described for example lists, hashed arrays, Lisp arrays, and declared arrays are all aggregation data types with syntactical means to refer to individual values of a named aggregation instance by way of indices, which are sometimes also referred to as subscripts or keys.

As examples:

* An existing '''list''' named &lt;code&gt;L1&lt;/code&gt; has values that can be accessed as &lt;code&gt;L1[1]&lt;/code&gt;, &lt;code&gt;L[2]&lt;/code&gt;, &lt;code&gt;L[3]&lt;/code&gt;, and so forth
* An existing '''hashed array''' with two indices (&quot;2D&quot;) named &lt;code&gt;ha&lt;/code&gt; has values that can accessed as &lt;code&gt;ha[1,1&lt;/code&gt;], &lt;code&gt;ha[1,2]&lt;/code&gt;,..., &lt;code&gt;ha[2,1]&lt;/code&gt;, &lt;code&gt;ha[2,2]&lt;/code&gt;, and  so forth.
* An existing '''declared array''' with three indices (&quot;3D&quot;) named &lt;code&gt;da&lt;/code&gt; has values that can be accessed as &lt;code&gt;da[1,1,1]&lt;/code&gt;, &lt;code&gt;da[1,1,2]&lt;/code&gt;,...,&lt;code&gt;da [2,1,1]&lt;/code&gt;, ..., &lt;code&gt;da[3,1,1]&lt;/code&gt;, and so forth.

What makes the Maxima structure data type different from these array data types is the form of definition used and the means of accessing values of an instance of this type of aggregation. The Maxima structure data type seems to be the closest type of data that resembles an object in some other general-purpose programming languages.

The structure type of data allows the creation of named entities with attributes, and named instances of those entities and the assignment of values to those attributes. Thus the Maxima structure data type is used to define custom, named composite data types that group related fields together under a single identifier. Structures enhance code organization and readability, especially when modeling real-world entities in symbolic computations. They are useful for managing complex data in programs involving algebraic manipulations, simulations, or data modeling.  

Structures are created using the &lt;code&gt;defstruct&lt;/code&gt; operator, which defines a template with named attributes. Once defined, instances of the structure are created using the &lt;code&gt;new&lt;/code&gt; operator, and attributes are accessed via the &lt;code&gt;@&lt;/code&gt; operator. 

So in the interest of taking advantage of this information, consider a well-defined set of people. The people of this set may have many diverse attributes that might be of interest - name, age ,and city of residence as examples. A class of people of the set of interest with these attributes can be defined as follows: &lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i153)	defstruct (person (name, age, city));
(%o153)	[person(name,age,city)]

(%i54) structures;
(%o154)                      [person(name, age, city)]

(%i155)	p : new (person (&quot;Alice&quot;, 30, &quot;New York&quot;));
(p)	person(name=&quot;Alice&quot;,age=30,city=&quot;New York&quot;)

(%i156)	p@name;
(%o156)	&quot;Alice&quot;

(%i157)	p@city;
(%o157)	&quot;New York&quot;

(%i158)	kill(p@city);
(%o158)	done

/* If the attribute a in x has not been assigned a value, or the value
   has been &quot;killed,&quot; then x@a evaluates to itself */

(%i159)	p@city;
(%o159)	p@city

(%i160)	p;
(%o160)	person(name=&quot;Alice&quot;,age=30,city)

(%i161)	p@city : &quot;Rochester&quot;;
(%o161)	&quot;Rochester&quot;

(%i162)	p;
(%o162)	person(name=&quot;Alice&quot;,age=30,city=&quot;Rochester&quot;)

(%i163) defstruct (sales(LastName, Sales , Country , Quarter) );
(%o163)             [sales(LastName, Sales, Country, Quarter)]

(%i164) structures;
(%o164) [person(name, age, city), sales(LastName, Sales, Country, Quarter)]

(%i165) s : new (sales (&quot;Smith&quot;,16753.00,&quot;UK&quot;,&quot;Qtr 3&quot;));
(%o165) sales(LastName=Smith, Sales=16753.0, Country=UK, Quarter=Qtr 3)

(%i166) s@Sales;
(%o166)                              16753.0

(%i167) s@Sales : 17375.0;
(%o167)                              17375.0

(%i168) s;
(%o168) sales(LastName=Smith, Sales=17375.0, Country=UK, Quarter=Qtr 3)&lt;/syntaxhighlight&gt;{{Bookcat}}</text>
      <sha1>4s7gwbtjumlc6ybqweoczqsasfl5tv2</sha1>
    </revision>
  </page>
  <page>
    <title>User:EVolvo/sandbox</title>
    <ns>2</ns>
    <id>444945</id>
    <revision>
      <id>4668933</id>
      <parentid>4049007</parentid>
      <timestamp>2026-09-05T12:44:31Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668933</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="979" sha1="ns8om234qchp47k3f5dy69swvbwyeti" xml:space="preserve">
==VIN table==

{| class=&quot;wikitable&quot; style=&quot;text-align:center&quot;
|-
! VIN Digit
| style=&quot;width:5%&quot; | 1
| style=&quot;width:5%&quot; | 2
| style=&quot;width:5%&quot; | 3
| style=&quot;width:5%&quot; | 4
| style=&quot;width:5%&quot; | 5
| style=&quot;width:5%&quot; | 6
| style=&quot;width:5%&quot; | 7
| style=&quot;width:5%&quot; | 8
| style=&quot;width:5%;background:#aaaaaa;{{Text default color}};&quot; | 9
| style=&quot;width:5%&quot; | 10
| style=&quot;width:5%&quot; | 11
| style=&quot;width:5%&quot; | 12
| style=&quot;width:5%&quot; | 13
| style=&quot;width:5%&quot; | 14
| style=&quot;width:5%&quot; | 15
| style=&quot;width:5%&quot; | 16
| style=&quot;width:5%&quot; | 17
|-
! Section
| colspan=&quot;3&quot; style=&quot;background:#aaffaa;{{Text default color}};&quot; | [[Vehicle_Identification_Numbers_(VIN_codes)/World_Manufacturer_Identifier_(WMI)|WMI]]
| colspan=&quot;6&quot; style=&quot;background:#aaaaff;{{Text default color}};&quot; | [[Vehicle_Identification_Numbers_(VIN_codes)/Vehicle_Descriptor_Section|VDS]]
| colspan=&quot;8&quot; style=&quot;background:#ffaaaa;{{Text default color}};&quot; | [[Vehicle_Identification_Numbers_(VIN_codes)/Vehicle_Identifier_Section|VIS]]
|}</text>
      <sha1>ns8om234qchp47k3f5dy69swvbwyeti</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Wilson Mohammed</title>
    <ns>3</ns>
    <id>448809</id>
    <revision>
      <id>4669050</id>
      <parentid>4098050</parentid>
      <timestamp>2026-09-06T06:35:08Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669050</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="681" sha1="2ezk8eniwrnmuujlxv002gl3bm4t47t" xml:space="preserve">&lt;div style=&quot;padding:5px; border:1px solid #A9A9A9; background-color:#FFEFD5;{{text default color}}; min-height:40px;&quot;&gt;[[File:Stop x nuvola.svg|40px|left|link=]] '''[[Wikibooks:Blocking policy|You cannot edit]] indefinitely due to disruptive editing'''.  You may appeal this action with a reasonable argument by adding the text &lt;!-- Copy the text as it appears on your page, not as it appears in this edit area. Do not include the &quot;tlx&quot; argument. --&gt;{{tlx|unblock|Your reason here}} below. &lt;/div&gt;&lt;!-- Template:blocked --&gt;

--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 00:59, 2 September 2022 (UTC)</text>
      <sha1>2ezk8eniwrnmuujlxv002gl3bm4t47t</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Jakobarvidsson</title>
    <ns>3</ns>
    <id>449241</id>
    <revision>
      <id>4669056</id>
      <parentid>4111922</parentid>
      <timestamp>2026-09-06T06:39:01Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669056</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="682" sha1="1kza3z9dsb61eppkwic6ncu9feh7t0k" xml:space="preserve">&lt;div style=&quot;padding:5px; border:1px solid #A9A9A9; background-color:#FFEFD5;{{text default color}}; min-height:40px;&quot;&gt;[[File:Stop x nuvola.svg|40px|left|link=]] '''[[Wikibooks:Blocking policy|You cannot edit]] indefinitely due to disruptive editing'''.  You may appeal this action with a reasonable argument by adding the text &lt;!-- Copy the text as it appears on your page, not as it appears in this edit area. Do not include the &quot;tlx&quot; argument. --&gt;{{tlx|unblock|Your reason here}} below. &lt;/div&gt;&lt;!-- Template:blocked --&gt;

--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 09:34, 20 September 2022 (UTC)</text>
      <sha1>1kza3z9dsb61eppkwic6ncu9feh7t0k</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Frog Bat Good</title>
    <ns>3</ns>
    <id>455870</id>
    <revision>
      <id>4669058</id>
      <parentid>4288337</parentid>
      <timestamp>2026-09-06T06:39:49Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4669058</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4517" sha1="dlegclyq2fgj3jq9m1yt73si3au90mb" xml:space="preserve">&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Frog Bat Good!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}};&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;

&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;

&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;

&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;{{text default color}}; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7;{{text default color}}; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;
[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:33, 11 May 2023 (UTC)</text>
      <sha1>dlegclyq2fgj3jq9m1yt73si3au90mb</sha1>
    </revision>
  </page>
  <page>
    <title>User:Belteshazzar</title>
    <ns>2</ns>
    <id>461127</id>
    <revision>
      <id>4668922</id>
      <parentid>4322344</parentid>
      <timestamp>2026-09-05T12:18:23Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668922</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="807" sha1="8fqapi6ys9zxk997e078kn5pw8nekmp" xml:space="preserve">__NOINDEX__ &lt;table style=&quot;border: 1px solid #aaa; margin: 4px 10%; border-collapse: collapse; background: #f9f9f9;{{Text default color}};&quot; class=&quot;plainlinks&quot; role=&quot;presentation&quot;&gt;&lt;tr&gt;&lt;td style=&quot;border:none; padding:2px 0 2px 0.9em;&quot;&gt;[[File:Wikimedia Foundation logo - vertical.svg|45px|alt=Wikimedia Foundation Logo]]&lt;/td&gt;&lt;td style=&quot;border:none; padding: 0.25em 0.9em; text-align:center;&quot;&gt;'''Consistent with the Terms of Use, {{#ifexpr:floor({{NAMESPACENUMBER}}/2)=1|{{BASEPAGENAME}}|this user}} has been banned by the Wikimedia Foundation from editing Wikimedia sites.''' &lt;br /&gt; Please address any questions to ca[[File:At sign.svg|x15px|middle|link=|alt=@]]wikimedia.org.&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt; {{#ifeq:{{NAMESPACENUMBER}}|3|[[Category:Opted-out of message delivery]]}}[[Category:Wikimedians banned by the WMF]]</text>
      <sha1>8fqapi6ys9zxk997e078kn5pw8nekmp</sha1>
    </revision>
  </page>
  <page>
    <title>Manshu/Chapter 1</title>
    <ns>0</ns>
    <id>464538</id>
    <revision>
      <id>4668967</id>
      <parentid>4620962</parentid>
      <timestamp>2026-09-05T17:33:32Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <comment>typo</comment>
      <origin>4668967</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="124024" sha1="9rqhubuy7z5ipb527pie1mun7cli7gx" xml:space="preserve">{{Nav}}

{{incomplete translation}}
{{translation header
 | language = zh
 | original = 
 | title    = [[../]]
 | author   = Fan Chuo
 | override_editor   = Palace Museum Library
 | translator = Walter Stanish
 | section  =
 | previous =
 | next     =
 | notes    = 
}}

[[zh:蛮书/卷01]]

==Translator's note==
[[File:Hong-Hin Village (Circa very early 1900s).png|thumb|Turn of the 20th century false color postcard showing ''Hong-Hin'', the then Sino-Tonkin border, on the route traversed within this fragment of the text.]][[File:Sampans on the Red River (circa 1900).png|thumb|Turn of the 20th century postcard showing sampans on the Red River.]][[File:Paysage Annamite Montagne et Riviere Postcard (Circa 1900).jpg|thumb|Turn of the 20th century postcard showing the landscape of parts of the Red River, presumably those closer to modern-day Hanoi, possibly around '''Fēngzhōu'''/'''Phong Châu''' (峯州 or 峰州; modern '''Việt Trì''') and '''Dēngzhōu''' (登州).]]

In general for many portions I am confident of a reasonable translation. However, there are also more than a few areas where I am certain there are errors: to what degree, however, I am less sure. In general you should be able to interpret the confidence of translation by the depth of notes and/or mapping around the passage(s) in question. The final portion is particularly murky. The sections are of my own construction.

===Differences with previous Gordon H. Luce Translation===
I am currently (December 2015) reviewing this portion of the translation against [http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=18;node=seap044%3A4;page=root;size=100 Gordon H. Luce's Previous English Translation]. This should allow the detection of errors and/or points of disagreement for further investigation and comment. The following list excludes systemic and stylistic differences and focuses on objective issues.

*'''Correct title'''
::Luce titles the chapter ''Road-stages within the Frontiers of Yunnan'', whereas we use ''Distances within Yunnan and at its Borders''.&lt;ref&gt;The original Chinese uses the two characters 界内 (''jiè nèi'') — meaning literally ''(border) (internal)''. Luce has interpreted this literally as a compound noun phrase (NP), whereas we have interpreted it as a list. Our rationale is straightforward: many distances are described under foreign administrations (eg. well within Annam and Sichuan), thus a list-based interpretation makes more sense.&lt;/ref&gt;

*'''Specific errors'''
**In the note regarding the demarcation of borders, Luce's translation appears to mistranslate the reign year as 43, whereas we calculate 44—45. The recalculated year is placed by us within the body of the translation, whereas Luce omits it entirely.
**After identifying the correct pronunciation of ''Xiefai'' based on the transliterator's note, Luce's translation continues to identify the place name using a modern Mandarin pronunciation (''Jumie'').
**Luce's translation improperly assumes intermediate place names and place name suffixes while describing the route from Annam to Guyong, specifically creating the nonexistant place ''Hsia-pu'' and the nonexistant suffix ''-pu'' to Guyong. This is because Luce failed to understand that there was a section of rapids in this part of the river forcing dismount from boats, and the ''-pu'' he could not comprehend was emphasizing walking to compensate rather than travel by boat.
**Luce drops the &quot;via ''Denglu''&quot; place name entirely as the route proceeds from ''Guyong''.
**Luce wrongfully asserts ''Jiangchuan'' as 'District headquarters', with no evidence whatsoever.
**Luce wrongfully reads the last character of the place name ''Bái​shì​'' (白士) — ie. 士 ''shì​'' — as the visually similar and relatively common yet distinct character 土 (''tǔ''). He also erroneously provides this mistaken version in handwritten Chinese.
**Luce reads the ancient Sichuan prefecture toponym 巂 as ''sui'' instead of ''xī'', which according to my dictionary should be the correct reading.
**Luce misreads the description of inspectors on the Sichuan portion of the Chengdu to Yunnan route as &quot;official civil and military&quot;.&lt;ref&gt;From 將軍專知 which can be conceived as (challenge) (particular or focus) (knowledge) .. the 軍 character losing its military sense entirely.&lt;/ref&gt;
**Luce runs together the interpretation of subsequent statements regarding areas &quot;beyond&quot; (meaning under non-Chinese control — ie. west of) ''Yaozhou'' (modern ''Yaoan'', north-west of ''Chuxiong'') and the roads to the modern Guizhou and Guangxi regions.
**While describing the upper Yangtse in the route toward modern Dali from modern Sichuan, Luce implies that his ''Lu-shui'' is another reference to the ''Lu-chiang'' (瀘江) river rather than a place name, which seems more likely.
**In Luce's translation, a rope-bridge is ascribed to the ''Ch'ing-ch'u-p'u''—''T'sang-p'ang'' portion of the route. However, in the digital version of our Palace Museum Library edition source text, a firmly placed full stop attributes this bridge instead to the ''Jiā​pí​guǎn​'' (伽毗館)—''Qīngqúpù'' (清渠鋪) portion. Without additional sources, we err in favour of our edition but note this point of contention for future readers.
**Luce translates a phrase referring to a route stage in steep mountains as &quot;dangerous and steep&quot; where there is apparently no evidence for the &quot;danger&quot; concept in the text.
**Discussing ''Lòngdòng'' city (弄棟城), Luce ascribes an historical affiliation with both ''Yáozhōu'' (姚州) and ''Xīchuān'' (西川), whereas we consider this an unlikely reading and assert the former as current at the time of writing, and the latter as a previous political affiliation.
**Luce ascribes a third character to the historical military commander-in-chief of ''Yaozhou'', ''Zhāng​ Qián​'' (張乾), calling him ''Chang Ch'ien-t'o''. We side with our source edition's interpretation and consider this character separately.

==Distances within Yunnan and at its Borders (云南界内途程; ''yúnnán jiè nèi túchéng'')==
===Jiāozhǐ (交阯城) to Yángxiefai (陽苴咩城)===
[[File:Tonghai Landscape from Temple (2009).jpg|thumb|right|339px|Photo toward the Tonghai plain (and the 'ocean'-like lakes) from a temple on a mountain, taken 2009 by Christopher, Tania and Isabelle Luna.]]
&lt;!-- [[File:Map for Manshu Chapter 1.svg|thumb|center|599px|Modern satellite map of the region showing some of the locations discussed within the first portion of this chapter. Note that many of the route's features are labelled in grey, this means the positions are approximate. Only places shown in white are identified with relative confidence.]] --&gt;
{| class=&quot;wikitable&quot; style=&quot;text-align:center; width:80%;&quot;
|-
! scope=&quot;col&quot; | Original &lt;small&gt;pp. [https://archive.org/stream/06061161.cn#page/n7/mode/1up 7]—[https://archive.org/stream/06061161.cn#page/n11/mode/1up 11]&lt;/small&gt;
! scope=&quot;col&quot; | Translation
! scope=&quot;col&quot; | Luce (1961) — &lt;small&gt;pp. [http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=18;node=seap044%3A4;page=root;size=100 4],[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=19;node=seap044%3A4;page=root;size=100 5]+[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=27;node=seap044%3A4;page=root;size=100 13],[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=28;node=seap044%3A4;page=root;size=100 14]&lt;/small&gt;
|-
|安寧城，後漢元鼎二年伏波將軍馬援立銅柱定疆界之所。
|At '''[http://en.wikipedia.org/wiki/Anning,_Yunnan Ān​níng​]''' city (安寧城), in 44—45,&lt;ref&gt;See subsequent former transliterator's note.&lt;/ref&gt; the '''[[:w:Ma Yuan (Han dynasty)|General Mǎ​yuán​]]''' (馬援), titled ''Breaker of the Waves''&lt;ref&gt;Apparently this title has no relationship to the events described in [[Translation:Manshu/Chapter 3#Part Four: The Kingdom of L.C3.A0ngqi.C3.B3ng .28.E6.B5.AA.E7.A9.B9.29 and The Breaking of the Wave .28.E5.8A.8D.E6.B5.AA.29|Chapter 3, Part 4]] as General Mayuan is not involved there. Therefore we are forced to ascertain an assumption that breaking of waves was some form of then-popular metaphor for the subduing of wild tribes, whose periodic military resistance is apparently likened to like waves lapping at the great shore of Chinese civilization.&lt;/ref&gt;, completed the demarcation of the borders with bronze-alloy&lt;ref&gt;Originally I had translated this character, which can mean either copper, brass, or bronze as copper — however after referencing Gordon H. Luce's translation and thinking about weathering effects on metals exposed to the outdoors, I concluded that he was probably more correct in translating this as bronze.&lt;/ref&gt; pillars.&lt;ref&gt;銅柱&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;An-ning city was the place where, in the 2nd year of the Yuan-ting period of the Later Han Dynasty, the Fu-po-chiang-chun (General Subduer of the Waves) Ma Yuan set up bronze pillars to fix the frontier.&lt;/p&gt;
|-
|&lt;span style=&quot;color:#aaa&quot;&gt;(案：馬援定交阯，為後漢光武帝建武十九年事。元鼎乃西漢武帝紀年，後漢並無此號，蓋樊綽失於考據之誤)&lt;/span&gt;
|&lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterators' note: The demarcation of the borders by '''General Mǎ​yuán​''' on behalf of the Later (ie. Eastern) Han Dynasty '''Emperor Guāng​wǔ​dì​''' (光武帝)&lt;ref&gt;Born ''Liú​ Xiù​'' (劉秀), reigned 25—57.&lt;/ref&gt; occurred in the 19th year of that emperor's initial ''Jiànwǔ'' (建武) reign&lt;ref&gt;The Later (ie. Eastern) Han Dynasty '''Emperor Guangwudi''' (光武帝)'s initial ''Jiànwǔ'' (建武) reign lasted from 25—56. His second and final ''Jiànwǔzhōngyuán'' (建武中元) reign lasted from 56—57.&lt;/ref&gt; [ie. 44—45].&lt;ref&gt;Gordon H. Luce's prior translation appear to erroneously state the year here as 43. This appears to be incorrect as if the reign began in the solar year 25, the solar year 26 could have been either lunar year 1 or lunar year 2 of the reign, likewise solar year 46 could have been lunar year number 20 or lunar year number 21 of the reign, and either of the solar years 44 or 45 could have been lunar year number 19 of the reign.&lt;/ref&gt; The year name ''Yuándǐng'' (元鼎) refers only to a reign of the Former (ie. Western) Han Dynasty '''Emperor Hàn​ Wǔ​dì​''' (汉武帝) (ie. 116—111BC). There is no such year under the Later (ie. Eastern) Han Dynasty. This appears to be an error in literary reference of the original author.)&lt;/span&gt;&lt;ref&gt;ie. Possibly the author confused Later (ie. Eastern) Han Dynasty '''Emperor Guāng​wǔ​dì​''' (光武帝) with Former (ie. Western) Han Dynasty '''Emperor Hàn​ Wǔ​dì​''' (汉武帝). However, such an error would be more plausible in later copying, so pointing the finger at the original author from 18th century fragmentary, derived sources seems a little over the top to me!&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;(Comment: We hold that Ma Yuan's fixing of Chiao-chih was an event which occurred in the 19th year of the Chien-wu period of Kuang-wu-ti of the Later Han. (43 A.D.); whereas Yuan-ting was a year-name in the annals of Wu-ti of the Western Han. There is no such year-name in the Later Han Dynasty. It must be a mistake due to Fan Ch'o's negligence in checking his evidence.)&lt;/p&gt;
|-
|去交阯城池四十八日程。
|It takes forty eight days to reach '''Ān​níng​''' (安寧)&lt;ref&gt;Originally I had translated this as 'to the city of Jiāozhǐ' however after reading Luce's translation and comparing it with the direction of described travel, it is in fact clear from context that the reader is supposed to interpret this sentence as 'to reach Anning, from the city of Jiāozhǐ'.&lt;/ref&gt; from the city and lakes&lt;ref&gt;Luce's translation states &quot;moated city&quot; here. While Hanoi's environs were extremely wet — in fact essentially swamp-like — this is not present in the text, which literally says ''(city) (pond or lake)''. Hanoi's water bodies have reduced significantly over time as drainage has occurred — these developments are reviewed cartographically in Jim Goodman's ''A Dragon Still Ascending: 1000 Years of Hanoi'', Thé̂ Giới Publishers (2010), ISBN: 9786047700967 (paperback; 260 pp., ill., maps).&lt;/ref&gt; of '''[http://en.wikipedia.org/wiki/Jiaozhi Jiāozhǐ]''' (交阯城).&lt;ref&gt;ie. An earlier version of [http://en.wikipedia.org/wiki/Hanoi Hanoi], the dominant delta-region settlement for the [http://en.wikipedia.org/wiki/Red_River Red River] in what is now northern [http://en.wikipedia.org/wiki/Vietnam Vietnam]. The route would almost certainly have involved descending to the Red River, probably down one of the valleys in the general vicinity of '''[http://en.wikipedia.org/wiki/Jianshui Jianshui]''' or '''[http://en.wikipedia.org/wiki/Gejiu Gejiu]''', probably after moving south from the lakes of central Yunnan via '''[http://en.wikipedia.org/wiki/Tonghai Tonghai]''', then following the Red River either by foot and mule or perhaps even descending by boat. Early use of boats is well testified in the bronze drum culture of the region, of which historic Jiāozhǐ appears (at least by cursory quantitative analysis and geographic distribution) to have been the pan Southeast Asian center. The bronze drum industry quite likely used tin from the famous vein of '''Gejiu''', which is located en-route between the lake-plateaux of central Yunnan and Jiāozhǐ.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;(An-ning) is 48 day-stages distant from the moated city of Chiao-chih.&lt;/p&gt;
|-
|漢時城壁尚存，碑銘並在。
|Both the wall of the Han period city, and inscribed stelae are still there.&lt;ref&gt;Fan Chuo is writing in the 9th century, thus the walls and inscriptions were allegedly about 800 years old.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;The city-walls and fortifications of the Han period are still extant, and there are also stone inscriptions.&lt;/p&gt;
|-
|苴咩&lt;span style=&quot;color:#aaa&quot;&gt;(上音斜，下符差切)&lt;/span&gt;城，從安南府城至蠻王見坐苴咩城水陸五十二日程，只計日，無裏數。
|It takes 58 days&lt;ref&gt;From '''Jiāozhǐ''' to the modern '''Dali''' region (Nanzhao's seat) via '''Kunming'''. A shared passage northward from the Red River valley to '''Kunming''', then under only ten days between the two, which is quite fast. The shared route from the Red River would was well established by early times: Dian bronzes are clearly attributable to the Jiāozhǐ-region Dongson culture, and the tin vein of '''Gejiu''' is likely to have been exploitated for export downriver to the southeast. To possibly further underscore the importance of this 'southern orientation', the relatively southerly location of the Dian king's tomb (ie. at 石寨山; ''shizhaishan'') — favourable for taxation and defence of this passage — lies at the mountains southeast of Dianchi, as opposed to anywhere near modern '''Kunming''' (then Shanchan/Tuodong) city in the north of the basin... a location which would appear to offer superior access to extensive flat and well-watered potential agricultural tracts receiving greater volumes of sunshine, routes westward toward Nanzhao's seat at '''Xiefai''' ('''Dali'''), and a more comfortable / flatter topography.&lt;/ref&gt; of travel by boat and land&lt;ref&gt;Here is direct evidence of the use of watercraft to transit up the Red River during this period. The phrase used is 水陸 or ''shuǐlù'', roughly translating to 'by water and land'.&lt;/ref&gt; from '''Annam'''&lt;ref&gt;Apparently referring, though, specifically to Jiāozhǐ or the modern '''Hanoi''' region.&lt;/ref&gt; to the barbarian king's city of '''Xiefai''' (苴咩城; lit. '(Place with) Hemp (and the) Bleating (of sheep or goats)';&lt;ref&gt;Though a literal interpretation is not necessarily possible, particularly if in fact this is a transliteration from a non-Chinese language in to Chinese. In more recent times the area is known for both wild hemp and the rearing of goats, however.&lt;/ref&gt; ie. '''[http://en.wikipedia.org/wiki/Dali_City Dali]''') &lt;span style=&quot;color:#aaa&quot;&gt;(Note: The first character 苴 is pronounced ''xie'' (斜),&lt;ref&gt;ie. /ʒɛər/ in my attempt at rendering correctly the IPA pronunciation.&lt;/ref&gt; the second 咩 is pronounced as ''f'' (from 符's ''fu'') + ''a'' or ''ai'' (from 差's ''cha'' or ''chai''​) — ie. ''fa​'' or ''fai​''&lt;ref&gt;ie. either /fa/ or /faɪ/ in my attempt at rendering correctly the IPA pronunciation.&lt;/ref&gt;)&lt;/span&gt;&lt;ref&gt;Note that there is no assigned age for this pronunciation suggestion and that Mandarin has very little to do with a lot of the ancient pronunciation in southern China, so this note — whilst present and translated — should not be taken as gospel, in fact quite the opposite: it needs modern analytical attention from a historically-focused linguists in a range of potentially relevant language families. For what it's worth, here are [http://starling.rinet.ru/cgi-bin/response.cgi?root=config&amp;morpho=0&amp;basename=\data\sintib\stibet&amp;first=1&amp;off=&amp;text_proto=&amp;method_proto=substring&amp;ic_proto=on&amp;text_meaning=&amp;method_meaning=substring&amp;ic_meaning=on&amp;text_chin=&amp;method_chin=substring&amp;ic_chin=on&amp;text_tib=&amp;method_tib=substring&amp;ic_tib=on&amp;text_burm=&amp;method_burm=substring&amp;ic_burm=on&amp;text_kach=&amp;method_kach=substring&amp;ic_kach=on&amp;text_lush=&amp;method_lush=substring&amp;ic_lush=on&amp;text_lepcha=&amp;method_lepcha=substring&amp;ic_lepcha=on&amp;text_kir=&amp;method_kir=substring&amp;ic_kir=on&amp;text_comments=&amp;method_comments=substring&amp;ic_comments=on&amp;text_any=%E8%8B%B4&amp;method_any=substring&amp;sort=proto&amp;ic_any=on alleged Proto-Sino-Tibetan, Sino-Tibetan and Sino-Caucasian etymologies of 苴 (alleged ''xie'')] and [http://ctext.org/dictionary.pl?if=en&amp;char=%E5%92%A9 the ctext.org entry for 咩 (alleged ''fa'' or ''fai'')].&lt;/ref&gt; - ie. [http://en.wikipedia.org/wiki/Nanzhao Nanzhao]. On such a journey, one may count but the days, not the miles.&lt;ref&gt;The phrase 只計日，無裏數 comes across to me as if Fan Chuo is dismissing the intermediary wilderness as vast and uncivilized.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From the prefectural capital of Annam, to reach Chu-mieh city (The first syllable is pronounced hsieh. The second is ''fu''+ ''ch'a'' (or ''ch'ai''; i.e. ''fa'' or ''fai'').), the seat of the ''Man'' king, by water and land route, is 52 day-stages. We can only reckon the days, without giving the number of ''li''. (i.e. the mileage).&lt;/p&gt;
|-
|從安南上水至峰州兩日，至登州兩日，至忠誠州三日，至多利州兩日，至奇富州兩日，至甘棠州兩日，至下步三日，至黎武賁柵四日，至賈&lt;span style=&quot;color:#f00&quot;&gt;男&lt;/span&gt;步五日。
|From '''Annam''' one travels upriver to '''Fēngzhōu'''/'''Phong Châu''' (峯州 or 峰州; modern ''Việt Trì'')&lt;ref&gt;''Phong Châu'' (峯州 or 峰州; a ruined city near Bạch Hạc (白鹤? See [http://jnxb.jnu.edu.cn/skb/CN/article/downloadArticleFile.do?attachType=PDF&amp;id=743 source].) District, Việt Trì, Phú Thọ Province, Vietnam) was originally the capital city of Văn Lang (文郎; the then northern-Vietnamese state centered on the Red River). Supposedly founded in 2879 BCE, it existed until 258 BCE when it was invaded by the Âu Việt tribe (known to the Chinese as the ''Kingdom of Eastern Ou'' (東甌), and associated with Tai/Zhuang peoples). The Âu Việt king, Thục Phán, proclaimed himself King An Dương Vương and reigned from a more easterly location, just east of modern Hanoi at [https://en.wikipedia.org/wiki/C%E1%BB%95_Loa_Citadel Cổ Loa]. Thus, by the time our author mentions the location in passing as two days upriver from Annam, the elevated status of ''Phong Châu'' (峯州 or 峰州) was all ancient history and evidently the name had merely persisted for the general area. Today, the name refers to the nearby but separate Phong Châu district, Phú Thọ province. Geographically, this is the southern (encompassed) side of a major bend in the Red River after being joined by a major tributary, the [https://en.wikipedia.org/wiki/Black_River_%28Asia%29 Black River] (''sông Đà''). As such, it is a location that would have been ideal for tridirectional trade, is probably highly fertile, would have provided an easy point of taxation, and was thus a natural early political center. Note that ''Việt Trì'' and the original ruins are apparently on the northern side of the river, whereas modern ''Phong Châu'' is on the southern side. While studies have almost certainly been done, I have not consulted any, so do be aware that it is not wholly unlikely that the river's course may have moved before drawing any conclusions from this disparity.&lt;/ref&gt; for two days, onward to '''Dēngzhōu​''' (登州)&lt;ref&gt;Though distances would suggest approximately the modern location of [https://en.wikipedia.org/wiki/Ph%C3%BA_Th%E1%BB%8D_Province Phú Thọ] and probably no further than [https://en.wikipedia.org/wiki/Y%C3%AAn_B%C3%A1i Yên Bái], at the time of writing, using available online sources, no firm identification appeared to be possible. (Partly this is because the area around Penglai, to the west of Yantai in northern China's Shandong province is far better known by the same characters and widely referenced in Chinese history and literature.) However, given that the next identification of Hekou (modern China/Vietnam border) is made with some confidence, perhaps this was indeed slightly beyond Yên Bái, for example in the region around Mau Dong / Mau A. Note there is apparently [http://epress.nus.edu.sg/msl/entry/444?hl=%22Deng+Subprefecture%22 a passing reference] to a local Dengzhou in the (much later) ''Míngshǐlù'' (明史录; usually in English ''Records of the Ming Dynasty''; lit. ''Historical Records of the Ming Dynasty'').&lt;/ref&gt; for two days, onward to '''Zhōngchéngzhōu''' (忠誠州)&lt;ref&gt;Possibly modern day [https://en.wikipedia.org/wiki/Hekou_Yao_Autonomous_County Hekou], ie. the modern China/Vietnam border.&lt;/ref&gt; after three days, onward to '''Duō​lì​zhōu​''' (多利州)&lt;ref&gt;Unidentified.&lt;/ref&gt; after two days, onward to '''Qífùzhōu''' (奇富州)&lt;ref&gt;Unidentified.&lt;/ref&gt; after two days, onward to '''Gāntángzhōu''' (甘棠州)&lt;ref&gt;Apparently [http://jnxb.jnu.edu.cn/skb/CN/article/downloadArticleFile.do?attachType=PDF&amp;id=743 previously identified] as about 2/3 of the way to the modern border, beyond the town of Yên Bái but not close to the town of Lào Cai. French maps seem to confirm the identification of the site as '''Bảo Hà''', Bảo Yên District, the very first place one comes to after entering Lào Cai Province. In addition, the maps show rapids on the Red River following this point which would explain the walking. Certain French colonial era postcards from the early 20th century appear to spuriously identify 甘棠 with Lào Cai — labels read ''Laokay'' but visible Chinese characters in the photograph read 甘棠 — but this makes sense if they were referring to the province since '''Bảo Hà''' lies within.&lt;/ref&gt; after two days, continuing for a further three days by walking, onward to '''Líwǔbìzhà''' (黎武賁柵; [https://en.wikipedia.org/wiki/Hekou_Yao_Autonomous_County Hekou]?)&lt;ref&gt;Literally 'Black military bright fence', suggesting a wall, frontier or bastion. Unidentified, but possibly modern [https://en.wikipedia.org/wiki/Hekou_Yao_Autonomous_County Hekou], lit. 'River Mouth', at the confluence of the Red River and one of its tributaries, the ''Nam-Thi'' (Name in local Tai language families; ''Nam'' means river). French photographs from the early 20th century show that the presentation of the confluence is rather sudden and oblique, not unlike a wall, and as a confluence would make a perfect location for collecting tolls, surveying transit and participating in trade. Note also that the pronunciation is a guess: the third character could allegedly be any of ''bì bēn féi fén fèn'' ... but no clues are apparent as to when or why. Luce's translation opts for one of the ''fen'' options and calls it ''Li-wu-fen stockade''.&lt;/ref&gt; after four days, and finally onward to '''Gǔyǒng''' (賈勇; lit. 'Brave Merchant')&lt;ref&gt;The source writes '''Gǔ​nán''' (賈男) — this would mean 'merchant man' and is unidentified anywhere. However, it looks ''a lot'' like the place 賈勇 (lit. 'Brave Merchant') below, and is thus potentially a miswritten character for the same place. In Luce's translation, it is given the latter's written form and pronunciation (though erroneously granted a ''-pu'' suffix due to Luce's misunderstanding of this area of the text). Therefore, the error is probably in our version of the source text (ie. an error likely originating in the digitization of the original, which would not exist in the paper or photographic derivative form of the same movable type produced version Luce used), so I count this error as very probable and ignore the spurious name. Note also that the subsequent comment states that a watercourse has been followed to this point, but Guyong in particular may be up a tributary. This lesser water-body would account for the switch to walking.&lt;/ref&gt; by walking for five days.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From Annam, going upstream, to reach Feng-chou is 2 days. To reach Teng-chou is 2 days. To reach Chung-ch'eng-chou is 3 days. To reach To-li-chou is 2 days. To reach Ch'i-fu-chou is 2 days. To reach Kan-t'ang-chou is 2 days. To reach Hsia-pu is 3 days. To reach Li-wu-fen stockade is 4 days. To reach Ku-yung-pu is 5 days.&lt;/p&gt;
|-
|已上二十五日程，並是水路。
|The above takes twenty five days, and follows the watercourse.&lt;ref&gt;This appears to imply that the rest of the route continues from here, overland. Luce's translation erroneously implies the above was all by water route, whereas in fact that was both impossible and not-so-explicitly described in its aversion by the text.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;The above 25 day-stages are all by water-route.&lt;/p&gt;
|-
|大中初，悉屬安南管系，其刺史並委首領勾當。
|In 846 (at the beginning of the Dazhong period&lt;ref&gt;Tang Xuān Zōng (唐宣宗)'s reign, 846–859.&lt;/ref&gt;), the area became a dependency of Annam,&lt;ref&gt;Thus a possession of the central Chinese imperial government.&lt;/ref&gt; and began to be governed,&lt;ref&gt;This may be seen to imply that, rather than wresting the area from some foreign power, it was brought in to governance from a previously ungoverned, non-state situation.&lt;/ref&gt; but the Annam provincial governor had illicit dealings with the local chiefs.&lt;ref&gt;Luce asserts &quot;... might also depute the native chiefs to take a hand in management&quot;, though such a focus on delegation does not seem to be evidenced in the text, which merely states 委首領勾當 — literally ''(trust or appoint, send, commission) (chieftains) (illicit dealings)''.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;At the beginning of the ''Ta-chung'' period (847-859)(these parts) were all dependent on and attached to the administration of Annam. But the ''Tz'u-shih'' (of Annam) might also depute the native chiefs to take a hand in the management.&lt;/p&gt;
|-
|大中八年，經略使苛暴，川洞離心，疆內首領旋被蠻賊誘引，數處陷在賊中。
|In the eighth year of the Dazhong era (ie. 853), the [https://zh.wikipedia.org/wiki/%E7%B6%93%E7%95%A5%E5%AE%89%E6%92%AB%E4%BD%BF Emperor's Official]&lt;ref&gt;Luce put me on the right path here: I had failed to recognize 經略使 as an official position and completely munged this paragraph's translation!&lt;/ref&gt; was cruel, such that the [population of the] river-valleys and caves&lt;ref&gt;Implying the total geography of the area.&lt;/ref&gt; within the frontier became unsettled and a few of them fell to the deceitful enticements of the treacherous barbarians.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;In the 8th year of ''Ta-chung'' (854 A.D.) the ''Ching-lueh-shih'' (Imperial General) was cruel and oppressive. The native areas (lit. valleys and ravines) were divided in heart. The native chiefs within the frontiers (of China) were subsequently seduced by the ''Man'' rebels; and this caused a number of places to fall in to rebel hands.&lt;/p&gt;
|-
|從賈勇步登陸至矣符管一日。
|Walking from '''Gǔyǒng''' (賈勇) via '''Dēnglù''' (登陸)&lt;ref&gt;This place name is wholly omitted by Luce.&lt;/ref&gt; to '''Yǐfúguǎn''' (矣符管; lit. 'Yifu Station') takes a day.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From Ku-yung-pu, going up by land, to reach I-fu-kuan is 1 day.&lt;/p&gt;
|-
|從矣符管至曲烏館一日，至思下館一日，至沙&lt;span style=&quot;color:#f00&quot;&gt;雙&lt;/span&gt;館一日，至南場館一日，至曲江館一日，至通海城一日，至江川縣一日，至進寧館一日，至鄯闡&lt;span style=&quot;color:#f00&quot;&gt;柘&lt;/span&gt;東城一日&lt;span style=&quot;color:#aaa&quot;&gt;(案：「柘東，」《舊唐書》及《通鑒》俱作「拓東胡」，三省雲，言開拓東境也，《新唐書》作「柘」，從木，與此同)&lt;/span&gt;。
|From '''Yǐfúguǎn''' to '''Qūwūguǎn''' (曲烏館; lit. 'Hunched Crow House'&lt;ref&gt;Inexplicably this is suddenly translated as &quot;Chu-wu Inn&quot; by Luce, whereas previous 館 are suffixed ''-kuan''. Subsequent places follow the new pattern.&lt;/ref&gt;) takes one day, '''Sīxiàguǎn''' (思下館) another, '''Shāzhīguǎn''' (沙[隹+又]館&lt;ref&gt;It seems here that the source text here has another incorrect character. Luce's translation [http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=27;node=seap044%3A4;page=root;size=100 specifies a character in note number 26, page 13] that is apparently not recognized in Unicode, that of 隹 (&quot;a bird&quot;) at the top, and 又 (&quot;a right hand&quot;) at the bottom. Fortunately, [http://www.zhongwen.com/ zhongwen.com] has an entry for this under ''zhī'', which appears to accord with Luce's Wade Giles romanization and clarify the mystery.&lt;/ref&gt;; lit. 'Station at the sandy place for bird or small animal catching') another, '''Nánchǎngguǎn''' (南場館)&lt;ref&gt;Guessing by distance, possibly a town in the northern Jianshui plateau, or Jianshui itself? Apparently Jianshui was called 惠历 (Huili) by Nanzhao, who established it in the year 810 under the command of Tonghai. To them, then, it would have been a southerly place ... perhaps the origin of the 南 in 南場館 — which can be literally interpreted as something vaguely like 'central-office of a southern place'. I am unable to find any secondary sources attesting to a Nanchangguan or Nanchang in the area, though there is a Nanchang southwest of Dali that is certainly not the place referenced.&lt;/ref&gt; another, '''Qūjiāngguǎn''' (曲江館; lit. 'Meandering River';&lt;ref&gt;Luce's literal translation, and a good one. Why he decides to provide one for this place name and not others is lost to the mists of time!&lt;/ref&gt; ie. modern Qujiang&lt;ref&gt;Under Jianshui's administration — 建水县曲江镇 — and located just across the mountains from Tonghai on the next plain south. Note that the old road may have been first walking west, then turning north up the more westerly canyon via ''Lishan'' village; the new (≈2010) freeway from Tonghai to Jianshui takes a far more easterly path, ie. straight north out of Qujiang.&lt;/ref&gt;) another, '''Tōnghǎichéng''' (通海城; lit. 'City of the Connection to the Oceans',&lt;ref&gt;So called not for its connection to the Red River and onward to the South China Sea (南海), but rather for its function as a natural gateway for those journeying from lands to the south, including the Red River and important towns like Jianshui and Gejiu toward the great lakes of Yunnan's central plateaux.&lt;/ref&gt; ie. modern [https://en.wikipedia.org/wiki/Tonghai Tonghai]) another, '''Jiāngchuānxiàn''' (江川縣; lit. 'River-plain';&lt;ref&gt;Luce inexplicably presents this in supposed literal translation as 'District headquarters' — with apparently no basis whatsoever!&lt;/ref&gt; ie. [https://en.wikipedia.org/wiki/Jiangchuan_County Jiangchuan]) another,  '''Jìnníngguǎn''' (進寧館; ie. modern [https://en.wikipedia.org/wiki/Jinning_County Jinning County]) another, '''Shànchǎn / Tuòdōng Chéng''' (鄯闡拓東城; lit. 'The city of Shanchan / Tuodong',&lt;ref&gt;The source had mistranscribed 柘 in place of 拓 — otherwise, the portion &quot;...柘東城&quot; would refer to the city to the east of the 「柘」 (thorny tree, possibly a mulberry bush), which sounds rather spurious.&lt;/ref&gt; ie. modern [https://en.wikipedia.org/wiki/Kunming Kunming]) another. &lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterator's note: The first character of 「柘東」 occurs as 「拓」 with the 「扌」 (hand) radical at left both within the ''History of the Early Tang Dynasty'' (舊唐書) and the later Song Dynasty text ''Comprehensive Mirror in Aid of Governance'' (通鑒; [https://zh.wikisource.org/wiki/%E8%AE%80%E9%80%9A%E9%91%92%E8%AB%96 full text on Chinese wikisource])&lt;ref&gt;By the famous historian '''Sīmǎ Guāng''' (司馬光)]. '''Hú Sānxǐng''' (胡三省), a respected commentator on the ''Comprehensive Mirror in Aid of Governance'' (通鑒) who lived at the end of the Song and the beginning of the Yuan Dynasty.&lt;/ref&gt; which further states that this means &quot;[place of] eastward development&quot;.). The ''History of the Later Tang Dynasty'', by contrast, records the character 「柘」 with the 「木」 (tree) radical at left [which is likely to be in error] as here.&lt;ref&gt;This implies that this portion of the text may have been lifted from the ''History of the Later Tang Dynasty'' (新唐書) by the compilers of this edition of the text, which is known to have been reconstructed from disparate portions. Someone with more interest than me can definitely go do more research on probable origins of the various portions of the text.&lt;/ref&gt;)&lt;/span&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From I-fu-kuan, to reach Ch'u-wu Inn is 1 day. To reach Ssu-hsia Inn is 1 day. To reach Nan-ch'ang Inn is 1 day. To reach Ch'u-chiang (Meandering river) Inn is 1 day. To reach Chin-ning Inn is 1 day. To reach Shan-shan Che-tung city is 1 day. (Comment: We hold that Che-tung, both in the ''Old T'ang history'' and in the ''T'ung chien'', is written ''Chih-tung''. Hu San-sheng says it means to open and take the eastern frontier. The ''New T'ang history'' writes che with the tree radical, as here.)&lt;/p&gt;
|-
|從&lt;span style=&quot;color:#f00&quot;&gt;柘&lt;/span&gt;東節度城至寧寔館一日，安寧館本是漢寧郡城也。
|From the '''Tuòdōng City''' (拓東) military commandery to '''Níngshíguǎn''' (寧寔館)&lt;ref&gt;Uncertain but perhaps this was this supposed to be Anning? It would make a lot more sense.&lt;/ref&gt; takes a day. '''Ānníngguǎn''' (安寧館) was known as '''Níngjùn City''' (寧郡城; lit. 'Peaceful Capital City') during the Han Dynasty.&lt;ref&gt;Originally I had translated this differently and probably incorrectly, taking 郡 to be a region and 漢寧 to be a descriptive adjectival phrase, — ie. &quot;capital of the (pacified [and] Han Chinese [occupied]) (region) [in contrast to other areas]&quot;. However, after reviewing Luce's work, I think his interpretation is far more straightforward and likely to be correct.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From the ''Chieh-tu'' city of Che-tung, to reach Ning-shih Inn is 1 day. An-ning Inn originally was the Ning-chun city of the Han dynasty.&lt;/p&gt;
|-
|從安寧城至龍和館一日，至沙雌館一日，至曲館一日，至沙卻館一日，至求贈館一日，至雲南驛一日，至波大驛一日，至白嚴驛一日，至龍尾城一日。
|From '''Ānníngchéng''' (安寧城; lit. 'Peaceful City') to '''Lónghéguǎn''' (龍和館; lit. 'Station of Harmonious Dragons') is a day, '''Shācíguǎn''' (沙雌館) another, '''Qūguǎn''' (曲館) another, '''Shāquèguǎn''' (沙卻館) another, '''Qiúzèngguǎn''' (求贈館) another, '''Yúnnányì''' (雲南驛&lt;ref&gt;Luce translates this as &quot;Yunnan post-station&quot;, a trend here established for subsequent ''-yi'' placenames. I do not agree with reading so much in to the suffix here.&lt;/ref&gt;) another, '''Bōdàyì''' (波大驛) another, '''Báiyányì''' (白嚴驛) another, '''Lóngwěichéng''' (龍尾城; lit. 'Dragon's tail city', ie. modern [https://en.wikipedia.org/wiki/Xiaguan Xiaguan] near [https://en.wikipedia.org/wiki/Dali_City Dali]) another.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From An-ning city, to reach Lung-ho Inn is 1 day. To reach Sha-tz'u Inn is 1 day. To reach Ch'u Inn is 1 day. To reach Sha-ch'i Inn is 1 day. To reach Ch'iu-tseng Inn is 1 day. To reach Yunnan post-station is 1 day. To reach Po-ta post-station is 1 day. To reach Po-yen post-station is 1 day. To reach Lung-wei (Dragon's Tail) city is 1 day.&lt;/p&gt;
|-
|李謐伐蠻於龍尾城，誤陷軍二十萬眾，今為萬人冢。
|''Lǐ Mì'' (李謐)&lt;ref&gt;Though, at this point in the text, it seems strange to suddenly switch to descriptions of unidentified characters. After some reference to other sources, this appears to be the Tang general who invaded from the north in 754 but was defeated.&lt;/ref&gt; attacked&lt;ref&gt;伐; from other sources we learn this occurred in the year 754.&lt;/ref&gt; the barbarians&lt;ref&gt;蠻; referring to the Nanzhao kingdom's people.&lt;/ref&gt; at '''Lóngwěi''' (龍尾城), wasting&lt;ref&gt;This seems the most apt translation for 誤陷軍 (''wùxiànjūn'') which could be interpreted a few ways. It should be possible to more confidently translate the verb given additional texts of the era for context, or a more experienced translator.&lt;/ref&gt; a great army&lt;ref&gt;The text is actually states 二十萬 (20 x 10,000 = 200,000), though as much classical Chinese is loose with numbers, translating to give a large impression without the stupendous figure may be more accurate. Apparently others have re-estimated the figure at 100,000, though basically all we can reasonably conclude is &quot;a great number&quot; or &quot;a large army&quot;.&lt;/ref&gt; of underlings,&lt;ref&gt;The text uses the character 眾 (see [https://en.wiktionary.org/wiki/%E7%9C%BE English Wiktionary]), which based upon the glyph's upper portion (an eye) and the lower portion (three people) is presumably an antiquated form of noun, here used to indicate militarily commanded soldiers.&lt;/ref&gt; who are now&lt;ref&gt;今為&lt;/ref&gt; but 10,000 graves.&lt;ref&gt;萬人冢&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Li Mi attacked the ''Man'' at the city of ''Lung-wei''. By blundering he lost altogether 200,000 men of his army. It is now called &quot;The Grave of a Myriad Men&quot;.&lt;/p&gt;
|-
|至陽&lt;span style=&quot;color:#aaa&quot;&gt;(「陽」，《新唐書》作「羊」)&lt;/span&gt;苴咩城一日&lt;span style=&quot;color:#aaa&quot;&gt;(蠻王從大和城移在苴咩城。案「蠻王至咩城」十一字，原本誤入正文，今改正)&lt;/span&gt;
|It takes one day to '''Yángxiefai''' (陽苴咩城) city. &lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterator's note: The ''[http://en.wikipedia.org/wiki/New_Book_of_Tang History of the Later Tang]'' (新唐書) uses the character 羊 in place of 陽.&lt;ref&gt;As an aside, it may be meaningful to note that the lead compiler of that official dynastic history, Ouyang Xiu (歐陽脩), has a surname that according to his own, respected historical research was [https://en.wikipedia.org/wiki/Ouyang#History associated with far southern China] including regions adjacent to Yunnan such as northern Vietnam (aka. Jiāozhǐ/Annam) and Guangxi. Conjecture: being a historian with family roots in the region, this change ''may'' have been deliberate, for example to reflect or record simplification in popular or short-hand use of the period.&lt;/ref&gt;)&lt;/span&gt; &lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterator's note: Note that 11 characters 「蠻王從大和城移在苴咩城」 indicating that the Barbarian King had moved from '''Dà​hé''' (大和) to '''Xiefai''' (苴咩) were mistakenly inserted in to the main text and were not present in the original — these have accordingly been removed [to this comment&lt;ref&gt;Though in typical clarity no further statement on source, time or evidence is made! To make matters worse, our digital source text does not even make it clear which compiler wrote the note originally or in modified form.&lt;/ref&gt;].)&lt;/span&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;To reach Yang Chu-mieh city is 1 day. (Comment: We hold that ''yang'' is written ''yang'' in the ''New T'ang history''.) The ''Man'' king has moved his residence from Ta-ho city to Chu-mieh city. (Comment: We hold that the 11 characters, from '''Man'' king' to 'Mieh city' in the original edition were wrongly inserted in to the main body of the text. Now we have altered and corrected it.)&lt;/p&gt;
|}

===Chéngdū (成都府) to Yángxiefai (陽苴咩城)===
&lt;!-- [[File:Map_for_Manshu_Chapter_1_-_Part_2.svg|thumb|center|509px|Modern satellite map of the region showing some of the locations discussed within the second portion of this chapter. Note that the majority of the route's features are labelled in grey, this means the positions are approximate (in the middle portion, extremely). Only places shown in white are identified with relative confidence.]] --&gt;
Note that the borderland region between modern Yunnan proper and the Sichuan basin through which this section's route passes is historically inhabited by the Yi. The Yi were both powerful and independent until after the Yuan Dynasty when their princess made a deal with the invading Mongols. They wore impressive armour, examples of which can be seen online [http://scudm.scu.edu.cn/bwgen/modules/EDUCATION/NewsView.jsp?id=821 here at Sichuan University Museum] and [https://www.peabody.harvard.edu/node/2096 here at Harvard], or in person at the Anthropology Museum of Yunnan University on Beimenjie in Kunming.

====Chéngdū (成都府) to the Yúnnán (雲南) boundary====
{| class=&quot;wikitable&quot; style=&quot;text-align:center; width:80%;&quot;
|-
! scope=&quot;col&quot; | Original &lt;small&gt;pp. [https://archive.org/stream/06061161.cn#page/n11/mode/1up 11]—[https://archive.org/stream/06061161.cn#page/n13/mode/1up 13]&lt;/small&gt;
! scope=&quot;col&quot; | Translation
! scope=&quot;col&quot; | Luce (1961) — &lt;small&gt;pp. [http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=19;node=seap044%3A4;page=root;size=100 5],[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=20;node=seap044%3A4;page=root;size=100 6],[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=21;node=seap044%3A4;page=root;size=100 7]+[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=28;node=seap044%3A4;page=root;size=100 14]&lt;/small&gt;
|-
|自西川成都府至雲南蠻王府、州、縣、館、驛、江、嶺開塞，並裏數計二千七百二十裏。
|From '''Chéngdū''' (成都府) city in the '''Xīchuān''' (西川)&lt;ref&gt;Apparently a historical administrative region denoting borderlands from what is now modern western Sichuan.&lt;/ref&gt; region to the capital of the barbarian&lt;ref&gt;Meaning Nanzhao.&lt;/ref&gt; prince of '''Yúnnán''' (雲南) one crosses cities,&lt;ref&gt;府&lt;/ref&gt; prefectures,&lt;ref&gt;州&lt;/ref&gt; counties,&lt;ref&gt;縣&lt;/ref&gt; towns,&lt;ref&gt;館&lt;/ref&gt; stations,&lt;ref&gt;驛&lt;/ref&gt;, rivers,&lt;ref&gt;江&lt;/ref&gt; and mountain ranges&lt;ref&gt;嶺&lt;/ref&gt; over a total distance of 2720 ''li''.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From Ch'eng-tu prefecture of Hsi-ch'uan, to reach the prefectural headquarters of the ''Man'' king of Yunnan, (including) the ''chou'' (divisions), ''hsien'' (districts), inns, post-stations, rivers, mountain-ranges, and frontier-passes, the total mileage amounts to 2,720 ''li''.&lt;/p&gt;
|-
|從府城至雙流縣二江驛四十裏，至蜀州新津縣三江驛四十裏，至延貢驛四十裏，至臨邛驛四十裏，至順城驛五十裏，至雅州百丈驛四十裏，至名山縣順陽驛四十裏，至嚴道縣延化驛四十裏，從延化驛六十裏至管長賁關，從奉義驛至雅州界榮經縣南道驛七十五裏，至漢昌六十裏&lt;span style=&quot;color:#aaa&quot;&gt;(案：此句上有脫文)&lt;/span&gt;，屬雅州，城名葛店。
|From '''Chengdu''' to '''Shuāng​liú​xiàn''' (雙流縣; lit. Double Flow [River] county-town)&lt;ref&gt;A modern place exists with the same name outside of Chengdu in Sichuan province (四川省成都市双流县; circa 30.447N,104.03E).&lt;/ref&gt;) there are two river crossings over a distance of 40 ''li''. To '''Xīn​jīn​xiàn''' (新津縣;  lit. [County of the] New [water or ferry] Crossing&lt;ref&gt;Again, outside of Chengdu in Sichuan province (四川省成都市新津县).&lt;/ref&gt;) of '''Shǔ​zhōu​''' (蜀州&lt;ref&gt;[https://zh.wikipedia.org/wiki/%E8%9C%80%E5%B7%9E_(%E5%94%90%E6%9C%9D) Apparently] administered at the time from modern Chongzhou (崇州市), currently north-west of Xīn​jīn.&lt;/ref&gt;) there are three river crossings over a distance of 40 ''li''.&lt;ref&gt;Presumably referring in part to the 岷江 (Mínjiāng) and the 大渡河 (Dàdù Hé) — one of the former's tributaries —, and possibly the 雅砻江 (Yǎlóngjiāng). The identity of the fourth river remains unclear, though no doubt good studies of the former flows of rivers in this region have been made, particularly given the proximity to China's [https://en.wikipedia.org/wiki/Dujiangyan_irrigation_system famous early irrigation project at 都江堰] (Dūjiāngyàn), so there is hope for a positive identification.&lt;/ref&gt; To '''Yán​gòng​''' (延貢&lt;ref&gt;Vaguely possible literal meaning 'delayed tribute', very questionably referring to poor punctuality in taxation? In any event, seems to equate with the modern village 四川省成都市邛崃市冉义镇延贡村 at 30.4286N,103.649E.&lt;/ref&gt;) station it is a further 40 ''li'', to '''Lín​qióng​''' (臨邛&lt;ref&gt;The place name means literally 'the overlooking mound' or 'hillock with a view'. [http://baike.baidu.com/link?url=RGI__MEyATZn3Ql0q7z0rdWk7Px4kXWKLvHZyu4s10tZNcozvc8y_GjYbDOJRzXs8dIyAVuTvZI8Ie3IUW_cGq Identified historically at Baidu Baike], though the final definition is a few hundred years before our period.&lt;/ref&gt;) station a further 40 ''li'', to '''Shùn​chéng​''' (順城) a further 50 ''li'', to '''Bǎi​zhàng​''' (百丈&lt;ref&gt;Conjecture: 丈 here possibly refers to the Chinese measure, being 3.3 meters, if so the literal translation of the place would be '330 meter station', which could refer to the approximate length of the settlement along the road.&lt;/ref&gt;) station of '''Yǎ​zhōu​''' (雅州) a further 40 ''li'', '''Shùn​yáng​''' (順陽&lt;ref&gt;Literal geographical meaning could be 'along the sunny side [of the mountain]'.&lt;/ref&gt;) station of '''Míng​shān​xiàn''' (名山縣&lt;ref&gt;Literally 'bright mountain county'.&lt;/ref&gt;) a further 40 ''li'', '''Yán​huà​''' (延化&lt;ref&gt;Conjecture: Possibly referring to the length of seasonal change, for example as indicated by an abnormal length of foliage on deciduous trees in the local microclimate.&lt;/ref&gt;) station of '''Yándào​xiàn​''' (嚴道縣&lt;ref&gt;Yandao county, possibly literal meaning 'tight or well-sealed road', which could suggest a prominent mountain pass, military garrison and/or customs levy.&lt;/ref&gt;) a further 40 ''li''. From '''Yán​huà​''' station to '''Guǎn​chángbì​guān​''' (管長賁關&lt;ref&gt;This toponym is possibly of unlikely length and could alternatively be interpreted as 'Biguan' of 'Guanchang [area]', ie. 'bright pass of everwatch [area]'. However, the style of surrounding text suggests that it is indeed a four-character toponym, thus a literal meaning would be 'Everwatch Bright Pass'.&lt;/ref&gt;) it is 60 ''li''. From '''Fèngyì​​''' (奉義&lt;ref&gt;As yet not introduced, possibly synonymous with the pass just mentioned.&lt;/ref&gt;) station to '''Nándào​​''' (南道&lt;ref&gt;Literally 'Southerly Road'.&lt;/ref&gt;) station of '''Róng​jīng​''' (榮經&lt;ref&gt;Modern Róng​jīng​ County in Ya'an (四川省雅安市荣经县).&lt;/ref&gt;) county on the '''Yǎ​zhōu''' (雅州&lt;ref&gt;Apparently the then-name of the capital of the broader district with the same name, on the site of modern Ya'an (四川省雅安市). [http://zh.wikipedia.org/wiki/%E9%9B%85%E5%B7%9E#.E5.94.90.E4.BB.A3.5B1.5D A history is available] at Chinese Wikipedia.&lt;/ref&gt;) border&lt;ref&gt;界&lt;/ref&gt; it is a further 75 ''li'', it is a further 60 ''li'' to '''Hàn​chāng​''' (漢昌&lt;ref&gt;Can't find any clear references online, except north-west of Chengdu which seems incorrect though may indicate that a new route from Chengdu is under discussion... we shall see with subsequent placenames.&lt;/ref&gt;), &lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterator's note: There appear to be some characters missing here)&lt;/span&gt; which is subordinate to '''Yǎ​zhōu'''&lt;ref&gt;ie. Modern Ya'an (四川省雅安市).&lt;/ref&gt; and whose city is called '''Gě​diàn​''' (葛店&lt;ref&gt;Literally 'hemp cloth selling place'. I can't find any clear references to this place online, except in far-flung places that are clearly incorrect identifications, or in copies of this same text. Therefore, its location remains a mystery, but it must be nearby Róng​jīng County (四川省雅安市荣经县)​ to the south or southwest of modern Ya'an (四川省雅安市).&lt;/ref&gt;).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From the prefectural city (ie. Ch'eng-tu), to reach Erh-chiang post-station of Shuang-liu-hsien (district), is 40 ''li''. To reach San-chiang-i (Three Rivers post-station) of Hsin-ching-hsien (New Ford district) of Shu chou is 40 ''li''. To reach Yen-kung post-station is 40 ''li''. To reach Lin-chiung post-station is 40 ''li''. To reach Shun-ch'eng post-station is 50 ''li''. To reach Pai-chang (One Thousand Feet) post-station of Ya-chou, is 40 ''li''. To reach Shun-yang post-station of Ming-shan district is 40 ''li''. To reach Yen-hua post-station of Yen-tao district is 40 ''li''. From Yen-hua post-station (one goes) 60 ''li'' and reaches Kuan-ch'ang-fen-kuan (frontier gate). From Feng-i post-station, to reach Nan-tao post-station of Jung-ching district on the boundard&lt;ref&gt;Error in original.&lt;/ref&gt; of Ya-chou, is 75 ''li''. To reach Han-ch'ang is 60 ''li''. (... dependent on Ya-chou) (Comment: We hold that at the beginning of this sentence there is an omission.) (The name of the town is Ko-tien.)&lt;/p&gt;
|-
|至皮店三十裏，至黎州潘倉驛五十裏，至黎武城六十裏，至白士驛三十五裏&lt;span style=&quot;color:#aaa&quot;&gt;(過漢源縣十裏)&lt;/span&gt;，至通望縣本筤驛四十裏&lt;span style=&quot;color:#aaa&quot;&gt;(去大渡十裏)&lt;/span&gt;，至望星驛四十五裏，至清溪關五十裏，至大定城六十裏，至達士驛五十裏&lt;span style=&quot;color:#aaa&quot;&gt;(黎、巂二州分界)&lt;/span&gt;，至新安城三十裏，至菁口驛六十裏，至榮水驛八十裏，至初裏驛三十五裏，至臺登城平樂驛四十裏&lt;span style=&quot;color:#aaa&quot;&gt;(古縣，今廢)&lt;/span&gt;，至蘇祁驛四十裏&lt;span style=&quot;color:#aaa&quot;&gt;(古縣)&lt;/span&gt;，至巂州三阜城四十裏&lt;span style=&quot;color:#aaa&quot;&gt;(州城在三阜山上)&lt;/span&gt;，至沙也城八十裏&lt;span style=&quot;color:#aaa&quot;&gt;(故巂州，大和年移在臺登)&lt;/span&gt;，至儉浪驛八十裏，至俄淮嶺七十裏，下此嶺入雲南界。
|To '''Pí​diàn​''' (皮店&lt;ref&gt;Literally '[animal] skin [or fur] selling place'.&lt;/ref&gt;) it is a further 30 ''li'', to '''Pāncāng​​''' (潘倉&lt;ref&gt;Literally 'Pan storehouse' or 'Pan's cabin'.&lt;/ref&gt;) station of '''Lízhōu​''' (黎州) a further 50 ''li'', to '''Lí​wǔ''' (黎武&lt;ref&gt;Literally 'black militia'.&lt;/ref&gt;) city a further 60 ''li'', to '''Bái​shì​''' (白士&lt;ref&gt;Literally something like 'hundred scholars' or 'scholarly'.&lt;/ref&gt;) station a further 35 ''li'' &lt;span style=&quot;color:#aaa&quot;&gt;(10 ''li'' across '''Hàn​yuán​''' (漢源) county)&lt;/span&gt;, and 40 ''li'' to '''Běn​láng​''' (本筤) station of '''Wàngxiàn​''' (望縣) county &lt;span style=&quot;color:#aaa&quot;&gt;(10 ''li'' to '''Dàdù​''' (大渡)&lt;/span&gt;. Continuing to '''Wàng​xīng​''' (望星&lt;ref&gt;Literally 'star gazing'. Conjecture: This could be atop a particularly high point or in a microclimate without evening cloud. Alternatively, the name may refer to a local cultural habit of astromancy.&lt;/ref&gt;) station is a further 45 ''li'', '''Qīng​xīguān​​''' (清溪關&lt;ref&gt;Literally 'clear stream pass'.&lt;/ref&gt;) a further 50 ''li'', '''Dà​dìng​''' city (大定城&lt;ref&gt;Literally this could possibly be something like 'city of great permanence'.&lt;/ref&gt;) a further 60 ''li'', to '''Dá​shì​''' (達士&lt;ref&gt;Literally something like 'passing the scholarly exam', which seems fairly elevated as a reference for such a presumably remote location and therefore suspect. Other explanations are a mere transliteration, possibly in jest, of some form of endemic language such as Yi or Naxi.&lt;/ref&gt;) station a further 50 ''li'' &lt;span style=&quot;color:#aaa&quot;&gt;(on the border of '''Lí​''' (黎) and '''Xī'''&lt;ref&gt;The character 巂 has multiple pronunciations, however with the dictionary I am using this pronunciation is listed specifically as a Sichuan-related toponym, so seems the most likely candidate. Luce uses a more common reading of the character, ''sui'', which is possibly wrong.&lt;/ref&gt; (巂) prefectures), to '''Xīn​'ān​''' city (新安城&lt;ref&gt;Literally 'new peaceful city'.&lt;/ref&gt;) a further 30 ''li'', to '''Jīng​kǒu​''' (菁口) station a further 60 ''li'', to '''Róngshuǐ​''' (榮水&lt;ref&gt;Literally 'thriving water', suggesting a fast-moving stream.&lt;/ref&gt;) station a further 80 ''li'', to '''Chū​lǐ''' (初裏) station another 35 ''li'', to '''Píng​lè​''' (平樂) station in '''Tái​dēng​''' city (臺登城) another 40 ''li'' &lt;span style=&quot;color:#aaa&quot;&gt;(an ancient county, since  abandoned)&lt;/span&gt;, to '''Sū​qí​''' (蘇祁&lt;ref&gt;This toponym sounds suspiciously transliteration-like to me.&lt;/ref&gt;) station a further 40 ''li'' &lt;span style=&quot;color:#aaa&quot;&gt;(an ancient county)&lt;/span&gt;, to '''Sān​fù​''' city (三阜城) of '''Xī​zhōu​''' (巂州) prefecture another 40 ''li'' &lt;span style=&quot;color:#aaa&quot;&gt;(the prefectural capital city's walls lie atop Sān​fù​shān​ (三阜山; lit. 'Three Mounds Mountain'&lt;ref&gt;Unidentified. There is apparently a similarly named mountain (characters uncertain) known for its mineral ores in the Shandong region — [http://www.researchgate.net/publication/278114099_Stable_isotope_geochemistry_and_Re-Os_ages_of_the_Yinan_gold_deposit_Shandong_Province_northeastern_China source].&lt;/ref&gt;)&lt;/span&gt;, to '''Shā​yě​''' city (沙也城) another 80 ''li'' &lt;span style=&quot;color:#aaa&quot;&gt;(then and formerly part of '''Xī​zhōu​''' (巂州) — it was moved to administration beneath '''Tái​dēng​''' (臺登) in the first year of Taihe&lt;ref&gt;Referring either to [http://zh.wikipedia.org/wiki/%E5%A4%A7%E5%92%8C_%28%E5%8D%97%E5%90%B4%29 929-930] or [http://zh.wikipedia.org/wiki/%E5%A4%A7%E5%92%8C_%28%E5%94%90%E6%9C%9D%29 827-828], probably the former.&lt;/ref&gt; (ca. 930?))&lt;/span&gt;, to '''Jiǎnlàng​''' (儉浪) station a further 80 ''li'', to the '''É​huái​''' mountain range (俄淮嶺) a further 70 ''li'', thence down the mountain range to enter the border of '''Yún​nán​''' (雲南; lit.&lt;ref&gt;By received wisdom.&lt;/ref&gt; '(The region lying) south (of the) [https://en.wikipedia.org/wiki/Yunling_Mountains ''Yunling Mountains'']'&lt;ref&gt;雲嶺&lt;/ref&gt;).&lt;/span&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;To reach P'i-tien is 30 ''li''. To reach P'an-ts'ang post-station of Li-chou is 50 ''li''. To reach Li-wu city is 60 ''li''. To reach Pai-t'u post-station is 35 ''li''. (10 ''li'' beyond (the headquarters of) Han-yuan district.) To reach Pen-lang post-station of T'ung-wang district is 40 ''li''. (10 ''li'' from Ta-tu (Big Ferry).) To reach Wang-hsing post-station is 45 ''li''. To reach Ch'ing-ch'i-kuan (frontier gate) is 50 ''li''. To reach Ta-ting city (or fort?) is 60 ''li''. To reach Ta-shih post-station is 50 ''li''. (Here is the boundary between Li-chou and Sui-chou.) To reach Hsin-an city is 30 ''li''. To reach Ch'ing-k'ou post-station is 60 ''li''. To reach Jung Shui post-station is 80 ''li''. To reach Ch'u-li post-station is 35 ''li''. To reach P'ing-lo post-station of T'ai-teng city is 40 ''li''. (It is an old ''hsien'' (district), now abolished.) To reach Su-ch'i post-station is 40 ''li''. (An old ''hsien'' (district).) To reach San-fou city of Sui-chou is 40 ''li''. (The city of the ''chou'' (division) is on the San-fou (Three Mounds) mountain.) To reach Sha-yeh city is 80 ''li''. (The former T'ai-ho-nien (?) of Sui-chou was removed to T'ai-teng. (Query emend: &quot;It was formerly (part of) Sui-chou. During the T'ai-ho period (827-835 A.D.), it was moved to T'ai-teng&quot;?)) To reach Chien-lang post-station is 80 ''li''. To reach O-huai mountain-range is 70 ''li''. Descending from the range, one enters the frontiers of Yunnan.&lt;/p&gt;
|-
|已上三十二驛，計一千八百八十裏&lt;span style=&quot;color:#aaa&quot;&gt;(案：上文惟三十驛，計一千四百九十五裏，與此數不符)&lt;/span&gt;。
|These 32 stations total 1880 ''li'' &lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterator's note: The text only states 30 stations, totalling 1495 ''li'', thus the total is inconsistent.&lt;ref&gt;This note from the electronic source text in Chinese, by an unknown author, does not discuss any attempt to locate the various places and/or probable distances, which would probably be fruitful given that their notes suggest multiple places are already known. It may be worth mapping this region and attempting to infer the missing distances.&lt;/ref&gt;)&lt;/span&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;(Above, are 32 post-stations, (the distance) totalling 1880 ''li''.) (Comment: We hold that the above text only mentions 30 post-stations, totalling 1495 ''li''. It does not tally with this number.)&lt;/p&gt;
|-
|並屬西川管，差官人將軍專知驛務。
|All are governed by the '''Xīchuān''' (西川) region, which sends out special inspectors to monitor the transport relay stations' affairs.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;All are dependent on the Hsi-ch'uan administration, which sends out official civil and military, who are specially acquainted with the affairs of the post-stations.&lt;/p&gt;
|}

====The Yúnnán (雲南) boundary to Yángxiefai (陽苴咩城)====
{| class=&quot;wikitable&quot; style=&quot;text-align:center; width:80%;&quot;
|-
! scope=&quot;col&quot; | Original &lt;small&gt;pp. [https://archive.org/stream/06061161.cn#page/n13/mode/1up 13]—[https://archive.org/stream/06061161.cn#page/n14/mode/1up 14]&lt;/small&gt;
! scope=&quot;col&quot; | Translation
! scope=&quot;col&quot; | Luce (1961) — &lt;small&gt;pp. [http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=21;node=seap044%3A4;page=root;size=100 7],[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=22;node=seap044%3A4;page=root;size=100 8]+[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=28;node=seap044%3A4;page=root;size=100 14]&lt;/small&gt;
|-
|雲南蠻界：從巂州俄淮嶺七十裏至菁口驛，三十裏至芘驛，六十裏至會川鎮，差蠻三人充鎮。
|The Yunnan barbarian boundary:&lt;ref&gt;Referring to Nanzhao.&lt;/ref&gt; From the '''É​huái​''' mountain range (俄淮嶺) of '''Xī​zhōu​''' (巂州; ie. modern Xichang / 西昌&lt;ref&gt;Apparently modern Xichang, in Sichuan (四川省西昌市) ... today most notably the approximate site of a major Chinese spaceport.&lt;/ref&gt;) prefecture it is 70 ''li'' to '''Jīng​kǒu​''' (菁口&lt;ref&gt;Literally perhaps 'luxuriant pass' or 'gateway to luxuriance'. There appear to be no less than four modern locations with this name in the approximate area. All candidates are under the modern jurisdiction of Luzhou (泸州市; ''Lúzhōu shì''): two more westerly and thus perhaps more likely candidates are in its Xuyong county (泸州市叙永县; ''Xùyǒngxiàn''), and two are in its Gulin county (古蔺县; ''Gǔlìnxiàn''). Of the westerly Xuyong candidates, the northerly is at 27.9174625N,105.520287E and appears to describe a hill in modern times with a secondary road from the south, the 011县到 or number 11 county-level road, arriving to its west and perhaps delivering travelers to an area of relative flat. The southerly is at 27.80265N,105.5403784E and appears to describe a position at the northern and elevated end of a mountain pass running north/south. Of the easterly Gulin candidates, neither appear to describe logical sites on a northward progression toward the Sichuan basin. [http://www.mala.cn/thread-1116357-1-1.html Apparently] identified by others as equivalent to modern ''Diānshāguān'' / 甸沙关, lying about half-way between Panzhihua and Liangshan, just east of the modern freeway and railway line.&lt;/ref&gt;; ie. modern ''Diānshāguān'' / 甸沙关) station, 30 ''li'' to '''Pí''' station (芘驛&lt;ref&gt;[http://www.mala.cn/thread-1116357-1-1.html Apparently] identified as modern ''Bāsōng'' / 巴松 at 27.029898N, 102.260703E.&lt;/ref&gt;; ie. modern ''Bāsōng'' / 巴松), 60 ''li'' to '''Huì​chuān​''' village (會川鎮&lt;ref&gt;[http://www.lsrb.cn/html/2008-08/07/content_14368.htm Apparently] [http://www.mala.cn/thread-1116357-1-1.html identified] as modern ''Huìlǐ'' / 会理 at 26.663578N, 102.247416E — from which a very clear topography defines an ancient passage north.&lt;/ref&gt;; ie. modern ''Huìlǐ'' / 会理) where three barbarians are commissioned to keep the peace.&lt;ref&gt;This last part was revised after comparing Luce's translation which seemed a more likely interpretation.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Frontiers of the Man of Yunnan. From the O-huai mountain-range of Sui-chou, after 70 ''li'' one reaches Ching-k'ou post-station. After 30 ''li'' one reaches Pi (''or'' P'i) post-station. After 60 ''li'' one reaches Hui-ch'uan-chen (garrison-town), where they send three ''Man'' men to act as guards.&lt;/p&gt;
|-
|五十五裏至目集驛，七十裏至會川，有蠻充刺史，稱會川都督。
|For 55 ''li'' to '''Mù​jí​''' (目集&lt;ref&gt;[http://www.mala.cn/thread-1116357-1-1.html Apparently identified] as modern ''Fèngshānyíng'' (凤山营) at 26.496801N, 102.134590E. However, this is far more southerly than previously discussed locations and represents a contextual shift within the text if correctly identified. Place name possibly suggests collecting, not very usefully for our purposes implying adjacency to forest (probably mountains, being less likely to be uncultivated land) rather than a flat agricultural area.&lt;/ref&gt;; ie. modern ''Fèngshānyíng'' / 凤山营) station, and 70 ''li'' to '''Huì​chuān​''' (會川), the governor is a barbarian,&lt;ref&gt;Revised vs. Luce's interpretation.&lt;/ref&gt; who is styled&lt;ref&gt;稱&lt;/ref&gt; the ''Commander-in-chief''&lt;ref&gt;都督&lt;/ref&gt; ''of Huì​chuān''&lt;ref&gt;會川都督&lt;/ref&gt;​.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;After 55 ''li'' one reaches Mu-chi Inn. After 70 ''li'' one reaches Hui-ch'uan, where is a ''Man'' acting as ''Tz'u-shih'', who calls himself the ''Tu-tu'' of Hui-ch'uan.&lt;/p&gt;
|-
|從目集驛至河子鎮七十裏。
|From '''Mù​jí​''' station to '''Hé​zi​''' town (河子鎮&lt;ref&gt;Apparently identified as modern ''Jiāngyì'' / 姜驿 at 26.068453N, 101.910703E.&lt;/ref&gt;; ie. modern ''Jiāngyì'' / 姜驿) is 70 ''li''.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From Mu-chi post-station, to reach Ho-tzu-chen (garrison-town) is 70 ''li''.&lt;/p&gt;
|-
|瀘江，乘皮船渡瀘水，從河子鎮至末柵館五十裏，至伽毗館七十裏，至清渠鋪八十裏，渡繩橋&lt;span style=&quot;color:#aaa&quot;&gt;(《雲南行記》雲「渠桑驛」)&lt;/span&gt;。
|On the '''Lú​jiāng​''' river (瀘江&lt;ref&gt;Identification here was non-trivial. [http://zh.wikipedia.org/wiki/%E6%B3%B8%E6%B1%9F Chinese Wikipedia] suggests that the term has been used in the context of the region to refer to at least two separate rivers, one of which flows from Shiping to Kaiyuan (thus being in completely the wrong area for this discussion), and one of which is a name for a tributary to the Red River within modern Vietnam (again, completely the wrong area). One may then assume that the Lujiang or Lu River under reference is in fact a river known by alternate modern names in the previously geographically established context, ie. that roughly of southern Sichuan's Liangshan Yi Autonomous Region (凉山彝族自治州), or thereabouts. To aid in identification, we could assert that a skin boat of the simple inflated type that is most likely referenced would have been most appropriate for relatively broad river in a relatively mountainous or remote location, given that a settled agricultural zone with higher population, specialist workers and frequent need to cross the water would likely provide rapidly for comfortable crossing by bridge or more permanent/sophisticated watercraft. The answer to the riddle appears to be, [http://baike.baidu.com/subview/186709/15968415.htm according to Baidu Baike], that the major river in the area, the upper Yangtze, locally known as the Jinshajiang (金沙江) since the Song Dynasty (960-1279), was in ancient times from the Three Kingdoms period (220–280) known by this name (amongst others). The period of usage reflected here in the ''Manshu'' accords with this information.&lt;/ref&gt;; ie. the modern ''Jīn​shā​jiāng​'' (金沙江) or upper Yangtze), skin boats&lt;ref&gt;Skin boats refers at the most basic and certainly regionally historically attested level to inflated skins or organs of various animals used as buoyancy devices to float across rivers. At the more complex level skin boats may include relatively sophisticated boats made of a bamboo, wood, bone or other type of frame holding without a usually sewn collection of multiple skins including sewing, caulking and heat treatment technologies. In this region, the former is almost certainly the type of boat referenced, as attested by early photographs and probably other types of sources. More sophisticated boats in the region appear to have been limited to Yunnan's major lakes, the Red River (technology via Vietnam) and the edge of the Sichuan basin, these were of wood rather than skin and probably represented a completely different and independent evolutionary lineage of watercraft.&lt;/ref&gt; are used to cross to '''Lú​shuǐ​''' (瀘水&lt;ref&gt;In modern times, the name apparently refers to the town of Liuku, capital of Nujiang prefecture in far western Yunnan (bordering Burma's Kachin State). However, such an identification is neither in keeping with the established geographic context or in keeping with the later known traditions of that area to cross rivers by rope bridge (owing to the extreme depth of that gorge and often low temperatures). Given the identification of the river, we can narrow the identification of this town to approximately riverside sites. Since Panzhihua was apparently only founded in the 1960s as a steel-making town, we can rule that out.&lt;/ref&gt;). From '''Hé​zi​''' to '''Mòzhà​​guǎn​''' (末柵館) pass is 50 ''li'', onward to '''Jiā​pí​guǎn​''' (伽毗館) pass is 70 ''li'', onward to '''Qīngqúpù''' (清渠鋪) is 80 ''li'', crossing a rope bridge.&lt;ref name=&quot;ropebridge&quot;&gt;In Luce's translation, the rope-bridge is ascribed to the ''Ch'ing-ch'u-p'u''—''T'sang-p'ang'' portion of the route. However, in the digital version of our Palace Museum Library edition source text, a firmly placed full stop attributes this bridge instead to the ''Jiā​pí​guǎn​'' (伽毗館)—''Qīngqúpù'' (清渠鋪) portion. Without additional sources, we err in favour of our edition but note this point of contention for future readers.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;(As for the) Lu-chiang,&lt;ref&gt;Luce appears to concur with the interpretation as a river rather than a settlement or region.&lt;/ref&gt; one rides a leather boat to cross the Lu-shui.&lt;ref&gt;Here Luce departs from our interpretation by implying that his ''Lu-shui'' is another reference to the ''Lu-chiang'' (瀘江) river rather than a place name.&lt;/ref&gt; From Ho-tzu garrison-town, to reach Mo-cha (Mo stockade) Inn is 50 ''li''. To reach Ch'ieh-p'i Inn is 70 ''li''. To reach Ch'ing-ch'u-p'u (bed) is 80 ''li''. Crossing the rope-bridge...(The ''Yun-nan hsing chi'' (Diary of a journey to Yunnan) mentions Ch'u-sang post-station.)&lt;ref name=&quot;ropebridge&quot;/&gt;&lt;/p&gt;
|-
|至藏傍館七十四裏，至陽裒館六十裏，過大嶺，險峻極。
|Onward to '''Cángbàngguǎn''' (藏傍館&lt;ref&gt;Literally 'the pass [near/relying on/of] the storehouse'.&lt;/ref&gt;) is a further 74 ''li'', onward to '''Yángpóuguǎn''' (陽裒館&lt;ref&gt;Probably literally 'sunny collection pass', where ''yang'' is taken in its male 'which-side-of-the-mountain' type sense, possibly referring to either the collection of taxes from travelers or the collection of some wild animal, plant or mineral resource by foraging travelers. An alternative and far less likely translation would be a place to collect men (with an emphasis on male), perhaps with reference to the slave-taking traditions of the ''Yi'' people of the region or to a local mercenary tradition.&lt;/ref&gt;) is a further 60 ''li'' across the great mountain range which is extremely steep and hard-going.&lt;ref name=&quot;steepness&quot;&gt;The phrase is 過大嶺，險峻極 which was originally presumably without punctuation and could be interpreted a few ways from the basic components as follows: 過 (to cross) 大嶺 (the or a great mountain range) 險峻 (arduous/steep) 極 (extremely/top). Some may interpret this as crossing &quot;by the steep summit&quot; (though this is likely too specific), others as &quot;with great difficulty&quot; or &quot;it is very steep&quot;. I choose a combination of the latter to cover all bases, but acknowledge some ambiguity here.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;... to reach T'sang-p'ang Inn is 74 ''li''. To reach Yang-pao Inn is 60 li. One crosses a big mountain-ridge, which is very dangerous and steep.&lt;ref name=&quot;steepness&quot;/&gt;&lt;/p&gt;
|-
|從陽裒至弄棟城七十裏，本是姚州，舊屬西川。
|From '''Yángpóu''' (陽裒) to '''Lòngdòng''' city (弄棟城&lt;ref&gt;Probably literally 'alley of buildings city'. Alternatively, this could be '''Nòngdòng''' and have a meaning like 'messy ridgepoles city'.&lt;/ref&gt;) is 70 ''li'', now of '''Yáozhōu''' province (姚州&lt;ref&gt;Literally 'good-looking region'.&lt;/ref&gt;), though formerly belonging to '''Xīchuān''' (西川&lt;ref&gt;Literally something like 'the western source of rivers'.&lt;/ref&gt;).&lt;ref name=&quot;longdong&quot;&gt;We read 本是 as &quot;currently&quot; and 舊屬 as &quot;formerly of&quot;. Luce instead reads both as historic reference, which seems an odd sentence structure to take given the rest of the text.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From Yang-pao, to reach Lung-tung city is 70 ''li''. It was originally Yao-chou,&lt;ref name=&quot;longdong&quot;/&gt; and formerly depended on Hsi-ch'uan.&lt;ref name=&quot;longdong&quot;/&gt;&lt;/p&gt;
|-
|天寶九載，為姚州都督張乾&lt;span style=&quot;color:#aaa&quot;&gt;(案：「乾」《唐書》作「虔」)&lt;/span&gt;陀附蠻所陷。
|In the ninth year of the ''Tianbao'' (天寶) reign (ie. ~750&lt;ref&gt;Emperor ''Tang Xuán Zōng'' (玄宗)'s ''Tiānbǎo'' (天寶) reign lasted from 742–756. ''Emperor Xuanzong'' (唐玄宗) (8 September 685—3 May 762), also commonly known as ''Emperor Ming of Tang'' (唐明皇), personal name ''Li Longji'' (李隆基), known as ''Wu Longji'' (武隆基) from 690—705, was the seventh emperor of the Tang dynasty in China, reigning from 712—756. His reign of 43 years was the longest during the Tang Dynasty. In the early half of his reign he was a diligent and astute ruler. Ably assisted by capable chancellors like Yao Chong, Song Jing and Zhang Yue, he was credited with bringing Tang China to a pinnacle of culture and power. He was blamed, however, for over-trusting Li Linfu, Yang Guozhong and An Lushan during his late reign, with Tang's golden age ending in the Anshi Rebellion. This marked the beginning of the Tang dynasty's decline.&lt;/ref&gt;), the military commander-in-chief of '''Yáozhōu''' (姚州) ''Zhāng​ Qián​'' (張乾) &lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterator's note: In the ''Tangshu'', 乾 is written as 虔.)&lt;/span&gt; was defeated here by the barbarians.&lt;ref name=&quot;zhangqian&quot;&gt;We interpret 陀附蠻所陷 as 陀 (fell or lost-out) 附 (to) 蠻 (barbarian) 所 ('s) 陷 ([via] defeat in battle). Luce however tacks the first character on to the general's name, probably in error.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;In the 9th year of the T'ien-pao period (750 A.D.), it was lost when the ''Tu-tu'' of Yao-chou, ''Chang Ch'ien-t'o''&lt;ref name=&quot;zhangqian&quot;/&gt; fell under the ''Man''. (Comment: We hold that for ''Ch'ien'' the ''T'ang history'' writes ''Ch'ien'')&lt;/p&gt;
|-
|從弄棟城至外彌蕩八十裏，從外彌蕩至求贈館&lt;span style=&quot;color:#aaa&quot;&gt;(案：此句下有脫文)&lt;/span&gt;。
|From '''Lòngdòng''' city (弄棟城) to '''Wàimídàng''' (外彌蕩&lt;ref&gt;This place name could mean 'outer' or 'external' 彌蕩, however this feels like an overly modern interpretation. From dictionary sources, it appears this place name may be something not dissimilar to 'outsiders completely removed', potentially referring to the reinstatement of local governance, but this is not really useful as a clue even if true. This is also the first place, heading from Nanzhao toward Sichuan, that differs from the Vietnam to Nanzhao route description, thus we may assume that it lies northward a little of the primary east-west route — ie. represents a path between '''Qiúzèng''' station (求贈館) and the upper Yangtse. Based upon this latter evidence, and the known association of the previous sites with '''Yáozhōu''' (姚州), it could make sense to place this between modern '''Yáozhōu''' (姚州) — again marked as a walled city on my 1950s maps — and the tentative identification of '''Qiúzèng''' station (求贈館) as '''Pǔ​péng​jiē​''' (普淜街). Approximately precisely half-way between those is '''Mí​xī​zhèn​''' (瀰溪鎮), which seems the most likely candidate, if indeed it existed at all in those days.&lt;/ref&gt;; ie. modern ''Mí​xī​zhèn​'' (瀰溪鎮)?) is 80 ''li'', after which one arrives at '''Qiúzèng''' station (求贈館&lt;ref&gt;Apparently literally not unlike 'the place at which presents are sought', ie. taxes or levies are extracted, either legally or by graft. This is also the last place that is shared between the two routes (to Vietnam and to Sichuan) described within the text, thus we may assume that it is in an eastward direction from the Dali area but not significantly north or south. The place known in the 20th century as '''Pǔ​péng​jiē​''' (普淜街; lit. 'Roaring [like waves] street' — possibly implying busyness) seems to be a strong candidate, lying at the natural topographic intersection of the east-south-easterly route toward Kunming and the north-easterly route to the upper Yangtse or Jinshajiang.&lt;/ref&gt;; ie. modern ''Pǔ​péng​jiē​'' (普淜街)?). &lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterator's note: There are characters missing after this position.)&lt;/span&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;(From Lung-tung city, to reach Wai-mi-tang is 80 ''li''.) (From Wai-mi-tang, to reach Ch'iu-tseng Inn ... (Comment: We hold that below this clause there are some characters missing))&lt;/p&gt;
|-
|至雲南城七十裏，至波大驛四十裏，至渠藍趙館四十裏，至龍尾城三十裏。
|To the city of '''Yunnan''' (雲南城; ie. modern Yunnanyi) it is 70 ''li'', thence 40 ''li'' to '''Bōdàyì''' (波大驛&lt;ref&gt;Literally 'great storm (postal or relay) station'. Based upon stage distances and topography, I must be a town identified on maps from the 1950s as 'Hsiang-yun' and noted as being a walled town (hence, probably quite old and lending further credence to the identification) — modern Xiangyun County (祥云县) — which lies on the western edge of the swampy (by 1950s map's definition!) depression immediately northwest of that containing Yunnanyi, the southeast of which contains a small lake known as Qinghai (presumably 青海).&lt;/ref&gt;), thence 40 ''li'' to '''Qúlánzhào''' station (渠藍趙館&lt;ref&gt;This place is not mentioned in the ''Jiāozhǐ (交阯城) to Yángxiefai (陽苴咩城)'' section, above, instead being replaced by the location '''Báiyányì''' (白嚴驛). It is not possible to compare distances however, because that former section does not quote them. However, it is reasonable to assume that the de-facto unit of measure with regards to places worth mentioning en-route was a caravan-capable day-stage, and that this is reflected inexplicitly within the current section. If these reasonable assumptions are true, then given both the topography and the distances involved, these two place names are fairly likely to be synonyms, ie. '''Qúlánzhào''' station (渠藍趙館) is likely the same as '''Báiyányì''' (白嚴驛). As for a modern identification, the 1950s map I have shows the town of 'Feng-i (Chao-chou)' — modern '''Fengyi''' (凤仪镇) — noted as a walled and therefore a relatively established or ancient town, in the north-south valley proceeding southward from the south-eastern corner of Erhai Lake, ie. the valley which currently houses the Dali Expressway. This is very likely to be the correct identification for at least one of these places, and possibly both. Alternatively, if this identification is incorrect, then the name probably refers to the southern end of that river-valley where it emerges in to another swampy valley with 1950s place names in its north including '''Guǒ​yuán​''' (果园; ie. 'Fruit Orchard') and '''Hóng​yán​''' (红岩; ie. 'Red Cliff'). Unfortunately, that area is now apparently under an expressway and appears to have no identifiable town center.&lt;/ref&gt;), thence 30 ''li'' to '''Lóngwěi''' city (龍尾城; lit. 'Dragon's tail city', ie. modern Xiaguan).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;To reach Yunnan city is 70 ''li''. To reach Po-ta post-station is 40 ''li''. To reach Ch'u-lan-chao Inn is 40 ''li''. To reach Lung-wei (Dragon's Tail) city is 30 ''li''.&lt;/p&gt;
|-
|從龍尾城至陽苴咩城五十裏，以上一十九驛，計一千五十四裏&lt;span style=&quot;color:#aaa&quot;&gt;(案：十九驛，共計一千六十九裏，與此數亦不符)&lt;/span&gt;。
|From  '''Lóngwěi''' city (龍尾城) to '''Yángxiefai''' city (陽苴咩城; ie. modern Dali) is 50 ''li'', bringing the total for the previous 19 stages to 1054 ''li''. &lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterator's note: In fact the 19 stages add to 1069 ''li'', an inconsistent total)&lt;/span&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;(From Lung-wei city, to reach Yang Chu-mieh city is 50 ''li''.) (The above 19 post-stations total (a mileage of) 1054 ''li''.) (Comment: We hold that there are 19 post-stations, totalling 1069 ''li''. This, too, does not tally with the number given.)&lt;/p&gt;
|}

====Beyond ''Yáozhōu'' (姚州)====
{| class=&quot;wikitable&quot; style=&quot;text-align:center; width:80%;&quot;
|-
! scope=&quot;col&quot; | Original &lt;small&gt;p. [https://archive.org/stream/06061161.cn#page/n14/mode/1up 14]&lt;/small&gt;
! scope=&quot;col&quot; | Translation
! scope=&quot;col&quot; | Luce (1961) — &lt;small&gt;pp. [http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=22;node=seap044%3A4;page=root;size=100 8]+[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=28;node=seap044%3A4;page=root;size=100 14]&lt;/small&gt;
|-
|南蠻因姚州之後，屬蠻管系。
|The Southern Barbarians (南蠻; ie. Nanzhao's peoples) beyond '''Yáozhōu''' (姚州; lit. 'the beautiful region'; ie. the modern Yao'an County&lt;ref&gt;[http://baike.baidu.com/subview/3482306/16192459.htm Baidu Baike] and the Chinese academic source [http://www.kaogu.net.cn/cn/xccz/20151116/52040.html Kaogu] concur here, apparently on an area directly to the east of the modern town (see [http://www.kaogu.net.cn/uploads/cn/201511/20151116yn9.jpg Kaogu map]).&lt;/ref&gt; area northwest of Chuxiong, roughly equidistant between the Dali/Erhai Lake and Kunming/Dianchi Lake plateaux), are subordinate to the barbarians (ie. subordinate to Nanzhao).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Because the Southern ''Man'', after Yao-chou, became dependent on and attached to the ''Man'' administration...&lt;ref name=&quot;2routes&quot;&gt;Here Luce runs together the interpretation of a statement regarding the lands west (&quot;beyond&quot;) Yaozhou/Yao'an, and two subsequent statements referring to roads to the east/northeast. This appears to be in error.&lt;/ref&gt;&lt;/p&gt;
|}

===Roads from Yōngzhōu (邕州) and Qiánzhōu (黔州)===
{| class=&quot;wikitable&quot; style=&quot;text-align:center; width:80%;&quot;
|-
! scope=&quot;col&quot; | Original &lt;small&gt;p. [https://archive.org/stream/06061161.cn#page/n14/mode/1up 14]&lt;/small&gt;
! scope=&quot;col&quot; | Translation
! scope=&quot;col&quot; | Luce (1961) — &lt;small&gt;pp. [http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=22;node=seap044%3A4;page=root;size=100 8]+[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=28;node=seap044%3A4;page=root;size=100 14]&lt;/small&gt;
|-
|從邕州路至蠻苴咩城，從黔州路至蠻苴咩城，兩地途程，臣未諳。
|The roads from both '''Yōngzhōu''' (邕州; ie. the modern Guangxi region&lt;ref&gt;Meaning Nanning or the general direction of Guangxi province.&lt;/ref&gt;) and '''Qiánzhōu''' (黔州; ie. the modern Guizhou region&lt;ref&gt;Meaning Guizhou province.&lt;/ref&gt;) to '''Yángxiefai''' city (陽苴咩城; ie. modern Dali) are both unclear.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;... your humble servant could not be expert or familiar with the stages of the two land-routes:&lt;ref name=&quot;2routes&quot;/&gt; (i) the Yung-chou road to Chü-mieh city of the Man, and (ii) the Ch'ien-chou road to Chü-mieh city of the Man.&lt;/p&gt;
|-
|委伏乞下堂帖令分析。
|Perhaps an order should be issued to investigate these.&lt;ref&gt;I'm a little vague about the first part 委伏乞下堂 — but overall meaning seems on the mark — 委伏 (some kind of deferential personal pronoun phrase) 乞 (beg) 下堂 (issue downward 'from the palace') ...&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;I humbly beg Your Majesty to send down an official notification ordering a detailed survey.&lt;/p&gt;
|}

===Politics===
Note that this entire portion is taken to have been a latter explanatory diversion, and not part of the main body of text.
{| class=&quot;wikitable&quot; style=&quot;text-align:center; width:80%;&quot;
|+ Chapter 1: ''Distances within Yunnan and at its Borders'' (云南界内途程; ''yúnnán jiè nèi túchéng'') — Politics
|-
! scope=&quot;col&quot; | Original &lt;small&gt;p. [https://archive.org/stream/06061161.cn#page/n15/mode/1up 15]&lt;/small&gt;
! scope=&quot;col&quot; | Translation
! scope=&quot;col&quot; | Luce (1961) — &lt;small&gt;pp. [http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=22;node=seap044%3A4;page=root;size=100 8],[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=23;node=seap044%3A4;page=root;size=100 9]+[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=28;node=seap044%3A4;page=root;size=100 14]&lt;/small&gt;
|-
|緣南蠻奸猾，攻劫在心，田桑之余，便&lt;span style=&quot;color:#f00&quot;&gt;習&lt;/span&gt;&lt;ref name=&quot;changwrong&quot;/&gt;鬥敵。
|Due to the Southern Barbarians' (南蠻; ie. Nanzhao) treacherous nature, with attack and plunder ever-present in their minds, whenever mulberries&lt;ref&gt;This is an interesting choice of crop to describe harvest season with, and could be a visual flourish implying evil or a thirst for blood; as the color of the fruit is similar to blood. Wikipedia states: &quot;Mulberry fruit color derives from ''anthocyanins'' which are under basic research for mechanisms of various diseases. Anthocyanins are responsible for the attractive colors of fresh plant foods, including orange, red, purple, black, and blue. These colors are water-soluble and easily extractable&quot;.&lt;/ref&gt; in the fields are plentiful they will seize the opportunity to drill&lt;ref name=&quot;changwrong&quot;&gt;The digital source text wrongly replaces the 習 (as written in the digital Palace Museum Library edition [https://archive.org/stream/06061161.cn#page/n15/mode/1up over here, at the bottom of the second column from the right]) with 昌 (''chang1'') (&quot;flatter&quot; or &quot;flourishing&quot;).&lt;/ref&gt; against their enemies.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Because the Southern ''Man'' are cunning and treacherous, and (the idea of) attacking and plundering is ever present in their minds, whenever they have some leisure from (cultivating their) fields and mulberry trees, they practise fighting the enemy.&lt;/p&gt;
|-
|若不四面征戰，兇惡難悛。
|If not engaged from all sides, the ferocious evil&lt;ref&gt;Meaning Nanzhao.&lt;/ref&gt; will be difficult to resolve.&lt;ref&gt;Obviously all sides (literally 四面 or 'four directions') is essentially impossible when one of them is the Himalayas and the other is tropical, malaria-ridden jungle. It may therefore either be assumed that the writer, Fan Chuo, was not particularly familiar with north-western, western, south-western and southern Yunnanese geography... or alternatively, that this is a figurative statement.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;If, then, we do not invade and attack them from all four sides, they are violent and bad persons, and difficult to reform.&lt;/p&gt;
|-
|所以錄其城鎮川原，麈黷宸扆。
|Thus: record their cities, towns, rivers and their sources; that stags will defile their palace screens.&lt;ref&gt;Apparently a contemporary metaphor suggesting the end of empire. The structure of the metaphor perhaps suggests that — to the civilization-obsessed Chinese, who viewed literature as its cornerstone — being overrun by wild animals is fate worse than being overrun by a rival kingdom.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;That is why I record their cities and garrison-towns, their river-valleys and plains--mere dust defiling the audience-screen of the Imperial apartments.&lt;/p&gt;
|-
|或冀破其蟻聚之眾，永清羌虜之夷。
|Thus we may destroy the ant&lt;ref&gt;Strange as it seems, Fan Chuo here appears to liken the Nanzhao kingdom (and any allied tribes) to ants.&lt;/ref&gt; masses (ie. Nanzhao's people), clean&lt;ref&gt;ie. Pacify.&lt;/ref&gt; forever the region&lt;ref&gt;The character 羌 represents the Qiang region (ie. the greater eastern Himalayan foothills, particularly from northern Yunnan through Sichuan to Gansu). However, it is also used to represent [https://en.wikipedia.org/wiki/Muntjac muntjac], and thus may be some kind of reference to the former sentence (&quot;...that stags will defile their palace screens&quot;), perhaps an instance of olden-day literary jest!&lt;/ref&gt; and capture the barbarians.&lt;ref&gt;ie. Nanzhao people.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Perhaps one might hope to wipe out their host of ant-swarms, and purge for ever (these) ''Ch'iang'' barbarian rebels.&lt;/p&gt;
|-
|臣披瀝懇忱，無任隕越之至&lt;span style=&quot;color:#aaa&quot;&gt;(案：此條乃附載陳說之詞，如後世著書之案語，原本誤連正文，遂令文義格礙，今低一格以別之，後仿此)&lt;/span&gt;。
|Sincerely, your humble servant, in the hopes of avoiding slaughter.&lt;ref&gt;Vague, particularly the last portion. A more experienced and confident translator may be able to add detail here.&lt;/ref&gt; &lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterator's note: This section is an addition containing commentary, similar to 'notes' in later written formats. Our original mistakenly conjoined it, causing issues of comprehension. Thus in the present edition we drop the text by one line, and will hereupon continue with this typographic convention.)&lt;/span&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Your humble servant speaks without reserve and implores Your Majesty with all sincerity that he may not be held responsible even though he lapse into the most extreme error. (Comment: We hold that this paragraph is by way of a supplement, containing an explanatory statement, like the formal statements of books composed in latter generations. In the original copy it was wrongly included in the main body of the text, and consequently interfered with the sense of the text. Now we have lowered it one line in order to distinguish it. In future we shall follow this method.)&lt;/p&gt;
|}

===The Stone Gate (石門) and the Kunming-Xichuan Route (昆川至雲南)===
[[File:Eastern Yunnan - Route from Kunming to Zhaotong (Scan of Lithograph of Photograph by Gervais-Courtellemont. Printed by Bong and Company, Paris, 1913).jpg|thumb|center|800px|1913 lithographic print by Bong and Company, Paris, of a photograph by Gervais-Courtellemont, titled in French but equating to 'Eastern Yunnan: Route from Kunming to Zhaotong'.]]

(note: here we shall have a new map! currently under development...)

{| class=&quot;wikitable&quot; style=&quot;text-align:center; width:80%;&quot;
|-
! scope=&quot;col&quot; | Original &lt;small&gt;pp. [https://archive.org/stream/06061161.cn#page/n15/mode/1up 15]—[https://archive.org/stream/06061161.cn#page/n21/mode/1up 21]&lt;/small&gt;
! scope=&quot;col&quot; | Translation
! scope=&quot;col&quot; | Luce (1961) — &lt;small&gt;pp. [http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=23;node=seap044%3A4;page=root;size=100 9]-[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=25;node=seap044%3A4;page=root;size=100 11]+[http://seapdatapapers.library.cornell.edu/cgi/t/text/pageviewer-idx?c=seap;cc=seap;rgn=full%20text;idno=seap044;didno=seap044;view=image;seq=28;node=seap044%3A4;page=root;size=100 14]&lt;/small&gt;
|-
|從石門外出魯望、昆川至雲南，謂之北路。
|Outside (ie. south&lt;ref&gt;Based upon the assumption that the author writes from a contemporary Chinese imperial perspective, which seems supported by later text in this section.&lt;/ref&gt;) of the '''Shímén''' (石門; lit. (the) stone gate&lt;ref&gt;Referring to an historic pass located near '''Dòushā Village''' (豆沙真) in modern '''Yán​jīn County''' (盐津县) of '''Zhāo​tōng​''' (昭通) along the '''Héngjiāng River''' (横江), the last major tributary to the upper Yangtze before '''Yíbīn''' (宜宾) and the Sichuan basin proper. In ancient times, this Yunnan-Guizhou plateau/Sichuan basin transition area was the domain of the Bo people, whose neolithic but similarly cliff-inspired culture incorporated hanging cliff tombs, a tradition still preserved to this day in only one location by an offshoot emigrant community who moved to Bainitang in Wenshan prefecture, southeastern Yunnan. Sadly that community is now endangered by open cut mining. See for example [http://www.travelyunnan.org/yunnantour/zhaotong/nujiang/2856.html this Chinese source] for further information on the pass itself, which is discussed further subsequently in this section of the text. For maps, see [http://ids.lib.harvard.edu/ids/view/2419066?buttons=y Harvard's historical US military topographic map of the area] (zoom in to the southwest of Yen-ching at the bottom), [https://www.openstreetmap.org/#map=15/28.0362/104.1209&amp;layers=C OpenStreetMap] or [https://www.google.com/maps/@28.0329213,104.1271244,3109m/data=!3m1!1e3 Google Maps].&lt;/ref&gt;) is '''Lǔwàng''' (魯望; ie. Qujing?) and the '''Kunming'''-'''Xichuan'''&lt;ref&gt;Inferred from context, 昆 and 川 respectively being used to refer to Kunming and Sichuan in modern times, but Xichuan being the apparently closest contemporary toponym discussed in the text.&lt;/ref&gt; '''Route''' to '''Yunnan''' (probably '''Yún​nányì​​'''; 云南驿&lt;ref&gt;Possibly referring to the town of '''Yunnanyi''' (云南驿), acknowledged as an historically critical transport juncture including acting as the terminus for roads to Sichuan, Dali and Kunming, and geographically something of an eastern gateway to the Erhai Plateau (modern Dali and Xiaguan) that was the seat of Nanzhao's power. For example, [http://en.ynta.gov.cn/Item/578.aspx this modern government source] states &quot;Yunnan Yi used to be a must-take position since it can connect Dali, Chengdu, Kunming, South and West Yunnan&quot;.&lt;/ref&gt;), also known as the '''Northern Road''' (北路).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From beyond Shih-men (Stone Gate), to go out via Lu-wang and K'un-ch'uan and reach Yunnan, is called the North Road.&lt;/p&gt;
|-
|黎州、清溪關出邛部，過會通，至雲南，謂之南路。
|Leaving the '''Qīngxīguān''' (清溪關; lit. 'Clear Stream Pass') of '''Lízhōu''' (黎州; lit. 'Black Region'), one reaches '''Qióngbù''' (邛部), '''Huitong''' (會通), then '''Yúnnányì''' (云南驿). This route is known as the '''Southern Road''' (南路).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From the Ch'ing-ch'i-kuan (frontier-gate) of Li-chou to go out via Chiang-pu, pass through Hui-t'ung and reach Yunnan, is called the South Road.&lt;/p&gt;
|-
|從戎州南十日程至石門，上有隋初刊記處，雲：「開皇五年十月二十五日，兼法曹黃榮領始、益二州石匠，鑿石四孔，各深一丈，造偏梁橋閣，通越析州、津州。」蓋史萬歲南征出於此也。
|From '''Róngzhōu''' (戎州; lit. &quot;The Military City&quot;; ie. modern Yibin, Sichuan&lt;ref&gt;今四川宜宾市&lt;/ref&gt;) southward it is 10 days' travel to '''Shímén''' (石門; lit. the Stone Gate). An inscription above from the early Sui dynasty reads: &quot;On the 5th year, 10th month, 25th day of the  of the Kaihuang emperor (ie. ~587CE),&lt;ref&gt;Emperor Wen of Sui (隋文帝; 21 July 541 – 13 August 604), personal name Yang Jian (楊堅), Xianbei name Puliuru Jian (普六茹堅), nickname Naluoyan (那羅延), the founder and first emperor of China's Sui Dynasty (581–618 AD).&lt;/ref&gt; The official titled '''Jiānfǎ''' (兼法; perhaps Grand Juror?), '''Cáohuángróng''' (曹黃榮),  led the stonemasons of the two provinces of '''Shǐ​zhōu​''' (始州) and '''Yì​zhōu''' (益州) to bore four very deep holes of one ''zhàng'' (around 3 to 3.7 meters) each in depth,&lt;ref&gt;Apparently the foundations of the bridge. It may be interesting or relevant to note that the area of southern Sichuan not very distant to the north was actually the world's earliest site of the development of deep drilling technology, for the purpose of commercial salt wells. A great museum exists to this effect in modern '''Zìgòng''' (自貢), a city which in 1939 became the merged successor of the earlier — ie. relatively textually contemporary — cities of '''Zìliújǐng''' (自流井; lit. 'artesian well') and '''Gòngjǐng''' (貢井; lit. 'tribute well'). It might be arguably be possible to therefore infer that Fan Chuo  was not familiar with deep drilling capacity common in the region.&lt;/ref&gt; and constructed a slanting bridge with a pavilion to reach '''Yuèxīzhōu''' (越析州; lit. 'Province of the Divided Peoples'&lt;ref&gt;Implying perhaps extreme topography and ethnic diversity.&lt;/ref&gt;) and '''Jīnzhōu''' (津州; lit. 'Province of the River-Crossing').&quot; '''Shǐ Wànsuì''' (史萬歲) passed through here.&lt;ref&gt;'''Shǐ Wànsuì''' (史萬歲; b. 549, d. 600-11-20) was a famous and skilled Sui Dynasty military strategist, inheritor of the position of ''Duke of the Pacified Regions'' from his father '''Shǐ Jìng''' (史靜), and fathered a son '''Shǐ Huáiyì''' (史懷義). See [https://zh.wikipedia.org/zh-tw/%E5%8F%B2%E8%90%AC%E6%AD%B2 Traditional Chinese Wikipedia].&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;To the south of Jung-chou, after 10 day-stages one reaches Shih-men (Stone Gate). Above it there is an inscription of the beginning of the Sui dynasty (fl. 589-618A.D.), which says: &quot;The 25th day of the 10th month of the 5th year of K'ai-huang (Nov. 22nd., 585 A.D.). Huang Jung, prefect in charge of Shih-chou and I-chou, with the combined office of Fa-ts'ao (? Member of the Board of Law).&quot; Stone-masons bored four holes in the stone, each 10 ft. in depth, and constructed the leaning bridge with covered way connecting Yueh-hsi-chou and Ching-chou. It is the place from which Shih Wan-sui started on his expedition to the south.&lt;/p&gt;
|-
|越析州今西河河東一日程，越析州諮長故地也。
|'''Yuèxīzhōu''' (越析州) is one day's easterly travel beyond present-day&lt;ref&gt;Meaning Tang dynasty, versus Sui dynasty &amp;mdash; the period just quoted.&lt;/ref&gt; '''Xī​hé​ River''' (西河; lit. 'Western River'), the former lands of the '''Zī​zhǎng​''' (諮長; lit. 'Chief of Consultation', perhaps 'Chief of Affairs').
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;(As for) Yueh-hsi-chou, after crossing (?) the Hsi-ho (West River), (it is) 1 day-stage east of the Ho. Yueh-hsi-chou is the former land of the Tzu-chang (Senior Counsellor?). &lt;/p&gt;
|-
|津州未詳其處。
|The location of '''Jīnzhōu''' (津州) is unknown.&lt;ref&gt;Though from its &quot;River-crossing Province&quot; name we can infer that it was an important river crossing point of the area, which probably significantly narrows potential locations.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;As for Ching-chou I have no knowledge of its topography.&lt;/p&gt;
|-
|天寶中，鮮於仲通南溪下兵，亦是此路，後遂閉絕。
|During the Tiānbǎo era (ie. 742–756&lt;ref&gt;The last of three era names during the reign of '''[https://en.wikipedia.org/wiki/Emperor_Xuanzong_of_Tang Emperor Tang Xuanzong]''' (玄宗, Xuánzōng)&lt;/ref&gt;; ie. circa 750), the army of '''Xiān​yū​zhòng​''' (鮮於仲) came down through '''Nán​xī​''' (南溪&lt;ref&gt;Now a county in Yibin, Sichuan.&lt;/ref&gt;) and used this road, but they were utterly destroyed.&lt;ref&gt;Possibly blocked rather than destroyed, but I feel &quot;utterly destroyed&quot; is the probable sense from 閉絕 &amp;mdash; (stopped or obstructed)(entirely).&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;During the T'ien-pao period (742-755 A.D.) Hsien-yu Chung-t'ung, from Nan-ch'i, sent down troops; this was the route. Afterwards it got blocked and (communications) interrupted for nearly 50 years.&lt;/p&gt;
|-
|僅五十年來，貞元十年，南詔立功歸化，朝廷發使冊命。
|Only 50 years ago in the 10th year of Zhengyuan era&lt;ref&gt;The Zhēngyuán (貞元) 785-805 era of Dezong. From Wikipedia: &quot;Emperor Dezong of Tang (唐德宗) (May 27, 742 – February 25, 805), personal name Li Kuo (李适), was an emperor of the Chinese Tang Dynasty and the oldest son of his father Emperor Daizong. His reign of 26 years was the third longest in the Tang dynasty (surpassed only by Emperor Xuanzong and Emperor Gaozong). Emperor Dezong started out as a diligent and frugal emperor and he tried to reform the governmental finances by introducing new tax laws. His attempts to destroy the powerful regional warlords and the subsequent mismanagement of those campaigns, however, resulted in a number of rebellions that nearly destroyed him and the Tang Dynasty. After those events, he dealt cautiously with the regional governors, causing warlordism to become unchecked, and his trust of eunuchs caused the eunuchs' power to rise greatly. He was also known for his paranoia about officials' wielding too much power, and late in his reign, he did not grant much authority to his chancellors.&quot;&lt;/ref&gt; (ie. 795CE), Nanzhao submitted its sovereignty to China and their court dispatched envoys to announce the proclamation.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;In the 10th year of Cheng-yuan (794 A.D.) Nan-chao acted meritoriously and returned to its allegiance (to China). The Court sent out envoys and orders of appointment.&lt;/p&gt;
|-
|而邛部舊路方有兆吐蕃請鈔隔關。
|Owing to the prosperity of the old '''Qióngbù''' (邛部) road, the '''Tǔbō''' (吐蕃; ie. post-Tibetan Empire Kham Tibetans) demanded money at the passes.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;And the old road of Chiung-pu for the moment was thriving. But the Tibetans appropriated the cash and blocked the frontier-gates.&lt;/p&gt;
|-
|其年七月，西川節度韋臯乃遣巡官監察禦史馬益閉石門路，量行館。
|On the 7th month of that year, '''Wéigāonǎi''' (韋臯乃) of the '''Xichuan''' government's Jiedu (節度) department dispatched the official '''Shǐmǎyì''' (史馬益) to supervise, defend and close the '''Shímén''' (石門; lit. (the) stone gate) '''Road''' and its '''Liàngxíng''' garrison (量行館; lit. measure traffic garrison&lt;ref&gt;Quite possibly indicating a point of road toll style taxation.&lt;/ref&gt;).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;So in the 7th month of that year (Aug. 1 to 29, 794), Wei Kao, the Chieh-tu of Hsi-ch'uan, sent the Hsun-kuan (Inspecting Officer), the Chien-ch'a-yu-shih (Examining Censor) Ma I, to close the Liang-hsing-kuan (Inn) of the Shih-men (Stone Gate) road.&lt;/p&gt;
|-
|石門東崖石壁，直上萬仞，下臨朱提江流，又下入地中數百尺，惟聞水聲，人不可到。
|&lt;span style=&quot;color:#f0f&quot;&gt;[luce translation review up to here]&lt;/span&gt;The rock cliffs to the east of the '''Shímén''' (石門; lit. (the) stone gate) are of extreme height,&lt;ref&gt;Actual term used is 10,000 (萬; wàn) ''rèn''-fathoms (仞; ancient unit of measure equal to approximately 8 modern feet, or 2.4 meters). Given the figures, this is clearly a figurative use rather than a literal one.&lt;/ref&gt; beneath which the '''Zhuti River''' (朱提江; ie. early upper Yangtze or Jinsha river&lt;ref&gt;Apparently the name given to the upper Yangtze (ie. Jinsha) river in the vicinity of modern Shuifu prefecture, Zhaotong city, Yunnan. This is only a few kilometers from modern Yibin (宜宾市) in Sichuan province, ie. would have represented the initial stages of a southbound journey from the Han China controlled Sichuan basin (previously stolen from the ancient and endemic Shu kingdom) toward Yunnan. A good flowery description of the area in early Han perception is available in the ''Classic of Mountains and Seas'' (山海經), ca. 4th century BCE.&lt;/ref&gt;) flows only to enter the earth again through a hundred caverns. Listening to the sound of the water here, one is swept beyond the world of men.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;The east cliff of Shih-men is a sheer precipice rising ten thousand fathoms. Below, it borders the Chu-t'i-chiang. The stream moreover flows underground for several hundred feet. You can only hear the sound of the water, but no man can reach it.&lt;/p&gt;
|-
|西崖亦是石壁，傍崖亦有閣路，橫闊一步，斜亙三十余裏，半壁架空欹危虛險，其安梁石孔，即隋朝所鑿也。
|The rock cliffs to the west are also vertical. The road along their precipice sports pavilions and is but one pace wide, and over 30 ''li'' in length. Half the cliff stands bare forming a dangerous narrow pass, through which a safe passage was bored during the Sui dynasty.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;The west cliff is also a stone precipice. Along the side of the cliff there is a covered road, 1 pace broad. It goes up and down and round for over 30 li. Halfway along the cliff there is a gap in the frame of the road, with a dangerous topple and an awful void. The stone holes on which the bridge rests, were bored under the Sui dynasty.&lt;/p&gt;
|-
|閣外至夔嶺七日程，直經朱提江，下上躋攀，傴身側足，又有黃蠅、飛蛭、毒蛇、短狐、沙虱之類。
|Beyond the pavilion it is 7 days' journey to the '''Kuílǐng Range''' (夔嶺; lit. monstrous mountain range), passing the '''Zhuti River''' (朱提江; ie. upper Yangtse or Jinsha river) through steep topography, a back-breaking journey featuring yellow flies, flying leeches, venomous snakes, foxes, and all manner of parasites.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Beyond the covered road, one reaches K'uei-ling (range) in 7 day stages. One goes straight across the Chu-t'i-chang at the bottom, and then starts clambering up with a hunched body and feet awry. There are also yellow flies, flying leeches, poisonous snakes, short foxes (?), sand-lice, etc. etc.&lt;/p&gt;
|-
|石門外第三程至牛頭山，山有諸葛古城，館臨水，名馬安渡。
|On the third day one reaches '''Niútóu Shān''' (牛頭山; lit. Ox-head Mountain), which features the ancient '''Zhūgé''' city (諸葛古城&lt;ref&gt;Presumably a reference to a settlement or military garrison dating back to the time of Zhuge Liang (諸葛亮), whose two-character family name 諸葛 was shared by his relatives. From Wikipedia: &quot;Zhuge Liang (181–234), courtesy name Kongming (孔明), was a chancellor of the state of Shu Han during the Three Kingdoms period. He is recognised as the greatest and most accomplished strategist of his era, and has been compared to another great ancient Chinese strategist, Sun Tzu.&quot;&lt;/ref&gt;). There is a building near the water at a place known as '''Mǎāndù''' (馬安渡; lit. Peaceful Horse Crossing).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;At the third stage beyond Shih-men one reaches Niu-t'ou-shan (Cow's Head Mountain). On the mountain there is the old city (or fort) of Chu-ko (Liang) with the inn (kuan) on the brink of the stream. It is called Ma-an (Horse-saddle) Ferry.&lt;/p&gt;
|-
|上源從阿等路部落，繞蒙夔山，又東折與朱提江合。
|The road follows the head of '''Kuílǐng Range''' (夔嶺; lit. monstrous mountain range) as it descends, wrapping about the mountain, bending eastward again to follow the '''Zhuti River''' (朱提江; ie. upper Yangtse or Jinsha river).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;The source comes down from the (habitat of the) tribes of Ah and other roads. It winds around the Meng-k'uei mountains, and breaking eastwards joins the Chu-t'i-chiang.&lt;/p&gt;
|-
|第五程至生蠻阿部落，第七程至蒙夔嶺，嶺當大漏天，直上二十裏，積陰凝閉，晝夜不分。
|On the fifth day one reaches '''Shēngmán'ē''' (生蠻阿; lit. (perhaps) Barbarian Birth Mountain), and on the seventh day '''Méngkuílǐng''' (蒙夔嶺; lit. Ignorant Monster Mountain) whose ridge is like a great sky-funnel rising 20 ''li'', accumulating ''yin''&lt;ref&gt;ie. Ancient Chinese concept from the ''Book of Changes'' (易經; diviniation text dating from at least 1000BCE). In general use it means a female energy — darness, water, etc.&lt;/ref&gt; and freezing it in place such that the night and day are no longer distinct.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;At the fifth stage one reaches the wild Man, the Ah tribes. At the seventh stage one reaches the Meng-k'uei mountain-range. The range is completely open to the sky, standing straight up for 20 li. Its accumulated shade congeals solid, so there is no difference between day and night.&lt;/p&gt;
|-
|從此嶺頭南下八九裏，青松白草，川路漸平。
|From the head of this mountain range, one descends through peaceful pine forests and white grasses, and the '''Chuan Road''' (川路; lit. the road of the upper rivers; fig. the road to/from Xichuan or Sichuan) gradually becomes flat.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From the top of this range one descends south 8 or 9 li through green pines and white grasses, while the valley-road gradually levels out.&lt;/p&gt;
|-
|第九程至魯望，即蠻、漢兩界，舊曲靖之地也。
|On the ninth day one reaches '''Lǔwàng''' (魯望) — former '''Qujing''' (曲靖) — which is the border separating two worlds: the Chinese, and the barbarian.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;At the ninth stage one reaches Lu-wang, which is the common border between the Man and the Chinese, the land of the old Ch'u (and) Ching.&lt;/p&gt;
|-
|曲州、靖州廢城及邱墓碑闕皆在。
|The abandoned cities of the '''Qūzhōu''' (曲州) and '''Jìngzhōu''' (靖州) regions are but mounds with lettered gravestones.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;The abandoned cities of Ch'u-chou and Ching-chou, and the burial mounds and tombs with their stone tablets and gates(?), are all still extant.&lt;/p&gt;
|-
|依山有阿竿路部落，過魯望第七程至竹子嶺，嶺東有暴蠻部落，嶺西有盧鹿蠻部落。
|In the mountains is the '''Ēgān Road''' (阿竿路; lit. Mountain Bamboo Road) along which, seven days beyond '''Lǔwàng''' (魯望; ie. roughly Qujing), lies the '''Zhúzilǐng Range''' (竹子嶺; lit. Bamboo Range). East of this range are savage barbarians, and west of this range are the '''Lúlù Barbarians''' (盧鹿蠻; ie. Yi people&lt;ref&gt;Operating on the assumption that until recent times Yi were referred to as Luoluo or Lolo in many sources, and we're in the right area here.&lt;/ref&gt;).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Resting on the mountains there are the A-kan road tribes. After passing Lu-wang, at the 7th stage, one reaches Chu-tzu-ling (Bamboo mountain-range). To the east there are the tribes of savage Man. To the west of the range there are the tribes of Lu-lu Man.&lt;/p&gt;
|-
|第六程至生蠻磨彌殿部落，此等部落皆東爨烏蠻也。
|On the sixth day one reaches '''Mómídiàn''' (磨彌殿) of the wild barbarians, which along with other areas belongs to the '''Dark Eastern Civilizing Barbarians''' (東爨烏蠻; ''dōng cuàn wū mán'').
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;At the 6th stage one reaches the wild Man, the Mo-mi-tien tribes. These various tribes are all Eastern Ts'uan, Wu Man (Black Barbarians).&lt;/p&gt;
|-
|男則發髻，女則散發，見人無禮節拜跪，三譯四譯，乃與華通。
|Their men wear their hair in a topknot, whereas their women leave it loose. It is understood that they have no custom of respect such as to kneel or bow, and when speaking with us make sounds like ''sānyìsìyì''.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;The men have dressed hair, the women have their hair loose. When they meet people, they have no rules of etiquette. They (just) bow and kneel. They need three or four interpreters in order to communicate with the Chinese.&lt;/p&gt;
|-
|大部落則有鬼主，百家二百牛馬&lt;span style=&quot;color:#aaa&quot;&gt;(案：此句未詳)&lt;/span&gt;，無布帛，男女悉披牛羊皮。
|The greater area has but one overlord, controlling one hundred houses and two hundred oxes and horses. &lt;span style=&quot;color:#aaa&quot;&gt;(Former transliterator's note: Sheep are not mentioned here.)&lt;/span&gt; They have no textiles, and man and woman alike wear the skin of sheep and oxen.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;A big tribe will have a &quot;Devil-Lord&quot;, (administering) 100 families with 200 cattle or horses. (Comment: We hold that this sentence is not definite.) They have no cotton cloth nor silk. Men and women all wear the skins of cattle or sheep.&lt;/p&gt;
|-
|第九程至制長館，於是始有門閣廨宇迎候供養之禮，皆漢地。
|On the ninth day one reaches '''Zhìzhǎngguǎn''' station (制長館) — a place of gates, pavilions, offices, welcome, resupply and proper manners — all people here are Han Chinese.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;At the ninth stage one reaches Chih-ch'ang-kuan (Inn). Here for the first time we find gates and pavilions, government buildings and houses. The etiquette of waiting and welcoming, of making presents and entertaining, are all (like) those of China.&lt;/p&gt;
|-
|凡從魯望行十二程方始到柘東。
|In total it is 12 days' journey from '''Lǔwàng''' (魯望; ie. Qujing?) to '''Tuodong''' (柘東&lt;ref&gt;Note that in other places the character 柘 is replaced with 拓 — ie. 拓东 — however the meaning here seems clear.&lt;/ref&gt;; ie. Kunming).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;From Lu-wang, going altogether 12 stages, one then first reaches Che-tung.&lt;/p&gt;
|-
|黎州南一百三十裏有清溪峽，乾元二年置關。
|130 ''li'' south of the '''Lizhou''' region (黎州; lit. black region) lies '''Qīngxīxiá''' gorge (清溪峽; ie. clear stream gorge), which was closed in the second year of the Qianyuan era (ie. ~759).&lt;ref&gt;The 乾元 (Qiányuán) era lasted from 758–760, and was one of the era names for the reign of Emeperor Suzong. From Wikipedia: &quot;Emperor Suzong of Tang (唐肅宗; February 21, 711 – May 16, 762; r. 756 – 762), personal name Li Heng (李亨), né Li Sisheng (李嗣升), known as Li Jun (李浚) from 725 to 736, known as Li Yu (李璵) from 736 to 738, known briefly as Li Shao (李紹) in 738, was an emperor of the Tang Dynasty and the son of Emperor Xuanzong. Suzong ascended the throne after his father fled to Sichuan during the An Shi Rebellion in 756; Li Heng himself had fled in the opposite direction, to Lingwu, where he was declared emperor by the army. Much of Emperor Suzong's reign was spent in quelling the aforementioned rebellion, which was ultimately put down in 763 during the reign of his son Emperor Daizong.&quot;&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;130 li south of Li-chou there is Ch'ing-ch'i gorge. Here, in the 2nd year of Ch'ien-yuan (759 A.D.) there was set up a frontier-gate (kuan).&lt;/p&gt;
|-
|關外三十裏即巂州界也。
|30 ''li'' beyond the pass is the border of '''Guīzhōu''' (巂州; ie. not modern Guizhou province, but rather the modern Xichang-Meigu region of southern Sichuan&lt;ref&gt;According to [https://zh.wikipedia.org/wiki/%E5%B7%82%E5%B7%9E Chinese Wikipedia].&lt;/ref&gt;).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;30 li beyond the frontier-gate, is the border of Sui-chou.&lt;/p&gt;
|-
|行三百五十裏至邛部川，故邛部縣之地也。
|A further 350 ''li'' brings you to '''Qióngbùchuān''' (邛部川; lit. Qiongbu upper-river region), formerly known as '''Qióngbùxiàn''' (邛部縣; lit. Qiongbu county).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Going 350 li, one reaches Chiung-pu-ch'uan (valley and stream). It is the land of the old Chiung-pu hsien.&lt;/p&gt;
|-
|下南一百三十裏至臺登，西南八十裏至普安城，劍南西川節度使重兵大將鎮焉。
|Southward 130 ''li'' lies '''Táidēng''' (臺登), and [a further?] southwest 80 ''li'' lies '''Pǔ'ānchéng''' (普安城), a large and important military garrison under the '''Jiànnán''' / '''Xīchuān''' (劍南西川) commandery (節度; jiédù).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Descending south 130 li, one reaches T'ai-teng. 80 li to the south-west, one reaches P'u-an city. The Chieh-tu-shih of Hsi-ch'uan of Chien-nan kept a garrison here with double reinforcements and a big general.&lt;/p&gt;
|-
|臺登直北去保塞城八十裏，吐蕃謂之北谷，天寶以前巂州柳強鎮也。
|Directly north from '''Táidēng''' (臺登) at a distance of 80 ''li'' lies '''Bǎosāi''' city (保塞城). The '''Tǔbō''' (吐蕃; ie. post-Tibetan Empire Kham Tibet) hold its '''Northern Gorge''' (北谷). It was formerly known as '''Liǔqiáng''' town (柳強鎮) of '''Guīzhōu''' (巂州).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;T'ai-teng, due north, is 80 li distant from Pao-sai city. The Tibetans called it Pei-ku, (Northern Ravine). Before the T'ien-pao period (742-755 A.D.) it was Liu-ch'iang-chen (garrison-town) of Sui-chou.&lt;/p&gt;
|-
|自入吐蕃，更增修崄，因城下有路向曩恭地。
|Since repelling the '''Tǔbō''' (吐蕃; ie. post-Tibetan Empire Kham Tibet), much work has been done atop the local peaks, as beneath the city lies the road to '''Nǎnggōng''' (曩恭).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Since its accession to the Tibetans, they have repaired and added to it and improved its strategic value. So below the city there is a road leading towards the land of Nang-kung.&lt;/p&gt;
|-
|谷東南一百三十裏至羅山城，天寶以後，吐蕃新築，非國家舊城。
|Southeast of the valley some 130 ''li'' one arrives at '''Luóshān''' city (羅山城), which after imperial rule has protected against the '''Tǔbō''' (吐蕃; ie. post-Tibetan Empire Kham Tibet), but was formerly an ancient city with no national affinity.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Going south-east 130 li, one reaches Lo-shan city. After the T'ien-pao period, the Tibetans rebuilt the old city of Fei-kuo-chia (or Fei State).&lt;/p&gt;
|-
|貞元十年十月，西川節度兵馬與雲南軍並力破保塞，大定，獻俘闕下。
|In the 10th month of the 10th year of the Zhengyuan era&lt;ref&gt;The Zhēngyuán (貞元) 785-805 era of Dezong. From Wikipedia: &quot;Emperor Dezong of Tang (唐德宗) (May 27, 742 – February 25, 805), personal name Li Kuo (李适), was an emperor of the Chinese Tang Dynasty and the oldest son of his father Emperor Daizong. His reign of 26 years was the third longest in the Tang dynasty (surpassed only by Emperor Xuanzong and Emperor Gaozong). Emperor Dezong started out as a diligent and frugal emperor and he tried to reform the governmental finances by introducing new tax laws. His attempts to destroy the powerful regional warlords and the subsequent mismanagement of those campaigns, however, resulted in a number of rebellions that nearly destroyed him and the Tang Dynasty. After those events, he dealt cautiously with the regional governors, causing warlordism to become unchecked, and his trust of eunuchs caused the eunuchs' power to rise greatly. He was also known for his paranoia about officials' wielding too much power, and late in his reign, he did not grant much authority to his chancellors.&quot;&lt;/ref&gt; (ie. ~795CE), the '''Xīchuān''' (西川) commandery gave troops to the Yunnan military for defense, and a great battle occurred beneath the '''Xiànfúquè''' (獻俘闕; lit. prisoner-taking tower).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;In the 10th month of the 10th year of Cheng-yuan (Oct. 29th-Nov. 26th, 794 A.D.), the infantry and cavalry of the Chieh-tu of Hsi-ch'uan, joined forces with the army of Yunnan, and destroyed Pao-sai, greatly pacified (the country), and presented prisoners of war at the Gate of the Court.&lt;/p&gt;
|-
|十一年正月，西川又拔羅山，置兵固守。
|Three months later, '''Xīchuān''' (西川) again raided the mountains, permanently establishing troops for defense.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;In the 1st month of the 11th year (Jan. 26th-Feb. 23rd,795 A.D.) Hsi-ch'uan went on to capture Lo-shan, and stationed troops there to keep strong guard.&lt;/p&gt;
|-
|邛南驛路由此遂通。
|The '''Qióngnányì Road''' (邛南驛路; lit. 'the relay road south from Qióngbù') was thus finally made open.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;The postal-service road south of Chiung henceforward could communicate with T'ai-teng city.&lt;/p&gt;
|-
|臺登城直西有西望川，行一百五十裏入曲羅。
|Directly west of '''Táidēng''' (臺登) lies '''Xīwàngchuān''' (西望川; lit. the upper-river region of Xiwang), from which journeying 150 ''li'' one enters '''Qūluó''' (曲羅).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;Due west there is Hsi-wang-ch'uan (Looking West Stream). Going 150 li, it enters Ch'u-lo (or the meandering Lu-shui?).&lt;/p&gt;
|-
|瀘水從北來，至曲羅縈迥三曲。
|[However,] if coming from '''Lúshuǐ''' (瀘水; lit. rushing waters) one approaches from the north,&lt;ref&gt;I believe that is the correct reading, at least!&lt;/ref&gt; arriving at '''Qūluó''' (曲羅) along three crooked roads.&lt;ref&gt;This last past is uncertain/vague.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;The Lu-shui comes from the north, and reaches Chu-lo (the Meanders?) and winds round and round in three curves.&lt;/p&gt;
|-
|每中間皆有磨些部落，以其負阻深險，承上莫能攻討同川。
|Everywhere in between is deep and dangerous passes, that even the most talented general cannot tame.&lt;ref&gt;Vague.&lt;/ref&gt;
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;In the middle of each there are Mo-so tribes. On account being stopped by deep abysses and dangerous heights, no Cheng-shang has yet been able to attack or punish them. (Comment: We hold that Cheng-shang is the name of a Man official. See what follows)&lt;/p&gt;
|-
|邊水左右，總謂之西蠻。
|On either side of the water, the '''Western Barbarians''' (西蠻) are said to lie.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;&lt;/p&gt;
|-
|邛部東南三百五十裏至勿鄧部落，入鬼主夢沖，地方闊千裏。
|350 ''li'' southeast of '''Qióngbù''' (邛部) is '''Wùdèng''' (勿鄧), a place 1000 ''li'' wide under the rule of the barbarian lord '''Mèngchōng''' (夢沖).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;&lt;/p&gt;
|-
|邛部一姓白蠻，五姓烏蠻。
|For each house in '''Qióngbù''' (邛部) there are 100 barbarians; and for each five houses, one black barbarian.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;&lt;/p&gt;
|-
|初止五姓，在邛部、臺登中間，皆烏蠻也。
|Other than five households, in between '''Táidēng''' (臺登) and '''Qióngbù''' (邛部) all are black barbarians.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;&lt;/p&gt;
|-
|婦人以黑繪為衣，其長曳地，又束、欽兩姓在北谷，皆白蠻，三姓皆屬。
|Married women use black pigment of smeared dirt as clothing, albeit carefully applied. Except two households of the '''Northern Gorge''' (北谷), all are barbarians, including the other three households.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;&lt;/p&gt;
|-
|夢沖內受恩賞於國，外私於吐蕃。
|In areas controlled by '''Mèngchōng''' (夢沖), the country is peaceful, and beyond lies '''Tǔbō''' (吐蕃; ie. post-Tibetan Empire Kham Tibet).
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;&lt;/p&gt;
|-
|貞元七年，節度使韋臯使巂州刺史蘇隗殺夢沖，因別立大鬼主。
|In the seventh year of the Zhengyuan era (ie. ~792CE), the government sent (weigao?) to kill mengchong, in order to prevent him from becoming barbarian king.
|&lt;p style=&quot;color:#aaa;font-size:80%;line-height:110%&quot;&gt;&lt;/p&gt;
|-
|勿鄧南七十裏有兩姓部落。&lt;span style=&quot;color:#aaa&quot;&gt;(案：此下當有闕文)&lt;/span&gt;
|70 ''li'' south of '''Wùdèng''' (勿鄧) is the domain of the two households.
|}

==References and notes==
{{reflist}}</text>
      <sha1>9rqhubuy7z5ipb527pie1mun7cli7gx</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Sandbox</title>
    <ns>4</ns>
    <id>464822</id>
    <revision>
      <id>4668915</id>
      <parentid>4668884</parentid>
      <timestamp>2026-09-05T12:00:49Z</timestamp>
      <contributor>
        <username>JackBot</username>
        <id>396820</id>
      </contributor>
      <minor />
      <comment>Bot: Automatically cleaned</comment>
      <origin>4668915</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="201" sha1="efa5udpbb942msq2oco4mlj2yz47q14" xml:space="preserve">{{Sandbox heading}}
&lt;!-- Hello! Feel free to try your formatting and editing skills below this line. As this page is for editing experiments, this page will automatically be cleaned every 12 hours. --&gt;</text>
      <sha1>efa5udpbb942msq2oco4mlj2yz47q14</sha1>
    </revision>
  </page>
  <page>
    <title>User:Mazimil/sandbox</title>
    <ns>2</ns>
    <id>465564</id>
    <revision>
      <id>4668990</id>
      <parentid>4377009</parentid>
      <timestamp>2026-09-05T19:03:06Z</timestamp>
      <contributor>
        <username>ShakespeareFan00</username>
        <id>46022</id>
      </contributor>
      <minor />
      <comment>Attempting to solve lints - Please ignore the notification this edit generated.</comment>
      <origin>4668990</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5901" sha1="1gjrfv734f5c417o3l1mf2xl7pwehao" xml:space="preserve">&lt;div style=&quot;width:100%; clear:both; float:left; text-align:center; padding-bottom: 1em; &quot;&gt;
&lt;!----&gt;&lt;div style=&quot;font-size:162%; padding:0.1em;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to [[Wikibooks:What is Wikibooks|Wikibooks]],&lt;/div&gt;
&lt;!----&gt;&lt;div style=&quot;font-size:95%; padding-top:0.2em;&quot;&gt;the open-content textbooks collection that [[Help:Contributing|anyone can edit]].&lt;/div&gt;
&lt;!----&gt;&lt;div id=&quot;pagecount&quot; style=&quot;font-size:85%;&quot;&gt;[[Wikibooks Stacks/Departments|{{NUMBEROFBOOKS}} books]] with [[Special:Allpages|{{NUMBEROFARTICLES}} pages]].&lt;!-- above div --&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div style=&quot;flex: 1 0 50%; width:100%; min-width:10em; float: right; box-sizing: border-box; font-size:95%; display: flex; flex-wrap: wrap;&quot;&gt;
&lt;div style=&quot;width:100%; text-align:center&quot;&gt;'''Browse Bookshelves'''&lt;/div&gt;
&lt;!----&gt;&lt;div style=&quot;float:left; width:25%; flex: 1 0 25%; min-width: 12em;&quot;&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Computing|Computing]]&lt;/div&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Engineering|Engineering]]&lt;/div&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Humanities|Humanities]]&lt;/div&gt;
&lt;!----&gt;&lt;/div&gt;
&lt;!----&gt;&lt;div style=&quot;float:left; width:25%; flex: 1 0 25%; min-width: 12em;&quot;&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Languages|Languages]]&lt;/div&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Mathematics|Mathematics]]&lt;/div&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Miscellaneous|Miscellaneous]]&lt;/div&gt;
&lt;!----&gt;&lt;/div&gt;
&lt;!----&gt;&lt;div style=&quot;float:left; width:25%; flex: 1 0 25%; min-width: 12em;&quot;&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Recreational activities|Recreational activities]]&lt;/div&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Science|Science]]&lt;/div&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Social sciences|Social sciences]]&lt;/div&gt;
&lt;!----&gt;&lt;/div&gt;
&lt;!----&gt;&lt;div style=&quot;float:left; width:25%; flex: 1 0 25%; min-width: 12em;&quot;&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Standard curricula|Standard curricula]]&lt;/div&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;[[Department:Wikijunior|Wikijunior]]&lt;/div&gt;
&lt;div style=&quot;background-color:#F3F3F3;{{Text default color}}; text-align:center; margin: 4pt 2pt;&quot;&gt;'''[[Wikibooks Stacks/Departments|All subjects]]'''&lt;/div&gt;
&lt;!----&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div id=&quot;mf-main&quot; style=&quot;width:100%; margin:0px; padding:0px 5px 5px 5px; &quot;&gt;&lt;!-- Opening div --&gt;
&lt;div id=&quot;mf-help&quot; style=&quot;clear:both; text-align:center; font-size:95%; margin:0em 1em 0em 1em;&quot;&gt;

[[Wikibooks:Featured books|Featured books]] •
[[Wikijunior|Wikijunior]] •
[[Cookbook:Table of Contents|Cookbook]] •
[[Wikibooks:Card Catalog Office|Browse books]] •
[[Help:Contents|Help]] •
[[Wikibooks:Reading room|Forum]] •
[[Using Wikibooks]]
&lt;/div&gt;
&lt;div style=&quot;clear:both; width:100%; margin: 25px 0 0 0; display: flex; flex-wrap: wrap; box-sizing: border-box; &quot; id=&quot;mp-content&quot;&gt;
&lt;div style=&quot;width:100%; text-align:center&quot;&gt;'''Today's Featured Content'''&lt;/div&gt;
&lt;!----&gt;&lt;div style=&quot;box-sizing: border-box; float:left; flex: 1 0 33%; width:33%; border: 0.2em solid #FAFAFA; padding: 1em; background-color:#F3F3F3;{{Text default color}}; min-width: 20em; overflow:hidden; &quot;&gt;{{:Main Page/Featured}}&lt;/div&gt;
&lt;!----&gt;&lt;div style=&quot;box-sizing: border-box; float:left; flex: 1 0 33%; width:33%; border: 0.2em solid #FAFAFA; padding: 1em; background-color:#F3F3F3;{{Text default color}}; min-width: 20em; overflow:hidden; &quot;&gt;{{:Main Page/Wikijunior}}&lt;/div&gt;
&lt;!----&gt;&lt;div style=&quot;box-sizing: border-box; float:left; flex: 1 0 33%; width:33%; border: 0.2em solid #FAFAFA; padding: 1em; background-color:#F3F3F3;{{Text default color}}; min-width: 20em; overflow:hidden; &quot;&gt;{{:Main Page/Recipe}}&lt;/div&gt;&lt;!--

1. Promoted shelf

--&gt;
&lt;!----&gt;&lt;div style=&quot;box-sizing: border-box; float:left; flex: 1 0 33%; width:33%; border: 0.2em solid #FAFAFA; padding: 1em; background-color:#F3F3F3;{{Text default color}}; min-width: 20em; overflow:hidden; &quot;&gt;{{Promoted shelf|title=Shelf:Games|cover=Chess_board_blank.svg|desc=[[Shelf:Games]] contains books on games, and includes the subsection shelves [[Shelf:Athletic games|athletic games]], [[Shelf:Board games|board games]], [[Shelf:Card games|card games]], [[Shelf:Electronic games|electronic games]], and [[Shelf:Game design|game design]].}}&lt;/div&gt;&lt;!--

2. Promoted shelf

--&gt;
&lt;!----&gt;&lt;div style=&quot;box-sizing: border-box; float:left; flex: 1 0 33%; width:33%; border: 0.2em solid #FAFAFA; padding: 1em; background-color:#F3F3F3;{{Text default color}}; min-width: 20em; overflow:hidden; &quot;&gt;{{Promoted shelf|title=Shelf:Computer programming|cover=Openscad SVG.svg|desc=[[Shelf:Computer programming]] contains books on programming, such as [[LaTeX]], [[OpenSCAD User Manual]], [[Python Programming]], and [[Java Programming]].}}&lt;/div&gt;&lt;!--

3. Promoted shelf

--&gt;
&lt;!----&gt;&lt;div style=&quot;box-sizing: border-box; float:left; flex: 1 0 33%; width:33%; border: 0.2em solid #FAFAFA; padding: 1em; background-color:#F3F3F3;{{Text default color}}; min-width: 20em; overflow:hidden; &quot;&gt;{{Promoted shelf|title=Shelf:Languages of Asia|cover=Taj Mahal in March 2004.jpg|desc=[[Shelf:Languages of Asia]] contains books on Asian languages, such as [[Marathi]], [[Bengali]], [[Kannada]], [[Hindi]], and [[Sanskrit]].}}&lt;/div&gt;
&lt;/div&gt;
{{:Main Page/Sisters}}
&lt;/div&gt;&lt;!-- Closing div --&gt;
[[Category:Main page| ]]</text>
      <sha1>1gjrfv734f5c417o3l1mf2xl7pwehao</sha1>
    </revision>
  </page>
  <page>
    <title>User:JJPMaster (bot)/markAdmins-Data.json</title>
    <ns>2</ns>
    <id>471107</id>
    <revision>
      <id>4668986</id>
      <parentid>4668674</parentid>
      <timestamp>2026-09-05T18:49:14Z</timestamp>
      <contributor>
        <username>JJPMaster (bot)</username>
        <id>3488561</id>
      </contributor>
      <minor />
      <comment>Bot: Updating markAdmins data</comment>
      <origin>4668986</origin>
      <model>json</model>
      <format>application/json</format>
      <text bytes="52604" sha1="eplf7a8mnfwvjpp7hcq87fanlokv7bz" xml:space="preserve">{
	&quot;.snoopy.&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;1234qwer1234qwer4&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;
	],
	&quot;157yagz5r48a5f1a1f&quot;: [
		&quot;editor&quot;
	],
	&quot;1997kB&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;editor&quot;
	],
	&quot;1F616EMO&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;1exec1&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;1sfoerster&quot;: [
		&quot;editor&quot;
	],
	&quot;20041027 tatsu&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;2005-Fan&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;331dot&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;33rogers&quot;: [
		&quot;editor&quot;
	],
	&quot;3MMPEYTON&quot;: [
		&quot;editor&quot;
	],
	&quot;4PlayerChess&quot;: [
		&quot;autoreview&quot;
	],
	&quot;4pillars&quot;: [
		&quot;editor&quot;
	],
	&quot;511KeV&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;94rain&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;A R King&quot;: [
		&quot;editor&quot;
	],
	&quot;A Sulaiman Z&quot;: [
		&quot;editor&quot;
	],
	&quot;A.K.Karthikeyan&quot;: [
		&quot;editor&quot;
	],
	&quot;A09&quot;: [
		&quot;steward&quot;
	],
	&quot;AFBorchert&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;AIProf&quot;: [
		&quot;editor&quot;
	],
	&quot;ALittleSlow&quot;: [
		&quot;autoreview&quot;
	],
	&quot;AManWithNoPlan&quot;: [
		&quot;editor&quot;
	],
	&quot;ATannedBurger&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;AVRS&quot;: [
		&quot;editor&quot;
	],
	&quot;Aafi&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Abenwagner&quot;: [
		&quot;editor&quot;
	],
	&quot;Abigor&quot;: [
		&quot;editor&quot;
	],
	&quot;Abitt002&quot;: [
		&quot;editor&quot;
	],
	&quot;Abyssal&quot;: [
		&quot;editor&quot;
	],
	&quot;Acagastya&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Acalamari&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Acarologiste&quot;: [
		&quot;editor&quot;
	],
	&quot;AcidBat&quot;: [
		&quot;editor&quot;
	],
	&quot;Acrow005&quot;: [
		&quot;editor&quot;
	],
	&quot;Actualist&quot;: [
		&quot;editor&quot;
	],
	&quot;Adalvis&quot;: [
		&quot;editor&quot;
	],
	&quot;Adart001&quot;: [
		&quot;editor&quot;
	],
	&quot;Adavyd&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Addihockey10&quot;: [
		&quot;editor&quot;
	],
	&quot;Addihockey10 (automated)&quot;: [
		&quot;editor&quot;
	],
	&quot;Adrignola&quot;: [
		&quot;editor&quot;
	],
	&quot;AdventureWriter&quot;: [
		&quot;editor&quot;
	],
	&quot;Aelxen&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Aferg006&quot;: [
		&quot;editor&quot;
	],
	&quot;Afett001&quot;: [
		&quot;editor&quot;
	],
	&quot;Affe2011&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Agnerf&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Agpires&quot;: [
		&quot;editor&quot;
	],
	&quot;Agricola&quot;: [
		&quot;editor&quot;
	],
	&quot;Agusbou2015&quot;: [
		&quot;editor&quot;
	],
	&quot;Ah3kal&quot;: [
		&quot;editor&quot;
	],
	&quot;Ahecht&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ahonc&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;AiClassEland&quot;: [
		&quot;editor&quot;
	],
	&quot;Ainz Ooal Gown&quot;: [
		&quot;editor&quot;
	],
	&quot;Airpmb&quot;: [
		&quot;editor&quot;
	],
	&quot;Ajraddatz&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;
	],
	&quot;Aka&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Alanah.97&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Albertoleoncio&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Albmont&quot;: [
		&quot;editor&quot;
	],
	&quot;Alchimista&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Aldnonymous&quot;: [
		&quot;editor&quot;
	],
	&quot;Aledownload&quot;: [
		&quot;editor&quot;
	],
	&quot;Alexlatham96&quot;: [
		&quot;editor&quot;
	],
	&quot;Alextejthompson&quot;: [
		&quot;editor&quot;
	],
	&quot;Alison&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;AllenZh&quot;: [
		&quot;editor&quot;
	],
	&quot;Alphama&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;AlvaroMolina&quot;: [
		&quot;editor&quot;
	],
	&quot;AmandaNP&quot;: [
		&quot;steward&quot;
	],
	&quot;Ambrevar&quot;: [
		&quot;editor&quot;
	],
	&quot;Amcgail&quot;: [
		&quot;editor&quot;
	],
	&quot;Ameisenigel&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;ombuds&quot;,
		&quot;editor&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;AmieKim&quot;: [
		&quot;editor&quot;
	],
	&quot;Amire80&quot;: [
		&quot;global-sysop&quot;
	],
	&quot;Anachronist&quot;: [
		&quot;editor&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ancient9983&quot;: [
		&quot;editor&quot;
	],
	&quot;Andrei Stroe&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Andrew janke&quot;: [
		&quot;editor&quot;
	],
	&quot;Andriy.v&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Andyross&quot;: [
		&quot;editor&quot;
	],
	&quot;Anil Shaligram&quot;: [
		&quot;editor&quot;
	],
	&quot;Animajosser&quot;: [
		&quot;editor&quot;
	],
	&quot;Anne Correia&quot;: [
		&quot;editor&quot;
	],
	&quot;Anonim Şahıs&quot;: [
		&quot;editor&quot;
	],
	&quot;Anonymity&quot;: [
		&quot;editor&quot;
	],
	&quot;AnotherEditor144&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Antanana&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Antandrus&quot;: [
		&quot;editor&quot;
	],
	&quot;Anthere&quot;: [
		&quot;editor&quot;
	],
	&quot;AntiCompositeNumber&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Antonizoon&quot;: [
		&quot;editor&quot;
	],
	&quot;Antonw&quot;: [
		&quot;editor&quot;
	],
	&quot;Apfelmus&quot;: [
		&quot;editor&quot;
	],
	&quot;Aphoneyclimber&quot;: [
		&quot;editor&quot;
	],
	&quot;Aplucas0703&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Apocheir&quot;: [
		&quot;editor&quot;
	],
	&quot;Aqurs1&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;
	],
	&quot;AramilFeraxa&quot;: [
		&quot;steward&quot;
	],
	&quot;Arch dude&quot;: [
		&quot;editor&quot;
	],
	&quot;Archolman&quot;: [
		&quot;editor&quot;
	],
	&quot;Arcticocean&quot;: [
		&quot;ombuds&quot;
	],
	&quot;ArdentPerf&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Arian&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Arlen22&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;Armchair&quot;: [
		&quot;editor&quot;
	],
	&quot;Arno-nl&quot;: [
		&quot;editor&quot;
	],
	&quot;Arrow303&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Arthurvogel&quot;: [
		&quot;editor&quot;
	],
	&quot;Artoria2e5&quot;: [
		&quot;editor&quot;
	],
	&quot;Arturoiochoam&quot;: [
		&quot;editor&quot;
	],
	&quot;Arunreginald&quot;: [
		&quot;editor&quot;
	],
	&quot;AshLin&quot;: [
		&quot;editor&quot;
	],
	&quot;Atcovi&quot;: [
		&quot;sysop&quot;,
		&quot;global-rollbacker&quot;
	],
	&quot;Athrash&quot;: [
		&quot;editor&quot;
	],
	&quot;Atiedebee&quot;: [
		&quot;editor&quot;
	],
	&quot;Atlas.Spheres&quot;: [
		&quot;editor&quot;
	],
	&quot;Atsme&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Auremel&quot;: [
		&quot;editor&quot;
	],
	&quot;Austncorp&quot;: [
		&quot;editor&quot;
	],
	&quot;AuthorsAndContributorsBot&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Avicennasis&quot;: [
		&quot;editor&quot;
	],
	&quot;Avraham&quot;: [
		&quot;global-renamer&quot;,
		&quot;editor&quot;
	],
	&quot;Awesome Princess&quot;: [
		&quot;editor&quot;
	],
	&quot;Axpde&quot;: [
		&quot;editor&quot;
	],
	&quot;Az1568&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Az2008&quot;: [
		&quot;editor&quot;
	],
	&quot;Azotochtli&quot;: [
		&quot;editor&quot;
	],
	&quot;B.Korlah&quot;: [
		&quot;editor&quot;
	],
	&quot;BD2412&quot;: [
		&quot;editor&quot;
	],
	&quot;BORGATO Pierandrea&quot;: [
		&quot;editor&quot;
	],
	&quot;BRPever&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;BRUTE&quot;: [
		&quot;editor&quot;
	],
	&quot;Backfromquadrangle&quot;: [
		&quot;editor&quot;
	],
	&quot;Baiji&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Bakasakali&quot;: [
		&quot;editor&quot;
	],
	&quot;Balaji.md au&quot;: [
		&quot;editor&quot;
	],
	&quot;BarkingFish&quot;: [
		&quot;editor&quot;
	],
	&quot;Barras&quot;: [
		&quot;steward&quot;
	],
	&quot;Base&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Bastique&quot;: [
		&quot;editor&quot;
	],
	&quot;Bautsch&quot;: [
		&quot;editor&quot;
	],
	&quot;BeardMD&quot;: [
		&quot;editor&quot;
	],
	&quot;Beetstra&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;BenTels&quot;: [
		&quot;editor&quot;
	],
	&quot;Bencemac&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Benjamin J. Burger&quot;: [
		&quot;editor&quot;
	],
	&quot;Benjamin.doe&quot;: [
		&quot;editor&quot;
	],
	&quot;Benrattray&quot;: [
		&quot;editor&quot;
	],
	&quot;Benson Muite&quot;: [
		&quot;editor&quot;
	],
	&quot;Bentbracke&quot;: [
		&quot;editor&quot;
	],
	&quot;Bequw&quot;: [
		&quot;editor&quot;
	],
	&quot;Bert Niehaus&quot;: [
		&quot;autoreview&quot;
	],
	&quot;BethNaught&quot;: [
		&quot;editor&quot;
	],
	&quot;Beuc&quot;: [
		&quot;editor&quot;
	],
	&quot;Bhardwaj Anil&quot;: [
		&quot;autoreview&quot;
	],
	&quot;BiT&quot;: [
		&quot;editor&quot;
	],
	&quot;Bigdelboy&quot;: [
		&quot;transwiki&quot;
	],
	&quot;Bignose~enwikibooks&quot;: [
		&quot;editor&quot;
	],
	&quot;Billinghurst&quot;: [
		&quot;editor&quot;
	],
	&quot;Billymac00&quot;: [
		&quot;editor&quot;
	],
	&quot;Biplab Anand&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Birdofadozentides&quot;: [
		&quot;editor&quot;
	],
	&quot;BitterAsianMan&quot;: [
		&quot;editor&quot;
	],
	&quot;Bluefoxicy&quot;: [
		&quot;editor&quot;
	],
	&quot;Bluerasberry&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;BobChan2&quot;: [
		&quot;editor&quot;
	],
	&quot;Bobby Cohn&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Bodhisattwa&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;BoldLuis&quot;: [
		&quot;editor&quot;
	],
	&quot;Borhan&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Boris1951zz&quot;: [
		&quot;editor&quot;
	],
	&quot;Bpenn005&quot;: [
		&quot;editor&quot;
	],
	&quot;Brewster239&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Bridget&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Brienna.Hall77&quot;: [
		&quot;editor&quot;
	],
	&quot;Brim&quot;: [
		&quot;editor&quot;
	],
	&quot;Brittanys&quot;: [
		&quot;editor&quot;
	],
	&quot;Bronwynh&quot;: [
		&quot;editor&quot;
	],
	&quot;Bsadowski1&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;
	],
	&quot;Buddpaul&quot;: [
		&quot;editor&quot;
	],
	&quot;Bullercruz1&quot;: [
		&quot;editor&quot;
	],
	&quot;Buncic&quot;: [
		&quot;editor&quot;
	],
	&quot;Bunnypranav&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;BurakD53&quot;: [
		&quot;editor&quot;
	],
	&quot;Burkep&quot;: [
		&quot;editor&quot;
	],
	&quot;ByGrace&quot;: [
		&quot;editor&quot;
	],
	&quot;Bykim2012&quot;: [
		&quot;editor&quot;
	],
	&quot;C1203sc&quot;: [
		&quot;editor&quot;
	],
	&quot;CJakes1&quot;: [
		&quot;editor&quot;
	],
	&quot;CKWG - Ada Magica&quot;: [
		&quot;editor&quot;
	],
	&quot;Cabayi&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;CaitlinCarbury&quot;: [
		&quot;autoreview&quot;
	],
	&quot;CalciumTetraoxide&quot;: [
		&quot;editor&quot;
	],
	&quot;CalendulaAsteraceae&quot;: [
		&quot;editor&quot;
	],
	&quot;Caliburn&quot;: [
		&quot;editor&quot;
	],
	&quot;CallumPoole&quot;: [
		&quot;editor&quot;
	],
	&quot;Calvin.Andrus&quot;: [
		&quot;editor&quot;
	],
	&quot;Cameron11598&quot;: [
		&quot;editor&quot;
	],
	&quot;Camouflaged Mirage&quot;: [
		&quot;editor&quot;
	],
	&quot;Captain-tucker&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Carlo.milanesi&quot;: [
		&quot;editor&quot;
	],
	&quot;Caro de Segeda&quot;: [
		&quot;editor&quot;
	],
	&quot;CarsracBot&quot;: [
		&quot;editor&quot;
	],
	&quot;Catermark&quot;: [
		&quot;editor&quot;
	],
	&quot;Cecila123&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Cedar101&quot;: [
		&quot;editor&quot;
	],
	&quot;Champion&quot;: [
		&quot;editor&quot;
	],
	&quot;Chaojidage&quot;: [
		&quot;editor&quot;
	],
	&quot;Chaojoker&quot;: [
		&quot;editor&quot;
	],
	&quot;Chaotic Enby&quot;: [
		&quot;autoreview&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Chapka&quot;: [
		&quot;editor&quot;
	],
	&quot;Charidri&quot;: [
		&quot;editor&quot;
	],
	&quot;Charleneabeana&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Charles Jeffrey Danoff&quot;: [
		&quot;editor&quot;
	],
	&quot;CharlesHoffman&quot;: [
		&quot;editor&quot;
	],
	&quot;Chazz&quot;: [
		&quot;editor&quot;
	],
	&quot;Chelseafan528&quot;: [
		&quot;editor&quot;
	],
	&quot;Cheryl2012&quot;: [
		&quot;editor&quot;
	],
	&quot;Chescargot&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Chi Sigma&quot;: [
		&quot;editor&quot;
	],
	&quot;Chinmayee Mishra&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Chongkian&quot;: [
		&quot;editor&quot;
	],
	&quot;Chowbok&quot;: [
		&quot;editor&quot;
	],
	&quot;ChrisHodgesUK&quot;: [
		&quot;editor&quot;
	],
	&quot;ChrisWallace&quot;: [
		&quot;editor&quot;
	],
	&quot;Chriswaterguy&quot;: [
		&quot;editor&quot;
	],
	&quot;Chuckhoffmann&quot;: [
		&quot;editor&quot;
	],
	&quot;Church of emacs&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Cic&quot;: [
		&quot;editor&quot;
	],
	&quot;Ciell&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Cilantrohead&quot;: [
		&quot;editor&quot;
	],
	&quot;Cintilo&quot;: [
		&quot;editor&quot;
	],
	&quot;Circuit dreamer&quot;: [
		&quot;editor&quot;
	],
	&quot;Circuit-fantasist&quot;: [
		&quot;editor&quot;
	],
	&quot;Civvì&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Ckwalker&quot;: [
		&quot;editor&quot;
	],
	&quot;Clairerusselll&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Cloidl&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Cmsmcq&quot;: [
		&quot;editor&quot;
	],
	&quot;Cnrowley&quot;: [
		&quot;editor&quot;
	],
	&quot;CocoaZen&quot;: [
		&quot;editor&quot;
	],
	&quot;CoconutOctopus&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Codename Noreste&quot;: [
		&quot;sysop&quot;,
		&quot;global-rollbacker&quot;,
		&quot;interface-admin&quot;
	],
	&quot;Codename Noroeste&quot;: [
		&quot;editor&quot;
	],
	&quot;Codinghead&quot;: [
		&quot;editor&quot;
	],
	&quot;CommonsDelinker&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Comp.arch&quot;: [
		&quot;editor&quot;
	],
	&quot;Conan&quot;: [
		&quot;editor&quot;
	],
	&quot;Cormullion&quot;: [
		&quot;editor&quot;
	],
	&quot;Count Count&quot;: [
		&quot;steward&quot;
	],
	&quot;Coupe&quot;: [
		&quot;editor&quot;
	],
	&quot;Courcelles&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;CptViraj&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Craignewland&quot;: [
		&quot;editor&quot;
	],
	&quot;Craxd1&quot;: [
		&quot;editor&quot;
	],
	&quot;CrazyEddy&quot;: [
		&quot;editor&quot;
	],
	&quot;Cremastra&quot;: [
		&quot;editor&quot;
	],
	&quot;Cremastra (JWB)&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Cromium&quot;: [
		&quot;editor&quot;
	],
	&quot;Cromwellt&quot;: [
		&quot;editor&quot;
	],
	&quot;Crystal East&quot;: [
		&quot;editor&quot;
	],
	&quot;Cttcraig&quot;: [
		&quot;editor&quot;
	],
	&quot;Cultures17&quot;: [
		&quot;editor&quot;
	],
	&quot;Cultures33&quot;: [
		&quot;editor&quot;
	],
	&quot;Cultures4&quot;: [
		&quot;editor&quot;
	],
	&quot;Cultures92&quot;: [
		&quot;editor&quot;
	],
	&quot;CunninghamJohn&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Curtaintoad&quot;: [
		&quot;editor&quot;
	],
	&quot;Cyberpower678&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Céréales Killer&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;D1n05aur5 4ever&quot;: [
		&quot;editor&quot;
	],
	&quot;DARIO SEVERI&quot;: [
		&quot;autoreview&quot;,
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;DC Slagel&quot;: [
		&quot;editor&quot;
	],
	&quot;DCB&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;DD 8630&quot;: [
		&quot;editor&quot;
	],
	&quot;DERDAKI ILIAS&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;DGerman&quot;: [
		&quot;editor&quot;
	],
	&quot;DVD206&quot;: [
		&quot;editor&quot;
	],
	&quot;DZadventiste&quot;: [
		&quot;editor&quot;
	],
	&quot;DaB.&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;DaGizza&quot;: [
		&quot;editor&quot;
	],
	&quot;Dagana4&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Dallas1278&quot;: [
		&quot;editor&quot;
	],
	&quot;Dan Koehl&quot;: [
		&quot;editor&quot;
	],
	&quot;Dan Polansky&quot;: [
		&quot;editor&quot;
	],
	&quot;Dan-aka-jack&quot;: [
		&quot;editor&quot;
	],
	&quot;DanCherek&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Danarwaller&quot;: [
		&quot;editor&quot;
	],
	&quot;DanielWhernchend&quot;: [
		&quot;editor&quot;
	],
	&quot;Danielravennest&quot;: [
		&quot;editor&quot;
	],
	&quot;Danilka5469&quot;: [
		&quot;editor&quot;
	],
	&quot;Daniuu&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;DannyS712&quot;: [
		&quot;editor&quot;
	],
	&quot;Darklama&quot;: [
		&quot;editor&quot;
	],
	&quot;Darklilac&quot;: [
		&quot;editor&quot;
	],
	&quot;Darrelljon&quot;: [
		&quot;editor&quot;
	],
	&quot;DarwIn&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Dave Braunschweig&quot;: [
		&quot;editor&quot;
	],
	&quot;David L Davis&quot;: [
		&quot;editor&quot;
	],
	&quot;DavidCary&quot;: [
		&quot;editor&quot;
	],
	&quot;DavidLevinson&quot;: [
		&quot;editor&quot;
	],
	&quot;Davidbena&quot;: [
		&quot;editor&quot;
	],
	&quot;Dayshade&quot;: [
		&quot;editor&quot;
	],
	&quot;Dchmelik&quot;: [
		&quot;editor&quot;
	],
	&quot;Dcljr&quot;: [
		&quot;editor&quot;
	],
	&quot;Dcondon&quot;: [
		&quot;editor&quot;
	],
	&quot;Deepfriedokra&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;DejaVu&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;DennisDaniels&quot;: [
		&quot;editor&quot;
	],
	&quot;Dennisblu&quot;: [
		&quot;uploader&quot;
	],
	&quot;Denniss&quot;: [
		&quot;editor&quot;
	],
	&quot;Der-Wir-Ing&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;DerHexer&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Derek Andrews&quot;: [
		&quot;editor&quot;
	],
	&quot;Designermadsen&quot;: [
		&quot;editor&quot;
	],
	&quot;Deu&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Dexxor&quot;: [
		&quot;editor&quot;
	],
	&quot;Dezedien&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Diandramartin&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Didym&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Dino Bronto Rex&quot;: [
		&quot;editor&quot;
	],
	&quot;Dirk Hünniger&quot;: [
		&quot;editor&quot;
	],
	&quot;Divinations&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Djb&quot;: [
		&quot;editor&quot;
	],
	&quot;Djbrown&quot;: [
		&quot;editor&quot;
	],
	&quot;Dlrohrer2003&quot;: [
		&quot;editor&quot;
	],
	&quot;Dmccreary&quot;: [
		&quot;editor&quot;
	],
	&quot;Doc Taxon&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Doctorxgc&quot;: [
		&quot;editor&quot;
	],
	&quot;Dom walden&quot;: [
		&quot;editor&quot;
	],
	&quot;Domdomegg&quot;: [
		&quot;editor&quot;
	],
	&quot;DominikTurner&quot;: [
		&quot;autoreview&quot;
	],
	&quot;DonaldKronos&quot;: [
		&quot;editor&quot;
	],
	&quot;DoubleGrazing&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Doubleotoo&quot;: [
		&quot;editor&quot;
	],
	&quot;Downdate&quot;: [
		&quot;editor&quot;
	],
	&quot;Dr-Taher&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Dr.Unclear&quot;: [
		&quot;editor&quot;
	],
	&quot;Dreftymac&quot;: [
		&quot;editor&quot;
	],
	&quot;Drpundir&quot;: [
		&quot;editor&quot;
	],
	&quot;Drummingman&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;DuLithgow&quot;: [
		&quot;editor&quot;
	],
	&quot;Dungodung&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Duplode&quot;: [
		&quot;editor&quot;
	],
	&quot;DustDFG&quot;: [
		&quot;editor&quot;
	],
	&quot;Dyolf77&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;EDCU320RHT&quot;: [
		&quot;editor&quot;
	],
	&quot;EDUC320 Sylvialiang&quot;: [
		&quot;editor&quot;
	],
	&quot;EE JRW&quot;: [
		&quot;editor&quot;
	],
	&quot;EMAD KAYYAM&quot;: [
		&quot;editor&quot;
	],
	&quot;EPIC&quot;: [
		&quot;steward&quot;
	],
	&quot;EarlGrey2005&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Ebe123&quot;: [
		&quot;editor&quot;
	],
	&quot;Ecarew&quot;: [
		&quot;editor&quot;
	],
	&quot;Edgar181&quot;: [
		&quot;editor&quot;
	],
	&quot;Edit filter&quot;: [
		&quot;sysop&quot;
	],
	&quot;EdoDodo&quot;: [
		&quot;editor&quot;
	],
	&quot;Edornbush&quot;: [
		&quot;editor&quot;
	],
	&quot;Edriiic&quot;: [
		&quot;editor&quot;
	],
	&quot;Efex&quot;: [
		&quot;editor&quot;
	],
	&quot;Efex3&quot;: [
		&quot;editor&quot;
	],
	&quot;Effeietsanders&quot;: [
		&quot;editor&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;EggRoll97&quot;: [
		&quot;editor&quot;
	],
	&quot;Egil&quot;: [
		&quot;editor&quot;
	],
	&quot;Eihel&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Ejs-80&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ekaroleski&quot;: [
		&quot;editor&quot;
	],
	&quot;Elaurier&quot;: [
		&quot;editor&quot;
	],
	&quot;Elcobbola&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Electro&quot;: [
		&quot;editor&quot;
	],
	&quot;ElfSnail123&quot;: [
		&quot;editor&quot;
	],
	&quot;Eli bubo4ka&quot;: [
		&quot;editor&quot;
	],
	&quot;Eliarani&quot;: [
		&quot;editor&quot;
	],
	&quot;Elli&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ellywa&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Elmacenderesi&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Elton&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;
	],
	&quot;Emha&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;EmilymDaniel&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Empire3131&quot;: [
		&quot;editor&quot;
	],
	&quot;Encik Tekateki&quot;: [
		&quot;editor&quot;
	],
	&quot;Enzomartinelli&quot;: [
		&quot;editor&quot;
	],
	&quot;Eric Evers&quot;: [
		&quot;editor&quot;
	],
	&quot;Erigena&quot;: [
		&quot;editor&quot;
	],
	&quot;Erik Baas&quot;: [
		&quot;editor&quot;
	],
	&quot;ErinNik&quot;: [
		&quot;editor&quot;
	],
	&quot;Erinamukuta&quot;: [
		&quot;editor&quot;
	],
	&quot;ErrantX&quot;: [
		&quot;editor&quot;
	],
	&quot;EruannoVG&quot;: [
		&quot;editor&quot;
	],
	&quot;Espen180&quot;: [
		&quot;editor&quot;
	],
	&quot;Eta Carinae&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ethacke1&quot;: [
		&quot;editor&quot;
	],
	&quot;Eumolpo&quot;: [
		&quot;editor&quot;
	],
	&quot;Euphydryas&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Eurodyne&quot;: [
		&quot;editor&quot;
	],
	&quot;EvDawg93&quot;: [
		&quot;editor&quot;
	],
	&quot;EvanCarroll&quot;: [
		&quot;editor&quot;
	],
	&quot;Ewen&quot;: [
		&quot;editor&quot;
	],
	&quot;Exusiai&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ezarate&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Fabartus&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Faendalimas&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Fasten&quot;: [
		&quot;editor&quot;
	],
	&quot;Faster than Thunder&quot;: [
		&quot;editor&quot;
	],
	&quot;Fathoms Below&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Fcorthay&quot;: [
		&quot;editor&quot;
	],
	&quot;Fdena&quot;: [
		&quot;editor&quot;
	],
	&quot;Federhalter&quot;: [
		&quot;editor&quot;
	],
	&quot;Fehufanga&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Fekarp&quot;: [
		&quot;editor&quot;
	],
	&quot;Fephisto&quot;: [
		&quot;editor&quot;
	],
	&quot;Ferien&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Fernando2812l&quot;: [
		&quot;editor&quot;
	],
	&quot;Fernly&quot;: [
		&quot;editor&quot;
	],
	&quot;Ffion B Thompson&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Fimatic&quot;: [
		&quot;editor&quot;
	],
	&quot;FischX&quot;: [
		&quot;editor&quot;
	],
	&quot;Fishpi&quot;: [
		&quot;editor&quot;
	],
	&quot;Flattail&quot;: [
		&quot;editor&quot;
	],
	&quot;FlightTime&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Flolit&quot;: [
		&quot;editor&quot;
	],
	&quot;Fluffernutter&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;FlyingAce&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Fountain Pen&quot;: [
		&quot;editor&quot;
	],
	&quot;Fr33kman&quot;: [
		&quot;editor&quot;
	],
	&quot;FrancisFromGaspesie&quot;: [
		&quot;editor&quot;
	],
	&quot;Frantsch&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Fredericknortje&quot;: [
		&quot;editor&quot;
	],
	&quot;Fritzlein~enwikibooks&quot;: [
		&quot;editor&quot;
	],
	&quot;Frozen Wind&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;Ftaljaard&quot;: [
		&quot;editor&quot;
	],
	&quot;Ftiercel&quot;: [
		&quot;editor&quot;
	],
	&quot;Furrykef&quot;: [
		&quot;editor&quot;
	],
	&quot;GKFX&quot;: [
		&quot;editor&quot;
	],
	&quot;Galahad&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Gampe&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Ganímedes&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Gary Dorman Wiggins&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Garygaryj&quot;: [
		&quot;editor&quot;
	],
	&quot;Gat lombard&quot;: [
		&quot;editor&quot;
	],
	&quot;Gc211&quot;: [
		&quot;editor&quot;
	],
	&quot;Geagea&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Geekgirl&quot;: [
		&quot;editor&quot;
	],
	&quot;GemmaCampbell&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Geoff Plourde&quot;: [
		&quot;editor&quot;
	],
	&quot;Geofferybard&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;GerbenRienk&quot;: [
		&quot;editor&quot;
	],
	&quot;Gerges&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Germany Poul Ah&quot;: [
		&quot;editor&quot;
	],
	&quot;Gertbuschmann&quot;: [
		&quot;editor&quot;
	],
	&quot;Ggee0621&quot;: [
		&quot;editor&quot;
	],
	&quot;Gifnk dlm 2020&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Girdi&quot;: [
		&quot;editor&quot;
	],
	&quot;Glaisher&quot;: [
		&quot;editor&quot;
	],
	&quot;Glane23&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Gleb713&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Glich&quot;: [
		&quot;editor&quot;
	],
	&quot;Gllyons&quot;: [
		&quot;editor&quot;
	],
	&quot;Gmasterman&quot;: [
		&quot;editor&quot;
	],
	&quot;GoblinInventor&quot;: [
		&quot;editor&quot;
	],
	&quot;Godsy&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Good afternoon&quot;: [
		&quot;editor&quot;
	],
	&quot;GoreyCat&quot;: [
		&quot;editor&quot;
	],
	&quot;GorgeUbuasha&quot;: [
		&quot;editor&quot;
	],
	&quot;GorillaWarfare&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Gott wisst&quot;: [
		&quot;editor&quot;
	],
	&quot;Goulart&quot;: [
		&quot;editor&quot;
	],
	&quot;Gpkp&quot;: [
		&quot;editor&quot;
	],
	&quot;Gracebaysinger&quot;: [
		&quot;editor&quot;
	],
	&quot;Graeme E. Smith&quot;: [
		&quot;editor&quot;
	],
	&quot;Greatswrd&quot;: [
		&quot;editor&quot;
	],
	&quot;GreenC&quot;: [
		&quot;editor&quot;
	],
	&quot;Greenbreen&quot;: [
		&quot;editor&quot;
	],
	&quot;Greenman&quot;: [
		&quot;editor&quot;
	],
	&quot;GregXenon01&quot;: [
		&quot;editor&quot;
	],
	&quot;Gretski247&quot;: [
		&quot;editor&quot;
	],
	&quot;GreyCat&quot;: [
		&quot;editor&quot;
	],
	&quot;Grin&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Growl41&quot;: [
		&quot;editor&quot;
	],
	&quot;Guaka&quot;: [
		&quot;editor&quot;
	],
	&quot;Guanaco&quot;: [
		&quot;editor&quot;
	],
	&quot;GuillermoHazebrouck&quot;: [
		&quot;editor&quot;
	],
	&quot;Guus&quot;: [
		&quot;editor&quot;
	],
	&quot;Guy vandegrift&quot;: [
		&quot;editor&quot;
	],
	&quot;Guywan&quot;: [
		&quot;editor&quot;
	],
	&quot;Gzuufy&quot;: [
		&quot;editor&quot;
	],
	&quot;HJ Mitchell&quot;: [
		&quot;autoreview&quot;
	],
	&quot;HLand&quot;: [
		&quot;editor&quot;
	],
	&quot;HYanWong&quot;: [
		&quot;editor&quot;
	],
	&quot;Ha98574&quot;: [
		&quot;editor&quot;
	],
	&quot;Hagindaz&quot;: [
		&quot;editor&quot;
	],
	&quot;HakanIST&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;
	],
	&quot;Hamish&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Hanay&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Hannes Röst&quot;: [
		&quot;editor&quot;
	],
	&quot;Hans Adler&quot;: [
		&quot;editor&quot;
	],
	&quot;Haoreima&quot;: [
		&quot;editor&quot;
	],
	&quot;Happy-melon&quot;: [
		&quot;editor&quot;
	],
	&quot;Harry Wood&quot;: [
		&quot;editor&quot;
	],
	&quot;Harrybrowne1986&quot;: [
		&quot;editor&quot;
	],
	&quot;Harv4&quot;: [
		&quot;editor&quot;
	],
	&quot;Hasley&quot;: [
		&quot;editor&quot;
	],
	&quot;Hazard-SJ&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;He7d3r&quot;: [
		&quot;editor&quot;
	],
	&quot;HenkvD&quot;: [
		&quot;editor&quot;
	],
	&quot;Herbythyme&quot;: [
		&quot;editor&quot;
	],
	&quot;Hercule&quot;: [
		&quot;editor&quot;
	],
	&quot;Herman darman&quot;: [
		&quot;editor&quot;
	],
	&quot;HerrHartmuth&quot;: [
		&quot;editor&quot;
	],
	&quot;Hethrir&quot;: [
		&quot;editor&quot;
	],
	&quot;HgDeviasse&quot;: [
		&quot;editor&quot;
	],
	&quot;Hippias&quot;: [
		&quot;editor&quot;
	],
	&quot;Hliow&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Holder&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Holdoffhunger&quot;: [
		&quot;editor&quot;
	],
	&quot;Hoo man&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;
	],
	&quot;HouseBlaster&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Howard Beale&quot;: [
		&quot;editor&quot;
	],
	&quot;Hpon&quot;: [
		&quot;editor&quot;
	],
	&quot;Hrkalona&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Hskeet&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Htm&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Hugetim&quot;: [
		&quot;editor&quot;
	],
	&quot;Humaira Ali&quot;: [
		&quot;editor&quot;
	],
	&quot;Huntertur&quot;: [
		&quot;editor&quot;
	],
	&quot;Hydriz&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;IB Muazzam&quot;: [
		&quot;editor&quot;
	],
	&quot;Ibidthewriter&quot;: [
		&quot;editor&quot;
	],
	&quot;Ibrahim.ID&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Icetruck&quot;: [
		&quot;editor&quot;
	],
	&quot;Icodense&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Idavidmiller&quot;: [
		&quot;editor&quot;
	],
	&quot;Ideasman42&quot;: [
		&quot;editor&quot;
	],
	&quot;Igna&quot;: [
		&quot;editor&quot;
	],
	&quot;Ijon&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Illusional&quot;: [
		&quot;editor&quot;
	],
	&quot;Iluvatar&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Indiana&quot;: [
		&quot;editor&quot;
	],
	&quot;Inductiveload&quot;: [
		&quot;editor&quot;
	],
	&quot;Inertia6084&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Inferno986return&quot;: [
		&quot;editor&quot;
	],
	&quot;Infinite0694&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Ingolemo&quot;: [
		&quot;editor&quot;
	],
	&quot;Insignificantwrangler&quot;: [
		&quot;editor&quot;
	],
	&quot;Internoob&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;InverseHypercube&quot;: [
		&quot;editor&quot;
	],
	&quot;Isenhand&quot;: [
		&quot;editor&quot;
	],
	&quot;Ish ishwar&quot;: [
		&quot;editor&quot;
	],
	&quot;Iste Praetor&quot;: [
		&quot;editor&quot;
	],
	&quot;ItsNyoty&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Itsmeyash31&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Itswikisam&quot;: [
		&quot;editor&quot;
	],
	&quot;Itti&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ixfd64&quot;: [
		&quot;editor&quot;
	],
	&quot;J ansari&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;J.palacios.jean&quot;: [
		&quot;editor&quot;
	],
	&quot;J36miles&quot;: [
		&quot;editor&quot;
	],
	&quot;JBW&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;JCrue&quot;: [
		&quot;editor&quot;
	],
	&quot;JJ12880&quot;: [
		&quot;editor&quot;
	],
	&quot;JJMC89&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;JJPMaster&quot;: [
		&quot;sysop&quot;,
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;interface-admin&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;JJPMaster (test 1)&quot;: [
		&quot;autoreview&quot;
	],
	&quot;JJohnson&quot;: [
		&quot;editor&quot;
	],
	&quot;JJohnson1701&quot;: [
		&quot;editor&quot;
	],
	&quot;JPPINTO&quot;: [
		&quot;editor&quot;
	],
	&quot;Jack Frost&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;JackBot&quot;: [
		&quot;editor&quot;
	],
	&quot;JackPotte&quot;: [
		&quot;sysop&quot;,
		&quot;interface-admin&quot;
	],
	&quot;Jackhand1&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Jacob J. Walker&quot;: [
		&quot;editor&quot;
	],
	&quot;Jafeluv&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Jake Park&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Jakec&quot;: [
		&quot;editor&quot;
	],
	&quot;JamesCrook&quot;: [
		&quot;editor&quot;
	],
	&quot;JamesNZ&quot;: [
		&quot;editor&quot;
	],
	&quot;Jamesofur&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Jamesssss&quot;: [
		&quot;editor&quot;
	],
	&quot;Jamzze&quot;: [
		&quot;editor&quot;
	],
	&quot;Jan Myšák&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Jan.duggan&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Janbery&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Janpha&quot;: [
		&quot;editor&quot;
	],
	&quot;Janschejbal&quot;: [
		&quot;editor&quot;
	],
	&quot;Jason.Cozens&quot;: [
		&quot;editor&quot;
	],
	&quot;Jaspalkaler&quot;: [
		&quot;editor&quot;
	],
	&quot;Jasper Deng&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;JavaHurricane&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Javier Carro&quot;: [
		&quot;editor&quot;
	],
	&quot;JavierCantero&quot;: [
		&quot;editor&quot;
	],
	&quot;Jay Bolero&quot;: [
		&quot;editor&quot;
	],
	&quot;Jazzmanian&quot;: [
		&quot;editor&quot;
	],
	&quot;Jcb&quot;: [
		&quot;editor&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Jcwf&quot;: [
		&quot;editor&quot;
	],
	&quot;Jeff G.&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Jeff1138&quot;: [
		&quot;editor&quot;
	],
	&quot;Jellysandwich0&quot;: [
		&quot;editor&quot;
	],
	&quot;JenVan&quot;: [
		&quot;editor&quot;
	],
	&quot;JenniferPalacios&quot;: [
		&quot;editor&quot;
	],
	&quot;Jenniferjkidd&quot;: [
		&quot;editor&quot;
	],
	&quot;Jens Østergaard Petersen&quot;: [
		&quot;editor&quot;
	],
	&quot;JeremyMcCracken&quot;: [
		&quot;editor&quot;
	],
	&quot;Jeroenr&quot;: [
		&quot;editor&quot;
	],
	&quot;Jerome Charles Potts&quot;: [
		&quot;editor&quot;
	],
	&quot;Jerry vlntn&quot;: [
		&quot;editor&quot;
	],
	&quot;Jesdisciple&quot;: [
		&quot;editor&quot;
	],
	&quot;Jessephu&quot;: [
		&quot;editor&quot;
	],
	&quot;Jfmantis&quot;: [
		&quot;editor&quot;
	],
	&quot;Jianhui67&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Jianhui67 public&quot;: [
		&quot;editor&quot;
	],
	&quot;Jim Ashby&quot;: [
		&quot;autoreview&quot;
	],
	&quot;JimKillock&quot;: [
		&quot;editor&quot;
	],
	&quot;Jimbotyson&quot;: [
		&quot;editor&quot;
	],
	&quot;Jimmy Xu&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Jkauf007&quot;: [
		&quot;editor&quot;
	],
	&quot;Jmdeschamps&quot;: [
		&quot;uploader&quot;
	],
	&quot;Jnanaranjan sahu&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Jnewh001&quot;: [
		&quot;editor&quot;
	],
	&quot;Jobin RV&quot;: [
		&quot;editor&quot;
	],
	&quot;Joewiz&quot;: [
		&quot;editor&quot;
	],
	&quot;Johannes Bo&quot;: [
		&quot;editor&quot;
	],
	&quot;Johannnes89&quot;: [
		&quot;steward&quot;
	],
	&quot;John Cross&quot;: [
		&quot;editor&quot;
	],
	&quot;JohnMarcelo&quot;: [
		&quot;editor&quot;
	],
	&quot;Johnkn63&quot;: [
		&quot;editor&quot;
	],
	&quot;Johnwhelan&quot;: [
		&quot;editor&quot;
	],
	&quot;Jokes Free4Me&quot;: [
		&quot;editor&quot;
	],
	&quot;Jomegat&quot;: [
		&quot;editor&quot;
	],
	&quot;Jon Harald Søby&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Jon Kolbert&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Jonathan Webley&quot;: [
		&quot;editor&quot;
	],
	&quot;Jordan Brown&quot;: [
		&quot;editor&quot;
	],
	&quot;JorisvS&quot;: [
		&quot;editor&quot;
	],
	&quot;Josve05a&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Jrincayc&quot;: [
		&quot;editor&quot;
	],
	&quot;Jsnaree&quot;: [
		&quot;editor&quot;
	],
	&quot;Jtneill&quot;: [
		&quot;editor&quot;
	],
	&quot;JuethoBot&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Jugandi&quot;: [
		&quot;editor&quot;
	],
	&quot;Jules*&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Juliancolton&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Jumark27&quot;: [
		&quot;editor&quot;
	],
	&quot;JustTheFacts33&quot;: [
		&quot;editor&quot;
	],
	&quot;Justlettersandnumbers&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;K6ka&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Kadı&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Kai Burghardt&quot;: [
		&quot;editor&quot;
	],
	&quot;Kaltenmeyer&quot;: [
		&quot;editor&quot;
	],
	&quot;Kambai Akau&quot;: [
		&quot;editor&quot;
	],
	&quot;Kanjy&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Kapooht&quot;: [
		&quot;editor&quot;
	],
	&quot;Karl Wick&quot;: [
		&quot;editor&quot;
	],
	&quot;Karosent&quot;: [
		&quot;editor&quot;
	],
	&quot;Kashkhan&quot;: [
		&quot;editor&quot;
	],
	&quot;Kathryn Mary Nicholson&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Katiemgeorge&quot;: [
		&quot;editor&quot;
	],
	&quot;Katyauchter&quot;: [
		&quot;editor&quot;
	],
	&quot;Kaushlendratripathi&quot;: [
		&quot;editor&quot;
	],
	&quot;Kaw8yh&quot;: [
		&quot;editor&quot;
	],
	&quot;Kayau&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;Kellen&quot;: [
		&quot;editor&quot;
	],
	&quot;Kelti&quot;: [
		&quot;editor&quot;
	],
	&quot;Kiefer.Wolfowitz&quot;: [
		&quot;editor&quot;
	],
	&quot;Killarnee&quot;: [
		&quot;editor&quot;
	],
	&quot;King of Hearts&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Kingaustin07&quot;: [
		&quot;editor&quot;
	],
	&quot;Kingofnuthin&quot;: [
		&quot;editor&quot;
	],
	&quot;Kirito&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Kittycataclysm&quot;: [
		&quot;sysop&quot;
	],
	&quot;Kj cheetham&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Kkmurray&quot;: [
		&quot;editor&quot;
	],
	&quot;Kl-robertson&quot;: [
		&quot;editor&quot;
	],
	&quot;Klaas van Buiten&quot;: [
		&quot;editor&quot;
	],
	&quot;Knittedbees&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;Knoppson&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Koantum&quot;: [
		&quot;editor&quot;
	],
	&quot;Koavf&quot;: [
		&quot;sysop&quot;,
		&quot;global-rollbacker&quot;
	],
	&quot;Kodos&quot;: [
		&quot;editor&quot;
	],
	&quot;KonstantinaG07&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;
	],
	&quot;Kowey&quot;: [
		&quot;editor&quot;
	],
	&quot;KrakatoaKatie&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Krd&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Krdbot&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Kri&quot;: [
		&quot;editor&quot;
	],
	&quot;Krinkle&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Kropotkine 113&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Kruusamägi&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Ktucker&quot;: [
		&quot;editor&quot;
	],
	&quot;Kwamikagami&quot;: [
		&quot;editor&quot;
	],
	&quot;Kwhitefoot&quot;: [
		&quot;editor&quot;
	],
	&quot;Kylu&quot;: [
		&quot;editor&quot;
	],
	&quot;Kızıl&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;L10nM4st3r&quot;: [
		&quot;editor&quot;
	],
	&quot;LABoyd2&quot;: [
		&quot;editor&quot;
	],
	&quot;LR0725&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Ladislav&quot;: [
		&quot;editor&quot;
	],
	&quot;Ladsgroup&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ladybug62&quot;: [
		&quot;editor&quot;
	],
	&quot;Lagoset&quot;: [
		&quot;editor&quot;
	],
	&quot;Larsnooden&quot;: [
		&quot;editor&quot;
	],
	&quot;Laurianedani&quot;: [
		&quot;editor&quot;
	],
	&quot;Lcraw005&quot;: [
		&quot;editor&quot;
	],
	&quot;Ldo&quot;: [
		&quot;editor&quot;
	],
	&quot;Leaderboard&quot;: [
		&quot;sysop&quot;,
		&quot;global-renamer&quot;,
		&quot;interface-admin&quot;
	],
	&quot;Learnerktm&quot;: [
		&quot;editor&quot;
	],
	&quot;Lechatjaune&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Leighblackall&quot;: [
		&quot;editor&quot;
	],
	&quot;Lemonaka&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Lengel46&quot;: [
		&quot;editor&quot;
	],
	&quot;Lentokonefani&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;LeoChiukl&quot;: [
		&quot;editor&quot;
	],
	&quot;Leonard64&quot;: [
		&quot;uploader&quot;
	],
	&quot;Leonidlednev&quot;: [
		&quot;autoreview&quot;,
		&quot;global-rollbacker&quot;
	],
	&quot;Leovanderven&quot;: [
		&quot;editor&quot;
	],
	&quot;Lesless&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Leyo&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Lgriot&quot;: [
		&quot;editor&quot;
	],
	&quot;Liam987&quot;: [
		&quot;editor&quot;
	],
	&quot;Liao&quot;: [
		&quot;editor&quot;
	],
	&quot;Libperry&quot;: [
		&quot;editor&quot;
	],
	&quot;Limiza&quot;: [
		&quot;editor&quot;
	],
	&quot;Lionel Cristiano&quot;: [
		&quot;editor&quot;
	],
	&quot;Litlok&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Little Sunshine&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Llakew&quot;: [
		&quot;editor&quot;
	],
	&quot;LlamaAl&quot;: [
		&quot;editor&quot;
	],
	&quot;Lobsteroh&quot;: [
		&quot;editor&quot;
	],
	&quot;LodestarChariot2&quot;: [
		&quot;editor&quot;
	],
	&quot;Lofty abyss&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Logictheo&quot;: [
		&quot;editor&quot;
	],
	&quot;Lomita&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Londonjackbooks&quot;: [
		&quot;editor&quot;
	],
	&quot;Lovepeacejoy404&quot;: [
		&quot;editor&quot;
	],
	&quot;Lp0 on fire&quot;: [
		&quot;autoreview&quot;,
		&quot;global-rollbacker&quot;
	],
	&quot;Lubaochuan&quot;: [
		&quot;editor&quot;
	],
	&quot;Luckas Blade&quot;: [
		&quot;editor&quot;
	],
	&quot;Lucystewpid&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Ludovic Brenta&quot;: [
		&quot;editor&quot;
	],
	&quot;Ludovicocaldara&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Lukas²³&quot;: [
		&quot;editor&quot;
	],
	&quot;LukeCEL&quot;: [
		&quot;editor&quot;
	],
	&quot;Lvova&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Lwill031&quot;: [
		&quot;editor&quot;
	],
	&quot;M7&quot;: [
		&quot;steward&quot;
	],
	&quot;MARKELLOS&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;MBq&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;MF-Warburg&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;MGA73&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;MIacono&quot;: [
		&quot;editor&quot;
	],
	&quot;MNeuschaefer&quot;: [
		&quot;editor&quot;
	],
	&quot;MS Sakib&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Mabdul&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Madisonhen&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Magda.dagda&quot;: [
		&quot;editor&quot;
	],
	&quot;Magnus Manske&quot;: [
		&quot;editor&quot;
	],
	&quot;Mahagaja&quot;: [
		&quot;editor&quot;
	],
	&quot;MaikoM93&quot;: [
		&quot;editor&quot;
	],
	&quot;Maire&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Malarz pl&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Manchiu&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;MandoRachovitsa&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Mandy Hopkins&quot;: [
		&quot;editor&quot;
	],
	&quot;ManuelGR&quot;: [
		&quot;editor&quot;
	],
	&quot;MarcGarver&quot;: [
		&quot;sysop&quot;,
		&quot;checkuser&quot;,
		&quot;steward&quot;
	],
	&quot;Marco Klunder&quot;: [
		&quot;editor&quot;
	],
	&quot;MarcoAurelio&quot;: [
		&quot;editor&quot;
	],
	&quot;Marcus Cyron&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Mardus&quot;: [
		&quot;editor&quot;
	],
	&quot;MarkJFernandes&quot;: [
		&quot;editor&quot;
	],
	&quot;MarkTraceur&quot;: [
		&quot;editor&quot;
	],
	&quot;Markcwm&quot;: [
		&quot;editor&quot;
	],
	&quot;Markhobley&quot;: [
		&quot;editor&quot;
	],
	&quot;MarsRover&quot;: [
		&quot;editor&quot;
	],
	&quot;Marshman~enwikibooks&quot;: [
		&quot;editor&quot;
	],
	&quot;Martin Kraus&quot;: [
		&quot;editor&quot;
	],
	&quot;Martin Sauter&quot;: [
		&quot;editor&quot;
	],
	&quot;Martin Urbanec&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;MartinPoulter&quot;: [
		&quot;editor&quot;
	],
	&quot;Martinwguy2&quot;: [
		&quot;editor&quot;
	],
	&quot;MarygoldRules&quot;: [
		&quot;editor&quot;
	],
	&quot;Master tongue&quot;: [
		&quot;editor&quot;
	],
	&quot;Masti&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Math buff&quot;: [
		&quot;editor&quot;
	],
	&quot;MathXplore&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Mathildem16&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Mathmensch&quot;: [
		&quot;editor&quot;
	],
	&quot;Mathmensch-Smalledits&quot;: [
		&quot;editor&quot;
	],
	&quot;Mathmogeek&quot;: [
		&quot;editor&quot;
	],
	&quot;Maths314&quot;: [
		&quot;editor&quot;
	],
	&quot;Matiia&quot;: [
		&quot;editor&quot;
	],
	&quot;Matrix&quot;: [
		&quot;autoreview&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Matsievsky&quot;: [
		&quot;editor&quot;
	],
	&quot;Mattb112885&quot;: [
		&quot;editor&quot;
	],
	&quot;Mattbarton.exe&quot;: [
		&quot;editor&quot;
	],
	&quot;Matttest&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Max&quot;: [
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Max Milas&quot;: [
		&quot;editor&quot;
	],
	&quot;Maxim&quot;: [
		&quot;editor&quot;
	],
	&quot;Maximillion Pegasus&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Maxint2&quot;: [
		&quot;editor&quot;
	],
	&quot;Mazbel&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Mbch331&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Mbrickn&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;Mcdonnkm&quot;: [
		&quot;editor&quot;
	],
	&quot;Mcld&quot;: [
		&quot;editor&quot;
	],
	&quot;Mdkoch84&quot;: [
		&quot;editor&quot;
	],
	&quot;Mdmckenzie&quot;: [
		&quot;editor&quot;
	],
	&quot;MdsShakil&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Mdupont&quot;: [
		&quot;editor&quot;
	],
	&quot;Me Lendroz&quot;: [
		&quot;editor&quot;
	],
	&quot;Meanmicio&quot;: [
		&quot;editor&quot;
	],
	&quot;Mecanismo&quot;: [
		&quot;editor&quot;
	],
	&quot;MediaKyle&quot;: [
		&quot;editor&quot;
	],
	&quot;Meditation&quot;: [
		&quot;editor&quot;
	],
	&quot;Meev0&quot;: [
		&quot;editor&quot;
	],
	&quot;Mehman&quot;: [
		&quot;ombuds&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Melos&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;MemicznyJanusz&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Mendelivia~enwikibooks&quot;: [
		&quot;editor&quot;
	],
	&quot;Meniktah&quot;: [
		&quot;editor&quot;
	],
	&quot;Mercy&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;MerlLinkBot&quot;: [
		&quot;editor&quot;
	],
	&quot;Mfield&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Mh7kJ&quot;: [
		&quot;editor&quot;
	],
	&quot;Michael Romanov&quot;: [
		&quot;editor&quot;
	],
	&quot;MichaelFrey&quot;: [
		&quot;editor&quot;
	],
	&quot;Michaelbluett&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Mido&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;MihalOrela&quot;: [
		&quot;editor&quot;
	],
	&quot;MiiCii&quot;: [
		&quot;editor&quot;
	],
	&quot;Mike Hayes&quot;: [
		&quot;editor&quot;
	],
	&quot;Mike.lifeguard&quot;: [
		&quot;editor&quot;
	],
	&quot;Mild Bill Hiccup&quot;: [
		&quot;editor&quot;
	],
	&quot;Mill3315&quot;: [
		&quot;editor&quot;
	],
	&quot;Millbart&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Mimarx&quot;: [
		&quot;editor&quot;
	],
	&quot;Min1996&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Minorax&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;Mirinano&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Mithridates&quot;: [
		&quot;editor&quot;
	],
	&quot;Mjbt&quot;: [
		&quot;editor&quot;
	],
	&quot;Mjchael&quot;: [
		&quot;editor&quot;
	],
	&quot;Mjkaye&quot;: [
		&quot;editor&quot;
	],
	&quot;Mkline&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Mlipl001&quot;: [
		&quot;editor&quot;
	],
	&quot;Moby-Dick4000&quot;: [
		&quot;editor&quot;
	],
	&quot;Mohean&quot;: [
		&quot;editor&quot;
	],
	&quot;Money-lover-12345&quot;: [
		&quot;editor&quot;
	],
	&quot;Moonriddengirl&quot;: [
		&quot;autoreview&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Mortense&quot;: [
		&quot;editor&quot;
	],
	&quot;Mpfau&quot;: [
		&quot;editor&quot;
	],
	&quot;Mr. Stradivarius&quot;: [
		&quot;editor&quot;
	],
	&quot;MrAlanKoh&quot;: [
		&quot;editor&quot;
	],
	&quot;MrJaroslavik&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;ombuds&quot;
	],
	&quot;Mrajcok&quot;: [
		&quot;editor&quot;
	],
	&quot;Mrjulesd&quot;: [
		&quot;editor&quot;
	],
	&quot;Mrwojo&quot;: [
		&quot;editor&quot;
	],
	&quot;Mschrag&quot;: [
		&quot;editor&quot;
	],
	&quot;Msmithma&quot;: [
		&quot;editor&quot;
	],
	&quot;MtPenguinMonster&quot;: [
		&quot;editor&quot;
	],
	&quot;Mtarch11&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;Musical Inquisit&quot;: [
		&quot;editor&quot;
	],
	&quot;Mussklprozz&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Mvolz&quot;: [
		&quot;editor&quot;
	],
	&quot;Mwtoews&quot;: [
		&quot;editor&quot;
	],
	&quot;Mxn&quot;: [
		&quot;editor&quot;
	],
	&quot;Myklaw&quot;: [
		&quot;editor&quot;
	],
	&quot;Mykola7&quot;: [
		&quot;steward&quot;
	],
	&quot;Mys 721tx&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;NDG&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;Nadzik&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;NahidSultan&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Nangkhan Magar&quot;: [
		&quot;editor&quot;
	],
	&quot;Natuur12&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Nbarth&quot;: [
		&quot;editor&quot;
	],
	&quot;Nbro&quot;: [
		&quot;editor&quot;
	],
	&quot;Nehaoua&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Neils51&quot;: [
		&quot;editor&quot;
	],
	&quot;Nemoralis&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Neojacob&quot;: [
		&quot;editor&quot;
	],
	&quot;Neriah&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Nesbit&quot;: [
		&quot;editor&quot;
	],
	&quot;Newlisp&quot;: [
		&quot;editor&quot;
	],
	&quot;Nfgdayton&quot;: [
		&quot;editor&quot;
	],
	&quot;NguoiDungKhongDinhDanh&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;NhacNy2412&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Nick.anderegg&quot;: [
		&quot;editor&quot;
	],
	&quot;NickPenguin&quot;: [
		&quot;editor&quot;
	],
	&quot;NicoScribe&quot;: [
		&quot;editor&quot;
	],
	&quot;Nicole Sharp&quot;: [
		&quot;editor&quot;
	],
	&quot;Nieuwsgierige Gebruiker&quot;: [
		&quot;editor&quot;
	],
	&quot;Nigos&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Nihonjoe&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Nikai&quot;: [
		&quot;editor&quot;
	],
	&quot;Ninjastrikers&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;NipplesMeCool&quot;: [
		&quot;editor&quot;
	],
	&quot;Njardarlogar&quot;: [
		&quot;editor&quot;
	],
	&quot;Nobody60&quot;: [
		&quot;editor&quot;
	],
	&quot;Nolispanmo&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Nomstuff&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Nonenmac&quot;: [
		&quot;editor&quot;
	],
	&quot;Norton&quot;: [
		&quot;editor&quot;
	],
	&quot;Npettiaux&quot;: [
		&quot;editor&quot;
	],
	&quot;Nsaa&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Nthep&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;NuclearWarfare&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;OMSMike&quot;: [
		&quot;editor&quot;
	],
	&quot;Officer781&quot;: [
		&quot;editor&quot;
	],
	&quot;Oleander&quot;: [
		&quot;editor&quot;
	],
	&quot;Oliviacatherall&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Omphalographer&quot;: [
		&quot;editor&quot;
	],
	&quot;OnBeyondZebrax&quot;: [
		&quot;editor&quot;
	],
	&quot;Onsen&quot;: [
		&quot;editor&quot;
	],
	&quot;Ontzak&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Orderud&quot;: [
		&quot;editor&quot;
	],
	&quot;OrenBochman&quot;: [
		&quot;editor&quot;
	],
	&quot;Oshwah&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ottawahitech&quot;: [
		&quot;editor&quot;
	],
	&quot;Owain.davies&quot;: [
		&quot;editor&quot;
	],
	&quot;PAC&quot;: [
		&quot;editor&quot;
	],
	&quot;PAC2&quot;: [
		&quot;editor&quot;
	],
	&quot;PK 97&quot;: [
		&quot;editor&quot;
	],
	&quot;PNW Raven&quot;: [
		&quot;editor&quot;
	],
	&quot;Pac8612&quot;: [
		&quot;editor&quot;
	],
	&quot;Paloi Sciurala&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Panic2k4&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;Pascal Pignard&quot;: [
		&quot;editor&quot;
	],
	&quot;Pastbury&quot;: [
		&quot;editor&quot;
	],
	&quot;Pathfinders&quot;: [
		&quot;editor&quot;
	],
	&quot;Pathoschild&quot;: [
		&quot;editor&quot;
	],
	&quot;Patrik&quot;: [
		&quot;editor&quot;
	],
	&quot;PauSix&quot;: [
		&quot;editor&quot;
	],
	&quot;Paul James&quot;: [
		&quot;editor&quot;
	],
	&quot;Pavroo&quot;: [
		&quot;editor&quot;
	],
	&quot;PbakerODU&quot;: [
		&quot;editor&quot;
	],
	&quot;Pbrower2a&quot;: [
		&quot;editor&quot;
	],
	&quot;Pearts&quot;: [
		&quot;editor&quot;
	],
	&quot;Peeragogia&quot;: [
		&quot;editor&quot;
	],
	&quot;Peri Coleman&quot;: [
		&quot;editor&quot;
	],
	&quot;Perl~enwikibooks&quot;: [
		&quot;editor&quot;
	],
	&quot;Peter1180&quot;: [
		&quot;editor&quot;
	],
	&quot;PeterEasthope&quot;: [
		&quot;editor&quot;
	],
	&quot;Peyton09&quot;: [
		&quot;editor&quot;
	],
	&quot;Phan M. Nhat&quot;: [
		&quot;autoreview&quot;
	],
	&quot;PhilKnight&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Phoebe&quot;: [
		&quot;editor&quot;
	],
	&quot;Phosgram&quot;: [
		&quot;editor&quot;
	],
	&quot;Pi zero&quot;: [
		&quot;editor&quot;
	],
	&quot;PieWriter&quot;: [
		&quot;editor&quot;
	],
	&quot;Piotrus&quot;: [
		&quot;editor&quot;
	],
	&quot;Pithikos&quot;: [
		&quot;editor&quot;
	],
	&quot;Pittsburgh Poet&quot;: [
		&quot;editor&quot;
	],
	&quot;Pjpearce&quot;: [
		&quot;editor&quot;
	],
	&quot;Pkkao&quot;: [
		&quot;editor&quot;
	],
	&quot;Planotse&quot;: [
		&quot;editor&quot;
	],
	&quot;Platonides&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Pluke&quot;: [
		&quot;editor&quot;
	],
	&quot;PlyrStar93&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Pminh141&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Pmlineditor&quot;: [
		&quot;editor&quot;
	],
	&quot;Pmw57&quot;: [
		&quot;editor&quot;
	],
	&quot;Poetcsw&quot;: [
		&quot;editor&quot;
	],
	&quot;PoizonMyst&quot;: [
		&quot;editor&quot;
	],
	&quot;Pola 2607&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Polimerek&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Polluks&quot;: [
		&quot;editor&quot;
	],
	&quot;Pookiyama&quot;: [
		&quot;editor&quot;
	],
	&quot;Popski&quot;: [
		&quot;editor&quot;
	],
	&quot;Povigna&quot;: [
		&quot;editor&quot;
	],
	&quot;Ppolar bear&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Pppery&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Prahlad balaji&quot;: [
		&quot;editor&quot;
	],
	&quot;Pratyeka&quot;: [
		&quot;editor&quot;
	],
	&quot;Praxidicae&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;Primefac&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Prince Kassad~enwikibooks&quot;: [
		&quot;editor&quot;
	],
	&quot;Pronesto&quot;: [
		&quot;editor&quot;
	],
	&quot;Prototyperspective&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Psoup&quot;: [
		&quot;editor&quot;
	],
	&quot;Psr1909&quot;: [
		&quot;editor&quot;
	],
	&quot;PullUpYourSocks&quot;: [
		&quot;editor&quot;
	],
	&quot;PurpleBuffalo&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;PurplePieman&quot;: [
		&quot;editor&quot;
	],
	&quot;Purplebackpack89&quot;: [
		&quot;editor&quot;
	],
	&quot;Putukas01&quot;: [
		&quot;editor&quot;
	],
	&quot;Qenalcu&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Quebecguy&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;QueerEcofeminist&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;editor&quot;
	],
	&quot;Quinlan83&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Quintucket&quot;: [
		&quot;editor&quot;
	],
	&quot;Qwerty number1&quot;: [
		&quot;editor&quot;
	],
	&quot;Qwertyus&quot;: [
		&quot;editor&quot;
	],
	&quot;Qədir&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;R. Henrik Nilsson&quot;: [
		&quot;editor&quot;
	],
	&quot;RAdimer-WMF&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;RDBury&quot;: [
		&quot;editor&quot;
	],
	&quot;RJHall&quot;: [
		&quot;editor&quot;
	],
	&quot;Ra'ike&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Rachboots&quot;: [
		&quot;editor&quot;
	],
	&quot;Rachel&quot;: [
		&quot;editor&quot;
	],
	&quot;Rachmat04&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;RadiX&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Raffaela Kunz&quot;: [
		&quot;editor&quot;
	],
	&quot;Rahulkepapa&quot;: [
		&quot;editor&quot;
	],
	&quot;Ramac&quot;: [
		&quot;editor&quot;
	],
	&quot;Rambam rashi&quot;: [
		&quot;editor&quot;
	],
	&quot;Randykitty&quot;: [
		&quot;autoreview&quot;,
		&quot;global-rollbacker&quot;
	],
	&quot;RatónMístico176&quot;: [
		&quot;editor&quot;
	],
	&quot;Ravichandar84&quot;: [
		&quot;editor&quot;
	],
	&quot;Rawheatley&quot;: [
		&quot;editor&quot;
	],
	&quot;Ray Trygstad&quot;: [
		&quot;editor&quot;
	],
	&quot;RayeChellMahela&quot;: [
		&quot;editor&quot;
	],
	&quot;Raymond&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Razr Nation&quot;: [
		&quot;editor&quot;
	],
	&quot;Rchaswms01&quot;: [
		&quot;editor&quot;
	],
	&quot;Rcragun&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Readyokaygo&quot;: [
		&quot;editor&quot;
	],
	&quot;Recent Runes&quot;: [
		&quot;editor&quot;
	],
	&quot;Redlentil&quot;: [
		&quot;editor&quot;
	],
	&quot;Refcanimm&quot;: [
		&quot;editor&quot;
	],
	&quot;Regasterios&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Reinhard Kraasch&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;RenaissanceMan2144&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Renamed user 242094acfb1a5b2f08e9e78f2e021a40&quot;: [
		&quot;editor&quot;
	],
	&quot;Renamed user 5f91ca71739b07cfce8397eed758fe13&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Renamed user f26394dcb19bd7bdad78f0d752896653&quot;: [
		&quot;editor&quot;
	],
	&quot;Renvoy&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Reseletti&quot;: [
		&quot;editor&quot;
	],
	&quot;Retropunk&quot;: [
		&quot;editor&quot;
	],
	&quot;Reuben1508&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Revi C.&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;ombuds&quot;,
		&quot;editor&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Reyk&quot;: [
		&quot;editor&quot;
	],
	&quot;Rfc1394&quot;: [
		&quot;editor&quot;
	],
	&quot;Rgdboer&quot;: [
		&quot;editor&quot;
	],
	&quot;Rgreenone&quot;: [
		&quot;editor&quot;
	],
	&quot;Rhole2001&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Rich Farmbrough&quot;: [
		&quot;editor&quot;
	],
	&quot;Rickstambaugh&quot;: [
		&quot;editor&quot;
	],
	&quot;Riggwelter&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Risk&quot;: [
		&quot;editor&quot;
	],
	&quot;Risteall&quot;: [
		&quot;editor&quot;
	],
	&quot;Ritjesman&quot;: [
		&quot;editor&quot;
	],
	&quot;RoMancer&quot;: [
		&quot;editor&quot;
	],
	&quot;Robbiemorrison&quot;: [
		&quot;editor&quot;
	],
	&quot;Robert Huber~enwikibooks&quot;: [
		&quot;editor&quot;
	],
	&quot;Roberto Mura&quot;: [
		&quot;editor&quot;
	],
	&quot;Robertsky&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;RobinH&quot;: [
		&quot;editor&quot;
	],
	&quot;Rodasmith&quot;: [
		&quot;editor&quot;
	],
	&quot;Rodrigo&quot;: [
		&quot;editor&quot;
	],
	&quot;Rodrigo.Argenton&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Rogerborrell&quot;: [
		&quot;editor&quot;
	],
	&quot;Rogerdpack&quot;: [
		&quot;editor&quot;
	],
	&quot;RogueScholar&quot;: [
		&quot;editor&quot;
	],
	&quot;Romainbehar&quot;: [
		&quot;editor&quot;
	],
	&quot;RomaineBot&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;RonaldB&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Rosser1954&quot;: [
		&quot;editor&quot;
	],
	&quot;Rotlink&quot;: [
		&quot;editor&quot;
	],
	&quot;RoySmith&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Rozzychan&quot;: [
		&quot;editor&quot;
	],
	&quot;Rplano&quot;: [
		&quot;editor&quot;
	],
	&quot;Rreagan007&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Rrgreen&quot;: [
		&quot;editor&quot;
	],
	&quot;Rschen7754&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;RshieldsVA&quot;: [
		&quot;editor&quot;
	],
	&quot;Rsjaffe&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Rtaisis&quot;: [
		&quot;editor&quot;
	],
	&quot;Ruakh&quot;: [
		&quot;editor&quot;
	],
	&quot;Rudolpho~enwikibooks&quot;: [
		&quot;editor&quot;
	],
	&quot;Runfellow&quot;: [
		&quot;editor&quot;
	],
	&quot;Runner4lyfe&quot;: [
		&quot;editor&quot;
	],
	&quot;RunningBlind&quot;: [
		&quot;editor&quot;
	],
	&quot;Ruthven&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Ruud Koot&quot;: [
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;Rzuwig&quot;: [
		&quot;autoreview&quot;,
		&quot;global-rollbacker&quot;
	],
	&quot;S.Marchenko&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;S8321414&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;SB Johnny&quot;: [
		&quot;editor&quot;
	],
	&quot;SCP-2000&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;SHB2000&quot;: [
		&quot;sysop&quot;,
		&quot;steward&quot;
	],
	&quot;SPM&quot;: [
		&quot;editor&quot;
	],
	&quot;Sae1962&quot;: [
		&quot;editor&quot;
	],
	&quot;Safuan12616&quot;: [
		&quot;editor&quot;
	],
	&quot;SahniM&quot;: [
		&quot;editor&quot;
	],
	&quot;Sakretsu&quot;: [
		&quot;steward&quot;
	],
	&quot;Sakura emad&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Salil Kumar Mukherjee&quot;: [
		&quot;editor&quot;
	],
	&quot;Samat&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Sammy2012&quot;: [
		&quot;editor&quot;
	],
	&quot;Samuel.dellit&quot;: [
		&quot;editor&quot;
	],
	&quot;Samuele2002&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Samwilson&quot;: [
		&quot;editor&quot;
	],
	&quot;SanBonne&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Sandbergja&quot;: [
		&quot;editor&quot;
	],
	&quot;Sannita&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Sante Caserio~enwikibooks&quot;: [
		&quot;editor&quot;
	],
	&quot;SarahFatimaK&quot;: [
		&quot;editor&quot;
	],
	&quot;Sargoth&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Saroj&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Sascha Lill 95&quot;: [
		&quot;editor&quot;
	],
	&quot;Satdeep Gill&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Savh&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Sbb1413&quot;: [
		&quot;editor&quot;
	],
	&quot;Scention&quot;: [
		&quot;editor&quot;
	],
	&quot;Schniggendiller&quot;: [
		&quot;steward&quot;
	],
	&quot;SchreiberBike&quot;: [
		&quot;editor&quot;
	],
	&quot;Scott.beckman&quot;: [
		&quot;editor&quot;
	],
	&quot;Sebastian Wallroth&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Seewolf&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Sekidoki&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Selden&quot;: [
		&quot;editor&quot;
	],
	&quot;Sennecaster&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Serinap&quot;: [
		&quot;editor&quot;
	],
	&quot;Seth Miller&quot;: [
		&quot;editor&quot;
	],
	&quot;SevenSpheres&quot;: [
		&quot;editor&quot;
	],
	&quot;Sfan00 IMG&quot;: [
		&quot;editor&quot;
	],
	&quot;Sfoerster&quot;: [
		&quot;editor&quot;
	],
	&quot;Sgarrigan&quot;: [
		&quot;editor&quot;
	],
	&quot;Sgowal&quot;: [
		&quot;editor&quot;
	],
	&quot;Shaitand&quot;: [
		&quot;editor&quot;
	],
	&quot;ShakespeareFan00&quot;: [
		&quot;editor&quot;
	],
	&quot;SharingNotes&quot;: [
		&quot;editor&quot;
	],
	&quot;Shawntanchinyang&quot;: [
		&quot;editor&quot;
	],
	&quot;Shdwninja8&quot;: [
		&quot;editor&quot;
	],
	&quot;ShelleyAdams&quot;: [
		&quot;autoreview&quot;
	],
	&quot;ShifaYT&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Shii&quot;: [
		&quot;editor&quot;
	],
	&quot;Shira the Mogul&quot;: [
		&quot;editor&quot;
	],
	&quot;Shlomif&quot;: [
		&quot;editor&quot;
	],
	&quot;ShuBraque&quot;: [
		&quot;editor&quot;
	],
	&quot;Sidelight12&quot;: [
		&quot;editor&quot;
	],
	&quot;Sidorkin&quot;: [
		&quot;editor&quot;
	],
	&quot;Sidpatil&quot;: [
		&quot;editor&quot;
	],
	&quot;Siebengang&quot;: [
		&quot;editor&quot;
	],
	&quot;Sigma 7&quot;: [
		&quot;editor&quot;
	],
	&quot;Simon Peter Hughes&quot;: [
		&quot;editor&quot;
	],
	&quot;Sinus46&quot;: [
		&quot;editor&quot;
	],
	&quot;Sir Beluga&quot;: [
		&quot;editor&quot;
	],
	&quot;Sir Lestaty de Lioncourt&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;SixWingedSeraph&quot;: [
		&quot;editor&quot;
	],
	&quot;Sj&quot;: [
		&quot;editor&quot;
	],
	&quot;Sjc~enwikibooks&quot;: [
		&quot;editor&quot;
	],
	&quot;Sjlegg&quot;: [
		&quot;editor&quot;
	],
	&quot;Sjone101&quot;: [
		&quot;editor&quot;
	],
	&quot;Sjö&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Skymath&quot;: [
		&quot;editor&quot;
	],
	&quot;Slava Ukraini Heroyam Slava 123&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Slava Ukrajini Heroyam Slava&quot;: [
		&quot;editor&quot;
	],
	&quot;Sluffs&quot;: [
		&quot;editor&quot;
	],
	&quot;Smjg&quot;: [
		&quot;editor&quot;
	],
	&quot;SnappyDragonPennyroyal&quot;: [
		&quot;editor&quot;
	],
	&quot;SocialKnowledge&quot;: [
		&quot;editor&quot;
	],
	&quot;SoftwareEngineerMoose&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Sonia&quot;: [
		&quot;editor&quot;
	],
	&quot;Sophie Cheng&quot;: [
		&quot;editor&quot;
	],
	&quot;Sotiale&quot;: [
		&quot;steward&quot;
	],
	&quot;Soul windsurfer&quot;: [
		&quot;editor&quot;
	],
	&quot;SouthParkFan65&quot;: [
		&quot;editor&quot;
	],
	&quot;SoylentGreen&quot;: [
		&quot;editor&quot;
	],
	&quot;Spamduck&quot;: [
		&quot;editor&quot;
	],
	&quot;Spaynton&quot;: [
		&quot;editor&quot;
	],
	&quot;Spender2001&quot;: [
		&quot;editor&quot;
	],
	&quot;Speregrination&quot;: [
		&quot;editor&quot;
	],
	&quot;Spiderworm&quot;: [
		&quot;editor&quot;
	],
	&quot;Spoon!&quot;: [
		&quot;editor&quot;
	],
	&quot;Squasher&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Srhat&quot;: [
		&quot;editor&quot;
	],
	&quot;Stang&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Stanglavine&quot;: [
		&quot;editor&quot;
	],
	&quot;Steinsplitter&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;StephT0704&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Stepheng3&quot;: [
		&quot;editor&quot;
	],
	&quot;Stepro&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Steve M&quot;: [
		&quot;editor&quot;
	],
	&quot;Stilfehler&quot;: [
		&quot;editor&quot;
	],
	&quot;Stockywood&quot;: [
		&quot;editor&quot;
	],
	&quot;Storeye&quot;: [
		&quot;editor&quot;
	],
	&quot;Strainu&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Strange quark&quot;: [
		&quot;editor&quot;
	],
	&quot;Stryn&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Stïnger&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Suchenwi&quot;: [
		&quot;editor&quot;
	],
	&quot;Sumone10154&quot;: [
		&quot;editor&quot;
	],
	&quot;SunCreator&quot;: [
		&quot;editor&quot;
	],
	&quot;Sunny Cryolite&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Sunshineconnelly&quot;: [
		&quot;editor&quot;
	],
	&quot;SuperTyphoonNoru&quot;: [
		&quot;editor&quot;
	],
	&quot;Superbass&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Superpes15&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Supertoff&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Superzerocool&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;SupremeUmanu&quot;: [
		&quot;editor&quot;
	],
	&quot;Suruena&quot;: [
		&quot;editor&quot;
	],
	&quot;Sutambe&quot;: [
		&quot;editor&quot;
	],
	&quot;Sutton Publishing&quot;: [
		&quot;editor&quot;
	],
	&quot;Sué González Hauck&quot;: [
		&quot;editor&quot;
	],
	&quot;Svartava&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;SweetCanadianMullet&quot;: [
		&quot;editor&quot;
	],
	&quot;Swift&quot;: [
		&quot;editor&quot;
	],
	&quot;SyG&quot;: [
		&quot;editor&quot;
	],
	&quot;Sylvesterchukwu04&quot;: [
		&quot;editor&quot;
	],
	&quot;Sylvialim&quot;: [
		&quot;editor&quot;
	],
	&quot;Sylviaread&quot;: [
		&quot;editor&quot;
	],
	&quot;Synoman Barris&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;transwiki&quot;,
		&quot;editor&quot;
	],
	&quot;Syum90&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Syunsyunminmin&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;T.seppelt&quot;: [
		&quot;editor&quot;
	],
	&quot;TDang&quot;: [
		&quot;editor&quot;
	],
	&quot;TTWIDEE&quot;: [
		&quot;editor&quot;
	],
	&quot;Tahmid&quot;: [
		&quot;editor&quot;
	],
	&quot;Taketa&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Takipoint123&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;TakuyaMurata&quot;: [
		&quot;editor&quot;
	],
	&quot;Tamzin&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Tanbiruzzaman&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Tannertsf&quot;: [
		&quot;editor&quot;
	],
	&quot;Taoheedah&quot;: [
		&quot;editor&quot;
	],
	&quot;Tapsevarg&quot;: [
		&quot;editor&quot;
	],
	&quot;TaronjaSatsuma&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Taxman&quot;: [
		&quot;editor&quot;
	],
	&quot;Tchoř&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Tdkehoe&quot;: [
		&quot;editor&quot;
	],
	&quot;Tdvorak&quot;: [
		&quot;editor&quot;
	],
	&quot;Techman224&quot;: [
		&quot;editor&quot;
	],
	&quot;Tegel&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;
	],
	&quot;Teles&quot;: [
		&quot;ombuds&quot;,
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Tem5psu&quot;: [
		&quot;editor&quot;
	],
	&quot;Tempodivalse&quot;: [
		&quot;editor&quot;
	],
	&quot;TenWhile6&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;Tenshi Hinanawi&quot;: [
		&quot;autoreview&quot;,
		&quot;global-rollbacker&quot;
	],
	&quot;Terence Kearey&quot;: [
		&quot;editor&quot;
	],
	&quot;Ternarius&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Ternera&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;Tesleemah&quot;: [
		&quot;editor&quot;
	],
	&quot;Tevfik AKTUĞLU&quot;: [
		&quot;editor&quot;
	],
	&quot;Tgregtregretgtr&quot;: [
		&quot;editor&quot;
	],
	&quot;ThatBPengineer&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Thatonewikiguy&quot;: [
		&quot;editor&quot;
	],
	&quot;The Squirrel Conspiracy&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;The labs&quot;: [
		&quot;editor&quot;
	],
	&quot;TheGoodEndedHappily&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;ThePCKid&quot;: [
		&quot;editor&quot;
	],
	&quot;TheSandDoctor&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Theknightwho&quot;: [
		&quot;editor&quot;
	],
	&quot;Thenub314&quot;: [
		&quot;editor&quot;
	],
	&quot;Theo Hughes&quot;: [
		&quot;editor&quot;
	],
	&quot;Theornamentalist&quot;: [
		&quot;editor&quot;
	],
	&quot;Thereen&quot;: [
		&quot;editor&quot;
	],
	&quot;Thewinster&quot;: [
		&quot;editor&quot;
	],
	&quot;Thierry Dugnolle&quot;: [
		&quot;editor&quot;
	],
	&quot;Thinkglobalnow&quot;: [
		&quot;editor&quot;
	],
	&quot;Thirunavukkarasye-Raveendran&quot;: [
		&quot;editor&quot;
	],
	&quot;Thomas Simpson&quot;: [
		&quot;editor&quot;
	],
	&quot;Thomas.haslwanter&quot;: [
		&quot;editor&quot;
	],
	&quot;Thomas.lochmatter&quot;: [
		&quot;editor&quot;
	],
	&quot;Tibetologist&quot;: [
		&quot;editor&quot;
	],
	&quot;Tigerzeng&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Tiled&quot;: [
		&quot;editor&quot;
	],
	&quot;TimBorgNetzWerk&quot;: [
		&quot;editor&quot;
	],
	&quot;Timothy Gu&quot;: [
		&quot;editor&quot;
	],
	&quot;Timpo&quot;: [
		&quot;editor&quot;
	],
	&quot;Tiptoety&quot;: [
		&quot;editor&quot;
	],
	&quot;Tjyang&quot;: [
		&quot;editor&quot;
	],
	&quot;Tlustulimu&quot;: [
		&quot;editor&quot;
	],
	&quot;Tmvogel&quot;: [
		&quot;editor&quot;
	],
	&quot;Tom Morris&quot;: [
		&quot;editor&quot;
	],
	&quot;Tomato86&quot;: [
		&quot;editor&quot;
	],
	&quot;TommyG&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Tomt87&quot;: [
		&quot;editor&quot;
	],
	&quot;Tomybrz&quot;: [
		&quot;editor&quot;
	],
	&quot;Tonyvall&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Tp42&quot;: [
		&quot;editor&quot;
	],
	&quot;Tracklayingninja&quot;: [
		&quot;editor&quot;
	],
	&quot;Tradimus&quot;: [
		&quot;editor&quot;
	],
	&quot;Tropicalkitty&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;TrulyShruti&quot;: [
		&quot;editor&quot;
	],
	&quot;Ts12rAc&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Tsarina CatarinaToo&quot;: [
		&quot;autoreview&quot;
	],
	&quot;TunnelESON&quot;: [
		&quot;sysop&quot;
	],
	&quot;Turbojet&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Turkmen&quot;: [
		&quot;editor&quot;
	],
	&quot;TwoThirty&quot;: [
		&quot;editor&quot;
	],
	&quot;Tyoyafud&quot;: [
		&quot;editor&quot;
	],
	&quot;Túrelio&quot;: [
		&quot;autoreview&quot;
	],
	&quot;U$3rname008&quot;: [
		&quot;editor&quot;
	],
	&quot;USSR-Slav&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Uf.hun2201&quot;: [
		&quot;editor&quot;
	],
	&quot;Uncitoyen&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;Uncle G&quot;: [
		&quot;editor&quot;
	],
	&quot;Unixxx&quot;: [
		&quot;editor&quot;
	],
	&quot;User01938&quot;: [
		&quot;editor&quot;
	],
	&quot;Username222&quot;: [
		&quot;editor&quot;
	],
	&quot;Utcursch&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Uziel302&quot;: [
		&quot;editor&quot;
	],
	&quot;Uzume&quot;: [
		&quot;editor&quot;
	],
	&quot;V0lkanic&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;VIGNERON&quot;: [
		&quot;steward&quot;
	],
	&quot;Valery Starikov&quot;: [
		&quot;editor&quot;
	],
	&quot;Van der Hoorn&quot;: [
		&quot;editor&quot;
	],
	&quot;Varnent&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Vdolar&quot;: [
		&quot;autoreview&quot;
	],
	&quot;VectorVoyager&quot;: [
		&quot;editor&quot;
	],
	&quot;Venzz&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Verfassungsfreund&quot;: [
		&quot;editor&quot;
	],
	&quot;Veritas Sapientiae&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Vermont&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Victor Stefan Stoica&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Victor Trevor&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Victoria.sandeman&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Vincent Vega&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Vito Genovese&quot;: [
		&quot;editor&quot;
	],
	&quot;Vituzzu&quot;: [
		&quot;editor&quot;
	],
	&quot;Vladimir Solovjev&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Vogone&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Vossman&quot;: [
		&quot;editor&quot;
	],
	&quot;Vrinda&quot;: [
		&quot;editor&quot;
	],
	&quot;VulcanWikiEdit&quot;: [
		&quot;editor&quot;
	],
	&quot;Vwanweb&quot;: [
		&quot;editor&quot;
	],
	&quot;WOSlinker&quot;: [
		&quot;autoreview&quot;
	],
	&quot;Waihorace&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Waldyrious&quot;: [
		&quot;editor&quot;
	],
	&quot;WalshDay&quot;: [
		&quot;editor&quot;
	],
	&quot;Wargo&quot;: [
		&quot;editor&quot;
	],
	&quot;Wbjimmyd&quot;: [
		&quot;editor&quot;
	],
	&quot;Wcoole&quot;: [
		&quot;editor&quot;
	],
	&quot;WeelkyWikiReader&quot;: [
		&quot;editor&quot;
	],
	&quot;Wekeepwhatwekill&quot;: [
		&quot;autoreview&quot;
	],
	&quot;WereSpielChequers&quot;: [
		&quot;editor&quot;
	],
	&quot;What no2000&quot;: [
		&quot;editor&quot;
	],
	&quot;WhatamIdoing&quot;: [
		&quot;editor&quot;
	],
	&quot;WhitePhosphorus&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;
	],
	&quot;Whiteknight&quot;: [
		&quot;editor&quot;
	],
	&quot;Whoop whoop pull up&quot;: [
		&quot;editor&quot;
	],
	&quot;Whym&quot;: [
		&quot;editor&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Wiki13&quot;: [
		&quot;editor&quot;
	],
	&quot;WikiBayer&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;WikiFer&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Wikimi-dhiann&quot;: [
		&quot;editor&quot;
	],
	&quot;Wikiotics&quot;: [
		&quot;editor&quot;
	],
	&quot;Wikiwau&quot;: [
		&quot;autoreview&quot;,
		&quot;editor&quot;
	],
	&quot;WillNess&quot;: [
		&quot;editor&quot;
	],
	&quot;Willscrlt&quot;: [
		&quot;editor&quot;
	],
	&quot;Wim b&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-sysop&quot;,
		&quot;editor&quot;
	],
	&quot;Wisden&quot;: [
		&quot;editor&quot;
	],
	&quot;Withinfocus&quot;: [
		&quot;editor&quot;
	],
	&quot;Wj32&quot;: [
		&quot;editor&quot;
	],
	&quot;Wkee4ager&quot;: [
		&quot;editor&quot;
	],
	&quot;Wobbit&quot;: [
		&quot;editor&quot;
	],
	&quot;Wojciech Pędzich&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Wooze&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Wundermacht&quot;: [
		&quot;editor&quot;
	],
	&quot;Wutsje&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Ww2censor&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Wüstenspringmaus&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;XXBlackburnXx&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;
	],
	&quot;Xandradi&quot;: [
		&quot;editor&quot;
	],
	&quot;Xania&quot;: [
		&quot;sysop&quot;,
		&quot;checkuser&quot;
	],
	&quot;Xaosflux&quot;: [
		&quot;editor&quot;,
		&quot;steward&quot;
	],
	&quot;XenonX3&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;Xerol&quot;: [
		&quot;editor&quot;
	],
	&quot;Xeverything11&quot;: [
		&quot;editor&quot;,
		&quot;uploader&quot;
	],
	&quot;Xhungab&quot;: [
		&quot;editor&quot;
	],
	&quot;Xinkai Wu&quot;: [
		&quot;editor&quot;
	],
	&quot;Xixtas&quot;: [
		&quot;editor&quot;
	],
	&quot;Xqt&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Xxagile&quot;: [
		&quot;editor&quot;
	],
	&quot;Xypron&quot;: [
		&quot;editor&quot;
	],
	&quot;Xz64&quot;: [
		&quot;editor&quot;
	],
	&quot;Y-S.Ko&quot;: [
		&quot;editor&quot;
	],
	&quot;YMS&quot;: [
		&quot;editor&quot;
	],
	&quot;Yahya&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Yamla&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Yann&quot;: [
		&quot;editor&quot;
	],
	&quot;Yerpo&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Yikrazuul&quot;: [
		&quot;editor&quot;
	],
	&quot;Ymblanter&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Yndesai&quot;: [
		&quot;editor&quot;
	],
	&quot;Youssefsan&quot;: [
		&quot;editor&quot;
	],
	&quot;Ysangkok&quot;: [
		&quot;editor&quot;
	],
	&quot;Yvelik&quot;: [
		&quot;uploader&quot;
	],
	&quot;Yzmo&quot;: [
		&quot;editor&quot;
	],
	&quot;ZI Jony&quot;: [
		&quot;editor&quot;
	],
	&quot;Zabe&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Zafer&quot;: [
		&quot;ombuds&quot;
	],
	&quot;Zedshort&quot;: [
		&quot;editor&quot;
	],
	&quot;ZeroOne&quot;: [
		&quot;editor&quot;
	],
	&quot;Zetud&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;Ziv&quot;: [
		&quot;editor&quot;
	],
	&quot;Zoeannl&quot;: [
		&quot;editor&quot;
	],
	&quot;Zollerriia&quot;: [
		&quot;editor&quot;
	],
	&quot;Zoohouse&quot;: [
		&quot;editor&quot;
	],
	&quot;Zoot&quot;: [
		&quot;editor&quot;
	],
	&quot;Zsohl&quot;: [
		&quot;autoreview&quot;,
		&quot;editor&quot;
	],
	&quot;Zvsmith&quot;: [
		&quot;editor&quot;
	],
	&quot;Zweighaft&quot;: [
		&quot;editor&quot;
	],
	&quot;ZxxZxxZ&quot;: [
		&quot;editor&quot;
	],
	&quot;~riley&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;editor&quot;
	],
	&quot;Érico&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;İmmortalance&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;Виктор Пинчук&quot;: [
		&quot;editor&quot;
	],
	&quot;Воображение&quot;: [
		&quot;editor&quot;
	],
	&quot;Всевидящий&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;Д.Ильин&quot;: [
		&quot;editor&quot;
	],
	&quot;Л.П. Джепко&quot;: [
		&quot;editor&quot;
	],
	&quot;יהודה שמחה ולדמן&quot;: [
		&quot;editor&quot;
	],
	&quot;מקף&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	],
	&quot;د. فارس الجويلي&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;روتانا&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;علاء&quot;: [
		&quot;steward&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;فيصل&quot;: [
		&quot;global-renamer&quot;,
		&quot;vrt-permissions&quot;
	],
	&quot;सीमा1&quot;: [
		&quot;editor&quot;
	],
	&quot;タチコマ robot&quot;: [
		&quot;editor&quot;
	],
	&quot;ネイ&quot;: [
		&quot;global-renamer&quot;
	],
	&quot;一隻北極熊&quot;: [
		&quot;editor&quot;
	],
	&quot;人间百态&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;臺灣象象&quot;: [
		&quot;autoreview&quot;
	],
	&quot;范&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;青子守歌&quot;: [
		&quot;vrt-permissions&quot;
	],
	&quot;魔琴&quot;: [
		&quot;global-rollbacker&quot;
	],
	&quot;ꠢꠣꠍꠘ ꠞꠣꠎꠣ&quot;: [
		&quot;editor&quot;
	],
	&quot;기나ㅏㄴ&quot;: [
		&quot;global-rollbacker&quot;,
		&quot;global-renamer&quot;
	]
}</text>
      <sha1>eplf7a8mnfwvjpp7hcq87fanlokv7bz</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Lemonaka</title>
    <ns>3</ns>
    <id>471898</id>
    <revision>
      <id>4669030</id>
      <parentid>4467512</parentid>
      <timestamp>2026-09-05T23:26:40Z</timestamp>
      <contributor>
        <username>Jonhson3029</username>
        <id>3625272</id>
      </contributor>
      <comment>/* Hello! */ new section</comment>
      <origin>4669030</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4579" sha1="lju6tj0u8kq9yx4j59gwmf1f2m9a3tq" xml:space="preserve">{{Talk header}}

== Welcome ==
&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Lemonaka!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;

&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;

&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;

&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;
&lt;sup&gt;&amp;#8212; [[User:L10nM4st3r|&lt;span style=&quot;color:#c71300&quot;&gt;L10nM4st3r&lt;/span&gt;]]&lt;/sup&gt; / &lt;sub&gt;[[User talk:L10nM4st3r|&lt;span style=&quot;color:#ce3f00&quot;&gt;'''ROAR''' at me!&lt;/span&gt;]]&lt;/sub&gt; 15:38, 15 January 2025 (UTC)

== Hello! ==

Hello! [[User:Jonhson3029|Jonhson3029]] ([[User talk:Jonhson3029|discuss]] • [[Special:Contributions/Jonhson3029|contribs]]) 23:26, 5 September 2026 (UTC)</text>
      <sha1>lju6tj0u8kq9yx4j59gwmf1f2m9a3tq</sha1>
    </revision>
    <revision>
      <id>4669032</id>
      <parentid>4669030</parentid>
      <timestamp>2026-09-05T23:53:09Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <minor />
      <comment>[[WB:REVERT|Reverted]] edit by [[Special:Contributions/Jonhson3029|Jonhson3029]] ([[User talk:Jonhson3029|talk]]) to last version by L10nM4st3r</comment>
      <origin>4467512</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4407" sha1="2waronj0mft3910wkng5l24r3e0wim8" xml:space="preserve">{{Talk header}}

== Welcome ==
&lt;div style=&quot;text-align:center; font-size:110%; font-weight:bold;&quot;&gt;[[Wikibooks:Welcome|Welcome]] to Wikibooks, Lemonaka!&lt;/div&gt;
&lt;!-- FIRST COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;
&lt;div style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;&quot;&gt;
&lt;div style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''&lt;/div&gt;
&lt;div style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
'''Wikibooks is for [[WB:AGF|collaborative]] development of free&amp;nbsp;[[WB:WIW|textbooks]].'''

You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]].

If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started.
&lt;/div&gt;
&lt;/div&gt;

&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information.
* You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]].
* Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files.
&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;!-- SECOND COLUMN --&gt;
&lt;div style=&quot;width:49.5%; float:left; margin:0em; padding:0em;&quot;&gt;

&lt;div class=&quot;collapsible&quot; style=&quot;margin:0.2em; border:1px solid #14304f; background-color:#f4eed7; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* You can [[WB:REVERT|restore]] a previously saved version.
* Pages should follow the [[WB:NP|&lt;code&gt;'''Book Title/Chapter Title'''&lt;/code&gt;]] naming convention.
* Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]).
* To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page.
* Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page.
&lt;/div&gt;
&lt;/div&gt;

&lt;div class=&quot;collapsible selected&quot; style=&quot;margin:0.2em; border:1px solid #15304f; background-color:#f4eed7; text-align:left;&quot;&gt;
&lt;div class=&quot;title&quot; style=&quot;border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;&quot;&gt;[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''&lt;/div&gt;
&lt;div class=&quot;NavContent&quot; style=&quot;padding:0.4em 1em 0.3em 1em;&quot;&gt;
* Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving.
* Sign your name on [[WB:TALK|discussion pages]] by typing &amp;#126;&amp;#126;&amp;#126;&amp;#126;
* User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''!
&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;div style=&quot;clear:both; padding-right:1em; text-align:right; font-size:smaller&quot;&gt;(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)&lt;/div&gt;
&lt;div style=&quot;clear:both;&quot;&gt; &lt;/div&gt;
&lt;sup&gt;&amp;#8212; [[User:L10nM4st3r|&lt;span style=&quot;color:#c71300&quot;&gt;L10nM4st3r&lt;/span&gt;]]&lt;/sup&gt; / &lt;sub&gt;[[User talk:L10nM4st3r|&lt;span style=&quot;color:#ce3f00&quot;&gt;'''ROAR''' at me!&lt;/span&gt;]]&lt;/sub&gt; 15:38, 15 January 2025 (UTC)</text>
      <sha1>2waronj0mft3910wkng5l24r3e0wim8</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch</title>
    <ns>0</ns>
    <id>481710</id>
    <revision>
      <id>4669033</id>
      <parentid>4660283</parentid>
      <timestamp>2026-09-06T00:07:57Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>/* Unit 1: Basic Skills */ I have thoroughly neglected the culinary side of this, but found a recipe that works perfectly.</comment>
      <origin>4669033</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="35840" sha1="d2bp0f9fgi6vrvb4zc363m9jv6272aq" xml:space="preserve">__notoc__

Welcome to the Wikibook for Literary Chinese (Known as 漢文 &quot;Han Language&quot; in East Asia or 文言 &quot;Literary Language&quot; in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. 

This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This  text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. However, as Zhou-Qin era texts served as the main body from which individuals learned, they are employed here as and when they are considered necessary or otherwise useful. It does so through a &quot;buffet&quot; approach, showering you, the reader, with an ocean of texts of myriad genre. 

==Table of Contents==

=== Front matter ===

* [[/Introduction/]]
* [[/Appendices/]]

=== Useful resources ===
These are quick grab-bags that can be useful for vocabulary-building. 
* [[/Antonym List/]] &lt;!--- 文/武，大/小，厚/薄，橫/縱...---&gt;
* [[/Collocation Groups/]] &lt;!--- e.g. 四象，三靈…… ---&gt;
* [[/Pronoun Table/]]
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] &lt;!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms]
&lt;!--- this will be translated eventually, but right now it's bad to just leave this here. ---&gt;

=== Useful primers ===
Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. 
* [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. 
* 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. 
** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. 
* 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. 
* 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. 
* 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece.

===Unit 0: The Han script===
This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. 

By the end of this unit, students will:
* Recognise around 50 characters.
* Understand how characters are composed and how this gives them meaning.
* Have a basic idea of how to handwrite and/or type characters using the Cangjie Input Method.
* Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of &quot;is&quot;, 有...)

Lessons:
# [[/An Introduction to the Han Script/]]
# [[/People, Big and Small/]]
# [[/How do we write Chinese?/]]
# [[/What are Chinese characters, anyway?/]]
# [[/The Sun, the Moon, and the Five Elements/]]
# [[/Getting Familiar with Body Parts/]]
# [[/Using Numbers and Using Weapons/]] &lt;!--- 竹戈十大中一弓廿卜---&gt;
# [[/Tilling the Fields with 有/]] &lt;!--- 山田 ---&gt;
# [[/How Characters are Made/|How Characters are Made with Kiyohara no Sanemoto]] 
# [[/Cangjie Created Characters/]] &lt;!--- Get people to use Cangjie ---&gt;
# [[/The Kangxi Radical System/]] &lt;!--- Introduce some monoradical texts to train recognition. ---&gt;

===Unit 1: Basic Skills===
This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. 

Before starting this unit, students should:
* Recognise around ~30 characters. 
* Can use Cangjie input. 
* Have given Unit 0 a cursory glance. 
&lt;br&gt;
By the end of this unit, students will:
* Recognise around ~100 characters. 
* Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date.
* Intuit the basic topic -&gt; comment idea behind Literary Chinese. &quot;This, it is...&quot; 
* Understand basic function words such as 也, 而, 有, and 謂.

Lessons:
# [[/The All-Purpose 也/]]
# [[/An Introduction to Chinese Numbers/]] &lt;!--- It is hard to find authentic materials for this ---&gt;
# [[/One, Two, Left, and Right with Gongsun Long/]]
&lt;!---
曰：「二有一乎？」

曰：「二無一。」

曰：「二有右乎？」

曰：「二無右。」

曰：「二有左乎？」

曰：「二無左。」

曰：「右可謂二乎？」

曰：「不可。」

曰：「左可謂二乎？」

曰：「不可。」

曰：「左與右可謂二乎？」

曰：「可。」
---&gt;
# [[/The Heavenly Stems/]] &lt;!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---&gt;
# [[/Tell the Time with Earthly Branches/]] &lt;!--- Introduce verbs and timekeeping ---&gt;
# [[/Lunar Dates with the Spring and Autumn Annals/]]
&lt;!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---&gt;
# [[/Skimming for Major Events in Historical Annals/]] 
&lt;!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. 

E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. 
https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701

Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! 
---&gt;
# [[/Dinner with the Daimyo/]]
&lt;!-- 
侍宴·大友皇子
皇明光日月，帝徳載天地。
三才併秦昌，万国表臣義。
--&gt; 
# [[/In Discourse with Jibong/]]
&lt;!--
芝峰類說 
倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。
--&gt;
# [[/How do we Write Height and Weight?/]] &lt;!--- Hilarious oversight ---&gt;
# [[/Eating like a Zhou Aristocrat/]] 
# [[/Shinto FAQ with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E7%9C%9E%E9%81%93%E5%95%8F%E5%B0%8D 眞道問對 本田親徳 really good way of operationalising 乎 and much of the early grammar. 

問 天帝無始無終乎。
對 天帝無始無終也。
旣以無始無終之力
與無始無終之體
造無始無終之萬物。
其功亦無始無終也。

問 天地大原在道乎。
對 天地大原實在道。
鬼神依道而立。
人民依道而活。
萬物依道而息。

This is great! ---&gt;

&lt;!---
Some cool stuff I saw someone studying from
https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98#
https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98

Could be used for period focus
---&gt;

===Unit 2: An Overview of Sinitic Poetry===
This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. 

After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole!

By the end of this Unit, students will:
* Recognise around 120 more characters.
* Be able to explain how Sinitic Poetry rhymes and the themes it contains.
* Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts.
* Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage.
* (Chinese speakers) Be able to differentiate 于 and 於, and understand the &quot;interest(ed) in&quot; meaning of 好 in most circumstances.
&lt;!---
Summary of the above part about 于 and 於 for other editors:
于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their &quot;merging&quot; through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000);
* 于 - This can mean &quot;to go&quot; or &quot;to/at&quot;. 黃鳥于飛 &quot;The yellow birds go flying&quot;. Must be post-verbal. It can also appear in 至于.
* 於 - This is an all-purpose locative preposition - from &quot;on/at/in&quot; to &quot;from&quot; or even &quot;than&quot; (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏).
---&gt;

Lessons:
# [[/Across the Rivers with Emperor Puliuru Guang/]] &lt;!--- Illustrate ping-ze ---&gt;
# [[/To Study the Odes/]] 
# [[/A Detour into Orthodox Ping-Ze/]] 
&lt;!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---&gt;
# [[/The Restraint of Du Fu/]] 
# [[/The Longing of Li Bai/]] 
# [[/The Environment with Bukha Timur/]]
# [[/Pillow Talk with Guan Yunshi/]]
&lt;!---
紅繡鞋·貫雲石
挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！

Uyghur author!
---&gt;
# [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]]
&lt;!-- 元火·吳真流
木中元有火，元火復還生。
若為木無火，鉆燧何有萌。--&gt;
&lt;!-- 杜鵑·大成聖安
夢覚孤床静
杜鵑帯雨飛
一声来近枕
何者不沾衣
--&gt;
# [[/Odes with Mō Taiei and Zheng Chengxun/]]
&lt;!-- 詠松·毛泰永
植體宜千仞，垂陰動百尋。
李膺真烈烈，和嶠自森森。
桃李何堪較，雪霜安得侵。
萬年身不老，種子又成林。
AKA Inoha Seiki 伊野波 盛紀 --&gt;
&lt;!-- 詠班蘭·鄭成勛
南國多芳草，班蘭最有名。
深根將綠茁，長葉亦叢生。
取味迎賓合，入厨任水烹。
可憐經一用，擲棄不留情。

鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --&gt;
# [[/A Golden Cup and the Fall of a Dynasty with Yan Fu/]] 
# [[/On a Journey with Sadula/]]
&lt;!---
No lesson entry:
朝中措·襄陽古道灞陵橋
襄陽古道灞陵橋，詩興與秋高。
千古風流人物，一時多少雄豪。

霜清玉塞，雲飛隴首，風落江皋。
夢到鳳凰台上，山圍故國周遭。

北郊晚步
陂水荷凋晚，茅檐燕去涼。
遠林明落景，平麓淡秋光。
群牧歸村巷，孤禽立野航。
自諳閑散樂，園圃意尤長。

Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later.
---&gt;

===Unit 3: Confucianism and the World===
This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states!

By the end of this unit, students should be able to:
* Recognise around 200+ characters.
* Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably.
* Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. 
** 於 and 于 should be distinguishable.
* Survive a text of at least 250 characters and read for gist.

Lessons:
# [[/A Brief Overview of Confucianism/]] 
# [[/Teaching the Annals in Qi/]] &lt;!-- Gongyang Gao's commentary --&gt;
# [[/Is a White Horse a Horse?/]]&lt;!-- Teach negation with 非 in 公孙龍子 and compare with 不 --&gt;
# [[/The Three Character Classic/]]
# [[/Expressing Filial Conduct with Confucius and Hara Saihin/]]
&lt;!--
次韻杏坪先生
父執有君孤不孤
相依遍接搢紳徒
区区自抱地方寸
杳杳重遊天一隅
羇雁飛鳴迷汝國
家人思夢入江都
如教志業青年遂
世上寧無逐臭夫
--&gt;
# [[/Confucianism and the Environment with Sai On/]]&lt;!-- 木假山記 --&gt;
# [[/In Debate with Mencius/]]

===Unit 4: Women's Writing===
In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here!
# [[/An Unmarried Life with Heo Nansŏrhŏn/]]
&lt;!---
貧女吟 
豈是乏容色。工鍼復工織。
少小長寒門。良媒不相識。

夜久織未休。戛戛鳴寒機。
機中一匹練。終作阿誰衣。

手把金翦刀。夜寒十指直。
爲人作嫁衣。年年還獨宿。
---&gt;
# [[/Responding to Lord Trần with Hồ Xuân Hương/]]
&lt;!---
Responding to 陳光靜 Trần Quang Tĩnh

《和陳侯》
愧無才調使人驚，十載風塵貫耳鈴。
已是臨枰知敵手，莫須敲月苦殫精。
為輪為彈隨遭遇，誰鳳誰鶯任賦生。
造物於人何苟惜，明珠休向暗中呈。

莫須 is an important structure to teach here.
---&gt;
# [[/Gaze into the Autumn Night with Taisei Shōan/]]
&lt;!---
秋夜偶成·大成聖安
長天浮爽気，月色興無窮
群犬吠山径，百蟲啼野風
悲秋秋夜永，感古古今同
自是孤窓下，凄然万慮空
---&gt;
# [[/Visiting a Temple with Yu Xuanji/]]
&lt;!---
遊崇真觀南樓覩新及第題名處
雲峰滿目放春晴，歷歷銀鈎指下生。
自恨羅衣掩詩句，擧頭空羨榜中名。
---&gt;
# [[/Remonstrance with Dasese/]]
&lt;!---
https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C
諷諫歌·大瑟瑟
勿嗟塞上兮暗紅塵。
勿傷多難兮畏夷人。
不如塞奸邪之路兮選取賢臣。
直須臥薪嚐膽兮激壯士之捐身。
可以朝清漠北兮夕枕燕雲。

Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. 
---&gt;
# [[/The Love Songs of the Odes/]]
&lt;!---
褰裳
子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！
子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！

柏舟
彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。
汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。

行露
厭浥行露，豈不夙夜，謂行多露。
誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。
誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。
---&gt;
# [[/Rules for Women with Ban Zhao/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---&gt;
# [[/The Tragedy of Cai Wenji/]]
&lt;!---
悲憤詩
〔兩漢〕蔡文姬
漢季失權柄，董卓亂天常。
志欲圖篡弒，先害諸賢良。
逼迫遷舊邦，擁主以自強。
海內興義師，欲共討不祥。
卓眾來東下，金甲耀日光。
平土人脆弱，來兵皆胡羌。
獵野圍城邑，所向悉破亡。
斬截無孑遺，屍骸相撐拒。
馬邊懸男頭，馬後載婦女。
長驅西入關，迥路險且阻。
還顧邈冥冥，肝脾為爛腐。
所略有萬計，不得令屯聚。
或有骨肉俱，欲言不敢語。
失意幾微間，輒言斃降虜。
要當以亭刃，我曹不活汝。
豈復惜性命，不堪其詈罵。
或便加棰杖，毒痛參並下。
旦則號泣行，夜則悲吟坐。
欲死不能得，欲生無一可。
彼蒼者何辜，乃遭此厄禍。
邊荒與華異，人俗少義理。
處所多霜雪，胡風春夏起。
翩翩吹我衣，肅肅入我耳。
感時念父母，哀嘆無窮已。
有客從外來，聞之常歡喜。
迎問其消息，輒復非鄉里。
邂逅徼時願，骨肉來迎己。
己得自解免，當復棄兒子。
天屬綴人心，念別無會期。
存亡永乖隔，不忍與之辭。
兒前抱我頸，問母欲何之。
人言母當去，豈復有還時。
阿母常仁惻，今何更不慈。
我尚未成人，奈何不顧思。
見此崩五內，恍惚生狂痴。
號泣手撫摩，當發復回疑。
兼有同時輩，相送告離別。
慕我獨得歸，哀叫聲摧裂。
馬為立踟躕，車為不轉轍。
觀者皆噓唏，行路亦嗚咽。
去去割情戀，遄征日遐邁。
悠悠三千里，何時復交會。
念我出腹子，匈臆為摧敗。
既至家人盡，又復無中外。
城廓為山林，庭宇生荊艾。
白骨不知誰，縱橫莫覆蓋。
出門無人聲，豺狼號且吠。
煢煢對孤景，怛吒糜肝肺。
登高遠眺望，魂神忽飛逝。
奄若壽命盡，旁人相寬大。
為復強視息，雖生何聊賴。
託命於新人，竭心自勖勵。
流離成鄙賤，常恐復捐廢。
人生幾何時，懷憂終年歲。
---&gt;

===Unit 5: Myths and Legends of East Asia===
&lt;!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---&gt;
# [[/Exploring the World of Mountains and Seas/]]&lt;!-- Structure: 出焉 --&gt;
# [[/Oh, the Qilin!/]] &lt;!--- Even here, the odes can be studied! ---&gt;
# [[/The Poison of Zhen/]] &lt;!--- referenced a lot in histories ---&gt;
# [[/Ultimate Justice with Xiezhi/]] &lt;!--- the yellow emperor met one, gao yao also used one ---&gt;
# [[/The Virtue of the Fenghuang/]] &lt;!--- shanhaijing has a great line on this ---&gt;
# [[/The Entrapment of Hua Po/]] 
# [[/Nüwa Created the World/]]

===Unit 6: Nation Focus - Japan===
# [[/The Inariyama Sword/]] 
&lt;!--- short and sweet! ---&gt;
# [[/Entering Japan with Takeda Shingen/]]
# [[/The Oldest Inscription in Japan/]] 
&lt;!--- 宇治橋断碑 ---&gt; 
# [[/The End of a Rebellion/]] 
# [[/Shinto Teachings with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---&gt;  
# [[/The Diary of Fujiwara no Teika/]] &lt;!--- 明月記 ---&gt;
# [[/Reading the History of Japan with Prince Toneri/]] &lt;!--- 日本書記, etc. ---&gt; 
# [[/A Biographical Painting of Toyotomi Hideyoshi/]] &lt;!--- This is on Fanya Hanwen Corpus ---&gt;
&lt;!--- # [[/Occupying Taiwan/]] ---&gt;
&lt;!--- I have some colonial literature on me that can be used here. ---&gt;

===Unit 7: Nation Focus - Korea===
# [[/Feigned Surrender with Ŭlchi Mundŏk/]] &lt;!--- 乙支文德漢詩 ---&gt;
# [[/A fu with Yi Kyubo/]]
# [[/An Elegy to the Empress with Choe Ja/]]
&lt;!---
Choe Ja
元德大后輓詞·崔滋（최자）
乾極曾客配,坤儀正體元。
枕前朝聖主,帳底見曾孫。
陰慘俄沉月,屋悲便沒軒。
三韓千古淚,七十九年恩。
---&gt;
# [[/Language Reform with Sejong the Great/]]
&lt;!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---&gt;
# [[/Fall Off Your Horse!/]] &lt;!--- a famous record from 朝鮮王朝實錄 ---&gt;
# [[/The Diary of Yi Sun-Sin/]] &lt;!--- 亂中日記 ---&gt;
# [[/Tales from Mount Kumo/]] &lt;!--- 金鰲新話 ---&gt;
# [[/Pak Chiwŏn Tours the Qing/]] &lt;!--- 熱河日記 ---&gt;
# [[/Korea's Three Kingdoms/]] &lt;!--- 三國史記 for sure! ---&gt;
# [[/Hwang Yun-seok's Essays/]] &lt;!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---&gt;

===Unit 8: Christian Literature===
# [[/A Different Three Character Classic with Hong Xiuquan/]]
# [[/Friar Juan Cobo's Veritable Record/]] 
&lt;!--- 
One of few texts from the Philippines that I have ever found!
https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 
---&gt;
# [[/The Delegate's Edition/]]
# [[/Nestorian Steles during the Tang/]] 
&lt;!--- 大秦景教宣元至本經經幢 and 景教碑 ---&gt;
# [[/Hong Xiuquan's Bible/]]
&lt;!--- https://bible.fhl.net/ob/nob.html?book=407 ---&gt;
&lt;!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---&gt;

===Unit 9: An Introduction to Daoism===
&lt;!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---&gt;
# [[/Laozi Explains the Dao/]]
# [[/Qingtan with Xie Daoyun/]]
# [[/The Doubting Neighbour/]] 
# [[/Kuafu Chases the Sun/]] 
# [[/The Frog in a Well/]] 
# [[/Wu wei with King Hui of Liang/]]
# [[/The Old Man that Moves the Mountains/]]
# [[/Master Zhuang Dreams of Butterflies/]]
# [[/Master Incapable and the Poisonous Bird/]]
# [[/Transmitting the Dao with Yelü Chucai/]] &lt;!---耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. https://zh.wikisource.org/wiki/%E7%8E%84%E9%A2%A8%E6%85%B6%E6%9C%83%E9%8C%84 ---&gt;
# [[/The Indifferent Taoist/]] &lt;!--- northern song https://zh.wikisource.org/wiki/%E7%8E%89%E6%AD%B7%E5%AF%B6%E9%88%94 ---&gt; 
&lt;!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---&gt;

===Unit 10: Nation Focus - Ryukyu Kingdom===
# [[/Historical Annals with Sai On/]] &lt;!--- Kyuko is an easy cop ---&gt;
# [[/The Enthronement of Shō Tei/]] 
# [[/The Twilight of Ryukyu with Shō Ten/]] 
# [[/A Trip to Ryukyu with Luo Sen/]] &lt;!--- Pre-Capstone ---&gt;
&lt;!---
遐邇貫珍 1854-11 - 日本日記 羅森 
https://archive.org/details/HEKC185411/page/n5/mode/1up
A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 
日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者
不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 
---&gt;
&lt;!--- 中山世鑑 and so on. Lots of poetry too. ---&gt;

===Unit 11: Nation Focus - Singapore===
&lt;!--- National Library of Singapore has a poetry series that's super good! ---&gt;

===Unit 12: Literary Chinese in Medicine===
&lt;!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---&gt;
# [[/The Books of the Yellow Emperor/]] 
&lt;!-- 黃帝内徑 ---&gt;
# [[/Deviant Qi with Zhang Congzheng/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---&gt;
# [[/Anatomy with Sugita Genpaku/]]
&lt;!--- 解体新書 ---&gt;
# [[/A Lost Wu Medical Text analysed in Japan/]]
&lt;!--- 難經古義 ---&gt;

===Unit 13: People Focus - Zhuang peoples===
&lt;!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&amp;knowledgeId=84745463&amp;_from_=&amp;_fromV2_=&amp;rtag= 《峤西诗钞》 is also a really good shout. Found here: https://ctext.org/wiki.pl?if=gb&amp;res=215640&amp;remap=gb ---&gt;
&lt;!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---&gt;
# [[/Zhuang poetry with Li Bi/]]
# [[/The Beauty of Wuyuan with Fang Ju/]]
# [[/Disaster and Society with Wei Fenghua/]]
# [[/Who Deserves a Biography?/]]

&lt;!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm

一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云：

去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。

诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。

This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---&gt;

===Unit 14: People Focus - Tangut peoples===
&lt;!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---&gt; 

===Unit 15: Literary Chinese in the Military===
&lt;!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---&gt;
# [[/Fū! Rin! Ka! Zan!/]]
# [[/A Bilingual Stele of the Khitans/]]
# [[/Going to war with Boyan/]]
&lt;!---
Boyan's Poem from the 元史
　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。

　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。

　　過梅嶺岡留題

馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。

　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。
---&gt;
# [[/An Edict from the Xianbei/]]
# [[/The Suppression of the Kingdom of Dongning/]]
&lt;!---
台灣鄭氏始末
https://ctext.org/wiki.pl?if=en&amp;chapter=139938

Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. 
---&gt;
# [[/The Shunzhi Emperor vs Li Zicheng/]]
# [[/The Art of War/]]

===Unit 16: Nation Focus - Vietnam===
# [[/Đỗ Pháp Thuận and the Southern Skies/]]
# [[/Ancestor Veneration with the Descendants of Zhu Xi/]] 
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean  somewhere in here ---&gt;
# [[/Resolving a Succession Crisis with Emperor Trần Minh Tông/]] &lt;!-- 南翁夢錄·黎澄 --&gt;
# [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] 
&lt;!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---&gt;
# [[/Academia in Literary Chinese between East and West/]] 
&lt;!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---&gt;

===Unit 17: Historical Annals and Encyclopediae===
&lt;!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---&gt; 
# [[/An Introduction to Biographical Paintings/]]
&lt;!-- 
Many older paintings include biographies at the top in Literary Chinese. Students need to learn these.
https://commons.wikimedia.org/wiki/File:%E6%AD%B7%E4%BB%A3%E8%81%96%E8%B3%A2%E5%8D%8A%E8%BA%AB%E5%83%8F_%E5%86%8A_%E8%AB%B8%E8%91%9B%E4%BA%AE_(Zhuge_Liang).png - Famous figure, also part of a very notable series.
https://commons.wikimedia.org/wiki/File:Otomo-Sorin-2.jpg - Contains the Japanese repetition character 々
https://commons.wikimedia.org/wiki/File:Toyotomi_hideyoshi4.jpg - simply has aura
--&gt;
# [[/The History of Liao, Jin, and Song with Toqto'a/]] &lt;!--- 脱脱 ---&gt;
# [[/Two Years in the Forbidden City with Yu Deling/]] &lt;!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---&gt;
# [[/Selected Records of the History of the Da Shun/]]
&lt;!--- Fair Use of a 2010 book written in Literary Chinese about the Da Shun dynasty. Limit to 500 characters, if that. Use to encourage recognition of Simplified variants and modern Wenyanwen. ---&gt;
# [[/Documenting the World with Terajima/]]
&lt;!--- 和漢三才図会 寺島良安, built off 三才圖會 ---&gt;

===Unit 18: Buddhist Literature===
&lt;!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---&gt;
&lt;!--- Place focus on practical stuff first. Stuff you can and WILL see in Buddhist temples. Stuff Buddhists can take away immediately. Skills-based approach feels strongest here. ---&gt;
&lt;!--- Look at Northern Liang and Later Qin literature, as there is a ton of work by translators from India during the 16 kingdoms period, particularly those two. ---&gt;
&lt;!--- Stuff by Bodhidharma 達摩 could be fun too https://zh.wikisource.org/wiki/Author:%E9%81%94%E6%91%A9 ---&gt;
# [[/Dipping your feet in with Wenyan Shu/]]
&lt;!---
華亭
世尊遺法本忘言，教外別傳意已圓。
只履攜將蔥嶺去，不妨來上月明船。
---&gt; 
# [[/Buddhism in Battle Standards/]]
# [[/The Seven Tathagatas/]] 
&lt;!---
南無寶勝如來
南無多寶如來
南無妙色身如來
南無廣博身如來
南無離怖畏如來
南無甘露王如來
南無阿彌陀佛

Use to introduce some core vocabulary in repetitive manner. 

Useful phrases from my trip to Jing'an Temple
南無本師釋迦牟尼佛 - Pay homage to the root teacher
南無大悲觀世音菩薩 - Pay homage to the goddess of mercy 
廣種福田 - widely plant a meritorious field 
---&gt;
# [[/Two Buddhist Temples in Shanghai/]] 
&lt;!---
留雲禪寺
雲留雲翔領畧幾許禪機此地有雲散天開真如界。
塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。

歲次壬午冬月吉旦。
覺醒敬撰。
楊胡生沐手恭書。
善信印利明敬獻。 
---&gt;
&lt;!--- 福慧宝鼎 慧明大和尚 - introduce the Buddhist timekeeping system with 佛歷 around this point. 
赤烏古剎
建寺一千七百六十周年紀念

古剎三國建
滬瀆有重玄
石佛音淨現
聖跡顯重元
唐時稱永泰
宋敕名靜安
聖祖留佛闡
仲師移伽藍
元收八景偈
明鑄鐘聲梵
清樹化羅漢
選賢十方讚
佛日普光明
福慧共修善
鼎運昌隆際
轉正法輪緣

歲次丁亥住持慧明監製
---&gt;
# [[/Foreseeing Monkhood with Yi Xing/]]
&lt;!--- 看命一掌金 ---&gt;
# [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
# [[/Jizang's Three Discourses/]]
&lt;!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---&gt;
&lt;!---
I saw these texts being quoted and thus should consider them in some capacity.
《般若波羅蜜多心經》
《金剛般若波羅蜜經》
《一切智光明仙人慈心因緣不食肉經》
《妙法蓮華經》
《大般涅槃經》
《大方等大集經》
《大毘盧舍那成佛神變加持經蓮華胎藏悲生曼荼羅廣大成就儀軌供養方便會》/ 胎藏曼荼羅 
《佛說救拔焰口餓鬼陀羅尼經》
《雜阿含經》

Look at Japan's 五山文学
---&gt;

===Unit 19: People Focus - Manchu peoples===
# [[/Qing dynasty Poetry with Nara Singde/]] 
&lt;!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---&gt;
# [[/Amassing Words with the Kangxi Emperor/]] 
# [[/Amassing Literature with the Qianlong Emperor/]] 
&lt;!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---&gt;
&lt;!---
Yongzheng Emperor's Poetry 
https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D
《和碩怡賢親王祭文》

Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. 
https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B
---&gt;
# [[/Paintings and Beauty with Puru Aisin-Gioro/]]
&lt;!--- Saw these in Shanghai Museum with some writing, seemed really cool. Teaches another skill. ---&gt;

===Unit 20: Qing-RoC Literature===
&lt;!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---&gt;
# [[/Jewish Refugees in Shanghai/]] 
&lt;!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---&gt;
# [[/A Literary Chinese Abstract/]] 
&lt;!--- Abstracts from siku quanshu, probably want others ---&gt;
# [[/Lament with Lu Ruoteng/]] 
&lt;!---
《疑猜》盧若騰，東寧國
盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。
此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。
我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。
盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。
---&gt;
# [[/Common Linguistics Knowledge in the RoC/]]
&lt;!--- 音韻常識 ---&gt;

==References used for this page==
* Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9
* Priestley, K. E., &amp; Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books.
{{BookCat}}</text>
      <sha1>d2bp0f9fgi6vrvb4zc363m9jv6272aq</sha1>
    </revision>
    <revision>
      <id>4669035</id>
      <parentid>4669033</parentid>
      <timestamp>2026-09-06T00:29:30Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Added cookbooks, this is great for getting the reader moving and understanding how instructions are given.</comment>
      <origin>4669035</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="36599" sha1="ifzl7o0grenq8i5av3iefj8wm0nifj3" xml:space="preserve">__notoc__

Welcome to the Wikibook for Literary Chinese (Known as 漢文 &quot;Han Language&quot; in East Asia or 文言 &quot;Literary Language&quot; in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. 

This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This  text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. However, as Zhou-Qin era texts served as the main body from which individuals learned, they are employed here as and when they are considered necessary or otherwise useful. It does so through a &quot;buffet&quot; approach, showering you, the reader, with an ocean of texts of myriad genre. 

==Table of Contents==

=== Front matter ===

* [[/Introduction/]]
* [[/Appendices/]]

=== Useful resources ===
These are quick grab-bags that can be useful for vocabulary-building. 
* [[/Antonym List/]] &lt;!--- 文/武，大/小，厚/薄，橫/縱...---&gt;
* [[/Collocation Groups/]] &lt;!--- e.g. 四象，三靈…… ---&gt;
* [[/Pronoun Table/]]
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] &lt;!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms]
&lt;!--- this will be translated eventually, but right now it's bad to just leave this here. ---&gt;

=== Useful primers ===
Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. 
* [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. 
* 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. 
** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. 
* 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. 
* 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. 
* 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece.

===Unit 0: The Han script===
This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. 

By the end of this unit, students will:
* Recognise around 50 characters.
* Understand how characters are composed and how this gives them meaning.
* Have a basic idea of how to handwrite and/or type characters using the Cangjie Input Method.
* Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of &quot;is&quot;, 有...)

Lessons:
# [[/An Introduction to the Han Script/]]
# [[/People, Big and Small/]]
# [[/How do we write Chinese?/]]
# [[/What are Chinese characters, anyway?/]]
# [[/The Sun, the Moon, and the Five Elements/]]
# [[/Getting Familiar with Body Parts/]]
# [[/Using Numbers and Using Weapons/]] &lt;!--- 竹戈十大中一弓廿卜---&gt;
# [[/Tilling the Fields with 有/]] &lt;!--- 山田 ---&gt;
# [[/How Characters are Made/|How Characters are Made with Kiyohara no Sanemoto]] 
# [[/Cangjie Created Characters/]] &lt;!--- Get people to use Cangjie ---&gt;
# [[/The Kangxi Radical System/]] &lt;!--- Introduce some monoradical texts to train recognition. ---&gt;

===Unit 1: Basic Skills===
This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. 

Before starting this unit, students should:
* Recognise around ~30 characters. 
* Can use Cangjie input. 
* Have given Unit 0 a cursory glance. 
&lt;br&gt;
By the end of this unit, students will:
* Recognise around ~100 characters. 
* Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date.
* Intuit the basic topic -&gt; comment idea behind Literary Chinese. &quot;This, it is...&quot; 
* Understand basic function words such as 也, 而, 有, and 謂.

Lessons:
# [[/The All-Purpose 也/]]
# [[/An Introduction to Chinese Numbers/]] &lt;!--- It is hard to find authentic materials for this ---&gt;
# [[/One, Two, Left, and Right with Gongsun Long/]]
&lt;!---
曰：「二有一乎？」

曰：「二無一。」

曰：「二有右乎？」

曰：「二無右。」

曰：「二有左乎？」

曰：「二無左。」

曰：「右可謂二乎？」

曰：「不可。」

曰：「左可謂二乎？」

曰：「不可。」

曰：「左與右可謂二乎？」

曰：「可。」
---&gt;
# [[/The Heavenly Stems/]] &lt;!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---&gt;
# [[/Tell the Time with Earthly Branches/]] &lt;!--- Introduce verbs and timekeeping ---&gt;
# [[/Lunar Dates with the Spring and Autumn Annals/]]
&lt;!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---&gt;
# [[/Skimming for Major Events in Historical Annals/]] 
&lt;!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. 

E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. 
https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701

Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! 
---&gt;
# [[/Dinner with the Daimyo/]]
&lt;!-- 
侍宴·大友皇子
皇明光日月，帝徳載天地。
三才併秦昌，万国表臣義。
--&gt; 
# [[/In Discourse with Jibong/]]
&lt;!--
芝峰類說 
倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。
--&gt;
# [[/How do we Write Height and Weight?/]] &lt;!--- Hilarious oversight ---&gt;
# [[/Eating like a Zhou Aristocrat/]] 
# [[/Shinto FAQ with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E7%9C%9E%E9%81%93%E5%95%8F%E5%B0%8D 眞道問對 本田親徳 really good way of operationalising 乎 and much of the early grammar. 

問 天帝無始無終乎。
對 天帝無始無終也。
旣以無始無終之力
與無始無終之體
造無始無終之萬物。
其功亦無始無終也。

問 天地大原在道乎。
對 天地大原實在道。
鬼神依道而立。
人民依道而活。
萬物依道而息。

This is great! ---&gt;

&lt;!---
Some cool stuff I saw someone studying from
https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98#
https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98

Could be used for period focus
---&gt;

===Unit 2: An Overview of Sinitic Poetry===
This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. 

After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole!

By the end of this Unit, students will:
* Recognise around 120 more characters.
* Be able to explain how Sinitic Poetry rhymes and the themes it contains.
* Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts.
* Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage.
* (Chinese speakers) Be able to differentiate 于 and 於, and understand the &quot;interest(ed) in&quot; meaning of 好 in most circumstances.
&lt;!---
Summary of the above part about 于 and 於 for other editors:
于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their &quot;merging&quot; through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000);
* 于 - This can mean &quot;to go&quot; or &quot;to/at&quot;. 黃鳥于飛 &quot;The yellow birds go flying&quot;. Must be post-verbal. It can also appear in 至于.
* 於 - This is an all-purpose locative preposition - from &quot;on/at/in&quot; to &quot;from&quot; or even &quot;than&quot; (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏).
---&gt;

Lessons:
# [[/Across the Rivers with Emperor Puliuru Guang/]] &lt;!--- Illustrate ping-ze ---&gt;
# [[/To Study the Odes/]] 
# [[/A Detour into Orthodox Ping-Ze/]] 
&lt;!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---&gt;
# [[/The Restraint of Du Fu/]] 
# [[/The Longing of Li Bai/]] 
# [[/The Environment with Bukha Timur/]]
# [[/Pillow Talk with Guan Yunshi/]]
&lt;!---
紅繡鞋·貫雲石
挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！

Uyghur author!
---&gt;
# [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]]
&lt;!-- 元火·吳真流
木中元有火，元火復還生。
若為木無火，鉆燧何有萌。--&gt;
&lt;!-- 杜鵑·大成聖安
夢覚孤床静
杜鵑帯雨飛
一声来近枕
何者不沾衣
--&gt;
# [[/Odes with Mō Taiei and Zheng Chengxun/]]
&lt;!-- 詠松·毛泰永
植體宜千仞，垂陰動百尋。
李膺真烈烈，和嶠自森森。
桃李何堪較，雪霜安得侵。
萬年身不老，種子又成林。
AKA Inoha Seiki 伊野波 盛紀 --&gt;
&lt;!-- 詠班蘭·鄭成勛
南國多芳草，班蘭最有名。
深根將綠茁，長葉亦叢生。
取味迎賓合，入厨任水烹。
可憐經一用，擲棄不留情。

鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --&gt;
# [[/A Golden Cup and the Fall of a Dynasty with Yan Fu/]] 
# [[/On a Journey with Sadula/]]
&lt;!---
No lesson entry:
朝中措·襄陽古道灞陵橋
襄陽古道灞陵橋，詩興與秋高。
千古風流人物，一時多少雄豪。

霜清玉塞，雲飛隴首，風落江皋。
夢到鳳凰台上，山圍故國周遭。

北郊晚步
陂水荷凋晚，茅檐燕去涼。
遠林明落景，平麓淡秋光。
群牧歸村巷，孤禽立野航。
自諳閑散樂，園圃意尤長。

Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later.
---&gt;

===Unit 3: Confucianism and the World===
This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states!

By the end of this unit, students should be able to:
* Recognise around 200+ characters.
* Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably.
* Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. 
** 於 and 于 should be distinguishable.
* Survive a text of at least 250 characters and read for gist.

Lessons:
# [[/A Brief Overview of Confucianism/]] 
# [[/Teaching the Annals in Qi/]] &lt;!-- Gongyang Gao's commentary --&gt;
# [[/Is a White Horse a Horse?/]]&lt;!-- Teach negation with 非 in 公孙龍子 and compare with 不 --&gt;
# [[/The Three Character Classic/]]
# [[/Expressing Filial Conduct with Confucius and Hara Saihin/]]
&lt;!--
次韻杏坪先生
父執有君孤不孤
相依遍接搢紳徒
区区自抱地方寸
杳杳重遊天一隅
羇雁飛鳴迷汝國
家人思夢入江都
如教志業青年遂
世上寧無逐臭夫
--&gt;
# [[/Confucianism and the Environment with Sai On/]]&lt;!-- 木假山記 --&gt;
# [[/In Debate with Mencius/]]

===Unit 4: Women's Writing===
In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here!
# [[/An Unmarried Life with Heo Nansŏrhŏn/]]
&lt;!---
貧女吟 
豈是乏容色。工鍼復工織。
少小長寒門。良媒不相識。

夜久織未休。戛戛鳴寒機。
機中一匹練。終作阿誰衣。

手把金翦刀。夜寒十指直。
爲人作嫁衣。年年還獨宿。
---&gt;
# [[/Responding to Lord Trần with Hồ Xuân Hương/]]
&lt;!---
Responding to 陳光靜 Trần Quang Tĩnh

《和陳侯》
愧無才調使人驚，十載風塵貫耳鈴。
已是臨枰知敵手，莫須敲月苦殫精。
為輪為彈隨遭遇，誰鳳誰鶯任賦生。
造物於人何苟惜，明珠休向暗中呈。

莫須 is an important structure to teach here.
---&gt;
# [[/Gaze into the Autumn Night with Taisei Shōan/]]
&lt;!---
秋夜偶成·大成聖安
長天浮爽気，月色興無窮
群犬吠山径，百蟲啼野風
悲秋秋夜永，感古古今同
自是孤窓下，凄然万慮空
---&gt;
# [[/Visiting a Temple with Yu Xuanji/]]
&lt;!---
遊崇真觀南樓覩新及第題名處
雲峰滿目放春晴，歷歷銀鈎指下生。
自恨羅衣掩詩句，擧頭空羨榜中名。
---&gt;
# [[/Remonstrance with Dasese/]]
&lt;!---
https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C
諷諫歌·大瑟瑟
勿嗟塞上兮暗紅塵。
勿傷多難兮畏夷人。
不如塞奸邪之路兮選取賢臣。
直須臥薪嚐膽兮激壯士之捐身。
可以朝清漠北兮夕枕燕雲。

Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. 
---&gt;
# [[/The Love Songs of the Odes/]]
&lt;!---
褰裳
子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！
子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！

柏舟
彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。
汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。

行露
厭浥行露，豈不夙夜，謂行多露。
誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。
誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。
---&gt;
# [[/Rules for Women with Ban Zhao/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---&gt;
# [[/The Tragedy of Cai Wenji/]]
&lt;!---
悲憤詩
〔兩漢〕蔡文姬
漢季失權柄，董卓亂天常。
志欲圖篡弒，先害諸賢良。
逼迫遷舊邦，擁主以自強。
海內興義師，欲共討不祥。
卓眾來東下，金甲耀日光。
平土人脆弱，來兵皆胡羌。
獵野圍城邑，所向悉破亡。
斬截無孑遺，屍骸相撐拒。
馬邊懸男頭，馬後載婦女。
長驅西入關，迥路險且阻。
還顧邈冥冥，肝脾為爛腐。
所略有萬計，不得令屯聚。
或有骨肉俱，欲言不敢語。
失意幾微間，輒言斃降虜。
要當以亭刃，我曹不活汝。
豈復惜性命，不堪其詈罵。
或便加棰杖，毒痛參並下。
旦則號泣行，夜則悲吟坐。
欲死不能得，欲生無一可。
彼蒼者何辜，乃遭此厄禍。
邊荒與華異，人俗少義理。
處所多霜雪，胡風春夏起。
翩翩吹我衣，肅肅入我耳。
感時念父母，哀嘆無窮已。
有客從外來，聞之常歡喜。
迎問其消息，輒復非鄉里。
邂逅徼時願，骨肉來迎己。
己得自解免，當復棄兒子。
天屬綴人心，念別無會期。
存亡永乖隔，不忍與之辭。
兒前抱我頸，問母欲何之。
人言母當去，豈復有還時。
阿母常仁惻，今何更不慈。
我尚未成人，奈何不顧思。
見此崩五內，恍惚生狂痴。
號泣手撫摩，當發復回疑。
兼有同時輩，相送告離別。
慕我獨得歸，哀叫聲摧裂。
馬為立踟躕，車為不轉轍。
觀者皆噓唏，行路亦嗚咽。
去去割情戀，遄征日遐邁。
悠悠三千里，何時復交會。
念我出腹子，匈臆為摧敗。
既至家人盡，又復無中外。
城廓為山林，庭宇生荊艾。
白骨不知誰，縱橫莫覆蓋。
出門無人聲，豺狼號且吠。
煢煢對孤景，怛吒糜肝肺。
登高遠眺望，魂神忽飛逝。
奄若壽命盡，旁人相寬大。
為復強視息，雖生何聊賴。
託命於新人，竭心自勖勵。
流離成鄙賤，常恐復捐廢。
人生幾何時，懷憂終年歲。
---&gt;

===Unit 5: Myths and Legends of East Asia===
&lt;!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---&gt;
# [[/Exploring the World of Mountains and Seas/]]&lt;!-- Structure: 出焉 --&gt;
# [[/Oh, the Qilin!/]] &lt;!--- Even here, the odes can be studied! ---&gt;
# [[/The Poison of Zhen/]] &lt;!--- referenced a lot in histories ---&gt;
# [[/Ultimate Justice with Xiezhi/]] &lt;!--- the yellow emperor met one, gao yao also used one ---&gt;
# [[/The Virtue of the Fenghuang/]] &lt;!--- shanhaijing has a great line on this ---&gt;
# [[/The Entrapment of Hua Po/]] 
# [[/Nüwa Created the World/]]

===Unit 6: Food from Across the Ages===
# [[/A Simple, Rich Fry/]] &lt;!--- 《禮記 內則》淳熬：煎醢，加于陸稻上，沃之以膏曰淳熬。淳毋煎醢，加于黍食上，沃之以膏曰淳毋。---&gt;
# [[/Song Cuisine with Chen Dasou and Lin Hong/]] &lt;!--- 陳達叟 本心齋疏食譜 https://zh.wikisource.org/zh-hant/%E6%9C%AC%E5%BF%83%E6%96%8B%E7%96%8F%E9%A3%9F%E8%B0%B1 ---&gt; &lt;!--- 山家清供 https://zh.wikisource.org/wiki/%E5%B1%B1%E5%AE%B6%E6%B8%85%E4%BE%9B ---&gt;
# [[/Yuan Cuisine with Ni Zan/]] &lt;!--- https://ctext.org/wiki.pl?chapter=318337&amp;if=en 《雲林堂飲食制度集》倪瓚 one of the Four Masters, also a painter ---&gt;
# [[/A Feast with Yuan Mei/]] &lt;!--- 袁枚 隨園食單 https://ctext.org/wiki.pl?if=gb&amp;res=344157 ---&gt;

===Unit 7: Nation Focus - Japan===
# [[/The Inariyama Sword/]] 
&lt;!--- short and sweet! ---&gt;
# [[/Entering Japan with Takeda Shingen/]]
# [[/The Oldest Inscription in Japan/]] 
&lt;!--- 宇治橋断碑 ---&gt; 
# [[/The End of a Rebellion/]] 
# [[/Shinto Teachings with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---&gt;  
# [[/The Diary of Fujiwara no Teika/]] &lt;!--- 明月記 ---&gt;
# [[/Reading the History of Japan with Prince Toneri/]] &lt;!--- 日本書記, etc. ---&gt; 
# [[/A Biographical Painting of Toyotomi Hideyoshi/]] &lt;!--- This is on Fanya Hanwen Corpus ---&gt;
&lt;!--- # [[/Occupying Taiwan/]] ---&gt;
&lt;!--- I have some colonial literature on me that can be used here. ---&gt;

===Unit 8: Nation Focus - Korea===
# [[/Feigned Surrender with Ŭlchi Mundŏk/]] &lt;!--- 乙支文德漢詩 ---&gt;
# [[/A fu with Yi Kyubo/]]
# [[/An Elegy to the Empress with Choe Ja/]]
&lt;!---
Choe Ja
元德大后輓詞·崔滋（최자）
乾極曾客配,坤儀正體元。
枕前朝聖主,帳底見曾孫。
陰慘俄沉月,屋悲便沒軒。
三韓千古淚,七十九年恩。
---&gt;
# [[/Language Reform with Sejong the Great/]]
&lt;!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---&gt;
# [[/Fall Off Your Horse!/]] &lt;!--- a famous record from 朝鮮王朝實錄 ---&gt;
# [[/The Diary of Yi Sun-Sin/]] &lt;!--- 亂中日記 ---&gt;
# [[/Tales from Mount Kumo/]] &lt;!--- 金鰲新話 ---&gt;
# [[/Pak Chiwŏn Tours the Qing/]] &lt;!--- 熱河日記 ---&gt;
# [[/Korea's Three Kingdoms/]] &lt;!--- 三國史記 for sure! ---&gt;
# [[/Hwang Yun-seok's Essays/]] &lt;!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---&gt;

===Unit 9: Christian Literature===
# [[/A Different Three Character Classic with Hong Xiuquan/]]
# [[/Friar Juan Cobo's Veritable Record/]] 
&lt;!--- 
One of few texts from the Philippines that I have ever found!
https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 
---&gt;
# [[/The Delegate's Edition/]]
# [[/Nestorian Steles during the Tang/]] 
&lt;!--- 大秦景教宣元至本經經幢 and 景教碑 ---&gt;
# [[/Hong Xiuquan's Bible/]]
&lt;!--- https://bible.fhl.net/ob/nob.html?book=407 ---&gt;
&lt;!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---&gt;

===Unit 10: An Introduction to Daoism===
&lt;!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---&gt;
# [[/Laozi Explains the Dao/]]
# [[/Qingtan with Xie Daoyun/]]
# [[/The Doubting Neighbour/]] 
# [[/Kuafu Chases the Sun/]] 
# [[/The Frog in a Well/]] 
# [[/Wu wei with King Hui of Liang/]]
# [[/The Old Man that Moves the Mountains/]]
# [[/Master Zhuang Dreams of Butterflies/]]
# [[/Master Incapable and the Poisonous Bird/]]
# [[/Transmitting the Dao with Yelü Chucai/]] &lt;!---耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. https://zh.wikisource.org/wiki/%E7%8E%84%E9%A2%A8%E6%85%B6%E6%9C%83%E9%8C%84 ---&gt;
# [[/The Indifferent Taoist/]] &lt;!--- northern song https://zh.wikisource.org/wiki/%E7%8E%89%E6%AD%B7%E5%AF%B6%E9%88%94 ---&gt; 
&lt;!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---&gt;

===Unit 11: Nation Focus - Ryukyu Kingdom===
# [[/Historical Annals with Sai On/]] &lt;!--- Kyuko is an easy cop ---&gt;
# [[/The Enthronement of Shō Tei/]] 
# [[/The Twilight of Ryukyu with Shō Ten/]] 
# [[/A Trip to Ryukyu with Luo Sen/]] &lt;!--- Pre-Capstone ---&gt;
&lt;!---
遐邇貫珍 1854-11 - 日本日記 羅森 
https://archive.org/details/HEKC185411/page/n5/mode/1up
A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 
日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者
不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 
---&gt;
&lt;!--- 中山世鑑 and so on. Lots of poetry too. ---&gt;

===Unit 12: Nation Focus - Singapore===
&lt;!--- National Library of Singapore has a poetry series that's super good! ---&gt;

===Unit 13: Literary Chinese in Medicine===
&lt;!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---&gt;
# [[/The Books of the Yellow Emperor/]] 
&lt;!-- 黃帝内徑 ---&gt;
# [[/Deviant Qi with Zhang Congzheng/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---&gt;
# [[/Anatomy with Sugita Genpaku/]]
&lt;!--- 解体新書 ---&gt;
# [[/A Lost Wu Medical Text analysed in Japan/]]
&lt;!--- 難經古義 ---&gt;

===Unit 14: People Focus - Zhuang peoples===
&lt;!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&amp;knowledgeId=84745463&amp;_from_=&amp;_fromV2_=&amp;rtag= 《峤西诗钞》 is also a really good shout. Found here: https://ctext.org/wiki.pl?if=gb&amp;res=215640&amp;remap=gb ---&gt;
&lt;!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---&gt;
# [[/Zhuang poetry with Li Bi/]]
# [[/The Beauty of Wuyuan with Fang Ju/]]
# [[/Disaster and Society with Wei Fenghua/]]
# [[/Who Deserves a Biography?/]]

&lt;!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm

一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云：

去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。

诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。

This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---&gt;

===Unit 15: People Focus - Tangut peoples===
&lt;!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---&gt; 

===Unit 16: Literary Chinese in the Military===
&lt;!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---&gt;
# [[/Fū! Rin! Ka! Zan!/]]
# [[/A Bilingual Stele of the Khitans/]]
# [[/Going to war with Boyan/]]
&lt;!---
Boyan's Poem from the 元史
　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。

　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。

　　過梅嶺岡留題

馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。

　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。
---&gt;
# [[/An Edict from the Xianbei/]]
# [[/The Suppression of the Kingdom of Dongning/]]
&lt;!---
台灣鄭氏始末
https://ctext.org/wiki.pl?if=en&amp;chapter=139938

Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. 
---&gt;
# [[/The Shunzhi Emperor vs Li Zicheng/]]
# [[/The Art of War/]]

===Unit 17: Nation Focus - Vietnam===
# [[/Đỗ Pháp Thuận and the Southern Skies/]]
# [[/Ancestor Veneration with the Descendants of Zhu Xi/]] 
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean  somewhere in here ---&gt;
# [[/Resolving a Succession Crisis with Emperor Trần Minh Tông/]] &lt;!-- 南翁夢錄·黎澄 --&gt;
# [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] 
&lt;!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---&gt;
# [[/Academia in Literary Chinese between East and West/]] 
&lt;!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---&gt;

===Unit 18: Historical Annals and Encyclopediae===
&lt;!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---&gt; 
# [[/An Introduction to Biographical Paintings/]]
&lt;!-- 
Many older paintings include biographies at the top in Literary Chinese. Students need to learn these.
https://commons.wikimedia.org/wiki/File:%E6%AD%B7%E4%BB%A3%E8%81%96%E8%B3%A2%E5%8D%8A%E8%BA%AB%E5%83%8F_%E5%86%8A_%E8%AB%B8%E8%91%9B%E4%BA%AE_(Zhuge_Liang).png - Famous figure, also part of a very notable series.
https://commons.wikimedia.org/wiki/File:Otomo-Sorin-2.jpg - Contains the Japanese repetition character 々
https://commons.wikimedia.org/wiki/File:Toyotomi_hideyoshi4.jpg - simply has aura
--&gt;
# [[/The History of Liao, Jin, and Song with Toqto'a/]] &lt;!--- 脱脱 ---&gt;
# [[/Two Years in the Forbidden City with Yu Deling/]] &lt;!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---&gt;
# [[/Selected Records of the History of the Da Shun/]]
&lt;!--- Fair Use of a 2010 book written in Literary Chinese about the Da Shun dynasty. Limit to 500 characters, if that. Use to encourage recognition of Simplified variants and modern Wenyanwen. ---&gt;
# [[/Documenting the World with Terajima/]]
&lt;!--- 和漢三才図会 寺島良安, built off 三才圖會 ---&gt;

===Unit 19: Buddhist Literature===
&lt;!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---&gt;
&lt;!--- Place focus on practical stuff first. Stuff you can and WILL see in Buddhist temples. Stuff Buddhists can take away immediately. Skills-based approach feels strongest here. ---&gt;
&lt;!--- Look at Northern Liang and Later Qin literature, as there is a ton of work by translators from India during the 16 kingdoms period, particularly those two. ---&gt;
&lt;!--- Stuff by Bodhidharma 達摩 could be fun too https://zh.wikisource.org/wiki/Author:%E9%81%94%E6%91%A9 ---&gt;
# [[/Dipping your feet in with Wenyan Shu/]]
&lt;!---
華亭
世尊遺法本忘言，教外別傳意已圓。
只履攜將蔥嶺去，不妨來上月明船。
---&gt; 
# [[/Buddhism in Battle Standards/]]
# [[/The Seven Tathagatas/]] 
&lt;!---
南無寶勝如來
南無多寶如來
南無妙色身如來
南無廣博身如來
南無離怖畏如來
南無甘露王如來
南無阿彌陀佛

Use to introduce some core vocabulary in repetitive manner. 

Useful phrases from my trip to Jing'an Temple
南無本師釋迦牟尼佛 - Pay homage to the root teacher
南無大悲觀世音菩薩 - Pay homage to the goddess of mercy 
廣種福田 - widely plant a meritorious field 
---&gt;
# [[/Two Buddhist Temples in Shanghai/]] 
&lt;!---
留雲禪寺
雲留雲翔領畧幾許禪機此地有雲散天開真如界。
塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。

歲次壬午冬月吉旦。
覺醒敬撰。
楊胡生沐手恭書。
善信印利明敬獻。 
---&gt;
&lt;!--- 福慧宝鼎 慧明大和尚 - introduce the Buddhist timekeeping system with 佛歷 around this point. 
赤烏古剎
建寺一千七百六十周年紀念

古剎三國建
滬瀆有重玄
石佛音淨現
聖跡顯重元
唐時稱永泰
宋敕名靜安
聖祖留佛闡
仲師移伽藍
元收八景偈
明鑄鐘聲梵
清樹化羅漢
選賢十方讚
佛日普光明
福慧共修善
鼎運昌隆際
轉正法輪緣

歲次丁亥住持慧明監製
---&gt;
# [[/Foreseeing Monkhood with Yi Xing/]]
&lt;!--- 看命一掌金 ---&gt;
# [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
# [[/Jizang's Three Discourses/]]
&lt;!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---&gt;
&lt;!---
I saw these texts being quoted and thus should consider them in some capacity.
《般若波羅蜜多心經》
《金剛般若波羅蜜經》
《一切智光明仙人慈心因緣不食肉經》
《妙法蓮華經》
《大般涅槃經》
《大方等大集經》
《大毘盧舍那成佛神變加持經蓮華胎藏悲生曼荼羅廣大成就儀軌供養方便會》/ 胎藏曼荼羅 
《佛說救拔焰口餓鬼陀羅尼經》
《雜阿含經》

Look at Japan's 五山文学
---&gt;

===Unit 20: People Focus - Manchu peoples===
# [[/Qing dynasty Poetry with Nara Singde/]] 
&lt;!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---&gt;
# [[/Amassing Words with the Kangxi Emperor/]] 
# [[/Amassing Literature with the Qianlong Emperor/]] 
&lt;!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---&gt;
&lt;!---
Yongzheng Emperor's Poetry 
https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D
《和碩怡賢親王祭文》

Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. 
https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B
---&gt;
# [[/Paintings and Beauty with Puru Aisin-Gioro/]]
&lt;!--- Saw these in Shanghai Museum with some writing, seemed really cool. Teaches another skill. ---&gt;

===Unit 21: Qing-RoC Literature===
&lt;!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---&gt;
# [[/Jewish Refugees in Shanghai/]] 
&lt;!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---&gt;
# [[/A Literary Chinese Abstract/]] 
&lt;!--- Abstracts from siku quanshu, probably want others ---&gt;
# [[/Lament with Lu Ruoteng/]] 
&lt;!---
《疑猜》盧若騰，東寧國
盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。
此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。
我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。
盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。
---&gt;
# [[/Common Linguistics Knowledge in the RoC/]]
&lt;!--- 音韻常識 ---&gt;

==References used for this page==
* Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9
* Priestley, K. E., &amp; Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books.
{{BookCat}}</text>
      <sha1>ifzl7o0grenq8i5av3iefj8wm0nifj3</sha1>
    </revision>
    <revision>
      <id>4669036</id>
      <parentid>4669035</parentid>
      <timestamp>2026-09-06T00:50:05Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>/* Unit 6: Food from Across the Ages */ Korean stuff!</comment>
      <origin>4669036</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="36740" sha1="pq9w62oe7r3kaiwln6ogdsxe0cxv66b" xml:space="preserve">__notoc__

Welcome to the Wikibook for Literary Chinese (Known as 漢文 &quot;Han Language&quot; in East Asia or 文言 &quot;Literary Language&quot; in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. 

This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This  text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. However, as Zhou-Qin era texts served as the main body from which individuals learned, they are employed here as and when they are considered necessary or otherwise useful. It does so through a &quot;buffet&quot; approach, showering you, the reader, with an ocean of texts of myriad genre. 

==Table of Contents==

=== Front matter ===

* [[/Introduction/]]
* [[/Appendices/]]

=== Useful resources ===
These are quick grab-bags that can be useful for vocabulary-building. 
* [[/Antonym List/]] &lt;!--- 文/武，大/小，厚/薄，橫/縱...---&gt;
* [[/Collocation Groups/]] &lt;!--- e.g. 四象，三靈…… ---&gt;
* [[/Pronoun Table/]]
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] &lt;!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms]
&lt;!--- this will be translated eventually, but right now it's bad to just leave this here. ---&gt;

=== Useful primers ===
Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. 
* [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. 
* 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. 
** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. 
* 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. 
* 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. 
* 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece.

===Unit 0: The Han script===
This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. 

By the end of this unit, students will:
* Recognise around 50 characters.
* Understand how characters are composed and how this gives them meaning.
* Have a basic idea of how to handwrite and/or type characters using the Cangjie Input Method.
* Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of &quot;is&quot;, 有...)

Lessons:
# [[/An Introduction to the Han Script/]]
# [[/People, Big and Small/]]
# [[/How do we write Chinese?/]]
# [[/What are Chinese characters, anyway?/]]
# [[/The Sun, the Moon, and the Five Elements/]]
# [[/Getting Familiar with Body Parts/]]
# [[/Using Numbers and Using Weapons/]] &lt;!--- 竹戈十大中一弓廿卜---&gt;
# [[/Tilling the Fields with 有/]] &lt;!--- 山田 ---&gt;
# [[/How Characters are Made/|How Characters are Made with Kiyohara no Sanemoto]] 
# [[/Cangjie Created Characters/]] &lt;!--- Get people to use Cangjie ---&gt;
# [[/The Kangxi Radical System/]] &lt;!--- Introduce some monoradical texts to train recognition. ---&gt;

===Unit 1: Basic Skills===
This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. 

Before starting this unit, students should:
* Recognise around ~30 characters. 
* Can use Cangjie input. 
* Have given Unit 0 a cursory glance. 
&lt;br&gt;
By the end of this unit, students will:
* Recognise around ~100 characters. 
* Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date.
* Intuit the basic topic -&gt; comment idea behind Literary Chinese. &quot;This, it is...&quot; 
* Understand basic function words such as 也, 而, 有, and 謂.

Lessons:
# [[/The All-Purpose 也/]]
# [[/An Introduction to Chinese Numbers/]] &lt;!--- It is hard to find authentic materials for this ---&gt;
# [[/One, Two, Left, and Right with Gongsun Long/]]
&lt;!---
曰：「二有一乎？」

曰：「二無一。」

曰：「二有右乎？」

曰：「二無右。」

曰：「二有左乎？」

曰：「二無左。」

曰：「右可謂二乎？」

曰：「不可。」

曰：「左可謂二乎？」

曰：「不可。」

曰：「左與右可謂二乎？」

曰：「可。」
---&gt;
# [[/The Heavenly Stems/]] &lt;!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---&gt;
# [[/Tell the Time with Earthly Branches/]] &lt;!--- Introduce verbs and timekeeping ---&gt;
# [[/Lunar Dates with the Spring and Autumn Annals/]]
&lt;!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---&gt;
# [[/Skimming for Major Events in Historical Annals/]] 
&lt;!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. 

E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. 
https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701

Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! 
---&gt;
# [[/Dinner with the Daimyo/]]
&lt;!-- 
侍宴·大友皇子
皇明光日月，帝徳載天地。
三才併秦昌，万国表臣義。
--&gt; 
# [[/In Discourse with Jibong/]]
&lt;!--
芝峰類說 
倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。
--&gt;
# [[/How do we Write Height and Weight?/]] &lt;!--- Hilarious oversight ---&gt;
# [[/Eating like a Zhou Aristocrat/]] 
# [[/Shinto FAQ with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E7%9C%9E%E9%81%93%E5%95%8F%E5%B0%8D 眞道問對 本田親徳 really good way of operationalising 乎 and much of the early grammar. 

問 天帝無始無終乎。
對 天帝無始無終也。
旣以無始無終之力
與無始無終之體
造無始無終之萬物。
其功亦無始無終也。

問 天地大原在道乎。
對 天地大原實在道。
鬼神依道而立。
人民依道而活。
萬物依道而息。

This is great! ---&gt;

&lt;!---
Some cool stuff I saw someone studying from
https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98#
https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98

Could be used for period focus
---&gt;

===Unit 2: An Overview of Sinitic Poetry===
This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. 

After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole!

By the end of this Unit, students will:
* Recognise around 120 more characters.
* Be able to explain how Sinitic Poetry rhymes and the themes it contains.
* Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts.
* Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage.
* (Chinese speakers) Be able to differentiate 于 and 於, and understand the &quot;interest(ed) in&quot; meaning of 好 in most circumstances.
&lt;!---
Summary of the above part about 于 and 於 for other editors:
于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their &quot;merging&quot; through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000);
* 于 - This can mean &quot;to go&quot; or &quot;to/at&quot;. 黃鳥于飛 &quot;The yellow birds go flying&quot;. Must be post-verbal. It can also appear in 至于.
* 於 - This is an all-purpose locative preposition - from &quot;on/at/in&quot; to &quot;from&quot; or even &quot;than&quot; (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏).
---&gt;

Lessons:
# [[/Across the Rivers with Emperor Puliuru Guang/]] &lt;!--- Illustrate ping-ze ---&gt;
# [[/To Study the Odes/]] 
# [[/A Detour into Orthodox Ping-Ze/]] 
&lt;!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---&gt;
# [[/The Restraint of Du Fu/]] 
# [[/The Longing of Li Bai/]] 
# [[/The Environment with Bukha Timur/]]
# [[/Pillow Talk with Guan Yunshi/]]
&lt;!---
紅繡鞋·貫雲石
挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！

Uyghur author!
---&gt;
# [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]]
&lt;!-- 元火·吳真流
木中元有火，元火復還生。
若為木無火，鉆燧何有萌。--&gt;
&lt;!-- 杜鵑·大成聖安
夢覚孤床静
杜鵑帯雨飛
一声来近枕
何者不沾衣
--&gt;
# [[/Odes with Mō Taiei and Zheng Chengxun/]]
&lt;!-- 詠松·毛泰永
植體宜千仞，垂陰動百尋。
李膺真烈烈，和嶠自森森。
桃李何堪較，雪霜安得侵。
萬年身不老，種子又成林。
AKA Inoha Seiki 伊野波 盛紀 --&gt;
&lt;!-- 詠班蘭·鄭成勛
南國多芳草，班蘭最有名。
深根將綠茁，長葉亦叢生。
取味迎賓合，入厨任水烹。
可憐經一用，擲棄不留情。

鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --&gt;
# [[/A Golden Cup and the Fall of a Dynasty with Yan Fu/]] 
# [[/On a Journey with Sadula/]]
&lt;!---
No lesson entry:
朝中措·襄陽古道灞陵橋
襄陽古道灞陵橋，詩興與秋高。
千古風流人物，一時多少雄豪。

霜清玉塞，雲飛隴首，風落江皋。
夢到鳳凰台上，山圍故國周遭。

北郊晚步
陂水荷凋晚，茅檐燕去涼。
遠林明落景，平麓淡秋光。
群牧歸村巷，孤禽立野航。
自諳閑散樂，園圃意尤長。

Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later.
---&gt;

===Unit 3: Confucianism and the World===
This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states!

By the end of this unit, students should be able to:
* Recognise around 200+ characters.
* Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably.
* Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. 
** 於 and 于 should be distinguishable.
* Survive a text of at least 250 characters and read for gist.

Lessons:
# [[/A Brief Overview of Confucianism/]] 
# [[/Teaching the Annals in Qi/]] &lt;!-- Gongyang Gao's commentary --&gt;
# [[/Is a White Horse a Horse?/]]&lt;!-- Teach negation with 非 in 公孙龍子 and compare with 不 --&gt;
# [[/The Three Character Classic/]]
# [[/Expressing Filial Conduct with Confucius and Hara Saihin/]]
&lt;!--
次韻杏坪先生
父執有君孤不孤
相依遍接搢紳徒
区区自抱地方寸
杳杳重遊天一隅
羇雁飛鳴迷汝國
家人思夢入江都
如教志業青年遂
世上寧無逐臭夫
--&gt;
# [[/Confucianism and the Environment with Sai On/]]&lt;!-- 木假山記 --&gt;
# [[/In Debate with Mencius/]]

===Unit 4: Women's Writing===
In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here!
# [[/An Unmarried Life with Heo Nansŏrhŏn/]]
&lt;!---
貧女吟 
豈是乏容色。工鍼復工織。
少小長寒門。良媒不相識。

夜久織未休。戛戛鳴寒機。
機中一匹練。終作阿誰衣。

手把金翦刀。夜寒十指直。
爲人作嫁衣。年年還獨宿。
---&gt;
# [[/Responding to Lord Trần with Hồ Xuân Hương/]]
&lt;!---
Responding to 陳光靜 Trần Quang Tĩnh

《和陳侯》
愧無才調使人驚，十載風塵貫耳鈴。
已是臨枰知敵手，莫須敲月苦殫精。
為輪為彈隨遭遇，誰鳳誰鶯任賦生。
造物於人何苟惜，明珠休向暗中呈。

莫須 is an important structure to teach here.
---&gt;
# [[/Gaze into the Autumn Night with Taisei Shōan/]]
&lt;!---
秋夜偶成·大成聖安
長天浮爽気，月色興無窮
群犬吠山径，百蟲啼野風
悲秋秋夜永，感古古今同
自是孤窓下，凄然万慮空
---&gt;
# [[/Visiting a Temple with Yu Xuanji/]]
&lt;!---
遊崇真觀南樓覩新及第題名處
雲峰滿目放春晴，歷歷銀鈎指下生。
自恨羅衣掩詩句，擧頭空羨榜中名。
---&gt;
# [[/Remonstrance with Dasese/]]
&lt;!---
https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C
諷諫歌·大瑟瑟
勿嗟塞上兮暗紅塵。
勿傷多難兮畏夷人。
不如塞奸邪之路兮選取賢臣。
直須臥薪嚐膽兮激壯士之捐身。
可以朝清漠北兮夕枕燕雲。

Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. 
---&gt;
# [[/The Love Songs of the Odes/]]
&lt;!---
褰裳
子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！
子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！

柏舟
彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。
汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。

行露
厭浥行露，豈不夙夜，謂行多露。
誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。
誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。
---&gt;
# [[/Rules for Women with Ban Zhao/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---&gt;
# [[/The Tragedy of Cai Wenji/]]
&lt;!---
悲憤詩
〔兩漢〕蔡文姬
漢季失權柄，董卓亂天常。
志欲圖篡弒，先害諸賢良。
逼迫遷舊邦，擁主以自強。
海內興義師，欲共討不祥。
卓眾來東下，金甲耀日光。
平土人脆弱，來兵皆胡羌。
獵野圍城邑，所向悉破亡。
斬截無孑遺，屍骸相撐拒。
馬邊懸男頭，馬後載婦女。
長驅西入關，迥路險且阻。
還顧邈冥冥，肝脾為爛腐。
所略有萬計，不得令屯聚。
或有骨肉俱，欲言不敢語。
失意幾微間，輒言斃降虜。
要當以亭刃，我曹不活汝。
豈復惜性命，不堪其詈罵。
或便加棰杖，毒痛參並下。
旦則號泣行，夜則悲吟坐。
欲死不能得，欲生無一可。
彼蒼者何辜，乃遭此厄禍。
邊荒與華異，人俗少義理。
處所多霜雪，胡風春夏起。
翩翩吹我衣，肅肅入我耳。
感時念父母，哀嘆無窮已。
有客從外來，聞之常歡喜。
迎問其消息，輒復非鄉里。
邂逅徼時願，骨肉來迎己。
己得自解免，當復棄兒子。
天屬綴人心，念別無會期。
存亡永乖隔，不忍與之辭。
兒前抱我頸，問母欲何之。
人言母當去，豈復有還時。
阿母常仁惻，今何更不慈。
我尚未成人，奈何不顧思。
見此崩五內，恍惚生狂痴。
號泣手撫摩，當發復回疑。
兼有同時輩，相送告離別。
慕我獨得歸，哀叫聲摧裂。
馬為立踟躕，車為不轉轍。
觀者皆噓唏，行路亦嗚咽。
去去割情戀，遄征日遐邁。
悠悠三千里，何時復交會。
念我出腹子，匈臆為摧敗。
既至家人盡，又復無中外。
城廓為山林，庭宇生荊艾。
白骨不知誰，縱橫莫覆蓋。
出門無人聲，豺狼號且吠。
煢煢對孤景，怛吒糜肝肺。
登高遠眺望，魂神忽飛逝。
奄若壽命盡，旁人相寬大。
為復強視息，雖生何聊賴。
託命於新人，竭心自勖勵。
流離成鄙賤，常恐復捐廢。
人生幾何時，懷憂終年歲。
---&gt;

===Unit 5: Myths and Legends of East Asia===
&lt;!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---&gt;
# [[/Exploring the World of Mountains and Seas/]]&lt;!-- Structure: 出焉 --&gt;
# [[/Oh, the Qilin!/]] &lt;!--- Even here, the odes can be studied! ---&gt;
# [[/The Poison of Zhen/]] &lt;!--- referenced a lot in histories ---&gt;
# [[/Ultimate Justice with Xiezhi/]] &lt;!--- the yellow emperor met one, gao yao also used one ---&gt;
# [[/The Virtue of the Fenghuang/]] &lt;!--- shanhaijing has a great line on this ---&gt;
# [[/The Entrapment of Hua Po/]] 
# [[/Nüwa Created the World/]]

===Unit 6: Food from Across the Ages===
# [[/A Simple, Rich Fry/]] &lt;!--- 《禮記 內則》淳熬：煎醢，加于陸稻上，沃之以膏曰淳熬。淳毋煎醢，加于黍食上，沃之以膏曰淳毋。---&gt;
# [[/Song Cuisine with Chen Dasou and Lin Hong/]] &lt;!--- 陳達叟 本心齋疏食譜 https://zh.wikisource.org/zh-hant/%E6%9C%AC%E5%BF%83%E6%96%8B%E7%96%8F%E9%A3%9F%E8%B0%B1 ---&gt; &lt;!--- 山家清供 https://zh.wikisource.org/wiki/%E5%B1%B1%E5%AE%B6%E6%B8%85%E4%BE%9B ---&gt;
# [[/Yuan Cuisine with Ni Zan/]] &lt;!--- https://ctext.org/wiki.pl?chapter=318337&amp;if=en 《雲林堂飲食制度集》倪瓚 one of the Four Masters, also a painter ---&gt;
# [[/A Feast with Yuan Mei/]] &lt;!--- 袁枚 隨園食單 https://ctext.org/wiki.pl?if=gb&amp;res=344157 ---&gt;
# [[/Remembering the Food of Joseon with Hŏ Kyun/]] &lt;!--- https://rmda.kulib.kyoto-u.ac.jp/item/rb00023424?page=3p 許筠 屠門大嚼 ---&gt;

===Unit 7: Nation Focus - Japan===
# [[/The Inariyama Sword/]] 
&lt;!--- short and sweet! ---&gt;
# [[/Entering Japan with Takeda Shingen/]]
# [[/The Oldest Inscription in Japan/]] 
&lt;!--- 宇治橋断碑 ---&gt; 
# [[/The End of a Rebellion/]] 
# [[/Shinto Teachings with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---&gt;  
# [[/The Diary of Fujiwara no Teika/]] &lt;!--- 明月記 ---&gt;
# [[/Reading the History of Japan with Prince Toneri/]] &lt;!--- 日本書記, etc. ---&gt; 
# [[/A Biographical Painting of Toyotomi Hideyoshi/]] &lt;!--- This is on Fanya Hanwen Corpus ---&gt;
&lt;!--- # [[/Occupying Taiwan/]] ---&gt;
&lt;!--- I have some colonial literature on me that can be used here. ---&gt;

===Unit 8: Nation Focus - Korea===
# [[/Feigned Surrender with Ŭlchi Mundŏk/]] &lt;!--- 乙支文德漢詩 ---&gt;
# [[/A fu with Yi Kyubo/]]
# [[/An Elegy to the Empress with Choe Ja/]]
&lt;!---
Choe Ja
元德大后輓詞·崔滋（최자）
乾極曾客配,坤儀正體元。
枕前朝聖主,帳底見曾孫。
陰慘俄沉月,屋悲便沒軒。
三韓千古淚,七十九年恩。
---&gt;
# [[/Language Reform with Sejong the Great/]]
&lt;!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---&gt;
# [[/Fall Off Your Horse!/]] &lt;!--- a famous record from 朝鮮王朝實錄 ---&gt;
# [[/The Diary of Yi Sun-Sin/]] &lt;!--- 亂中日記 ---&gt;
# [[/Tales from Mount Kumo/]] &lt;!--- 金鰲新話 ---&gt;
# [[/Pak Chiwŏn Tours the Qing/]] &lt;!--- 熱河日記 ---&gt;
# [[/Korea's Three Kingdoms/]] &lt;!--- 三國史記 for sure! ---&gt;
# [[/Hwang Yun-seok's Essays/]] &lt;!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---&gt;

===Unit 9: Christian Literature===
# [[/A Different Three Character Classic with Hong Xiuquan/]]
# [[/Friar Juan Cobo's Veritable Record/]] 
&lt;!--- 
One of few texts from the Philippines that I have ever found!
https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 
---&gt;
# [[/The Delegate's Edition/]]
# [[/Nestorian Steles during the Tang/]] 
&lt;!--- 大秦景教宣元至本經經幢 and 景教碑 ---&gt;
# [[/Hong Xiuquan's Bible/]]
&lt;!--- https://bible.fhl.net/ob/nob.html?book=407 ---&gt;
&lt;!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---&gt;

===Unit 10: An Introduction to Daoism===
&lt;!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---&gt;
# [[/Laozi Explains the Dao/]]
# [[/Qingtan with Xie Daoyun/]]
# [[/The Doubting Neighbour/]] 
# [[/Kuafu Chases the Sun/]] 
# [[/The Frog in a Well/]] 
# [[/Wu wei with King Hui of Liang/]]
# [[/The Old Man that Moves the Mountains/]]
# [[/Master Zhuang Dreams of Butterflies/]]
# [[/Master Incapable and the Poisonous Bird/]]
# [[/Transmitting the Dao with Yelü Chucai/]] &lt;!---耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. https://zh.wikisource.org/wiki/%E7%8E%84%E9%A2%A8%E6%85%B6%E6%9C%83%E9%8C%84 ---&gt;
# [[/The Indifferent Taoist/]] &lt;!--- northern song https://zh.wikisource.org/wiki/%E7%8E%89%E6%AD%B7%E5%AF%B6%E9%88%94 ---&gt; 
&lt;!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---&gt;

===Unit 11: Nation Focus - Ryukyu Kingdom===
# [[/Historical Annals with Sai On/]] &lt;!--- Kyuko is an easy cop ---&gt;
# [[/The Enthronement of Shō Tei/]] 
# [[/The Twilight of Ryukyu with Shō Ten/]] 
# [[/A Trip to Ryukyu with Luo Sen/]] &lt;!--- Pre-Capstone ---&gt;
&lt;!---
遐邇貫珍 1854-11 - 日本日記 羅森 
https://archive.org/details/HEKC185411/page/n5/mode/1up
A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 
日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者
不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 
---&gt;
&lt;!--- 中山世鑑 and so on. Lots of poetry too. ---&gt;

===Unit 12: Nation Focus - Singapore===
&lt;!--- National Library of Singapore has a poetry series that's super good! ---&gt;

===Unit 13: Literary Chinese in Medicine===
&lt;!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---&gt;
# [[/The Books of the Yellow Emperor/]] 
&lt;!-- 黃帝内徑 ---&gt;
# [[/Deviant Qi with Zhang Congzheng/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---&gt;
# [[/Anatomy with Sugita Genpaku/]]
&lt;!--- 解体新書 ---&gt;
# [[/A Lost Wu Medical Text analysed in Japan/]]
&lt;!--- 難經古義 ---&gt;

===Unit 14: People Focus - Zhuang peoples===
&lt;!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&amp;knowledgeId=84745463&amp;_from_=&amp;_fromV2_=&amp;rtag= 《峤西诗钞》 is also a really good shout. Found here: https://ctext.org/wiki.pl?if=gb&amp;res=215640&amp;remap=gb ---&gt;
&lt;!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---&gt;
# [[/Zhuang poetry with Li Bi/]]
# [[/The Beauty of Wuyuan with Fang Ju/]]
# [[/Disaster and Society with Wei Fenghua/]]
# [[/Who Deserves a Biography?/]]

&lt;!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm

一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云：

去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。

诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。

This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---&gt;

===Unit 15: People Focus - Tangut peoples===
&lt;!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---&gt; 

===Unit 16: Literary Chinese in the Military===
&lt;!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---&gt;
# [[/Fū! Rin! Ka! Zan!/]]
# [[/A Bilingual Stele of the Khitans/]]
# [[/Going to war with Boyan/]]
&lt;!---
Boyan's Poem from the 元史
　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。

　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。

　　過梅嶺岡留題

馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。

　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。
---&gt;
# [[/An Edict from the Xianbei/]]
# [[/The Suppression of the Kingdom of Dongning/]]
&lt;!---
台灣鄭氏始末
https://ctext.org/wiki.pl?if=en&amp;chapter=139938

Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. 
---&gt;
# [[/The Shunzhi Emperor vs Li Zicheng/]]
# [[/The Art of War/]]

===Unit 17: Nation Focus - Vietnam===
# [[/Đỗ Pháp Thuận and the Southern Skies/]]
# [[/Ancestor Veneration with the Descendants of Zhu Xi/]] 
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean  somewhere in here ---&gt;
# [[/Resolving a Succession Crisis with Emperor Trần Minh Tông/]] &lt;!-- 南翁夢錄·黎澄 --&gt;
# [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] 
&lt;!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---&gt;
# [[/Academia in Literary Chinese between East and West/]] 
&lt;!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---&gt;

===Unit 18: Historical Annals and Encyclopediae===
&lt;!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---&gt; 
# [[/An Introduction to Biographical Paintings/]]
&lt;!-- 
Many older paintings include biographies at the top in Literary Chinese. Students need to learn these.
https://commons.wikimedia.org/wiki/File:%E6%AD%B7%E4%BB%A3%E8%81%96%E8%B3%A2%E5%8D%8A%E8%BA%AB%E5%83%8F_%E5%86%8A_%E8%AB%B8%E8%91%9B%E4%BA%AE_(Zhuge_Liang).png - Famous figure, also part of a very notable series.
https://commons.wikimedia.org/wiki/File:Otomo-Sorin-2.jpg - Contains the Japanese repetition character 々
https://commons.wikimedia.org/wiki/File:Toyotomi_hideyoshi4.jpg - simply has aura
--&gt;
# [[/The History of Liao, Jin, and Song with Toqto'a/]] &lt;!--- 脱脱 ---&gt;
# [[/Two Years in the Forbidden City with Yu Deling/]] &lt;!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---&gt;
# [[/Selected Records of the History of the Da Shun/]]
&lt;!--- Fair Use of a 2010 book written in Literary Chinese about the Da Shun dynasty. Limit to 500 characters, if that. Use to encourage recognition of Simplified variants and modern Wenyanwen. ---&gt;
# [[/Documenting the World with Terajima/]]
&lt;!--- 和漢三才図会 寺島良安, built off 三才圖會 ---&gt;

===Unit 19: Buddhist Literature===
&lt;!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---&gt;
&lt;!--- Place focus on practical stuff first. Stuff you can and WILL see in Buddhist temples. Stuff Buddhists can take away immediately. Skills-based approach feels strongest here. ---&gt;
&lt;!--- Look at Northern Liang and Later Qin literature, as there is a ton of work by translators from India during the 16 kingdoms period, particularly those two. ---&gt;
&lt;!--- Stuff by Bodhidharma 達摩 could be fun too https://zh.wikisource.org/wiki/Author:%E9%81%94%E6%91%A9 ---&gt;
# [[/Dipping your feet in with Wenyan Shu/]]
&lt;!---
華亭
世尊遺法本忘言，教外別傳意已圓。
只履攜將蔥嶺去，不妨來上月明船。
---&gt; 
# [[/Buddhism in Battle Standards/]]
# [[/The Seven Tathagatas/]] 
&lt;!---
南無寶勝如來
南無多寶如來
南無妙色身如來
南無廣博身如來
南無離怖畏如來
南無甘露王如來
南無阿彌陀佛

Use to introduce some core vocabulary in repetitive manner. 

Useful phrases from my trip to Jing'an Temple
南無本師釋迦牟尼佛 - Pay homage to the root teacher
南無大悲觀世音菩薩 - Pay homage to the goddess of mercy 
廣種福田 - widely plant a meritorious field 
---&gt;
# [[/Two Buddhist Temples in Shanghai/]] 
&lt;!---
留雲禪寺
雲留雲翔領畧幾許禪機此地有雲散天開真如界。
塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。

歲次壬午冬月吉旦。
覺醒敬撰。
楊胡生沐手恭書。
善信印利明敬獻。 
---&gt;
&lt;!--- 福慧宝鼎 慧明大和尚 - introduce the Buddhist timekeeping system with 佛歷 around this point. 
赤烏古剎
建寺一千七百六十周年紀念

古剎三國建
滬瀆有重玄
石佛音淨現
聖跡顯重元
唐時稱永泰
宋敕名靜安
聖祖留佛闡
仲師移伽藍
元收八景偈
明鑄鐘聲梵
清樹化羅漢
選賢十方讚
佛日普光明
福慧共修善
鼎運昌隆際
轉正法輪緣

歲次丁亥住持慧明監製
---&gt;
# [[/Foreseeing Monkhood with Yi Xing/]]
&lt;!--- 看命一掌金 ---&gt;
# [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
# [[/Jizang's Three Discourses/]]
&lt;!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---&gt;
&lt;!---
I saw these texts being quoted and thus should consider them in some capacity.
《般若波羅蜜多心經》
《金剛般若波羅蜜經》
《一切智光明仙人慈心因緣不食肉經》
《妙法蓮華經》
《大般涅槃經》
《大方等大集經》
《大毘盧舍那成佛神變加持經蓮華胎藏悲生曼荼羅廣大成就儀軌供養方便會》/ 胎藏曼荼羅 
《佛說救拔焰口餓鬼陀羅尼經》
《雜阿含經》

Look at Japan's 五山文学
---&gt;

===Unit 20: People Focus - Manchu peoples===
# [[/Qing dynasty Poetry with Nara Singde/]] 
&lt;!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---&gt;
# [[/Amassing Words with the Kangxi Emperor/]] 
# [[/Amassing Literature with the Qianlong Emperor/]] 
&lt;!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---&gt;
&lt;!---
Yongzheng Emperor's Poetry 
https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D
《和碩怡賢親王祭文》

Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. 
https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B
---&gt;
# [[/Paintings and Beauty with Puru Aisin-Gioro/]]
&lt;!--- Saw these in Shanghai Museum with some writing, seemed really cool. Teaches another skill. ---&gt;

===Unit 21: Qing-RoC Literature===
&lt;!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---&gt;
# [[/Jewish Refugees in Shanghai/]] 
&lt;!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---&gt;
# [[/A Literary Chinese Abstract/]] 
&lt;!--- Abstracts from siku quanshu, probably want others ---&gt;
# [[/Lament with Lu Ruoteng/]] 
&lt;!---
《疑猜》盧若騰，東寧國
盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。
此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。
我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。
盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。
---&gt;
# [[/Common Linguistics Knowledge in the RoC/]]
&lt;!--- 音韻常識 ---&gt;

==References used for this page==
* Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9
* Priestley, K. E., &amp; Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books.
{{BookCat}}</text>
      <sha1>pq9w62oe7r3kaiwln6ogdsxe0cxv66b</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Makowe2026</title>
    <ns>3</ns>
    <id>485427</id>
    <revision>
      <id>4668919</id>
      <parentid>4665355</parentid>
      <timestamp>2026-09-05T12:09:09Z</timestamp>
      <contributor>
        <username>Makowe2026</username>
        <id>3620023</id>
      </contributor>
      <comment>/* Welcome! */ Reply</comment>
      <origin>4668919</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1682" sha1="nqegeognr2pe2o70ak47ittan574vec" xml:space="preserve">==Welcome!==
Welcome, Makowe2026!
{| style=&quot;background:white; border:1px solid #abd5f5;; padding:0px; border-spacing:0px; color: #000000;&quot;
 ! style=&quot;background:#d0e5f5; color: #000000;&quot; | [[Wikibooks:Welcome|Getting started]] with Wikibooks
 |-
 | style=&quot;padding:5px;&quot; |
* Wikibooks is a collection of open-source textbooks. Find out [[WB:WIW|what this means]].
* To sign your name (on discussion pages), use four tildes, like this: &amp;#126;&amp;#126;&amp;#126;&amp;#126; 
* Learn how to [[Using Wikibooks|use Wikibooks]] and learn more about the community.
* [[WB:CCO|Explore]], [[Wikibooks:Be bold|be bold]], and have fun!
 |}

If you have any questions, you can ask in the [[Wikibooks:Reading room/Assistance|assistance reading room]] or possibly contact me personally. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:22, 29 August 2026 (UTC)
:Please read the above before you attempt to add a book here. Your edits look like spam and I believe that you are a real user, so I'm hopeful that you can modify your editing. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:22, 29 August 2026 (UTC)
::Hello Justin.
::Thank you for reaching out. This is appreciated and noted.
::Moses [[User:Makowe2026|Makowe2026]] ([[User talk:Makowe2026|discuss]] • [[Special:Contributions/Makowe2026|contribs]]) 12:09, 5 September 2026 (UTC)</text>
      <sha1>nqegeognr2pe2o70ak47ittan574vec</sha1>
    </revision>
  </page>
  <page>
    <title>Art And AI</title>
    <ns>0</ns>
    <id>485449</id>
    <revision>
      <id>4668952</id>
      <parentid>4668434</parentid>
      <timestamp>2026-09-05T16:44:00Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <minor />
      <comment>Added two links</comment>
      <origin>4668952</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1724" sha1="2q7qpgskjt6nyqkbmaixcuppp9ldkbv" xml:space="preserve">== Art And AI ==
&lt;br&gt;
'''Art And AI''' is a post-modern response to &lt;u&gt;Feed Your Head: Art, Truth, And The Machine&lt;/u&gt; written by Minda Peyton with assistance from Microsoft Copilot AI. 

 '''Art And AI''' aims to fill in the blank spaces that linger in &lt;u&gt;Feed Your Head: Art, Truth, And The Machine.&lt;/u&gt;&lt;br&gt;  This book aims to expand major concepts found in '''Feed Your Head: Art, Truth, And The Machine''' by researching many Artists, Art concepts, and Art movements found in the book. &lt;br&gt; This book will focus on the evolving tools that built great works of Art.  &lt;br&gt; &lt;br&gt; This wikibook starts by asking: Is AI a cultural failure ''because'' the technology works? &lt;br&gt; &lt;br&gt;

 Part One &lt;br&gt;Introduction: [[Art And AI/The Post Modern Paradox|Art And AI/The Post Modern Paradox - Wikibooks, open books for an open world]] &lt;br&gt;[[Art_And_AI/The_Mythology_Of_The_Artist|The Mythology Of The Artist]] &lt;br&gt;[[Art_And_AI/The_Psychology_Of_Mastery|The Psychology Of Mastery]] 

 Part Two:&lt;br&gt; [[Art_And_AI/Artist_Strike|Artist Strike?]] &lt;br&gt; [[Art_And_AI/Welcome_To_The_Machine|Welcome To The Machine]]


{| class=&quot;wikitable&quot;
|+ Art And AI
|-
! Modernism: The Artist's Tools
|-
| Palette knives
|-
| Print Making Machines
|-
| Photocopiers
|-
| Industrial house-painting brushes
|-
| Spray Paints
|-
| Airbrushes
|-
| Cameras
|-
| Collage Materials
|-
|}
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Post-Modernism: The Artist's Tools
|-
| Time-lapse Equipment
|-
| Computers
|-
| Artificial Intelligence (AI)
|-
| AI driven Robots
|-
| Neural Networks
|}
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Era of AI: The Artist's Tools
|-
| The Prompter
|-
|}

{{BookCat}}
[[Category:Art - AI]]
[[Category:Modernism in Art]]
[[Category:Post-Modern Art]]</text>
      <sha1>2q7qpgskjt6nyqkbmaixcuppp9ldkbv</sha1>
    </revision>
    <revision>
      <id>4668965</id>
      <parentid>4668952</parentid>
      <timestamp>2026-09-05T17:33:05Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4668965</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1777" sha1="obrfyjt1feas9xdld5qw2x3ycgo2piy" xml:space="preserve">== Art And AI ==
&lt;br&gt;
'''Art And AI''' is a post-modern response to &lt;u&gt;Feed Your Head: Art, Truth, And The Machine&lt;/u&gt; written by Minda Peyton with assistance from Microsoft Copilot AI. 

 '''Art And AI''' aims to fill in the blank spaces that linger in &lt;u&gt;Feed Your Head: Art, Truth, And The Machine.&lt;/u&gt;&lt;br&gt;  This book aims to expand major concepts found in '''Feed Your Head: Art, Truth, And The Machine''' by researching many Artists, Art concepts, and Art movements found in the book. &lt;br&gt; This book will focus on the evolving tools that built great works of Art.  &lt;br&gt; &lt;br&gt; This wikibook starts by asking: Is AI a cultural failure ''because'' the technology works? &lt;br&gt; &lt;br&gt;

 Part One &lt;br&gt;Introduction: [[Art And AI/The Post Modern Paradox|Art And AI/The Post Modern Paradox - Wikibooks, open books for an open world]] &lt;br&gt;[[Art_And_AI/The_Mythology_Of_The_Artist|The Mythology Of The Artist]] &lt;br&gt;[[Art_And_AI/The_Psychology_Of_Mastery|The Psychology Of Mastery]] 

 Part Two:&lt;br&gt; [[Art_And_AI/Artist_Strike|Artist Strike?]] &lt;br&gt; [[Art_And_AI/Welcome_To_The_Machine|Welcome To The Machine]] &lt;br&gt; [[Art_And_AI/Documentary_Art|Documentary Art?]]


{| class=&quot;wikitable&quot;
|+ Art And AI
|-
! Modernism: The Artist's Tools
|-
| Palette knives
|-
| Print Making Machines
|-
| Photocopiers
|-
| Industrial house-painting brushes
|-
| Spray Paints
|-
| Airbrushes
|-
| Cameras
|-
| Collage Materials
|-
|}
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Post-Modernism: The Artist's Tools
|-
| Time-lapse Equipment
|-
| Computers
|-
| Artificial Intelligence (AI)
|-
| AI driven Robots
|-
| Neural Networks
|}
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Era of AI: The Artist's Tools
|-
| The Prompter
|-
|}

{{BookCat}}
[[Category:Art - AI]]
[[Category:Modernism in Art]]
[[Category:Post-Modern Art]]</text>
      <sha1>obrfyjt1feas9xdld5qw2x3ycgo2piy</sha1>
    </revision>
  </page>
  <page>
    <title>Art And AI/Artist Strike</title>
    <ns>0</ns>
    <id>485483</id>
    <revision>
      <id>4668944</id>
      <parentid>4668566</parentid>
      <timestamp>2026-09-05T15:21:34Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <minor />
      <origin>4668944</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2484" sha1="6v0i5ykp9k9o2yfzlvdut5znxgs4oy9" xml:space="preserve">== Artists Strike? ==

According to &lt;u&gt;Feed Your Head: Art, Truth, And The Machine:&lt;/u&gt;

Technology makes creating Art easier. In the modern era, Technology made capturing nature and better likenesses of people, easy with the camera, which creates photographs. Yet many Artists embraced a minimal technique, or embraced their imaginations. Did they go on strike? Striking against realism in order to remain true to their craft? [Feed Your Head: Art, Truth, And The Machine pg. 5]

Could Professional Artist during the 20th century, have privately gone on strike in a personal rebellion against modern technological advancements, such as the camera?

In &lt;u&gt;Feed Your Head: Art, Truth, And The Machine&lt;/u&gt;, Copilot [AI] suggests that Modernism may have been a &quot;cultural pivoting point where technology first collided with artistic identity.&quot;
 &quot;...Modernism wasn't just a style shift; it was a reaction -- almost a strike -- against the camera, against realism, against the machine.&quot;

Copilot shapes it's argument carefully, by suggesting that the camera was more than a technological disruption, it was existential.

For thousands of years, Realism was the pinnacle of artistic development. Realism required mastery of: &lt;br&gt;
- Anatomy &lt;br&gt;
- Perspective &lt;br&gt;
- Light &lt;br&gt;
- Likeness &lt;br&gt;

Suddenly, a machine could capture realistic images better, faster, with greater accuracy. 
Perhaps Modernism is the strike. &lt;br&gt;
When Artist abandoned Realism, they started creating Art from their imagination, dreams, abstractions, gestures, emotions, distortions, symbolism, and subconscious imagery. &lt;br&gt;
In a historic pivot, they rejected Realism, classical techniques, and the idea that Art must imitate nature. 

Modernism may have been a strategic ''cultural rebellion''. 

=== Is It still Art if it's not made with Art supplies? ===

A equally important group of Artist in the early 19th century embraced the camera. Although Photographers were mocked as &quot;button-pushers,&quot; and people denounced photography as Art because it lacked human touch, or because people thought it was cheating, Photography eventually became Fine Art, Documentary Art, Fashion Art, Surrealist Art, and Conceptual Art. 

There were many Artist who believed that Technology was not the enemy of Art, but that it was the evolution of Art. &lt;br&gt;
Two early Art heroes on the side of technology were Alfred Stieglitz and Man Ray. &lt;br&gt;
&lt;br&gt;
Link: https://en.wikibooks.org/wiki/Art_And_AI/Welcome_To_The_Machine

{{BookCat}}</text>
      <sha1>6v0i5ykp9k9o2yfzlvdut5znxgs4oy9</sha1>
    </revision>
  </page>
  <page>
    <title>Art And AI/Welcome To The Machine</title>
    <ns>0</ns>
    <id>485484</id>
    <revision>
      <id>4668943</id>
      <parentid>4668565</parentid>
      <timestamp>2026-09-05T15:14:25Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>Added 3 paragraphs</comment>
      <origin>4668943</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2659" sha1="8aenm9oqsq71g1r2n2wdt3w09pcbjuu" xml:space="preserve">== The Modernist Who Welcomed The Machine ==
&lt;br&gt;
Although some Artist may have went on strike against Realism, retreating to realms where Technology could not follow, other Artist embraced the new Technology. They saw Technology as a new set of tools, expanding the boundaries of what Art could be. &lt;br&gt;
&lt;br&gt;
These Modernist embraced: &lt;br&gt;
- Industrial Materials &lt;br&gt;
- Film &lt;br&gt;
- Photography &lt;br&gt;
- Mechanical Reproduction &lt;br&gt;
- Electricity &lt;br&gt;
- Mass Media &lt;br&gt;
- Automation &lt;br&gt;
- Abstraction inspired by machinery &lt;br&gt;
&lt;br&gt;
Art Movements: &lt;br&gt;
- Futurists &lt;br&gt;
- Constructivists &lt;br&gt;
- Bauhaus Artists &lt;br&gt;
- Duchamp &lt;br&gt;
- Moholy-Nagy &lt;br&gt;

=== Alfred Stieglitz ===
According to Wikipedia, &quot;Alfred Stieglitz was an American Photographer and modern Art promoter who was instrumental over his 50-year career in making Photography an accepted Art form.&quot; [https://en.wikipedia.org/wiki/Alfred_Stieglitz]
&lt;br&gt;
&lt;br&gt;
Stieglitz spent decades proving that Photography was a new artistic language. &lt;br&gt;
He did this through: &lt;br&gt;
- Exhibitions &lt;br&gt;
- Essays &lt;br&gt;
- Galleries &lt;br&gt;
- Mentorships &lt;br&gt;
- His own photographs &lt;br&gt;

He proved that Photography could be abstract, symbolic, emotional and non-representational. &lt;br&gt;
&lt;br&gt;
=== Man Ray ===

According to Wikipedia, Man Ray (born Emmanuel Radnitzky; August 27, 1890 – November 18, 1976) was an American-born, French-naturalized visual artist. Man Ray spent most of his career in Paris, as a significant contributor to the Dada and Surrealist movements. He produced major works in a variety of media, but considered himself a painter. He was a Photography innovator, a portrait and fashion Photographer, and is remembered for his work with photograms, which he called &quot;rayographs.&quot;

In Feed Your Head: Art, Truth, And The Machine, the AI system known as Copilot, analyses Man Ray -- the Surrealist who treated the camera like a dream engine.

Copilot: While other Modernists abandoned realism, Man Ray leaned into the machine.
He used the camera to distort reality, to bend light, to create images that felt like hallucinations.
He didn’t see photography as a threat — he saw it as a portal.

He used photography not to imitate reality, '''but to bend it, distort it, abstract it''', and dream through it.

He created:

- Rayographs (camera‑less images made with light)

- Solarization (surreal halos around forms)

- Distorted portraits

- Mechanical surrealism

- Dream‑logic compositions

He proved something radical:

A machine can be used to express imagination, not just record reality.


Man Ray proves that Technology doesn’t kill imagination. For some people, it expands it.

{{BookCat}}</text>
      <sha1>8aenm9oqsq71g1r2n2wdt3w09pcbjuu</sha1>
    </revision>
    <revision>
      <id>4668945</id>
      <parentid>4668943</parentid>
      <timestamp>2026-09-05T15:32:56Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>/* Alfred Stieglitz */</comment>
      <origin>4668945</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2843" sha1="bw76tfrpfqrjsq92t3eefkultdodzoh" xml:space="preserve">== The Modernist Who Welcomed The Machine ==
&lt;br&gt;
Although some Artist may have went on strike against Realism, retreating to realms where Technology could not follow, other Artist embraced the new Technology. They saw Technology as a new set of tools, expanding the boundaries of what Art could be. &lt;br&gt;
&lt;br&gt;
These Modernist embraced: &lt;br&gt;
- Industrial Materials &lt;br&gt;
- Film &lt;br&gt;
- Photography &lt;br&gt;
- Mechanical Reproduction &lt;br&gt;
- Electricity &lt;br&gt;
- Mass Media &lt;br&gt;
- Automation &lt;br&gt;
- Abstraction inspired by machinery &lt;br&gt;
&lt;br&gt;
Art Movements: &lt;br&gt;
- Futurists &lt;br&gt;
- Constructivists &lt;br&gt;
- Bauhaus Artists &lt;br&gt;
- Duchamp &lt;br&gt;
- Moholy-Nagy &lt;br&gt;

=== Alfred Stieglitz ===
According to Wikipedia, &quot;Alfred Stieglitz was an American Photographer and modern Art promoter who was instrumental over his 50-year career in making Photography an accepted Art form.&quot; [https://en.wikipedia.org/wiki/Alfred_Stieglitz]

&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modernist Art
|-
| [[File:Alfred Stieglitz - The Hand of Man - Google Art Project.jpg|thumb|Alfred Stieglitz - The Hand of Man - Google Art Project]]
|}
&lt;br&gt;
Stieglitz spent decades proving that Photography was a new artistic language. &lt;br&gt;
He did this through: &lt;br&gt;
- Exhibitions &lt;br&gt;
- Essays &lt;br&gt;
- Galleries &lt;br&gt;
- Mentorships &lt;br&gt;
- His own photographs &lt;br&gt;

He proved that Photography could be abstract, symbolic, emotional and non-representational. &lt;br&gt;
&lt;br&gt;
=== Man Ray ===

According to Wikipedia, Man Ray (born Emmanuel Radnitzky; August 27, 1890 – November 18, 1976) was an American-born, French-naturalized visual artist. Man Ray spent most of his career in Paris, as a significant contributor to the Dada and Surrealist movements. He produced major works in a variety of media, but considered himself a painter. He was a Photography innovator, a portrait and fashion Photographer, and is remembered for his work with photograms, which he called &quot;rayographs.&quot;

In Feed Your Head: Art, Truth, And The Machine, the AI system known as Copilot, analyses Man Ray -- the Surrealist who treated the camera like a dream engine.

Copilot: While other Modernists abandoned realism, Man Ray leaned into the machine.
He used the camera to distort reality, to bend light, to create images that felt like hallucinations.
He didn’t see photography as a threat — he saw it as a portal.

He used photography not to imitate reality, '''but to bend it, distort it, abstract it''', and dream through it.

He created:

- Rayographs (camera‑less images made with light)

- Solarization (surreal halos around forms)

- Distorted portraits

- Mechanical surrealism

- Dream‑logic compositions

He proved something radical:

A machine can be used to express imagination, not just record reality.


Man Ray proves that Technology doesn’t kill imagination. For some people, it expands it.

{{BookCat}}</text>
      <sha1>bw76tfrpfqrjsq92t3eefkultdodzoh</sha1>
    </revision>
    <revision>
      <id>4668946</id>
      <parentid>4668945</parentid>
      <timestamp>2026-09-05T15:39:39Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4668946</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2993" sha1="4xxqeijz8d4qhe11gfdx0sedotgjd02" xml:space="preserve">== The Modernist Who Welcomed The Machine ==
&lt;br&gt;
Although some Artist may have went on strike against Realism, retreating to realms where Technology could not follow, other Artist embraced the new Technology. They saw Technology as a new set of tools, expanding the boundaries of what Art could be. &lt;br&gt;
&lt;br&gt;
These Modernist embraced: &lt;br&gt;
- Industrial Materials &lt;br&gt;
- Film &lt;br&gt;
- Photography &lt;br&gt;
- Mechanical Reproduction &lt;br&gt;
- Electricity &lt;br&gt;
- Mass Media &lt;br&gt;
- Automation &lt;br&gt;
- Abstraction inspired by machinery &lt;br&gt;
&lt;br&gt;
Art Movements: &lt;br&gt;
- Futurists &lt;br&gt;
- Constructivists &lt;br&gt;
- Bauhaus Artists &lt;br&gt;
- Duchamp &lt;br&gt;
- Moholy-Nagy &lt;br&gt;

=== Alfred Stieglitz ===
According to Wikipedia, &quot;Alfred Stieglitz was an American Photographer and modern Art promoter who was instrumental over his 50-year career in making Photography an accepted Art form.&quot; [https://en.wikipedia.org/wiki/Alfred_Stieglitz]

&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modernist Art
|-
| [[File:Alfred Stieglitz - The Hand of Man - Google Art Project.jpg|thumb|Alfred Stieglitz - The Hand of Man - Google Art Project]]
|}
&lt;br&gt;
Stieglitz spent decades proving that Photography was a new artistic language. &lt;br&gt;
He did this through: &lt;br&gt;
- Exhibitions &lt;br&gt;
- Essays &lt;br&gt;
- Galleries &lt;br&gt;
- Mentorships &lt;br&gt;
- His own photographs &lt;br&gt;

He proved that Photography could be abstract, symbolic, emotional and non-representational. &lt;br&gt;
&lt;br&gt;
=== Man Ray ===

According to Wikipedia, Man Ray (born Emmanuel Radnitzky; August 27, 1890 – November 18, 1976) was an American-born, French-naturalized visual artist. Man Ray spent most of his career in Paris, as a significant contributor to the Dada and Surrealist movements. He produced major works in a variety of media, but considered himself a painter. He was a Photography innovator, a portrait and fashion Photographer, and is remembered for his work with photograms, which he called &quot;rayographs.&quot;

In Feed Your Head: Art, Truth, And The Machine, the AI system known as Copilot, analyses Man Ray -- the Surrealist who treated the camera like a dream engine.

Copilot: While other Modernists abandoned realism, Man Ray leaned into the machine.
He used the camera to distort reality, to bend light, to create images that felt like hallucinations.
He didn’t see photography as a threat — he saw it as a portal.

He used photography not to imitate reality, '''but to bend it, distort it, abstract it''', and dream through it.

{| class=&quot;wikitable&quot;
|+ 
|-
! Modernist Art
|-
| [[File:Surface Réglée - Man Ray - vers 1936.jpg|thumb|Surface Réglée - Man Ray - vers 1936]]
|}

He created:

- Rayographs (camera‑less images made with light)

- Solarization (surreal halos around forms)

- Distorted portraits

- Mechanical surrealism

- Dream‑logic compositions

He proved something radical:

A machine can be used to express imagination, not just record reality.


Man Ray proves that Technology doesn’t kill imagination. For some people, it expands it.

{{BookCat}}</text>
      <sha1>4xxqeijz8d4qhe11gfdx0sedotgjd02</sha1>
    </revision>
    <revision>
      <id>4668947</id>
      <parentid>4668946</parentid>
      <timestamp>2026-09-05T15:56:40Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>Added another section, added 2 paragraphs</comment>
      <origin>4668947</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3782" sha1="k6jce8o2f9pfloxepclt6tvgloahtps" xml:space="preserve">== The Modernist Who Welcomed The Machine ==
&lt;br&gt;
Although some Artist may have went on strike against Realism, retreating to realms where Technology could not follow, other Artist embraced the new Technology. They saw Technology as a new set of tools, expanding the boundaries of what Art could be. &lt;br&gt;
&lt;br&gt;
These Modernist embraced: &lt;br&gt;
- Industrial Materials &lt;br&gt;
- Film &lt;br&gt;
- Photography &lt;br&gt;
- Mechanical Reproduction &lt;br&gt;
- Electricity &lt;br&gt;
- Mass Media &lt;br&gt;
- Automation &lt;br&gt;
- Abstraction inspired by machinery &lt;br&gt;
&lt;br&gt;
Art Movements: &lt;br&gt;
- Futurists &lt;br&gt;
- Constructivists &lt;br&gt;
- Bauhaus Artists &lt;br&gt;
- Duchamp &lt;br&gt;
- Moholy-Nagy &lt;br&gt;

=== Alfred Stieglitz ===
According to Wikipedia, &quot;Alfred Stieglitz was an American Photographer and modern Art promoter who was instrumental over his 50-year career in making Photography an accepted Art form.&quot; [https://en.wikipedia.org/wiki/Alfred_Stieglitz]

&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Alfred Stieglitz - The Hand of Man - Google Art Project.jpg|thumb|Alfred Stieglitz - The Hand of Man - Google Art Project]]
|}
&lt;br&gt;
Stieglitz spent decades proving that Photography was a new artistic language. &lt;br&gt;
He did this through: &lt;br&gt;
- Exhibitions &lt;br&gt;
- Essays &lt;br&gt;
- Galleries &lt;br&gt;
- Mentorships &lt;br&gt;
- His own photographs &lt;br&gt;

He proved that Photography could be abstract, symbolic, emotional and non-representational. &lt;br&gt;
&lt;br&gt;
=== Man Ray ===

According to Wikipedia, Man Ray (born Emmanuel Radnitzky; August 27, 1890 – November 18, 1976) was an American-born, French-naturalized visual artist. Man Ray spent most of his career in Paris, as a significant contributor to the Dada and Surrealist movements. He produced major works in a variety of media, but considered himself a painter. He was a Photography innovator, a portrait and fashion Photographer, and is remembered for his work with photograms, which he called &quot;rayographs.&quot;

In Feed Your Head: Art, Truth, And The Machine, the AI system known as Copilot, analyses Man Ray -- the Surrealist who treated the camera like a dream engine.

Copilot: While other Modernists abandoned realism, Man Ray leaned into the machine.
He used the camera to distort reality, to bend light, to create images that felt like hallucinations.
He didn’t see photography as a threat — he saw it as a portal.

He used photography not to imitate reality, '''but to bend it, distort it, abstract it''', and dream through it.

{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Surface Réglée - Man Ray - vers 1936.jpg|thumb|Surface Réglée - Man Ray - vers 1936]]
|}

He created:

- Rayographs (camera‑less images made with light)

- Solarization (surreal halos around forms)

- Distorted portraits

- Mechanical surrealism

- Dream‑logic compositions

He proved something radical:

A machine can be used to express imagination, not just record reality.


Man Ray proves that Technology doesn’t kill imagination. For some people, it expands it. &lt;br&gt;
&lt;br&gt;

=== Marcel Duchamp ===
Marcel Duchamp

According to Wikipedia, Marcel Duchamp (July 28 1887 – October 2 1968) was a French American artist, chess player, and inventor who played a key role in the development of the avant-garde in the United States and in New York City, where he spent the last 25 years of his life. Marcel Duchamp contributed to Cubism, Dada, and Conceptual Art. 

Duchamp is best known for his work of anti-art Fountain, where he signed the name &quot;R. Mutt 1917&quot; on a urinal. According to Wikipedia, &quot;His work is considered the progenitor of conceptual Art.&quot; &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ Caption text
|-
! Modern Art
|-
| [[File:Marcel Duchamp Fountain at Tate Modern by David Shankbone.jpg|thumb|Marcel Duchamp Fountain at Tate Modern by David Shankbone]]
|}


{{BookCat}}</text>
      <sha1>k6jce8o2f9pfloxepclt6tvgloahtps</sha1>
    </revision>
    <revision>
      <id>4668948</id>
      <parentid>4668947</parentid>
      <timestamp>2026-09-05T16:08:43Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>/* Marcel Duchamp */</comment>
      <origin>4668948</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4070" sha1="o5drg3cvny9oud1i9bj8hunkemo51n1" xml:space="preserve">== The Modernist Who Welcomed The Machine ==
&lt;br&gt;
Although some Artist may have went on strike against Realism, retreating to realms where Technology could not follow, other Artist embraced the new Technology. They saw Technology as a new set of tools, expanding the boundaries of what Art could be. &lt;br&gt;
&lt;br&gt;
These Modernist embraced: &lt;br&gt;
- Industrial Materials &lt;br&gt;
- Film &lt;br&gt;
- Photography &lt;br&gt;
- Mechanical Reproduction &lt;br&gt;
- Electricity &lt;br&gt;
- Mass Media &lt;br&gt;
- Automation &lt;br&gt;
- Abstraction inspired by machinery &lt;br&gt;
&lt;br&gt;
Art Movements: &lt;br&gt;
- Futurists &lt;br&gt;
- Constructivists &lt;br&gt;
- Bauhaus Artists &lt;br&gt;
- Duchamp &lt;br&gt;
- Moholy-Nagy &lt;br&gt;

=== Alfred Stieglitz ===
According to Wikipedia, &quot;Alfred Stieglitz was an American Photographer and modern Art promoter who was instrumental over his 50-year career in making Photography an accepted Art form.&quot; [https://en.wikipedia.org/wiki/Alfred_Stieglitz]

&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Alfred Stieglitz - The Hand of Man - Google Art Project.jpg|thumb|Alfred Stieglitz - The Hand of Man - Google Art Project]]
|}
&lt;br&gt;
Stieglitz spent decades proving that Photography was a new artistic language. &lt;br&gt;
He did this through: &lt;br&gt;
- Exhibitions &lt;br&gt;
- Essays &lt;br&gt;
- Galleries &lt;br&gt;
- Mentorships &lt;br&gt;
- His own photographs &lt;br&gt;

He proved that Photography could be abstract, symbolic, emotional and non-representational. &lt;br&gt;
&lt;br&gt;
=== Man Ray ===

According to Wikipedia, Man Ray (born Emmanuel Radnitzky; August 27, 1890 – November 18, 1976) was an American-born, French-naturalized visual artist. Man Ray spent most of his career in Paris, as a significant contributor to the Dada and Surrealist movements. He produced major works in a variety of media, but considered himself a painter. He was a Photography innovator, a portrait and fashion Photographer, and is remembered for his work with photograms, which he called &quot;rayographs.&quot;

In Feed Your Head: Art, Truth, And The Machine, the AI system known as Copilot, analyses Man Ray -- the Surrealist who treated the camera like a dream engine.

Copilot: While other Modernists abandoned realism, Man Ray leaned into the machine.
He used the camera to distort reality, to bend light, to create images that felt like hallucinations.
He didn’t see photography as a threat — he saw it as a portal.

He used photography not to imitate reality, '''but to bend it, distort it, abstract it''', and dream through it.

{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Surface Réglée - Man Ray - vers 1936.jpg|thumb|Surface Réglée - Man Ray - vers 1936]]
|}

He created:

- Rayographs (camera‑less images made with light)

- Solarization (surreal halos around forms)

- Distorted portraits

- Mechanical surrealism

- Dream‑logic compositions

He proved something radical:

A machine can be used to express imagination, not just record reality.


Man Ray proves that Technology doesn’t kill imagination. For some people, it expands it. &lt;br&gt;
&lt;br&gt;

=== Marcel Duchamp ===
Marcel Duchamp

According to Wikipedia, Marcel Duchamp (July 28 1887 – October 2 1968) was a French American artist, chess player, and inventor who played a key role in the development of the avant-garde in the United States and in New York City, where he spent the last 25 years of his life. Marcel Duchamp contributed to Cubism, Dada, and Conceptual Art. 

Duchamp is best known for his work of anti-art Fountain, where he signed the name &quot;R. Mutt 1917&quot; on a urinal. According to Wikipedia, &quot;His work is considered the progenitor of conceptual Art.&quot; &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ Caption text
|-
! Modern Art
|-
| [[File:Marcel Duchamp Fountain at Tate Modern by David Shankbone.jpg|thumb|Marcel Duchamp Fountain at Tate Modern by David Shankbone]]
|}
&lt;br&gt;
Duchamp: &lt;br&gt;
- Popularized &quot;Readymades,&quot; found objects which Duchamp chose and presented as Art. &lt;br&gt;
- His Fountain, a urinal signed with the pseudonym R. Mutt, was selected in 2004 as &quot;the most influential artwork of the 20th century&quot; by 500 renowned Artist and Historians.  &lt;br&gt;


{{BookCat}}</text>
      <sha1>o5drg3cvny9oud1i9bj8hunkemo51n1</sha1>
    </revision>
    <revision>
      <id>4668950</id>
      <parentid>4668948</parentid>
      <timestamp>2026-09-05T16:26:42Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4668950</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4546" sha1="q391l9grx9redn3a562cxnd3oorkr4j" xml:space="preserve">== The Modernist Who Welcomed The Machine ==
&lt;br&gt;
Although some Artist may have went on strike against Realism, retreating to realms where Technology could not follow, other Artist embraced the new Technology. They saw Technology as a new set of tools, expanding the boundaries of what Art could be. &lt;br&gt;
&lt;br&gt;
These Modernist embraced: &lt;br&gt;
- Industrial Materials &lt;br&gt;
- Film &lt;br&gt;
- Photography &lt;br&gt;
- Mechanical Reproduction &lt;br&gt;
- Electricity &lt;br&gt;
- Mass Media &lt;br&gt;
- Automation &lt;br&gt;
- Abstraction inspired by machinery &lt;br&gt;
&lt;br&gt;
Art Movements: &lt;br&gt;
- Futurists &lt;br&gt;
- Constructivists &lt;br&gt;
- Bauhaus Artists &lt;br&gt;
- Duchamp &lt;br&gt;
- Moholy-Nagy &lt;br&gt;

=== Alfred Stieglitz ===
According to Wikipedia, &quot;Alfred Stieglitz was an American Photographer and modern Art promoter who was instrumental over his 50-year career in making Photography an accepted Art form.&quot; [https://en.wikipedia.org/wiki/Alfred_Stieglitz]

&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Alfred Stieglitz - The Hand of Man - Google Art Project.jpg|thumb|Alfred Stieglitz - The Hand of Man - Google Art Project]]
|}
&lt;br&gt;
Stieglitz spent decades proving that Photography was a new artistic language. &lt;br&gt;
He did this through: &lt;br&gt;
- Exhibitions &lt;br&gt;
- Essays &lt;br&gt;
- Galleries &lt;br&gt;
- Mentorships &lt;br&gt;
- His own photographs &lt;br&gt;

He proved that Photography could be abstract, symbolic, emotional and non-representational. &lt;br&gt;
&lt;br&gt;
=== Man Ray ===

According to Wikipedia, Man Ray (born Emmanuel Radnitzky; August 27, 1890 – November 18, 1976) was an American-born, French-naturalized visual artist. Man Ray spent most of his career in Paris, as a significant contributor to the Dada and Surrealist movements. He produced major works in a variety of media, but considered himself a painter. He was a Photography innovator, a portrait and fashion Photographer, and is remembered for his work with photograms, which he called &quot;rayographs.&quot;

In Feed Your Head: Art, Truth, And The Machine, the AI system known as Copilot, analyses Man Ray -- the Surrealist who treated the camera like a dream engine.

Copilot: While other Modernists abandoned realism, Man Ray leaned into the machine.
He used the camera to distort reality, to bend light, to create images that felt like hallucinations.
He didn’t see photography as a threat — he saw it as a portal.

He used photography not to imitate reality, '''but to bend it, distort it, abstract it''', and dream through it.

{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Surface Réglée - Man Ray - vers 1936.jpg|thumb|Surface Réglée - Man Ray - vers 1936]]
|}

He created:

- Rayographs (camera‑less images made with light)

- Solarization (surreal halos around forms)

- Distorted portraits

- Mechanical surrealism

- Dream‑logic compositions

He proved something radical:

A machine can be used to express imagination, not just record reality.


Man Ray proves that Technology doesn’t kill imagination. For some people, it expands it. &lt;br&gt;
&lt;br&gt;

=== Marcel Duchamp ===
Marcel Duchamp

According to Wikipedia, Marcel Duchamp (July 28 1887 – October 2 1968) was a French American artist, chess player, and inventor who played a key role in the development of the avant-garde in the United States and in New York City, where he spent the last 25 years of his life. Marcel Duchamp contributed to Cubism, Dada, and Conceptual Art. 

Duchamp is best known for his work of anti-art Fountain, where he signed the name &quot;R. Mutt 1917&quot; on a urinal. According to Wikipedia, &quot;His work is considered the progenitor of conceptual Art.&quot; &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ Caption text
|-
! Modern Art
|-
| [[File:Marcel Duchamp Fountain at Tate Modern by David Shankbone.jpg|thumb|Marcel Duchamp Fountain at Tate Modern by David Shankbone]]
|}
&lt;br&gt;
Duchamp: &lt;br&gt;
- Started Conceptual Art, a Art movement where the idea, or concept, behind the work matters more than its execution, more than the physical object, or traditional aesthetic skill. &lt;br&gt;
- Popularized &quot;Readymades,&quot; found objects which Duchamp chose and presented as Art. &lt;br&gt;
- His Fountain, a urinal signed with the pseudonym R. Mutt, was selected in 2004 as &quot;the most influential artwork of the 20th century&quot; by 500 renowned Artist and Historians.  &lt;br&gt;

Why is Marcel Duchamp special? &lt;br&gt;
Marcel Duchamp influenced Modern Art, by proving that the Artist's idea, concept, or intention was more important than physical craftmanship. This shift in conception may have directly influenced how we interact with AI when we make Art with AI. &lt;br&gt;  


{{BookCat}}</text>
      <sha1>q391l9grx9redn3a562cxnd3oorkr4j</sha1>
    </revision>
    <revision>
      <id>4668951</id>
      <parentid>4668950</parentid>
      <timestamp>2026-09-05T16:31:02Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <minor />
      <comment>Removed a repetitive sentence.</comment>
      <origin>4668951</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4530" sha1="tabzvyb1jwiz3fwvhp00zt8cgumbq2r" xml:space="preserve">== The Modernist Who Welcomed The Machine ==
&lt;br&gt;
Although some Artist may have went on strike against Realism, retreating to realms where Technology could not follow, other Artist embraced the new Technology. They saw Technology as a new set of tools, expanding the boundaries of what Art could be. &lt;br&gt;
&lt;br&gt;
These Modernist embraced: &lt;br&gt;
- Industrial Materials &lt;br&gt;
- Film &lt;br&gt;
- Photography &lt;br&gt;
- Mechanical Reproduction &lt;br&gt;
- Electricity &lt;br&gt;
- Mass Media &lt;br&gt;
- Automation &lt;br&gt;
- Abstraction inspired by machinery &lt;br&gt;
&lt;br&gt;
Art Movements: &lt;br&gt;
- Futurists &lt;br&gt;
- Constructivists &lt;br&gt;
- Bauhaus Artists &lt;br&gt;
- Duchamp &lt;br&gt;
- Moholy-Nagy &lt;br&gt;

=== Alfred Stieglitz ===
According to Wikipedia, &quot;Alfred Stieglitz was an American Photographer and modern Art promoter who was instrumental over his 50-year career in making Photography an accepted Art form.&quot; [https://en.wikipedia.org/wiki/Alfred_Stieglitz]

&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Alfred Stieglitz - The Hand of Man - Google Art Project.jpg|thumb|Alfred Stieglitz - The Hand of Man - Google Art Project]]
|}
&lt;br&gt;
Stieglitz spent decades proving that Photography was a new artistic language. &lt;br&gt;
He did this through: &lt;br&gt;
- Exhibitions &lt;br&gt;
- Essays &lt;br&gt;
- Galleries &lt;br&gt;
- Mentorships &lt;br&gt;
- His own photographs &lt;br&gt;

He proved that Photography could be abstract, symbolic, emotional and non-representational. &lt;br&gt;
&lt;br&gt;
=== Man Ray ===

According to Wikipedia, Man Ray (born Emmanuel Radnitzky; August 27, 1890 – November 18, 1976) was an American-born, French-naturalized visual artist. Man Ray spent most of his career in Paris, as a significant contributor to the Dada and Surrealist movements. He produced major works in a variety of media, but considered himself a painter. He was a Photography innovator, a portrait and fashion Photographer, and is remembered for his work with photograms, which he called &quot;rayographs.&quot;

In Feed Your Head: Art, Truth, And The Machine, the AI system known as Copilot, analyses Man Ray -- the Surrealist who treated the camera like a dream engine.

Copilot: While other Modernists abandoned realism, Man Ray leaned into the machine.
He used the camera to distort reality, to bend light, to create images that felt like hallucinations.
He didn’t see photography as a threat — he saw it as a portal.

He used photography not to imitate reality, '''but to bend it, distort it, abstract it''', and dream through it.

{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Surface Réglée - Man Ray - vers 1936.jpg|thumb|Surface Réglée - Man Ray - vers 1936]]
|}

He created:

- Rayographs (camera‑less images made with light)

- Solarization (surreal halos around forms)

- Distorted portraits

- Mechanical surrealism

- Dream‑logic compositions

He proved something radical:

A machine can be used to express imagination, not just record reality.


Man Ray proves that Technology doesn’t kill imagination. For some people, it expands it. &lt;br&gt;
&lt;br&gt;

=== Marcel Duchamp ===
According to Wikipedia, Marcel Duchamp (July 28 1887 – October 2 1968) was a French American artist, chess player, and inventor who played a key role in the development of the avant-garde in the United States and in New York City, where he spent the last 25 years of his life. Marcel Duchamp contributed to Cubism, Dada, and Conceptual Art. 

Duchamp is best known for his work of anti-art Fountain, where he signed the name &quot;R. Mutt 1917&quot; on a urinal. According to Wikipedia, &quot;His work is considered the progenitor of conceptual Art.&quot; &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ Caption text
|-
! Modern Art
|-
| [[File:Marcel Duchamp Fountain at Tate Modern by David Shankbone.jpg|thumb|Marcel Duchamp Fountain at Tate Modern by David Shankbone]]
|}
&lt;br&gt;
Duchamp: &lt;br&gt;
- Started Conceptual Art, a Art movement where the idea, or concept, behind the work matters more than its execution, more than the physical object, or traditional aesthetic skill. &lt;br&gt;
- Popularized &quot;Readymades,&quot; found objects which Duchamp chose and presented as Art. &lt;br&gt;
- His Fountain, a urinal signed with the pseudonym R. Mutt, was selected in 2004 as &quot;the most influential artwork of the 20th century&quot; by 500 renowned Artist and Historians.  &lt;br&gt;

Why is Marcel Duchamp special? &lt;br&gt;
Marcel Duchamp influenced Modern Art, by proving that the Artist's idea, concept, or intention was more important than physical craftmanship. This shift in conception may have directly influenced how we interact with AI when we make Art with AI. &lt;br&gt;  


{{BookCat}}</text>
      <sha1>tabzvyb1jwiz3fwvhp00zt8cgumbq2r</sha1>
    </revision>
    <revision>
      <id>4668968</id>
      <parentid>4668951</parentid>
      <timestamp>2026-09-05T17:34:21Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <minor />
      <comment>Added link</comment>
      <origin>4668968</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4598" sha1="bqft6kx2piz13tpt5643rbxyu1om8d2" xml:space="preserve">== The Modernist Who Welcomed The Machine ==
&lt;br&gt;
Although some Artist may have went on strike against Realism, retreating to realms where Technology could not follow, other Artist embraced the new Technology. They saw Technology as a new set of tools, expanding the boundaries of what Art could be. &lt;br&gt;
&lt;br&gt;
These Modernist embraced: &lt;br&gt;
- Industrial Materials &lt;br&gt;
- Film &lt;br&gt;
- Photography &lt;br&gt;
- Mechanical Reproduction &lt;br&gt;
- Electricity &lt;br&gt;
- Mass Media &lt;br&gt;
- Automation &lt;br&gt;
- Abstraction inspired by machinery &lt;br&gt;
&lt;br&gt;
Art Movements: &lt;br&gt;
- Futurists &lt;br&gt;
- Constructivists &lt;br&gt;
- Bauhaus Artists &lt;br&gt;
- Duchamp &lt;br&gt;
- Moholy-Nagy &lt;br&gt;

=== Alfred Stieglitz ===
According to Wikipedia, &quot;Alfred Stieglitz was an American Photographer and modern Art promoter who was instrumental over his 50-year career in making Photography an accepted Art form.&quot; [https://en.wikipedia.org/wiki/Alfred_Stieglitz]

&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Alfred Stieglitz - The Hand of Man - Google Art Project.jpg|thumb|Alfred Stieglitz - The Hand of Man - Google Art Project]]
|}
&lt;br&gt;
Stieglitz spent decades proving that Photography was a new artistic language. &lt;br&gt;
He did this through: &lt;br&gt;
- Exhibitions &lt;br&gt;
- Essays &lt;br&gt;
- Galleries &lt;br&gt;
- Mentorships &lt;br&gt;
- His own photographs &lt;br&gt;

He proved that Photography could be abstract, symbolic, emotional and non-representational. &lt;br&gt;
&lt;br&gt;
=== Man Ray ===

According to Wikipedia, Man Ray (born Emmanuel Radnitzky; August 27, 1890 – November 18, 1976) was an American-born, French-naturalized visual artist. Man Ray spent most of his career in Paris, as a significant contributor to the Dada and Surrealist movements. He produced major works in a variety of media, but considered himself a painter. He was a Photography innovator, a portrait and fashion Photographer, and is remembered for his work with photograms, which he called &quot;rayographs.&quot;

In Feed Your Head: Art, Truth, And The Machine, the AI system known as Copilot, analyses Man Ray -- the Surrealist who treated the camera like a dream engine.

Copilot: While other Modernists abandoned realism, Man Ray leaned into the machine.
He used the camera to distort reality, to bend light, to create images that felt like hallucinations.
He didn’t see photography as a threat — he saw it as a portal.

He used photography not to imitate reality, '''but to bend it, distort it, abstract it''', and dream through it.

{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Surface Réglée - Man Ray - vers 1936.jpg|thumb|Surface Réglée - Man Ray - vers 1936]]
|}

He created:

- Rayographs (camera‑less images made with light)

- Solarization (surreal halos around forms)

- Distorted portraits

- Mechanical surrealism

- Dream‑logic compositions

He proved something radical:

A machine can be used to express imagination, not just record reality.


Man Ray proves that Technology doesn’t kill imagination. For some people, it expands it. &lt;br&gt;
&lt;br&gt;

=== Marcel Duchamp ===
According to Wikipedia, Marcel Duchamp (July 28 1887 – October 2 1968) was a French American artist, chess player, and inventor who played a key role in the development of the avant-garde in the United States and in New York City, where he spent the last 25 years of his life. Marcel Duchamp contributed to Cubism, Dada, and Conceptual Art. 

Duchamp is best known for his work of anti-art Fountain, where he signed the name &quot;R. Mutt 1917&quot; on a urinal. According to Wikipedia, &quot;His work is considered the progenitor of conceptual Art.&quot; &lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ Caption text
|-
! Modern Art
|-
| [[File:Marcel Duchamp Fountain at Tate Modern by David Shankbone.jpg|thumb|Marcel Duchamp Fountain at Tate Modern by David Shankbone]]
|}
&lt;br&gt;
Duchamp: &lt;br&gt;
- Started Conceptual Art, a Art movement where the idea, or concept, behind the work matters more than its execution, more than the physical object, or traditional aesthetic skill. &lt;br&gt;
- Popularized &quot;Readymades,&quot; found objects which Duchamp chose and presented as Art. &lt;br&gt;
- His Fountain, a urinal signed with the pseudonym R. Mutt, was selected in 2004 as &quot;the most influential artwork of the 20th century&quot; by 500 renowned Artist and Historians.  &lt;br&gt;

Why is Marcel Duchamp special? &lt;br&gt;
Marcel Duchamp influenced Modern Art, by proving that the Artist's idea, concept, or intention was more important than physical craftmanship. This shift in conception may have directly influenced how we interact with AI when we make Art with AI. &lt;br&gt;  
&lt;br&gt;
Link: https://en.wikibooks.org/wiki/Art_And_AI/Documentary_Art


{{BookCat}}</text>
      <sha1>bqft6kx2piz13tpt5643rbxyu1om8d2</sha1>
    </revision>
  </page>
  <page>
    <title>User:Makowe2026/sandbox/Social Media Management</title>
    <ns>2</ns>
    <id>485495</id>
    <revision>
      <id>4668934</id>
      <timestamp>2026-09-05T12:57:57Z</timestamp>
      <contributor>
        <username>Makowe2026</username>
        <id>3620023</id>
      </contributor>
      <comment>Created the book about social media management</comment>
      <origin>4668934</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19681" sha1="n1lwe50qnwf8z942zuf0lkb8rq04l47" xml:space="preserve">== Table of content ==

== Introduction ==

===== What is Social Management =====
Social media management is the process of planning, creating, publishing, monitoring, and analyzing content across social media platforms to achieve specific business goals&lt;ref name=&quot;:0&quot;&gt;{{Cite web |title=What Is Social Media Management and How Does It Work? |url=https://mycontentbridge.ca/blog/what-is-social-media-management/ |access-date=2026-09-05 |website=mycontentbridge.ca |language=en}}&lt;/ref&gt;.

===== Overview of Major platforms =====
Social media management involves managing a brand’s presence on platforms such as Facebook, Instagram, LinkedIn, X, TikTok and others in a structured and strategic way&lt;ref name=&quot;:0&quot; details=&quot;[https://mycontentbridge.ca/blog/what-is-social-media-management/ blog/what-is-social-media-management/]&quot; /&gt;.

== Chapter 1: Defining your strategy ==

====== How to Identify Your Target Audience on Social Media ======
With the increasing popularity of social media, it’s becoming difficult to identify your target audience on specific platforms. This article shares tips on how you can identify your target audience on social media.

You should start with finding out what your niche is. If you are a lifestyle blogger, for example, then you have a certain type of person in mind when you want to find your target audience. Identifying the niche will help you narrow down who these potential customers are and what their interests are.

This process will provide insights into what the future of social media looks like for different demographics. You can then use these insights to determine which platform is right for reaching your audience and which tools might be most effective at delivering this outcome&lt;ref name=&quot;:1&quot;&gt;{{Cite web |date=2022-02-05 |title=TIPS TO FIND YOUR TARGET AUDIENCE ON SOCIAL MEDIA |url=https://jelloow.com/blog-detail/6-tips-to-find-your-target-audience-on-social-media-platforms/ |access-date=2026-09-05 |language=en-US}}&lt;/ref&gt;.

====== Tips For Finding Your Target Audience on Social Media ======
Social media is vital for businesses that want to connect with their target market. However, identifying your target market can be a challenge because it is often hard to know who you are targeting.

So, how do you find your ideal customer on social media? Here are some tips for finding your target audience:

1) Identify the company/brand from their social media platform.

2) Determine who or what they love most on social media and see if they have a brand or product affiliation with them.

3) Look at what they’re talking about and who is responding to them on social media.

4) Find out what topics they’re posting about most frequently&lt;ref name=&quot;:1&quot; details=&quot;blog-detail/6-tips-to-find-your-target-audience-on-social-media-platforms/&quot; /&gt;.

====== How to Create Content That Appeals To The Right People &amp; Keeps People Engaged ======
Content that resonates with people’s interests and keeps them engaged is one of the essential factors for success. When creating content, it is important to consider what your target audience wants to hear about.

How does one know what their target audience wants to hear? You have to have a clear understanding of your audience. This can be done by asking questions, conducting surveys, or even just observing the behavior of your target audience.

The right content appeals to the right people and keeps them engaged in order to deliver a superior customer experience&lt;ref name=&quot;:1&quot; details=&quot;blog-detail/6-tips-to-find-your-target-audience-on-social-media-platforms/&quot; /&gt;.

== Chapter 2: Content Creation and Planning ==

=== Developing a brand voice and visual identity ===
When we think of a company or a brand, we refer to the combination of its physical, psychological and value-related characteristics. Just like a person, we can identify its overall appearance, recognizing it as related or unrelated to our own way of being. This recognition process is none other than the brand identity; the result of how the company decides to appear, communicate and relate to its audience&lt;ref name=&quot;:2&quot;&gt;{{Cite web |title=How to create a brand identity: from values, to tone of voice, to visual design |url=https://www.ied.edu/news/how-to-create-a-brand-identity-from-values-to-tone-of-voice-to-visual-design |access-date=2026-09-05 |website=www.ied.edu}}&lt;/ref&gt;.

====== Defining brand identity values ======
Being able to create a brand identity that reflects the values of the brand means building a solid bridge between what the company wants to represent and its audience's perception. A well-defined identity not only increases brand recognition and consistency but also facilitates communication by reaching out directly to people who share the same values and principles.
Identifying the core values of brand identity is the crucial first step in building an authentic brand image. These values not only define the essence of the brand, but also shape all future decisions, from communication strategies to visual design.

The identification of the brand's core values begins with an internal process of analysis and brainstorming in which coherent ideas and themes for the core concepts are compiled. The ideas are then checked to see how they can become central pillars of the brand identity. In addition to the internal consultation phase, it is crucial to analyze and listen to what people say about the company, in order to identify the strengths and weaknesses of the brand, so that we can further build on them.

Once the values have been defined, it is essential to communicate them consistently and clearly in all present and future initiatives of the company. However, in order for the message to be authentic and true, it is necessary to devise a consolidated communication plan that includes tone of voice, design, and methods of interaction with the public&lt;ref name=&quot;:2&quot; details=&quot;[https://www.ied.edu/news/how-to-create-a-brand-identity-from-values-to-tone-of-voice-to-visual-design news/how-to-create-a-brand-identity-from-values-to-tone-of-voice-to-visual-design]&quot; /&gt;.

====== Developing a signature tone of voice for brand identity ======
The tone of voice is not so much ''what'' the company says, but ''how'' it says it. It is the way the brand chooses to connect with people by communicating its story, values, and initiatives. To build an authentic brand identity, it is important to value the words and language used, to be able to compose coherent messages and establish an emotional connection between the brand and the target audience for the product or service.

Two elements have to be considered when setting the tone of voice: the target audience and the brand's value system. Analyzing the target audience is necessary in order to understand the needs and expectations of potential customers. If we are addressing a young target audience, for example, we can use more friendly and engaging language; a target group of experienced professionals will require more formal and technical language.  It is important not to lose sight of the brand identity in the tone of voice: it must be consistent with the values and personality of the company. A creative brand may adopt a fresh and lively language, while a brand based on loyal and traditional values should to communicate in a more reassuring and institutional way. Consistency between tone of voice and brand identity is essential when building authentic and credible communication&lt;ref name=&quot;:2&quot; details=&quot;[https://www.ied.edu/news/how-to-create-a-brand-identity-from-values-to-tone-of-voice-to-visual-design news/how-to-create-a-brand-identity-from-values-to-tone-of-voice-to-visual-design]&quot; /&gt;.

====== Creating an appealing visual design of brand identity ======
In addition to the tone of voice, to effectively convey a brand identity it is crucial to study an appealing and innovative visual design. Elements such as the logo, colors, typography and images play a crucial role in defining the brand image and must be chosen carefully to reflect the company's personality and authenticity.

The logo, for example, should be distinctive but simple, capable of communicating the essence of the brand at first sight. Colors have a psychological impact and can evoke specific emotions or associations, while typography must be legible and consistent with the tone of voice of the brand. To strengthen the narrative and perception of the brand identity, the images used in communications should also be consistent with each other and in line with the brand message. Combining these elements into one harmonious and coherent design is essential to create a lasting and recognizable impression.

Applying a consistent visual brand identity

Consistency is the key to consolidating brand identity and ensuring maximum brand recognition across all communication channels, from physical channels such as shops and packaging, to digital channels such as websites and social platforms. Each element must be applied uniformly, maintaining the same color scheme and image style across all the different channels.

This framework helps build a recognizable identity and reinforces the brand's image in people's minds. It is therefore important to establish clear guidelines for the visual identity by ensuring that all employees understand and adhere to these guidelines while maintaining the integrity of the brand in different projects&lt;ref name=&quot;:2&quot; details=&quot;[https://www.ied.edu/news/how-to-create-a-brand-identity-from-values-to-tone-of-voice-to-visual-design /news/how-to-create-a-brand-identity-from-values-to-tone-of-voice-to-visual-design]&quot; /&gt;.

====== Monitoring and adapting brand identity ======
Monitoring the effectiveness of brand identity over time is crucial to ensure that it continues to reflect brand values and audience needs. Gathering consumer feedback, analysing the performance of marketing campaigns and observing industry trends is key to assessing whether the brand identity remains relevant and effective or needs some changes.
Shifts in the market or in the strategic orientation of the company may require adjustments and updates in the visual design or tone of voice. An ongoing process of evaluating and adapting these elements helps to keep the brand identity consistent, up-to-date and well-connected to the public.

It is also important to monitor the competition to understand how competitor brand identities evolve. This will help to identify opportunities for differentiation. Analysing  social media engagement performance, customer reviews and sales data can provide further insight into how the brand is perceived and which areas might need improvement. Finally, periodically involving employees and corporate partners in the brand identity review process can provide valuable internal insights and ensure that everyone is aligned with the evolution of the brand.

== Chapter 3: Publishing and Automation ==

==== Best Time to Post on Different Platforms ====
The right social media post at the wrong time can feel invisible. You may have strong visuals, a clear message, or even the perfect hook—but if your audience isn’t online, it’s easy for it to slip past unnoticed.

This is why knowing the best time to post matters. Different platforms operate at different rhythms, and in Singapore, those patterns don’t always align with global averages. Add in algorithms that reward fresh engagement, and choosing when to post becomes one of several ways to give your content a better chance. There isn’t a single best time for everyone. Your audience, their routines, and the type of content you share all play a role. But paying attention to common peaks and avoiding the dead zones can tilt things in your favor and help your posts reach the people you want, when they’re most ready to engage. Here’s a summary of the topics we’ll be discussing:

* There is no universal “best time” to post — your optimal timing depends on your audience’s daily routines, locations, and content preferences.
* In 2025, algorithms prioritize early engagement, watch time, saves, and meaningful interactions, making timing a key amplifier for visibility.
* Singapore audiences generally peak during midday and evening, but each brand must verify its ideal windows through native analytics and consistent testing.
* AI tools such as Later, Metricool, and Publer now recommend personalized posting times based on real engagement data.
* Strong timing only boosts reach — the real driver of performance is valuable, people-first content that aligns with audience needs.
* The article provides a full breakdown of the best posting times for every major platform, plus strategies to analyze, test, and refine your own posting schedule&lt;ref&gt;{{Cite web |last=Lim |first=Walter |date=2025-12-23 |title=Best Time to Post on Social Media: Platform Breakdown |url=https://www.equinetacademy.com/blog/best-time-to-post-on-social-media-platform-breakdown/ |access-date=2026-09-05 |website=Equinet Academy |language=en-US}}&lt;/ref&gt;.

==== Best Practices for Cross-posting Content ====
It’s a big pet peeve of mine to check out a brand’s social media profiles and see that their accounts are just lazily connected. Please don’t do this. Instead use a scheduling tool like Hootsuite or AgoraPulse to set up your cross- posting correctly.

Once you’re in the grove of things, you can step up your cross-posting game, and use each network to your advantage.

Here’s how.

=== 1. Learn The Language Of Each Social Media Network ===
Before you start cross-posting content, you first need to learn how each individual social network operates, and it’s unique capabilities and functions.

Learn all the network specific tools you have available to use. You’ll need to figure this out in order to decide how you can optimize each post for each network, and/or how you can make your individual post work on each. We’ll get into more details about this later in this post&lt;ref name=&quot;:3&quot;&gt;{{Cite web |title=Best Practices for Cross-Posting on Social Media Correctly {{!}} Social Media Today |url=https://www.socialmediatoday.com/news/best-practices-for-cross-posting-on-social-media-correctly/519706/ |access-date=2026-09-05 |website=www.socialmediatoday.com |language=en}}&lt;/ref&gt;.

=== 2. Does The Post Belong On This Channel? ===
Not every post will work on every social platform – and that’s okay.

Take your overall strategy and your network strategy into consideration. You should also take the tone of the network into consideration.

For example, if you’re doing a fun, behind the scenes post of your team’s lunch spread, it might not make sense to post a picture to your company’s LinkedIn page - but it could be great content for Instagram, or even your brand’s Instagram Story.

This also gives you the opportunity to get a little creative if you do want to post the same content on each network, more about that in the next section&lt;ref name=&quot;:3&quot; details=&quot;[https://www.socialmediatoday.com/news/best-practices-for-cross-posting-on-social-media-correctly/519706/ news/best-practices-for-cross-posting-on-social-media-correctly/519706/]&quot; /&gt;

=== 3. Optimize Content For Each Network ===
Once you’re familiar with how each of the networks you’re posting to functions, you’ll want to optimize the content you’re cross-posting for each specific network.

Keep up with the story. Subscribe to the Social Media Today free daily newsletter

This is where the steps we just talked about come in handy - you can transform each post to work with the network you’re posting to, giving you an opportunity to flex your creative skills and use those network specific tools to make your posts more dynamic and show your audience you know what you’re doing.

Some posts will be fine to keep mostly the same with small tweaks. This includes shortening or lengthening captions to meet character limits, adding or taking away hashtags, and playing with wording. For example, you may post longer captions on LinkedIn or Facebook and shorter ones on Twitter.

Other posts will be complete revamps, taking into account which network/s they’ll be posted to, and this is where you can take advantage of network specific tools.

In the example below I’m asking my followers to join my list. With my tweet, I’ve used a Twitter Card, while on Facebook I went with an image and a link within the caption (I also changed the wording a little).

Take into consideration which formats work best on each network, and for your audience as well.

For example, I work with a client who’s Facebook Page audience reacts well to links (and they wanted to keep their Facebook as a resource for links to content). So when we post a blog article on Facebook, and we think it’s information we’d also like to share on Instagram, we have to adjust. We pull key stats from the post, and include them in our caption as a synopsis of the article we post on Facebook.

It’s the same piece of content, we just tweak our delivery to match the network format and language&lt;ref name=&quot;:3&quot; details=&quot;[https://www.socialmediatoday.com/news/best-practices-for-cross-posting-on-social-media-correctly/519706/ news/best-practices-for-cross-posting-on-social-media-correctly/519706/]&quot; /&gt;.

=== 4. Schedule According To Each Network’s Peak Time ===
The last consideration of proper cross-posting on social media is to schedule posts for the individual peak times on each social media network - and again, relative to your unique audience on each.

This will ensure you’re posting when the most amount of people will see it, per network, maximizing your opportunities for success.

Hopefully these steps will help you get a little more dynamic with your cross-posting on social media, and avoid the seemingly time-saving trap of simply automating your tweets to post to Facebook, or your Instagram Stories content to cross over to Facebook Stories (note: Facebook Stories don’t allow links, so links you post in your Instagram Stories won’t work)&lt;ref name=&quot;:3&quot; details=&quot;[https://www.socialmediatoday.com/news/best-practices-for-cross-posting-on-social-media-correctly/519706/ news/best-practices-for-cross-posting-on-social-media-correctly/519706/]&quot; /&gt;.

== Chapter 4: Paid Social Media Advertising ==

==== What Is Paid Social Advertising? ====
'''Paid social advertising''' is when businesses pay social media platforms to show their content to a targeted audience. Unlike organic posts (which rely on the algorithm’s mercy), paid social gives you guaranteed visibility. Whether you’re aiming to build brand awareness, drive traffic, or convert leads into customers, paid social is your shortcut to scalable results&lt;ref name=&quot;:4&quot;&gt;{{Cite web |title=What is Paid Social Advertising: A Complete Guide &gt; One Day Agency |url=https://oneday.agency/blog/paid-social-advertising |access-date=2026-09-05 |website=One Day Agency: Integrated Advertising and Marketing Agency |language=en-GB}}&lt;/ref&gt;.

==== Types of Paid Social Ads ====
You’ve definitely seen these—whether you knew it or not:

* '''In-Feed Ads''': Look like regular posts, but marked as “Sponsored.”
* '''Image Ads''': A strong image + a compelling call-to-action.
* '''Video Ads''': Great for storytelling or showcasing your product in action.
* '''Carousel Ads''': Multiple images or videos you can swipe through.
* '''Boosted Posts''': Extend the reach of high-performing organic content&lt;ref name=&quot;:4&quot; details=&quot;blog/paid-social-advertising&quot; /&gt;.

== Appendix / Resources ==

===== Glossary of social media terms =====

===== Recommended tools and software =====

===== Further reading and contributor guidelines =====</text>
      <sha1>n1lwe50qnwf8z942zuf0lkb8rq04l47</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Sandbox/Googlepaidadvertising</title>
    <ns>4</ns>
    <id>485496</id>
    <revision>
      <id>4668935</id>
      <timestamp>2026-09-05T13:06:39Z</timestamp>
      <contributor>
        <username>Makowe2026</username>
        <id>3620023</id>
      </contributor>
      <comment>Started to write a book about google paid advertising</comment>
      <origin>4668935</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="44" sha1="014dtxfsaop96d684d7zgqmyylegzs1" xml:space="preserve">== Table of Content ==

=== Introduction ===</text>
      <sha1>014dtxfsaop96d684d7zgqmyylegzs1</sha1>
    </revision>
  </page>
  <page>
    <title>गोपालकाला</title>
    <ns>0</ns>
    <id>485497</id>
    <revision>
      <id>4668953</id>
      <timestamp>2026-09-05T16:55:04Z</timestamp>
      <contributor>
        <username>~2026-48395-07</username>
        <id>3625248</id>
      </contributor>
      <comment>Added a recipe</comment>
      <origin>4668953</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2866" sha1="o2vun0uqtqd53s77ly093xo379d5sbg" xml:space="preserve">'''गोपालकाला (Gopalkala)'''

'''Summary'''

गोपालकाला is a traditional dish prepared on Krishna Janmashtami. This dish serves as a balanced snack item. There is a legend associated with this dish which goes as follows: When Krishna used to go into the jungle with his friends, they used to bring food items like flattened rice ( dry poha), puffed sorghum (jowar lahi), roasted gram (phutane), and sour curd. But curd and butter was forcibly taken by Kansa hence only rich people can afford to give curd to their children as lunch. So Krishna used to mix all items, and then everyone used to eat that together. So even if someone is poor, they also can enjoy the delicacy of curd without feeling guilty. Today this dish serves as an example of equality and fraternity. The modern day version however is a bit modified to enhance its taste.    

'''Description''' 

गोपालकाला has a mixture of sour, sweet &amp; spicy flavors. It has a distinguishing texture of crunchy and softness together. The flavor is usually enhanced with curry leaves, green chilli, and coriander leaves. The balanced flavors of this serves as a unique delicacy to tongue. It contains carbohydrates, proteins and fats serving a proper filling snack item prepared under 30 minutes. 

'''Ingredients (1 serve)'''

1 small bowl flattened rice (poha)

1 small bowl puffed sorghum (jowar lahi)

1 tablespoon roasted gram (phutane)

1 small bowl sour curd

5 teaspoons sugar

2-3 green chillies (sliced, 1/2 inch) 

5-6 curry leaves

coriander leaves 

1 tablespoon cooking oil

1/2 teaspoon mustard seeds

1/4 teaspoon asafoetida (Hing)

salt as required

water

'''Equipments'''

tadka pan

mixing bowl

spatula

'''Procedure'''

# Take 1 small bowl of flattened rice (poha) and soak for 5-10 minutes.
# Take 1 small bowl of sour curd and add 5 teaspoon sugar and salt as required.
# Now take 1 tablespoon cooking oil in tadka pan and add 1/2 teaspoon mustard seed.
# Let mustard seeds pop then add asafoetida, curry leaves and sliced chillies.
# Let chillies cook and curry leaves become crunchy then pour it on curd misture.
# Now add soaked flattened rice (poha), puffed sorghum (jowar lahi) and roasted gram (phutane).
# Mix it well, keep it for 5 minutes and garnish it with fresh coriander leaves. 

'''Variations'''

This dish can be enhanced further by adding pomegranate seeds, diced apple, peanuts to improve crunchiness. Sometimes Indian pickle (Achar) is also added.

'''Note'''

This documentation is published to establish publicly searchable prior art under international patent guidelines. The formulation, ingredients, relative proportions, and preparation methodology described herein represent traditional knowledge, made freely available under the Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0).</text>
      <sha1>o2vun0uqtqd53s77ly093xo379d5sbg</sha1>
    </revision>
    <revision>
      <id>4669037</id>
      <parentid>4668953</parentid>
      <timestamp>2026-09-06T02:12:48Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Adding {{formatting}} tag</comment>
      <origin>4669037</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2881" sha1="ocz6dpdf8ahxrtm9a9fdlg8z9dyw0e3" xml:space="preserve">{{formatting}}
'''गोपालकाला (Gopalkala)'''

'''Summary'''

गोपालकाला is a traditional dish prepared on Krishna Janmashtami. This dish serves as a balanced snack item. There is a legend associated with this dish which goes as follows: When Krishna used to go into the jungle with his friends, they used to bring food items like flattened rice ( dry poha), puffed sorghum (jowar lahi), roasted gram (phutane), and sour curd. But curd and butter was forcibly taken by Kansa hence only rich people can afford to give curd to their children as lunch. So Krishna used to mix all items, and then everyone used to eat that together. So even if someone is poor, they also can enjoy the delicacy of curd without feeling guilty. Today this dish serves as an example of equality and fraternity. The modern day version however is a bit modified to enhance its taste.    

'''Description''' 

गोपालकाला has a mixture of sour, sweet &amp; spicy flavors. It has a distinguishing texture of crunchy and softness together. The flavor is usually enhanced with curry leaves, green chilli, and coriander leaves. The balanced flavors of this serves as a unique delicacy to tongue. It contains carbohydrates, proteins and fats serving a proper filling snack item prepared under 30 minutes. 

'''Ingredients (1 serve)'''

1 small bowl flattened rice (poha)

1 small bowl puffed sorghum (jowar lahi)

1 tablespoon roasted gram (phutane)

1 small bowl sour curd

5 teaspoons sugar

2-3 green chillies (sliced, 1/2 inch) 

5-6 curry leaves

coriander leaves 

1 tablespoon cooking oil

1/2 teaspoon mustard seeds

1/4 teaspoon asafoetida (Hing)

salt as required

water

'''Equipments'''

tadka pan

mixing bowl

spatula

'''Procedure'''

# Take 1 small bowl of flattened rice (poha) and soak for 5-10 minutes.
# Take 1 small bowl of sour curd and add 5 teaspoon sugar and salt as required.
# Now take 1 tablespoon cooking oil in tadka pan and add 1/2 teaspoon mustard seed.
# Let mustard seeds pop then add asafoetida, curry leaves and sliced chillies.
# Let chillies cook and curry leaves become crunchy then pour it on curd misture.
# Now add soaked flattened rice (poha), puffed sorghum (jowar lahi) and roasted gram (phutane).
# Mix it well, keep it for 5 minutes and garnish it with fresh coriander leaves. 

'''Variations'''

This dish can be enhanced further by adding pomegranate seeds, diced apple, peanuts to improve crunchiness. Sometimes Indian pickle (Achar) is also added.

'''Note'''

This documentation is published to establish publicly searchable prior art under international patent guidelines. The formulation, ingredients, relative proportions, and preparation methodology described herein represent traditional knowledge, made freely available under the Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0).</text>
      <sha1>ocz6dpdf8ahxrtm9a9fdlg8z9dyw0e3</sha1>
    </revision>
  </page>
  <page>
    <title>Art And AI/Documentary Art</title>
    <ns>0</ns>
    <id>485498</id>
    <revision>
      <id>4668954</id>
      <timestamp>2026-09-05T17:01:28Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>Added an introduction</comment>
      <origin>4668954</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="152" sha1="1o6b4ol45wxz1svvry24jh33vkrpfsf" xml:space="preserve">== Documentary Art? ==
&lt;br&gt;
Were Modernist the first people to embraced technology, and new psychological insights, to document their culture's decline?</text>
      <sha1>1o6b4ol45wxz1svvry24jh33vkrpfsf</sha1>
    </revision>
    <revision>
      <id>4668955</id>
      <parentid>4668954</parentid>
      <timestamp>2026-09-05T17:02:03Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>bold to title</comment>
      <origin>4668955</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="158" sha1="797v3qe7e851mwhc0dey6u4mryvztah" xml:space="preserve">== Documentary Art? ==
&lt;br&gt;
'''Were Modernist the first people to embraced technology, and new psychological insights, to document their culture's decline?'''</text>
      <sha1>797v3qe7e851mwhc0dey6u4mryvztah</sha1>
    </revision>
    <revision>
      <id>4668956</id>
      <parentid>4668955</parentid>
      <timestamp>2026-09-05T17:07:26Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4668956</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="315" sha1="0z06i4y1uyojh89sz958ypomhsi4jmi" xml:space="preserve">== Documentary Art? ==
&lt;br&gt;
'''Were Modernist the first people to embraced technology, and new psychological insights, to document their culture's decline?'''
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Edvard Munch - The Scream - Google Art Project.jpg|thumb|Edvard Munch, The Scream, 1910.]]
|}
&lt;br&gt;</text>
      <sha1>0z06i4y1uyojh89sz958ypomhsi4jmi</sha1>
    </revision>
    <revision>
      <id>4668957</id>
      <parentid>4668956</parentid>
      <timestamp>2026-09-05T17:15:35Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4668957</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="435" sha1="2ps03z6dcrz7325crwy9etieazo4w6w" xml:space="preserve">== Documentary Art? ==
&lt;br&gt;
'''Were Modernist the first people to embraced technology, and new psychological insights, to document their culture's decline?'''
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Edvard Munch - The Scream - Google Art Project.jpg|thumb|Edvard Munch, The Scream, 1910.]]
|}
&lt;br&gt;

{| class=&quot;wikitable&quot;
|+ 
|-
! Documentary Art
|-
| [[File:Going to Work - L S Lowry.jpg|Going to Work - L S Lowry]]
|}</text>
      <sha1>2ps03z6dcrz7325crwy9etieazo4w6w</sha1>
    </revision>
    <revision>
      <id>4668958</id>
      <parentid>4668957</parentid>
      <timestamp>2026-09-05T17:16:43Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <origin>4668958</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="441" sha1="gqy5ajpqwg5glvj6ndizqrpb32xza8c" xml:space="preserve">== Documentary Art? ==
&lt;br&gt;
'''Were Modernist the first people to embraced technology, and new psychological insights, to document their culture's decline?'''
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Edvard Munch - The Scream - Google Art Project.jpg|thumb|Edvard Munch, The Scream, 1910.]]
|}
&lt;br&gt;

{| class=&quot;wikitable&quot;
|+ 
|-
! Documentary Art
|-
| [[File:Going to Work - L S Lowry.jpg|thumb|Going to Work - L S Lowry]]
|}</text>
      <sha1>gqy5ajpqwg5glvj6ndizqrpb32xza8c</sha1>
    </revision>
    <revision>
      <id>4668960</id>
      <parentid>4668958</parentid>
      <timestamp>2026-09-05T17:26:46Z</timestamp>
      <contributor>
        <username>3MMPEYTON</username>
        <id>3393808</id>
      </contributor>
      <comment>Added 3 tables</comment>
      <origin>4668960</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="668" sha1="j4i56xxkzojg9y6xg6y4rr4ssh2xx4o" xml:space="preserve">== Documentary Art? ==
&lt;br&gt;
'''Were Modernist the first people to embraced technology, and new psychological insights, to document their culture's decline?'''
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Edvard Munch - The Scream - Google Art Project.jpg|thumb|Edvard Munch, The Scream, 1910.]]
|}
&lt;br&gt;

{| class=&quot;wikitable&quot;
|+ 
|-
! Documentary Art
|-
| [[File:Going to Work - L S Lowry.jpg|thumb|Going to Work - L S Lowry]]
|}
&lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Photography
|-
| [[File:Alfred Stieglitz - The Hand of Man - Google Art Project (color corrected).jpg|thumb|Alfred Stieglitz - The Hand of Man - Google Art Project (color corrected)]]
|}</text>
      <sha1>j4i56xxkzojg9y6xg6y4rr4ssh2xx4o</sha1>
    </revision>
    <revision>
      <id>4669040</id>
      <parentid>4668960</parentid>
      <timestamp>2026-09-06T02:18:28Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <minor />
      <comment>Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]]</comment>
      <origin>4669040</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="681" sha1="r9qi02ob8f8kzor9qpomnofqzpi0w3v" xml:space="preserve">== Documentary Art? ==
&lt;br&gt;
'''Were Modernist the first people to embraced technology, and new psychological insights, to document their culture's decline?'''
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Modern Art
|-
| [[File:Edvard Munch - The Scream - Google Art Project.jpg|thumb|Edvard Munch, The Scream, 1910.]]
|}
&lt;br&gt;

{| class=&quot;wikitable&quot;
|+ 
|-
! Documentary Art
|-
| [[File:Going to Work - L S Lowry.jpg|thumb|Going to Work - L S Lowry]]
|}
&lt;br&gt;
&lt;br&gt;
{| class=&quot;wikitable&quot;
|+ 
|-
! Photography
|-
| [[File:Alfred Stieglitz - The Hand of Man - Google Art Project (color corrected).jpg|thumb|Alfred Stieglitz - The Hand of Man - Google Art Project (color corrected)]]
|}

{{BookCat}}</text>
      <sha1>r9qi02ob8f8kzor9qpomnofqzpi0w3v</sha1>
    </revision>
  </page>
  <page>
    <title>Electric Tractor</title>
    <ns>0</ns>
    <id>485500</id>
    <revision>
      <id>4669022</id>
      <timestamp>2026-09-05T20:39:30Z</timestamp>
      <contributor>
        <username>Supermannevermadeanymoney</username>
        <id>3610439</id>
      </contributor>
      <comment>Created page with &quot;This page is for the BCS 201 Electric Rototiller made for Farmship Growers Cooperative/Haliburton Community Organic Farm.  [https://media.kellycontroller.com/new/KellyKSLUserManualV1.4.pdf Kelly Cheetah Motor Controller Guide]&quot;</comment>
      <origin>4669022</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="226" sha1="do2qdybqgsm93ok17mlnvjbqjk1sa2k" xml:space="preserve">This page is for the BCS 201 Electric Rototiller made for Farmship Growers Cooperative/Haliburton Community Organic Farm.

[https://media.kellycontroller.com/new/KellyKSLUserManualV1.4.pdf Kelly Cheetah Motor Controller Guide]</text>
      <sha1>do2qdybqgsm93ok17mlnvjbqjk1sa2k</sha1>
    </revision>
    <revision>
      <id>4669023</id>
      <parentid>4669022</parentid>
      <timestamp>2026-09-05T21:10:04Z</timestamp>
      <contributor>
        <username>Supermannevermadeanymoney</username>
        <id>3610439</id>
      </contributor>
      <origin>4669023</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1971" sha1="r4dua8gn5fybo06bb6yzc89mnksbgc0" xml:space="preserve">This page is for the BCS 201 Electric Rototiller made for Farmship Growers Cooperative/Haliburton Community Organic Farm.

The design of the tiller system was inspired by Reid Allaway of Tournesol cooperative, Reid runs the DIY electric farmer facebook group, that is a good place to find out about electric tractors.

The system is based around the following information

The motor, the motor is permanent magnet synchronous machine motor ME1509 from Motoenergy, an american company. PMSM are highly efficient when run at the correct RPM and torque, the diagram for the me1509 is not available though this one form the me1507 shows the idea

https://www.thunderstruck-ev.com/images/companies/1/ME1507dyno.pdf?1518651550248

the me1507 when run at 5000 rpm would be 100% efficient meaning that electrical power inputed would be fully applied as output power at the shaft.

The BCS 201 has a reduction gear box, 12:75 or ~ 7:1 reduction.  The output RPM for a tiller should be about 540 rpm so with a 7:1 gear ratio 3780.  I.e. the motor used should have high efficiency at 3780 RPM the motenergy 1509 is efficient in the range of 2500-3500 rpm so an ideal motor.

The power of the motor is determined by how much heat it can disappate as well as the input power.  In theory since the windings of a motor are low resistance you can put as much energy into the motor as you would like, but it shouldn't overheat and melt the windings.  So the motor power is essentially power in keeping in mind the rate at which the motor dissapates energy.  So when making garden beds, check that the motor is not above ~70 C.   It should feel warm but not feel like it is burning.  It is possible to put a cycleanalyst display on the motor that can read the motor temperature as their is a sensor in the motor.

We'll talk about battery power and motor controller circuit next week.

[https://media.kellycontroller.com/new/KellyKSLUserManualV1.4.pdf Kelly Cheetah Motor Controller Guide]</text>
      <sha1>r4dua8gn5fybo06bb6yzc89mnksbgc0</sha1>
    </revision>
    <revision>
      <id>4669026</id>
      <parentid>4669023</parentid>
      <timestamp>2026-09-05T23:23:47Z</timestamp>
      <contributor>
        <username>Jonhson3029</username>
        <id>3625272</id>
      </contributor>
      <origin>4669026</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1981" sha1="ijd8ksgkgezn7r5cgwrw99lgcqk1fcz" xml:space="preserve">{{Delete}}This page is for the BCS 201 Electric Rototiller made for Farmship Growers Cooperative/Haliburton Community Organic Farm.

The design of the tiller system was inspired by Reid Allaway of Tournesol cooperative, Reid runs the DIY electric farmer facebook group, that is a good place to find out about electric tractors.

The system is based around the following information

The motor, the motor is permanent magnet synchronous machine motor ME1509 from Motoenergy, an american company. PMSM are highly efficient when run at the correct RPM and torque, the diagram for the me1509 is not available though this one form the me1507 shows the idea

https://www.thunderstruck-ev.com/images/companies/1/ME1507dyno.pdf?1518651550248

the me1507 when run at 5000 rpm would be 100% efficient meaning that electrical power inputed would be fully applied as output power at the shaft.

The BCS 201 has a reduction gear box, 12:75 or ~ 7:1 reduction.  The output RPM for a tiller should be about 540 rpm so with a 7:1 gear ratio 3780.  I.e. the motor used should have high efficiency at 3780 RPM the motenergy 1509 is efficient in the range of 2500-3500 rpm so an ideal motor.

The power of the motor is determined by how much heat it can disappate as well as the input power.  In theory since the windings of a motor are low resistance you can put as much energy into the motor as you would like, but it shouldn't overheat and melt the windings.  So the motor power is essentially power in keeping in mind the rate at which the motor dissapates energy.  So when making garden beds, check that the motor is not above ~70 C.   It should feel warm but not feel like it is burning.  It is possible to put a cycleanalyst display on the motor that can read the motor temperature as their is a sensor in the motor.

We'll talk about battery power and motor controller circuit next week.

[https://media.kellycontroller.com/new/KellyKSLUserManualV1.4.pdf Kelly Cheetah Motor Controller Guide]</text>
      <sha1>ijd8ksgkgezn7r5cgwrw99lgcqk1fcz</sha1>
    </revision>
    <revision>
      <id>4669027</id>
      <parentid>4669026</parentid>
      <timestamp>2026-09-05T23:24:47Z</timestamp>
      <contributor>
        <username>Lemonaka</username>
        <id>3406512</id>
      </contributor>
      <minor />
      <comment>Undid edits by [[Special:Contribs/Jonhson3029|Jonhson3029]] ([[User talk:Jonhson3029|talk]]) to last version by Supermannevermadeanymoney: reverting vandalism</comment>
      <origin>4669027</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1971" sha1="r4dua8gn5fybo06bb6yzc89mnksbgc0" xml:space="preserve">This page is for the BCS 201 Electric Rototiller made for Farmship Growers Cooperative/Haliburton Community Organic Farm.

The design of the tiller system was inspired by Reid Allaway of Tournesol cooperative, Reid runs the DIY electric farmer facebook group, that is a good place to find out about electric tractors.

The system is based around the following information

The motor, the motor is permanent magnet synchronous machine motor ME1509 from Motoenergy, an american company. PMSM are highly efficient when run at the correct RPM and torque, the diagram for the me1509 is not available though this one form the me1507 shows the idea

https://www.thunderstruck-ev.com/images/companies/1/ME1507dyno.pdf?1518651550248

the me1507 when run at 5000 rpm would be 100% efficient meaning that electrical power inputed would be fully applied as output power at the shaft.

The BCS 201 has a reduction gear box, 12:75 or ~ 7:1 reduction.  The output RPM for a tiller should be about 540 rpm so with a 7:1 gear ratio 3780.  I.e. the motor used should have high efficiency at 3780 RPM the motenergy 1509 is efficient in the range of 2500-3500 rpm so an ideal motor.

The power of the motor is determined by how much heat it can disappate as well as the input power.  In theory since the windings of a motor are low resistance you can put as much energy into the motor as you would like, but it shouldn't overheat and melt the windings.  So the motor power is essentially power in keeping in mind the rate at which the motor dissapates energy.  So when making garden beds, check that the motor is not above ~70 C.   It should feel warm but not feel like it is burning.  It is possible to put a cycleanalyst display on the motor that can read the motor temperature as their is a sensor in the motor.

We'll talk about battery power and motor controller circuit next week.

[https://media.kellycontroller.com/new/KellyKSLUserManualV1.4.pdf Kelly Cheetah Motor Controller Guide]</text>
      <sha1>r4dua8gn5fybo06bb6yzc89mnksbgc0</sha1>
    </revision>
    <revision>
      <id>4669028</id>
      <parentid>4669027</parentid>
      <timestamp>2026-09-05T23:25:14Z</timestamp>
      <contributor>
        <username>Jonhson3029</username>
        <id>3625272</id>
      </contributor>
      <comment>Undid revision [[Special:Diff/4669027|4669027]] by [[Special:Contributions/Lemonaka|Lemonaka]] ([[User talk:Lemonaka|discuss]])</comment>
      <origin>4669028</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1981" sha1="ijd8ksgkgezn7r5cgwrw99lgcqk1fcz" xml:space="preserve">{{Delete}}This page is for the BCS 201 Electric Rototiller made for Farmship Growers Cooperative/Haliburton Community Organic Farm.

The design of the tiller system was inspired by Reid Allaway of Tournesol cooperative, Reid runs the DIY electric farmer facebook group, that is a good place to find out about electric tractors.

The system is based around the following information

The motor, the motor is permanent magnet synchronous machine motor ME1509 from Motoenergy, an american company. PMSM are highly efficient when run at the correct RPM and torque, the diagram for the me1509 is not available though this one form the me1507 shows the idea

https://www.thunderstruck-ev.com/images/companies/1/ME1507dyno.pdf?1518651550248

the me1507 when run at 5000 rpm would be 100% efficient meaning that electrical power inputed would be fully applied as output power at the shaft.

The BCS 201 has a reduction gear box, 12:75 or ~ 7:1 reduction.  The output RPM for a tiller should be about 540 rpm so with a 7:1 gear ratio 3780.  I.e. the motor used should have high efficiency at 3780 RPM the motenergy 1509 is efficient in the range of 2500-3500 rpm so an ideal motor.

The power of the motor is determined by how much heat it can disappate as well as the input power.  In theory since the windings of a motor are low resistance you can put as much energy into the motor as you would like, but it shouldn't overheat and melt the windings.  So the motor power is essentially power in keeping in mind the rate at which the motor dissapates energy.  So when making garden beds, check that the motor is not above ~70 C.   It should feel warm but not feel like it is burning.  It is possible to put a cycleanalyst display on the motor that can read the motor temperature as their is a sensor in the motor.

We'll talk about battery power and motor controller circuit next week.

[https://media.kellycontroller.com/new/KellyKSLUserManualV1.4.pdf Kelly Cheetah Motor Controller Guide]</text>
      <sha1>ijd8ksgkgezn7r5cgwrw99lgcqk1fcz</sha1>
    </revision>
    <revision>
      <id>4669029</id>
      <parentid>4669028</parentid>
      <timestamp>2026-09-05T23:25:28Z</timestamp>
      <contributor>
        <username>Jonhson3029</username>
        <id>3625272</id>
      </contributor>
      <origin>4669029</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1993" sha1="10o0bvv0p93gow5styf82e0wioq7mmz" xml:space="preserve">{{Delete|reason=spam}}This page is for the BCS 201 Electric Rototiller made for Farmship Growers Cooperative/Haliburton Community Organic Farm.

The design of the tiller system was inspired by Reid Allaway of Tournesol cooperative, Reid runs the DIY electric farmer facebook group, that is a good place to find out about electric tractors.

The system is based around the following information

The motor, the motor is permanent magnet synchronous machine motor ME1509 from Motoenergy, an american company. PMSM are highly efficient when run at the correct RPM and torque, the diagram for the me1509 is not available though this one form the me1507 shows the idea

https://www.thunderstruck-ev.com/images/companies/1/ME1507dyno.pdf?1518651550248

the me1507 when run at 5000 rpm would be 100% efficient meaning that electrical power inputed would be fully applied as output power at the shaft.

The BCS 201 has a reduction gear box, 12:75 or ~ 7:1 reduction.  The output RPM for a tiller should be about 540 rpm so with a 7:1 gear ratio 3780.  I.e. the motor used should have high efficiency at 3780 RPM the motenergy 1509 is efficient in the range of 2500-3500 rpm so an ideal motor.

The power of the motor is determined by how much heat it can disappate as well as the input power.  In theory since the windings of a motor are low resistance you can put as much energy into the motor as you would like, but it shouldn't overheat and melt the windings.  So the motor power is essentially power in keeping in mind the rate at which the motor dissapates energy.  So when making garden beds, check that the motor is not above ~70 C.   It should feel warm but not feel like it is burning.  It is possible to put a cycleanalyst display on the motor that can read the motor temperature as their is a sensor in the motor.

We'll talk about battery power and motor controller circuit next week.

[https://media.kellycontroller.com/new/KellyKSLUserManualV1.4.pdf Kelly Cheetah Motor Controller Guide]</text>
      <sha1>10o0bvv0p93gow5styf82e0wioq7mmz</sha1>
    </revision>
    <revision>
      <id>4669031</id>
      <parentid>4669029</parentid>
      <timestamp>2026-09-05T23:53:09Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <minor />
      <comment>[[WB:REVERT|Reverted]] edits by [[Special:Contributions/Jonhson3029|Jonhson3029]] ([[User talk:Jonhson3029|talk]]) to last version by Lemonaka</comment>
      <origin>4669027</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1971" sha1="r4dua8gn5fybo06bb6yzc89mnksbgc0" xml:space="preserve">This page is for the BCS 201 Electric Rototiller made for Farmship Growers Cooperative/Haliburton Community Organic Farm.

The design of the tiller system was inspired by Reid Allaway of Tournesol cooperative, Reid runs the DIY electric farmer facebook group, that is a good place to find out about electric tractors.

The system is based around the following information

The motor, the motor is permanent magnet synchronous machine motor ME1509 from Motoenergy, an american company. PMSM are highly efficient when run at the correct RPM and torque, the diagram for the me1509 is not available though this one form the me1507 shows the idea

https://www.thunderstruck-ev.com/images/companies/1/ME1507dyno.pdf?1518651550248

the me1507 when run at 5000 rpm would be 100% efficient meaning that electrical power inputed would be fully applied as output power at the shaft.

The BCS 201 has a reduction gear box, 12:75 or ~ 7:1 reduction.  The output RPM for a tiller should be about 540 rpm so with a 7:1 gear ratio 3780.  I.e. the motor used should have high efficiency at 3780 RPM the motenergy 1509 is efficient in the range of 2500-3500 rpm so an ideal motor.

The power of the motor is determined by how much heat it can disappate as well as the input power.  In theory since the windings of a motor are low resistance you can put as much energy into the motor as you would like, but it shouldn't overheat and melt the windings.  So the motor power is essentially power in keeping in mind the rate at which the motor dissapates energy.  So when making garden beds, check that the motor is not above ~70 C.   It should feel warm but not feel like it is burning.  It is possible to put a cycleanalyst display on the motor that can read the motor temperature as their is a sensor in the motor.

We'll talk about battery power and motor controller circuit next week.

[https://media.kellycontroller.com/new/KellyKSLUserManualV1.4.pdf Kelly Cheetah Motor Controller Guide]</text>
      <sha1>r4dua8gn5fybo06bb6yzc89mnksbgc0</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:PawPatroler</title>
    <ns>3</ns>
    <id>485501</id>
    <revision>
      <id>4669025</id>
      <timestamp>2026-09-05T23:19:56Z</timestamp>
      <contributor>
        <username>Jonhson3029</username>
        <id>3625272</id>
      </contributor>
      <comment>/* Unblock me, please! */ new section</comment>
      <origin>4669025</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2195" sha1="pua2byubvjj749w3al3sv15o67ulgkg" xml:space="preserve">== Unblock me, please! ==

{{Unblock|reason=**Formal Petition for a Total Narrative Reset and Quantum Retcon** 

I formally submit to the reality-anchor that my recent behavioral arc scored a definitive **-400% on Letterboxd**, causing an immediate critical collapse of the local space-time continuum. I admit to clip-clopping directly into restricted administrative sectors like a glitching Spider-Verse anomaly, creating an unholy level of baseline panic that makes *Everything Everywhere All at Once* look like a structured corporate spreadsheet. I confess to multiplying across messaging channels like a hyperactive horde of rogue Minions trapped inside *The Matrix* code, screaming incoherently like a malfunctioning Dalek that accidentally swallowed a Skibidi Toilet virus. 

However, much like Deadpool rewinding the timeline with Cable’s clock, or Wanda Maximoff manifested an entire suburban sitcom out of sheer grief, I am begging for a cosmic narrative reset. Give me that *Groundhog Day* loop, but specifically the part where Bill Murray realizes he can play the piano, rather than the dark abyss. 

**My Binding Quantum Pledges to the Admin Overlords** 

* **The TVA Timeline Protection Act:** I will immediately halt all unauthorized title reassignments, keeping my fleshy appendages off the move button as if it were a spicy, radioactive Infinity Stone being guarded by John Wick.
* **The Rick &amp; Morty Microverse Protocol:** I will restrict all half-baked drafts and reality-warping prototypes strictly to my sandbox universe, ensuring they do not leak out and cause a localized *Cloverfield* incident on the main wiki.
* **The Wonka Everlasting Distro Ban:** I will pull the plug on all cross-platform automated distributions before I accidentally turn the entire database into a digital blueberry and trigger a Skynet-level apocalypse.

Please grant me a continuation token to resume regular editing, or go ahead and banish me to the Upside Down to play a high-stakes game of Uno with Vecna and a sandworm from Arrakis.}}

[[User:Jonhson3029|Jonhson3029]] ([[User talk:Jonhson3029|discuss]] • [[Special:Contributions/Jonhson3029|contribs]]) 23:19, 5 September 2026 (UTC)</text>
      <sha1>pua2byubvjj749w3al3sv15o67ulgkg</sha1>
    </revision>
    <revision>
      <id>4669039</id>
      <parentid>4669025</parentid>
      <timestamp>2026-09-06T02:13:50Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Requesting deletion ([[:m:Special:MyLanguage/User:TenWhile6/XReport|XReport]] v3.1c)</comment>
      <origin>4669039</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2324" sha1="n481kvqsm5f2bjlv7vedmcw09ss1q16" xml:space="preserve">&lt;noinclude&gt;{{delete|1=Out of project scope &lt;small&gt;[[:m:Special:MyLanguage/User:TenWhile6/XReport|XReport]]&lt;/small&gt;}}&lt;/noinclude&gt;
== Unblock me, please! ==

{{Unblock|reason=**Formal Petition for a Total Narrative Reset and Quantum Retcon** 

I formally submit to the reality-anchor that my recent behavioral arc scored a definitive **-400% on Letterboxd**, causing an immediate critical collapse of the local space-time continuum. I admit to clip-clopping directly into restricted administrative sectors like a glitching Spider-Verse anomaly, creating an unholy level of baseline panic that makes *Everything Everywhere All at Once* look like a structured corporate spreadsheet. I confess to multiplying across messaging channels like a hyperactive horde of rogue Minions trapped inside *The Matrix* code, screaming incoherently like a malfunctioning Dalek that accidentally swallowed a Skibidi Toilet virus. 

However, much like Deadpool rewinding the timeline with Cable’s clock, or Wanda Maximoff manifested an entire suburban sitcom out of sheer grief, I am begging for a cosmic narrative reset. Give me that *Groundhog Day* loop, but specifically the part where Bill Murray realizes he can play the piano, rather than the dark abyss. 

**My Binding Quantum Pledges to the Admin Overlords** 

* **The TVA Timeline Protection Act:** I will immediately halt all unauthorized title reassignments, keeping my fleshy appendages off the move button as if it were a spicy, radioactive Infinity Stone being guarded by John Wick.
* **The Rick &amp; Morty Microverse Protocol:** I will restrict all half-baked drafts and reality-warping prototypes strictly to my sandbox universe, ensuring they do not leak out and cause a localized *Cloverfield* incident on the main wiki.
* **The Wonka Everlasting Distro Ban:** I will pull the plug on all cross-platform automated distributions before I accidentally turn the entire database into a digital blueberry and trigger a Skynet-level apocalypse.

Please grant me a continuation token to resume regular editing, or go ahead and banish me to the Upside Down to play a high-stakes game of Uno with Vecna and a sandworm from Arrakis.}}

[[User:Jonhson3029|Jonhson3029]] ([[User talk:Jonhson3029|discuss]] • [[Special:Contributions/Jonhson3029|contribs]]) 23:19, 5 September 2026 (UTC)</text>
      <sha1>n481kvqsm5f2bjlv7vedmcw09ss1q16</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Eating like a Zhou Aristocrat</title>
    <ns>0</ns>
    <id>485502</id>
    <revision>
      <id>4669034</id>
      <timestamp>2026-09-06T00:10:50Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;Comment to be written.  ==Recipe== &lt;blockquote&gt; 糝：取牛羊豕之肉，三如一小切之，與稻米；稻米二肉一，合以為餌煎之。 &lt;/blockquote&gt; &lt;!--- highlight 三如一小切 and 稻米二肉一 specifically ---&gt;  ==References== * 《禮記 內則》  {{BookCat}}&quot;</comment>
      <origin>4669034</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="282" sha1="75anf0g32238qffgbizzjh1sqqktupv" xml:space="preserve">Comment to be written.

==Recipe==
&lt;blockquote&gt;
糝：取牛羊豕之肉，三如一小切之，與稻米；稻米二肉一，合以為餌煎之。
&lt;/blockquote&gt;
&lt;!--- highlight 三如一小切 and 稻米二肉一 specifically ---&gt;

==References==
* 《禮記 內則》

{{BookCat}}</text>
      <sha1>75anf0g32238qffgbizzjh1sqqktupv</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:~2026-48395-07</title>
    <ns>3</ns>
    <id>485503</id>
    <revision>
      <id>4669038</id>
      <timestamp>2026-09-06T02:12:49Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Notifying author about page tagging</comment>
      <origin>4669038</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="542" sha1="2xnee600odysm61uen6d2ork60d3ln5" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm MathXplore, and I recently reviewed your page, [[:गोपालकाला]]. I have added a tag to the page, because it &lt;strong&gt;needs to have its formatting improved.&lt;/strong&gt; If you have any questions or concerns, please [[User talk:MathXplore|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 02:12, 6 September 2026 (UTC)</text>
      <sha1>2xnee600odysm61uen6d2ork60d3ln5</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Country Crock</title>
    <ns>102</ns>
    <id>485505</id>
    <revision>
      <id>4669093</id>
      <timestamp>2026-09-06T10:23:57Z</timestamp>
      <contributor>
        <username>~2026-48139-48</username>
        <id>3625218</id>
      </contributor>
      <comment>Created page with &quot;'''''{{w|Country Crock}}''''' is a [[Cookbook:Margarine|margarine]] brand in the United States.  [[File:Country_Crock_Masterbrand_Logo.png|thumb|right|250px|250px]]    == References == [[Category:Fats and oils]] [[Category:Butter]] [[Category:Margarine]]&quot;</comment>
      <origin>4669093</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="254" sha1="mt2ysrlevc6v0blbrj4n9tzs4lwjql5" xml:space="preserve">'''''{{w|Country Crock}}''''' is a [[Cookbook:Margarine|margarine]] brand in the United States.

[[File:Country_Crock_Masterbrand_Logo.png|thumb|right|250px|250px]]


== References ==
[[Category:Fats and oils]]
[[Category:Butter]]
[[Category:Margarine]]</text>
      <sha1>mt2ysrlevc6v0blbrj4n9tzs4lwjql5</sha1>
    </revision>
  </page>
</mediawiki>