Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!think.com!rpi!usc!elroy.jpl.nasa.gov!ncar!gatech!psuvax1!rutgers!cbmvax!mks From: mks@cbmvax.commodore.com (Michael Sinz) Newsgroups: comp.sys.amiga.programmer Subject: Re: "Busy" pointer Message-ID: <22730@cbmvax.commodore.com> Date: 27 Jun 91 14:15:41 GMT References: <1991Jun26.030833.9974@crash.cts.com> <3846@sirius.ucs.adelaide.edu.au> Reply-To: mks@cbmvax.commodore.com (Michael Sinz) Organization: Commodore, West Chester, PA Lines: 40 In article <3846@sirius.ucs.adelaide.edu.au> jpotter@ucs.adelaide.edu.au (Jonathan Potter) writes: >In article <1991Jun26.030833.9974@crash.cts.com> bruceg@crash.cts.com (Bruce Geerdes) writes: >>What's the easiest way to get the "busy" pointer to come up? The RKM's >>show one how to define his own alternate pointer, but I'd like to use the >>standard one. I'm assuming it's someone in ROM? > >I understand the busy pointer is stored in the info.library. But how to get >it to appear I can't tell you. No, it is in workbench.library currently and you can not get at it. However, here is the current image: static USHORT WaitPointer[] = { 0x0000, 0x0000, /* vert. and horiz. start posn. */ 0x0400, 0x07C0, 0x0000, 0x07C0, 0x0100, 0x0380, 0x0000, 0x07E0, 0x07C0, 0x1FF8, 0x1FF0, 0x3FEC, 0x3FF8, 0x7FDE, 0x3FF8, 0x7FBE, 0x7FFC, 0xFF7F, 0x7EFC, 0xFFFF, 0x7FFC, 0xFFFF, 0x3FF8, 0x7FFE, 0x3FF8, 0x7FFE, 0x1FF0, 0x3FFC, 0x07C0, 0x1FF8, 0x0000, 0x07E0, 0x0000, 0x0000, /* reserved, must be NULL */ }; /----------------------------------------------------------------------\ | /// Michael Sinz - Amiga Software Engineer | | /// Operating System Development Group | | /// BIX: msinz UUNET: rutgers!cbmvax!mks | |\\\/// When people are free to do as they | | \XX/ please, they usually imitate each other. | \----------------------------------------------------------------------/