HDTenEightyP/NetNews huggingface dataset:
From: alex@bilver.uucp (Alex Matulich)
Subject: Mouse blanking in 2.0 = TRASH (help!)
Organization: W. J. Vermillion - Winter Park, FL
Date: Mon, 23 Nov 1992 15:51:30 GMT


I wrote a program that needs to blank the mouse at times.  Under
AmigaDOS 1.3, the method I used worked perfectly.

However, now that I've upgraded to 2.04, when I blank the mouse a vertical
bar of trash appears on the screen.  The bar does not move when I move the
mouse.  It's fixed in place, and stays there until I restore the mouse.
The bar is not even in the same position as the mouse when the mouse goes
blank.  It *looks* like a trashed sprite of some sort.

Here is what I'm doing.  Please tell me if there's a better way, that will
work under both 1.3 and 2.0....

--------------------------------------------------------------------------

static short blankpointer { 0, 0 };   // bit image for blank mouse pointer
 .
 .
 .
SetPointer(Window, blankpointer, 1, 1, 0, 0);  // blank the mouse pointer
 .
 . // under 2.0, a vertical bar of trash is now showing on the screen
 .
ClearPointer(Window);  // restore the mouse pointer; bar disappears

--------------------------------------------------------------------------

If it makes any difference, the 2.0 "Text Overscan" and "Standard
Overscan" are both set to 680x440, but I am using a custom screen and
window, sized to 640x400, in the program above.  I am using SAS C 5.10b
with 1.3 include files.

I'm rather new at this.  If someone knows a better way, please post or
send email.  Thanks in advance for any help offered.

