Xref: utzoo comp.sys.mac.programmer:18119 comp.protocols.appletalk:4454 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!apple!claris!ClarisII!clay From: clay@iti.org (Clay A. Maeckel) Newsgroups: comp.sys.mac.programmer,comp.protocols.appletalk Subject: Re: picking node in server range when opening .MPP Keywords: server,.MPP,opening,appletalk Message-ID: Date: 9 Oct 90 20:22:33 GMT References: <3168@bruce.cs.monash.OZ.AU> Sender: news@claris.com Followup-To: comp.sys.mac.programmer Lines: 25 younger@bruce.cs.monash.OZ.AU (Chris Younger) writes: >While reading Inside Mac vol V page 515 I noticed that I should pick a node >in the server range when opening the .MPP driver for a node that will be >acting as a server. I wouldn't worry about picking a node number in the server range if you are writing code for a Mac. From what I understand the server range was really set aside just for LaserWriters because of the relatively long times they don't listen to the network for "Is this node number in use?" packets (or any other). When you are dealing with an Ethernet or Token Ring networks the server range is not supported in the AppleTalk drivers. > result = OpenDriver("\p.MPP",&refnum); I would recommend going back to using MPPOpen instead of the OpenDriver call. If you have a IIfx using LocalTalk and AppleTalk is turned off in the Chooser, the the OpenDriver call will crash the machine. Also their seems to be some problems with the IIcx and IIci, System 6.0.6, and OpenDriver method of starting AppleTalk. If AppleTalk is turned off, calling OpenDriver or PBOpen will turn it back on instead of return the error that MPPOpen does. -- Clay Maeckel * UUCP: {ames,apple,portal,sun,voder}!claris!clay (I know nothing!) * Internet: clay@claris.com * GEnie: C.MAECKEL Claris Corporation * AppleLink: Maeckel1 * CompuServe: 73057,255