[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AppleShare (was: Another ZipGSX Mod Success!)

Scott Alfter wrote:

In article <BPadnfjOToPjQZfanZ2dnUVZ_rWtnZ2d@giganews.com>,
Steven Hirsch  <snhirsch@gmail.com> wrote:
I'm trying to zero in on the problem. If I slow the ZipGS down to 50% (of 12.5 MHz.) it stays connected all day. The Zip manual does mention the requirement for setting 87% speed on an 8MHz ZipGS when using Appletalk so that's roughly equivalent. I think there are some critical timing loops buried in the client code. 

Oh?  I have an 8-MHz ZipGS (with 64K cache) connected to netatalk on one of
my Linux boxen through a GatorBox CS.  I keep it running at maximum speed
except when I need to knock it all the way back to 1 MHz for whatever
purpose, and the only time I get disconnected from the server is when I hit
Ctrl-Reset while running at 1 MHz.  As near as I can tell, it'll stay
connected all day while running at 8 MHz.

I am using the "LinuxShare" NDA to connect to the server, as there's some
case-sensitivity issue (IIRC) that keeps the AppleShare NDA from talking to
netatalk.  Maybe netatalk can be patched to work with the AppleShare NDA; I
think I had a patched netatalk working with it a few years ago.  (At this
point, it's nice to just be able to "emerge netatalk" and not have to screw
with things too much on the server side. :-) )
Where did you get the "LinuxShare" NDA? Is that something Marsha Jackson did? I don't think I needed to do anything special on the client end to get it talking with netatalk. That said, Ubuntu (and perhaps others) are distributing a new netatalk version that present some issues for A2 connectivity. I uploaded a patch and some complete debs to the "usual place" (e-mail privately for specifics). From memory, they default to not building 'randnum' auth support. Also, somewhere along the line they made a change that breaks propagation of A2 file timestamps. Everything copied in either direction gets the current time. You may be able to work around the first one with a new connection NDA, but the second one definitely requires a patch (one-liner, I believe) to afpd. 


Since the GatorBox is supposed to be able to translate from NFS to AFP, I
might give that a shot next...but that's starting to drift off-topic.


I didn't realize that!  Let us know how that goes?