-- 
 _ |__  Alex Matulich    alex.matulich@oau.org
 /(+__>  Unicorn Research Corp, 4621 N Landmark Dr, Orlando, FL 32817
//| \     UUCP:  alex@bilver.uucp   {peora|ge-dab|uunet!tous}!bilver!alex
///__)     Internet:  alex@bilver.oau.org | alex%bilver@peora.sdc.ccur.com
From: ejames@venus.iucf.indiana.edu (ERIC JAMES)
Newsgroups: comp.sys.amiga.programmer
Subject: Re-Bootable RAD disk and ARP
Date: 16 Nov 92 20:53:52 GMT
Article-I.D.: usenet.BxtuBr.C1n
Reply-To: ejames@venus.iucf.indiana.edu
Organization: nothing
News-Software: VAX/VMS VNEWS 1.3-4


  I am having trouble creating a rebootable RAD disk,  It works just fine if I
start from the standard Workbench 1.3 disk, but If I try it with ARP installed,
It will no longer detect the rad disk during a reboot.  It's there, because you
put the boot disk back into the drive, and It detects it and transferrs control
back to the RAD.  Dose anyone know what's wrong?  I wouldn't think ARP would
have anything to do with it at that point, I thought it was all in the 
kickstart ROM's.

Thanks

Eric James
ejames@venus.iucf.indiana.edu
From: Patrik_Gyltefors@augs.se (Patrik Gyltefors)
Newsgroups: comp.sys.amiga.programmer
Subject: Gfx boars detection
Date: 23 Nov 92 00:27:41 GMT
Organization: Amiga User Group - Sweden


I am programming a raytracer in C, and I would like it to support different
graphics boards and resolutions. Does anyone know how to check which boards
and which resoulutions are available? It must work with both 1.3 and 2.0.

If you know, please E-mail me at this address: Patrik_Gyltefors@augs.se


-- Via DLG Pro v0.995
From: bjbernstein@miavx1.acs.muohio.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Character repeat ANSI code on OS
Date: 15 Nov 92 11:11:04 GMT
Article-I.D.: miavx1.1992Nov15.161104.14237
Organization: Miami University Academic Computer Service"


  Is there an ANSI code to repeat a character X ammount of times (eg: one 
ANSI code to repeat '-' 79 times to make a line)

  And does 1.3 or 2.xx+ support this?

  PLEASE REPLY BY EMAIL
-- 


@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Brian Bernstein (Drone)           @@ "I'm a white dread, I'm a white   @@ 
@@ bjbernstein@miavx1.acs.muohio.edu @@  dread, so? I got a little ring   @@
@@-----------------------------------@@  and I hang it from my nose.."    @@
@@ the Fabulous Furry Freak Brothers!@@                -Jane's Addiction  @@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
From: tlbechar@thunder.LakeheadU.Ca (Timothy Lee Bechard)
Newsgroups: comp.sys.amiga.programmer
Subject: FTP & Development
Summary: none
Keywords: FTP Development SAS/C
Date: 17 Nov 1992 04:09:54 GMT
Distribution: comp.sys.amiga.programmer
Organization: Lakehead University; Thunder Bay, Ont


	I'm interested in any information people can send me wtih regards to places where I can FTP here from school to get cool programming tools.  I've been using the SAS/C development software for the last 2 years, and majorly oriented around that software.  If anyone can send me FTP as well as any programming stuff, I would be eternally greatfull!

	I have no signature... <G> 

	tlbechar@thunder.lakeheadu.ca
From: jbickers@templar.actrix.gen.nz (John Bickers)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: New hardware reference guide?
Date: 22 Nov 92 11:01:07 PST
Organization: TAP

Quoted from <37160@cbmvax.commodore.com> by andy@cbmvax.commodore.com (Andy Finkel):

> 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

    I've seen an article in this newsgroup within the last few months
    where the author needed to drop DTR and then write to the device.
    I think that was when Russell posted his code that writes directly
    to the hardware.

    I myself want to be able to drop DTR without closing the device
    for several reasons:

    1.  To remain compatible with a particular PC link library, to aid
        in porting an application from MS-DOS to the Amiga.

    2.  There is a chance that the attempt to reopen the device would
        fail (because another application got in first).

    3.  Closing the device will not drop DTR if it was opened in
        shared mode, and another application still has it open.

    There are a couple of other things that would be nice to have in
    the serial device, like a way to open the device in shared mode,
    then promote oneself to exclusive use of the device - other apps
    that had opened it in shared mode would have their requests put
    "on hold" until a "demote" command was sent to the device.

> 			andy
--
*** John Bickers, TAP.                   jbickers@templar.actrix.gen.nz ***
***    "Radioactivity - It's in the air, for you and me" - Kraftwerk    ***
Newsgroups: comp.sys.amiga.programmer
Subject: Re: A Style Guide Question
From: jbickers@templar.actrix.gen.nz (John Bickers)
Date: 24 Nov 92 14:31:04 PST
Organization: TAP

Quoted from <d92.ANN@halmuc.muc.sub.org> by dolittle@halmuc.muc.sub.org (Ludwig Hurt):

> How about using the TAB-key to deactivate the textbox ? I can't imagine one
> case where I need a TAB in a textbox.

    Searching for a string that contains a Tab. It's not that big a
    deal though, there's some way to enter the Tab using the Alt key,
    so you can still use a normal Tab as "go to next field".

> Ludwig Hurt,      | The first myth of management is that it exists !!
--
*** John Bickers, TAP.                   jbickers@templar.actrix.gen.nz ***
***    "Radioactivity - It's in the air, for you and me" - Kraftwerk    ***
From: podesta@qut.edu.au
Newsgroups: comp.sys.amiga.programmer
Subject: Re: New hardware reference guide?
Date: 18 Nov 92 13:46:41 EST
Organization: Queensland University of Technology

In article <OAHVENLA.92Nov17002933@lk-hp-4.hut.fi>, oahvenla@snakemail.hut.fi (Osma Ahvenlampi) writes:
> In article <1992Nov16.130752.18379@imada.ou.dk> breese@monet.imada.ou.dk (Bjoern Reese) writes:
> [...]
>>doesn't release a new Hardware Ref Guide, featuring the AGA
> 
> This is the whole point. C= won't release the Hardware information, because
> that would mean saying that it's OK to directly access hardware, when it's

I don't get it. What's the big deal????
Why don't Commodore just release it and say something like:

"BANGING THE HARDWARE IS NOT UPWARDLY COMPATIBLE"

Then all of us who don't give a damn about upward compatibility
(ie. in demos and some games) can write our demos and have fun, and
those who want to write software that will last forever can go through
the OS.

People have argued that you should write a ECS version, using hardware, and
include an OS friendly AGA version. WHY??? If your gonna go to all that
trouble, just write an ECS version, and change the hardware routines
for the AGA versions. Even machine code can be modular :) If a new machine
comes out, we insert new code. This way we are always getting the most out
of the system...rather than just wasting MIPS by going through the OS.

