HDTenEightyP/NetNews huggingface dataset:
From: nilsco@ifi.uio.no (Nils Liaaen Corneliusen)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: PAL or NTSC, how to c
Date: 5 Nov 92 11:31:59 GMT
Organization: Dept. of Informatics, University of Oslo, Norway
Originator: nilsco@kolsaas.ifi.uio.no


In article <1992Nov5.095622.9939@ifi.uio.no>, olavka@ifi.uio.no (Olav Lur}s Kalgraf) writes:
> This offset is VBLANKFREQUENCY, but there is a small catch with using 
> this byte. It does NOT change EVER. Even if you change from PAL to NTSC
> using the screenmode prefs program. You can use this byte to determine
> the clocking of the CIA's =) but little else. :(

So what is the point in having and offset called PowerSupplyFrequency that
in most cases would be just the same? If you set NTSC in the bootmenu on
A4000 what does it say then?

Anyway, why should that setting change? It occurs a bit strange that data
concerning screenmodes should be put in execbase. There must be an easier
to determine the mode of the wb screen...

------------------------------------------------------------
INCLUDE "disclaimer.i"                     snail-mail:
Nils Corneliusen                           Heyerdahls vei 17
internet: nilsco@ifi.uio.no                OSLO, Norway
Newsgroups: comp.sys.amiga.programmer
From: brett@visix.com (Brett Bourbin)
Subject: Re: 3.0 includes
Date: Sat, 7 Nov 1992 18:42:53 GMT
Reply-To: brett@visix.com
Organization: Visix Software, Reston, Virginia

In article <1992Oct30.071635.5298@desire.wright.edu>  
fheitkamp@desire.wright.edu writes:
> 	I called Commodore, and a very nice lady named TJ told me the
						       ^^
> 	3.0 includes will not be available to the general public for
> 	a couple of months.  :-(

I think you mean "EJ". You could always join one of the Developer  
programs. 8^)
--			       __
Brett Bourbin		\  / /(_  /\/  11440 Commerce Park Drive
  brett@visix.com	 \/ / __)/ /\  Reston, Virginia 22091
  ..uupsi!visix!brett	 Software Inc  703.758.8230
From: fheitkamp@desire.wright.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Re: What kind of hardware? (was Re: New hardware reference guide?)
Date: 13 Nov 92 06:34:52 EST
Organization:  Wright State University 

In article <1992Nov10.124937.26690@imada.ou.dk>, breese@monet.imada.ou.dk (Bjoern Reese) writes:

>> There are (OS) routines for checking things like that. Please surprise me
>> with a reason why these routines wouldn't be good enough.
> 
> Which routines? I may be an ignorant fool, but I honestly don't know.
> 
> 
	I don't know if this will help, but there are several functions
	you could use to find out what CPU etc.  These are in the ExecBase
	structure and there are also some structures in the intuition or
	graphics library that will let you check which agnus and denise
	you have.  I can't find them right now but I've seen them.

	Now if you want to do it directly without going through the OS. I 
	don't know.  Do you have the RKMs?
