Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ukma!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Alert problems
Message-ID: <2009@husc6.harvard.edu>
Date: 6 Jun 89 12:30:47 GMT
References: <18282@unix.cis.pittsburgh.edu>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Distribution: usa
Organization: Symantec/THINK Technologies, Bedford, MA
Lines: 38

In article <18282@unix.cis.pittsburgh.edu> adams3@unix.cis.pittsburgh.edu (Larry Adams) writes:

>them).  i used to pass NIL as the wStorage value, but kept getting the 
>THINK pascal error "Address Error".  when i used a variable to store the
>windows (actually, an array of three elements, i.e., @wStore[i] ), my
>problem went away.

	If you pass a pointer to NewWindow,  GetNewWindow,  NewDialog, or
GetNewDialog, it has to be a pointer to NON-relocatable storage. The
address of an element in a handled array is not such storage.

	If you're using StopAlert, be sure that the resource ID you're
passing is the ID of a real ALRT resource in your project's resource
file, and the the alert has a properly set up item list.

	Beyond that,  it's really hard to diagnose your problems without
seeing some of the code you wrote.

>my question is, why, when i have ~20 K free memory (as reported by
>MemAvail), would i get an address error?  have i done anything
>seriously wrong, or overlooked something that should be obvious?

	Address errors have nothing to do with allocation; an address
exception is raised by the 68000 when a word or longword fetch or store
is attempted from a numerically odd memory address.

		--Rich

~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

 "She told me to make myself comfortable, so I pulled down my pants
 and sat in the pudding." -Emo Phillips
~~~~~~~~~~~~~~~