HDTenEightyP/NetNews huggingface dataset:
From: raist@rmece02.upr.clu.edu (Ricardo Hernandez)
Subject: SOLUTION FOR AGA's SPECS!
Organization: UPR-Mayaguez--ASEL Lab
Date: Thu, 19 Nov 1992 20:34:07 GMT

	There has been a gigantic fuzz about whether C= should release
the AGA hardware specs or not.  This is due that C= wants to ensure that
all new programs (or as much as they can) are written using the OS, so
that if there's an upgrade to the chipset, the programs will easily run.

	But also there is the group of people who want to bang the 
hardware directly, to get the most out of the machince... well, 
here's THE SOLUTION:  Use the...

 #####  #     # ####### ######
#     # #     # #     # #     #
#       #     # #     # #     #
 #####  ####### #     # ######
      # #     # #     # #
#     # #     # #     # #
 #####  #     # ####### #

######  ######  ####### ####### #######  #####  ####### #
#     # #     # #     #    #    #     # #     # #     # #
#     # #     # #     #    #    #     # #       #     # #
######  ######  #     #    #    #     # #       #     # #
#       #   #   #     #    #    #     # #       #     # #
#       #    #  #     #    #    #     # #     # #     # #
#       #     # #######    #    #######  #####  ####### #######


   What is the SHOP Protocol?  S]ystem H]ardware O]perating P]rocedures.

   Now, future software can run on AGA, X-AGA, Super AGA, Ultra-AGA and
the Super Duper RISC based with virtual reality copprocessors - AGA 
(SDRVR-AGA).  Here's how it works:

   Each time a program loads, and needs hardware banging (like BLAZEMONGER),
it will do some system querires.  Basic hardware registers will be
specified, like for example: HardwareScroll register, Sprite 0 DMA data
read register, etc. along with its data type (byte, word, long word).

   The SHOP Protocol will return the EXACT ADDRESS in hardware of those
registers.  Ah, yes, add also the BltCrl, BltStart, etc.  In that way,
the programs (including VR-BLAZEMONGER) will be able to access the 
hardware directly, but they will self-modify in such a way that no
matter how C= tries to make the new AGA's totally incompatible with
previous chipsets, the software (including EURO-DEMOS) will run 
without a glitch!

   Of course, a basic set of operations has to be specified, but the
SHOP PROTOCOL will get richer in hardware addresses with new releases
of AGA chipsets (like the scheduled for November 16, 2003 SDRVR-AGA, 
which can rotate, zoom, give pleasure and torture the users in real-time!).

   So all that C= has to do is define an abstract set of hardware registers,
support them with The SHOP PROTOCOL and voila!

  Happy Happy Joy Joy!

------------------------------------------------------
  Raist   // Amiga 500, 38Mhz Special MegaMidget Racer
        \X/  Avid user of AmigaVision, sending mail from Mayaguez, Puerto Rico 
---------
           "If the PC or Mac continues to be the standard,
            the SkyNet will never be built." - OUCH! were not my words!
From: eas3714@ultb.isc.rit.edu (E.A. Story)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: New hardware reference guide?
Date: 18 Nov 92 18:06:12 GMT
Organization: Rochester Institute of Technology
Originator: eas3714@ultb

In csg019@cch.coventry.ac.uk (-~=Zaphod=~-) writes:
>In nn.mpg.de> mlelstv@specklec.mpifr-bonn.mpg.de (Michael van Elst) writes:
>
>>This is hardly right. In most cases you will end with a program that
>>a)runs on some machines only 
>It would work on any amiga with the custom chips at location $DFF000.

Other considerations... Does the machine have $C0 Fast ram?  Or is it
$20? Or perhaps it doesn't have FAST ram in the original 24-bit address
space at all. (A3000, A4000).  The OS thinks about all these things, do
demo (or for that matter, game) programmers?

>>b)crashes with a new OS version or when started from system that is 
>>  booted further than the initial CLI.
>It would not crash under new OS versions, because it would only use a few
>bare essential routines like Forbid() and Permit().

Most just hit INTENA and DMACON, anyway.

>>c) does generate bogus displays on either NTSC or PAL systems.
>Depends what you mean by bogus displays.
>NTSC users would loose a portion of the screen due to the fact that the
>NTSC screen can't display as many lines at a PAL screen.

Well, I know what *I* mean by bogus displays.  How about one that
doesn't work at all...  And it's easy to fix... I think 90% of these
"demo" programmers are guilty of it too.  How 'bout waiting on a
scanline that doesn't exist?  I can't tell you how many of these "PAL
only" programs work on an NTSC machine by changing just one byte in a
test on DFF004/6 or in a copper list that generates an interrupt.  It's
absolutely ridiculous.  I can live with lossing a portion of my
display.. its gotta happen, but when it doesn't work at ALL, thats
stupidity.

