-=> Quoting Jeff Dunlop to All <=-
 JD> R. Brown's Interrupt listing shows two ways of getting information
 JD> from Netware: int 21h, ah=E3 and int21h, ah=F2. E3 is labelled
 JD> compatible with versions 4.0 and up, and F2 is labelled compatible
 JD> with 3.0 and up.
 JD> Running a 3.12 server with an ODI client using both Netx and VLM, I've
 JD> found that both the 3.0 and 4.0 API calls get the correct login
 JD> information. Is this because ODI is in essence a 4.x client that is
 JD> backwards compatible with 3.x servers? Is a 3.x client really the old
 JD> ipx+netx combination?
Some of those calls are truly ancient. So ancient that the v4.0 they
refer to is actually OLDER than the version 3.0 they refer to! It's NOT
the modern day v4.0.
I started with Advanced Netware v2.0a, so it's all before my time, but I
believe before that came Advanced Netware v1, and before that was
(non-advanced) Netware v4.0.
I know this because I have a really old SDK, which came out with v2.0a.
It predates v3.0, let alone modern day 4.0, yet it refers all the way
through to v4.0.
Beware especially of old calls for printer status, etc. I haven't looked
at the interrupt list for ages now - I ended up buying the latest SDK.
At that time there were things the new SDK could do that could not be
done with the interrupt list.
---
---------------