Subject: Re: : Re: LIB$INITIALIZE image_info record layout Date: Sun, 20 Jan 2002 23:07:21 GMT From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) Organization: TMESIS Software Newsgroups: comp.os.vms In article , "Richard Maher" writes: >Hi, > >Thanks to the replies for an other note (Mark London and Brian >Schenkenberger) I've been able to map the first 288 bytes of image-info but >am having trouble finding a macro that deciphers the list of activated >images that is lurking in the remaining bytes. To the best of my knowledge >my initialization routine receives the $EIHDDEF data that points to all the >interesting stuff at EIHD$L_IMGIDOFF that maps according to to $EIHIDEF. But >where I would expect a mapping of $EISDDEF at EIHD$_ISDOFF I'm getting what >appears to be a header followed by a list off images that have been >activated upto and including the image that my initialization routine is >responsible for. (If the image was run from DCL you get the current image >followed by loginout.exe. If the image was run detached tehn loginout is >leftout. I'm sure if my image was a shareable then it would be my image >plus and preceeding shareables plus the main image and finally >loginout.exe.) > >Does this construct ring a bell with anyone? > >The confusing bit is that most macros limit image name to 40 bytes and these >counted ASCII strings exceed 40 bytes. Brian mention IAC$GL_IMAGE_LIST queue >is there a macro for this? Linked list? Is this what I'm seeing? IAC$GL_IMAGE_LIST points to a queue (double linked list) of I(M)CB data structures (They are called ICBs on VAX, IMCBs on Alpha). I(M)CB$L_IHD should point to an image header you can decipher. You'll need to be in exec mode to access a lot of this. -- VAXman- OpenVMS APE certification number: AAA-0001 VAXman(at)TMESIS(dot)COM "And of course, I'm a genius, so people are naturally drawn to my fiery intellect. Their admiration overwhelms their envy!" -- Calvin & Hobbes