🚀 go-pugleaf

In article <3psrtb$ppo_001@ip-pdx3-21.teleport.com>, paulha@teleport.com (Paul Hanchett) says:
>
>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". 

From the Programmer's Guide for Assembly:-

@CallRequester MACRO caller_id, dest_id, dest_func
push bp
mov  bp, caller_id
push bp
mov  bp, dest_id
push bp
mov  bp, dest_func
push bp
call dword ptr _Requester
pop  bp
endm

It appears that destination ID and Destination Function are rather
necessary things. They just don't seem to be listed very often.


>Do you mean the connection number?

No

>Are you using the VLM interface?  

Trying to.

>From the Vol 3 SDK Programmer's Guide for Assembly:
>
>"The Client API for Assembly documents Netx-style functions.

It does say that, doesn't it. It's lying. They aren't there. I rang
Novell. They agreed the stuff wasn't there. It took me several weeks 
to get the info (one page) from them.


>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.

Yep.

>  When I was looking 
>at it, I have found the assembly documentation for the VLM interface to be 
>very obtuse.

Yep.

>  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

The information that is missing from the manual is 6 (SIX) lines long,
and tells you how to make it all work with NETX.EXE or VLMs.

In case anybody else is interested, this is it:-

AH = F2h
AL = Function
CX = Length of request buffer (in bytes)
DX = Length of reply buffer (in bytes)
DS:SI -> request buffer
ES:DS -> reply buffer

The request and reply buffers are the same as documented for the
Requester, and once the above is set, call Int 21h. No fragments to
mess around with either. Why anyone would want to split a twenty byte
buffer into five bits is beyond me.

If anybody else is even vaguely interested in this, I hope it's of use.


Leslie Styles

lms@soton.ac.uk