🚀 go-pugleaf

I know I'm treading in unfamiliar ground, but I figure if anyone knows the   
straight dope, it will be the comp.sys.next folks. So here goes:

The other day I was hooking up a small Macintosh network at a client site,
with plans to connect it to the company's larger NeXT network (ethernet over
UTP). We had planned to use one of the Macs as a personal file server for
the other Macs and one NeXT (running NeXTStep 3.0, which I thought could 
act as an AppleShare client) to work with WordPerfect files.

The big moment comes, and the IS guy -- a NeXT devotee to the point of, well,
obnoxiousness -- announces we can't hook into his NeXT network. He'd had
reservations before about this (something about the Macs screwing up *his*
NeXT network) but I thought everything was cool, that there wouldn't be 
any problem.

Anyway, he announces that there's a huge bug in 3.0 that, when files are
being copied between a NeXT client and an AppleShare server, the NeXT hangs,
crashes, bombs out, whatever. He said he had just called NeXT, and they were
going to release a patch "sometime next month" to fix it.

My initial (unvoiced) reaction was: If NeXT was going to bother with putting
in the necessary AppleTalk stuff to make the client setup possible, you'd 
think they'd test something as simple as a file copy on it. So, does anyone
know anything about this? Is it a load of bunk, or has their been problems in
this area?

Any and all help is appreciated, and, if you're doing something like this,
please let me know!

Dave Manning
Mac Guy and NeXT Fan

--
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::  "No. 2's got me confused,				Dave Manning	     ::
::    hope to be Nos. 1 and 3..."		dmanning@cwis.unomaha.edu    ::
:::::::::::::::::--Mercury Rev:::::::::::::::::::::::::::::::::::::::::::::::::