HDTenEightyP/NetNews huggingface dataset:
From: sue@cbmvax.cbm.commodore.com (Sue West - CATS)
Newsgroups: comp.sys.amiga.announce
Subject: Commodore Announces Winners of 4000 Reasons Contest
Date: 18 Nov 92 07:19:42 GMT
Article-I.D.: ucdavis.19366
Reply-To: sue@cbmvax.cbm.commodore.com (Sue West - CATS)
Followup-To: comp.sys.amiga.misc

[ Minor edits to improve formatting.  -Dan ]

The "Commodore Amiga 4000 Reasons Contest" is now over. The winning
entries, as selected by a panel of judges, are:

GRAND PRIZE: Amiga 4000 with 1960 monitor
WINNER: Eugene T. Cottle
REASON: "Since it was first introduced, the Amiga has been a pioneer.
        While IBM users anticipate the next innovation, Amiga owners
	are already using it."

SECOND PRIZE: Amiga 600HD with 1084S monitor
WINNER: Michael Fontana
REASON: "Used a MAC at school! Used an IBM at work. Bought an Amiga
        for home. To use it is to choose it!"

THIRD PRIZE (TIE): AmigaVision Professional
WINNER: David Klinkowize
REASON: "By using Amiga's audio/video applications, I started, at
        age fourteen, DWK Productions, my own video business, which
	will finance my college tuition."

WINNER: Mike Savin
REASON: "It's Advanced, Mind-blowing, Incredible, Graphics and Animation
        Has Awakened My Imagination Genius, and Artistry!  My AMIGA is
	an Astonishing Mesmerizing Indispensible Genuine Amiga (friend)!"
        (Mike prepared his entry quite artistically). 

There were over 2,500 entries . . . some humorous, some technical . . .
descriptive, graphic and on and on.

Commodore Business Machines, Inc. sincerely thanks all participants for
their time and efforts with this contest!

--
Read all administrative posts before putting your post up.  Mailing
list: announce-request@cs.ucdavis.edu.  Comments to zerkle@cs.ucdavis.edu.
MAIL ALL COMP.SYS.AMIGA.ANNOUNCE ANNOUNCEMENTS TO announce@cs.ucdavis.edu.
From: dsears@cie.uoregon.edu (Douglas Sears)
Newsgroups: comp.sys.amiga.announce
Subject: Origins -- genealogy program
Date: 16 Nov 92 09:04:11 GMT
Reply-To: dsears@cie.uoregon.edu (Douglas Sears)
Followup-To: comp.sys.amiga.misc


                 THE PUZZLE FACTORY ANNOUNCES

                          ORIGINS

The Puzzle Factory, Inc. has released Origins, a dedicated data base for
keeping track of genealogical information.  It will support databases of
over 6 million individuals.  The user interface is designed to be both
easy to use and very powerful.  Origins will correctly handle multiple
marriages, step-children, unmarried parents, and other difficult
situations that some programs refuse to allow.  Lists Persons, Marriages,
Parent/Child Index, Ahnentafel (direct ancestors), and Soundex (grouping
surnames by similar pronunciation).  Generates reports on Persons, Family
Group sheets, Pedigree Charts, Descendants Charts, and Tiny-Tafel
(a summary of your surnames).

Features include:  Automatically call your ARexx-compatible editor to
create Source and Note files.  These files may also be written and
displayed in hypertext format.

* Search on any combination of fields or by Soundex codes.

* Context-sensitive hypertext help is built in.

* Support for IFF files.  Pictures of individuals, marriages,
  baptisms, and family groups may be displayed instantly.

* Import and export data between Origins and other
  genealogical programs using the standard GEDCOM file format.

* Generate Tiny-Tafel listings for use with the Tafel Matching
  System.

* Many useful ARexx functions are included.
      
A single floppy data disk will hold approximately 2000 person and
500 marriage records.  Origins is not LDS compatible.

Origins requires V1.3 or later of the Amiga OS, at least 1 megabyte
of ram, and hard disk or 2 floppy drives minimum configuration.
Suggested retail price: US$85

