HDTenEightyP/NetNews huggingface dataset:
Newsgroups: comp.sys.amiga.programmer
Subject: .ICO/.BMP -> Amiga Format
From: robbins@brandonu.ca
Date: 28 Jul 92 18:03:46 CST
Organization: Brandon University, Brandon, Manitoba, Canada

A simple and short question - since my last one about handlers and devices must
have been too hard - since it only got 1 reply...

Has anyone written or know of programs to convert MSDOS/Windows .ICO and .BMP
files to Amiga format for use as icons/imagery/etc.

I realize that some sort of colour mapping may be necessary but since people
have done this for GIFs, I would assume .ICO/.BMP would also have been done.

If anyone could provide me with such or at least point me in the right
direction, I would appreciate it.

And if anyone else would again like to try my first question about handlers and
devices, I wouldn't mind that either...

Thanks in advance.

Wayne Robbins
Email:  Robbins@BrandonU.CA
From: chopps@ro-chp.UUCP (Chris Hopps)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: MUNGWALL 37.54 uploaded
Date: Wed, 29 Jul 1992 18:28:02 GMT
Keywords: Mungwall V37.54 Programming Debug tools
Summary: Available here.
X-Newsreader: Arn V1.00 beta rel2

In article <8blqr*PJ0@caleb.UUCP>, Jim Pritchett writes:

> Has anyone made the above program available for bms?
>
>                                                 Jim Pritchett


Sure have. see address below.
("BMS:Pub/Prog" is where it resides)

>
>
> UUCP:  rwsys.lonestar.org!caleb!jdp
>  or    utacfd.uta.edu!rwsys!caleb!jdp
------------------------
The Royal Oak Chophouse >> Chris Hopps
Royal Oak, Michigan     >> sycom.mi.org!ro-chp!chopps
From: peterk@cbmger.de.so.commodore.com (Dr Peter Kittel Germany)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Hey Commodore types
Date: 23 Jul 92 06:46:11 GMT
Reply-To: peterk@cbmger.de.so.commodore.com (Dr Peter Kittel Germany)
Organization: Commodore Germany

In article <1992Jul22.151307.1736@sagpd1> monty@sagpd1.UUCP (Monty Saine) writes:
 >>
 >>The autodocs specify the values the function expects/returns, the
 >>prototypes specify what the C-code has to pass to the function.
 >
 >	I am confused???? You are saying that a function expects a UBYTE so the
 >	complier passes an unsigned long???????? and this is correct ?????
 >
 >	What am I overlooking here, do all amiga compliers always pass longs
 >	on the stack???

Yes, this seems to be the fact. On the stack, there are always longs.
If you take a look at the .FD files, you'll find that every parameter
of a function is always passed to one own processor register. So yes,
on the stack these values have always the length of a full register,
and this is 32 bits, a long. How they are interpreted by the real function
is another story.

-- 
Best regards, Dr. Peter Kittel  // E-Mail to \\  Only my personal opinions...
Commodore Frankfurt, Germany  \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk
				   or  peterk@public.sub.org
From: paulk@terapin.com (Paul Kienitz)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Using System() when started from Workbench -- path?
Date: 26 Jul 92 18:28:38 GMT
Article-I.D.: terapin.paulk.0wje
Organization: BBS

