paul@actrix.gen.nz (Paul Gillingwater) (12/08/90)
In article <OTTO.90Dec6085306@tukki.jyu.fi> otto@tukki.jyu.fi (Otto J. Makela) writes: > We've recently been experimenting with 3COM +Open network (LAN Manager based). First I'll have to say that my experience has only been with Hewlett-Packards version of this software, which is clearly an OEM version of the 3COM stuff (since it has 3OPEN all thru it), but has additional HP-only functionality, such as LM/X for HP-UX and SCO UNIX. > I'm not too keen on it, since it requires a dedicated server machine (running > OS/2), uses NetBIOS etc. but I must admit that the network interface is small Nope. The HP version will work with servers on OS/2, HP-UX and SCO UNIX. All three use TCP/IP as the transport, with NetBIOS as an option. > Does anyone have ideas/ > experience on running it simultaneously with TCP/IP stuff like NCSA Telnet. Works just fine. But you don't need the NCSA stuff, since the HP LM product comes with HP ARPA 2.0, which includes Telnet, FTP, rsh etc. The Telnet uses Kermit, but will work with other terminal emulators as well that support BAPI. It does work OK with NCSA stuff on the same LAN. > from the the-world's-an-ibm-pc-running-netbios syndrome. I've ended up with > two ethernet cards on my machine, one for NetBIOS and one for TCP/IP :-( Well, you can get rid of one of those. Note that you don't have to buy any HP hardware -- if you can persuade the local HP office to sell it to you! That seems to be the biggest problem, in that HP aren't promoting it very well, especially the fact that they have a version for SCO UNIX, with TCP/IP. > Can anyone tell me what difference does it make if I tell Windows3 about the > 3COM network being installed, or not ? The people who loaned us the 3COM demo HP report that their next release (LM 2.0 and ARPA 2.1) will have fixes for the bugs introduced by Windows 3.0. Note also that you can mix 3OPEN stuff and HP stuff quite happily. > machine told me that their own specialists had told that's it better NOT to > tell Windows about it (seemed there was some kind of problems). There are also problems with most expanded memory managers in coping with both LANs and Windows in enhanced mode, e.g. 386MAX and QEMM386. -- Paul Gillingwater, paul@actrix.gen.nz