Talk:AmigaOS

message: The article says that the AmigaOS as developed by Commodore. This is not quite correct. The Amiga and the early version of the OS was developed by the Amiga, Inc company, headed up by Dave Hayne and others who created this killer computer. Commodore bought out the technology from the and hired them, of course.  — Preceding unsigned comment added by LordAlveric (talk • contribs) 06:38, 31 October 2014 (UTC)
thread_title:  Origins of the AmigaOS 

message: The current article states 'subsequent Amiga models all used ROM chips' [following the A1000] in relation to Kickstart.
However, I remember that the Amiga 3000 also required such a Kickstart disk. Can anyone confirm? Thanks!
:Most A3000s used ROMs, but some (like mine) had a small "Super Kickstart" in ROM which read Kickstart from floppy or hard disk. (Super Kickstart was based on AmigaOS 1.4, which never appeared anywhere else.) IIRC, only the machines manufactured in Europe had "Super Kickstart", but I may well be wrong on that detail. I do know that I never got my machine to boot a v3.x AmigaOS :=(. Cheers, CWC(talk) 02:41, 6 August 2006 (UTC)
thread_title:  Kickstart disks 

message: (This is relevant to a different Wikipedia article). I have the statement in front of me that, when a program terminates in AmigaOS, memory assigned by the program is not freed, and that it is therefore vital for the program to release all memory that it asked for, otherwise it is permanently "leaked". Is this the case? Notinasnaid 10:48, 23 October 2006 (UTC)
replies: text: Memory that is not freed before termination of a program in the Amiga OS is leaked (assuming it was supposed to be freed - in some cases a program may have allocated structures and attached them to system objects, such as a device node).  One of the most common modes of testing on the Amiga was checking free memory after program exit; there were many tools that automated that.  Normal behavior of a program was to free all memory, and all malloc'd memory was automatically freed via exit-time hooks.  (I.e. leaking memory typically only happened to memory obtained via AllocMem() and the like.)  jesup 12:02, 23 October 2006 (UTC)

text: Indeed. AmigaOS does little to no resource tracking in order to save the memory overhead that it costs to include tracking. There was also a third-party program that patched many allocate/free resource functions (e.g. AllocMem/FreeMem, OpenWindow/CloseWindow) and added resource tracking to them, however this would break any software that deliberately allocate memory then exited, for example programs which installed patches on system functions. Programs assume the responsibility for freeing all allocated memory. The standard C library implementation in most Amiga C compilers used an onexit handler that freed any memory allocated with the malloc() implementation, but if the program crashed or the AmigaOS memory allocation routines were called directly, memory allocations were not freed. Other languages had varying degrees of support for tracking memory, usually (like C) only if you used the language-specific memory allocators. 195.173.23.111 13:50, 24 October 2006 (UTC)

text: The amiga would be included in "modern operating systems", and it does release "normal memory" (i.e. malloced) when the application ends.  Program crashes on an Amiga do not release memory, so you could say it leaks on process crash.  And a program that uses things like OpenFile() instead of open() will leak a filehandle (and some memory) if the program calls exit() without closing the file.  As for your second question, the answer would be "some systems" - many "modern" embedded systems (including running unix variants like uclinux) do not have memory protection, and can read (and possibly write) structures using NULL as a pointer without an access violation.  Personally, I HATE programs that don't check malloc (or any other calls) for failure.  Good programming practice on the Amiga (due to the lack of VM) was to test programs and the OS against random memory allocation failures to see if they recovered cleanly or not.  All allocations (and all system calls, etc) should be checked for failure and proper rollback/error-recovery done, unlike the typical Unix/Windows/etc method of "if (NULL == (foo = malloc(N)) exit(1);" or equivalent.  But that's another rant.... :-)  jesup 19:59, 24 October 2006 (UTC)

text: I would say "in most operating systems". Only (1970s/80s/early 90s) microcomputer operating systems and some embedded systems, especially those running on hardware without an MMU, would have no resource tracking. The number of such operating systems is quite small. I wouldn't use "modern", because almost all "old" (since late 1960s) operating systems running on expensive minicomputers or mainframes definitely had resource tracking, and some modern embedded operating systems don't have resource tracking. 195.173.23.111 13:21, 25 October 2006 (UTC)
thread_title:  Freeing memory 