> --
> 
> Bjoern Reese                   |     Email: breese@imada.ou.dk
> Odense University, Denmark     |     Voice: +45 65 932 182 (private)
Fred
From: dobrien@sybase.com (Dave O'Brien)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Where can I get example CanDo Decks
Date: 4 Nov 92 22:23:22 GMT
Organization: Sybase, Inc.
X-UserAgent: Nuntius v1.1

In article <12177@hq.hq.af.mil> Scott D Nolan,
snolan@postmaster@hq.af.mil writes:
>The subject says it... Anyone know a BBS or
>ftp site where there are some CanDo decks of
>varying levels of complexity that could help
>me learn to use this tool.

One place to look is the Inovatronics BBS at (214) 342-1930. Most
neighbourhood BBSs should also have homegrown decks. You should also be
able to find some FTP sites, but I don't have any specific addresses
since I don't have FTP access.

I'm waiting for my CanDo 2.0 upgrade, so I can finish up my first few
decks.

Hope this helps...
Newsgroups: comp.sys.amiga.programmer
From: mortene@Lise.Unit.NO (Morten Eriksen)
Subject: Re: New hardware reference guide?
Organization: Norwegian Institute of Technology
Date: Tue, 10 Nov 92 13:57:06 GMT

>csg019@cch.coventry.ac.uk (-~=Zaphod=~-) writes:
>> The fact is, what ever you can do in the OS in 4 frames using the OS, a good
>> demo programmer would probably do in 100 raster lines, and make it work on
>> any machine.
>
>Yeah, sure.
>Can you give me the names of 10 advanced demos which all work on the full
>range of Amigas (A500, A500+, A600, A1000, A1200, A2000, A3000, A4000)?
>
>No, I didn't think so either...
>
>		-- Bjorn

So, please give us the names of 10 great democoders which all have unlimited
access to all the computers you mentioned.

Nope, didn't think so either...   ;)

Morten
From: dave@dogbox.acme.gen.nz (David Dustin)
Newsgroups: comp.sys.amiga.programmer
Subject: Assembly access to IFFParse
Date: Fri, 06 Nov 92 22:12:00 +1300
Organization: The Dawghaus BBS, Palmerston North, New Zealand (+64 6 357 9245)

Can SOMEONE please give me some help with this.

I want to make use of the IFFParse Library via assembly (Devpac).

What I basicly want to do is, Load a file, then either display the 
graphic in a Window/Screen or make it available so I can change/use it 
later on. (say, cut bits out of the picture to use as blocks for a map 
editor (i'm working on a game, and want to work with IFF files)

PLEASE HELP!!!!!!!!!!!!!!!!!!!!!!!!

                                                                 :)ave

--
David Dustin             |  "Nice jail.  Looks strong."
Dave@Dogbox.acme.gen.nz  |                               - H. Houdini
From: hemmer@hemmer.adsp.sub.org (Franz Hemmer)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: SAS/C 6.0 stdio prototypes
Date: 5 Nov 92 01:19:30 GMT
Reply-To: hemmer@hemmer.adsp.sub.org (Franz Hemmer)
Organization: Interactivsion
X-NewsSoftware: GRn 1.16e (7/4/92) by Mike Schwartz & Michael B. Smith

In article <68769@cup.portal.com> Fred_M_Hamilton@cup.portal.com writes:

> Can anyone tell me why this seemingly innocent SAS/C 6.0 code as this:
> --------------------------------------------------------------------------
> #include<stdio.h>
> #include<clib/alib_stdio_protos.h>
> 
> main()
> {
> 
>    printf("Help me, world!");
> 
> }
> --------------------------------------------------------------------------
> causes lots of compiler errors, such as:
> 
> LONG  __builtin_printf ( STRPTR fmt, ... );
> include:clib/alib_stdio_protos.h 18 Error 72: conflict 
> with previous declaration.  See line 98 file "include:stdio.h"
> 
> I thought I was including the prototypes like I was supposed to.

Well you're referring to both sc.lib's and amiga.lib's printf() code,
which is faulty. Remove the second #include line to get the printf()
code from sc.lib, or remove the first #include to get printf() from
amiga.lib (I won't recommend it :).

> -Fred

-- 

Best regards                    Reply to: hemmer@hemmer.adsp.sub.org
Franz Hemmer                    #include <stddisclaimer.h>
Software Developer       _      >> Carpe Diem! - Seize the day! <<
                         \\ _
                 Interacti\X/ision - The name of precision
Newsgroups: comp.sys.amiga.programmer
From: jamie@cdevil.unx.sas.com (James Cooper)
Subject: Re: cmpi.l #,d16(pc) with SAS6asm, A68K, etc
Originator: jamie@cdevil.unx.sas.com
Date: Thu, 12 Nov 1992 16:14:12 GMT
Organization: SAS Institute Inc.


In article <BxKq3t.E9q@unx.sas.com>, jamie@cdevil.unx.sas.com (James Cooper) writes:
>
>In article <69309@cup.portal.com>, Aurelius@cup.portal.com (Mark Christian Barnes) writes:
> [various arguments about whether (d16,pc) mode is legal for cmpi on
>  68000 deleted]
>
>Now the acid test is to execute this statement on a 68000, and see if it
>works or not... well, it doesn't crash my machine, but I'd have to spend
>a few minutes writing to actually see if it works or not...  :-)

O.K.  I did some tests here, with an assembler which will work with this
addressing mode for this instruction.

Sample program:

        section code
        moveq   #0,d0
        cmpi.l  #1,12(pc)
        beq.b   1$
        moveq   #5,d0
1$:
        rts
        
        dc.l    1,1,1,1

        end

Results:

Above program work fine on both 68000 and 68030 (my only test processors
available) for sizes of .W and .L.

However, the .B size only works on my 68030.  The instruction:

        cmpi.b  #1,12(pc)

causes a illegal instruction exception on a 68000.

So, can we forget about this now?  The answer to the original question
is that yes, this should be allowed, but the .B size should be illegal
unless you are assembling for an '020 or greater.

-- 
---------------
Jim Cooper
(jamie@unx.sas.com)                             bix: jcooper

Any opinions expressed herein are mine (Mine, all mine!  Ha, ha, ha!),
and not necessarily those of my employer.
Newsgroups: comp.sys.amiga.programmer
From: rittle@supra.comm.mot.com (Loren James Rittle)
Subject: Re: SAS/C 6.00 & ANSI & Strict and C='s includes
Organization: Land Mobile Products Sector, Motorola Inc.
Date: Thu, 5 Nov 1992 07:58:36 GMT
Keywords: n

In article <1992Nov4.192404.1147@jupiter.sun.csd.unb.ca> mctaylor@mta.ca writes:
>Why does my program get lots of warnings when I use ANSI and Strict for
>the messages, not from my program but from within the C= includes. The

Because the fine people at C= haven't gotten around to updating the C=
includes to be %100 ANSI compliant.  I hope that the 3.0 includes fix
these problems.  Actually, I'll take the 3.0 includes in any form at
this time... :-)

>warning I am talking about is 149, something abouts structs. I would think
>that SAS would of picked this up. I am using the uncompressed headers.
>Not much else I can think that would effect it. So why does it do it?

As a SAS/C beta tester, I asked them to include something like
the following in the 6.0 manual (it may be there somewhere even
--- I haven't reread the entire new manual yet):

To compile without warnings with the STRICT ANSI WARNING=ALL
options enabled on SC, you must place the following around
any #include statements that refers to C= OS includes:

Before including one or a set of C= includes:

#pragma msg 148 ignore push
#pragma msg 149 ignore push
#pragma msg 61 ignore push

After including one or a set of C= includes:

#pragma msg 149 pop
#pragma msg 61 pop

Note that msg 148 can't be reset after the includes or a warning/error
will be flagged every time certain items in the includes are referred
to.

Hope this helps.  I used the above to get my version of ls to compile
under 6.0 with all warning enabled.

Regards,
Loren
--
Loren J. Rittle (rittle@comm.mot.com)
Systems Technology Research (IL02/2240)
Motorola, Inc.
(708)576-7794
From: rob@spirits.ka.sub.org (Roland Bless)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Want a PD LISP interpreter
Date: Tue, 10 Nov 1992 20:35:01 GMT
Organization: Blessed Software Products, private, Karlsruhe (FRG)
Content-Type: text/plain; charset=ISO-8859-1
X-Newsreader: Arn V1.00 pre

In article <1dc5ofINNgb2@usenet.INS.CWRU.Edu>, Kevin A. Roll writes:

> The subject pretty much says it all: I'm looking for a PD LISP interpreter.
> Anyone know where I can find one?

Try AMXLisp from Fish-Disk 181.

Regards,
 Roland
--
R o l a n d   B l e s s |UUCP/USENET: rob@spirits.ka.sub.org        IRC: rob|
Groetzinger Strasse 44  |BITNET: UKG5@DKAUNI2.BITNET      FAX: +49211623818 |
7500 Karlsruhe - FRG    |---------spirits--in--the--material--world---------|
voice +49 721 497381    |           Die Menschheit lernt nie. Aus.          |
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: GadTools and String Gadget Callback Hooks
Date: 5 Nov 92 13:21:02 GMT
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore-Amiga, Inc.  West Chester, PA.

In article <1992Nov5.025409.17427@u.washington.edu> cooper@carson.u.washington.edu (Ken Cooper) writes:
>
>     I have been unsucessfully trying for a couple of days to get string gadget
>callback editing hooks to work with GadTools STRING_KIND gadgets.  I have 
>been able to successfully do this with regular intuition string gadgets, but
>the gadtools gadget does not seem to call the hook.  I would appreciate it if
>someone could provide some insight on whether or not the callback hooks
>actually work with gadtools gadgets or not.

GadTools string gadgets _are_ Intuition string gadgets, with a friendly
creation/handling/deletion wrapper.  String edit hooks work fine.
ASL uses them.  Use the GTST_EditHook tag, with a pointer to your hook
structure.  The same hook that works for your own hand-defined string
gadgets will work with GadTools string and integer gadgets.

#define GTST_EditHook        GT_TagBase+55 /* String EditHook */

>Ken Cooper

     Peter
--
Peter Cherna, User Interface Development Group, Commodore-Amiga, Inc.
{uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"I believe it's bad luck to be superstitious."
From: mark@zeno.fit.edu (Mark Craig)
Newsgroups: comp.sys.amiga.programmer
Subject: Help!  Anyone know GURU numbers?
Date: 10 Nov 92 16:40:31 GMT
Organization: Florida Institute of Technology

Lately I've been getting some GURU #'s that aren't listed in my list of
Guru #'s (80000025 and also another one I can't remember).  I figured
my chart was out of date so I looked at 2.04's /include/exec/alerts.h
file and it isn't in there either (which really says something about how
worthless these guru numbers are :-) )  BTW, I have an Amiga 2000
running 2.04 and the revision comment on alerts.h says 2.04 so I know
I'm looking at the right alerts.h file.  I think 80000025 would be
something to do with out of memory (since that was the state I was in at
the time).  HOWEVER, I don't just want to know what it is, I want an
updated file (or whatever) of ALL Guru #'s... It really amazes me that
alerts.h doesn't have all the #'s (at least the one I have)...
    Thanks...

Mark Craig
mark@zach.fit.edu

-- 
***************************************************************************
* FLORIDA INSTITUTE of TECHNOLOGY                 //                      *
* Dept. of Computer Science                      //    Mark R. Craig      *
* 150 W. University Blvd., Melbourne, FL 32901  //   mark@zach.fit.edu    *
From: Lee_Robert_Willis@cup.portal.com
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Amiga Application Framework
Date: Sat,  7 Nov 92 17:10:57 PDT
Organization: The Portal System (TM)
Distribution: world

>In article <68764@cup.portal.com> Lee_Robert_Willis@cup.portal.com writes:
>
>> ABSTRACT:  
>> 
>>    I'm trying to develop an application framework skeleton that will
>>    work for 99% of Amiga Intuition programs.  Before I invest too
>>    much time in this, I'd like to know if this has already been done.
>
>Well, we have ToolMaker and GadToolsBox, both of which are far from
>perfect. 

NO NO NO NO!  Read it again.  I'm NOT looking for an Interface builder.
I'm looking for documentation on the 'best' software architecture.
i.e. how (whether by hand or by program) to structure one Amiga application
so that one can easily modify it, and add all the niceties (Multiple
screens, projects, ARexx, Font indepedence, etc.) that is recommend
in the Amiga User Interface Style Guide.

>
>> But (and this _is_ something of a criticism) I've never seen any C= document
>> that does tell you the "best" way to structure a full-blown application to
>> avoid these pitfalls. (I'm not a developer, just a hacker.  Perhaps C= has
>> such a thing for developers.)
>> 
>> So has anyone heard of this?
>
>Yes! David N. Junod has written 55308 bytes about 'Modular Event Processing',
>which presents an excellent scheme for processing events from multiple
>sources! The document is in some older AmigaMail issue, propably in some
>1989 issue.

Can someone tell me which issue?  That's at least a start.

Lee      Lee_Robert_Willis@cup.portal.com
From: bjst@sth.frontec.se (Bjorn Stenberg)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: New hardware reference guide?
Date: 5 Nov 92 18:49:16 GMT
Organization: IDK/Frontec, Sweden


 cs_e445@ceres (Vlod Kalicun) writes:
>Hmmm.. I was hoping to see some nice 3d graphic demos in 256000 colours!
>:-)