> for (wext = BADDR(wbclap->cli_CommandDir); wext; wext = BADDR(*wext)) {
>     if (!(mext = AllocP(2 * sizeof(BPTR))))
>         break;
 
 
oops -- I thought I expanded all the private macros in that snippet
of code for copying a path, but I missed one.  "AllocP(foo)" means
"AllocMem(foo, MEMF_PUBLIC)".
Newsgroups: comp.sys.amiga.programmer
From: jdickson@jato.jpl.nasa.gov (Jeff Dickson)
Subject: Re: Going from volume lock to device name
Organization: Jet Propulsion Laboratory
Date: Tue, 28 Jul 1992 16:50:01 GMT

In article <rfmmkdp.davids@netcom.com> davids@netcom.com (Dave Schreiber) writes:
>Can anyone tell me how to get a device name, given a lock on the volume
>that the device is associated with.  I'm writing a program that takes
>as input locks (to disks) from Workbench, and need to go to the appropriate
>device name ("DF0:", "WB_2.X:", etc). 
>
>I tried doing something like this already:
>
>{
>for(all disk devices in system)
>{
>   lock=Lock(devicename,ACCESS_READ);
>   if(SameLock(lock,volumelock)==LOCK_SAME)
>      unlock lock;
>      return device name
>   else
>      unlock lock;
>}
>
>return error;
>}
>
>But this caused Workbench to become unstable (dragging an icon into a 
>floppy disk's trashcan froze Workbench), even with all the appropriate
>checking of return values, etc.  Could this be a bug in Workbench, or
>am I missing something (Kickstart V37.175, Workbench V37.67)?
>
>Thanks.
>
>
>-- 
>Dave Schreiber/davids@netcom.com (until 9/15/92)/"Ask, don't touch"

Every lock issued by a device contains a pointer to that device's device
node entry. The pointer is stored in the fl_Volume field as a BPTR. Going
to that structure you could extract the device name of the device the lock
belongs via the dl_Name field (BSTR). I believe the relative include file
is libraries/dosextens.h.

It is up to you to exercise arbitration of the DOS list. You're asking for
trouble if you don't. From a process it is best to use the functions
LockDosList(), etc. From a task you have no choice, but to use Forbid/Permit.

Hope this helps.

Jeff
From: podesta@qut.edu.au
Newsgroups: comp.sys.amiga.programmer
Subject: Game Developers, Marketing...?
Date: 28 Jul 92 16:08:10 EST
Organization: Queensland University of Technology

A few questions for all you Developers out there, esp. Game Developers.

A few groups of Aussie lads (Brisbane based) are at different stages in
completing Amiga Games. We are wondering if anyone can give advice on
how to get the game(s) published. Are there any companies that are best
to approach. We have been looking into EA and OssieSoft but they have a
very laid back attitude and don't seem to take much interest in the games
that they agree to publish.

Also, what's the advantages and pre-requisites/costs of registering
as a Developer.

Thanks in advance.
Rincewind.
Newsgroups: comp.sys.amiga.programmer
From: Hans Ridder <ridder@zso.dec.com>
Subject: Re: Hey Commodore types
Originator: ridder@zowie.zso.dec.com
Organization: Digital Equipment Corporation - DECwest Engineering
Date: Thu, 23 Jul 1992 00:27:34 GMT

In article <1992Jul22.151307.1736@sagpd1> monty@sagpd1.UUCP (Monty Saine) writes:
>In article <1992Jul15.114615.25849@mpifr-bonn.mpg.de> mlelstv@specklec.mpifr-bonn.mpg.de (Michael van Elst) writes:
>>
>>The autodocs specify the values the function expects/returns, the
>>prototypes specify what the C-code has to pass to the function.
>
>	I am confused???? You are saying that a function expects a UBYTE
>	so the complier passes an unsigned long???????? and this is
>	correct ?????
>
>	What am I overlooking here, do all amiga compliers always pass
>	longs on the stack???

OK, read carefully.  All Amiga ".library" functions take parameters in
*registers*, not on the stack.  Those parameters are *always* longs.
See any release of the RKM's.

Although the function may (currently) only look at, for example, the low
order byte, you should make sure that the high order bits are set
appropriately (sign extended for signed parameters, zero for unsigned.)

>	This is not a flame, I am truely confused by how both can be
>	'correct' in the above examples.

No problem.  Just think about what would happen if your program calls a
library function which (currently) takes a UWORD for say, a "screen
width."  A newer release of the library comes out which allows screens
that can be wider than a UWORD can hold.  If you (or the compiler)
didn't make sure that the high order word in the register were zero (in
this case,) then your program could crash/bomb/die due to any "garbage"
bits in upper part of that register.  It's a future compatibility thing.

>	Monty Saine

Does that help?

(Note that I don't think C= could ever change any of the parameter sizes
because of all that assembly code out there which isn't carefull about
the high bits.  Oh well.)

-hans
-- 
  Hans-Gabriel Ridder				Digital DECwest Engineering
  ridder@rust.zso.dec.com			Bellevue, Washington, USA
  {pacbell,pyramid,uunet}!rust.zso.dec.com!ridder
From: Irwin_Aschkenas@neonate.amiga.atl.ga.us (Irwin Aschkenas)
Newsgroups: comp.sys.amiga.programmer
Subject: Taglist HELP !!
Date: 30 Jul 92 03:12:29 GMT
Organization: The Village BBS

I am trying to get the REQTOOLS file requester to work and need some help
with
creating a tag list.  I know TAGS are new with the release of 2.0 and I
don't 
have any 2.0 RKMs to reference...  Could someone please provide some sample
code in assembly which creates a taglist that can be passed to the 
rtFileRequestA library routine... I'd like to see how to create a taglist
with the RTFI_Flags...  Thanks...

-- Via DLG Pro v0.992
From: mwm@contessa.palo-alto.ca.us (Mike Meyer)
Subject: Re: Please crash my machine
Newsgroups: comp.sys.amiga.programmer
Distribution: world
X-NewsSoftware: Amiga Yarn 2.0, 1992/06/25 01:41:36
Keywords: 
Summary: 
Date: 22 Jul 92 02:13:22 PST
Organization: Missionaria Phonibalonica

In <paulk.0uci@terapin.com>, paulk@terapin.com (Paul Kienitz) wrote:
> > The answer is clear.  If the software is good, the author will
> > attempt to deal with EVERY possible failure gracefully.
>  
> The question is whether 1.1 is "possible".

The answer is "yes".

	<mike
From: jpr@sun4.lri.fr (Jean-Pierre Riviere)
Newsgroups: comp.sys.amiga.programmer
Subject: Qed, what's happening ?
Date: 23 Jul 92 08:42:04 GMT
Organization: Laboratoire de Recherche en Informatique


In article <33197@cbmvax.commodore.com>, bj@cbmvax.commodore.com (Brian
Jackson - Amiga Networking) writes:
|> In article <14fneaINN75v@darkstar.UCSC.EDU> jonathan@cats.ucsc.edu
|> (Jonathan Cano) writes:
|> >Another excellent option is QED, a shareware editor by Darren M.
|> Greenwald
|> >(who is a programmer at C= ).  QED amazing! 
|> 
|> Highly recommended. It's been my editor of choice for years now.
|> Truly
|> nice. Another thing that should be mentioned is that all the code in
|> QED is
|> 'legal'.  I have yet to have it give me -any- trouble on any revision
|> of
|> the OS that I've had here (and I get many :)).  Solid as a rock.
|> Also, it

Nay!
*every* time I found Qed on a *working* system (mainly on disk based
catalogue), it always
says to me
"unknown command"
eacjh time I try to load, save or even quit the program !
It's my bane!!!
So what ? Can you bring force an explication for that ?
Why should it crash on my machine, when any other editor runs OK ?

BTW, my favorite edior is AZ. neat, small and reasonably powerfull. Lack
of power, though.
But good enough in 80% of the time. :-) (and this  include programming)

