HDTenEightyP/NetNews huggingface dataset:
From: dac@prolix.pub.uu.oz.au (Andrew Clayton)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Fun w/DateStamp
Date: Sun, 23 Aug 92 10:24:44 GMT
Reply-To: munnari!labtam!eyrie!prolix!dac
FollowUp-To: comp.sys.amiga.programmer
Keywords: 
Organization: More like Dis~, really.

In article <1992Aug22.190411.1049@CS.ORST.EDU>, Glade Diviney writes:

> 
>   Okay, fellow power users/codes.  For a project I'm working on, I need
>   to deduce the current date.  DateStamp does the trick, of course, but

...

   long   timestart, timeend, tottime;	// for time information

   timestart = time(&timestart);

   fprintf(stderr,WELCOME"\n%s",ctime(&timestart));
                                ~~~~~
...

produces 

Myjunkywelcomestring
Sun Aug 23 20:26:40 1992

This is using SAS/C 5.10a

Dac
--
munnari!labtam!eyrie!prolix!dac      David Andrew Clayton.           // _| _  _
  prolix!dac%eyrie@labtam.oz.au      Canberra, Australia           \X/ (_](_](_
        dac@prolix.pub.uu.oz.au      I post .
prolix!dac@sserve.cc.adfa.oz.au            . . I am.             +61 6 290 2215
Newsgroups: comp.sys.amiga.programmer
From: kopnicky@owlnet.rice.edu (Lyle Warren Kopnicky)
Subject: Re: LOOK, CBM IS WORKING HARD...
Organization: Rice University
Date: Wed, 26 Aug 1992 02:28:12 GMT

In article <1992Aug7.003216.16043@cs.su.oz.au>, ronny@basser.cs.su.oz.au (Ronald Cook) writes:

|> * Faster processors - up to the 68030 (from CBM - I'm not talking about third
|> 	parties here, and I don't *think* a CBM 68040 Amiga has come out.)
|> 	If you're impressed by this, why?

The Amiga 3000T now ships withh a 25 MHz 68040 CPU.

-- 
--------------------------------------------------------------------------
  They Love, They Share        -            They Share and Love and Share
    Love, Love, Love           -                Share, Share, Share
                   The Itchy and Scratchy Show!
--------------------------------------------------------------------------
"Elvis has left the building." / Quantum Seep / kopnicky@owlnet.rice.edu
--------------------------------------------------------------------------
From: heinz@edohwg.UUCP (Heinz Wrobel)
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  Speculations: Amiga and Mach?
Date: 25 Aug 92 20:12:15 GMT
Organization: Edotronik GmbH

In article <wk+yr*dS0@caleb.UUCP> jdp@caleb.UUCP (Jim Pritchett) writes:
>In article <rwm.713991011@atronx.OCUnix.On.Ca>, Russell McOrmond writes:
>
>>   Developers need firewalls, users do not.  Developers use MMU based machines.
>
>I strongly disagree with this statement.  I have had several "commercial"
>programs which would not run well together.

How about: Developers __SHOULD__ use MMU based machines.

>						 Jim Pritchett

--
Heinz Wrobel, Edotronik GmbH (ECG018)
FAX +49 89 850 51 25 / TEL +49 89 850 25 20 (HOME!&VOICE, sometimes...)
From: lofaso@tsd.arlut.utexas.edu (Bernie Lofaso)
Subject: Re: Question about GCC and DICE?
Organization: Applied Research Labs, University of Texas at Austin
Date: Mon, 31 Aug 1992 13:16:54 GMT

malcolm@emcamiga.UUCP (E. Malcolm Crosby) writes:

>I recently, in the last day or so, installed GCC 2.2.2 on my system and
>from what I can tell it works ok. The question I have is about acquiring
>Commodore's 2.0 header files for use with GCC.

>I'm planning on getting a registered copy of DICE and have a few questions
>about it. 

>  1.  Does the registered version of DICE come with CBM's 2.0 headers and
>      libraries?

Yes to both questions.

>  2.  Will the 2.0 headers and libraries that come with DICE also work with
>      GCC or will I have to get them seperately?

	Most of the 2.0 headers will work - You'll have to use stdio.h that's
compatible with gcc (like from ixemul library). The libraries won't work
directly, but Markus has been kind enough to write the 'hunk2gcc' translater
that will allow you to create GCC compatible libraries from the Amiga ones.

>  3.  I'd also like to know how others feel about DICE as compared to SAS &
>      Manx.

Don't know about SAS, but I prefer it to Manx. Code is usually faster and
smaller, though mainly the compiler is more robust.

>  4.  How ANSI compatible is DICE? I take source code between systems quite
>      frequently (Amiga Manx, MS-DOS Borland C++ and HP Unix systems at 
>      school).

Seems pretty compatible to me. At least I haven't run into any problems.
But then again, I'm used to writing for our brain dead non-ANSI Sun
compilers at work.

Bernie Lofaso
Applied Research Labs
From: malcolm@emcamiga.UUCP (E. Malcolm Crosby)
Newsgroups: comp.sys.amiga.programmer
Subject: Question about GCC and DICE?
Date: Sun, 30 Aug 1992 21:39:59 EDT
Reply-To: emcamiga!malcolm@redpoll.neoucom.edu
Distribution: world
Organization: Personal UUCP System
X-Newsreader: Arn V1.00 alpha rel3

I recently, in the last day or so, installed GCC 2.2.2 on my system and
from what I can tell it works ok. The question I have is about acquiring
Commodore's 2.0 header files for use with GCC.

I'm planning on getting a registered copy of DICE and have a few questions
about it. 

  1.  Does the registered version of DICE come with CBM's 2.0 headers and
      libraries?
  
  2.  Will the 2.0 headers and libraries that come with DICE also work with
      GCC or will I have to get them seperately?

  3.  I'd also like to know how others feel about DICE as compared to SAS &
      Manx.

  4.  How ANSI compatible is DICE? I take source code between systems quite
      frequently (Amiga Manx, MS-DOS Borland C++ and HP Unix systems at 
      school).

----
E. Malcolm Crosby

Internet:   mcrosby@bsa1.kent.edu
E-Mail:     emcamiga!malcolm@redpoll.neoucom.edu (E-Mail Please)
Newsgroups: comp.sys.amiga.programmer
From: lahurst@unix1.tcd.ie ( )
Subject: ToggleSelect + MutualExclusion Gadgets.
Organization: Trinity College, Dublin
Date: Thu, 27 Aug 1992 20:43:39 GMT

I want to have the same day buttons as those that appear on the Time util
in the prefs drawer on a program I am writing.

If someone has done this ... HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HE



LP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP Please.. Pretty Please..
 
Newsgroups: comp.sys.amiga.programmer
From: rb345@rbhp25.rbg.informatik.th-darmstadt.de (Matthias Meixner)
Subject: Re: Double buffering and flicker..
Date: Thu, 27 Aug 1992 15:03:03 GMT
Organization: TH Darmstadt
Keywords: WaitBOVP() and WaitTOF()...

In article <mcuddy.714894318@fensende>, mcuddy@fensende.Rational.COM (Mike Cuddy) writes:
|> I've got some double buffer routines that I'm putting the final touches
|> on, but I can't seem to grok what's wrong with the page-flip routine:
|> In short, I'm using 'view-swapping' (i.e.: two copper lists, one view, and
|> LoadView()), and just before I do the LoadView(), I do a WaitTOF().  
|> Unfortunately, when I do this, the double buffering flickers like mad!
|> (The graphics can't be seen while they're being drawn, so I know I'm
|> drawing on the right page...)
|> 
|> The catch is, when I use WaitBOVP() with the last ViewPort in my view, 
|> everything works fine. But, according to the RKM, WaitBOVP() busy waits, 
|> and that's bad. (I'm trying to be system friendly!)
|> 
|> *HELP*
|> 
|> BTW: I'm on a 68040 based system (RCS FF40), and I thought that the extra
|> speed might have something to do with it (trying to display more than 60FPS)
|> but the tearing happens in 68K mode also.
|> 

