HDTenEightyP/NetNews huggingface dataset:
From: chris@132.236.236.63 (Christopher A. Wolf)
Subject: Illegal device BeginIO _LVO?
Content-Type: text/plain; charset=iso-8859-1
Nntp-Posting-User: tc13@cornell.edu
Reply-To: chris@alchemy.tn.cornell.edu
Content-Transfer-Encoding: 8bit
Organization: none
X-Newssoftware: GRn-beta 1.16g (31.12.92) by Michael B. Smith & Mike Schwartz
Mime-Version: 1.0
Date: Thu, 7 Jan 1993 04:44:47 GMT

Sorry if you've seen this twice - first time it accidentally got
posted to .multimedia instead of .programmer.

I've written a program which needs to SetFunction() the BeginIO vector on
the user's hard-disk device.  The program was crashing hard on systems
which had ICD's IDE disk device (ICDIDEdisk.device I think) installed and I
finally discovered why last night.  The BeginIO _LVO entry for the ICD
device uses a bra.s statement instead of a jmp statement, which, needless
to say, wreaked havoc with SetFunctioning that entry.

Is this a legal practice or is ICD wrong to do this?  Anyone know of any
other hard-disk device drivers which do this so I can warn users of the
problem?

My solution right now is to check to make sure that the _LVO entry starts
with a jmp opcode before trying to SetFunction() it and exitting gracefully
if it doesn't.  Also, someone provided me with a patch program to fix the
ICDIDEdisk.device to use jmp instead of bra.s.  Anyone have any better
ideas or a more general solution which would work even if the _LVO jmp had
been replaced with something else?  (like a moveq and then a bra.s like DOS
1.3 used for some entries I think?)

                                                      - Chris

--
------------------------------------------------------------------------------
Christopher A. Wolf   mail: chris@alchemy.tn.cornell.edu   IRC: cwolf (#amiga)

The rec.arts.sf.starwars Frequently Asked Question List is available via anon.
FTP from the Star Wars archive site at wpi.wpi.edu. "May the FAQ be with you!"
------------------------------------------------------------------------------
From: Jason_Mulligan@camelot.apana.org.au (Jason Mulligan)
Newsgroups: comp.sys.amiga.programmer
Subject: Test
Distribution: world
Date: 30 Dec 92 13:26:17 EST
Organization: The TOWER BBS



 -- AEd V1.36f/EvaA

-- Via DLG Pro v0.992
From: davids@cats.ucsc.edu (Dave Schreiber)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Flushing Devices;  C= doco (mutter!)
Date: 7 Jan 1993 22:19:09 GMT
Organization: University of California; Santa Cruz
NNTP-Posting-Host: as215-ws-19.ucsc.edu


In article <1993Jan7.092127.13752@philips.oz.au> gduncan@philips.oz.au (Gary Duncan) writes:
>Passing thought ; why the heck aren't unused libraries/devices
>flushed automatically anyway? Sounds like a legacy of the days 
>when hard disks were rare and dragging a device off floppy was
>time-consuming. Those days are gone...

Why should they be flushed?  An unused library essentially takes up
zero memory, since the memory it uses can be demanded from it at
any time (and will be demanded from it before a memory allocation
is allowed to fail).  The only people for whom auto-removal of
libraries is important are developers who are checking for memory
leaks; there are plenty of ways of flushing libraries on those
rare occassions when it is needed.

I say this, BTW, as a non-professional developer with lots of hard
drive space and RAM, and who was checking a program for memory leaks
two days ago :-).

>Gary Duncan			gduncan@rosella.pts.philips.oz.au	


-- 
Dave Schreiber  "Look.  Don't touch."  davids@cats.ucsc.edu (until 6/20/93)
Xref: sparky comp.sys.amiga.programmer:18249 comp.sys.amiga.hardware:22536
From: meek@csu.murdoch.edu.au (Lindsay Meek)
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
Subject: Re: HostileTakeOver of Amiga OS
Date: 7 Jan 1993 22:27:48 GMT
NNTP-Posting-Host: fizzy.csu.murdoch.edu.au
Keywords: flame bait lives here

Well, one thing to do before running amok is to own the blitter
properly using OwnBlitter(graphics.library) and DisownBlitter, and
waiting for the blitter to finish before doing anything to the chip
registers. I never had any problems when not using these calls however,
disabling-the-hell out of everything seems to work fine for all the
current Amigas (but not any future ones if they generate their own
interrupts using different chips).
	Make sure you wait for the disk drive to finish writing before