|> has an arexx learn mode whereby you can record a series of actions and then
|> QED will write an -arexx script- for you that will repeat the list. Nice. 

I wish Qed could work on my Amiga, from what you say.

|> 
|> >| Jonathan Cano             |     //   _   |
|> >| jonathan@cats.ucsc.edu    | \\ //   (_)  |
|> 
|> Brian
|>        +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +  +
|>        Brian Jackson    Amiga Networking Group, Commodore-Amiga Inc.
|>                         bj@cbmvax.commodore.com
|>      {uunet|rutgers}!cbmvax!bj    or   networking@cbmvax.commodore.com
|>  "Oh, so you have a Borg named Hugh."           Uva uvam vivendo varia fit 

-- 
  Jean-Pierre RIVIERE        |     ///
  LRI - Universite Paris Sud | \\\///
  e-mail : jpr@lri.lri.fr    |  \///
From: umward10@ccu.umanitoba.ca (Derek Ward)
Newsgroups: comp.sys.amiga.programmer
Subject: A Few Questions
Date: 24 Jul 92 00:15:15 GMT
Organization: University of Manitoba, Winnipeg, Canada



  I hope I am not asking too many (elementary) questions here, but I am
just learning C.  Anyhow, I am interested in using the serial port in some
programs, specifically to call out, answer, and for input/output.  (I would
like to eventually come up with a BBS program).

  So how can I do the above?  How do I use the serial.h header file?

  Also, are there any text files around that explains the functions and
