Aperture insists that I reregister it continually

cook - 09:08am Nov 8, 2007 PST

I have been a mac user for 22 years and I am getting mighty angry with the Apploids.

Aperture appears to be tied as closely to hardware as quark express - I spit on those bastards 5 years ago.

after calling support 15 minutes before closing time i tried waiting on speaker phone so i could type... then I picked the phone up to see if they were still there and lost the connection when i didn't reinitiated speaker properly.

Any way the problem - I am properly registered with apple, getting my machine to register the machine by calling apple over the internet was a pain, but i finally accomplished that.

Now aperature seems to need to be on the same drive that stores the photos.... my start up is a new seagate 320- gig that i installed with a 160 160 partition a few months ago. I am beginning to digitize color negatives 2560 by 1750 pixels in size.... in TIFF each file is about 12 meg. I color manage in photoshop and then migrate to aperture. I have about 15,000 negatives that i would like to do.

I was rapidly running out of space on my 160 gig partition. I bought a lacie firewire mac mini 500 gig hard drive and began using that about 10 days ago. I have aperture and all its files there and start aperture from there via an alias and store all libraries projects etc there. Today aperture refused to open until i reregisterd it which i did and sent the data to apple. Then tonight when i went back at 8:45 eastern it again asked me to fill out the registration form. Really pissed me off. So i tried calling... with this program you go to enterprise support which gererally sucks... they give no waiting time data... none...

and the DRM has stolen an hour of my time and i am disgusted with them... I paid $294 for the stinking product earlier this year... i want it to work and not hassle me every other day to re register it. At this point this is the last apple software i will buy.... ARGH!!!!

Aperture needs a system ID file to function, I checked and that file is there where it should be.

The problem in running it from this drive is just like the problems I had with running it on my internal G5 tower drive