You will, except that this time the stuff might work on *ALL* machines instead
of just the one it was programmed on...

		-- 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!"
From: Roger_Nordin@atb.bbs.bad.se (Roger Nordin)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: New hardware reference guide?
Date: 6 Nov 92 22:33:48 GMT
Reply-To: Roger_Nordin@atb.bbs.bad.se (Roger Nordin)
Organization: ANet Test Bench, Karlstad, Sweden
OD-Comment-To: Internet_Gateway

> This seems a bit silly, for two reasons:
> 
>         1) It would be interesting to read about the AGA chip-set
> 
>         2) Someone, somewhere, sooner or later, will disassemble the 3.0
>            Kickstart to figure out how to program the new chips directly
>            (I would, if I had the ROM... :-( ), and there's nothing to stop
>            that person releasing any information they may find.

It is not the least silly, IMO. Previously, programming the PAD hardware 
directly have been accepted and supported by C=. It no longer is, because it 
causes too much trouble with chip and RTG OS upgrades. It creates an illusion 
that your code will work on all future machines if you follow the guidelines 
in the hardware reference manual.

Something that would indeed be very silly, would be to release official 
documentation on programming practices that C= no longer supports!

With Release4 in the not-so-distant future (yes, I'm an optimist if you are 
wonderig :)) with Device Independant Graphics, we need to get rid of the 
hardware hacking. Therefore, Release3 has been vastly improved in most areas 
regarding speed and available functions with it comes to graphics and 
animation. Use the Operation System, or die, with future machines.