header files for the Amiga?  I mean, I only know what the ones from
stdio.h, strings.h, fcntl.h and a couple others do.  And my manual doesn't
explain any other ones than those.

  Please send any help through mail.  Thanks

Derek

-- 
---------------------------------------------------------------------------
umward10@ccu.umanitoba.ca     <=- That's me.
---------------------------------------------------------------------------
From: dvaz@dvtown.UUCP (David Vazquez)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Custom-Bitmapped screen!!!!
Distribution: world
Date: 21 Jul 92 14:51:19 CST
Organization: Not an Organization

In article <1992Jul21.135317.10888@usage.csd.unsw.OZ.AU> jeice@newt.phys.unsw.oz.au (Jose Ma.Goikoetxea) writes:
>
>Lately I have been playing with Intuition and I am currently trying to write
>a program using the Intuition under v1.3. Currently my problem is that I want
>to use my own CustomBitmap as the screen but I have been unsuccesful in doing
>so. What I have done up to now is draw a screen in Low Res and then convert it
>into a RAW format using a program called iffmaster. After loading this into the
>assembler, Oh by the way I have set the screenmode to 2 and screen type to $40
>but after compiling and then trying to run the program it keeps crashing.
>Thru reading some books such as ROM Kernels I have discovered that I have to set up
> a bitmap structure using InitBitmap but before doing that I have to
>AllocRaster.
>Now what I dont understand is how do I use this routine if I have 2 Bitplanes
>therefore I must call AllocRaster twice and it returns the pointer to the
>memory location for each bitplane but then what do I do???????
>

How are you loading it into your assembler (with INCBIN)?  If so you must
so this:

	INCLUDE graphics/gfx.i

; open graphics.library and any others that you'll need.
	:
	lea	bitMap,a0
	move.l	#2,d0			;  Depth
	move.l	#320,d1 		;  Width
	move.l	#200,d2 		;  Height
	move.l	_GfxBase,a6
	jsr	_LVOInitBitMap(a6)

	lea	bitMap,a0
	move.l	#planes,bm_Planes(a0)         ;  first bitplane.
	move.l	#planes+8000,bm_Planes+4(a0)  ;  second bitplane.
	:
;  Set up NewScreen structure with a pointer to bitMap in the CustomBitMap
; field and flags set accordingly then OpenScreen(), etc.
	:
bitMap	ds.b	bm_SIZEOF		;  You can also use AllocMem to
					; allocate this structure.
	:
	SECTION graphic_data,DATA_C
	;  Anything that follows will be placed in chip (graphics) memory.
planes	INCBIN	RawPictureFileName	;  Data representing 2bp screen.

--
============================================================================
     //  Look Ma,	O		 David Vazquez		     \\
    //		       -|-     INTERNET: dvaz%dvtown@cs.tulane.edu    \\
  \X/	   No hands.   / \	 USENET: ...!rex!dvtown!dvaz	       \X/
============================================================================
From: ridgwad@jacobs.CS.ORST.EDU (Dean Ridgway)
Newsgroups: comp.sys.amiga.programmer
Subject: WorkBench 2.04 - bug, or feature?
Summary: bug or feature?
Keywords: AmigaDOS 2.04
Date: 21 Jul 92 08:10:47 GMT
Article-I.D.: leela.1992Jul21.081047.677
Followup-To: comp.sys.amiga.programmer
Organization: Computer Science Outreach Services - Oregon State University

While working on my latest computer club disk (now in a new Workbench 2.04
format) I noticed that when you resize or reposition a drawer's window and
try to save that information back into the .INFO file that only the resizing
information is saved.  The system still opens the window where ever it feels
like it (even on cold boot).  If I want to fix the position that the window
opens at, I have to drop back to 1.3.2, its...IRRITATING!

Does anyone know if this is a bug, or if the INFORMATION pull down menu item
was deliberately rewritten not to save positional information.  I have looked
through the _Using_the_System_Software_ book under the INFORMATION pull down
menu and it does not say you have to do anything different to save the
position of a window.  If this is mentioned anywhere in the System Software
book please give me a page number, or other reference.

