Welcome, Guest. Please login or register.

Author Topic: A glossary of Amiga specific terms  (Read 2572 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline PentadTopic starter

A glossary of Amiga specific terms
« on: August 02, 2017, 09:03:21 PM »
I wanted to share a post from Bryce Nesbitt from 30 years ago that I thought you might get a kick out of. I’ve subscribed to Oldusenet’s servers (http://olduse.net) where they are replaying usenet posts from 30 years ago. So I’m reading the posts from this date from 1987. I started in early 2016 on comp.sys.amiga which would be from 1986. It has been a real treat to see the Amiga come to life and unfold through these posts. They call it a Realtime Historical Exhibit and it kind of is.

I think what makes it so interesting is that all the main people started posting on here from the beginning. So you have most of the original Amiga creators (RJ, Dale, Kodiak, Glen, Sam, Bob, Rob, etc..) and then a lot of Commodore people like Dave Haynie, George Robbins, Hedley Davis, Bryce Nesbitt, CATS, etc..

Developers and users alike had direct access to the people with the most knowledge of the Amiga from the start. Given the complexity of the Amiga, it was a fantastic resource and many people took advantage of it. George Robbins (who I knew little of before I started reading these groups) would post a slew of messages in a day trying to help people out. Dave Haynie was also incredibly active in helping people.

As most of the original team faded from Usenet the Commodore people really came out in force including people from CATS. I also have been following the Mac and Atari groups and only Apple had some support people post on their groups and even then it was pretty sporadic.

Bryce Nesbitt posted this message to help people with the new terminology of the Amiga. Many people thought execute was like delete/kill and I never thought about it like that until you think of an executioner killing things.  Anyway, I hope you enjoy it!




:-)
    A net smilely.  When sprinkled near a statement it indicates that it
    was was not meant seriously.  "The bombs drop in 5 minutes"  -Ronald
    Reagan :-)

()
    Used to signify a routine.   If I talk about Wait(), I am referring to
    the routine named "Wait".

$C00000 MEMORY
    Memory that sits at location $C00000.  Such memory is automatically
    added to the memory lists by the V1.2 operating system, yet does not
    take up normal auto-config space.

AGNUS
    One of the "big three" custom chips inside the Amiga.  Controls RAM
    addressing, DMA and other timing.

AmigaDOS
    Amiga Disk Operating System.  Strictly speaking, the part of the Amiga
    operating system that controls the file system.  Unlike MS-DOS, there
    is more to the Amiga operating system that just DOS.

    Workbench  CLI   Programs
         \      |       /
          \     |      /
      \    |     /
       \   |    /
        \  |   /
       AmigaDOS          ;DOS level
      /    |    \
         RAM:  DF0:  HD0:          ;FILE SYSTEM level
          |     |      |           ;(managed by handler processes)
     memory   disk    hard disk       ;DEVICE level
         drive   drive        ;(managed by device drivers)

    Programs may often bypass the DOS level by sending a packet directly to
    the proper handler process.

ARP
    AmigaDOS Replacement Project.  A holy crusade undertaken by Charlie
    Heath (of Microsmiths) to implement and distribute a free set of
    improved CLI commands, and programmer facilities.

ATOM
    A kludge to help developers tell their programs the differences between
    FAST and CHIP memory.  See FIXHUNK.

AUTO-CONFIG
    A system of automatically detecting and configuring memory and hardware
    without the need for millions of dip switches or direct user hassle.
    Basically, the software will tell the individual board's hardware what
    address ranges to respond to, and will resolve conflicts. Not actually
    implemented in the Amiga until operating system V1.2.

AUTODOC
    A brief, sometimes cryptic, summary of each Amiga library routine is
    kept in the actual original source code. These are extracted
    automatically by C-A and distributed on paper (in the RKM) or on disk
    to programmers.

BOOT
    From "to pull oneself up by one's bootstraps".  To start or restart
    one's computer from scratch.  With the exception of recoverable RAM
    disks, this means loosing all data in memory.

BARREL SHIFTER
    The part of the blitter that can shift bit images to arbitrary
    boundaries nearly instantly.

BIMMER
BLITTER
    A graphics engine that is part of the custom chips.  It can do BLITs
    (Block Image Transfers) in hardware.  Sometimes called a BIMMER (Bitmap
    IMmage Manipulator) because it can also do logic operations during the
    transfer, line draws, hardware fills, and more.

