crash.
in case you're wondering what's holding up the vacation photos: the hard drive in my (otherwise gracefully aging) 867 mhz 12" aluminum powerbook G4 had to be replaced yesterday.
we had some warning, and a semi-recent back up coupled with the important files i yanked onto my ipod that morning should mean a complete recovery. i replaced the hard drive with a speedy 100 gig job, and it was a little pricey, but i was frequently running out of room on the old 40 gig hard drive (i know! did you ever think?) and i was entranced by the idea of having all my photographs on my actual laptop, instead of being leashed to an external hard drive.
except.
i've also been really jazzed about buying a copy of aperture, which won't run on my tiny PB (actually, i have run into at least one account of it being successfully installed on a machine like mine, but it requires some hacks and is slower than dookie). it occurred to me that now that i've dished for a fast drive, if i packed the machine with the most RAM available, maybe i could suffer through poor Aperture performance. or maybe install it on both our machines and use chris's new baby when i could (keeping the photo library on my new gigantic hard drive) and mine as a last resort. i even considered getting a processor upgrade towards this end, one that was more expensive than the hard drive replacement. which someone at work wisely and speedily talked me out of.
or.
i could try the new beta of Adobe Lightroom, which has more lenient system requirements, ones that my machine actually meets. but what if i get all into the adobe product and can't stand the trauma of changing over once i have an actual aperture-able machine? no foul, i guess, so long as i have something that works, but: oh, aperture. you look so sweet.
or.
i could potentially have put the money i spent on the hard drive against a macbook. and i wouldn't even need the black one. sigh. it's a non-issue now; the technicians are doing the surgery as we speak. i really couldn't have thrown the money at a new machine in good conscience, but i'm sure i could have assuaged the guilt somehow.
besides, i think computers in our house should be like cars in my parents' house. you buy new ones at staggered intervals, so that someone's always driving something newer and the other person is usually tied to a dog for a few more years. reverse; repeat. and with potentially five more years of educational discounts, i could be in for something really sweet come 2011.
we had some warning, and a semi-recent back up coupled with the important files i yanked onto my ipod that morning should mean a complete recovery. i replaced the hard drive with a speedy 100 gig job, and it was a little pricey, but i was frequently running out of room on the old 40 gig hard drive (i know! did you ever think?) and i was entranced by the idea of having all my photographs on my actual laptop, instead of being leashed to an external hard drive.
except.
i've also been really jazzed about buying a copy of aperture, which won't run on my tiny PB (actually, i have run into at least one account of it being successfully installed on a machine like mine, but it requires some hacks and is slower than dookie). it occurred to me that now that i've dished for a fast drive, if i packed the machine with the most RAM available, maybe i could suffer through poor Aperture performance. or maybe install it on both our machines and use chris's new baby when i could (keeping the photo library on my new gigantic hard drive) and mine as a last resort. i even considered getting a processor upgrade towards this end, one that was more expensive than the hard drive replacement. which someone at work wisely and speedily talked me out of.
or.
i could try the new beta of Adobe Lightroom, which has more lenient system requirements, ones that my machine actually meets. but what if i get all into the adobe product and can't stand the trauma of changing over once i have an actual aperture-able machine? no foul, i guess, so long as i have something that works, but: oh, aperture. you look so sweet.
or.
i could potentially have put the money i spent on the hard drive against a macbook. and i wouldn't even need the black one. sigh. it's a non-issue now; the technicians are doing the surgery as we speak. i really couldn't have thrown the money at a new machine in good conscience, but i'm sure i could have assuaged the guilt somehow.
besides, i think computers in our house should be like cars in my parents' house. you buy new ones at staggered intervals, so that someone's always driving something newer and the other person is usually tied to a dog for a few more years. reverse; repeat. and with potentially five more years of educational discounts, i could be in for something really sweet come 2011.
posted by l. at 5:19 PM
0 Comments:
Post a Comment
<< Home