Annoying: Max 9 insists in locating a none existent Net drive on file load. Beachball spin Fest.
When trying to load any file into Max, its insisting in trying locate an old drive that was connected via ethernet, though it isn't connected. I have search for references to the drive in the system user library but its not there. Cannot find anything referencing to it in Max preferences either. It spins a beachball for a good 60 seconds before showing the Osx filesharing icon error, "Cannot Find Drive blah blah blah." I have cleaned all reference to this in Osx but its stuck with Max9. Any idea how to cure this?
can it be that you still have that location in your search path?
beside having a serach path related to that HD still active,
this is usually overseen in Max preferences , and could cause that behaviour
so, I should have made it clear in the description. No, its not a drive path I have set in the Max preferences. Ive been up and down the preferences. Im a long time Max user since its inception and on each new version, new settings creep in. Having had a break between 7 and 9 I wondered if there was something in Max 9 startup behaviour that had changed in terms of RNBO,Node ( which I dont use), asset paths. But no, there's nothing user settable that ive tweaked or added to include that path, as its a dedicated photography server that is disconnected. So no active path.
@ SourceAudio, thats one setting I need to check, though the dependencies my patch has, are all in the same patch folder on the same drive as Max.
I tried deleting other possible culprits in the Cycling74 application support library folder but no it insists in trying to locate. Tried Console.app to trace it but nothing obvious stands out. I thought it might be a system network sharing issue, but its only Max thats displaying this behaviour
Unticking the "Save Dependency Paths" seems to have cured it. Thank you @Source Audio for the tip.
It is hard to tell when you say I searched all possible culprits in app support folder,
what you expect to be a source of the problem.
Only 100% cleanup is to delete complete
Cycling folder in library, to remove all traces of max from documents including packages and everything else.
If max still produces that problem, one has to check the system , if there are any left aliases or links pointing to it that would tell max to rebuild database or search for something at that location
P.S. is creating new file working without problems ?
As stated previously. Solved. thx
All ok, I posted before seeing your reply