C-A
    Shorthand for Commodore-Amiga, Inc.

CHIP MEMORY
    Memory accessible by the custom chips.  This contains the frame buffer,
    sprites, audio DMA buffers, etc.  This memory runs at twice the speed
    of the 68000, which normally allows the 68000 to run without delay.
    With a very busy display that has lots of extra colors, copper lists,
    or blitter moves, this memory can get bogged down with all the extra
    work. Fortunately there is an alternative, it's called FAST MEMORY.

CHUNK
    See IFF.

CLI
    The AmigaDOS Command Line Interpreter.  A traditional line oriented DOS
    interface.   Can be though of as existing "under" the Workbench Tool.

COPPER
    Display co-processor.  Yet another microprocessor within the Amiga,
    this time specialized at for raster synchronization.  It only has three
    instructions, but since it can access any of the ~100 custom chip
    registers it's rather powerful.  Easy tricks include changing
    resolution on any line, reusing sprites later in a display, modifying
    the pallette on the fly, page flipping with no 68000 involvement, etc.

DEAMON
    The actual working part of a program that may do it's dirty work while
    hidden in the background.

DENISE
    One of the "big three" custom chips in the Amiga.  Contains the video
    output signals, mouse input and misc. timing.

DEVICE, EXEC
    Usually a task that that talks directly to some piece of hardware.   The
    "keyboard.device", for example, reads the keyboard then tells the rest
    of the world about it.  The "trackdisk.device" is an example of a
    device that can have multiple units.
    Programs communicate to devices with IO requests, a form of inter-task
    communication.
    The standard devices are: timer, trackdisk, keyboard, gameport, input,
    console, audio, narrator, serial, parallel, and printer.  With each
    hard drive, SCSI interface, or extra serial port, you will probably get
    another exec device.

DEVICE DRIVER
    The actual code that a device executes.

EHB
    Extra HalfBrite.  A video mode that allows 64 colors per line.
    Available on all A500s and A2000s, and roughly half of the A1000s.

EXEC
    The executive.  Master of the Amiga.  Controls task switching and low
    level system details.

EXECUTE
    To command a program or sequence of computer instructions to commence.
    Not "put to death".

FAST MEMORY
    Memory that is not accessible to the custom chips, and not subject to
    possible delay, either.  Most quality expansion memory fits in this
    category.  This is the preferred location for most program code and
    data.

FILE SYSTEM
    A place to store files.  DF0: is one, so is RAM:.

FIXHUNK
    A utility.   Some older programs for the Amiga where improperly written
    and will not work if non-CHIP memory is added.  Fixhunk can usually fix
    the problem.

GARY
    Stands for "Gate ARaY", cute eh?  A single custom chip used in the
    Amiga 500 that replaces a large number of individual chips from the
    original A1000.

GENLOCK
    The capability that allows synchronizing of the Amiga's video to an
    external source and the overlay of the two images.

GOLDFISH
    A intellectual possession of another that is not to be abused, stepped
    on, fried or otherwise compromised. :-)
Linux User (Arch & OpenSUSE TW) - WinUAE via WINE
 

Offline PentadTopic starter

Re: A glossary of Amiga specific terms
« Reply #1 on: August 02, 2017, 09:04:18 PM »
Here is the rest. I received an error when I tried to post it all in one message:


HAM
    Hold And Modify.  A obscure, but powerful, Amiga video mode that
    expresses each pixel as a modification of the last.  Allows for some
    nice shading.

HANDLER
    On the Amiga, the code that manages a file system.   Handlers often live
    in the L: directory when not in use.

HEAP
    A place to toss all sorts of junk.

HUNK
    A subdivision of an AmigaDOS object file.  HUNKS come in several
    flavors including those that store CODE, DATA and BSS (uninitialized
    data).  If all the HUNKS in a file do not line up correctly, AmigaDOS
    will report error 121, "file not an object module".

HUNKPAD
    A utility that can fix files that have been damaged by XMODEM transfer.
    One symptom of a damaged file is error 121, "file is not an object
    module".  This utility also prevents future XMODEM damage.

HYBRID MEMORY
    Memory that can't be addressed by the custom chips, yet is still
    subject to the delays they can can cause.  Sometimes called SLOW FAST
    memory.

