Fetch Softworks

Fetch suddenly quits on startup OS X .04 (5 posts)

• Started 21 years ago by jim
• Latest reply 21 years ago from AlVal

• jim Member

  Fetch has been running fine. All of a sudden it quits "with unexpected error" during launch.

  I have: dumped all Fetch preferences except the file which stores my accounts; searched for "(null).plist" (did not exist); re-installed Fetch.

  So far nothing has helped. I used another program to upload a project I *had* to.

  Thanks in advance.

  James

  Posted 21 years ago #

• Jim Matthews Administrator

  That's a new one for me -- every other quit-at-launch problem that I've come across has been fixed by removing (null).plist.

  One thing to try: create a new account on your Mac (using UserManager), and try running Fetch while logged into that account.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 21 years ago #

• jim Member

  Originally posted by JimMatthews:

  That's a new one for me -- every other quit-at-launch problem that I've come across has been fixed by removing (null).plist.

  One thing to try: create a new account on your Mac (using UserManager), and try running Fetch while logged into that account.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Hi and thanks for the fast response! It is much appreciated. I followed your suggestion and yes it worked. :-(

  I knew the only thing I added to the Mac (and then had Fetch problems) was TurboMem. It is program that scrubs RAM. Making more available. This time I logged in as usual but * did not * launch TurbMem at all. Fetch works.

  Here is the URL for TurboMem <http://www.macunicorn.com/turbomem/index.htm> I read some reader reviews while at Version Tracker . . . I think I'll remove it from the Mac.

  Again, thanks.

  James M. Gross

  Posted 21 years ago #

• Jim Matthews Administrator

  Thanks for the followup. I don't know offhand why TurboMem would break Fetch, but anything that works at such a low level is going to pose a risk to compatibility.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 21 years ago #

• AlVal Member

  I acquired the same problem after I installed a whole bunch of docklets. Deleting (null).plist fixed the problem. :-)

  Posted 21 years ago #