you disable everything however, otherwise your drive will validate
and the blocks queued for writing will be lost. Does anybody know a
commidore unauthorised naughty-bit of code for doing this?

Anarchy rules         
(especially when you have a bug ridden operating system)
Lindsay
From: walker@twix.unx.sas.com (Doug Walker)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: ETA for SAS 6.2?
Date: 4 Jan 93 22:28:08 GMT
Organization: SAS Institute Inc.
Originator: walker@twix.unx.sas.com


In article <C0CAvt.JI8@undergrad.math.waterloo.edu>, svanegmo@cantor.math.uwaterloo.ca (Stephen Van Egmond) writes:
|> I would like to know if there is any rough guesses as to the arrival date of
|> SAS 6.2.  I have a few projects in the works that are would benefit greatly
|> from the use of the math-co, which I can't get to at the moment.  This is just
|> a matter of curiosity, it's not earth-shatteringly important for me.

We have a rather nasty bug that only occurs on 68040 machines 
running 3.0 of the OS.  It has probably been in there all
along, but is showing up with more regularity now.  We are
holding 6.2 until we find and fix this bug.

Unfortunately, we haven't gotten anything done on it since
December 24 (today was our first day back at work since then.)

I can't give you a date because I don't know how long this bug
will take to fix.  It's eluded us for two work-weeks now already.

|> | Stephen Van Egmond (Power Station)        svanegmond@descartes.uwaterloo.ca

-- 
  *****
=*|_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.
Newsgroups: comp.sys.amiga.programmer
From: comeau@csanta.attmail.com (Greg Comeau)
Subject: Re: Version Strings...
Originator: comeau@well.sf.ca.us
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Date: Sat, 9 Jan 1993 01:09:33 GMT

In article <1571@blue.cis.pitt.edu> stern+@pitt.edu (Eric G Stern) writes:
>In article <1993Jan8.111612.25180@sunbim.be> accs1@bagheera.mumath writes:
>>
>>UBYTE Version[] = "\0$VER: ProgName 1.0 (7.1.92)";
>>
>>I wonder why that stays in the executable. I would expect a good compiler  
>>would through that line away unless it is really referenced.
>
>
>If the variable is defined outside a function so that it
>is global, then the compiler can't know that it is not referenced
>in some other possibly separately compiled module and so it
>has to leave it in.

That suffers from that it views a compiler from what I guess is best termed
as a traditional approach wheeas their are explicit things like source
files as well as explicit things like command line compilers (or even
IDE ones) that get provoked by the user for some response.  Even at that
though it suffers from the view of traditional implementations and thier
lack of willingness to socialize with themselves (there can be some level
of smarts in which the compiler can conspire with itself to arrange some
of these).  Additional suffering come in that it doesn't view that the
the compiler can leave the situation in the hands of a so-called
traditional linker, or that a "compiler system" should be able to make
some arrangement for this.

- Greg
-- 
         Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418
                   Producers of Comeau C++ 3.0 With Templates
          Here:attmail.com!csanta!comeau / BIX:comeau / CIS:72331,3421
	    Voice:718-945-0009 / Fax:718-441-2310 / Prodigy: tshp50a
Newsgroups: comp.sys.amiga.programmer
From: sd7047787@v9000 (SD7047787)
Subject: Need help on workstation...
News-Software: VAX/VMS VNEWS 1.41    
Organization: Nanyang Technological University - Singapore
Date: Mon, 4 Jan 1993 14:24:00 GMT

Hi!
I have some problems on workstation. I know this is not the
appropriate place to ask. But pardon me, I really need the answer fast and I 
dunno
which usenet discussion list should I ask. So would some kind souls
out there please help me:

Problem Encounter: In the company I attached, ppl from different departments
log into the few Sun workstations. They left for urgent meetings etc. quite
oftenly without logging out from the station. This cause inconvience to
others who came at random to use the stations.

Solution Requirement: Is there any daemons/programs that came with Sun that I 
can invoke so that
users idled for a period of time will automatically be logged out? I know that 
this is quite
similar to a screen blanker. But I have no idea how to do/program it because it
is also required that the processes status and application programs eg. CAD
program files etc. called/created by the user are saved before the user is 
logged out
of the workstation.

I am no experience user for workstation. I think it might not be possible to
achieve the requirement. But I need advices. Please reply to my address
as far as possible. All suggestions are welcomed! Thanx a million!!!


  |\/\/\/\/|    Steven K.B. |  NTU, Singapore
  |	   |	Internet : sd7047787@ntuvax.ntu.ac.sg
  |	   |	Bitnet   : sd7047787@ntuvax
 (    (o) (o)   
  |        )    You're only young once, but you can  
  |        \    be immature forever...             
  |  _______\   Save our earth. Think GREEN.
  | /           