ICON
    A pictorial representation of a file.  Expressed as a file with the
    ".info" suffix.  These come in the DISK, DRAWER, TOOL, PROJECT,
    GARBAGE, DEVICE and KICK flavors.  The last is not used, and the second
    to last is used in conjunction with auto-config.

IFF
    Interchange File Format.  A standard for creating file format
    standards.   Popular formats include ILBM (InterLeaved Bit-Map) for
    raster images, SVX8 (8 bit digital samples), and SMUS (Simple MUsical
    Score).
    ILBM, SVX8 and SMUS are all FORMs.   Each form is composed of one or
    more CHUNKS.  Each CHUNK holds a specific class of the file's data. For
    example in ILBM FORMs there are several possible CHUNKs including BHMD
    which holds the actual picture data, CMAP which holds the color map,
    and DEST which has to do with converting pictures with different
    depths.  Any writer that does not know about DEST won't write that. Any
    reader that does not care about DEST won't read it.  If a program wants
    a CMAP, but a file does not have it, it will use default values or make
    something up.  The beauty of this system is that new CHUNKS can be be
    added to an existing IFF file definition without affecting portability.

INPUT.DEVICE
    Where all the input from the keyboard, mouse and other user input
    devices flows.  Also a popular place for user interface modifying
    programs to hang out.

INTUITION
    "The Amiga user interface".  Intuition uses the low level layers and
    graphics libraries to build screens, windows, menus, gadgets and other
    user interaction mechanisms.

LIBRARY
    All Amiga system function calls are grouped into libraries.  Commonly
    used libraries include exec, intuition, dos and graphics.

LOCK
    An AmigaDOS structure that prevents multitasking programs from stomping
    on shared files.  Other Amiga subsystems use locks for other purposes.

MMU
    A device for arbitrating and protecting against a task damaging the
    memory of another task.  Also has lots of other uses that are beyond
    the scope of this discussion.  The current generation Amigas do not
    contain one.

MESSAGE
    A mechanism of inter-task communication.

NUKE
    To destroy, demolish, obliterate, wipe out, mung, hash into little
    bits, waste, screw up, or make FUBAR, by means of atomic weapons, or
    with a computer.

OVERLAY
    An AmigaDOS feature that allows part of a program to sit on disk, to be
    brought into memory only when needed.

OVERSCAN
    Any of the pixels beyond 640 (high res) or 320 (lo res) wide and 200 or
    400 high that are actually used in a display.  The Amiga system
    software will let you specify a display as wide as 704, and as high as
    464 pixels, but on most monitors some of that will be clipped by the
    borders of the display monitor used.  It is possible to adjust a
    monitor to show that space, however.  The "morerows" program can be
    used to add overscan pixels to the Workbench screen.  For broadcast TV
    use, overscan allows the picture to use the full width of the display.

PACKET, AmigaDOS
    An AmigaDOS specific message.  All DOS activity is actually carried out
    with a packet sent to the proper DOS HANDLER process.

PAULA
    Another of the "big three" custom chips.  Includes the audio DAC's,
    4703 custom interrupt chip, custom serial chip, and hyper-fancy custom
    disk controller.

PROCESS
    A task that has been taught how to talk to AmigaDOS.

PROJECT
    Workbenchism for the output of a tool.  A data file.

RKM
    The ROM Kernal Manual, the Amiga programmer's bible.  The other two
    essential books are the Intuition manual and the AmigaDOS manual(s).
    These books are *not* tutorial in nature.

PUBLIC
    A memory attribute that must be specified if a section of memory is to
    be shared between two processes.  This will become critical when a MMU
    is added to the Amiga.

TASK
    The system's idea of a running program.  Each task thinks that it has
    the main processor all to itself.  Each task is wrong.  It will
    actually be sharing it with many other tasks.  Tasks that have nothing
    to do will Wait().   Waiting tasks take virtually no processor time.

TOOL
    Workbenchism for "program"

UUDECODE
UUENCODE
    Encode and decode routines that allow the transmission of binary files
    over normal text based mail systems.

VULCAN NERVE PINCH
    The CTRL-AMIGA-AMIGA reboot sequence.

WCS
    Writable Control Store.  This is the 256K of extra memory on the Amiga
    1000 that is provided to hold the contents of the Kickstart disk. The
    V1.1 and V1.2 operating system updates where distributed on disk.

