Fetch Softworks

The Application Fetch 4.0 has unexpectedly quit... (13 posts)

• Started 22 years ago by DaRatBoyz
• Latest reply 22 years ago from jims

• DaRatBoyz Member

  PowerBook G3 466 Wallstreet 384 megs of ram.
  Mac OS X 10.0.3
  Fetch 4.0 quits upon launch with the above message just after the shortcut window appears. Deleting all files and reinstalling has no effect.
  Fetch runs fine in OS 9.1.

  Suggestions?

  Posted 22 years ago #

• DaRatBoyz Member

  I should also add that the first crash of Fetch in OS X came at the end of the purchase license after first install. Now it crashes on all subsequent launches in OS X.
  I am sure there is some file I need to delete or tweek, but I'm damned if I can find it.

  Posted 22 years ago #

• Jim Matthews Administrator

  A couple things to try:

  1) Delete the Fetch Prefs, Fetch Cache and Fetch Shortcuts files. They should be in the Library/Preferences folder in your home directory.

  2) Hold down Control and Option while Fetch launches; this causes it to ignore any saved registration information.

  Let me know if neither of these works.

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #

• DaRatBoyz Member

  Tried 1 already with no change.
  So I did 1 and 2 simultaniously, got the screen about it being a trial version. But if I tried to enter my registration number or if I tried to go as a trial version the app immediately quits with the same message.
  I hope we can get this resolved. I have used Fetch for years and would like to continue to do so in OS X.
  It's a sweet little FTP client.

  Posted 22 years ago #

• Jim Matthews Administrator

  Thanks. I haven't been able to reproduce the problem on a PowerBook G4, but I'll give it a shot on a PB G3.

  Posted 22 years ago #

• Karl Rubin Member

  I'm having exactly the same problem, on a dual-processor G4, 256 megs ram, running OSX 10.0.3. It worked fine through this morning, but now it quits after launch with the above message. I tried the 2 suggested remedies with the same results.

  Strangely, if I log in as the administrator then it starts up fine, so the application itself is not corrupted. I thought that might mean some permissions got corrupted, but when I give myself administrator privileges and log in again, Fetch still crashes on launch.

  Thanks very much for any help.

  Posted 22 years ago #

• Jim Matthews Administrator

  I installed 10.0.3 from scratch on a PowerBook G3 Firewire, and could not reproduce this problem, but then I was using the administrator account. I will try to reproduce using a user account.

  Are either of you comfortable enough with UNIX to edit a text configuration file? That might help me collect more information about the crash.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #

• Karl Rubin Member

  > Are either of you comfortable enough with UNIX to edit a text configuration file?

  I'd be happy to do that.

  Posted 22 years ago #

• Karl Rubin Member

  > Are either of you comfortable enough with UNIX to edit a text configuration file?

  I'd be happy to do that.

  Posted 22 years ago #

• Karl Rubin Member

  I solved the problem, at least for me. There was a file named "(null).plist" in Library/Preferences. With that file in place Fetch would crash, and without it Fetch works fine.

  I don't know where "(null).plist" came from, or why it caused the problem.

  Posted 22 years ago #

• Jim Matthews Administrator

  Thanks for that information! I will ask other people reporting this problem whether they have that file as well. Did you by any chance save the file? I would be interested in taking a look at it.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #

• DaRatBoyz Member

  That was it!
  (null).plist in my user/library/preferences

  Removed it and Fetch works just fine.

  I still have the file if you want to examine it. I thought that it had to be some file, but I did not know where to start the search.

  What made you think of that one, Karl?

  Posted 22 years ago #

• jims Member

  Add me as another user affected by this problem with the same solution -- find and remove the rogue (null).plist.

  Also don't know where it came from.

  Posted 22 years ago #