Xref: utzoo comp.sys.novell:1162 comp.sys.mac.system:4386 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mdisea!jackb From: jackb@MDI.COM (Jack Brindle) Newsgroups: comp.sys.novell,comp.sys.mac.system Subject: Re: System 7.0 for the Mac and Novell Netware... Keywords: Mac Novell System 7 Message-ID: <1991Apr16.000710.28381@MDI.COM> Date: 16 Apr 91 00:07:10 GMT References: <1991Apr15.164422.9731@dartvax.dartmouth.edu> Sender: news@MDI.COM Organization: Motorola, Mobile Data Division - Seattle, WA Lines: 43 In article <1991Apr15.164422.9731@dartvax.dartmouth.edu> rsvp@eleazar.dartmouth.edu (R. Scott V. Paterson) writes: >From Comp.sys.Novell > >iIn <1991Apr12.203756.3939@MDI.COM> jackb@MDI.COM (Jack Brindle) writes: > >>In article <1991Apr11.195758.26515@novell.com> brianb@wc.novell.com (Brian >Bulk >owski) writes: >>>The same problem exists with NetWare for Mac 3.0 ... It is *APPLE'S >PROBLEM* >>>... It has to do with the number of volumes, system 7 won't >>>accept a volume ID of 0, which is what we return for the SYS volume. > ... stuff removed... For those reading this thread, Brian, Mark and I have exchanged messages on the topic. Brian's original posting mentioned a volume id. There are actually two volume ids being processed here. One is on the local macintosh, where the id ranges from -1 downward and references each mounted volume. This is the one I was referring to. The second, which Brian referred to, is that of the Appleshare volume, handled by Appleshare. This volume can have a range from 0 to 65536 (I believe). The AFP volume is mapped to a local volume through the Appleshare client code running in the local Mac. The reason for my original response was a reaction to a perceived attack on Apple (the here we go again syndrome...). The information, as I saw it was incorrect, or at least needed additional explanation as to which volume refnum they were talking about. My Flame addressed this reaction (which we, unfortunately, see all too often). My apologies to Brian, Mark and Novell for giving them heat when they were actually doing a good job, working with Apple to correct a problem. This shows that Apple listens, and responds, to problems that developers come up with (I've seen it with my own work also). And, that developers listen to customer complaints, suggestions and pats on the back. I would suggest that we all (Brian and myself included) be more specific on what we post so that confusions of this sort do not happen. Again, we were both correct, just talking about different things. Go for it, Brian! - Jack Brindle ham radio: wa4fib/7