Xref: utzoo comp.windows.ms.programmer:2029 comp.sys.novell:1273
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uunet!odi!ed
From: ed@odi.com (Ed Schwalenberg)
Newsgroups: comp.windows.ms.programmer,comp.sys.novell
Subject: Re: Installing Windows in a net - a solution
Message-ID: <1991Apr23.172611.8891@odi.com>
Date: 23 Apr 91 17:26:11 GMT
References: <91100.194201MUHRTH@DB0TUI11.BITNET> <1991Apr18.011233.22446@npd.Novell.COM>
Organization: Object Design, Inc.
Lines: 26
In-Reply-To: jlamb@npd.Novell.COM's message of 18 Apr 91 01:12:33 GMT


  From: jlamb@npd.Novell.COM (Jason "Nematode" Lamb)
  Date: 18 Apr 91 01:12:33 GMT

  Novell publishes NetWare Application Notes which cover System 
  Administration type stuff on a variety of subjects. These Application Notes
  are published monthly and are available from Novell for 5.00 US (10.00 
  International) for the reprints, and for 50.00 US (100.00 International) for a
  years subscription. You can order these by calling 1-800-UPDATE1.

  In the January 1991 issue I wrote an Application Note entitled NetWare and 
  Microsoft Windows Integration and it covers most current issues (including
  most of what you outlined) regarding this subject.

I'm looking for the answer(s) to a slightly different problem: writing
network applications for Windows.  Our application (an object-oriented
database) has several processes on the "client" host, and several processes
on the "server" host, which must talk to each other.  On Unix systems we
use the "socket" facilities.  We have the NetWare 3.11 20-user kit promoted
by your developer program, but I'm still not sure what we need to write
Windows apps that use NetWare services.  Any help you can provide would be
most appreciated.

PS. I'm posting rather than mailing because I think this topic is of general
interest, and because mail to a variety of permutations of your network
address failed.