If this is a known bug, does anyone know if Commodore knows about it?

My stats: KickStart 37.175, Workbench 37.67 .

Dean Ridgway | FidoNet 1:357/1.103 | InterNet ridgwad@jacobs.cs.orst.edu
	     | CIS 73225,512       |          ridgwad@atlantis.cs.orst.edu
Organization: Penn State University
Date: Mon, 27 Jul 1992 10:19:19 EDT
From: Doug "Bish" Bischoff EMT-MAST <DEB110@psuvm.psu.edu>
Newsgroups: comp.sys.amiga.programmer
Subject: GadTools bugs?

     I've just hopped knee-deep into programming (following a $100 purchase of
a bunch of phone books masquerading as RKM's... ;-) and found this lovely tool
to make interface programming a BREEZE.  What was this marvelous thing?
     GadToolsBox, of course.
     Problem is, it seems to have some big nasty bugs.  For example:

     I create a screen (default, hires interlaced) and open a window on it.
Now I place a text gadget in the window.  Oops, placed it too high.  I want
to use "Move Gadget."  I select it and it says "Click on Gadget to Move."
     Okay, I click on it, and the message stays there.  I keep clicking until
my index finger falls off, trying every pixel of the gadget and its title, and
still "Click on Gadget to Move."  Okay, enough with that, I'll go to something
else.  I click the Right Mouse Button.... and the "Click on Gadget to Move"
goes away and the whole program locks.  Won't do anything.  The menus come up,
but selecting something doesn't work.  I can't even quit 'cept by cancelling
the task, etc.
     Help?

/---------------------------------------------------------------------\
| -Doug  Bischoff- |    *** ***    ====--\         | Krieger's Plains |
| -DEB110 @ PSUVM- |   *  ***  *     ==|<>\___     |      Dwarves     |
| -The Black Ring- |    *** ***        |______\    | "Remember an age |
| --- "Wheels" --- |      ***           O   O      |   When Dwarves   |
| Corwyn Blakwolfe |     T.R.I.     -------------  |    Knew Glory"   |
\---- DEB110@PSUVM.PSU.EDU - AMIGA: there can be only one... ---------/
From: paulk@terapin.com (Paul Kienitz)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Registers from C
Date: 28 Jul 92 02:09:54 GMT
Organization: BBS

> To quote the 2.0 RKM:Includes & Autodocs page 647 NP_Arguments entry:
> 
>       "cstring of arguments - passed with str in a0, length in d0."
> 
> Ok.  So, assuming the function is CreateNewProc()-ing correctly, how
> do I pull these arguments out of the registers from C.  I realize this
> is a probably a very simple thing to do, but I would really appreciate
> help from anyone with some experience.
 
Depends on your particular C compiler.  SAS, Aztec, and DICE all do
this in different ways.  If you are using CreateNewProc to start a
process where the entry point is a function like this:
 
   long Sub_process_main(char *argline, long arglen)
 
Then in Aztec you would put
 
   #pragma regcall(Sub_process_main(a0, d0))
 
before the function.  Or you can use #pragma intfunc with the same
syntax and it will set up the small-data A4 register for you.
 
In SAS it's something vaguely like:
 
   long Sub_process_main(register __a0 char *argline,
                           register __d0 long arglen)
 
but don't quote me on that because I don't use it.
 
As for DICE, I dunno.
From: mks@cbmvax.commodore.com (Michael Sinz)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: StackSwap in all v37 releases?
Date: 24 Jul 92 18:29:10 GMT
Reply-To: mks@cbmvax.commodore.com (Michael Sinz)
Organization: Commodore, West Chester, PA

paulk@terapin.com (Paul Kienitz) writes:
>Since StackSwap -- or is it SwapStack -- is documented in some v37 autodocs and
>not others, does this mean that, in order to use the function, I have to check
>the exec revision number?  Or is it really in all v37s?  What revision number
>is the dividing line at, if there is one?

It is in V37 EXEC.  (Any V37 that was released to the public)

The autodoc should show:

| exec.library/StackSwap                                 exec.library/StackSwap
|
|   NAME
| 	StackSwap - EXEC supported method of replacing task's stack      (V37)
|
|   SYNOPSIS
| 	StackSwap(newStack)
| 	          A0
|
| 	VOID StackSwap(struct StackSwapStruct *);

Note the (V37) in the corner.  This means that as of V37 of the library in
question (in this case, EXEC) this function is available.

/----------------------------------------------------------------------\
|      /// Michael Sinz  -  Senior Amiga Systems Engineer              |
|     ///                   Operating System Development Group         |
|    ///   BIX:  msinz      UUNET:  mks@cbmvax.commodore.com           |
|\\\///                     When people are free to do as they         |
| \XX/                      please, they usually imitate each other.   |
\----------------------------------------------------------------------/
Newsgroups: comp.sys.amiga.programmer
From: mlelstv@specklec.mpifr-bonn.mpg.de (Michael van Elst)
Subject: Re: Developing for CDTV ? and...to CDTV or not to CDTV ???
Organization: Max-Planck-Institut f"ur Radioastronomie
Date: Thu, 30 Jul 1992 18:50:06 GMT

In <1992Jul29.194131.909@ultb.isc.rit.edu> mjp3783@ritvax.isc.rit.edu writes:
>Parnet is exceedingly fast (unless we define fast/slow much differently!)

Iiks ? Fast ? Parnet maxed out at about 35kb/s between an A3000
and an 68020/16MHz A1000 and leaves the slower 68020 machine nearly
unusuable during the transfers.
Is there some magic to get better results ?


-- 
Michael van Elst
UUCP:     universe!local-cluster!milky-way!sol!earth!uunet!unido!mpirbn!p554mve
Internet: p554mve@mpirbn.mpifr-bonn.mpg.de
                                "A potential Snark may lurk in every tree."
From: aru@mentor.cc.purdue.edu (Sri Ramkrishna)
Newsgroups: comp.sys.amiga.programmer
Subject: knowing about protocols and stuff...
Keywords: protocols,packets,networks,network,amiga,unix
Date: 22 Jul 92 22:15:18 GMT
Organization: Purdue University

I'm trying to design a networking program between Unix and Amiga ala
DNet.  My question is what should I be looking for when it comes to
designing a protocol.  I'm trying to get some understanding about
networking, packets and all that good stuff, but I'm rather lost.  I'm
not sure what sort of documents I should look at.  If someone can point
me in the right direction that would be great.  Are their any specific books
that I can buy that will help me out?  Any help would be great.  Once I get
the skeleton worked out, I can start programming it. (heck got nothing else to
do this summer :-)

I haven't tried DNet as of yet, and I have been told that its rather jumpy at
slower bauds.  If you were to put a good cache, wouldn't that solve the problem?
I'm attempting to take a look at Matt Dillon's source (I keep thinking of 
Gunsmoke everytime I hear his name!) and see if it could be modified.  
(NOTE: if I get it working, I am NOT going to be distributing this, copyrights
you know.:)

	sri
From: kholland@hydra.unm.edu (Kiernan Holland)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: WB 2.1
Date: 31 Jul 92 05:43:10 GMT
Organization: University of New Mexico, Albuquerque

How about a good C compiler. What's good?  
I'm taking Intro to "C" (finaly 8-> ) and would like to buy a good 
ANSI-C compiler. Any suggestions?
From: epang@fraser.sfu.ca (Eugene Pang)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: line f trap <- what?
Date: 28 Jul 92 04:53:53 GMT
Distribution: comp
Organization: Simon Fraser University, Burnaby, B.C., Canada

james.kewageshig@canrem.com (james kewageshig) writes:
>after selecting the filename and "LOAD" gadget, my Amiga (with '030) 
>guru's with '00000004' I believe.  According to my guru code program
>this code means "Line F trap error" or some such.

Your guru code program is wrong.  Mine's better...  :-)

>Does anyone know what this is or how it can be rectified??

It's an illegal instruction.  The cause could be a variety of things.  If
this is reproduceable, try running Enforcer (dumping output to the serial
port or printer?) and sending it to the author to fix.  Otherwise, don't
select "LOAD".  :-)