>Easy enough to avoid, just :
>
>1.. Write another version where the graphics are kept withing a smaller
>area on the screen.

Ya, but of course, most of these programmers are too lazy to do so....
otherwise "PAL only" wouldn't be so popular a phrase.

>2.. Write a just an NTSC version, so all the lucky PAL owners have a chunk
>of screen missing (*not big OR clever CINEMAWARE*).

Or just center the NTSC size screen on a PAL display.  
 
>>d) risks hardware damage with things connected to the serial or parallel port.
>How could it *dammage* hardware?

I can't wait for the first complaint from a A4000 or A1200 owner when
one of these demos hits the wrong register and the display goes to 31Khz
on their 1084... You don't think THAT could damage hardware?  

The point is that the serial and parallel ports shouldn't even be
active, yet I've seen my modem lights flash during demos... most
annoying.

>>Ah, yes.. that's my experience with the creations from "demo coders".
>Are you sure?

tee hee hee.. 

-- 
"THAT is a DRY turtle.  That turtle is NOT moist!"
Ezra Story, a student at RIT, and
eas3714@ultb.isc.rit.edu, his trusty(?) mailing address.
Newsgroups: comp.sys.amiga.programmer
Subject: Re: AMIGA STINKS
From: hoffmann@nutmeg.ntu.edu.au (Arthur Hoffmann)
Date: 21 Nov 92 12:11:25 +0900
Distribution: world
Organization: Information Technology, Northern Territory University

In article <1686000005@chasque.apc.org>, fabianr@chasque.apc.org writes:
> 
> So you hate Amigas, eh? And you want to kill us too, how kind of you. At least you should post your name so we can know who is going to kill us.... 
> I think you should also clarify why you hate the Amiga (and Amiga Users)....
> 
> Regards,
>          Fabian           EMail: fabianr@chasque.apc.org
> 
> P.S. Remember you should always be polite....


Who cares? Let him mumble what he wants.
This person probably sits in the back and shows his friends how easy
it is to stir up those "Stupid Amiga Users". Just forget him.

Arthur.

					Arthur Hoffmann
					hoffmann@nutmeg.ntu.edu.au
From: Eco_-_Development@cup.portal.com
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  Matt Dillon: Where has he gone?
Date: Sat, 21 Nov 92 07:56:22 PST
Organization: The Portal System (TM)
Distribution: na
  <69308@cup.portal.com> <dillon.0rcd@overload.Berkeley.CA.US>

>In article <69308@cup.portal.com> Aurelius@cup.portal.com (Mark Christian Barnes) wri
t
>es:
>> Matt Dillon is alive and well. Judging from some return Email that
>>I recieved from him, in the last few weeks ( DICE bug reports and
>>such ), I'd guess that he has perhaps moved and gotten a new job???
>>Still, his well known internet addresses are still valid. Remember,
>>on of those addresses has "OVERLOAD" in it.
>>
>>                       Regards, Aurelius@cup.portal.com
>>
>>PS: if my guesses are right ... Best Wishes Matt.
>
>    Same job, new contract, overloaded...
>
>    For people who are worrying, the reason I've dropped DNet, AmigaUUCP,
>    and BSD 4.4 is to be able to concentrate on DICE and my job.
>
>                                        -Matt
>--
>
>    Matthew Dillon              dillon@Overload.Berkeley.CA.US
>    1005 Apollo Way             uunet.uu.net!overload!dillon
>    Incline Village, NV. 89451  ham: KC6LVW (no mail drop)
>    USA                         Sandel-Avery Engineering (702)831-8000

I have noticed your postings in NeXT/blah and I was wondering, since I am
purchasing a NeXT machine,  if you have written something that will allow your
Amiga and your NeXT to communicate at something other than the floppy level?
Also we are working on an intuition development environment/tools and would
like to support DICE.  If you would mail me the info I need we will register
with you and add DICE support to our system.
From: wolfe@wvnvms.wvnet.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Amiga Sprite Editors
Date: 19 Nov 92 04:40:04 GMT
Organization: West Virginia Network for Educational Telecomputing


   Hello.  I was wondering if anyone out there knew where I could get
   a copy of a sprite editor for an Amiga 500 with 1 meg of ram, and two
   floppies.
      Thanks.

                                        Wolfe