For more information or to order, contact:

  The Puzzle Factory, Inc.
  P.O. Box 986
  Veneta, OR 97487
  800-828-9952  or  503-935-3709
  jlavin@cie.uoregon.edu

See The Puzzle Factory's ad in the October or December issue of Amazing
Computing or the Fall/Winter AC's Guide.

                           DEMO

There is a freely distributable demo version of Origins available, which
has a limit on the number of records, has some printing functions
disabled, and does not include the GEDCOM utilities.  The demo can be
found on BIX and CIS, and the demo file Origins.lzh (and Origins.readme)
are available for anonymous ftp at wuarchive.wustl.edu (128.252.135.4) in
the directory /systems/amiga/demos/commercial.

This announcement contributed by Doug Sears (dsears@cie.uoregon.edu) on
behalf of The Puzzle Factory, Inc. (I worked with TPF as a consultant on
parts of Origins).

--
Read all administrative posts before putting your post up.  Mailing
list: announce-request@cs.ucdavis.edu.  Comments to zerkle@cs.ucdavis.edu.
MAIL ALL COMP.SYS.AMIGA.ANNOUNCE ANNOUNCEMENTS TO announce@cs.ucdavis.edu.
From: koren@hpfcogv.fc.hp.com (Steve Koren)
Newsgroups: comp.sys.amiga.announce
Subject: PubChange commodity for OS 2.04
Date: 16 Nov 92 09:06:35 GMT
Reply-To: koren@hpfcogv.fc.hp.com (Steve Koren)
Followup-To: comp.sys.amiga.misc


TITLE:         PubChange
VERSION:       1.0
AUTHOR:        Steve Koren

DESCRIPTION:   PubChange is a commodity for AmigaDos 2.04.  It isn't a
               public screen manager, but it is useful when used in
               conjunction with one.  It is designed to make public
               screens easier to use.  Whenever a new screen is brought to
               the front, this screen is examined.  If it is a public
               screen, it is made into the default automatically without
               having to explicitly do it from within a public screen
               manager.  If not, it is left alone.  Thus, the current
               default public screen is always the one which you have most
               recently brought to the front, and applications which use
               the default public screen will appear there.  PubChange can
               also bring the previous (instead of next) screen to the
               front, or bring the workbench screen to the front.  In all
               cases, they are made into the default public screen if
               possible.

REQUIREMENTS:  AmigaDos 2.04 or later

FTP LOCATIONS: File name: PubChange010.lzh

               wuarchive.wustl.edu: systems/amiga/utilities/comodities [sic]
				    systems/amiga/incoming/utils

               amiga.physik.unizh.ch: amiga/os20/cdity
				      amiga/new

PRICE:         US$0.00

DISTRIBUTION:  Copyrighted freeware.  I won't email it, so don't ask.

--
Read all administrative posts before putting your post up.  Mailing
list: announce-request@cs.ucdavis.edu.  Comments to zerkle@cs.ucdavis.edu.
MAIL ALL COMP.SYS.AMIGA.ANNOUNCE ANNOUNCEMENTS TO announce@cs.ucdavis.edu.
From: caw@miroc.chi.il.us (Christopher A. Wichura)
Newsgroups: comp.sys.amiga.announce
Subject: CyberX10 v1.1 now available
Date: 16 Nov 92 09:26:50 GMT
Reply-To: caw@miroc.chi.il.us (Christopher A. Wichura)
Followup-To: comp.sys.amiga.misc

TITLE

	CyberX10

VERSION

	1.1	(first public release)

AUTHOR

	Christopher A. Wichura		(caw@miroc.chi.il.us)

DESCRIPTION

CyberX10 allows one to control the BSR X-10 CP290 computer interface from
their computer.  This allows one to turn lights and/or appliances off at
various times.

The X-10 line of control devices can be obtained from a number of places.  I
purchased mine from Radio Shack (where it is know as Plug'n Power instead of
X-10).  The CP290 costs about $80 US, while receiver units are generally
around $12-$15 US each.

CyberX10 has two modes of operation:

	1)  one can issue commands in direct mode so that the unit will
	    respond immediately.

	2)  one can create a human readable ascii event file using
	    a text editor and download this to the CP290's memory.
	    this programs the CP290 to act on its own and the device need
	    not remain hooked up to the computer's serial port.

