HDTenEightyP/NetNews huggingface dataset:
From: Donald.Kennedy@launchpad.unc.edu (Donald Kennedy)
Subject: Bob programming
Organization: University of North Carolina Extended Bulletin Board Service
Date: Sun, 20 Dec 1992 03:40:15 GMT


I am having problems with flicker while programming bobs. I have a 4
bitplane Workbench with 16 bobs (roughly 20 x 20) in a 640 x 200 screen in
WB1.3. I am having a bob follow the mouse pointer while selected. They
start out in a horizontal row, and the last 10 or so bobs flicker badly
while the first bob is selected. Similar flickering occurs regardless of
which bob is selected. I am using double buffering and WaitTOF(), and I
have tried several variations with no effect. I originally thought the
problem was CPU oriented (I am programming on an unaccelerated 2000) but a
friend with a 3000 reported the same problems. Any suggestions would be
appreciated!

Thanks in advance,

Don Kennedy
donald.kennedy@bbs.oit.unc.edu

--
   The opinions expressed are not necessarily those of the University of
     North Carolina at Chapel Hill, the Campus Office for Information
        Technology, or the Experimental Bulletin Board Service.
           internet:  laUNChpad.unc.edu or 152.2.22.80
Newsgroups: comp.sys.amiga.programmer
From: wlanders@nexus.yorku.ca (W L Anderson)
Subject: DICE 2.06.39 to 2.06.40 changes
Summary: Could someone post version.doc?
Organization: York University, CS Dept. Toronto
Date: Sun, 20 Dec 1992 01:49:59 GMT

Could someone post the version.doc file for DICE  2.06.40?   I've
got 2.06.39, and I'm wondering what the changes are.

Tom Hayko
wlanders@nexus.yorku.ca
Newsgroups: comp.sys.amiga.programmer
From: wlanders@nexus.yorku.ca (W L Anderson)
Subject: GCC & Amiga.lib
Summary: how do I get this to work?
Organization: York University, CS Dept. Toronto
Date: Sun, 20 Dec 1992 01:56:34 GMT

I'm trying to do some programming  using  Intuition  and  various
other  libraries using GNU C.  I tried using hunk2gcc to take the
amigal20.lib from DICE and creating a libamiga.a, but as soon  as
I  tried  to use the SystemTags() function call, I got a EMT sig-
nal.  My question is, is anybody actually doing  any  development
with GNU C with a created version of the amiga.lib?  What did you
do?

Tom Hayko
wlanders@nexus.yorku.ca
From: ianm@laghey.UUCP (Ian Moran)
Newsgroups: comp.sys.amiga.programmer
Subject: AmigaDos Assign command
Date: 15 Dec 92 01:16:20 GMT
Organization: Private Amiga Site
X-Newsreader: TIN [version 1.1 PL6]

I have noticed strange behaviour with the 'assign' command under 2.04 and
above. If I take advantage of the multiple assign facility thus :

 assign rexx: s: dh0:turbotext/rexx

Then Arexx macros will not be located under Turbotext which is contrary to
what I would expect, only s: is searched.

Also, why do few (if any) file requesters follow multiple assigned
paths similar to the above. If I enter rexx: in the C= requester then I will
get only the contents of s:

 Ian

--
Ian Moran                   Internet:  ianm@icsbelf.co.uk
ICS Computing Group Ltd     UUCP:      ...{uknet,uunet,mcsun}!icsbelf!ianm
Belfast                     Fidonet:   2:257/10.1, 2:440/59.5, 2:252/309.6
N. Ireland                  AmigaNet:  39:137/1.6
From: ry53@rz.uni-karlsruhe.de (Angela Schmidt)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Getting a valid FileSysStartupMsg pointers.
Date: 16 Dec 1992 16:42:48 GMT
Organization: Nessyhoehle@I501.NessyNet.de
Distribution: world
Reply-To: Angela@rz.uni-karlsruhe.de
NNTP-Posting-Host: tp70.rz.uni-karlsruhe.de