Newsgroups: comp.sys.amiga.programmer
From: wittb@nextnet.csus.edu (brian witt)
Subject: Re: How to program multi-threaded programs on Amiga ?
Summary: Strong Endoresment of David Navas!
Organization: California State University Sacramento
Date: Sat, 21 Nov 1992 06:42:47 GMT

I whole-heartedly endores all of David's statements, especially about
his SHADOW Jazzbench System.  I watched him *debug* it myself.
Navas2 for President!  :-)  :-)  :-)  :-)  :-)

In article <1992Nov13.232458.24242@oracle.us.oracle.com> dnavas@oracle.uucp (David Navas) writes:
>In article <1992Nov12.195317.19859@csus.edu> wittb@nextnet.csus.edu (brian witt) writes:
>>However, I realize you probably also want some sort of low proiorty/
>>high priorty scheme to handle the mouse and to handle screen updating.
[..]
>Or you can use SHADOW V and run your methods synchronously/asynchronously
>across as many processes at as many priorities as you like.

USE SHADOW -- CONVERT ALL SOFTWARE NOW!  (plug plug)

>SHADOW V will be available at a local ftp site near you as soon as I can
>coax netcom to stay alive long enough to transfer the 260k (compressed)
>file....  [Don't worry, the library is 27k or something like that, it's
>the 500k of Docs that come with it....]

>>	Open libraries and such first off.
>
>Problem -- CBM doesn't want you to share library bases anymore :(
I discussed this with Dale Luck.  Need better support from C runtime for this.

>>	At exit time, send the low priorty process a kill message.
>>	Then loop with a sleep() call until some global varaible is
>>	set to indicate OK to die.
*see followup message for explaination of this*

>SHADOW will cleanup your subprocesses automatically for you if you just
>use the AddAutoResource() call....
>It will also handle all the method dispatching automagically 
[..]
>You can have a method-dispatch create a new process for each invocation, or
>redirect each method into an arbitrary process, etc. etc.
>[where arbitrary process == SHADOW process, of course! :)]

For the really curious, check out NextStep user interface code.
Quite some magic; you just wrote your app.  Huge executables, though.. :-(

>>My knowledge goes up to ADOS 1.3 as I still have (and am typing on) an
>>Amiga 1000  !!!!!!!!!!
>>PS:  I'm looking for an Amiga 1000 ethernet adapter and a 68020 with MMU
>>     and memory plug-in (used OK).

>David C. Navas						dnavas@oracle.com
>Working for, but not speaking on behalf of, Oracle Corp.

I'm also in need of a replacement A1000 keyboard.  Many keys ares sticking, 
including "A", "I", "1", which makes vi hell, and bang-paths can get hariy.

--- brian witt
============================================================================= !
   Brian Witt  [Sac State Computer Science]   "Waldo, the pariot, is dead"
   Internet:  wittb@cube01.ccs.csus.edu               -- Agent Cooper
                #define  POSIX_ME_HARDER     1       <-- GNU

-- 
============================================================================= !
   Brian Witt   Sac State Computer Science]   "Waldo, the pariot, is dead"
   Internet:  wittb@cube01.ccs.csus.edu               -- Agent Cooper
                #define  POSIX_ME_HARDER     1       <-- GNU
From: andy@cbmvax.commodore.com (Andy Finkel)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: New hardware reference guide?
Date: 20 Nov 92 01:06:50 GMT
Reply-To: andy@cbmvax.commodore.com (Andy Finkel)
Organization: Flying Cat, Inc.

In article <1992Nov13.211221.1609@freenet.carleton.ca> aa302@Freenet.carleton.ca (Russell McOrmond) writes:
>know you are a Welmat user and by your definition Welmat is
>a poorly written package because it has to hit the hardware in order
>to get control over the DTR line on the internal serial port.  It would
>be seconds for CBM to fix this blatantly obvious bug that they were informed
>of quite some number of years ago, but so far they have not.

Closing the serial.device drops DTR;  its done so for a long time;
(possibly forever :-) )  and is what I do when I need DTR low.
Since I seldom need to send data through a modem that is offline,
closing the device is no hardship.  When I want to raise DTR, I
open it again.

>  I myself don't know much about the reasons why other hardware is hit, but
>from this simple example I bet there are legitimate reasons for getting
>around bugs in the O.S.

I can't really imagine a good reason for not using th Open/Close method,
but I assume the author of Welmat did.  That's basically the problem;
someone can always think of a reason (valid or not) to hit the hardware.

> Russell McOrmond, Ottawa Ontario, Canada    | Standard Disclaimer applies.


			andy

-- 
andy finkel		andy@cbmvax.commodore.com