Both modes are invoked from the command line (tooltypes that match the
command line options are recognized for those who wish to use Workbench icons
instead of the CLI).  No GUI interface is present, although it wouldn't be
difficult to create a program that provided one and shelled out to CyberX10
to actually talk to the CP290.

CyberX10 lets you dim, turn on or turn off any unit in direct mode, set the
CP290's clock to that of the Amiga's system clock, set the CP290's base house
code, download events to the CP290's memory as well as upload them to the
Amiga.

The documentation for CyberX10 comes in the form of an AmigaGuide document.

SYSTEM REQUIREMENTS

	Any Amiga computer running Workbench 2.04 or higher
	    Workbench 2.1 or higher required to make use of localization
	BSR X-10 CP290 Computer Interface

HOST

	amiga.physik.unizh.ch

DIRECTORY

	/amiga/hard/drivr

FILE NAME

	CyberX10.lha

DISTRIBUTIBALITY

	Freely redistributable

-=> CAW

Christopher A. Wichura                Multitasking.  Just DO it.
caw@miroc.chi.il.us  (my amiga)                          ...the Amiga way...
u12401@uicvm.uic.edu (school account)

--
Read all administrative posts before putting your post up.  Mailing
list: announce-request@cs.ucdavis.edu.  Comments to zerkle@cs.ucdavis.edu.
MAIL ALL COMP.SYS.AMIGA.ANNOUNCE ANNOUNCEMENTS TO announce@cs.ucdavis.edu.
From: caw@miroc.chi.il.us (Christopher A. Wichura)
Newsgroups: comp.sys.amiga.announce
Subject: CyberCron v1.5 now available
Date: 16 Nov 92 09:24:49 GMT
Reply-To: caw@miroc.chi.il.us (Christopher A. Wichura)
Followup-To: comp.sys.amiga.misc

CyberCron v1.5 is now available.  It is on amiga.physik.unizh.ch as
/amiga/os20/cli/CyberCron15.lha, has been uploaded to BIX in
amiga.user/listings as CybrCron15.lha and is also available from my machine
via BMS as BMS:Pub/CyberCron/CyberCron15.lha.

What is CyberCron?  It is a cron (stangely enough :->) that was written
specifically for any Amiga running Workbench 2.04+.  Having ARexx available
will increase its usefulness, but is not required.

For those that don't know what a cron is: it is a program which allows you to
specify certain commands to be executed at specific times without user
intervention.

CyberCron is no ordinary Amiga cron, however.  It supports, amoung other
things:

    1)  Uses the dos.library System() call to start jobs, providing greater
        flexibility in launching the job.  This allows for things like stack
        size, priority and shell to be specified on a per event basis.

    2)  Can directly launch ARexx commands and scripts without the need of
        the RX activator.

    3)  Output can be redirected to a file or __sent as mail to a user__
        (provided the system has a sendmail command).

    4)  Job queues similar to the UNIX cron allows for the UNIX commands
        'at' and 'batch' to be simulated via ARexx scripts (provided).
        Queues can also be used to insure sequencing of events, etc.

    5)  ARexx port supporting 22 commands.

    6)  Uses file notification to determine automatically when the crontab
        file has been modified and should be re-read.

    7)  Sensitive to small shifts backwards in time (such as might be caused
        by doing a SetClock LOAD once a day via cron) are noticed and
        accounted for.

    8)  Localization support under Workbench 2.1.

    9)  ...several more options exist too

Changes from v1.3 to v1.5 include the addition of several ARexx commands,
localization support when running under Workbench 2.1, better Workbench
support, various code tweaks, an enhanced at.rexx macro, a doc file
re-written in AmigaGuide format and one or two other miscellaneous things.

Check it out, you won't be sorry! :-)

-=> CAW

Christopher A. Wichura                Multitasking.  Just DO it.
caw@miroc.chi.il.us  (my amiga)                          ...the Amiga way...
u12401@uicvm.uic.edu (school account)