In article <1992Dec15.110215.18810@odin.diku.dk>, bombadil@diku.dk (Kristian Nielsen) writes:
> ry53@rz.uni-karlsruhe.de (Angela Schmidt) writes:

> >Or are there disks which are no real disks...?
> 
> Yes. For example the RAM: disk, or XFH:, or some network file systems
> apparently (?).

Hmm - I don't know XFH:, but RAM: puts 0x00000000 into dn_Startup and
so avoids any conflicts with other programs.

> The problem is that programs like 'diskcopy' apparently assume that any
> handler that satisfies 'IsFileSystem()' and has a non-null 'startup'
> field is an exec-device based filing system with a valid FSSM. This
> might be the only currently working way, but with the 'Startup' field
> documented and supported in 'mount' it seems seriously broken.

I'm writing a disk editor and I have the same problems as DiskCopy.
I don't see any good way to guess if there's a fssm in dn_Startup
or not. TypeOfMem() only works with RAM, but some of the entries in
the fssm can be in ROM or even in the expansion space as well. So
for now, I assume that non-zero-values mean that there is a valid
fssm. I tried TypeOfMem() but I really missed some devices after that,
because their device name (and I think the environment vector, too)
was in ROM.

> Anyway, I'd be VERY interested in any opinions on the best way to solve
> this problem (ie. how to pass information to a file system handler that
> cannot provide a valid FSSM). My current approach is to overwrite the
> 'Startup' field in the device node with NULL (!), which is a terrible
> hack IMHO.

Hmm - overwriting it with 0x00000000 after you got your information
sounds not too bad (IMHO). You only should remember to restore dn_Startup
before you execute a real ACTION_DIE.

     V v
  @/@@=\   Salut,
    00 &=-      Angela 