"Unix is the Operating System of the future, and always will be."

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.
Newsgroups: comp.sys.amiga.programmer
Subject: Re: GCC 2.2.2 Patch3
From: hoffmann@nutmeg.ntu.edu.au (Arthur Hoffmann)
Date: 18 Nov 92 20:24:12 +0900
Distribution: world
Organization: Information Technology, Northern Territory University

In article <1992Nov16.233246.4252@darwin.ntu.edu.au>, hoffmann@nutmeg.ntu.edu.au (Arthur Hoffmann) writes:
> 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
Hi, I am sorry to write again about it.
I found the reply that Marukus Wild sent, but when I wanted to read it I got a
requester saying something about filesystem full and stuff like that and xrn
wouldn't let me read it, so I  really would apreciate it if you could resend your
reply, maybe via email? 

Thanks a lot Markus.

Arthur.

					Arthur Hoffmann
					hoffmann@nuntmeg.ntu.edu.au
Newsgroups: comp.sys.amiga.programmer
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re: Trivial thoughts on SAS/C 6.00
Originator: walker@twix.unx.sas.com
Date: Wed, 18 Nov 1992 14:52:37 GMT
Organization: SAS Institute Inc.


In article <1992Nov18.171128.58776@qut.edu.au>, barham@qut.edu.au writes:
|> 1) This is the really really SUPER DOOPER trivial one.  When you open
|>    se (that editor of all editors... %^), it seems if you resize the
|>    window before all it's rendering has been done se it doesn't realise
|>    the fact and you end up with that horizontal bar that seperates the
|>    edit area from the area down the bottom (where you input stuff like
|>    what to search for etc) in a really wierd place.  I can't always get
|>    it to do this for me, but it happens with reasonable regularity.

Yes, we've seen this too, but haven't been able to track it down 
exactly.  Since it's more in the category of an annoyance than
a show-stopper, we haven't gone all-out on it yet.

|> 2) Now the serious BUG TO END ALL BUGS - when the Global Optimiser is
|>    running, any warnings it puts up (like "removing dead assignment" or
|>    something) don't get sent to the message browser.  This is not a real
|>    buggy bug in the actual "bug" sense of the word, merely an enhancement
|>    request I suppose.

That's already on the planned enhancement list.  Also the assembler
messages should go there.

|> 3) This is just an irritation - I am only running on a lowly 68000, and
|>    for some reason se gets REALLY SLOOOOOOW when you are adding or
|>    deleting characters in a line of which part is selected as a block

It's probably being forced to redraw the block highlighted, I'll ask
Steve to look into it after we get done with the 6.1 patch.

|> It is a great package (though you should get a graphic artist to design
|> your default icons - want me to send you some good ones based very closely
|> on yours but tidied up in a huge way?), many very useful enhancments

Thanks, and I'll pass your feedback along to our graphic artist 8^)
Sure, I wouldn't mind seeing some new icons.  I assume that you
have replaced ours with yours at this point?

|> | Tim Barham (t.barham@qut.edu.au)    |                              |

-- 
  *****
=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
 *|. o.| ||                                          1200/2400/9600 Dual
  | o  |//     For all you do, this bug's for you!
  ====== 
usenet: walker@unx.sas.com                            bix: djwalker 
Any opinions expressed are mine, not those of SAS Institute, Inc.
From: bn@mndcrme.uoknor.edu (Bo Najdrovsky)
Subject: Re: GadToolsBox Compiling Questions.
Newsgroups: comp.sys.amiga.programmer
X-Newsreader: TIN [version 1.1 PL6]
Date: 15 Nov 92 21:12:21 CST
Organization: Operation Mindcrime

William Waring (willw@extro.ucc.su.OZ.AU) wrote:
:
: Yes very close, but how about a gadtools.library and maybe an
: intuition.library! I bet it crashes. I must say that Jan Van den Baard
: (Sorry if I spelt it wrong) should be shot for not mentioning the fact
: that you need to open libraries in the code. If that doesn't fix it, then
: please let me know.

In Jan's defense I would like to point out that he uses DICE (great product!)
which automatically opens the libraries for you.

Newsgroups: comp.sys.amiga.programmer
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re: Unusual SAS6.0 results
Originator: walker@twix.unx.sas.com
Date: Tue, 17 Nov 1992 14:44:00 GMT
Organization: SAS Institute Inc.


In article <BxtxyK.C72@fc.hp.com>, koren@fc.hp.com (Steve Koren) writes:
|> Doug Walker (walker@twix.unx.sas.com) wrote:

|> Ok, I'll do that.  I don't doubt that strncpy is somehow being
|> referenced.  I still find it odd, however, that when I run the program
|> under CPR it never once hits strncpy, yet the profiler claims I'm
|> spending ~95% of the time there.  Something's fishy...

We did also fix an lstat bug... perhaps that will fix this problem.
The lstat bug we fixed was present in V5.10 as well as V6.0, though,
so it may not be the culprit here.

|> example for SAS tech support.  I don't think its reasonable to expect
|> them to dig through something large, but trying to come up with a small
|> test case could be a whopping lot of work.  In fact, if I trim much, my
|> program won't work any more.  I guess this is the standard problem when
|> trying to report potential compiler/profiler problems.

True... If access to the source code is not a "trade secret", go ahead
and send it in and let us take a look.  If it is, then perhaps we can
sign a nondisclosure or something - we've done it before when working
on compiler bugs.

If you want to send us JUST the executables, send one compiled with
V5.10 and one compiled with V6.0, and make sure that symbols are
included in the executable.  We might be able to figure it out
just from that.  Sending the source increases our odds, of course.
(Sending instructions on how to run it increases them even more 8^)

|>   - steve

-- 
  *****
=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
 *|. o.| ||                                          1200/2400/9600 Dual
  | o  |//     For all you do, this bug's for you!
  ====== 
usenet: walker@unx.sas.com                            bix: djwalker 
Any opinions expressed are mine, not those of SAS Institute, Inc.
From: kontos@clipper.ingr.com (Thorne Kontos)
Newsgroups: comp.sys.amiga.programmer
Subject: SAS5.10 includes - a question
Date: 21 Nov 92 20:34:48 GMT
Organization: Intergraph Advanced Processor Division - Palo Alto, CA

I purchased the Lattice/SAS 5.10 a few years back and they came with
the 2.0? includes. Are these 2.04 includes or just 2.0 includes?

Will the upgrade to 6.0 provide the proper includes? 2.04/2.1/3.0

E-mail please - save bandwidth... T. K. Kontos
                                  kontos@clipper.clipper.ingr.com
From: barham@qut.edu.au
Newsgroups: comp.sys.amiga.programmer
Subject: Re: A Style Guide Question
Date: 24 Nov 92 11:27:24 EST
Organization: Queensland University of Technology

dave@dogbox.acme.gen.nz (David Dustin) writes:
> tim@cbe.qut.edu.au (Tim Barham) writes:
> > Normally, this would be the case, with the enter key deactivating
> > the text box so you could then use the keyboard short-cut key (as
> > per the style guide).  If the enter key just takes you to a new
> > line (as I mentioned above), then we have a problem.  How are the
> > Amigas two return keys labelled?  Enter and return?  I can't
> > remember, it's at home.  If so, the return key could take you to
> > the next line and the Enter key deactivate the text box (ie Enter
> > normally means "accept the text" and return is short for carriage
> > return, or a new line on a type writer).  Not very elegant I
> > agree.
>
> But then you run into a problem of using it on a A600, which has no
> NP, therefore, no Enter key.

That it one of the main reasons I said this was not a very elegant
solution, and why I think this situation really poses a problem.
While I am in no way sure the situation of a multiline text box is
what the initial poster was on about, I think that it is a problem
that needs a solution, because I'm sure a multiline text box (that
lets you enters text, of course) would be something that a lot of
people would want to use, and we need some keyboard only way to get
out of it (for "orthogonality" of user interface?) - Return is not a
solution as it should take you to a new line.  Even the old TAB key
is a bit dubious because you a bery likely to want to use the TAB key
in a multiline text box - so what's a solution that's consistent with
the current style recommendations?  Anyone from Commodore want to
comment?

Tim.

-- 

----------------------------------------------------------------------
| t.barham@qut.edu.au (Tim Barham) - "Dances with Mice"              |
| Applications Programmer for the Computer Based Education Section,  |
| Queensland University of Technology, Brisbane, Qld, Australia      |
----------------------------------------------------------------------
| "You're so open-minded that your brain leaked out..."              |
----------------------------------------------------------------------
From: s442013@nexus.yorku.ca (Ray Frederick)
Subject: kprint and null modem solved
Organization: York University
Date: Sat, 21 Nov 1992 20:53:22 GMT

Sorry about the previous post. I read the documentation more carefully and
found out that in order to connect two Amigas via the serial port a null
modem cable is needed. I just picked one up today and I'm happily debugging
at 9600bps.

Thanks, Ray. 	s442013@nexus.yorku.ca

Newsgroups: comp.sys.amiga.programmer