Newsgroups: comp.sys.amiga.programmer
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re: Programming is getting painful!
Originator: walker@twix.unx.sas.com
Date: Fri, 8 Jan 1993 14:50:49 GMT
Organization: SAS Institute Inc.


In article <C0IwoG.7ow@usenet.ucs.indiana.edu>, shulick@navajo.ucs.indiana.edu (Sam Hulick) writes:
|> 
|> *ARH*!!!  It seems I can't program a thing without memory leaks.  I
|> wrote a little simple server, and I run the server, then shut it down
|> immediately, and sure enough.. about 8k bytes are not freed.  HOW does
|> one trace these memory leaks?  And please don't say MungWall or
|> Enforcer.  I really don't understand one bit of their output.  ANy help
|> would be REALLY appreciated.  Thanks.

|>     // Amiga 3000   ___ \ Sam Hulick: shulick@indiana.edu (NeXTmail OK!)

Get a copy of my memlib stuff.  It should be available on various
PD archives, including Fish Disk #240.  An updated version also
comes with SAS/C 6.0 in the SC:EXTRAS/MEMLIB drawer.

Memlib is designed to catch the following kinds of memory problems:

   *) Not freeing memory
   *) Freeing memory twice
   *) Freeing an incorrect length
   *) Overwriting the beginning or end of a block
   *) Relying on the value of freed memory
   *) Writing to freed memory

If/when it detects an error, it will tell you the filename and line
number of the location that allocated and/or freed the memory.

As for enforcer/mungwall output, LEARN HOW TO USE IT.  Enforcer in
particular is a critically important tool.  If you're using SAS/C
Version 6.x, the CPR debugger will automatically use enforcer to
stop your program at the location that is causing the enforcer hit;
this is probably the easiest way to use it.

-- 
  *****
=*|_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.

Newsgroups: comp.sys.amiga.programmer
From: juncewic@dodo.cis.ohio-state.edu (thomas michael juncewicz)
Subject: ScrollVPort vs ScrollRaster
Organization: The Ohio State University Dept. of Computer and Info. Science
Date: Wed, 6 Jan 1993 14:35:58 GMT


Calling all gurus,
	I wish to write a game that uses 8-directional smooth-scrolling.  I've
looked into ScrollVPort() and ScrollRaster(), but I'm confused (and
the RKM manual I have has 1 sentence about each function).  The way I think
I understand it, ScrollRaster() actually moves data thru the BitMap(raster)
while ScrollVPort() just moves the ViewPort "window" around over different
parts of a BitMap.  Is this right?  If so, then ScrollRaster would seem
too slow to do the job (like if I had to scroll an entire screen of stuff)
and ScrollVPort wouldn't work either as my 'playfield' will be quite
large and therefore couldn't fit into 1 raster (1024 x 1024).  So what do you
you all recommend?  Oh, BTW, I want to be as system friendly as possible, so
I'd like suggestions that will work on other Amigas, from 1.3-3.0 KS and
68000-68040.  Plus, I'd prefer a C solution but I can work with assembly
if necessary...Thanx in advance.
From: jm372s420@sycom.mi.org (John Martin)
Newsgroups: comp.sys.amiga.programmer
Subject: Serial Help, Basic term source?
Distribution: world
X-BBS-Software: EXCELSIOR! V0.975
Date: 5 Jan 93 04:22:35 EST
Organization: Michigan Information eXchange

Does somebody out there have a basic term source in C?  Something even as 
simple(?) as opening a screen, opening the serial.device, then allow you to 
enter at commmands.. (call out, set auto-answer, etc.) then allow you to 
close screen, which would close the device. Am I making this sound much 
easier than it is to do??  Thanks...
 
            John Martin
Newsgroups: comp.sys.amiga.programmer
From: comeau@csanta.attmail.com (Greg Comeau)
Subject: Re: Wanted: info on available C++ compilers
Originator: comeau@well.sf.ca.us
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Date: Wed, 6 Jan 1993 04:52:31 GMT

In article <1h5pgkINNp36@huon.itd.adelaide.edu.au> wayne@cs.adelaide.edu.au (Wayne McKeen) writes:
>
>I am looking for a decent C++ compiler for the Amiga and I have not able
>to find any dealers in S.A., and very few elsewhere. What compilers are
>available, at what cost, and from where can I get one? I am aware of the
>existence of g++, however I would like information on the commercial C++
>compilers which are available.