Definatly a step in the Right Direction!

                        _       .    __
    Roger Nordin     _ //      /!Net /est Bench
 2:203/602.0@fidonet \X/  Internet: Roger_Nordin@bad.se

--- 
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
From: amc@wucs1.wustl.edu (Adam Costello)
Subject: Attn Commodore: You are making a Big Mistake (Hardware Manual)
Keywords: hardware reference manual
Organization: Washington University, St. Louis MO
Date: Thu, 12 Nov 1992 00:00:37 GMT

One of the things I loved most about my old C-64 was the custom
hardware.  It was documented, so I could program it, experiment with
it, and play with it.

One of the main reasons I chose to buy an Amiga was that I was
impressed by the hardware.  I knew that there was much less useful
software for the Amiga, but that's not what turns me on.

For people who want their computers to be productive and don't want to
have to think too hard, there's Apple and IBM.  For people who want to
enjoy their computers, and especially for people who want to enjoy
programming their computers, there's Amiga.

If Commodore refuses to release a hardware manual for future Amigas,
they will be betraying their most loyal customers, the very customers
for whom IBM and Apple were never even an option.  Commodore should
compete by striving to be different from its competitors, not by trying
to mimic them.  Compatibility has always been one of the strengths of
IBM and Apple.  Capability has always been the strength of Amiga.  The
Amiga can do things other computers simply cannot do, but only if
programmers know how the machine works.

