Xref: utzoo comp.sys.mac.apps:4361 comp.sys.mac.misc:9083
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!hsdndev!husc6!endor!siegel
From: siegel@endor.uucp (Rich Siegel)
Newsgroups: comp.sys.mac.apps,comp.sys.mac.misc
Subject: Really Annoying AppleShare Crashes
Message-ID: <5866@husc6.harvard.edu>
Date: 4 Mar 91 14:22:26 GMT
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 60


For a long time, I've been having an extremely annoying problem with our 
inhouse AppleShare server. I've tried a variety of remedies, but nothing
helps.

The System:

	Mac IIcx
	System 6.0.5
	EtherTalk 1.2, installed by the Asante Ethernet installer 2.0.6
	8MB RAM
	600MB external hard disk, formatted and partitioned with
		SilverLining 5.26
	AppleShare 2.0.1
	Apple CD-ROM software 3.0.1

The Symptoms:
	
	Every morning (but never when I'm around), the server crashes.
	Before I installed TMON, the crash would be in the form of a
	System Error 02, System Error 29, or just a system freeze.
	Sometimes when the system crashes, one or more of the mounted
	partitions gets damaged, probably because of AppleShare's
	insistence on turning up the Apple RAM cache to a ridiculously
	high value.

	TMON, when installed, reports an Address Error when trying to 
	RTS from what looks like a _RecoverHandle patch in the system
	heap. The last routine which appears in an A6 stack crawl is
	called "DRAWSTAT". (How nice of Apple to provide Macsbug names
	in finished software, so that we can debug it! :-))

What I've Tried:

	Installing a new system from both the original AppleShare
	distribution and virgin system floppies; I've tried versions
	6.0.3, 6.0.4, and 6.0.5. None makes a difference. Along with
	this I've tried reinstalling the AppleShare software from the
	original floppies. No dice.

	I've tried running without the CD-ROM mounted. No dice.

	I've tried installing more RAM, increasing the installed memory
	from 5MB to 8MB makes no difference.

	I've tried installing a little INIT to grow the system heap
	at startup time. No difference. When the server crashes, there's
	plenty of space in the system heap.

I'm at the end of my rope on this one. This is a production server, which
is the mainstay of our office network, and to have it crash as often as 
it does is unacceptable. If anyone has any idea as to what's going on,
and how to correct it, please mail me or post to comp.sys.mac.apps
or comp.sys.mac.misc. Not only will I be eternally grateful, I'll also
send you some goodies. :-)

R.
 Rich Siegel	Symantec Languages Group  Internet: siegel@endor.harvard.edu

"I was just trying to be subtle. That's my job, isn't it?"