WORKBENCH SCREEN
    The default screen that appears when the machine first starts up.  It's
    titled "Workbench Screen" and may, or may not, contain the workbench
    tool.

WORKBENCH TOOL
    The icon oriented interface to AmigaDOS.  This is normally started up
    when the machine is booted via the "LoadWB" command.  "LoadWB -debug"
    can be used to start up with an invisible debug menu.
Linux User (Arch & OpenSUSE TW) - WinUAE via WINE
 

guest11527

  • Guest
Re: A glossary of Amiga specific terms
« Reply #2 on: August 03, 2017, 11:01:35 AM »
Quote from: Pentad;828961
ARP
    AmigaDOS Replacement Project.  A holy crusade undertaken by Charlie
    Heath (of Microsmiths) to implement and distribute a free set of
    improved CLI commands, and programmer facilities.
To add to this, ARP succeeded in so far as most (all?) of the CLI commands of 2.01 where taken from ARP, i.e. the original BCPL versions were ditched. Also, major parts of ARP were integrated into the Os, most notably pattern matching (which went into the dos.library) and the file requester (which became asl.library). The only BCPL component left in 3.1 is the AUX-Handler.

To add to the RKRMs: I would not recommend the Bantam Books AmigaDos manual - it does not add much to the user manual people already got with the system, and the internal information it offers is rather weak. A better source for dos internals is Ralph Babel's Guru Book.
 

Offline Matt_H

Re: A glossary of Amiga specific terms
« Reply #3 on: August 03, 2017, 02:24:52 PM »
"BIMMER"

That one didn't really catch on, did it? ;)

Great post!
 

Offline EugeneNine

  • Jr. Member
  • **
  • Join Date: Aug 2016
  • Posts: 88
    • Show only replies by EugeneNine
Re: A glossary of Amiga specific terms
« Reply #4 on: August 03, 2017, 06:01:35 PM »
I remember a similar list from back in the day

It also had

CATS:  Commodore Amiga Technical Support
Gronk:  The sound the floppy disk head makes
RTFM:  please Read The Manual
 

Offline PentadTopic starter

Re: A glossary of Amiga specific terms
« Reply #5 on: August 03, 2017, 07:18:13 PM »
I thought ARP was amazing and started using it right away. Given that so many developers were coming from other platforms (many single tasking) I'm sure the Amiga was like nothing they had encountered before in terms of programming. So I'm sure this was a great resource. CATS really did a great job as well. I'm in 1987 and there are some great CATS people on here giving help, advice, and example programs.

Here are some other items I thought were interesting:


-IDK when George Robbins started living at Commodore but he was a madman at posting on Usenet. I didn't really know much about him until I started reading his posts and he was a heck of a nice guy. He and Dave Haynie posted a lot and then they seem to post in cycles.

-Matt Dillion was also a prolific poster.

-I didn't realize how popular emojis were even 30 years ago.

-People hated the concept of shareware. I mean hated it. I was really surprised at the amount of posts about this.

-The need for 2 MB of chip memory was being talked about from as early as 1986. I was surprised by this.

-Apparently Motorola started doing random drug tests at work and people really hated it. Fred Fish was quite outspoken about it.  Seemed like a great guy from his posts.

-Rob Peck posted some pretty neat projects he was working on. Voice recognition and the Amiga. A very nice guy (I was lucky enough to talk with him before he passed away).

-John Draper was one of the first people to buy an Amiga and develop for it. He was pretty active but then just disappeared. I think he got arrested for phreaking and was gone for a few years.

-Fred Bowen posted a lot on comp.sys.cbm about new hardware ROMs, support documentation, and just really supported the 8 bit line.

-I didn't know RJ had a son until I read his post...30 years later. :-)
Linux User (Arch & OpenSUSE TW) - WinUAE via WINE
 

Offline Pat the Cat

Re: A glossary of Amiga specific terms
« Reply #6 on: August 04, 2017, 02:14:47 PM »
One Amiga term I am very happy to see excluded is "Lamer". I always hated it, such a derogotory, smarta$$ putdown that meant absolutely jack. Why are people ever going to bother learning if they are permanently labelled as a retard?

Quote from: Pentad;829018

-John Draper was one of the first people to buy an Amiga and develop for it. He was pretty active but then just disappeared. I think he got arrested for phreaking and was gone for a few years.


