jesup@cbmvax.commodore.com (Randell Jesup) (10/10/90)
In article <1990Oct8.211635.22205@jato.jpl.nasa.gov> jdickson@jato.Jpl.Nasa.Gov (Jeff Dickson) writes: >Newsgroups: comp.sys.amiga.tech >Subject: MOUNT Jeff - your news software (or your use of it) is causing problems. This ended up in comp.sys.amiga.hardware, with the wrong title, and the header was followed by what you wanted the header to be. Check with your news administrator. > Anyhow, it is talked about a message is sent to the handler. This >message contains the base of the Device list, the startup text stuff, >etc. What is the format of this message? And I suppose if a message is >sent to the handler on startup that means that a message port has already >been created. How does the handler learn of this port ? It contains a pointer to the DeviceList node for your device, the contents of the dl_Startup field, and the string that caused this access. dp_Arg1 has the name (BSTR), dp_Arg2 has the dl_Startup value, and dp_Arg3 has a BPTR to the DeviceList node for your handler. Return with dp_Res1 = -1 if you succeeded, or 0 (and reason in dp_Res2). If your handler wants all future refernces to go to this process, set dl_Task to be an APTR to your process messageport. I would be wary of considering yourself almost done if you don't know these things yet. Handlers are subtle and will bite you in ways you don't anticipate. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com BIX: rjesup Common phrase heard at Amiga Devcon '89: "It's in there!"