message: Comment: Now, there shall be havy change to mainpage :-) Sources: Amiga World News Hyperion news
Leuven, Belgium, 24 December 2006.
Hyperion-entertainment is very pleased to announce the immediate availability (for registered AmigaOne customers) of Amiga OS 4.0, The Final Update.
Originally released in May of 2004, Amiga OS 4.0 (www.amigaos4.com) is the most stable, modern and feature-rich incarnation to date of the multi-media centric operating system launched by Commodore Business Machines (CBM) in 1985 with which it still retains a high degree of compatibility.
Amiga OS 4.0, The Final Update is the culmination of 5 years of development and takes the form of a stand-alone ISO image which contains a full installation of all Amiga OS 4.0 components.
A list of new features can be found here .
Availability of PowerPC hardware suitable for operation with Amiga OS 4.0 will be announced by third parties early 2007.
The Hyperion Entertainment management would like to take this opportunity to wish all our customers and supporters a pleasant holiday season!
Links: Amiga OS4 Hyperion Amiga section
--Rastavox 22:59, 5 January 2007 (UTC)
thread_title:  OS4 Final Realised 

message: In other articles the OS is depicted with a "non-personalized" screenshot taken after the first boot of the newest version. The current screenshot has a background image, AmigaAMP and other details I'm sure are not present after the first boot.
Anyone with AOS 4.0, or if not that - AOS 3.9, willing to upload such a screenshot?
--Anss123 17:03, 5 May 2007 (UTC)
replies: text: Note that AmigaAMP and PlayCD are installed as standard on AOS 3.9, but yes, it would be good to have a shot which doesn't have application windows or showing all the other stuff which has been installed. Unfortunately I can't do OS 4.0, but I've just done a fresh install of OS 3.9 under WinUAE, so I'll try to upload one soon. Mdwh 02:44, 28 May 2007 (UTC)
replies: text: I've created one, see  (not sure how to wikilink an image) - how's that? Mdwh 01:49, 11 June 2007 (UTC)
thread_title: The screenshot

message: The article states that multiple, draggable screens are a Workbench feature. Surely these are a core AmigaOS feature? They're present before Workbench loads.
Zeem.uk (talk) 11:41, 6 January 2008 (UTC)
replies: text: While the sliding Viewports are provided by the hardware and graphics.library, the ability to drag them with the mouse, "move" one in front of another, etc is provided by Intuition. Some people regard Intuition as part of Workbench, some don't. Cheers, CWC 08:11, 7 January 2008 (UTC)
thread_title:  Virtual screens 

message: I've rewritten the bit about ARP because it incorrectly stated that it was only possible to interface with AmigaDOS from BCPL.  In fact it was not only possible to do so, it was done regularly by early Amiga programmers. However because BCPL uses an unusual addressing scheme (storing pointers not as machine addresses but as so-called BPTRs, which are scaled according to the BCPL location size chosen by the language implementor) it was notoriously difficult to do. It was easy to cause chaos by sending AmigaDOS a C pointer where it expected a BPTR (and Amigas had no memory protection....)  This is why ARP was born--to provide a C interface to existing kernel functions. --Tony Sidaway 14:51, 2 February 2008 (UTC)
thread_title: ARP

message: :Image:Amiga Workbench 1 3 large.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to ensure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is  other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page.  Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
BetacommandBot (talk) 00:08, 8 March 2008 (UTC)
thread_title: Fair use rationale for Image:Amiga Workbench 1 3 large.png

message: :Image:Amiga kickstart.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to ensure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is  other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page.  Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
BetacommandBot (talk) 00:09, 8 March 2008 (UTC)
thread_title: Fair use rationale for Image:Amiga kickstart.png

message: There are too many external links. Some links could and should be moved to OS4 article. There are also too many links to developer sites (utilitybase should be enough) and why there are links to non-english sites? They are not used as a reference in this article.
01:12, 23 November 2008 (UTC)
thread_title:  External links 

message: This was placed on Metadata, but is too OS-specific. Please feel free to include it on this article,.:
AmigaOS stored metadata in sections of data files called "chunks" or deep into specific "hunks" that form the structure of executable files (Hunks), where are stored for example the file comments, the owner of the file (not mandatory in AmigOS), the tool that originated the data file (again not mandatory), or in parallel the metadata can also be stored into separated files named ".info" which contain not only metadata, but also various other informations needed to the data file or to the program itself, such as the options available for the executable file, the minimum stack of RAM to run the program, and also the bitmaps images that phisically represent the icon on desktop.
:Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 15:15, 31 December 2008 (UTC)
thread_title:  Metadata 