If the OS is documented, programmers can choose to use it for
compatibility.  If the hardware is documented, programmers can choose
to use it for capability.  If both are documented, the programmer has a
choice.  It's a trade-off that is best evaluated by the programmer on a
per-program basis, not once-and-for-all by Commodore.

If Commodore fails to document the hardware, lots of Commodore's paying
customers will suffer.  They may even desert.

And if none of the above is convincing, consider this: hackers will
figure out much of the hardware anyway, but not all of it, which is an 
even more dangerous situation than the one Commodore is afraid of.  If
Commodore does document the hardware, at least hardware programmers
have a chance to know what they're doing, and Commodore can make some
money from books sales.

It's not too late for a change-of-mind!

AMC
Newsgroups: comp.sys.amiga.programmer
From: toredale@idt.unit.no (Bjoern Tore Dale)
Subject: Docs on 68K: MMUs++?
Organization: Div. of CS & Telematics, Norwegian Institute of Technology
Date: Fri, 13 Nov 92 11:33:55 GMT

I currently have the 68000/010/008 User Manual,68020 User Manual and
68K Programmer's Manual (printed 1989,covers all chips).

What I lack is docs on
  1) 851/030/040 MMUs 
     The programmer's manual describes each instruction
     which handles MM, but it's not enough. I need docs on how
     these instructions are used together to actually 
     implement, say an OS-kernel which supports multi-tasking
     and memory-protection .This includes how address translation
     works (with all those multi-level tables), etc.
  2) 030/040 Execution Timings
  3) Any other info which describes aspects of the M68K chips
     which aren't covered in the books I already have or 1) or 2) above!