I mean the OS is GREAT. I love it. It's one of the reasons that Amiga rules..
but its a development environment, not a demo or game environment.


James.

Disclaimer: The above opinions are mine...obviously
From: fheitkamp@desire.wright.edu
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
Subject: Re: Attn Commodore: You are making a Big Mistake (Hardware
Date: 19 Nov 92 06:22:08 EST
Organization:  Wright State University 

In article <37138@cbmvax.commodore.com>, spence@cbmvax.commodore.com (Spencer Shanson) writes:
> In article <Bxvrpv.31E@acsu.buffalo.edu> jcmurphy@acsu.buffalo.edu (Jeff Murphy) writes:
>>difficult. So.. in the interest of helping those who wish to undertake
>>such things as a port of UNIX to new machines, Commodore should release
>>an hardware manual for the machine.
> 
> Realise that a port of another OS to the Amiga, such as UNIX, is not the type of
> project that many software companies are likely to do. In a really extreme case,
> then maybe we could help out with regards the details of the AA chip set.
> 

	Now that Commodore has apparently given up on Unix systems but is
	selling the Unix software sepparately, is there intention (by
	Commodore) to continue to upgrade the Unix package to work with any
	current Unix capable Amigas such as the A4000?

>>jcmurphy@acsu.buffalo.edu                   cit network installation & repair
>>opnsmurf@ubvms.cc.buffalo.edu                                          sunyab
>>				   
> ---------------------------------------------------------------------------
> Spencer Shanson - Amiga Software Engineer     | email: spence@commodore.COM
>                                               | or uunet!cbmvax!spence
> All opinions expressed are my own, and do not | Bix: sshanson
> (necessarily) represent those of Commodore.   | Have you Wobbled a
>                                               | Weeble today?
Fred Heitkamp, ** Not an organization **

Newsgroups: comp.sys.amiga.programmer
From: R3DRS@VM1.CC.UAKRON.EDU
Subject: Programming Perfect Vision and Digi-View
Organization: The University of Akron
Date: Mon, 23 Nov 1992 23:09:38 GMT

I have an old digi-view and Perfect-Vision laying around from my amiga 1000
days...  I currently own a 486 (possibly another amiga in the future) and I
was wondering if there is any programming information somewhere for these
devices?  Will a standard, PC style parralel port even handle the job (assuming
the pinouts are adapted)???
 
Any help would be greatly appreciated...
 
David Snyder
r3drs@vm1.cc.uakron.edu
From: jow@hcast.franken.de (Juergen Weinelt)
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  New hardware reference guide?
Date: 15 Nov 92 19:50:36 GMT
Reply-To: jow@sun.rz.uni-wuerzburg.de
Organization: None at all

In article <Bxnwno.6ns@cck.coventry.ac.uk> csg019@cch.coventry.ac.uk (-~=Zaphod=~-) writes:
>In article <1992Nov13.023341.27459@mpifr-bonn.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 (most likely A500's and A3000's with no expansion)
>
>It would work on any amiga with the custom chips at location $DFF000.

I think that's what caused the *big* delay between ECS and AGA. If you
go down to the bare hardware, then you don't just rely on *where* the
custom chip registers are... you're also making assumptions about their
*meaning*.

>>d) risks hardware damage with things connected to the serial or parallel port.
>
>How could it *dammage* hardware?
>Your not one of them guys that think that some viruses write to the disk
>label are you?  :)

Very funny. Just imagine there's some device connected to my
serial/parallel/joystick ports, that expects certain lines to be
_input lines_ (seen from the computer side). Now, some semi-smart
#+!^"+$ like you comes along and (accidentally) makes some of those
lines _output_, causing an excessively high current to flow.
*POOF* there goes my hardware.

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

Never happened to me, but it's possible. You could easily destroy an
audio/video digitizer that way. Of course you could protect those
peripherals (actually some *are* protected :-), but you would still
kill one of the CIAs.

>******************************************************************************
>*        ///  O O   A member of S.H.I.T. (Super High Intelligence Team) ///  *
                                           ^^^^^^^^^^^^^^^^^^^^^^^
To quote what you wrote above... are you sure? :)

-- Juergen Weinelt, Germany

  o  _         1) jow@sun.rz.uni-wuerzburg.de (preferred)
  | (_) \/\/   2) jow@hcast.adsp.sub.org
  '            3) jow@hcast.franken.de