Try RemakeDisplay() instead of LoadView(), maybe this will help you, but i don't
know if this will fix the flicker.


|> --Mike Cuddy (mcuddy@rational.com, fensende!mcuddy@apple.com)
|> To Anachreon in Heav'n/Where he sat in full glee/A few sons of harmony sent a 
|> petition/That he them inspi-re and patron would be/When this answer arrived/
|> from the jolly old Grecian/"Boys fiddle and flute,/no longer be mute,/
|> I'll lend 'ye my name/And inspire ya' ta' boot/And besides I'll instruct 'ye/
|> like me, to entwine/ the Myrtle of Venus with Bacchus' vine!
|> -- sing to the tune of the star spangled banner... (these are the orig words,
|> yes folks, our national anthem is a ``let's get drunk and F*** song'').

-Matthias
From: forgeas@swinjm.UUCP (Jean-Michel Forgeas)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: 1.2, 1.3, and 2.0 question
Date: 30 Aug 92 14:13:46 GMT
Reply-To: cbmvax!cbmehq!cbmfra!swinjm!forgeas (Jean-Michel Forgeas)
Organization: The Software Winery
X-Newsreader: Arn V1.00 alpha rel2

In article <64890@cup.portal.com>, ANTHONY FRANCIS PRESTON writes:

> [...] a problem running the programs this way(i.e. Execut("program",0,0); )
> People have reported they do not run(guru, lockups, inconsistant behavior)
> under 1.3.  I am using Execute, not System.

Try to give an output stream to the program. For example:

    if (nil = Open( "nil:", MODE_NEWFILE ))
        {
        Execute("program",0,nil);
        Close( nil);
        }

Be carefull in 1.3, if "program" launches itself other programs, it must have
something more consistent than nil:, so in this case you better should open
a "con:........" for Execute() instead of nil:.

Best regards
    Jean-Michel
--
Jean-Michel Forgeas         uunet!cbmvax!cbmehq!cbmfra!swinjm!forgeas
4 rue du General Leclerc                       __
95210 Saint Gratien, France                    \/
Newsgroups: comp.sys.amiga.programmer
From: vsanchez@casbah.acns.nwu.edu (Victor Sanchez)
Subject: Re: SimpleRexx 2.0
Organization: Northwestern University, Evanston Illinois.
Date: Thu, 27 Aug 1992 17:37:06 GMT

In article <1992Aug27.120316.2063@cas.org> vjh21@cas.org (Vince Herried) writes:
>
>Some time back I ordered from CATS the 2.0 native developers disks
>and the programmers guide to AREXX.  Well the mail arrived....
>
...
>The native developers disks were screwed up, the invoice said it was
>supposed to be 2.04 but the disks were all 1.3  Sigh...
>I'm probably out $20.00 plus shipping.  Anyone care to send me their
>copy, I can produce an invoice saying I paid for 2.04 so it ain't like
>I'm stealing em.

I have a similar problem. I received the 2.0 Native developers disks
but did not receive the AREXX guide. Can anybody provide me with a 
phone number for Dept. C to inquire?

	Thanks,
	Victor
From: gest_ss@uhura.cc.rochester.edu (Gavin Stark)
Newsgroups: comp.sys.amiga.programmer
Subject: fork() for AmigaDOS?
Summary: Is there such a thing?
Keywords: fork
Date: 26 Aug 92 01:04:50 GMT
Organization: University of Rochester - Rochester, New York

Is there a AmigaDOS fork() that works like UNIX fork()?

Or is there a way to get a 'C' program to spawn a subroutine as a child that
runs concurently?

-- 
_______________________________________________________________________________
Gavin Stark          gest_ss@troi.cc.rochester.edu      University of Rochester
"But alienation's for the rich and I'm a-feelin' poorer every day." - TMBG
From: Aurelius@cup.portal.com (Mark Christian Barnes)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Assembler programming.
Date: Sun, 23 Aug 92 12:37:14 PDT
Organization: The Portal System (TM)
Distribution: world
  <1992Aug21.220718.24365@jato.jpl.nasa.gov>

<stuff deleted>

|>Paragraph 2.11.2.5: Address Register Indirect with Index
|>
|> ... The address of the operand is the sum of the address in the
|>address register, the sign-extended displacement integer in the
|>low order eight bits of the extension word, and the contents of
|>the index register...
|>
|> SYNTAX:  d8(An, Xn.W), or (d8, An, Xn.W)
|>          d8(An, Xn.L), or (d8, An, Xn.L)
|>
|>                       Regards, Aurelius@cup.portal.com
|  
|I stand corrected. Quite unnerving to think that in situations where address
|register indirect with index type addressing is used (i.e. null terminating
|a string: move.b #0,(a0,d0.w) ) requires an additional memory read _just_
|to find out that the displacement value wasn't given (zero). The assembler I
|use obviously assumes a zero displacement value in the event I don't specify
|one, because it doesn't complain.
| 
|jeff

 Not exactly Jeff, Indirect with Index addressing takes *one* extension
word. This is in addition to the opcode word. The high byte of the
extension word specifies the index register and its size. The low byte
is the displacement integer, which will be signed extended.

 Although, :-), on the 68020+ processors, the displacement can be 8,
16, or 32 bits. The 8 bit form is what I have described. The 16 and
32 bit forms *do* have to read *two* extension words, as you feared.

			Regards, Aurelius@cup.portal.com

PS: Always use legal syntax. Assemblers may allow you to save
    a little typing (and thinking) by permitting degenerate
    forms (like your example) or aliases (like MOVE x,An
    instead of MOVEA x,An), but it can just lead to confusion
    in the long run.
From: heinz@edohwg.UUCP (Heinz Wrobel)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Breaks
Date: 30 Aug 92 10:54:52 GMT
Organization: Edotronik GmbH

In article <5215@tuegate.tue.nl> marcelk@blade.stack.urc.tue.nl (Marcel van Kervinck) writes:
>This is probably a FAQ, but I can't find a decent answer anywhere.
>
>What is the correct way to detect user breaks (CTRL-C,D,E,F) in machine
>code? I noticed that they are implemented as signals (12..15 as I remember)

You use a Signal() call to check SIGBREAKF_CTRL_C/D/E/F to check them or
better CheckSignal() in >=V36.

>but according to my documentation those are reserved for system use.

They have a system defined meaning. You are allowed to check for them.

>Is it correct to use SetException() on them?

It's ok to use SetException() on them but maybe it's easier for you to use
CheckSignal() in your program.

> - Marcel van Kervinck

--
Heinz Wrobel, Edotronik GmbH (ECG018)
FAX +49 89 850 51 25 / TEL +49 89 850 25 20 (HOME!&VOICE, sometimes...)
From: dej@qpoint.ocunix.on.ca (David Jones)
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  fork() for AmigaDOS?
Distribution: world
Date: 28 Aug 92 20:38:43 EST
Organization: Dejital Software

In article <paulk.1a06@terapin.com> paulk@terapin.com (Paul Kienitz) writes:
>> Is there a AmigaDOS fork() that works like UNIX fork()?

Although CreateNewProc() can be used to create a new process, there is
a fundamental difference in OS design between AmigaOS and Unix which
can seriously affect the way a Unix programmer designs an Amiga program.

Under Unix, fork() causes an exact copy of the currently executing
process's memory image to be made.  The resulting parent and child
processes do not share any common memory (unless they deliberately
set up a shared memory segment).  Also, file handles are duplicated
so that both parent and child have open whatever was open just before
the fork() call.  When setting up pipes, usually parent and child
close opposite ends of a pipe so that data transfer is unidirectional.

Under AmigaOS, there is no memory protection, so separate core images
are impossible (for now).  Also, no system resources are duplicated,
so closing a file in one process will cause the other process's file
to be closed as well.  (Not the case in Unix).

An example of this difference in design can be seen in the gnutar
source code.  Under Unix, gnutar forks twice if compressed archiving
is requested: a reader process, a writer process, and compress.
Under AmigaOS, gnutar cannot compress.  Reason: although AmigaOS can
spawn child processes, the differences in pipe handling required
between AmigaOS and Unix would have made the program too difficult
to port, so compression was not supported on the Amiga.

--
 David Jones, 6730 Tooney Drive, Orleans, Ontario K1C 6R4 CANADA
       email: dej@qpoint.ocunix.on.ca    Fido: 1:163/109.8
 AMIGA: Advanced Multimedia with Interactive Graphics and Audio
From: pblum@vsbbs.UUCP (Paul Blum)
Newsgroups: comp.sys.amiga.programmer
Subject: Re:   ToolMaker from CATS
Date: 3 Sep 92 06:54:05 PST
Organization: BBS

How can a person get ToolMaker if you're not a developer?
Newsgroups: comp.sys.amiga.programmer
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re: SAS/C 6.0 Details (LONG!)
Originator: walker@twix.unx.sas.com
Date: Wed, 26 Aug 1992 13:32:47 GMT
Organization: SAS Institute Inc.


In article <1992Aug26.124301.22998@email.tuwien.ac.at>, mjl@newton.auto.tuwien.ac.at (Martin J. Laubach) writes:
|> |> So, when I switch to V6.0 I'll have to set all my library pointers to NULL
|> |> after CloseLibrary(), in order to avoid autoterm() to close it again ?
|> 
|>   No. You'd only need to do this if your code opens and closes the libraries
|> yet does not define the library base -- quite unlikely, I'd say.
|> 
|> 	mjl

No, his code would still work even if he doesn't define the library
base.  It would just open the library redundantly.

I'll quote myself here (this was a posting from a couple of days ago):
|> 
|> The autoinit code does this:
|> 
|>    static struct Library *libbase;
|>    tmpbase = IntuitionBase = OpenLibrary("intuition.library",__oslibversion);
|>    ...
|> 
|> The autoterm code does this:
|> 
|>    CloseLibrary(libbase);
|> 
|> This means that, no matter what your code does with IntuitionBase, the library
|> is still closed the same number of times that it is opened.  Many people do
|> this when they close the library:
|> 
|>    CloseLibrary(IntuitionBase);
|>    IntuitionBase = NULL;
|> 
|> The reason we use the static variable 'libbase' is so we can still close the
|> library the correct number of times if you set the library base to NULL in
|> your own code.

Hmm, looks like there is an error there - that "tmpbase = " should
be "libbase = ".  That's what comes of typing in code on the fly.

In any event, no existing code will break.

-- 
  *****
=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
 *|. o.| ||                                          1200/2400/9600 Dual
  | o  |//     For all you do, this bug's for you!
  ====== 
usenet: walker@unx.sas.com                            bix: djwalker 
Any opinions expressed are mine, not those of SAS Institute, Inc.
From: adonkin@waikato.ac.nz
Newsgroups: comp.sys.amiga.programmer
Subject: Debugger ftp site?
Date: 31 Aug 92 10:42:13 +1200
Organization: University of Waikato, Hamilton, New Zealand

	I have PowerVisor 1.0 Beta, and I'm very impressed with what it can do. 
However it is very sensitive under 1.3 and some things don't work under 2.0
(e.g. conditional breakpoints).  Is there a more recent release somewhere? 
Failing that, a better debugger (although I'd like to stick with PV)?
	Thanks for your help... Andrew.	

--
     ///            Please mail to...
 \\\///     Andrew Donkin, adonkin@mars.cs.waikato.ac.nz
  \XX/
Newsgroups: comp.sys.amiga.programmer
From: coup@crs.cl.msu.edu (Chris Klaus)
Subject: workbench size modified in C (src wanted)
Reply-To: coup@crs.cl.msu.edu.UUCP (Chris Klaus)
Organization: Michigan State University
Date: Sat, 29 Aug 92 04:08:26 GMT




I am looking for src code regarding modifying the size of workbench.
In C, I want to change the number of pixels from 640x200 to
650x210.   Can someone show me some example src code how I would
change the workbench size?   

thank you.
---
coup@crs.cl.msu.edu cklaus@hotsun.nersc.gov @cklaus%hotsun.nersc.gov@llnl.gov
From: mpue2@syma.sussex.ac.uk (James E. Talbut)
Newsgroups: comp.sys.amiga.programmer
Subject: Gcc 2.2.2 Man, WAS: Re: InfoView
Date: 1 Sep 92 14:21:26 GMT
Organization: University of Sussex, five miles away from Brighton

In article <1992Aug29.122350.26972@bernina.ethz.ch> wild@nessie.cs.id.ethz.ch (Markus Wild) writes:
>In article <SIE.92Aug28140811@introitus.fulcrum.bt.co.uk> sie@fulcrum.bt.co.uk (Simon Raybould) writes:
>>Has anyone got InfoView distributed with gcc2.2.2 working ?
>>I just get "Your terminal isn't clever enough" or something like that.
>
>And you did remove any TERMPATH variable from env: and envarc:? This is in 
>the README as well...
>

Not really connected with the first question 'cos my InfoView works,
(though GNU Emacs is much better at it!) it's just that my man doesn't!

I had it working once and now it seems to have stopped, whenever I call
it dwith a subject that it has a man page for it simply does nothing!
It does correctly report problems with non-existent man pages.
Any ideas?

	J.T.
-- 
Fine beer may be judged with just one sip,
	but it's better to be thoroughly sure.  -  Czech proverb

James Talbut            mpue2@syma.susx.ac.uk
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: ClearEOL and SetAPen
Date: 2 Sep 92 20:42:11 GMT
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA

chrisg@cbmvax.commodore.com (Chris Green) writes:
>In article <65079@cup.portal.com> Lee_Robert_Willis@cup.portal.com writes:
>>Out of curiousity: _Why_ is SetAPen() slow?  What is involved in changing
>>the pen color besides simply storing the new value?
>>
>	SetAPen figures out new minterms for the blitter, based on the DraMod
>and BPen.
>	Reports of its slowness are greatly exaggerated (at least under >2.0).

	For a comparison, in 1.3 SetAPen (et al) took roughly 1400 68000
cycles to do.  In 2.0, if I remember correctly, they take ~200-700 cycles
depending on drawmode/etc.  (I did the first cut at optimization of them
back in the early 1.4 days, later redone by Bart for a few more cycles.)

-- 
"Rev on the redline, you're on your own; seems like a lifetime, but soon it's
 gone..."  Foreigner
-
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.
Newsgroups: comp.sys.amiga.programmer
From: jamie@cdevil.unx.sas.com (James Cooper)
Subject: Re: lpatch/lcompare from SAS
Originator: jamie@cdevil.unx.sas.com
Date: Fri, 28 Aug 1992 15:15:24 GMT
Organization: SAS Institute Inc.


In article <1992Aug27.195216.1@misvax.mis.arizona.edu>, gstark@misvax.mis.arizona.edu writes:
>
>I was told by SAS that I need to use a program called "lcompare" to
>generate files usable by "lpatch" if I want to generate binary diffs. 
>Where-o-where can I find lcompare?  I did an archie search but it turned
>up nothing.  From what I gathered from SAS lcompare/lpatch are
>distributable.  Is this true?  If so, perhaps someone could tell me where I
>could FTP it from?  

lpatch is freely-distributable, but lcompare is *not*.

To get a copy, send your serial number to SAS, Amiga Tech Support, and
someone can send you a copy.

-- 
---------------
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.
From: utoddl@guitar.oit.unc.edu (Todd M. Lewis)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: using 1.3
Date: 4 Sep 92 20:08:36 GMT
Organization: UNC Office of Information Technology

In article <1992Sep2.162023.1200@ultb.isc.rit.edu> tsm2124@ritvax.isc.rit.edu  
writes:
>Not that I want to put anyone down or anything.  But Commodore has officially
>pronounced Kickstart/Workbench 1.3 DEAD a long time ago.

Neat!  It's still alive in about 2.5 million machines.

>  So all in all, I would just like to ask developers to develop for
>the current most powerful version of the OS.

My publisher pays about half as much for a 2.0-only program as compared to a
1.3 compatible program.  I have a mortgage, I like to eat, I have to buy gas
for the car and new programming tools and manuals, I prefer clean underwear.
What do you want to _PAY_ for 2.0-only programs?

>			Todd Major

I like the name.

--
Todd M. Lewis / Todd_Lewis@unc.edu / utoddl@guitar.oit.unc.edu