Comeau C++ 3.0b With Templates is one possibility.  For AmigaDOS, the
cost is $US250.  It could be express mailed to S.A. for an additional
$US60, and you'd have it "within hours".

- Greg
-- 
         Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418
                   Producers of Comeau C++ 3.0 With Templates
          Here:attmail.com!csanta!comeau / BIX:comeau / CIS:72331,3421
	    Voice:718-945-0009 / Fax:718-441-2310 / Prodigy: tshp50a
Newsgroups: comp.sys.amiga.programmer
From: brycerw@brandonu.ca
Subject: Re: IFF DR2D drawing creation help
Organization: Brandon University, Brandon, Manitoba, Canada
Date: Thu, 7 Jan 1993 18:19:51 GMT

In article <Douglas_Stockman.1n3x@graceUUCP>, Douglas_Stockman@graceUUCP (Douglas Stockman) writes:
> Greetings!,
>    I want to output some simple graphic objects using the IFF DR2D
> standard, but am not sure where to begin.  I have the doc files
> located in the RKRM:Devices and I have the reader and writer routines
> graciously supplied by Jeff Blume of Stylus, Inc.  Unfortunately,

I, too, am trying to produce DR2D files.  All I've got are the docs in the
RKRM:Devices book.  And after looking at the PageStream import file, I think
these docs are out of date.  Are these reader and writer routines PD?  Can
I get a copy, somehow?  Where can I get up-to-date docs?

> this simple mind of mine is not putting all the pieces together.  If
> someone has some very simple code to share with me or advice on how
> to write some basic code, I would be very thankful.  Even just showing
> me how to create an IFF DR2D file that draws a line, polygon, or some
> text would probably point me in the correct direction.  Writing the
> information out appears to be straightforward.  I seem to be stuck
> on writing the commands that define the graphical objects/drawing.

Ditto, for me.
> 
>    On a related topic, is there any utility/program that will allow
> me to view this IFF DR2D file once I create it (that is short of
> purchasing an expensive commercial product that has another purpose
> entirely)?  To debug any code I write, I will need to visually see
> the error of my ways.  Thanks to all.
> 
> 
> -- Via DLG Pro v0.992
> 
Robert Bryce
BRYCERW@BrandonU.CA
Newsgroups: comp.sys.amiga.programmer
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re: HELP: malloc() and system dependancy
Originator: walker@twix.unx.sas.com
Date: Mon, 11 Jan 1993 20:57:14 GMT
Organization: SAS Institute Inc.


In article <1993Jan11.144745.999@uoft02.utoledo.edu>, mneylon@jupiter.cse.utoledo.edu (Michael Neylon) writes:
|> It seems that the memory gets trashed at some point after allocation, because
|> we have verified that the file is read properly, but otherwise we have no clue.
|> 
|> -- 
|> Michael Neylon   aka Masem the Great and Almighty Thermodynamics GOD!

DEFINATELY try compiling and linking with my memlib stuff, in
SC:EXTRAS/MEMLIB.  Read the "readme" file in there for details.

-- 
  *****
=*|_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.

Newsgroups: comp.sys.amiga.programmer
From: breese@monet.imada.ou.dk (Bjoern Reese)
Subject: Re: Hardware bashing demo takes an OS friendly turn.
Organization: Dept. of Math. & Computer Science, Odense University, Denmark
Date: Fri, 8 Jan 1993 15:01:12 GMT

Thanks to everybody who replied that WaitBlit() preserves the
scratch registers (condition codes doesn't matter). Now I will
definitely use WaitBlit().

--

Bjoern Reese                   |     Email: breese@imada.ou.dk
Odense University, Denmark     |     Voice: +45 65 932 182 (private)
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
From: spc@pineal.math.fau.edu (Sean 'Captain Napalm' Conner)
Subject: HostileTakeOver of Amiga OS
Followup-To: comp.sys.amiga.programmer,comp.sys.amiga.hardware
Summary: How to take over the OS
Keywords: flame bait lives here
Organization: Florida Atlantic University, but who cares?
Date: Mon, 4 Jan 1993 19:33:25 GMT

(donning asbestos long johns in preparation of a potential flame-a-rama)

  I'm currently trying to write some code to take over the Amiga system from
the OS, do what ever I want to the hardware, and then return the system back
to the OS in as much of the same state as it was before I took it over.

  So, what I'm wanting to know, is what exactly do I need to do to (in as
friendly a mannor as possible) to take over the system from the OS.  Code
fragments (in any language) would be nice, as well as possible
warnings/cavets/etc ... that may be required.

  The system I'm doing this on is an Amiga 500 running 1.3 with 3M RAM (512K
