sorry for the long title, but hey, trying to be as detailed as possible.
I have the following problem with my aperture library... I have two computers a MBP and PM. The library resides on a external FW drive that also has a back up boot system on it from last year when my PM drive died. I had been running the PM off of the external since that point till 2 weeks ago when i finally found my tiger install disks after the HD on my MBP died and I lost all my music so was riffling through a box of CD's. The MBP's drive was replaced by apple care (as was the HD on the PM, though at the time I didn't have the time to have them install the OS since 1) I thought that i had the install disks at home, and 2) I had to be to work later and it was an in and out genius bar swap).
Now that I found my install disks and did a clean OS install on the PM I am having huge problems accessing the library when I boot off of the internal drive, but no problems what so ever when booted via external or when accessing it on the MBP (though it to has a clean install).
All updates are current on all systems and the aperture library sits at the root level of the external drive. My problems with the library when booted under the internal are that I can't create new projects in some folders, random crashing, slow loading of projects thumbnails and previewing, slow scrolling through projects, and errors coming up saying that either I don't have permission to do what I am doing or there is no space left on the drive (which there is, and on the topic of permission if I don't have permissions set then why can I access it via the MBP with no problems?)
Anybody have any ideas as to what this can be or more importantly what I can do to fix it? I have an internal drive on the PM that holds the vault and is separate from and I've thought of dragging the library to that drive and seeing if I can run it off of there, but I don't have the space on that drive to do it. Also, I realize that repairing permissions isn't going to do anything, and I've tried to rebuild the library under each system (under the external and the MBP it doesn't do anything, under the internal drive it crashes aperture). Oh, and when aperture is running, I can't even quit it normally, but am forced to force quit every time. But one thing that I failed to mention, is that if I create a new library with the internal booted aperture, then it runs perfectly fine.
Sorry that this is such a long post, but can anyone help?
I have the following problem with my aperture library... I have two computers a MBP and PM. The library resides on a external FW drive that also has a back up boot system on it from last year when my PM drive died. I had been running the PM off of the external since that point till 2 weeks ago when i finally found my tiger install disks after the HD on my MBP died and I lost all my music so was riffling through a box of CD's. The MBP's drive was replaced by apple care (as was the HD on the PM, though at the time I didn't have the time to have them install the OS since 1) I thought that i had the install disks at home, and 2) I had to be to work later and it was an in and out genius bar swap).
Now that I found my install disks and did a clean OS install on the PM I am having huge problems accessing the library when I boot off of the internal drive, but no problems what so ever when booted via external or when accessing it on the MBP (though it to has a clean install).
All updates are current on all systems and the aperture library sits at the root level of the external drive. My problems with the library when booted under the internal are that I can't create new projects in some folders, random crashing, slow loading of projects thumbnails and previewing, slow scrolling through projects, and errors coming up saying that either I don't have permission to do what I am doing or there is no space left on the drive (which there is, and on the topic of permission if I don't have permissions set then why can I access it via the MBP with no problems?)
Anybody have any ideas as to what this can be or more importantly what I can do to fix it? I have an internal drive on the PM that holds the vault and is separate from and I've thought of dragging the library to that drive and seeing if I can run it off of there, but I don't have the space on that drive to do it. Also, I realize that repairing permissions isn't going to do anything, and I've tried to rebuild the library under each system (under the external and the MBP it doesn't do anything, under the internal drive it crashes aperture). Oh, and when aperture is running, I can't even quit it normally, but am forced to force quit every time. But one thing that I failed to mention, is that if I create a new library with the internal booted aperture, then it runs perfectly fine.
Sorry that this is such a long post, but can anyone help?