News to me. Oh, he's still around. He's due to publish his memoirs and is crowdsourcing it now. He was just at Defcon and is currently freaking about Hutchin's arrest.

http://beyondthelittlebluebox.com/

Facebook page is

https://www.facebook.com/beyondthelittlebluebox/?hc_ref=ART35QzEyarotK2lEq-T0-Gk_THTzLBa7wRz_NBOK5f1eUHICTV0ruTT_RW_sO7hYtE&fref=nf

(Obviously not his personal page).

It's not like I'm best buddies with the guy, was a complete accident getting an intro to him just a few years ago.
« Last Edit: August 04, 2017, 02:16:56 PM by Pat the Cat »
"To recurse is human. To iterate, divine."

A1200, Vanilla, Surf Squirrel, SD Card, KS 3.0/3.z, PCMCIA dev
A500, Vanilla, A570, Rev 5, KS 1.2/1.3 Testbench system
Rasp Pi, UAE4ARM, 3D laser scanner, experimental, hoping for AmigaOS4Arm, based on Watterott Fabscan Pi
 

Offline PentadTopic starter

Re: A glossary of Amiga specific terms
« Reply #7 on: August 04, 2017, 08:31:02 PM »
Quote from: Pat the Cat;829071
One Amiga term I am very happy to see excluded is "Lamer".

I agree. I think it ranks up there with 'flaming' a new user for asking a question or the often posted 'RTFM'.  

One term I didn't see but heard a lot on the Amiga was "bang the hardware". This referred to bypassing the OS and talking directly to the hardware.

I too was surprised that John Draper was an Amiga user. I know he was was ill earlier this year.  Here is a link: https://venturebeat.com/2017/04/02/hacking-pioneer-john-draper-aka-capn-crunch-needs-funds-for-medical-help/

-P
Linux User (Arch & OpenSUSE TW) - WinUAE via WINE
 

Offline Pat the Cat

Re: A glossary of Amiga specific terms
« Reply #8 on: August 05, 2017, 03:42:43 PM »
Quote from: Pentad;829089

I too was surprised that John Draper was an Amiga user. I know he was was ill earlier this year. Here is a link: https://venturebeat.com/2017/04/02/hacking-pioneer-john-draper-aka-capn-crunch-needs-funds-for-medical-help/

-P

Not just a user, a coder? :)

I'm pretty sure he was busted twice, 70s and early 80s, and spent the early 90s raving and partying like most of us "sensible" folk. Certainly I've seen photos of that era with him in them. So I don't think he was imprisoned again after his second trial (which he maintains was a setup, a visitor used a blue box from his home to call him at an outside cafe).

Happily he reckons to have reached his health care fundraiser and is now running a sweepstake on the release of his memoirs - cut off date is September 1st, so should be around before then.
 
 
Quote from: Pentad;829089
I agree. I think it ranks up there with 'flaming' a new user for asking a question or the often posted 'RTFM'.
 
 The documentation for my Fabscan Pi consists of a sticky label saying "RTFM".
 
 The funny part is, there isn't one. Just a youtube video of assembly. How times have changed.
"To recurse is human. To iterate, divine."

A1200, Vanilla, Surf Squirrel, SD Card, KS 3.0/3.z, PCMCIA dev
A500, Vanilla, A570, Rev 5, KS 1.2/1.3 Testbench system
Rasp Pi, UAE4ARM, 3D laser scanner, experimental, hoping for AmigaOS4Arm, based on Watterott Fabscan Pi
 

Offline PentadTopic starter

Re: A glossary of Amiga specific terms
« Reply #9 on: August 06, 2017, 04:48:26 PM »
Quote from: Pat the Cat;829134
Not just a user, a coder? :)


I wonder what he was working on when his work was interrupted?  :-) Seriously though, I wondered if he was porting Easy Writer to the Amiga or doing something with graphics? He appears to have fallen off the Amiga platform entirely after this as I do not recall his name in the Amiga scene in later years.

He seemed like a nice enough guy and I'm glad that his health has stabilized. His book should be pretty interesting. I'm looking forward to reading it when I get some free time.

Most of the time the manual in RTFM was either non-existant or so poorly written that you couldn't make heads or tails out of it. When I was experimenting in the early days of Linux I recall seeing RTFM all the time on IRC and the few support forums. Crazy times...

-P
Linux User (Arch & OpenSUSE TW) - WinUAE via WINE