OSX on G5 Trouble
I have a dual 1.8 G5 with OSX 10.3.9. Recently I have had trouble with it. Sometimes the screen gets an opaque grey come up telling me to restart the computer by the power button. When I try to turn it on it only bongs and boots up about once every six times.
I ran disk utility from the boot disk and it came up with an 'illegal name' error but then when it tried to fix it, it said:
ERROR: The underlying task reported failure on exit. (-9972)
What should I do??
Thanks
Hi adss1,
first of all: WELCOME TO THE DISCUSSIONS!
Here is the solution for your problem: Disk Utility reports "Underlying task reported failure" when repairing a volume
If this answered your question please consider granting some stars: Why reward points?
TIP: You can search the main Support page. If you enter "9972" into the search-field it will directly show the article I linked to above.
Similar Messages
-
FW8 on OSX : UNICODE FONT TROUBLE
Well ... Hi !
Can someone help me ... I'm new on MAC OSX ... but I use to
work with FW !
On this OS, FW don't want to let me write with accent :
é, à, ï ... won't appear.
If I check with popchar the font table, i see that the accent
are in the unicode tab... so I suppose that FW have some trouble
with unicode font on mac.
I've read this
technote, but i didn't
find this file...
What can i do ?
THANXI don't believe that you can type as you would with MS Word
or Illustrator and have the accented characters appear as you type.
However, you can create a text block and type with the keyboard
normally and when you require an accented character you can insert
one manually from the Special Characters panel as I mentioned in my
last reply.
One other option is to import your text from Photoshop CS2 or
Illustrator into Fireworks. See the Fireworks help menu for details
of how to do this. Text can be imported and remain editable or even
used as vector objects.
One final note; you could search for a Fieworks Extension
that may exist for creating the feature that you are after.
Nick Barling
barkingweb.com -
Since yesterday my iMac running OS 10.5 won't start up. Note that this is my first mac ever and I am totally not a tech head.
When it starts up, I get a grey screen with the Apple logo and some sort of engine running beneath it. Nothing happens.
I called applesupport but they would only help me if I signed up for this rather expensive Applecare eventhough the mac is less then one year old.
Things I have tried:
- starting up in safe mode by holding left shift key when hearing the start up sound until I see the logo... nothing happens
- Inserting the installation disc, starting up while holding option key, selecting the disc and going to the disc utility. I ran disc repair for the HD, no errors. I ran disc permissions, I get: Error: The underlying task reported failure on exit
- I tried reinstalling osx using archive and install (I actually don't know if it keeps my documents :, I don't have backups ) and here I got the same error. Installation failed.
I don't know what could have caused this problem, I did do the following: I option clicked the mac disc on the dashboard, and I got this window with beneath where permissions is there was a lock, not knowing what it does, I clicked it but could not click it to it's previous option. (don't remember what I was looking for) Could this be causing all these problems?
Anyhow, any help would be very much appreciated. I don't know anyone with a mac who can help me.Didn't work? Hrmmm, this is a tough one. I have feeling your system is intact, but something is just not letting it get past the initial boot stage. If you heard clicking noises with this, I would say perhaps you are having a HD failure.
TeleDanz wrote:
I don't know what could have caused this problem, I did do the following: I option clicked the mac disc on the dashboard, and I got this window with beneath where permissions is there was a lock, not knowing what it does, I clicked it but could not click it to it's previous option. (don't remember what I was looking for) Could this be causing all these problems?
At first I didn't think this could be the issue. I had trouble sorting out what you are saying. But at closer inspection, it could be the problem. If you locked your startup disk, then it might not be able to perform basic read/write function needed during the boot. I option-clicked on my main HD, but I don't see what you are describing. I get the lock is when I click on Get Info in that pop up menu, under ownership and permissions there is a lock next to owner and it is locked already. I don't think that would be the issue.
When you boot from the OSX DVD or another external HD, can you see your main hard drive? Can you access it at all?
Unless someone else here has an idea, I'm afraid you make need to take it in to an Apple Store. -
Mac OSX Software Update Trouble
I am trying to update my Mac's software. Right now I have Mac OSX 5.2
Everytime i go to update it, it will restart and get stuck at "configuring installation".
I was wondering if anyone could help me with this.Hello wclark03,
And welcome to Apple Discussions!
I would start with this Apple support document related to your issue.
[Mac OS X 10.5: Software Update stops responding during "Configuring installation"|http://support.apple.com/kb/ts2383]
B-rock -
When starting up, the grey screen with the apple appears for about 2 minutes, then the blue screen appears with grey box and title MAC OS X. A few files seem to load until "Login Window Starting." At this point the system is completely frozen. Spinning wheel of death spinning at this point.
Have tried running disk utilties which said "disk repaired," but no change with the start-up.
I would really appreciate any advice you can give me.
Thanks, RickYou might give this a try:
You will need to type some Unix commands. If you are not comfortable with this, I don't know of anything other than a re-install. But if you are careful, you should be OK. I recommend you print this out in a largish mono-spaced font so you don't miss any spaces (or add extra ones). Note that case is important.
Be careful. Some of these commands are dangerous, since you are going to be root.
Start up in Single-User mode by holding down the command (Apple) key and the 's' key while you press the power switch. You can let go the keys when you see white text on a black background. When this has finished you will see a prompt ending in '#', although there may be other messages. Type
*/sbin/fsck -fy*
followed by a return, at the prompt and wait a few seconds for 8-10 lines of output. If the last line says repairs were carried out, repeat this command until you get a message 'The volume <yourdiskname> appears to be OK'. Then continue with
/sbin/mount -uw /
cd /Library/Preferences
rm com.apple.loginwindow.plist
rm com.apple.windowserver.plist
cd /Library/Caches
rm -r *
cd /System/Library
rm Extensions.kextcache
cd /System/Library/Caches
rm -r *
reboot
This should now take you to a proper login screen after the normal boot sequence. You should then Repair Permissions by using Disk Utility (in your /Applications/Utilities folder). -
Trouble opening files on networked storage
In our small office we are using a Buffalo Linkstation networked hard drive to store and share files between Macs and PCs. One of our Macs in particular has trouble opening files. Either:
1. The file is invisible
2. The file doesn't open in the correct application by default (for instance, an InDesign file opening in textedit)
3. Only files created on this mac, and not on another, will open, though the files created on other macs are visible and have the same extension (but grey and without the usual icon).
Oddly, when I copy the file onto a USB stick and 'manually' bring it over, it will open fine.
The Mac in question is a Mac Mini (Power PC) running OSX 10.4.8. Other Computers on the network, which don't have the same trouble opening files are:
Mac Mini (Intel) with OSX 10.4.8 and Windows XP via Bootcamp
Power Mac G5 with OSX 19.3.9
iBook with OSX 10.4.
Dell Inspiron 5150 laptop with Windows XP
It seems like a software problem, but the Intel Mac is running the same version of OSX. The troubled Mac seems to drop its connection to the Linkstation much more often than the other computers as well, suggesting possibly a hardware problem?
iBook, PowerPC G5, Mac Mini Mac OS X (10.4.8)Could this be an issue with file names?
I've used a linkstation with macs and had huge problems copying files TO the NAS because of bad file names or file names containing illegal characters for the linkstations formatting (Fat32 or whatever).
Make sure that you have files with names up to 32 chars and not more
Make sure you exlcude characters like " [ ] / \ = + : ; " , * |" from your filename
Include a file extension (.indd for an indesign file for example) for all files.
By changing file names and adding extensions as required I have been able to store and recover files from the linkstation.
Try a test file or two. If they work, it could be that that is the problem. -
My wacom tablet does not work correctly after updating to mavericks.
My wacom doesn't work.
Jason, how did you switch back? My tablet does not work either. All I can do for the moment is work on my laptop which has the old system.
Thanks,
Teresa
I was almost certain that the new osx would be trouble as was Lion and after that Mountail Lion. So, instead of my usual hard drive clone, which I make with superduper, I made a second one just to be certain. After 10 minutes of Mavericks, I am happy back to snow leopard.
I really think that it is the most developed, glitch free operating system. If it wasn't for all these money thirsty companies stopping the support of the previous op. systems perhaps we could stop at Snow leopard. What more to ask. Even aesthetically osx 10.9 is much worse that snow leopard.
Anyway, long answer. sorry. It is a good habit to clone your HD once in a while.
p.s. my only reason for wanting to upgrade is because Lightroom stopped support but I am still doing my work with the previous versions. I guess people will allways think that if they have the newest, biggest, baddest version of a software will make them better in what they do..or in who they are, really. -
How can ANYONE be happy with this piece of junk? Seriously?
I started by importing my iPhoto library. It's 10k pictures, many if
which I could probably delete if I had a good tool like Aperture to
help me. In iPhoto I have about 50 or 60 keywords and I have applied
at least some keywords to lots of my pictures. When I try to search my
photos by keyword in iPhoto, it responds instantly, much like Apple's
spotlight technology does.
The first thing I noticed was that just bringing up the filter window
takes 60 seconds. I wish I were kidding. The other thing I noticed
was, As I am adjusting the filter, or adding new criteria like EXIF
aperture setting, the software automatically starts searching even
before I have finished specifying all the criteria. Normally I think
that wouldn't bother me, but it took 60 seconds to perform each filter
operation.
OK - so filter is slow, I'll get over it. I really wanted this app for
the image management and adjustments capabilities. So, I found an
image that had a bad exposure and I selected the exposure slider and
moved it to the right to brighten the picture. My CPU pegged for
several minutes before the slider moved one pixel and any visible
changes appeared on the screen. It shouldn't take minutes, it should
take milliseconds, like in iPhoto or Picasa or any other image
manipulation program I have ever run.
I think the problem is that it was creating a new version of the
image, and I came to discover that any operation that affects the
number of images in your "working set" can take minutes or more.
There are many other really simple operations I wanted to do which I
could not do because the application pegged the CPU for hours and made
no visible progress, and I was forced to Force Quit the
application. Here's a perfect example. I noticed that all the photos
imported from my iPhoto library were keyworded with the "iPhoto
Original" keyword. How nice I thought. Then there was another keyword
called "iPhoto Edited" which I thought was even better because what I
really wanted to do was delete all my changes made in iPhoto, go back
the original files, and then make non-destructive versions of those
changes with Aperture.
So, I created a filter to find all the images that had the "iPhoto
Edited" keyword associated with them. Turns how that those images were
already automatically stacked with the corresponding original
versions. So I decided to Unstack the images so I could delete the
"iPhoto Edited" ones. Unfortunately that operation never completed
after hours. I tried selecting just 3 of the images to unstack, and
that took 10 minutes. I tried 10 images at once and that never
completed after an hour. I had to Force Quit the application many
times.
Then somebody gave me the hint that to accomplish this task you need
to do the initial filter, create an album based on the filter results,
and then perform all your operations in that album. I gave that a
try. It took about 10 minutes to set up that album because of the
slowness of the system, but once in that album I found I was able to
unstack images much faster: still hundreds of times too slow, but
still much better. 2 hours later I had them all unstacked, and had
deleted the iPhoto Edited images.
This is the kind of pain we're talking about.
I've tried importing from iPhoto without the keywords to see if that
might be what's making it slow. It appears to be a big part of the
problem but I cannot be sure.
I tried moving my photos out of individual per-roll projects that were
created by the iPhoto import and into a single large project, to see
if that would help. No difference.
Today I ran some kernel tracing tools on Aperture when it seemed to be
quite hung or at least slow, and found a few very disturbing
things. One biggy while deleting 1000 thumbnail images that got
imported when I imported my iPhoto library one directory at a time,
was that it was rewriting the same file:
1388 Aperture CALL stat(0xf0101870,0xf0100fd0)
1388 Aperture NAMI "/Users/jonathan/Pictures/Aperture Library.aplibrary/Aperture.aplib/LatestDeleteDates.plist"
1388 Aperture RET stat 0
1388 Aperture CALL statfs(0xbfffc6e0,0xbfffc5d0)
1388 Aperture RET statfs -1 errno 2 No such file or directory
1388 Aperture RET open 14/0xe
1388 Aperture CALL write(0xe,0x1eb2fa10,0x157)
1388 Aperture GIO fd 14 wrote 343 bytes
"<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/P\
ropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>latestMasterFileDeleteDate</key>
<date>2005-12-09T01:43:58Z</date>
<key>latestMetadataDeleteDate</key>
<date>2005-12-09T01:43:58Z</date>
</dict>
</plist>
1388 Aperture RET write 343/0x157
1388 Aperture CALL fsync(0xe)
It did this thousands of times, and there are several really sad
things about this:
(1) It's the same data and the same file every time.
(2) It calls fsync(0xe) after each write.
The latter means that the program is not going to make any progress
until that data is written from the kernel's memory buffer onto the
hard drive, which could take many milliseconds depending on what
sector the heads are looking at right now! This is insane.
After the images seemed to be deleted, however, Aperture remained CPU
pegged for hours. I didn't realize it and had gone to eat dinner,
dessert, clean the dishes, get beaten badly in Othello by my 7 year
old daughter again, do her piano practice, and put her to bed. So I
kernel traced it again and discovered that it was endlessly seeking
around and then reading 1k blocks from some file, without actually
causing any physical disk I/O. In other words the entire file was
somehow in memory and Aperture was just running around in circles
reading chunks of it ... for hours, CPU pegged the whole time. I had
to "Force Quit" again.
So, I ask you, What is this program good for? As far as I can tell,
nothing works properly once you pass a certain number of images in the
library.
Here's what I think Aperture can be good for: load your new "roll" of
digital pictures into it. Hopefully fewer than 500 photos. Use all the
cool tools to group and stack, adjust the color tempurature, white
balance, sharpness, crop it, etc. Then export it to some random folder
and import than folder into iPhoto (or whatever you want to use to
manage your photo database). Then delete the photos from Aperture.
Folks, I am sorry to tell you this, but this is a program with bad
bones and it's not going to get fixed soon. I hope I can get my money
back. I've already been told that I cannot because I installed it, but
I am going to complain and make sure they at least know how bad this
is.
Believe me I wanted this to be the best program ever. I have used
Final Cut Pro and Photoshop on my mac, and those programs are two of
the very best I have ever used. They are fast, extremely good at what
they do, perform well on much lower-performing hardware (e.g., my imac
G4 with 512Mb RAM), and they are just great in every way. I told all
my friends, "My love affair with the Mac can continue despite my
disatifaction with iPhoto because they have created another Pro tool
called Aperture which looks like the best thing ever!" But those demos
were all staged with very few photos in the libraries.
Mac OS X (10.4.3)
Dual 2.5Ghz Power Mac w/3Gb RAM Mac OS X (10.4.3)I've done some research on the SQLite database. Whenever Aperture hangs up (like during auto-stack or opening the filter hud) there are thousands of SQLite queries happening. These SQLite queries cause massive file I/O because the database is stored on the disk as 1kb pages. However, the OS is caching the database file; mine's only 12MB. I'm trying to track down some performance numbers for SQLite on osx but having trouble.
It's starting to look like most of the speed problems are in the libraries that Aperture uses instead of the actual Aperture code. Of course, that doesn't completely let the developers off the hook since they choose to use them in the first place.
Oh, and if anyone is curious, the database is completely open to queries using the command line sqlite3 tool. Here's the language reference http://www.sqlite.org/lang.html
Hmm, just found this. Looks like someone else has been playing around in the db http://www.majid.info/mylos/stories/2005/12/01/apertureInternals.html
Dual 1.8 G5 Mac OS X (10.4.3) 1GB RAM, Sony Artisan Monitor, Sony HC-1 HD Camera -
Windows 7 PC's doesn't show up automatically in Finder
Windows 7 PC's doesn't show up in Finder
I know there are probably a lot of threads about this already but the ones I have read haven't helped me with my problem yet.
The problem I am facing is that my Windows 7 PC's doesn't show up automatically in Finder.
What works:
1. I can see all of the computers (Mac and Windows) on the network on my Windows machines, if I look under Network in Windows.
2. I can see my Mac computers in Finder under Shared
3. I can CMD+K connect to all of the computers on the network using SMB, both with entering the name of the computer or the IP
4. I can ping all of the IP's on the network
What doesn't work:
1. Windows 7 machines doesn't show up automatically in Finder
2. I can't ping hostnames in Network Utility, can only ping IP's - it says cannot resolve hostname
What I have tried:
1. Turned on SMB sharing on OSX
2. Edited /private/etc/hosts to include Windows PC's
3. Turned off all firewalls on Windows, OSX and Router
4. Installed Bonjour on Windows machines
5. A bunch of other things...
Theories:
1. The best theory I can come up with is that OSX is having trouble with NETBIOS and that's why the Windows computers aren't showing up in OSX but I can still see the OSX computers in Windows 7. And the reason why I can see the other Macs in OSX is that they use something other than NETBIOS to broadcast their existence on the network.
2. The Gods are against me...
It should be said that I had it work for a very short while, but then i changed something and couldn't reverse it.
I hope someone can help me find the little thing I am missing to get this thing to work.See my response in this Discussion string.
Link: [http://discussions.apple.com/thread.jspa?threadID=2644930&tstart=0] -
External Hard Drive woes (possibly Time Machine related)
Hello everyone,
I am using one of the partitions on my WD My Passport for Mac (1 TB) partitioned into two sepaprate partions (both Mac OS Extended Journaled) of 500 GB each as my backup disk for Time Machine.
Now, Time Machine seems to work fine on it for some time. However, after a period of time (~5 hours) time machine stops working. Here are the relevant logs.
2/2/12 5:35:26.221 AM com.apple.backupd: Starting standard backup
2/2/12 5:35:26.424 AM com.apple.backupd: Backing up to: /Volumes/Mridanga/Backups.backupdb
2/2/12 5:35:27.351 AM com.apple.backupd: 2.52 GB required (including padding), 243.30 GB available
2/2/12 5:35:39.920 AM com.apple.backupd: Copied 1408 files (49.3 MB) from volume Macintosh HD.
2/2/12 5:35:40.073 AM com.apple.backupd: 2.46 GB required (including padding), 243.25 GB available
2/2/12 5:35:43.099 AM com.apple.backupd: Copied 876 files (199 bytes) from volume Macintosh HD.
2/2/12 5:35:43.631 AM com.apple.backupd: Starting post-backup thinning
2/2/12 5:35:43.631 AM com.apple.backupd: No post-back up thinning needed: no expired backups exist
2/2/12 5:35:43.655 AM com.apple.backupd: Backup completed successfully.
2/2/12 6:35:26.125 AM com.apple.backupd: Starting standard backup
2/2/12 6:35:26.379 AM com.apple.backupd: Backing up to: /Volumes/Mridanga/Backups.backupdb
2/2/12 6:37:30.081 AM com.apple.backupd: Error: (-50) Creating directory 2012-02-02-063730.inProgress
2/2/12 6:37:30.081 AM com.apple.backupd: Failed to make snapshot container.
2/2/12 6:37:43.118 AM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Mridanga/Backups.backupdb/googly size:37
2/2/12 6:37:53.131 AM com.apple.backupd: Backup failed with error: 2
2/2/12 7:35:25.953 AM com.apple.backupd: Starting standard backup
2/2/12 7:35:26.129 AM com.apple.backupd: Backing up to: /Volumes/Mridanga/Backups.backupdb
2/2/12 7:35:26.190 AM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Mridanga/Backups.backupdb/googly size:37
2/2/12 7:35:26.192 AM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Mridanga/Backups.backupdb/googly size:37
2/2/12 7:35:36.207 AM com.apple.backupd: Backup failed with error: 2
2/2/12 8:35:25.847 AM com.apple.backupd: Starting standard backup
2/2/12 8:35:26.020 AM com.apple.backupd: Backing up to: /Volumes/Mridanga/Backups.backupdb
2/2/12 8:35:26.076 AM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Mridanga/Backups.backupdb/googly size:37
2/2/12 8:35:26.078 AM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Mridanga/Backups.backupdb/googly size:37
2/2/12 8:35:36.091 AM com.apple.backupd: Backup failed with error: 2
When this happens, the Hard Drive makes beeping noises (each time Time Machine tries to access it). It refuses to unmount, and Disk Utility refuses to either verify or repair the hard drive. Forcibly unplugging the hard drive and replugging it does not help either. It makes beeping noises for about half a minute and then goes quiet. However, neither is it mounted nor is it visible in the disk utility.
The only way I have managed to fix this is to plug the hard drive in another mac, where it mounts without any problem. I then run disk utility to verify the hard drive (on that mac) and then when I replug the drive to my laptop, it works. Until it breaks again.
The only other "error" related to my external hard drive that I have found in system logs is also pasted below:
2/2/12 12:50:07.161 AM com.apple.backupd: Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 "The file “objects.nib” couldn’t be opened." UserInfo=0x7f9097807460 {NSURL=file://localhost/Volumes/Mridanga/Backups.backupdb/googly/2012-02-01-222347/Macintosh%20HD/System/Library/ColorPickers/NSColorPickerWheel.colorPicker/Resources/ar.lproj/NSColorPickerWheel.nib/objects.nib, NSFilePath=/Volumes/Mridanga/Backups.backupdb/googly/2012-02-01-222347/Macintosh HD/System/Library/ColorPickers/NSColorPickerWheel.colorPicker/Resources/ar.lproj/NSColorPickerWheel.nib/objects.nib, NSUnderlyingError=0x7f9097833650 "The operation couldn’t be completed. Not a directory"}
2/2/12 12:50:07.289 AM com.apple.backupd: Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 "The file “objects.nib” couldn’t be opened." UserInfo=0x7f9097096050 {NSURL=file://localhost/Volumes/Mridanga/Backups.backupdb/googly/2012-02-01-222347/Macintosh%20HD/System/Library/ColorPickers/NSColorPickerWheel.colorPicker/Resources/hu.lproj/NSColorPickerWheel.nib/objects.nib, NSFilePath=/Volumes/Mridanga/Backups.backupdb/googly/2012-02-01-222347/Macintosh HD/System/Library/ColorPickers/NSColorPickerWheel.colorPicker/Resources/hu.lproj/NSColorPickerWheel.nib/objects.nib, NSUnderlyingError=0x7f9097095f40 "The operation couldn’t be completed. Not a directory"}
2/2/12 12:50:07.294 AM com.apple.backupd: Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 "The file “objects.nib” couldn’t be opened." UserInfo=0x7f9097359940 {NSURL=file://localhost/Volumes/Mridanga/Backups.backupdb/googly/2012-02-01-222347/Macintosh%20HD/System/Library/ColorPickers/NSColorPickerWheel.colorPicker/Resources/ko.lproj/NSColorPickerWheel.nib/objects.nib, NSFilePath=/Volumes/Mridanga/Backups.backupdb/googly/2012-02-01-222347/Macintosh HD/System/Library/ColorPickers/NSColorPickerWheel.colorPicker/Resources/ko.lproj/NSColorPickerWheel.nib/objects.nib, NSUnderlyingError=0x7f90973598e0 "The operation couldn’t be completed. Not a directory"}
2/2/12 12:50:07.313 AM com.apple.backupd: Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 "The file “objects.nib” couldn’t be opened." UserInfo=0x7f909772fc90 {NSURL=file://localhost/Volumes/Mridanga/Backups.backupdb/googly/2012-02-01-222347/Macintosh%20HD/System/Library/ColorPickers/NSColorPickerWheel.colorPicker/Resources/sv.lproj/NSColorPickerWheel.nib/objects.nib, NSFilePath=/Volumes/Mridanga/Backups.backupdb/googly/2012-02-01-222347/Macintosh HD/System/Library/ColorPickers/NSColorPickerWheel.colorPicker/Resources/sv.lproj/NSColorPickerWheel.nib/objects.nib, NSUnderlyingError=0x7f909772bcc0 "The operation couldn’t be completed. Not a directory"}
2/2/12 12:50:07.326 AM com.apple.backupd: Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 "The file “objects.nib” couldn’t be opened." UserInfo=0x7f909709b6f0 {NSURL=file://localhost/Volumes/Mridanga/Backups.backupdb/googly/2012-02-01-222347/Macintosh%20HD/System/Library/ColorPickers/NSColorPickerWheel.colorPicker/Resources/zh_CN.lproj/NSColorPickerWheel.nib/objects.nib, NSFilePath=/Volumes/Mridanga/Backups.backupdb/googly/2012-02-01-222347/Macintosh HD/System/Library/ColorPickers/NSColorPickerWheel.colorPicker/Resources/zh_CN.lproj/NSColorPickerWheel.nib/objects.nib, NSUnderlyingError=0x7f9097095e30 "The operation couldn’t be completed. Not a directory"}
I don't know what the problem is, but I would like to be able to use an external. I also have another external plugged in my computer (NTFS, and I have NTFS write enabled via http://www.paragon-software.com/home/ntfs-mac/) and that hard drive works perfectly. Also, the problem was there before I enabled NTFS write so nothing was harmed in enabling NTFS write.
System Info
OS X 10.7.3 (problem existed with 10.7.2) as well
RAM: 8 GB
Macbook Pro 15" (i7 2.2 GHz, 2011 model)OSX is having trouble reading or writing to the drive. That's usually hardware (the drive, port, or cable).
Try different ports, cables, and combinations of the two (a plug that works fine in one port may not make good contact in a different one).
Be sure it's connected directly to your Mac -- no hubs or daisy chains, and not a port on your keyboard.
Also, what Partition Map Scheme does the drive have? (Check via Disk Utility - select the top line for the drive -- it should show at the lower right.) -
Can't get EPSON nx300 to work with airport express
hey yall
i'm running a 3 year old white 13" macbook with 10.5.7 osx installed -~- having trouble getting things to print via my new airport express. my boyfriend has no troubles with his brand new macbook pro - it just worked instantly for him.
my computer is able to recognize the printer in a 'Bonjour' location when i add the printer, but when i go to print, it just opens an empty print queuueueue and nothing happens.
i tried installing the latest EPSON drivers to no avail, so i deleted all of them, which also didn't help.
eep
kevinWelcome to the discussions!
Don't have an exact answer because I can't replicate the problem, but will offer a guess for what it's worth.
You are running Leopard 10.5.7 on your computer and the MacBook Pro might be running 10.6.x Snow Leopard, which may have updated printer drivers for the USB port on the AirPort Express.
Try updating 10.5.7 first by clicking the Apple icon at the upper left of your screen and then clicking Software Update. This may allow you to move to 10.5.8, which did offer a number of printer updates.
Then work your way through the Apple Printer Troubleshooting Guide to see if that might help allow printing to occur. -
I am running firefox4 on win XP. When I start firefox, it says it is trying to restore a previous session which has only the blank tab. After about 10 seconds the whole instance of firefox freezes - none of the buttons work and the only way to close firefox is to use the Ctrl+Alt+Del and task manager. If I open a second parallel sessionof firefox, it works normally, as long as the first session is left alone (frozen). What could be causing the freeze up of the first firefox instance, and how can it be prevented?
I've done some research on the SQLite database. Whenever Aperture hangs up (like during auto-stack or opening the filter hud) there are thousands of SQLite queries happening. These SQLite queries cause massive file I/O because the database is stored on the disk as 1kb pages. However, the OS is caching the database file; mine's only 12MB. I'm trying to track down some performance numbers for SQLite on osx but having trouble.
It's starting to look like most of the speed problems are in the libraries that Aperture uses instead of the actual Aperture code. Of course, that doesn't completely let the developers off the hook since they choose to use them in the first place.
Oh, and if anyone is curious, the database is completely open to queries using the command line sqlite3 tool. Here's the language reference http://www.sqlite.org/lang.html
Hmm, just found this. Looks like someone else has been playing around in the db http://www.majid.info/mylos/stories/2005/12/01/apertureInternals.html
Dual 1.8 G5 Mac OS X (10.4.3) 1GB RAM, Sony Artisan Monitor, Sony HC-1 HD Camera -
Time Machine freezes/stalls now that I have a new external HD
I have been using a LaCie HD for years to back up my computer with Time Machine. All has been fine. I have an iMac/OS 10.5.8. But a few months ago, I got an EZQ 1 TB external HD to store my video. The Time Machine is still set to store my backup on the LaCie. But now, every so often, Time Machine will freeze up and stall while trying to back things up. I can't force quit anything, so I need to do a hard restart of the computer. It takes forever to reboot, and when it does, it can't find my EZQ HD. What's going on? Thanks for the info.
Kyrak21 wrote:
Thanks for the suggestions. I tried all of them, but I'm still having problems. Could the new hard drive be messing up Time Machine, even though they are not connected?
Possibly, directly or indirectly.
Is Time Machine backing-up anything on the EZQ drive? If so, exclude it for a while and see if the problems stop.
How are these drives connected to your Mac? If they're not on separate ports, try that if at all possible, at least temporarily. If a hub or daisy-chaining is involved, try connecting directly if at all possible. Those should narrow down the possibilities.
If not, it's possible that OSX is having trouble with the EZQ, slowing things down, but not too badly until Time Machine also needs some resources. What happens if you eject and disconnect it -- do the problems stop?
Another way to see what's happening is to watch your CPU usage via the +Activity Monitor+ app (in your Applications/Utilities folder). When it starts, select either +All Processes+ or +Active Processes+ in the toolbar, and sort the list by the +% CPU+ column, so the highest numbers are on top, and select the CPU tab towards the bottom. For this purpose, also select +View > Update Frequency > Less Often+ or Normal from the Menubar.
Various processes will "spike" up and down normally as they do things, then are idle, so you need to watch it for a while and get a feel for the processes that are using the most CPU, and the +% Idle+ at the bottom.
Let it run; try to keep at least the first few lines visible at all times, so you'll be able to see them when your Mac slows down or freezes. When that happens, see what process(es) are using the most CPU.
If the process(es) involved aren't familiar to you, post their names here (and or check this out: http://triviaware.com/macprocess/all) -
I'm using safari on mac osx and having trouble updating to the latest version of flash.
i'm able to get up to the stage of entering in my computer password, then nothing happens after that. No prompts, nothing. I've tried this several times over, and restarting my computer. My settings allow for flash player to work.
Help please?!?!How to perform a "clean install" of Flash Player in Mac OS X
-
Since 2012 I have Photoshop Elements always worked without any problem, however now the language is suddenly German how can this be changed, removed the program and re-installed, not working. Program is downloaded and updated via the apple app store?
I've done some research on the SQLite database. Whenever Aperture hangs up (like during auto-stack or opening the filter hud) there are thousands of SQLite queries happening. These SQLite queries cause massive file I/O because the database is stored on the disk as 1kb pages. However, the OS is caching the database file; mine's only 12MB. I'm trying to track down some performance numbers for SQLite on osx but having trouble.
It's starting to look like most of the speed problems are in the libraries that Aperture uses instead of the actual Aperture code. Of course, that doesn't completely let the developers off the hook since they choose to use them in the first place.
Oh, and if anyone is curious, the database is completely open to queries using the command line sqlite3 tool. Here's the language reference http://www.sqlite.org/lang.html
Hmm, just found this. Looks like someone else has been playing around in the db http://www.majid.info/mylos/stories/2005/12/01/apertureInternals.html
Dual 1.8 G5 Mac OS X (10.4.3) 1GB RAM, Sony Artisan Monitor, Sony HC-1 HD Camera
Maybe you are looking for
-
Problem with Time Machine back up
Hello all, Grateful for anyone's help with this issue. Firstly, a summary of specs: Mac OS X 10.7. Late 2007 Macbook 13inch External hard drive - LaCie 1TB D2 Quaddra Issue - When trying to back up my 2007 Macbook it fails! When I back up my 2011 Mac
-
Where Can I Buy a 2011 Mac Mini Replacement Fan?
Broke the cable on my fan during a hard drive replacement. Anyone know where I can buy a replacement?
-
Adding DVD File to Library - File Name Changes
When I add a DVD file name to my library, iTunes changes the name of the file. How do I retain the name of the file that is in my iTunes sub-directory?
-
error 1015 occuring during ugrade threw itune
-
Hi Friends, Can i get code for creating object for outgoingpayments and entries for that. Regards, Susan