Newsgroups: comp.sys.amiga.programmer
From: s37732v@snakemail.hut.fi (Markus Juhani Aalto)
Subject: Re: New hardware reference guide?
Organization: Helsinki University of Technology, Finland
Date: Fri, 20 Nov 1992 16:57:30 GMT

In article <1992Nov19.140544.28847@imada.ou.dk> breese@monet.imada.ou.dk (Bjoern Reese) writes:

   You people with the big machines actually have an option: Don't watch
                      ^^^^^

Yes my A500 is quite big, but I would like to get something smaller but
more powerfull. :^)

   demos!!! If you're so afraid that demos will crash your machine or
   that it may harm your hardware, don't watch demos! If C= doesn't
   release the hardware specs, I can ensure you that it doesn't mean
   that democoders will start producing OS-demos; more likely they will
   leave the Amiga world.

Why not! You could try to make as good demos as you can with OS. The
guy who makes the best without banging the hardware obviously is 
a very good (best) demo coder. 

   Why can't you let us write our demos and have the fun what we want?

Because it makes lives of Commodore engineers a lot easier.

   > I mean the OS is GREAT. I love it. It's one of the reasons that Amiga rules..
   > but its a development environment, not a demo or game environment.

   I agree again. The OS is GREAT, and I can understand that the software
   engineers at C= aren't feeling too happy about people like me, when I
   stuff the OS, which they have been working hard at for several years. But
   I think that every programmer should be given to freedom to do as he/she
   likes, based on guidelines from C=. If we don't care about upwards
   compatibility, it's our problem (we probably never intended these
   programs to run on a future machine; we made them to show what the
   current machine can do, and remember: we never got any money for our
   efforts!!)

Remember that if you coded with OS, you could actually get money. 

   Bjoern Reese                   |     Email: breese@imada.ou.dk
   Odense University, Denmark     |     Voice: +45 65 932 182 (private)
--


**************************************************************************
*         Markus Aalto              | Helsinki University of Technology  *
*                                   |                                    *
*  EMail: s37732v@vipunen.hut.fi    | Faculty of Electric Engineering    *
*  Fax:   358-0-8746991 (Sometimes) |                                    *
*                                   | Undergraduate in Computer Science  *
**************************************************************************
From: amigamat@ccwf.cc.utexas.edu (Mark Thomas)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: How to program multi-threaded programs on Amiga ?
Date: 16 Nov 92 18:26:33 GMT
Organization: The University of Texas at Austin, Austin TX

In article <1992Nov12.195317.19859@csus.edu> wittb@nextnet.csus.edu (brian witt) writes:
>	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.

Why not just have the sub-process reply back to you when it is okay
to quit?
I like for the OS to handle telling me a change in state.

>   Brian Witt   Sac State Computer Science]   "Waldo, the pariot, is dead"

-- 
-------------------------------------------------------------------
         Mark A. Thomas          / (amigamat@ccwf.cc.utexas.edu)
         CS Student : University of Texas at Austin
From: mwm@contessa.palo-alto.ca.us (Mike Meyer)
Subject: Re: A Style Guide Question
Newsgroups: comp.sys.amiga.programmer
Distribution: world
X-NewsSoftware: Amiga Yarn 3.4, 1992/08/12 15:49:52
Keywords: 
Summary: 
Date: 15 Nov 92 23:08:02 PST
Organization: Missionaria Phonibalonica

In <17474@pitt.UUCP>, dan@cs.pitt.edu (Dan Drake) wrote:
> This is a style guide question.
> 
> To be consistent in my user interface, I am using buttons called done and 
> cancel, that reside in all of my windows.  I want the user to be able to
> activate these buttons through their keyboard equivalents: eg d for done, 
> and c for cancel.  Now on several of these windows, I want the user to type
> text into a beveled box which I handle manually.  THe problem is that if the
> user wants to type a d or a c, there is some ambiguity concerning what 
> should happen.  Will the buttons be activated, or should the characters
> appear in the "textbox"?  I have 2 solutions, and would be interested in
> any other solutions or recommendations.

I just designed an interface around this same problem.

> 1.) If a text box is active, the user must click on the buttons to activate
> them.  I consider this unacceptable because it ruins the orthogonality of
> the interface.  You can't have some things work in one window, and not in
> others.

I don't particularly like that one, either. It didn't change the
orthoganality of the interface (i.e. - all buttons would be the same),
but it meant you'd have to use the mouse to get to the keyboard
shortcuts.

