Closed haggis444 closed 11 years ago
It probably should have handled that more cleanly, I'll make sure it does in the next release.
I have this problem, too. Where do I find paths.xml? I must've let the app upgrade itself to 0.6alpha7. Looking at the readme, it seems that I need to look for a database. All I can find is a cache folder with images and a preferences plist which doesn't contain and remote paths.
I downloaded 0.5.4, and I'm working again. The network path issue seems to be gone, too.
Inside the application support folder for ViMediaManager, you may find one or more XML files, if you delete those it should forget the items it had listed before. Next to that you should probably remove the preferences files: /Users/YOURNAME/Library/Preferences/com.vidalvanbergen.vimediamanager.plist and/or: /Users/YOURNAME/Library/Preferences/com.vidalvanbergen.vimediamanager-alpha.plist
I deleted the entire ViMediaManager folder and the two plist files. However, 0.6a7 still tries to mount network shares. VMM 0.5.4 seems to be ok.
And if you try one of these builds after removing the settings: http://www.mediafire.com/vimediamanager (you'll probably want the "Intel" version)
The _Intel_
version no longer tries to mount network drives.
Good to hear. If you have the time, could you make sure that the Cocoa version works as well?
Weird, the cocoa one works, but doesn't give the welcome wizard.
And just be sure, I went back and re-tested the bug in the 0.6a7 from the main website and the network mount problem is there, but not in the two _Latest builds.
Unless you threw away the preferences file in between testing the intel and cocoa versions, it shouldn't show up since it's 'first start' has already happened.
The _Latest builds will eventually be released as v0.7a1, providing an official fix for the mentioned v0.6a7 bug.
I've removed the preferences before each run including the Cocoa build. No wizard for Cocoa, but wizard for Intel.
Odd, I have two test machines, but i'm unable to reproduce the issue on either of them.
It seems to have now reversed. I have no explanation.
From Application Support: rm -rf ViMediaManager/ ../Preferences/com.vidalvanbergen.vimediamanager* Then I double-click the app.
I had some paths setup that pointed to network shares (AFP). I shutdown ViMM, and disconnected the shares. When I started VMM I got the beach ball and it stop responding immediately. I waited minutes. I "Force quit" the app, and renamed the paths.xml file and started it again and it started right up---albeit with no paths.
This happened on 0.5.3/Lion 10.7.2