--
Read all administrative posts before putting your post up.  Mailing
list: announce-request@cs.ucdavis.edu.  Comments to zerkle@cs.ucdavis.edu.
MAIL ALL COMP.SYS.AMIGA.ANNOUNCE ANNOUNCEMENTS TO announce@cs.ucdavis.edu.
Newsgroups: comp.sys.amiga.programmer
From: mlelstv@specklec.mpifr-bonn.mpg.de (Michael van Elst)
Subject: Re: New hardware reference guide?
Organization: Max-Planck-Institut f"ur Radioastronomie
Date: Thu, 19 Nov 1992 13:49:39 GMT

In <1992Nov16.130752.18379@imada.ou.dk> breese@monet.imada.ou.dk (Bjoern Reese) writes:
>with or without a Guide, they will try. So I say, it is better
>to release a new Guide, in order to set guidelines and to
>prevent fatal errors.

Why ? The only thing a new hardware guide will do is speed up the rate
of programs that use the hardware directly in a way that seems to work.

Regards,
-- 
Michael van Elst
UUCP:     universe!local-cluster!milky-way!sol!earth!uunet!unido!mpirbn!p554mve
Internet: p554mve@mpirbn.mpifr-bonn.mpg.de
                                "A potential Snark may lurk in every tree."
Newsgroups: comp.sys.amiga.programmer
From: maniac@ronnie.cs.unlv.edu (Eric J. Schwertfeger)
Subject: Re: New hardware reference guide?
Reply-To: maniac@ronnie.cs.unlv.edu (Eric J. Schwertfeger)
Organization: UNLV Computer Science and Electrical Engineering
Date: Tue, 24 Nov 92 00:05:51 GMT

In article <paulk.2asu@terapin.com>, paulk@terapin.com (Paul Kienitz) writes:
) > Er, what is an AutoDoc?
)  
) > What i'd like to know is what C= actually object to.
)  
) I think I just said something about speaking from ignorance.  I
) didn't realize how right I was.
)  
) First question: the Autodocs are the official documentation of each
) function in the OS.  If you don't read the autodocs then you don't
) know the capabilities of the OS.  It really is that simple.  Not
) studying the autodocs == not knowing what you're talking about when
) you say what the OS can or can't do.

I really didn't want to get caught up in this one, but I agree completely.
Anyone who isn't familiar with the OS shouldn't flame it like they think
they know what their talking about.

I remember one Democoder that flamed the Amiga OS because "You can't open
a window without those ugly borders".  As for speed, yes the generic graphics 
routines aren't the fastest, but properly used, they do very well, and you can
get at some of the less generic routines in the OS, all well documented in
the RKM's.


-- 
Eric J. Schwertfeger, maniac@cs.unlv.edu
From: aurel@uni-paderborn.de (Aurel Balmosan)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: physical memory protection with MMU
Date: 17 Nov 1992 09:43:08 GMT
Organization: Uni-GH Paderborn, Germany
Distribution: worlD
NNTP-Posting-Host: miro.uni-paderborn.de
Keywords: mmu, memory, task

I think I found a way to handle memory protection which would work with 
all existing programs.
On condition that the MMU can handle any number of memory segments,
the system should distinguish between public memory (MEMF_PUBLIC) and
none public memory (allocated without MEMF_PUBLIC). If some task would 
access a public memory segment of an other there would be no 
MMU-interception. If a task try to access none public memory (not equal with 
non allocated memory!) a execption would be the result.

In practice, in the <task-switch> the task should insert his private memory
segments and in the <task-launch> the task should remove his private memory
segments. 

Note:	Each task has its normal address space.
	The MMU is used only for generating execptions.
	The MMU must handle any number of memory segments.
	In advaced use an allocated memory segment could have public and
	private (eg. libraries have public data and private data)


PS:	You don't need a MMU. You only need an execption generator(eg. BUS-Error).
	And this would be (easy) to build.

Could this a way to a real secure amiga ???

-- 
	Alexandru-Aurel Balmosan		aurel@uni-paderborn.de
	University of Paderborn (Germany)
Xref: sparky comp.sys.amiga.programmer:16280 comp.sys.amiga.misc:17360
Newsgroups: comp.sys.amiga.programmer,,comp.sys.amiga.misc
Subject: File comments
From: dave@dogbox.acme.gen.nz (David Dustin)
Date: Tue, 24 Nov 92 13:11:32 +1300
Followup-To: comp.sys.amiga.programmer
Organization: The Dawghaus BBS, Palmerston North, New Zealand (+64 6 357 9245)
Keywords: Strange characters

