Xref: utzoo comp.sys.novell:1157 comp.sys.mac.system:4363 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!hsdndev!dartvax!eleazar.dartmouth.edu!rsvp From: rsvp@eleazar.dartmouth.edu (R. Scott V. Paterson) 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: <1991Apr15.164422.9731@dartvax.dartmouth.edu> Date: 15 Apr 91 16:44:22 GMT References: Sender: news@dartvax.dartmouth.edu (The News Manager) Organization: Dartmouth College, Hanover, NH Lines: 64 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. >This is bologna. Netware 3.0 just recently went out. Novell has had >System 7 in beta form since at least October. They should have seen >the problem A LONG TIME AGO. It would have been a simple fix to resolve >the problem before 3.0 went out the door. I guess it is just easier for >them to try to reflect the problem back on Apple. Now, as far as volume IDs, >Apple published recommended methods for obtaining a new volume id to >mount a volume with. The notes described a method for searching the volume >table for free entries. None of the notes showed the use of volume 0, they >all started counting at -1, going down (the index into the volume table >is the 2s complement of this number; thus volume -1 has an index of 0). Sorry Jack; it's not bologna. This is indeed Apple's bug: that's why _they_ fixed it, not us. Apple knows it's their bug, and they are not complaining to us. The bug was not in 6.0.x (I don't know which versions of 7.0 had it or not, except as noted), was in 7.0b4, and was fixed in 7.0b5. Believe me, it's not like we're twisting Apple's arm to get them to change their specs; when we noticed this problem and called Apple about it they told us that they had already noticed it and fixed it in b5. >Flame on> >It is disgusting for developers to receive all kinds of information from >Apple on what they should and shouldn't do (I've seen the info - I get it >too!), then go off and invent their own way, ignoring Apple's info, then try >to blame the resulting mess on Apple. Maybe they are just used to getting >away with it in the DOS world. >Flame off> >Jack Brindle We aren't inventing our own way; 0 is a perfectly valid volume id. You are right that we should have seen the bug early and got Apple to fix it before 7.0b4. For that matter Apple should not have put the bug in, and having put it in should have fixed it before 7.0b4. That's what bugs are; things that don't work right. That's one of the reasons that 7.0 is in beta -- they haven't fixed all of the bugs. You're right again; we do receive tons of information about what we should and shouldn't do. Much of it is correct (like saying that 0 is a valid volume id). Some things slip through the cracks. Lighten up a little, ok? Incidentally, while we may be used to many things in the DOS world, blaming Apple for stuff is not one I'd be likely to place at the top of the list. /markw