Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!microsoft!beng
From: beng@microsoft.UUCP (Ben Goetter (beng, 1/2154, x68609))
Newsgroups: comp.dcom.lans
Subject: Re: LAN Manager APIs & Windows
Summary: Need LM 2.0 or later
Message-ID: <60327@microsoft.UUCP>
Date: 7 Jan 91 22:45:27 GMT
References: <163rwmira01@ULKYVX.bitnet> <924@pdxgate.UUCP> <60101@microsoft.UUCP> <3441@gazette.bcm.tmc.edu>
Reply-To: beng@microsoft.UUCP (Ben Goetter (beng, 1/2154, x68609))
Organization: MS Sys, Network Development, UI
Lines: 29

In article <3441@gazette.bcm.tmc.edu> bsteiner@bcm.tmc.edu writes:
| 
| Although the details are sketchy it seems someone is trying to use
| Lanman's API in a Windows environment.
| 
| Q: Can the .LIB or .DLL libraries supplied with Lanman 1.1 be used
| under a Windows environment?
| 
| I've tried using the NetWkstaSetUID function and Windows responds with
| a message indicating that the application in not a Windows nor DOS
| application. Whats up?

While I'm not familiar with the particular libs you're using, it sure
sounds like you're trying to link to an OS/2 DLL.  Unless 3Com did some
value-add there, the answer under 1.1 is No, those libs and dlls cannot
be used under Win; those dlls are for OS/2 only, while those libs are
either OS/2 import libs or else pure DOS libs incompatible with Win.

| 
| The libraries are those supplied with 3COM's 3+OPEN.
| Windows version is 3.0.
| Compiling with MSC 6.0.

Lanman 1.1 predates Win 3.0.  In order to write a Windows app which calls
the Lanman APIs, you need to be using Lanman 2.0 or later.  Lanman 2.0
includes proper Win DLL versions of its APIs.

Ben Goetter
microsoft!beng