I have a question about the comment feilds of files.

I just brought a copy of DirOpus 3.41, and when I used it to check my
system, I foudn that some files had a strange character as the first
letter of the comment.

I have never noticed this before, and I had never seen it before.  If
I used the list command, or anything else which shows the comment, the
extra character is not shown.

After talking to my friend on the phone, we (well, he) suggested that
it might be the number of chatacters in the comment field.  And it
was.

According to "Mapping the Amiga" and several other books, the
character is the first of the 80 characters set aside for the comment.


Can anyone please tell me if this is ment to be here, and what we are
ment to do with it?  Am I ment to skip the first character, or what?

                                                                 :)ave
--
David Dustin             |  'How come I get all the hard questions?'
Dave@Dogbox.acme.gen.nz  |                                    - O. North
From: podesta@qut.edu.au
Newsgroups: comp.sys.amiga.programmer
Subject: Re: New hardware reference guide?
Date: 19 Nov 92 13:52:38 EST
Distribution: world
Organization: Queensland University of Technology

In article <mwm.2mi5@contessa.palo-alto.ca.us>, mwm@contessa.palo-alto.ca.us (Mike Meyer) writes:
>> And don't forget that demo coders don't get any wonderful Developers info.
> 
> For that, they have no one to blame but themselves.
> 

I have been told that you can't get Developer status unless you develop
non-demo, non-game software. Is this untrue?? Is it simply a matter of paying
money?? Otherwise, its not the demo coders' fault that they have no
Developers information, is it?

> 	<mike

James
From: bj@cbmvax.commodore.com (Brian Jackson - Amiga Networking)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: ANSI Cursor Controls
Date: 17 Nov 92 19:00:59 GMT
Reply-To: bj@cbmvax.commodore.com (Brian Jackson - Amiga Networking)
Organization: Commodore, West Chester, PA
Keywords: DOS, documentation

In article <1992Nov16.062618.26550@tamsun.tamu.edu> n298ad@tamuts.tamu.edu (John Jordan) writes:
>
>	Could someone please post or email a list of ANSI commands?
>Specifically I am looking for commands to adjuct the cursor position.
>Is there a command to do an exact (x,y) position of the cursor in 
>a shell window???
>Thanks in advance, 
>-JOhn
>n298ad@tamuts.tamu.edu
> 

This information is available in the chapter on the console device in the
ROM Kernel Manual - Libraries and Devices.

       +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +
       Brian Jackson    Amiga Networking Group, Commodore-Amiga Inc.
                        bj@cbmvax.commodore.com
     {uunet|rutgers}!cbmvax!bj    or   networking@cbmvax.commodore.com
                       uva uvam vivendo varia fit 


Newsgroups: comp.sys.amiga.programmer
From: wild@nessie.cs.id.ethz.ch (Markus Wild)
Subject: Re: GCC 2.2.2 and math functions
Keywords: gcc 2.2.2, unix math library
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Mon, 23 Nov 1992 17:35:55 GMT

In article <1992Nov23.015258.20036@marlin.jcu.edu.au> phsbs@marlin.jcu.edu.au (Simon Spagnol) writes:
>I can't seem to find some math functions like
>
>	y0, y1, yn, j0, j1, jn, lgamma,
>	erf, erfc
>
>in libm.a (or any .a file I have for that matter).

>To Mr Markus Wild, is there a possibility that
>this will be fixed/included in newer releases of
>gcc's libm.a?

Hmm... I didn't leave out functions on purpose... if they're available,
it has been an oversight, else the BSD code doesn't come with those functions?
There are some differences between AT&T libm and BSD libm..

-Markus
-- 
Markus M. Wild    -  wild@nessie.cs.id.ethz.ch  |  wild@amiga.physik.unizh.ch 
Vital papers will demonstrate their vitality by spontaneously moving
from where you left them to where you can't find them.
From: bjst@sth.frontec.se (Bjorn Stenberg)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: New hardware reference guide?
Date: 15 Nov 92 10:40:25 GMT
Organization: IDK/Frontec - System Design Group

