🚀 go-pugleaf

In article <13641@ucbvax.BERKELEY.EDU>, mazlack@ernie.Berkeley.EDU (Lawrence J. Mazlack) writes:
> In response to the MacServe query:
> When I started to get weird failures, I took it off of my system.
> The failures stopped - so I am not motivated to put it back on.
> 
> Larry Mazlack
> mazlack@ernie.berkeley.edu
I've been using MacServe now for about a week and a half, and I, too, have 
noticed an unusual number of bombs/crashes.  While some of this is undoubtedly
related to my testing of public-domain software on my Lisa, some of the other
programs I used to use quite often (Red Ryder, ResEdit, QUED) have crashed 
spectacularly (the usual result is that the Lisa reboots and gives a 'CPU 
error ID=40, which I've never seen before).  I've also had a couple of 
other problems, such as 'Out of Memory' crashes (this is on a 1 meg machine
not using Switcher or Keeper or the MacServe cache, mind you!) and a few
failures of MacServe to load (once, it reset the configuration and wouldn't
let me boot off the hard disk because it couldn't find a nonexistant printer
connected to the parallel (hard disk) port).  I'm running MacServe as a stand
alone (until I get a new Mac) on the Lisa, and I find that when it works, 
it works well (it fixes the hard disk trashing bug of MacWorks, it allows
you to partition the Lisa hard disk, it adjusts the sector allocation so that
files don't take up 4K chunks, and it has a backup program).  However, I'm
wondering if the problems outweigh the benefits.  Don't get me wrong, I like
MacServe when it works, it's just that it's not very robust (is ANY Mac
application very robust?).  I'd appreciate hearing anyone else's comments on it.

Robert J. Hammen     {seismo,allegra,ihnp4,harvard,topaz}!uwvax!puff!hammen
UW-Madison CS Dept.   hammen@puff.wisc.edu
UW-Madison Plasma Physics Dept.     plasma%wiscpsl.bitnet {@wiscvm.wisc.edu}
---
Working here is like being in a nightmare.  You'd like to get out of it, but
you need the sleep.