🚀 go-pugleaf

In article <3oqsdm$pag@wendy.ibmpcug.co.uk>,
   lms@soton.ac.uk (Leslie Styles) wrote:
>I am having a problem with the Get Bindery Object ID function in
>the Netware SDK (vol 3) Client API for Assembly. First problem is
>that it doesn't list the Destination ID or the Destination Function
>(in fact, this is missing from many of the calls). I got them from
>the example code (20h and 0006h), but my program still doesn't work.
>I then tried pulling out and running the example code (with changes
>for my user id and server name), and still nothing.

I don't follow what you mean by "Destination ID or the Destination Function". 
Do you mean the connection number?  Are you using the VLM interface?  From 
the Vol 3 SDK Programmer's Guide for Assembly:

"The Client API for Assembly documents Netx-style functions. These functions 
are invoked through interrupt 21h. Avoid using Netx functions unless you need 
to operate in a local environment that for some reason has not upgraded to 
the Requester. Currently, the Requester will support applications that use 
Netx functions (through  netx.vlm), but there is no guarantee how long such 
support will continue."

Basically they want you to move to the VLM API, I think.  When I was looking 
at it, I have found the assembly documentation for the VLM interface to be 
very obtuse.  And I suppose if I were still working with it, I'd understand 
your question right off!

Sorry if I've accidentally gone off on a tangent :)

Paul