Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!mailrus!ames!pasteur!cory.Berkeley.EDU!koster From: koster@cory.Berkeley.EDU (Herbert West) Newsgroups: comp.sys.amiga Subject: Re: Assembly Blues Message-ID: <4969@pasteur.Berkeley.EDU> Date: 11 Aug 88 19:45:06 GMT References: <3295@crash.cts.com> Sender: news@pasteur.Berkeley.EDU Reply-To: koster@cory.Berkeley.EDU.UUCP (Herbert West) Organization: University of California, Berkeley Lines: 24 In article <3295@crash.cts.com> steelie@pro-charlotte.cts.com (Jim Howard) writes: >Can anyone out there figure out what is wrong with the following >excerpt of code? (besides the obvious sloppy style) > ">screenvars dc.w 0 * ns_LeftEdge "> dc.w 0 * ns_TopEdge "> dc.w 320 * ns_Width "> dc.w 200 * ns_Height "> dc.w 3 * ns_Depth "> dc.b 3 * ns_DetailPen "> dc.b 1 * ns_BlockPen "> dc.w 0 * ns_ViewModes "> dc.w WBENCHSCREEN * ns_Type "> dc.l 0 * ns_Font "> dc.l 0 * ns_DefaultTitle "> dc.l 0 * ns_Gadgets "> dc.l 0 * ns_CustomBitMap My guess would be you want COSTOMSCREEN instead of WBENCHSCREEN. Usually with intuition, the machine bombs when things aren't just exactly right. Try single stepping the program with your debugger, and see if it is the OpenScreen that does it.