> 2.) Use (ALT|CTRL|right amiga) key to activate the buttons in all cases.
> Alt doesn't work because European languages use it.  Control is awkward
> for left handed people to use like me. (I like to keep one hand on the
> mouse, and one on the keyboard), Right Amiga is somewhat awkward too.

You forgot that in standard text gadgets, CTRL can do usefull things.

> 3.) Don't use keyboard equivalents.  I really don't like this option.

I agree; it's unacceptable. But you forgot:

4.) Add menu items Done and Cancel that are identical to the buttons,
	and have the shortcuts be Amiga-D and Amiga-C.

That's what I settled on. That made *all* my keyboard shortcuts be
Amiga-<>, and doesn't interfere with the text entry gadget (which was
the bulk of the application). If you're going to have modes where it
wouldn't be active, you might make unadorned d and c work, as well.

	<mike
From: ina_craig@actew.oz.au (Craig Alexander)
Newsgroups: comp.sys.amiga.programmer
Subject: Want a routine/procedure to draw a circle
Date: 19 Nov 92 13:46:16 EST
Organization: ACT Electricity & Water

Hi !

I am programming with SAS C 5.10 on AmigaDOS 2.04.

I have a program that needs to draw a filled circle.

I have been unable to find a suitable routine supplied with the OS.

I have looked through all of the manuals that I have and cannot find any
function/routines to draw a circle. 

If there is a routine available to do this could someone point me in the 
right direction. If someone has the source for a suitable procedure I would
appreciate if it could be email'ed to me.

Please respond via email 

Craig 

-- 
---------------------------------------------------------------------------
Craig Alexander , ACT Electricity & Water
EMAIL : ina_craig@actew.oz.au
MAIL  : PO Box 996          PHONE : (06) 248 3595 BH
	Woden ACT 2606
	Australia
---------------------------------------------------------------------------
From: Ty_Sarna@fcircus.sat.tx.us (Ty Sarna)
Subject: Re: Attn Commodore: You are making a Big Mistake (Hardware
Newsgroups: comp.sys.amiga.programmer
X-NewsSoftware: BBX-UMB 0.26c beta (Nov 19 1992)
Date: 22 Nov 92 18:31:03 CST
Organization: The Flying Circus Amiga BBX, San Antonio, Texas


In <1992Nov22.192042.10307@freenet.carleton.ca>, aa302@Freenet.carleton.ca (Russell McOrmond) writes:
>   Sorry.  The whole nature of operating systems such as Linux, Mach
> and BSD is that they are source released.  If CBM doesn't provide
> publicly accessable documentation to these people, the Amiga will just
> be dropped as a platform to bother to support these operating systems
> on.

It would still work under copyleft or the Berzerkeley license to just
distribute those driver files as object only, if they weren't copylefted
themselves. Nonoptimal, but better than nothing.

> my DTR issue from a CBM employee, and a few past-employee's have just
> made me begin to think all over again why it is that I bother to
> try to support AmigaDos.

I think the same thing from time to time, but a good session of Xview
programming will cure me quickly... and NFS locking problems, and SunOS
distributed with /etc/passwd and some other files world-writable, and...

>   It's funny that while one shared library (serial.device) gets
> me ticked, it's other shared libraries like xpr*.library,
> xferq.library, etc that keep me with the Amiga.

Every system has it's ups and downs.... Overall the Amiga is a very nice
machine for me, but there are some very annoying things about it.

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::    Ty Sarna, Postmaster       The Flying Circus BBX, San Antonio, TX ::
:: Ty_Sarna@fcircus.sat.tx.us      512/697-9134 (USRobotics Dual Std)   ::
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Organization: Johannes Kepler University Linz - Computing Center
Date: Friday, 20 Nov 1992 14:31:04 CET
From: <K3023E2@ALIJKU11.BITNET>
Newsgroups: comp.sys.amiga.programmer
Subject: DIG/RTG ?

Sorry People...
...
  I didn't get it. What is DIG/RTG ?
...
* "This manual is dedicated to all people WHO MADE AMIGA AND ARE AMIGA"  *
* ( Taken from "hardware reference manual" 2nd edition, page ii )        *
...
Regards, Werner.
...
Everyone has a right of free information... Release AA Chip-Specs and stop
useless discussions