message: For some reason the PDF creator creates this article without images. Other articles are created fine.  — Preceding unsigned comment added by 195.130.121.48 (talk) 16:23, 2 December 2011 (UTC)
thread_title:  PDF creation problem 

message: Hello fellow Wikipedians,
I have just modified  on AmigaOS. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive http://web.archive.org/web/20080223154107/http://www.newtek.com:80/newtek/milestones.php to http://www.newtek.com/newtek/milestones.php
*Added archive http://web.archive.org/web/20060314185142/http://www.lysator.liu.se/ahi/ to http://www.lysator.liu.se/ahi/
*Added archive http://web.archive.org/web/20110718202151/http://arp2.berlios.de/ahi/ to http://arp2.berlios.de/ahi/#binaries
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—cyberbot IITalk to my owner:Online 15:27, 25 April 2016 (UTC)
thread_title:  External links modified 

message: Before an edit war starts, please discuss pros and cons here. In case anyone is interested I'll be glad to point out why I think Amiga OS uses a microkernel. --Zac67 (talk) 06:39, 29 September 2016 (UTC)
replies: text: Oh no not again (see archived discussion...). Better than post what you think, please provide reliable sources to support your claim. Note kernel type of AmigaOS is mentioned on other articles/lists too, we should create consensus here once and for all, it would be a mess otherwise... Pavlor (talk) 08:18, 29 September 2016 (UTC)
replies: text:  The microkernel page lists AmigaOS as an example while Hybrid kernel doesn't. The German AmigaOS page lists it as microkernel undisputed. Are , The Future Was Here, Early Home Computers, Tech Book 1, Introduction To Computers RS? Can anyone point out the monolithic aspects of AmigaOS? You could perhaps argue it's not a microkernel (by today's definition) but it definitely isn't hybrid – at all. --Zac67 (talk) 17:32, 29 September 2016 (UTC)
replies: text: What lists DE Wiki is not answer to our question, but these books could be useable (with exact pages for direct reference). I suggest to wait for some time. If nobody objects (with better reliable sources of course), we can assume new consensus and do all the needed changes on the entire Wiki. Pavlor (talk) 06:02, 30 September 2016 (UTC)
thread_title:  Microkernel vs hybrid 

message: Hello fellow Wikipedians,
I have just modified  on AmigaOS. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20081009150302/http://os4.hyperion-entertainment.biz/index.php%3Foption=content&task=view&id=22&Itemid=.html to http://os4.hyperion-entertainment.biz/index.php?option=content&task=view&id=22&Itemid=.html
*Added archive https://web.archive.org/web/20081009150308/http://os4.hyperion-entertainment.biz/index.php%3Foption=content&task=view&id=23&Itemid=.html to http://os4.hyperion-entertainment.biz/index.php?option=content&task=view&id=23&Itemid=.html
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—InternetArchiveBot (Report bug) 17:08, 11 October 2016 (UTC)
thread_title:  External links modified 

message: Please stop vandalizing the article with outdated information. The latest AmigaOS release is 3.1.4 not 4.1FE. This can easily be checked by simply going to Hyperion's website.  — Preceding unsigned comment added by 2A02:A442:581E:1:E393:6D91:F2C9:8D80 (talk) 05:32, 16 May 2020 (UTC)
replies: text: First, reverting unsourced edits to a stable revision is not vandalism. Hyperion maintains two branches of AmigaOS (3.1.x and 4.x), we may of course discuss which of these should be in the infobox, but inserting own unsourced POV certainly is not the best way to start a discussion. Note there is also a "3.X" branch from Cloanto, which also claims to be the rightful owner of AmigaOS. Pavlor (talk) 06:09, 16 May 2020 (UTC)
replies: text: 3.1.4 release = September 2018. 4.1FE release = December 2016. You may be unaware but time flows forwards not backwards. 3.1.4 being the latest release is simply a fact, not a matter of POV. 2A02:A442:581E:1:E393:6D91:F2C9:8D80 (talk) 04:22, 17 May 2020 (UTC)
replies: text: Well, one may call it some small update to an old version... Both branches could be included in the infobox (eg. as done for RISC OS). Pavlor (talk) 06:31, 17 May 2020 (UTC)
thread_title:  Latest version