breese@monet.imada.ou.dk (Bjoern Reese) writes:
> Consider this: "The more knowledge people have about the hardware the more
> likely their programs will work well."

Well, this HAS been tested for the past seven years, with little success...

		-- Bjorn

       ///  Bjorn Stenberg, Stockholm, Sweden         bjst@sth.frontec.se
      ///  main() { printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);}
 \\\ ///  "- Your documentation no longer confuses me, old version!"
Newsgroups: comp.sys.amiga.programmer
From: benjamin@cs.UAlberta.CA (Ben Ferreira)
Subject: gcc 2.2.2 unix/dev help
Organization: University of Alberta, Edmonton, Canada
Date: Thu, 19 Nov 1992 03:47:08 GMT

Can anyone tell me what's supposed to be in this dir?  The newly archived
version of gcc 2.2.2 on wuarchive didn't have the this directory and 
apparently it is needed to use genclass (I get all these 'insert /bin in any
volume' requestors).  

Ben
From: mwm@contessa.palo-alto.ca.us (Mike Meyer)
Subject: Re: New hardware reference guide?
Newsgroups: comp.sys.amiga.programmer
Distribution: world
X-NewsSoftware: Amiga Yarn 3.4, 1992/08/12 15:49:52
Keywords: 
Summary: 
Date: 17 Nov 92 14:01:11 PST
Organization: Missionaria Phonibalonica

In <1992Nov16.134153.6356@ifi.uio.no>, olavka@ifi.uio.no (Olav Lur}s Kalgraf) wrote:
> > We need blazing speed, not necessarily optimized assembly.  Two different
> > things.
> > 
> Different, true. But also very closely connected, optimized assembly
> means blazing speed. 

Not in the sense people usually mean when they say "optimized
assembly"; that of someone carefully scrutinizing code to squeeze the
last cycle out of it. Optimizing the wrong algorithm (the vector math
example mentioned earlier comes to mind) means you get fast code, but
a slow program.

In the more general sense of optimizing the entire program - looking
at large collections of sample data, choosing an algorithm that fits
it well, looking at the sample again and seeing where most of the time
is going, making that faster, etc - then assembly is sort of moot.
It's "optimized X means blazing speed", where X is pretty much
anything that isn't interpreted, and avoids provoking things with lots
of overhead. You can even do it with LISP, if you know how. 

That said, it's generally true that the closer you are to the
hardware, the easier it is to insure that you're not provoking
something with lots of overhead. A bad compiler could translate to
"lots of overhead". Even with a good compiler, there are gotchas. In
C, you have to worry about accidently invoking a support routine to do
your math; in LISP, you have to worry about using any routine that
does a cons.

	<mike
Newsgroups: comp.sys.amiga.programmer
Subject: GCC 2.2.2 Patch3
From: hoffmann@nutmeg.ntu.edu.au (Arthur Hoffmann)
Date: 16 Nov 92 23:32:46 +0900
Distribution: world
Organization: Information Technology, Northern Territory University

Hi, I just applied the third patch to the GCC 2.2.2 port of Markus Wild.
I really would like to know if the following are Error messages or if they are ok
the way they are.

ar: gcc:lib/libc.a: operation not supported by device
ranlib: gcc:lib/lib.a: operation not supported by device
ar: gcc:blib/libc.a: operation not supported by device
ranlib: gcc:blib/libc.a: operation not supported by device

Thanks a lot.

Arthur.

					Arthur Hoffmann
					hoffmann@nutmeg.ntu.edu.au
From: paulk@terapin.com (Paul Kienitz)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: New hardware reference guide?
Date: 20 Nov 92 18:45:31 PST
Organization: BBS

> I can't see why people give demo writters such a tough time. If the
> demo does not work on your machine, then just delete it.
 
We give them a tough time because they (you) want the rest of us to
support their style of programming, at the expense of the kind of
programming that actually improves the usefulness of present and
future Amigas.  Such as by creating yet another generation of
software that can't work with retargetable graphics.
Newsgroups: comp.sys.amiga.programmer