Library Management Issue
I connected an external hard drive to my Airport Extreme through the USB. I set up the preferences correctly to move the folder there. I then consolidated the library and no problem. However, I am now manually copying a much larger library to that same hard drive from a second computer with a different library. I will then have two different folders on that external hard drive. How will I then have access through each computer to ALL the music? What's the next step?
You could copy the larger library to your Mac first, and then add the songs to iTunes using the "Add to library" Menu item.
But first, make sure that the settings in iTunes are pointing to the folder on the USB drive connected to your Airport Extreme. Then, when you add them to your library on the Mac, they're being copied to the library folder on the USB drive.
Scott
Similar Messages
-
Last month I downloaded this software called Sponge to get rid of duplicated pictures. I had about 6000+ pictures then. Now when it found a duplicated pic, they went in the trash and I kept it in there till I got the job done. So then I opened my iPhoto and to my surprise almost all of my pics had the exclamation point. I got really scared. So I checked the Pictures>iPhoto Library folder and all my pics are still there. So thankfully I still had all the duplicated pics in the trash, so I pulled them out and imported them back to iPhoto thinking that will solve the problem. That only made things worse! Now I have over 11000 pics and still exclamation points!
So I have been reading all the forums here and they say to use the iPhoto Library Manager . So i have used that but i have some problems with it. It seems like it is rebuilding my library but it always stops because its running out of room. I know i need to delete some pics but if i do that what will happen?
I was also wondering : If I take everything out of iPhoto , will it also be gone in the iPhoto Library Folder?
I'm just so confused on which approach I should take to recover my beloved pics.
Thanks for all your help in advanceWelcome to the Apple Discussions.
Your problem begins here:
Last month I downloaded this software called Sponge to get rid of duplicated pictures.
Using this on your iPhoto Library Folder has broken the cardinal rule of using iPhoto: Don't change anything in the iPhoto Library Folder via the Finder or any other application. iPhoto depends on the structure as well as the contents of this folder. Moving things, renaming things or otherwise making changes will prevent iPhoto from working and could even cause you to damage or lose your photos.
This app does not understand iPhoto and so it has damaged your Library:
Unfortunately you compounded the problem:
I still had all the duplicated pics in the trash, so I pulled them out and imported them back to iPhoto thinking that will solve the problem. That only made things worse! Now I have over 11000 pics and still exclamation points!
The ! turns up when iPhoto loses the connection between the thumbnail in the iPhoto Window and the file it represents. Re-importing the files will mean new files, it will not reconnect the old one.
You have a back up, right? These are your beloved pics, so you've got them backed up? The easiest solution to this mess is to restore from your back up and overwrite the ruined Library.
Regards
TD -
IPhoto and iPhoto Library Manager Issue With Faces
I use iPhoto ’11. I just recently imported some photos from my iMac iPhoto to my Macbook using the product iPhoto Library Manager. I thought everything went well until closer inspection. A lot of the faces in the imported library are off meaning for example, the people may be in the centre of the photo but the face tags are off to the left or right.
I thought I would manually try to fix this. However when I try to “add a face”, it looks like it’s going to work until I leave the photo and come back to it. The face tag has disappeared. Also on some photos, I can’t even click “add a face”. A few of the pictures say there is an unnamed face but there isn’t.
Any suggestions? Would it help if I reinstalled iPhoto 11?
TomIf you export out of iPhoto with Format=JPEG and the checkboxes selected to include keywords you can keep the keywords, titles and descriptions. If you check the box for Locations I believe you will get the faces also but am not sure on that.
iPhoto Library Manager keeps keywords, titles, description and Faces and Places when it copes between libraries. The fact that you had faces problems leads me believe that the library you were rebuilding with iPLM was damaged initially.
But you could check that out very easily. Create a new library, import about 10 photos and identify the faces in them. Then rebuild that library with iPLM. If it comes up the same then there's a problem with iPLM. It it comes up good then the original library was the culprit. -
I've had issues with my iPhoto "not responding" and as a result I am attempting to save my photos to an external hard drive using iPhoto library Manager but each time I start the program it saves some, and then when it starts iPhoto, iPhoto then goes into not responding mode. Using mac book pro, iphoto 9.5.1, and maverick 10.9.2. I have completed all of the photo library first aid steps several times, but it makes no difference, iphoto eventually goes to "not responding." Initial issues started with Time Machine back ups stopping because of iphoto. Thanks......
Do you have a back up?
If you're just trying to recover the photos you can do that much more simply:
Go to your Pictures Folder and find the iPhoto Library there. Right (or Control-) Click on the icon and select 'Show Package Contents'. A finder window will open with the Library exposed.
Look there for a Folder called 'Originals' or 'Masters'. (varies according to the version of iPhoto)
Your photos are inside - these are the originals as imported from your camera. -
The Ultimate Guide to Resolving Profile and Device Manager Issues
The following article also applies to issues after re-setting the severs' hostname. It also applies to situations where re-setting the Code Signing Certifictateas described by Apple has not resolved the issue.
Hello,
I have been plagued with Profile Manager and Device Manager issues since day one.
I would like to share my experience and to suggest a way how to resolve issues such as device cannot be enrolled or Code Signing Certificate not accepted.
I shall try to be as brief as possible, just giving an overview of the steps that resolved my issues. The individual steps have been described elsewhere in this forum. For users who have purchased commercial SSL certs the following may not apply.
In my view many of these issues are caused by missing or faulty certificates. So let us first touch on the very complex matter of certificates.
Certificates come in many flavours such as CA (Certificate Authority), Code Signing Certificate, S/MIME and Server Identification.
(Mountain?) Lion Server creates a so-called Intermediate CA certificate (IntermediateCA_hostname_1") and Server Identification Certificate ("hostname") when it installs first. This is critical for the operation of many server functionalities, including Open Direcory. These certs together with the private/public keys can be found in your Keychain. Profile and Device Manager may need a Code Signing Certificate.
The most straightforward way to resolve the Profile Manaher issues is in my view to reset the server created certicates.
The bad news is that this procedure involves quite a few steps and at least 2 hours of your precious time because it means creating a fresh Direcory Master.
I hope that I have not forgotten to mention an important step. Readers' comments and addenda are welcome.
I shall outline a sensible strategy:
1. Clone your dysfunctional server to an external harddrive (SuperDuper does a reliable job)
2. Start the server fom the clone and shut down ALL services.
3. It may be sensible to set up a root user access.
4. Back-up all user data such as addess book, calendar and other data that you *may* need to set up your server.
5. Open Workgroup Manager and export all user and workgroup accounts to the drive that you using to re-build your server (it may cause problems if you back-up to an external drive).
6. Just in case you may also want to back-up the Profile Manager database and erase user profiles:
In Terminal (this applies to Lion Server - paths may be diferent in Mountain Lion !)
Backup: sudo pg_dump -U _postgres -c device_management > $HOME/device_management.sql
Erase database:
sudo /usr/share/devicemgr/backend/wipeDB.sh
7. Note your Directory (diradmin) password for later if you want to re-use it.
8. Open Open Server Admin and demote OD Master to Standalone Directory.
9. In Terminal delete the old Certificate Authority
sudo rm -R /var/root/Library/Application\ Support/Certificate\ Authority/
This step is crucial because else re-building you OD Master will fail.
9. Go back to Server Admin and promote the Standalone Directory to OD Master. You may want to use the same hostname.
10. When the OD Master is ready click on Overview and check that the LDAP and Keberos Realm reflect your server's hostname.
11. Go back to Workgroup Manager and re-import users and groups.
NOTE: passwords are not being exported. I do not know how to salvage user passwords. (Maybe passwords can be recovered by re-mporting an OD archive - comments welcome! ).
12. Go to Server App and reset passwords and (not to forget) user homefolder locations, in particular if you want to login from a network account!
If the home directory has not been defined you cannot login from a network account.
13. You may now want to restore Profile Manager user profiles in Terminal. Issue the following commands:
sudo serveradmin stop devicemgr
sudo serveradmin start postgres
sudo psql -U _postgres -d device_management -f $HOME/device_management.sql
sudo serveradmin start devicemgr
14. You can now switch back on your services, including Profile Manager.
In Profile Manager you may have to configure Device Management. This creates a correct Code Signng Certicate.
15. Check the certificate settings in Server App -> Hadware -> Settings-> SSL Certificates.
16. Check that Apple Push Notifications are set.(you easily check if they are working later)
17. You may want to re-boot OS Server from the clone now.
18. After re-boot open Server App and check that your server is running well.
19. Delete all profiles in System Preferences -> Profiles.
19. Login to Profile Manager. You should have all users and profiles back. In my experience devices have to be re-enrolled before profiles can be pushed and/or devices be enrolled. You may just as well delete the displayed devices now.
20. Grab one of your (portable) Macs that you want to enrol and go to (yourhostname)/mydevices and install the server's trust profile. The profile's name should read "Trust Profile for...) and underneath in green font "Verified".
21. Re-enrol that device. At this stage keep your finger's crossed and take a deep breath.
22. If the device has been successfully enrolled you may at last want to test if pushing profiles really works. Login to Profile Manager as admin, select the newly enrolled device. Check that Automatic Push is enabled (-> Profile -> General). Create a harmless management profile such as defining the dock's position on the target machine. (Do not forget to click SAVE at the end - this is easily missed here). If all is well Profile Manager will display an active task (sending) and the dock's position on the target will have changed in a few seconds if you are on a LAN (Note: If sending seems to take forever: check on the server machine and/or on your router that the proper ports are open and that incoming data is not intercepted by Little Snitch or similar software).
Note: if you intend to enrol an Apple iPhone you may first need to install the proper Apple Configuration software.
Now enjoy Profile and Device Manager !
Regards,
TwistanHI
1. In Action profiles, logon to system and recheck correcion are available in action definition as well in condition configuration and the schedule condition is also maintained. but the display is not coming(i.e in the worklist this action is not getting displayed).
You can check the schedule condition for the action and match the status values...or try recreating the action with schedule condition again....for customer specific ....copy the standard aciton with ur zname and make a schedule condition and check the same.
2, In suppport team of incident when i give individual processor it throwing a warning that u r not the processor. but when i give org unit it is working perfectly. Could anyone guide on this.
You need to have the empolyee role for BP ..goto BP and got here dropdown for ur bp and choose role Employee and then enter ur userid
also make sure that u have the message processing role
Hope it clarifies ur doubt and resolve ur prob
Regards
Prakhar -
Is there a better way to deal with Edge Animate CC's library management?
I haven't been using Edge Animate CC for very long, but I already have a huge list of complaints. Although I could go into detail about features that seem to be missing from my version of Edge (just a quick example, all of the tutorials I've seen have a quick code insert feature on the right side of the code dialog box that my version doesn't seem to have, or even have the option for turning on), right now I want to focus on Edge's HORRENDOUS LIBRARY MANAGEMENT.
So I created the following animation which I have put into an iframe:
The issue I had on the first draft of this project was that I (perhaps naively) thought that there would be an option to actually re-size the pictures on export. There wasn't, and so my original version was really, really large, took way too long to load, and needed to be updated. For the second version, I reduced the size of the pictures and made them JPEG files (some of the originals were - quite unnecessarily - large PNG files) and reduced the quality so that they were all under 10KB. Of course, I had to rename the files and re-import them to Edge's library. This is where my problems started.
You see, edge will put the files into a folder marked "images" when you publish them in a folder, so I just assumed (NOT UNREASONABLY) that the resulting animation would pull from the images folder. It worked fine in the preview, so I pushed it via FTP, only to find that all of the original files (which were not in the new animation) were pushed to the new "images" folder. The only library management that you get in Edge is apparently looking for the file in the folder you designate as the "Library" folder, so deleting these images out of the "Images" folder makes not one bit of difference. That should have been my first clue that something was rotten in Denmark, to use a Shakespearean metaphor. After removing these files and publishing my banner again, suddenly the new images weren't showing up. They were clearly in the "images" folder on the FTP server, but they weren't showing up in the animation. So I inspected the banner on the site, only to find that rather than point to the images folder, they are in fact pointing to the library folder. WHY DO THE PUBLISHED IMAGES POINT TO THE "LIBRARY" FOLDER THEY WERE PULLED FROM INSTEAD OF THE "IMAGES" FOLDER THAT THEY'RE PUBLISHED TO? I added a new file tree that mimicked the folder structure and put the images in a mock "library folder" and now the animation works again.
The library management in this program is just plain awful (I can't stress this enough), making it a chore for experienced users and a red-hot rage-keyboard-pounding mess for everyone else. And the worst part, there doesn't seem to be any explanation from Adobe on why it is this way.
I am really not looking forward to the next time I have to use this program at work.I'm not sure that's any easier. It would be nice if Edge gave you a(n obvious) way to re-link files, but it even fails in that respect.
What would be better is if I could just point Edge to my FTP site and put the library on there. It would solve so many problems... failing that though, some sort of library management option set needs to be implemented in this software. I try to practice appropriate file management, but I hate having to be punished with an extra twenty minutes of work for one little mistake. -
Aperture 3 VS. iPhoto Library management policies
Let me start this off with the fact that I am new to the whole Mac scene. I am used to the PC world of managing everything neatly in folders and subfolders inside My Pictures folder. In PC land I was using importing everything automaticaly with my Nikon software. I seriously miss its ability to lable my folders exactly as I wanted them. I could then use whatever software I needed to edit from simple stuff with my Nikon software suite, to Correl Draw, to Photoshop. Sonce everything was left in the same folders, "library managment" was much simpler. Manually going in and moving pictures around was easy. Before the switch to Apple, I spent many many hours researching and studying.
So I have been usign my new MacBook Pro exclusivly for about 6 months now and still can not get my libraries organized as effectivly as I would like. The whole lack of one central folder location, has me thrown off. Okay lets start with my questions. I have a pile of them, so my apologies in advance...
1) Can I use one library for both applications? I started off with iPhoto, then purchased Aperture 3 as soon as it was avalible. I see that deleting fluff in one does not currently correspond to the other program. When setting up Aperture, I imported my iPhoto library. It seems to me that it doubled the amount of space used for my photos...
2) From what I have read, I am lead to understand that iPhoto is less of a space hog. It saved layers of edits over the pictures, while Aperture 3 saves each as a new photo. All done seamlessly behind the scenes. Is this correct?
3) When I imported the iPhoto library to Aperture, it forgot all my faces I had named. Yes I have Aperture setup to see the faces thing... I think. Can I fix this simply without going through the whole naming process again?
4) Can I "manually" import/export the librarys simply by dropping them to the desktop, and renaming them then dropping them back in the picutres folder?
I would like to really consolidate and trim down the space being used. I have over 100 gigs of photos per library and that is being VERY choosy about what I save. All my professional work I shoot in RAW. As for the two programs, I see no real reason to keep iPhoto, as it seems all the other software programs like mail and iWork integrate just as well with Aperture.
5) How do I set a high quality desktop image from my own librarys? This is super frustrating!!! The only way I can seem to get high resolution pictures reliably, is if I can figure out how to open it in Safari, then set as a desktop. Sometimes using system preferances it will work, but mostly I get really low resolution shots that look like maybe they are blown up preview or thumbnail images. Even delibertly using the same shot and trying to find it in the multiple locations I find, I can't seem to duplicate a process that gets me a clean shot via System Preferances. It seems that the iPhoto versions are higher quality.
I have gigs woth of personal shots I would love to browse through and use, but everytime it is a huge headache to do so.... I think most of my issues here are in understandign how to navigate the pictures in the Mac OS X. I think ideally I would like to dump iPhoto and stick to just Aperture. Mostly, I am loving the way all the programs in OS X seem to integrate and work together. Just having some serious stumbling blocks with the photography apects, and that was the primary reason I switched to a Mac.
6) So will the rest of the software like iMovie, iWeb, Mail, and Garage Band work as well with Aperture as iPhoto?
I need to sort out all the above issues and decide what direction to go and how to go about rebuilding my libraries. I have gigs worth of older family shots, downloaded images, freinds photography, and other random images I would like to keep seperated from my professional work. Aperture is without a dought a much better program for my professional, and daily use. I am just having issues accessign my work directly like I used to do on the PC no matter what program on the Mac I am working with.I'll try to help you out a bit more:
First I'd recommend a post here by Kirby Krieger
This will get you on par with Aperture workflow and nomenclature. I can only reccomend you a good book if you're able to understand Dutch ;-) And BTW a book or manual is easier to pause then a video ;-)
The Well-trod Path. Walk it unless you have a map for a different route.
The Library is your image database. It contains all the information Aperture has about your images: where they are stored on your computer/drives/network, how you have them organized within Aperture, what adjustments you have made to them, all the pre-Aperture metadata (EXIF, IPTC, keywords, etc.) they had before you imported them into Aperture, and all the Aperture metadata (Version names, ratings, color labels, Stacks, additional keywords, etc.) you assign to them from within Aperture. The Library also contains small copies of each image (in effect, thumbnails, but in Aperture larger than actual thumbnails and called "Previews").
The image is the core record in your Aperture database. The database is a giant list of images with a whole bunch of information assigned to each image.
Within Aperture you can view individual images and any grouping of images. You can create a group based on any of the information you have about your images.
The Project is your primary image holder. It has a unique, privileged relationship with your images: Every image must be in a Project; No image can be in more than one Project. You should make a Project from every actual, out-in-the-world photo shoot that you do. Shoot=Project. Stick to this (the mis-naming of "Project" is one of the worst interface decisions made in Aperture).
You will regularly want to view your images in groups other than the Project in which they reside. Aperture provides several specific containers for this (as well as superb tools for creating ad hoc groupings). As a family, those containers are Albums. Aperture includes (regular) Albums, Smart Albums, and the following albums dedicated to special tasks: Book, Light Table, Slide Show, Web Journal, Web Page. Any image can be in any album, and can be in as many albums as you want.
As your Aperture database grows, you will want to organize your Projects and Albums. Aperture provides Folders to aid you. Folders hold groups of Projects, Albums, and other Folders. Folders cannot contain images which are not in a Project or Album: You do not put images in Folders; you put containers in Folders.
The organization of your image database is entirely for you to customize for your needs.
There are two additional pieces of the Aperture puzzle every new user needs to understand in order to make good use of it.
In additional to what I listed above, your Library may or may not contain your original image files. Each image in Aperture has an original. Aperture is non-destructive -- your original image files are never altered. If the original image file is contained within your Library, it is called a Managed Master (Aperture's pointer to this file, and the file itself, are both inside the Library). If the original image file is not contained within your Library, it is called a Referenced Master (the pointer in your Aperture Library points to a file outside your Aperture Library). Referenced Masters bring some important advantages -- but the new user of Aperture can rely on Managed Masters until the need for Referenced Masters arises. Aperture makes is easy to convert your original image files back and forth from Managed to Referenced.
A Version is the name given to the variants and copies you make of you original image within Aperture. You use Aperture's tools to make Adjustments to images. Each group of adjustments you make to one image is saved as a Version. You can (and should) create as many Versions as you need. Versions appear as images, but are simply text instructions which tell Aperture what Adjustments to make to the original image file. Aperture presents these to you on-the-fly. This is brilliant. It means that Versions are minuscule compared to Masters. The gain in storage and computational efficiency is enormous.
This also means that your images in Aperture do not exist as image format files. In order to create an image format file, you must export the image from within Aperture. There is no reason to do this until you need an image format file outside of Aperture.
Aperture, then, is best understood as a workspace for
storing
organizing
adjusting
preparing for publication, and
publishing
digital photographs.
Your workflow is
shoot
import as Project(s)
add image-specific metadata
organize into Albums, organize Albums and Projects with Folders
make adjustments to images (crop, rotate, change exposure, etc. etc. etc)
prepare for publication
publish.
If you still need to synchronize between computers (which or NOT running Aperture) you could still be using your old folder structure. Import then from the _raw folder, organize and manage them in Aperture and use relocate masters to move them to the correct position. In Aperture you could setup a Project per shoot, and then (Smart)albums in that project for what used to be subfolders when you where working on Windows. For synchronizing between Aperture using computers it best to copy libraries. (You can export a project as a new library as well)
Then for other RAW converters, take a look at why people recommend CaptureNX. It's mostly because of initial conversion. That is because CapertureNX is able to read in camera settings whereas other converters cannot. For some Nikon's color rendering in Aperture might be a bit of, but you can correct that while developing. Personally I had only one occasion where I wanted to edit in ACR instead of Aperture. (Because I needed a gradient adjustment and Aperture at that time did not have brushes yet) As you mentioned yourself already, one converter is usually the best choice. Pick one that suits you and stick with it.
For HDR, there are some plugins for that, otherwise export to 16-bit TIFF (which is essentially RAW), do the HDR in PS and import back again. Not that big-a-deal.
For there rest, when you encounter some problems anywhere on the Mac, think of the easiest solution you can imagine, that usually how it works on the Mac. That why you hardly ever have to leave your Aperture interface while organizing your photo's. -
IPhoto 6 crashes when opening with iPhoto Library Manager with external sto
I've had stored many iPhoto libraries on my Freecom Mobile Drive 160gb, accessing them via iPhoto Library Manager, for years. Suddenly, when I try to open a library, iPhoto crashes. I'm still able to go into the storage disk so I don't think this is damaged. I've also reinstalled IPLManager (using original 3.2.3), without any luck.
I get this crash report (greatly abbreviated)
PID: 809
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Does this make sense to anyone? I can't understand why one minute everything is fine, and then the next a procedure which has worked for a long time, doesn't. BTW, I've taken off lots of junk from the Freecom external drive (have 44gb available) and 3gb available on my iBook.
Many thanks in advance for any help or advice.That
Exception Codes: KERNPROTECTIONFAILURE
is always a Data Related issue.
So use iPhoto Library Manager to rebuild the Library. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
Regards
TD -
My organisation is just getting into Java development. We are keen to maximise the re-use benefits of Java and there is potential for a wide range of common components across projects. We will have 3 main environments: development, acceptance and production, on separate servers. We will soon have a number of separate projects and developer teams. We want to avoid getting into a situation where there are lots of libraries with incompatible versions of similar class files, that will ultimately end up as a mess for someone to clean up.
There does not appear to be much guidance material around that deals with this type of Java management issue. Can anyone point me in the right direction?
Thanks
John Franze
[email protected]Hi.
The first thing to realise (which it appears you have) is that reuse does not happen on its own. The reasons for this are political, sociological, psychological, organisational, etc...
If you are serious about reuse, then your organisation will have to:
a) encourage developers to reuse existing stuff
b) encourage developers to develop reusable stuff
c) support the management of reusable stuff with suitable infrastructure (a component library for example)
Now, if your organisation is intending to use any metrics like 'lines of code produced' then you will kill (a) completely. So be very careful about what you measure.
If your organisation is intending to hassle developers to get their project task finished and move onto the next one because their current project has aggressive deadlines to meet, then you will kill (b) completely.
Also, be aware that developing reusable stuff typically takes about 3 times as long as writing stuff ad-hoc. Also, writing re-usable stuff is generally hard until you know how it's going to be reused. A common approach is: write the specific form of the code. If you need something similar again and you can't see how to generalise the first form immediately, then write it again for the second time. If you need something similar a third time, then you have two working examples of the component and one requirement for a slightly different form so you now know enough about what the general form is to make it economically viable to develop it.
My last piece of advice is: you need somewhere to put your components where they are locatable by keyword search or something. This might be a separate department that acts as a library/librarian.
You might find some useful writings in the links that you will see here: http://dir.yahoo.com/Computers_and_Internet/Programming_and_Development/Tools/Software_Engineering/Software_Reuse/
Good luck.
Lance
Lance Walton - [email protected]
Team In A Box - Software without Tragedy
http://www.teaminabox.co.uk -
hi i asked this recently: there are 2 admin accounts on this mac, one for me and one for my dad. i'm the only person who has time to use iphoto and all of our pictures and slideshows are on my account. so if my dad wants to see the pictures or slideshows, he can't from his own account. is there a way to make this a sort of joint-application or perhaps another solution?
one solution recommended was using the program iphoto library manager. well i downloaded the program, but i still can't figure out how to solve my issue. any ideas at all?asli:
iPhoto Library Manager is for one user managing multiple libraries. There are several ways to share a library. One way is for each user to have their own library using the "alias" mode and then share the source files that are placed in the Shared folder on in the Users folder. Then each user would have complete control of their own library, edits, etc. Neither can delete one of the source files from the Shared folder via their library, only delete it from their library.
Do a search for "share library" or similar and you'll find other ways to do the job. One of the pitfalls of sharing is that when one user accesses the library and does any editing it changes the permissions and can block out the other user. But the alias method gets around that as well as some of the other sharing methods. I'm not conversant in those other methods so that's why I'm suggesting you do a search. Lori is one poster who knows a lot about the sharing process. Look for her posts also.
Do you Twango? -
IPhoto Memory Management Issue?!
I've been having an issue with trying to import Photos with iPhoto 9.21 for some time now and finally decided to try to figure out what's going on. Config: Mac Pro 1.1, 5 gigs RAM, 250 Gig, 500 Gig x 2 (RAID 1) where iTunes and iPhoto reside, 160 Gig for Time Machine, OSX Lion.
I believe this issue is due to a lack of memory management. Our iPhoto library is approximately 40 gigabytes and will crash when trying to import even small quantities of images/video. I've run disk permissions, deleted plists, etc. I have noticed that iphoto will use all of the available RAM on the computer when it's running.
I figured I'd try rebuilding the library using iPhoto Library Manager and while that was running, I was watching memory usage while the rebuild process was going and over time more memory was getting used. The rebuilt library hit around 27.5 gigs when I ran out of free memory and iPhoto quit.
The next step was to create a new library and try importing photos and videos again. Started with a mix of files from my iphone 4S and then RAW and jpeg files from a Canon (18 megapixel) and they all imported without issue. The same files would crash iphoto in the original library.
Adding another 4 gigs of RAM to the computer to see if that rectifies the problem assuming it doesn't get sucked dry on a 40 gig library! I'll update the post after I get the RAM installed and can try importing into the main library.
JohnFinished rebuilding the library per Fix #1. Tried to import 48 RAW files and it crashed while in process. Again, the RAM Free RAM was gone! Here's the crash report:
Process: iPhoto [706]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier: com.apple.iPhoto
Version: 9.2.1 (9.2.1)
Build Info: iPhotoProject-628000000000000~1
App Item ID: 408981381
App External ID: 4641130
Code Type: X86 (Native)
Parent Process: launchd [152]
Date/Time: 2012-01-28 15:52:26.203 -0800
OS Version: Mac OS X 10.7.2 (11C74)
Report Version: 9
Interval Since Last Report: 182337 sec
Crashes Since Last Report: 8
Per-App Interval Since Last Report: 21333 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: F900FBFC-BDD3-4299-ADFF-5CC409100C51
Crashed Thread: 44 Import thread 1
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000001568b2
VM Regions Near 0x1568b2:
shared memory 0000000000002000-0000000000003000 [ 4K] rw-/rw- SM=SHM
-->
MALLOC_SMALL 0000000004458000-0000000004800000 [ 3744K] rw-/rwx SM=PRV
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.HIToolbox 0x9b863a7f RunCurrentEventLoopInMode + 318
7 com.apple.HIToolbox 0x9b86ad9b ReceiveNextEventCommon + 381
8 com.apple.HIToolbox 0x9b86ac0a BlockUntilNextEventMatchingListInMode + 88
9 com.apple.AppKit 0x901bc040 _DPSNextEvent + 678
10 com.apple.AppKit 0x901bb8ab -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
11 com.apple.AppKit 0x901b7c22 -[NSApplication run] + 911
12 com.apple.AppKit 0x9044c18a NSApplicationMain + 1054
13 ??? 0x0001159a 0 + 71066
14 ??? 0x00010a29 0 + 68137
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9b7d2b5e __select_nocancel + 10
1 libdispatch.dylib 0x938e6b11 _dispatch_mgr_invoke + 642
2 libdispatch.dylib 0x938e56a7 _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c674607 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 ??? 0x0175aaed 0 + 24488685
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c674607 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 ??? 0x0175aaed 0 + 24488685
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 5:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 6:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c674607 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 ??? 0x0175aaed 0 + 24488685
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 14:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 15:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 18:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 19:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 20:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 21:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 22:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 23:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 24:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 ??? 0x0184bf41 0 + 25476929
3 ??? 0x0184bdc9 0 + 25476553
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 25:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 ??? 0x0184bf41 0 + 25476929
3 ??? 0x0184bdc9 0 + 25476553
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 26:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01d35ac1 0 + 30628545
7 com.apple.CoreFoundation 0x9ac2f53a -[NSObject performSelector:] + 58
8 ??? 0x01763626 0 + 24524326
9 com.apple.CoreFoundation 0x9ac27091 -[NSObject performSelector:withObject:] + 65
10 ??? 0x0175acb5 0 + 24489141
11 ??? 0x0175a406 0 + 24486918
12 ??? 0x01759f55 0 + 24485717
13 ??? 0x017586c6 0 + 24479430
14 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
15 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
16 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
17 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 27:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreServices.CarbonCore 0x944385a3 TSWaitOnConditionTimedRelative + 178
4 com.apple.CoreServices.CarbonCore 0x94438319 TSWaitOnSemaphoreCommon + 490
5 com.apple.CoreServices.CarbonCore 0x9443812a TSWaitOnSemaphoreRelative + 24
6 com.apple.QuickTimeComponents.component 0x91abade6 0x914ce000 + 6213094
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 28:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.Foundation 0x9c6c9d40 -[NSCondition wait] + 304
4 ??? 0x0005c66a 0 + 378474
5 ??? 0x0005c5c2 0 + 378306
6 com.apple.CoreFoundation 0x9ac29e1d __invoking___ + 29
7 com.apple.CoreFoundation 0x9ac29d59 -[NSInvocation invoke] + 137
8 ??? 0x01d57e61 0 + 30768737
9 ??? 0x01d696c4 0 + 30840516
10 com.apple.CoreFoundation 0x9ac27091 -[NSObject performSelector:withObject:] + 65
11 ??? 0x01763626 0 + 24524326
12 com.apple.CoreFoundation 0x9ac27091 -[NSObject performSelector:withObject:] + 65
13 ??? 0x0175acb5 0 + 24489141
14 ??? 0x0175a406 0 + 24486918
15 ??? 0x01759f55 0 + 24485717
16 ??? 0x017586c6 0 + 24479430
17 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
18 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
19 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
20 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 29:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 30:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c6d421c +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
7 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
8 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
9 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
10 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 31:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x9b7d2b42 __select + 10
1 com.apple.CoreFoundation 0x9ac16195 __CFSocketManager + 1557
2 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
3 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 32:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 ??? 0x0184bf41 0 + 25476929
3 ??? 0x0184bdc9 0 + 25476553
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 33:: JavaScriptCore::BlockFree
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c3e0 pthread_cond_timedwait$UNIX2003 + 70
3 com.apple.JavaScriptCore 0x92ce09dc ***::ThreadCondition::timedWait(***::Mutex&, double) + 156
4 com.apple.JavaScriptCore 0x92ed4f03 JSC::Heap::blockFreeingThreadMain() + 323
5 com.apple.JavaScriptCore 0x92ed4f3f JSC::Heap::blockFreeingThreadStartFunc(void*) + 15
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 34:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc2382a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x91bdccc9 0x914ce000 + 7400649
4 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 35:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc2382a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x91bdccc9 0x914ce000 + 7400649
4 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 36:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc2382a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x91bdccc9 0x914ce000 + 7400649
4 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 37:
0 libsystem_kernel.dylib 0x9b7d302e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9bc79ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 38:
0 libsystem_kernel.dylib 0x9b7d2b0a __rename + 10
1 libsystem_kernel.dylib 0x9b7d1c53 rename + 25
2 com.apple.CoreFoundation 0x9ac151bc -[CFXPreferencesPropertyListSourceSynchronizer writePlistToDisk] + 1052
3 com.apple.CoreFoundation 0x9abd9ab3 -[CFXPreferencesPropertyListSourceSynchronizer synchronizeAlreadyFlocked] + 595
4 com.apple.CoreFoundation 0x9abd981e -[CFXPreferencesPropertyListSourceSynchronizer synchronize] + 526
5 com.apple.CoreFoundation 0x9ac1c88a __-[CFXPreferencesPropertyListSource synchronizeInBackgroundWithCompletionBlock:]_block_invoke_1 + 122
6 libdispatch.dylib 0x938e4e11 _dispatch_call_block_and_release + 15
7 libdispatch.dylib 0x938e6797 _dispatch_queue_drain + 224
8 libdispatch.dylib 0x938e663c _dispatch_queue_invoke + 47
9 libdispatch.dylib 0x938e5e44 _dispatch_worker_thread2 + 187
10 libsystem_c.dylib 0x9bc79b24 _pthread_wqthread + 346
11 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 39:: CVDisplayLink
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreVideo 0x953f92e8 CVDisplayLink::waitUntil(unsigned long long) + 306
4 com.apple.CoreVideo 0x953f843a CVDisplayLink::runIOThread() + 706
5 com.apple.CoreVideo 0x953f8161 _ZL13startIOThreadPv + 160
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 40:
0 libsystem_kernel.dylib 0x9b7d302e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9bc79ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 41:
0 libsystem_kernel.dylib 0x9b7d302e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9bc79ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 42:: com.apple.appkit-heartbeat
0 libsystem_kernel.dylib 0x9b7d2bb2 __semwait_signal + 10
1 libsystem_c.dylib 0x9bc2c7b9 nanosleep$UNIX2003 + 187
2 libsystem_c.dylib 0x9bc2c558 usleep$UNIX2003 + 60
3 com.apple.AppKit 0x90403be2 -[NSUIHeartBeat _heartBeatThread:] + 2399
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 43:: Import thread 0
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.AE 0x9367024f AESendMessage + 4116
7 com.apple.ImageCapture 0x93e8c462 ICAAESendMessage + 192
8 com.apple.ImageCapture 0x93e8c112 ICACommand::SendSync() + 62
9 com.apple.ImageCapture 0x93e8c00e ICACommand::ProcessCommand() + 74
10 com.apple.ImageCapture 0x93e8def3 ICADownloadFile + 819
11 ??? 0x0029a2fb 0 + 2728699
12 ??? 0x006831de 0 + 6828510
13 ??? 0x00150aeb 0 + 1379051
14 ??? 0x001508ef 0 + 1378543
15 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
16 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 44 Crashed:: Import thread 1
0 ??? 0x001568b2 0 + 1403058
1 libobjc.A.dylib 0x9369754e _objc_rootRelease + 47
2 ??? 0x0067b2de 0 + 6795998
3 ??? 0x001512a0 0 + 1381024
4 ??? 0x001508ef 0 + 1378543
5 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
6 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 45:: Import thread 2
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? 0x00683178 0 + 6828408
5 ??? 0x00150aeb 0 + 1379051
6 ??? 0x001508ef 0 + 1378543
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 46:: Import thread 3
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? 0x00683178 0 + 6828408
5 ??? 0x00150aeb 0 + 1379051
6 ??? 0x001508ef 0 + 1378543
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 47:: Import thread 4
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? 0x00683178 0 + 6828408
5 ??? 0x00150aeb 0 + 1379051
6 ??? 0x001508ef 0 + 1378543
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 48:: Import thread 5
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? -
Grotesque - an interactive fiction library manager
Grotesque is a library manager for interactive fiction (text adventures). Its currently at version 0.9.2, so it's close to feature complete but I'm still ironing out some bugs.
It features automatic metadata extraction for Treaty of Babel-compatible games. For other cases, metadata, coverart and ratings are fetched from the Interactive Fiction Database. For launching the games, you'll need a separate interpreter, such as Gargoyle.
There are two flavors available:
GTK2: https://aur.archlinux.org/packages.php?ID=28915
GTK3: https://aur.archlinux.org/packages.php?ID=51572
Enjoy!
Last edited by jakobcreutzfeldt (2011-08-16 18:11:37)I don't think an interactive portion of a PDF is an obscure problem (lots of designers I know use rollable PDF files for emailing 3D models) and while I understand that it's in a legacy program, there is no guarantee if I purchase Acrobat X, that the same problem won't exist. It's no an issue in Reader 10 but then again, it wasn't an issue in Reader 9 either. Since Adobe doesn't give trial versions for Mac (stupid), I have no way of checking this. The problem doesn't annoy me as much as being an Adobe product user who upgraded only to not have functionality and not have a way to have it resolved.
-
IPhoto Library Manager won't open, what to do? .
Pls HELP.
I downloaded iPhoto 9.2.3, and when i tried to open it the app completely froze. I was instructed to hold down command and option keys when clicking on iPhoto and use the resulting dialogue box to rebuild the library database. I tried that, but half of my photos are not there. I was told to use the Library Manager, which i downloaded but it will not open. I get, "Can not open the application because it is not supported on this type of Mac". I have the Mac OS X, 10.6.8.
WHAT CAN I DO NOW??? I DON'T WANT TO LOSE ALL THOSE PHOTOS BECAUSE I DOWNLOADED iPhoto 9.2.3!!!
Can I download an older version of iPhoto? the older one worked fine.
SOMEONE PLS HELP ME!!!??Contact the makers of Library Manager at their website
http://www.fatcatsoftware.com -
ITunes 10 and iTunes Library Manager 5.3
Is there any kind soul out there on a Mac who uses Doug's iTunes Library Manager 5.3 and has upgraded from iTunes 9 to iTunes 10? Does iTunes Library Manager 5.3 work with version 10?
I am NOT looking for people telling me to use iTunes' own multiple library feature; I already have a complex multi-library/multi-preference/multi-hard drive set up and will only update to iTunes 10 if it works with Doug's iTunes Library Manager 5.3 (or if Doug updates; no mention of iTunes 10 on his website).
I'd appreciate any feedback from anyone who's actually upgraded to iTunes 10 and is using iTunes Library Manager 5.3.
Thanks in advance.Paris Jake wrote:
I'd appreciate any feedback from anyone who's actually upgraded to iTunes 10 and is using iTunes Library Manager 5.3.
if you don't get any feedback, send Doug an email and obtain feedback from the horse's mouth
JGG -
How do I use iphoto library manager to restore photos
Upon opening iphoto is says it is unreadable and i read other posts to hold option and command down and click all the options to start iphoto. Didnt work. I downloaded iphoto library manager, but am unable to click on the photos. Can someone give me step by step directions? As of right now I am copying the original iphoto library to see if that will work. I am freaking out over losing all my pics....
Please helpIPLM support link is here. http://www.fatcatsoftware.com/iplm/
LN
Maybe you are looking for
-
Hi, I am modifying the Signature email body under workflow in Cutom Translations in Data Admin Tool Kit. When I am trying to write in new line, I am not able to write. I used HTML tags like \n but then also it is not writing in to new line.It is comi
-
Report to list all infotype record per employee
Hi All is there a report that list all infotypes record per employee ? thanks for helping Corinne
-
Help me turn off the spell checker
The iApps are usually so intuitive but for some reason I simply can't find a way to turn off the extremely annoying spell checker in Keynote. Not only do I strenuously object to being second-guessed on my spelling by a piece of software, I also get v
-
Can't have the retrieval e-mail automaticaly.
i have the nokia 5800, v50 Impossible to update my e-mail box. It's disconnected before 1 min. and then i have to again connect, whereas the wifi still connected. I put to five minutes the retrieval time. I think it's a problem in the e-mail box prog
-
Can't boot after installing updates
I am quite new apple and this is my first problem I have encountered. I downloaded updates and now my computer wont boot. I have tried safeboot and it just freezes on the 'starting OSX bar'. I have inserted 'install disk 1' (which is OSX 10.4.6) and