Any recommendations would be appreciated!

Regards
 - Bjoern T. Dale
Newsgroups: comp.sys.amiga.programmer
Subject: New assembly programmer, need help, Why wouldn't this work?
From: clin@zeus.calpoly.edu (Chihtsung Jeffrey Lin)
Date: Fri, 13 Nov 1992 06:00:36 GMT
Organization: California Polytechnic State University, San Luis Obispo

Hi, 

I've just started taking a 68000 assembly language class. We do our class
works on Macs. Recently I've tried to do some assembly programming on my
Amiga but have not idea how to do it. I've tried some simple programs that
worked on the Macs assembler we use for our class, but none of them seems
to work. I have an A3000, and I've used A68K and asm for SAS C. The linker I
use is blink. Here's one I tried.

		
start:		move.w	#5,d0

				end


It seems to assemble and bind ok, but when I try to run it from CLI, it
gives me a Software Failure window, error #8000000B of #80000004. I know
that's silly program but I don't see any harm in doing that either. Are
there specific codes that are need for an Amiga program? (I did put a csect
directive for asm, btw). Oh yeah, I bound it with amiga.lib and lc.lib even
though I don't see any reason to. 

Any hint/ clue is appreciated.

Jeff :)
Newsgroups: comp.sys.amiga.programmer
From: jpelkone@vipunen.hut.fi (Janne R M Pelkonen)
Subject: Re: Comments needed: Math Equation ed
Reply-To: jpelkone@vipunen.hut.fi (Janne R M Pelkonen)
Organization: Helsinki University of Technology
Date: Fri, 13 Nov 1992 12:17:59 GMT

	Why bother, when you can always use TeX + suitable macro package.

	- Janne
-- 
* Janne Pelkonen	*   Helsinki	* "With the day came the	*
* JMT 7C 352		*  University	*  resolution"	 		*
* 02150 Espoo		*      of	*  Uriah Heep: July Morning	*
* FINLAND		*  Technology	*				*