oOoO_/` \\_
    \ /&\   Angela Schmidt cand. inf. (Nessy@IRC) | Amiga //
  |>O<|         EMail: Angela@rz.uni-karlsruhe.de | 1000 // 
   / \_/\/\/v,  Weekend: +49 731 712316 (9am-9pm) |  \\ // since 
  /___________\ Weekdays: 721 6904263 (10am-11pm) |   \X/ 1986
From: idr@rigel.cs.pdx.edu (Ian D Romanick)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Hardware Reference Manual
Date: 18 Dec 92 01:14:28 GMT
Article-I.D.: pdxgate.6588
Organization: /etc/organization

In article <1992Dec12.193951.27913@mpifr-bonn.mpg.de> mlelstv@specklec.mpifr-bonn.mpg.de (Michael van Elst) writes:
>Some of todays demos may run on an A3000 but just because the demo coder
>had access to an A3000 and not because he had the manual.

The problems that games/demos/etc have with A3000's have nothing to do with
the chip set!  They are problems with idiots writing directly to vector
bases with out checking the VBR, using self-modifing code, and other general
stupid stuff.  I'll admit, I've done that too, but only when on a tight
deadline (read: 2 hours left to finish my demo) and didn't have time.

It's not the chips!  Maybe people need to also get the Motorola manuals and
not just the CBM one!  You don't see Motorola (warning:  what follows is a
JOKE!) saying, "Stuff seems to break from one chip to another, so let's
quit documenting them."

                                  - Ian Romanick
                                    Dancing Fool of Epsilon

[]--------------------------------------------------------------------[]
 |                                                                    |
 | My opinions are exactly the same as PSU's.  NOT!                   |
 | Mail at:  idr@cs.pdx.edu             Epsilon, for the best in NTSC |
 |                                      demos! :^)                    |
 |                                                                    |
[]--------------------------------------------------------------------[]
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
From: tomasa@dront.nada.kth.se (Tomas Arvidsson)
Subject: Re: Attn Commodore: You are making a Big Mistake (Hardware
Organization: Royal Institute of Technology, Stockholm, Sweden
Date: Fri, 18 Dec 1992 00:13:34 GMT

In <1992Dec16.193826.1973@microsoft.com> iank@microsoft.com (Ian Kennedy) writes:

>In article <1992Dec16.012049.4783@kth.se> tomasa@dront.nada.kth.se (Tomas Arvidsson) writes:
>>In <1992Dec15.170840.60807@qut.edu.au> podesta@qut.edu.au (Department of Computing Science, QUT) writes:
>>>Does anybody know what the lowest end MMU AGA Amiga will be and when??
					     ^^^
>>All A3000's have a MMU and they've been available for quite some time. Before 
>>that you had the A2630 accelerator (in the A2500) which also had a MMU.

>Is it just me or doesn't anybody bother to read posts completly anymore?
>He was looking for an AGA machine. The A3000 doesn't have the AGA chipset.
							       ^^^
Ooops! I missed something...

(A slip like that and the following flame always make me remember not to
answer any posting when I too tired to read...)

>|Currently Amigaless soon to   | Eagle Talon TSI AWD/ABS/Turbo     |
>|own A1200/100MB               | Iank@Microsoft.com                |


-- 
Tomas Arvidson			 			     ///
d91tar@csd.uu.se,					    ///
tomasa@nada.kth.se, tomasa@sprawl.adsp.sub.org   	\\\///
Expressed opinions are mine unless stated otherwise      \XX/
-- 
Tomas Arvidson			 			     ///
d91tar@csd.uu.se,					    ///
tomasa@nada.kth.se, tomasa@sprawl.adsp.sub.org   	\\\///
Expressed opinions are mine unless stated otherwise      \XX/
From: bloc1469@ee.ee.uwm.edu (Gregory R Block)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: App(Icon|Window) and Style Guide.
Date: 21 Dec 1992 05:33:17 GMT
Organization: Electrical Engineering Dept. University of Wisconsin - Milwaukee
Distribution: world
NNTP-Posting-Host: 129.89.2.33

In article <EfAYvAu00WB_QsSQ1Q@andrew.cmu.edu> "Edward D. Berger" <eb15+@andrew.cmu.edu> writes:
>the program icon would be: Program
>the AppIcon for program would be: Program.1 or Program_App or ...

I agree.  It _SHOULD_ be either a tooltype, or internal to the program.

>Having an AppIcon should be a user setting, as I may already have created one
>with ToolManager, and not want to have 2 AppIcons for the same thing.

How's this:

(APPICON)		No AppIcon
APPICON			Give me an AppIcon with the std. Icon as the image
APPICON=		(The 1.3 version of the above)
APPICON = Sys:Icons/Yow Give me an AppIcon with the image given.  If
				not found, use the std. icon as the image

That's how _I_ think it should work.

>I see no great reason to make AppIcons with different borders than standard
>Icons, as I keep the 2 separate.  AppIcons are out in the workbench window,
>while Tool/Project Icons are in their drawers.

However, this I disagree with.  And it's because people use the "Leave
Out" option for directories, sometimes.  For instance, I've got
"Prefs" sitting out on my workbench.  I'd like to have visual feedback
that it's not an appicon.

The problems come in that without a different visual feedback, you're
telling the user there's no difference between an AppIcon and a std.
icon.  I agree, lets standardize the drop system by making AppIcons
and AppWindows have the "lip".  More importantly, if, someday, C=
decides to make an icon type (when .info files are no more, and
everybody uses 2.0 std. functions for accessing them) that allows
"dropping" onto them (The WB's copy function would simply examine the
icon's type, and if it was of type STD_DropApp, do whatever), that
icon could have a lip too.

"lipping" windows and icons should become the standard look for
droppable stuff.  After all, aren't we trying to set a standard with a
style guide?  Let's do it, then, and standardize your own standards.
:)

Greg



--
(: (: (: (: Have you overdosed on smileys today?  Why NOT!?! :) :) :) :)
(:   "Commodore has never proven to me, to my satisfaction, that      :)
(:    Marc Barrett is still alive."			       -Wubba :)
(: (: (: (: (: (: (: (: (: (: (: (: () :) :) :) Wubba, the Dark Angel :)
Newsgroups: comp.sys.amiga.programmer
From: bandy@netnews.jhuapl.edu (Mike Bandy)
Subject: Re: wierd sas/c bug
Organization: JHU/Applied Physics Laboratory
Date: Mon, 21 Dec 1992 01:58:07 GMT

umfehr06@ccu.umanitoba.ca (John Fehr) writes:

>I've been trying to compile an lpmud driver with sas/c, and I've
>come upon a wierd bug...  In my main program file, I have the following
>code:

>char master_file = "obj/master";

>main() {
>/* bunch of other variables declared */
>	printf("master_file='%s'\n",master_file);
>...

>When I compile and run this, I get:

>master_file='bj/master'

Shouldn't that be?
char *master_file = "obj/master";

-- 

	Mike Bandy
	bandy@aplcomm.jhuapl.edu
	Johns Hopkins University / Applied Physics Lab
Xref: sparky comp.sys.amiga.programmer:17319 comp.sys.amiga.hardware:21440
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
Subject: Re: Attn Commodore: You are making a Big Mistake (Hardware
Date: 14 Dec 92 03:25:27 GMT
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA

amipb@amipb.gna.org (Philippe Berard) writes:
>> Yet, Legends of Valour, a fast scrolling game does work. And doesn't
>> blow away the OS.
>
>    You miss a serious point here : most of the games break on the 4000
>    because of the instruction/data cache. Turn it off, and 80-90% or
>    your games will work again.

	Factual correction: more break due to taking over hardware that's 
already running in high-bandwidth modes than caches.  Note that until
3.0 setpatch is run, the '040 data cache is NOT enabled, and high-bandwidth
modes are NOT enabled.  Even then, as I understand it, only about 50% of
the european games run.  (From a report here.)  I could be wrong, I personally
don't have many Euro-arcade games.  These games are one reason why everything
is disabled until setpatch, to give them some hope of running.

	Of the games I play (largely strategy/simulation, all but 1 or 2 HD-
installable), only a couple require ECS mode or booting off the disks.  Only
1 was broken by '040 caches, I think (actually not the caches, but by not
using VBR to patch vectors in copy-protection code - the 68040 library moves
the vectors).

-- 
To be or not to be = 0xff
-
Randell Jesup, Jack-of-quite-a-few-trades, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Disclaimer: Nothing I say is anything other than my personal opinion.
From: fgd3@nifty.UUCP (Fabbian G. Dufoe, III)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Default buttons under 2 or ^
Distribution: world
Date: 16 Dec 92 14:38:52 EST
Organization: Fabbian G. Dufoe, III

In article <BzBrzI.GME@csugrad.cs.vt.edu> jaker@csugrad.cs.vt.edu (Jake Rose) writes:
>The idea is to draw a sunken borderbox around the gadtools gadget that
>will be "hit" if the return key is pressed, to indicate that that is the
>default response.  I think it looks very clean and that it doesn't clutter

   Why a sunken box?  Why not just double the width of the lines in the
border of the default gadget?  The heavier border would be easy to spot and
it would remain consistent with the metaphor of a raised button that can
be pushed.

--Fabbian G. Dufoe, III
   350 Ling-A-Mor Terrace South   | GEnie:    F.DUFOE3
   St. Petersburg, Florida  33705 | internet: fgd3%nifty@tct.com
   813-823-2350                   | uucp:     ...tct!deep6!nifty!fgd3
From: Tony-Preston@cup.portal.com (ANTHONY FRANCIS PRESTON)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: MPEG on the Amiga
Date: Tue, 15 Dec 92 08:12:40 PST
Organization: The Portal System (TM)
  <1992Dec10.113642.15859@mpifr-bonn.mpg.de>
  <1g84ndINNm1e@swrinde.nde.swri.edu>
  <1992Dec10.195928.5789@sol.cs.wmich.edu> <37811@cbmvax.commodore.com>

While your at it, make it compatible with the ESC chipset and 2.1!
Not everyone has an A4000 and AGA!
Newsgroups: comp.sys.amiga.programmer
From: eas3714@ultb.isc.rit.edu (Ezra Story)
Subject: Re: Attn Commodore: Yo
Originator: eas3714@ultb
Organization: Rochester Institute of Technology
X-Newsreader: Arn V1.00 beta rel2
Date: Tue, 15 Dec 1992 05:53:21 GMT

Rockerboy writes:

> I Write:
> > If I open up a screen, attach a bitmap, and query its attributes, I can
> > make certain assuptions about that screen and bitmap.  If the bitmap is
> > shown to be a normal amiga interleaved bitmap in chip memory, nothing
> > prevents me from using the blitter directly to write to the bitmap...
> > Remember we're not talking about PageStream here... we're talking about a
> > demo or a game.
>
> How can you do it if you have no information on how the blitter works?
> _The lack of data on the hardware_ prevents you from safely using the
> blitter, or any other chips, for that matter.

Ah, but I do... The 2.0 hardware reference manual has all the info I need.

Using the OS to do blits is preferable, of course.. but as long as there are
Dis/OwnBlitter() and Q(S)Blit() calls you can be pretty sure that the blitter
will work like it always has.  Note that the only other hardware direct access
the OS allows (other than resources..) is Copper instructions.. and since
those are used just as a medium for accessing the hardware anyway, the only
areas that are legal are color registers when ECS is active and the
blitter.


-- 
"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.
From: dstuve@storm.CS.ORST.EDU (David Stuve)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Sorry, can't learn from includes alone
Summary: Get the RKM: Libraries
Date: 16 Dec 92 06:03:51 GMT
Organization: Computer Science Department, Oregon State University
NNTP-Posting-Host: storm.cs.orst.edu

If you want to learn how to program the Amiga, get the
Rom Kernel Manual: Libraries -- it's a massive volume that
describes all of the system libraries.  (GadTools, Intuition,
Graphics, Exec, etc.)  Required reading.

Oh.  Make sure you get the 3rd edition (black) for 2.04 stuff.

-David

-- 
========================================================================
David Stuve                          | InterNet: dstuve@storm.cs.orst.edu
Software Engineer                    |
MindWorks -- Advanced Amiga Software | Crescat Scientia Vita Excolatur
From: paulk@terapin.com (Paul Kienitz)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Attn Commodore: You are making a Big Mistake (Hardware Manual)
Date: 11 Dec 92 19:40:52 PST
Organization: BBS

> The OS people are _constantly_ trying to prevent the hackers from
> hitting the hardware, though.
 
NO.  WRONG.
 
We are trying to prevent COMMERCIAL programmers from hitting the
hardware.  And it's not just games that do that -- folks with
expensive video products are often rude to the system as well.
 
There's an analogy here.  In the good old days, intuition/intuitionbase.h
had a big section marked #ifdef INTUITIONPRIVATE, with a note saying
"these are NOT supported for your use.  They ... are provided for
education, debugging, and information."  It was marked as stuff that
would change and was not supported, but it was there, and people messed
with it ... in commercial programs.  And all the programs that messed
with it BROKE when 2.0 came out, and C= ended up spending months on
putting kluges into 2.04 to get a lot of these bad programs to work
again.  Now that header file has this instead of the #ifdef'd section:
 
    /* I told you this was private.
     * The data beyond this point has changed, is changing, and
     * will continue to change.
     */
 
Now, programs don't break that particular way any more.  Practical experience
has shown that C= would have gotten a better system out sooner and at
lower cost if they had taken this approach the first time.  We ALL
would have benefitted if they had kept the private part of
IntuitionBase undocumented.
 
It's the same with the AGA registers, ONLY MORE SO.  The more
programmers use them directly, the less able C= or anyone else will
be to make future Amigas work better than present ones.
From: shulick@navajo.ucs.indiana.edu (Sam Hulick)
Newsgroups: comp.sys.amiga.programmer
Subject: Help a 1.3 programmer get started on 2.0
Date: 15 Dec 92 16:13:03 GMT
Reply-To: shulick@navajo.ucs.indiana.edu
Organization: Vallen Software
Originator: shulick@navajo


I'm still writing apps that work on OS 1.3. :)  I don't know where to
start learning OS 2.0 specific code.  For instance, how does one make
the gadgets w/ key shortcuts?  I see them all the time.. i.e. a gadget
'Help' with the 'H' underlined.  And how do you make cycling gadgets?
etc. etc.  I need a book that explains what functions to use, how to do
it, etc.  I have the 'Includes And Autodocs' with all the functions..
but I have no clue which functions to use to make these things.  Any
help would be great.. thanks.

-- 
    // Amiga 3000   ___ \ Sam Hulick: shulick@indiana.edu (NeXTmail OK!)
   // 68030 25 MHz /__/\ \ My opinions wear combat boots.  Or whatever.
\\// OS 2.04       \__\/ / "Walk!  Not bloody likely.  I am going in a
 \/                     / taxi."  --George Bernard Shaw
From: bombadil@diku.dk (Kristian Nielsen)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Getting a valid FileSysStartupMsg pointers.
Date: 15 Dec 92 11:02:15 GMT
Organization: Department of Computer Science, U of Copenhagen

ry53@rz.uni-karlsruhe.de (Angela Schmidt) writes:

>In article <37848@cbmvax.commodore.com>, jesup@cbmvax.commodore.com (Randell Jesup) writes:

>Here is a part of <dos/dosextens.h>. Please have a look at the commented
>line. Doesn't this say, that there has to be a fssm in dol_Startup?
>Or are there disks which are no real disks...?

Yes. For example the RAM: disk, or XFH:, or some network file systems
apparently (?).

>> 	This is an ugly area.  Unfortunately, early in the Amiga days (or
>> perhaps back in tripos), someone though strings would be neat to hold
>> parameters for handler startups.

>Grmpf. Programs like DiskCopy _need_ a fssm in dol_startup - otherwise
>they cannot work correctely. Why do programmers make their handler 
>doing bad things with dol_startup? To annoy the user by causing his
>machine to crash or hang up?

No. In my case (XFH), the problem is that there is a handler that
supports a filing system, but does not have an underlying exec device
(XFH sits on top of another filing system). However, I need to pass
information from the mountlist to the handler (to support multiple units
etc). I started out creating a fake mountlist entry

	FILESYSTEM = "XFH-Handler"
	DEVICE = "dummy.device" (or just "")
	LOWCYL = 0
	HIGHCYL = 0
	[ and so on... ]

However, this caused problems, and by popular demand (and because it was
apparently the 'correct' way), I changed this to use the 'Handler'
keyword instead and pass a string in the 'Startup' entry.  Unfortunately
this causes problems, too.

The problem is that programs like 'diskcopy' apparently assume that any
handler that satisfies 'IsFileSystem()' and has a non-null 'startup'
field is an exec-device based filing system with a valid FSSM. This
might be the only currently working way, but with the 'Startup' field
documented and supported in 'mount' it seems seriously broken.

I guess it's just ol' BCPL haunting the Amiga yet again.

Anyway, I'd be VERY interested in any opinions on the best way to solve
this problem (ie. how to pass information to a file system handler that
cannot provide a valid FSSM). My current approach is to overwrite the
'Startup' field in the device node with NULL (!), which is a terrible
hack IMHO.

	- Kristian.
From: rnelson@wsuaix.csc.wsu.edu (roger nelson;S23487)
Newsgroups: comp.sys.amiga.programmer
Subject: Console RAW mode.
Date: 17 Dec 92 05:11:57 GMT
Article-I.D.: serval.1992Dec17.051157.23971
Organization: Washington State University

Is there an escape sequence that will put the CLI shell into
unbuffered mode and one that will enter RAW mode.  

I am programming in C and scheme and I would like to be able to do the 
following:

    I would like to read the next key pressed with getc() in C or
    (read-char) in scheme without waiting for the return key to be pressed.
   
    If a function key, cursor on num-keypad key is pressed, I want to be
    able to read the escape sequence.
 
Esc [ 1 {    and    Esc [ 1 {    doesn't seem to do what I want 

Thanks,
Roger
Newsgroups: comp.sys.amiga.programmer