of that is chip) and a 50M harddrive.

  I have some code to take over the machine, but one fragment comes from a
commercial quality game (written by a professional game writer as a tutorial
on writing games for the Amiga), and the other from one of the (not that I
want to use this, mind you) Abacus books.  I was wondering if there were any
'better' ways of taking over the machine than just to disable all DMA and
interrupts and then running amok in the system 8-)

  Thanks in advance (and I may even post the routines when I write them if
there is sufficient interest in it).

  -spc (And yes, I do respect the OS and appreciate it, but sometimes, I
	would like to hit the hardware and not worry about the OS at all)
Newsgroups: comp.sys.amiga.programmer
Subject: Public screen - how?
From: alien@acheron.amigans.gen.nz (Ross Smith)
Date: 2 Jan 93 02:01:51 GMT+12
Distribution: world
Organization: Muppet Labs

How do you make a screen public (from a C program)? The Libraries RKM
(3rd ed., p. 53) says to use the PubScreenStatus() function, but that
function's autodoc says that it can only be used to make a public screen
private, not vice versa. So once I've opened the screen (with an SA_PubName
tag), how do I switch it from private to public?


--
...... Ross Smith (Wanganui, NZ) ...... alien@acheron.amigans.gen.nz ......

"I blame you for the moonlit sky and the dream that died with the Eagle's flight
I blame you for the moonlit nights when I wonder why are the seas still dry
Don't blame me, sleeping satellite"                              (Tasmin Archer)

--
From: davidj@cbmvax.commodore.com (David N. Junod)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Regions and BOOPSI gadgets?
Date: 11 Jan 93 19:08:38 GMT
Reply-To: davidj@cbmvax.commodore.com (David N. Junod)
Distribution: comp
Organization: Commodore, West Chester, PA

s37732v@snakemail.hut.fi (Markus Juhani Aalto) writes:
>
>Hi!
>
>I've been programming a gadtools listview replacement with BOOPSI gadgets
>and it worked alright until I started to use Regions to clip my drawing
>to the rastport. I currently InstallClipRegion when I get GM_RENDER
>message and do my rendering after that. This works fine when I open
>the gadgets but after I size the window all clipping goes absolutely
>out of control. So is there a possible way to use Regions in BOOPSI
>gadgets? 
>
>I think that the problem is with InstallClipRegion routine used
>between Refreshing because of window sizing. I just can't imagine any
>other way to do clipping properly and fast.

Here's a fragment from one of my boopsi objects that installs a clipping
region while rendering.

struct Region *
installclipregion (struct Window *w, struct Layer *l, struct Region *r)
{
    BOOL refresh = FALSE;
    struct Region *or;

    if (w->Flags & WINDOWREFRESH)
    {
	EndRefresh (w, FALSE);
	refresh = TRUE;
    }
    or = InstallClipRegion (l, r);
    if (refresh)
	BeginRefresh (w);
    return (or);
}

LONG
renderMethod (Class *cl, Object *o, struct gpRender *msg)
{
    struct Window *win = msg->gpr_GInfo->gi_Window;
    struct objectData *od = INST_DATA (cl, o);
    struct Rectangle rect;
    struct Region *or;

    /* ... your region is created in OM_NEW and deleted in OM_DISPOSE */
    ClearRegion (od->od_Region);
    /* Fill in the rectangle structure here...*/
    /* In 3.x and beyond, you can set up the region in GM_LAYOUT instead
     * of every single GM_RENDER call */
    OrRectRegion (od->od_Region, &rect);
    or = installclipregion (win, msg->gpr_RPort->Layer, od->od_Region);

    /* do your rendering in here... */

    installclipregion (win, msg->gpr_RPort->Layer, or);
}

>*         Markus Aalto              | Helsinki University of Technology  *

~DNJ~
From: cunniff@cup.portal.com (Ross Alan Cunniff)
Newsgroups: comp.sys.amiga.programmer
Subject: DR2D sample code
Date: Sat,  9 Jan 93 09:35:12 PST
Organization: The Portal System (TM)

The next two responses from me will contain a uuencoded zoo of
the DR2D sample code which uses iffparse.library.  Included are
routines to display a DR2D as a PostScript file, which you can
examine with Post or by copying to a PostScript printer.  I'm
posting this here because Portal doesn't seem to want me posting
to alt.sources.amiga (it thinks the group is moderated...).  If
somebody wants to place this on an FTP site, feel free.

Ross Cunniff
President, Stylus, Inc.
cunniff@cup.portal.com