Firewire port failure/ tried all remedies
Hey Guys,
The problem I'm having is in regards to connecting a G-Drive Mini to my Firewire 800 port. My main question is can my firewire port be "fried" and still provide my drive with power? The drive will connect Via USB successfully.
The solutions/remedies I've tried are:
Reset Pram
Reset SMC
Reinstalled Combo Update for 10.6.8
Booted off install disk and opened disk utility to see if drive would mount
AHT Extended Test resulting in no problems found
Used an external power supply to power G-drive when plugged into Firewire 800 port. (1 amp power supply)
Drive was successfully mounted on a Mac pro using the same firewire cable.
Formated/added files onto drive using USB
Reset Firewire port by unplug power and shutdown for 15 minutes
Symptoms occuring are:
Drive is getting power from Firewire port.
Can connect via USB to the drive.
Will not mount of be recognized in disk utility or firewire section in system profiler (only information under firewire tab is the Max speed limitation of 800mb/s)
My Macbook Pro:
Macbook Pro 7,1 (Mid-2010)
Intel Core Duo 2
Running Snow Leopard 10.6.8
2.66ghz
8Gb-Ram
My External Hard-drive:
G-Technology
G-Drive Mini
1Tb
Any thoughts, suggestions, or questions are greatly.
P.s. I sadly don't have another firewire device to test on the port but this device is indeed working properly because I tested it on a Mac Pro with the same cable.
Is it possible for my port to be fried and AHT report no problems?
I'm considering updating mac to Mountain Lion or Mavericks to see if problem persists (Last Resort) Bootup off install disk should have disproved this theory?
Take it in to an Apple Genius, the diagnosis is almost always free, they have much more sophisticated testing. AHT may not tell you about issues that deep. (make an appointment for the genius bar)
http://www.apple.com/retail/storelist/
https://getsupport.apple.com/GetproductgroupList.action?caller=saso&category_id= SC0997&locale=en_US&SG=SG001
Similar Messages
-
MacBook Pro: Unable to Empty Trash (secure or otherwise). Have tried all remedies suggested on Apple's site. I think "Secure Empty Trash" bogs at the first file "iPhone4, 1_8.02_12A495_Restore.ipsw" at 1.78 GB size and goes no further. When I try to move it out of Trash to a temporary location so I can empty remainder of Trash, I get the message "Some of the items you are moving are in use by another application. Moving the items can cause problems with the application using them. Are you sure you want to move these items?" at which point I select "Stop" to avoid possible disaster. Can you help? Thanks.
01/05/15 6:01:27.000 pm kernel[0]: Previous shutdown cause: -62
That usually indicates an abnormal shutdown due to a hardware fault. The exact cause can only be determined by Apple, so schedule a Genius Bar Reservation. -
Full Firewire Port Failure (three different machines : iMac Intel, iMac G5, Black Macbook)
I'm experiencing a failure of all FireWire ports on all of my three machines. I believe this problem began with a faulty external, FireWire powered hard drive from G-Tech. Here are all my specs, followed by a rundown of the order of events that has lead to this situation, followed by the various troubleshooting I have done.
Equipment :
iMac Aluminum Intel - 24" Mid 2007 - running OsX 10.5.8 - currently 1 FW400 and 1 FW800 ports disabled
iMac G5 - 20" - running OsX 10.5.8 - currently 2 FW400 ports disabled
MacBook - 13" black Early 2008 - running OsX 10.5.8 - currently 1 FW400 port disabled
2 500GB G-Drives (by G-Tech) - AC powered
1 5TB G-RAID Drive (by G-Tech) - AC powered
1 250GB G-Drive Mini (by G-Tech) - FW powered
Initial Setup :
1 500GB G-Drive connected directly to iMac Intel via FW800
1 500GB G-Drive connected to first 500GB G-Drive via FW800 (daisy chained)
1 250GB G-Drive connected to second 500GB G-Drive via FW400 (daisy chained)
1 5TB G-RAID connected directly to iMac Intel via FW800>400 adapter
Sequence of Events :
I had transferred some files to my G-Drive Mini in order to move them to my MacBook from my iMac Intel. I copied the files to the G-Drive Mini and ejected it normally and plugged it into my MacBook via FW400. The drive would not mount, and the power indication light would not go on. After experimenting with various connections and cables I was able to get the drive to power with FW400 and USB connected at the same time, but the drive would still not mount.
I then plugged the G-Drive Mini back into the 2nd 500GB G-Drive as it was previously connected via FW400. This action caused the G-Drive to immediately reboot and eject itself from my iMac Intel.
I then attempted to plug the G-Drive Mini into my older iMac G5 via FW400. Immediately upon plugging in, the computer shut down, and would not restart.
At this point I kind of started to freak out. I was unaware of the extent of the damage, but was upset that the FW powered G-Drive Mini had shutdown my iMac G5. I contacted G-Tech Support and they offered to replace the drive and instructed me how to manually reset the computer's SMC by opening up the iMac and finding the Cuda switch. This worked and the computer was able to start and function again, but the FW400 port seemed to be disabled.
I then tried to swap out configurations and drives on my iMac Intel to see if there was any cable problems, but doing so, slowly rendered all my FireWire ports useless. It's almost as if the act of plugging in the FW-powered G-Drive Mini started a kind of shortout chain reaction. I soon learned that none of my hard drives would connect to any of my three machines, with any kind of cable combination via FW400 or 800.
I am currently able to connect my 5TB G-RAID drive to any machine via USB, as well as my G-Drive Mini. I am unable to access the other two external hard drives, as one has only FW400 and 800 ports and the other's USB connection is not functional as well on any machine.
Troubleshooting Steps Taken :
I have on all machines, reset the SMC in the following methods. iMac G5 - manually, by opening the case and pressing Cuda switch. iMac Intel - unplug, hold power button, restart method. MacBook - unplug, hold power button, restart method.
I have also on all machines, reset the PRAM by the Cmnd + Opt + P + R method at startup.
I have also unplugged all cables / removed battery, from all machines and left alone for a period of at least 12 hours, then re-plugged in each device one at a time.
I have also restored my hibernate mode (through Terminal) on my iMac Intel to mode 3 and also turned on Virtual Memory in system preferences and set hibernatemode to mode 7, the restarted and attempted to plug in devices. The reason I even began to deal with the hibernate mode was because I had around the same time my ports began malfunctioning, installed the DeepSleep widget, which allows you to control your computer's hibernate mode. I thought that tweaking with this setting may have made my computer incapable of recognizing devices that were plugged in. I have since uninstalled the widget and experimented with different hibernatemodes to no avail.
I also have Repaired Disk Permissions and Repaired Disk on all my machines, from within my Admin User as well as from the OsX Install Disk.
Sometimes in my System Profiler (like right now for example on my iMac Intel) my computer is "Unable to list FireWire devices," but sometimes, no warning message comes up and it simply displays the appropriate Bus speed.
I also conducted a system restore using a backup from my 5TB G-Raid Drive via USB, to a date before these problems started, but my ports are still not working.
Summary :
I am looking at a situation where all my FW ports on all my computers appear to be disabled, and possibly also on my four external hard drives, with one possible USB port malfunction on one external drive. The only root of this seems to be a malfunctioning FW-powered external hard drive.
Is this possible? Has this happened to anyone else before? G-Tech assures me that it is impossible for my 250GB G-Drive Mini to draw enough power from a computer to permanently disable any ports, but I have tried all of the FW port problem troubleshooting steps and am at a loss.
I do not have AppleCare and would like to avoid bringing two iMacs, a MacBook and four hard drives to the Apple store and take my chances with the geniuses.
I would appreciate any help or advice you all have. Thanks for reading and for your support!Ok. So if that was too confusing, I've re-labeled this post with letters for my hard drives and some mapping of the connectivity configurations I have attempted.
Equipment :
iMac Aluminum Intel - 24" Mid 2007 - running OsX 10.5.8 - currently 1 FW400 and 1 FW800 ports disabled
iMac G5 - 20" - running OsX 10.5.8 - currently 2 FW400 ports disabled
MacBook - 13" black Early 2008 - running OsX 10.5.8 - currently 1 FW400 port disabled
1 500GB G-Drive (by G-Tech) w/ no USB port - AC powered : A
1 500GB G-Drive (by G-Tech) w/ USB port - AC powered : B
1 5TB G-RAID Drive (by G-Tech) - AC powered : C
1 250GB G-Drive Mini (by G-Tech) - FW powered : D
Initial Setup :
C > FW400-800 adapter > iMac Intel
D > FW400 > A > FW800 > B > FW800 > iMac Intel
Sequence of Events :
D > FW400 > MacBook
I had transferred some files to my G-Drive Mini D in order to move them to my MacBook from my iMac Intel. I copied the files to the G-Drive Mini D and ejected it normally and plugged it into my MacBook via FW400. The drive would not mount, and the power indication light would not go on. After experimenting with various connections and cables I was able to get the drive to power with FW400 and USB connected at the same time, but the drive would still not mount.
D > FW400 > A > FW800 > B > FW800 > iMac Intel
I then plugged the G-Drive Mini D back into the 2nd 500GB G-Drive A as it was previously connected via FW400. This action caused the G-Drive to immediately reboot and eject itself from my iMac Intel.
D > FW400 > iMac G5
I then attempted to plug the G-Drive Mini into my older iMac G5 via FW400. Immediately upon plugging in, the computer shut down, and would not restart.
At this point I kind of started to freak out. I was unaware of the extent of the damage, but was upset that the FW powered G-Drive Mini D had shutdown my iMac G5. I contacted G-Tech Support and they offered to replace the drive and instructed me how to manually reset the computer's SMC by opening up the iMac and finding the Cuda switch. This worked and the computer was able to start and function again, but the FW400 port seemed to be disabled.
I then tried to swap out configurations and drives on my iMac Intel to see if there was any cable problems, but doing so, slowly rendered all my FireWire ports useless. It's almost as if the act of plugging in the FW-powered G-Drive Mini D started a kind of shortout chain reaction. I soon learned that none of my hard drives would connect to any of my three machines, with any kind of cable combination via FW400 or 800.
D > USB > AnyMachine
C > USB > AnyMachine
I am currently able to connect my 5TB G-RAID C drive to any machine via USB, as well as my G-Drive Mini D. I am unable to access the other two external hard drives, as one has only FW400 and 800 ports (A) and the other's USB connection is not functional as well on any machine (B).
Troubleshooting Steps Taken :
I have on all machines, reset the SMC in the following methods. iMac G5 - manually, by opening the case and pressing Cuda switch. iMac Intel - unplug, hold power button, restart method. MacBook - unplug, hold power button, restart method.
I have also on all machines, reset the PRAM by the Cmnd + Opt + P + R method at startup.
I have also unplugged all cables / removed battery, from all machines and left alone for a period of at least 12 hours, then re-plugged in each device one at a time.
I have also restored my hibernate mode (through Terminal) on my iMac Intel to mode 3 and also turned on Virtual Memory in system preferences and set hibernatemode to mode 7, the restarted and attempted to plug in devices. The reason I even began to deal with the hibernate mode was because I had around the same time my ports began malfunctioning, installed the DeepSleep widget, which allows you to control your computer's hibernate mode. I thought that tweaking with this setting may have made my computer incapable of recognizing devices that were plugged in. I have since uninstalled the widget and experimented with different hibernatemodes to no avail.
I also have Repaired Disk Permissions and Repaired Disk on all my machines, from within my Admin User as well as from the OsX Install Disk.
Sometimes in my System Profiler (like right now for example on my iMac Intel) my computer is "Unable to list FireWire devices," but sometimes, no warning message comes up and it simply displays the appropriate Bus speed.
I also conducted a system restore using a backup from my 5TB G-Raid Drive C via USB, to a date before these problems started, but my ports are still not working.
Summary :
I am looking at a situation where all my FW ports on all my computers appear to be disabled, and possibly also on my four external hard drives (A, B, C, D), with one possible USB port malfunction on one external drive (B). The only root of this seems to be a malfunctioning FW-powered external hard drive.
Is this possible? Has this happened to anyone else before? G-Tech assures me that it is impossible for my 250GB G-Drive Mini D to draw enough power from a computer to permanently disable any ports, but I have tried all of the FW port problem troubleshooting steps and am at a loss.
I do not have AppleCare and would like to avoid bringing two iMacs, a MacBook and four hard drives to the Apple store and take my chances with the geniuses.
I would appreciate any help or advice you all have. Thanks for reading and for your support! -
Firewire Port Failure Diagnosis?
I moved a number of harddrives around the desk. I realized when I finished that I had completely forgotten to power down the iMac and Firewire drives. When I got them where I wanted them I reconnected the Firewire 800 cable to oneexternal drive and then the Firewire 800 cable to the other drive in a daisy chain, like I've always had. My iMac refuses to ackowledge either Firewire 800 hard drive. The drives have power, I've re-switched the cabling and the ports around, but no success. I'm fairly good at running down broken cables, disconnected cables, etc..
My fear at this point, based on my testing, is that the Firewire 800 Port on the back of my iMac may have failed. I'm running Mountain Lion 10.8.2, and I no longer am aware of how to diagnose an iMac Firewire 800 Port failure. We don't seem to have the Extended Apple Hardware Test in Mountain Lion, like we used to on our earlier Original disks. If that even would been of any use in this case.
How do I proceed???
ThanksWell, I'm still very interested in whether we have access to the Extended AHT in Mountain Lion. In the meantime though I thought about the situation and came up with one useful test. The external hard drives are multi- connection drives and so also offer USB2 ports. I hooked up the two external hard drives to the USB ports on the back of my iMac and the drives were fully recognized and accessible. I believe I now have a burned out Firewire 800 port on my iMac, due to my own mistake, Ouch. We live and we learn...
RM -
I continue to receive "Firefox unable to update error". Have tried all remedies suggested.
I have tried all suggestions listed on your support site to correct this issue. Even after receiving the "something is causing Firefox not to be updated" message, I check the current version of Firefox and it says it is up-to-date. I have also uninstalled Firefox and reinstalled it with the same results. Please help. Thanks.
Make sure that your firewall isn't blocking the updater process.
It is possible that your security software (firewall, anti-virus) blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.
Remove all rules for Firefox and the plugin-container from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process and the updater process.
See:
*https://support.mozilla.org/kb/Server+not+found
*https://support.mozilla.org/kb/Firewalls
*https://support.mozilla.org/kb/fix-problems-connecting-websites-after-updating -
My crash reports show low memeory for most of them, but the phone is crashing even with no background apps running. I could be replying/reading a text message and it will turn to a black screen then return to homescreen. It does this no matter what app I'm running. All this started after the upgrade (I have an iPhone 4) and I'm having problems with the appletv as well since I upgraded that too.
Here's one of the crash reports I got on the phone:
Incident Identifier: 91807741-CB3C-4AD0-A017-6F44CCCA63A2
CrashReporter Key: de7ca28cabf109df3fd3771a006faa5067233be9
Hardware Model: iPhone3,1
Process: MobileMail [2678]
Path: /Applications/MobileMail.app/MobileMail
Identifier: MobileMail
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2013-02-07 22:26:10.694 -0500
OS Version: iOS 6.1 (10B144)
Report Version: 104
Exception Type: 00000020
Exception Codes: 0x000000001baddea1
Highlighted Thread: 7
Application Specific Information:
Exception raised during monitored invocation of run, exception: <_MFNewcastleAuthenticator: 0x1c5d0710> claimed to support initial response data, and didn't supply an initial response
Stack:
0x325f22a3
0x3a28c97f
0x325f215d
0x32ec7ab7
0x3681633b
0x368e2bf9
0x36811c41
0x36837847
0x36837f91
0x368321e7
0x3682ae1b
0x36880a21
0x57567
0x325f59c4
0x3254cfeb
0x368788c1
0x36878601
0x32f08e85
0x3a6e3311
0x3a6e31d8
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0:
0 libsystem_kernel.dylib 0x3a779eb4 0x3a779000 + 3764
1 libsystem_kernel.dylib 0x3a77a048 0x3a779000 + 4168
2 CoreFoundation 0x325c7040 0x32530000 + 618560
3 CoreFoundation 0x325c5d5a 0x32530000 + 613722
4 CoreFoundation 0x32538eb8 0x32530000 + 36536
5 CoreFoundation 0x32538d44 0x32530000 + 36164
6 GraphicsServices 0x360fa2e6 0x360f5000 + 21222
7 UIKit 0x3444e2fc 0x343f7000 + 357116
8 MobileMail 0x00035ea6 0x33000 + 11942
9 libdyld.dylib 0x3a6c3b1c 0x3a6c2000 + 6940
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0 libsystem_kernel.dylib 0x3a77a648 0x3a779000 + 5704
1 libdispatch.dylib 0x3a6b34ec 0x3a6a2000 + 70892
2 libdispatch.dylib 0x3a6a5df4 0x3a6a2000 + 15860
Thread 2:
0 libsystem_kernel.dylib 0x3a78ad98 0x3a779000 + 73112
1 libsystem_c.dylib 0x3a6d8cf6 0x3a6d2000 + 27894
2 libsystem_c.dylib 0x3a6d8a12 0x3a6d2000 + 27154
3 libsystem_c.dylib 0x3a6d88a0 0x3a6d2000 + 26784
Thread 3 name: WebThread
Thread 3:
0 libsystem_kernel.dylib 0x3a779eb4 0x3a779000 + 3764
1 libsystem_kernel.dylib 0x3a77a048 0x3a779000 + 4168
2 CoreFoundation 0x325c7040 0x32530000 + 618560
3 CoreFoundation 0x325c5d9e 0x32530000 + 613790
4 CoreFoundation 0x32538eb8 0x32530000 + 36536
5 CoreFoundation 0x32538d44 0x32530000 + 36164
6 WebCore 0x3852d500 0x38523000 + 42240
7 libsystem_c.dylib 0x3a6e330e 0x3a6d2000 + 70414
8 libsystem_c.dylib 0x3a6e31d4 0x3a6d2000 + 70100
Thread 4:
0 libsystem_kernel.dylib 0x3a78ad98 0x3a779000 + 73112
1 libsystem_c.dylib 0x3a6d8cf6 0x3a6d2000 + 27894
2 libsystem_c.dylib 0x3a6d8a12 0x3a6d2000 + 27154
3 libsystem_c.dylib 0x3a6d88a0 0x3a6d2000 + 26784
Thread 5:
0 libsystem_kernel.dylib 0x3a78ad98 0x3a779000 + 73112
1 libsystem_c.dylib 0x3a6d8cf6 0x3a6d2000 + 27894
2 libsystem_c.dylib 0x3a6d8a12 0x3a6d2000 + 27154
3 libsystem_c.dylib 0x3a6d88a0 0x3a6d2000 + 26784
Thread 6:
0 libsystem_kernel.dylib 0x3a779eb4 0x3a779000 + 3764
1 libsystem_kernel.dylib 0x3a77a048 0x3a779000 + 4168
2 CoreFoundation 0x325c7040 0x32530000 + 618560
3 CoreFoundation 0x325c5d9e 0x32530000 + 613790
4 CoreFoundation 0x32538eb8 0x32530000 + 36536
5 CoreFoundation 0x32538d44 0x32530000 + 36164
6 Foundation 0x32e5bf92 0x32e58000 + 16274
7 Foundation 0x32eff860 0x32e58000 + 686176
8 Message 0x3686f69c 0x36869000 + 26268
9 libsystem_c.dylib 0x3a6e330e 0x3a6d2000 + 70414
10 libsystem_c.dylib 0x3a6e31d4 0x3a6d2000 + 70100
Thread 7:
0 libsystem_kernel.dylib 0x3a779eb4 0x3a779000 + 3764
1 libsystem_kernel.dylib 0x3a77a048 0x3a779000 + 4168
2 CoreFoundation 0x325c7040 0x32530000 + 618560
3 CoreFoundation 0x325c5d9e 0x32530000 + 613790
4 CoreFoundation 0x32538eb8 0x32530000 + 36536
5 CoreFoundation 0x32538d44 0x32530000 + 36164
6 Foundation 0x32e5bf92 0x32e58000 + 16274
7 Foundation 0x32eff860 0x32e58000 + 686176
8 DAEAS 0x3583e938 0x3583d000 + 6456
9 Foundation 0x32f08e80 0x32e58000 + 724608
10 libsystem_c.dylib 0x3a6e330e 0x3a6d2000 + 70414
11 libsystem_c.dylib 0x3a6e31d4 0x3a6d2000 + 70100
Thread 8:
0 libsystem_kernel.dylib 0x3a78ad98 0x3a779000 + 73112
1 libsystem_c.dylib 0x3a6d8cf6 0x3a6d2000 + 27894
2 libsystem_c.dylib 0x3a6d8a12 0x3a6d2000 + 27154
3 libsystem_c.dylib 0x3a6d88a0 0x3a6d2000 + 26784
Thread 9:
0 libsystem_kernel.dylib 0x3a779eb4 0x3a779000 + 3764
1 libsystem_kernel.dylib 0x3a77a048 0x3a779000 + 4168
2 CrashReporterSupport 0x3572d424 0x3572c000 + 5156
3 CrashReporterSupport 0x3572d8b4 0x3572c000 + 6324
4 Message 0x36878b4c 0x36869000 + 64332
5 Message 0x368785fc 0x36869000 + 62972
6 Foundation 0x32f08e80 0x32e58000 + 724608
7 libsystem_c.dylib 0x3a6e330e 0x3a6d2000 + 70414
8 libsystem_c.dylib 0x3a6e31d4 0x3a6d2000 + 70100
Thread 10:
0 libsystem_kernel.dylib 0x3a779eb4 0x3a779000 + 3764
1 libsystem_kernel.dylib 0x3a77a048 0x3a779000 + 4168
2 CoreFoundation 0x325c7040 0x32530000 + 618560
3 CoreFoundation 0x325c5d9e 0x32530000 + 613790
4 CoreFoundation 0x32538eb8 0x32530000 + 36536
5 CoreFoundation 0x32538d44 0x32530000 + 36164
6 Foundation 0x32e5bf92 0x32e58000 + 16274
7 Foundation 0x32eff860 0x32e58000 + 686176
8 Foundation 0x32f08e80 0x32e58000 + 724608
9 libsystem_c.dylib 0x3a6e330e 0x3a6d2000 + 70414
10 libsystem_c.dylib 0x3a6e31d4 0x3a6d2000 + 70100
Thread 11 name: com.apple.CFSocket.private
Thread 11:
0 libsystem_kernel.dylib 0x3a78a594 0x3a779000 + 71060
1 CoreFoundation 0x325cb1f2 0x32530000 + 635378
2 libsystem_c.dylib 0x3a6e330e 0x3a6d2000 + 70414
3 libsystem_c.dylib 0x3a6e31d4 0x3a6d2000 + 70100
Thread 12 name: com.apple.NSURLConnectionLoader
Thread 12:
0 libsystem_kernel.dylib 0x3a779eb4 0x3a779000 + 3764
1 libsystem_kernel.dylib 0x3a77a048 0x3a779000 + 4168
2 CoreFoundation 0x325c7040 0x32530000 + 618560
3 CoreFoundation 0x325c5d9e 0x32530000 + 613790
4 CoreFoundation 0x32538eb8 0x32530000 + 36536
5 CoreFoundation 0x32538d44 0x32530000 + 36164
6 Foundation 0x32e853d0 0x32e58000 + 185296
7 Foundation 0x32f08e80 0x32e58000 + 724608
8 libsystem_c.dylib 0x3a6e330e 0x3a6d2000 + 70414
9 libsystem_c.dylib 0x3a6e31d4 0x3a6d2000 + 70100
Thread 13:
0 libsystem_kernel.dylib 0x3a78ad98 0x3a779000 + 73112
1 libsystem_c.dylib 0x3a6d8cf6 0x3a6d2000 + 27894
2 libsystem_c.dylib 0x3a6d8a12 0x3a6d2000 + 27154
3 libsystem_c.dylib 0x3a6d88a0 0x3a6d2000 + 26784
Unknown thread crashed with unknown flavor: 5, state_count: 1
Binary Images:
0x33000 - 0x12dfff +MobileMail armv7 <e07ca7a7280736c7bf301451f89d1c02> /Applications/MobileMail.app/MobileMail
0x2fe19000 - 0x2fe39fff dyld armv7 <454baf45f9a831aa88e1ea4447c58d4e> /usr/lib/dyld
0x31713000 - 0x317f9fff AVFoundation armv7 <320761e836883aeabf3cb5c53edb636d> /System/Library/Frameworks/AVFoundation.framework/AVFoundation
0x317fa000 - 0x317fafff Accelerate armv7 <b68ff92e404931f3bcb6361720f77724> /System/Library/Frameworks/Accelerate.framework/Accelerate
0x317fb000 - 0x31939fff vImage armv7 <30522b92940d3dd184c8e46780594048> /System/Library/Frameworks/Accelerate.framework/Frameworks/vImage.framework/vIm age
0x3193a000 - 0x31a1dfff libBLAS.dylib armv7 <d8edada1cea133458ca779e34a3a7f88> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/lib BLAS.dylib
0x31a1e000 - 0x31cd3fff libLAPACK.dylib armv7 <9e08aead79d13043bab622402a270fba> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/lib LAPACK.dylib
0x31cd4000 - 0x31d2dfff libvDSP.dylib armv7 <09e2a5e3e9203950890ba57592523132> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/lib vDSP.dylib
0x31d2e000 - 0x31d3ffff libvMisc.dylib armv7 <7b7d4ccc9f2b364cb0da4251e745545d> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/lib vMisc.dylib
0x31d40000 - 0x31d40fff vecLib armv7 <a7751c047dcc35ba8885212e1938b93f> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/vec Lib
0x31d41000 - 0x31d52fff Accounts armv7 <ea2de358b6cc3baab27d6ab809c31e39> /System/Library/Frameworks/Accounts.framework/Accounts
0x31d54000 - 0x31db8fff AddressBook armv7 <8cfae84dc66d3c1f9d17335c53c3d7b7> /System/Library/Frameworks/AddressBook.framework/AddressBook
0x31db9000 - 0x31e73fff AddressBookUI armv7 <0017d0a0c2593522acaaa0eee41775e4> /System/Library/Frameworks/AddressBookUI.framework/AddressBookUI
0x31fbe000 - 0x32246fff AudioToolbox armv7 <bb11489c87e93a3b8c26aa995a2fdec9> /System/Library/Frameworks/AudioToolbox.framework/AudioToolbox
0x32247000 - 0x3230cfff CFNetwork armv7 <4771a5e4f9b83bceb252f0f3d166aaca> /System/Library/Frameworks/CFNetwork.framework/CFNetwork
0x3230d000 - 0x32363fff CoreAudio armv7 <5d534dbf76ff30f4a628f25f56c5f26a> /System/Library/Frameworks/CoreAudio.framework/CoreAudio
0x32377000 - 0x3252ffff CoreData armv7 <3930f672c76535a2abb768ee59958fa7> /System/Library/Frameworks/CoreData.framework/CoreData
0x32530000 - 0x32662fff CoreFoundation armv7 <fcb8d4e838543bcb9a52c9f232b8b4eb> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
0x32663000 - 0x3279bfff CoreGraphics armv7 <81e213f810a034d4ba411f9b505da2a6> /System/Library/Frameworks/CoreGraphics.framework/CoreGraphics
0x3279d000 - 0x327d8fff libCGFreetype.A.dylib armv7 <a5d20b80ab1532d8831027a66d2d9eb5> /System/Library/Frameworks/CoreGraphics.framework/Resources/libCGFreetype.A.dyl ib
0x329d8000 - 0x32a8dfff CoreImage armv7 <6ae4ae2461313e3f84c6a8102d5b1b0e> /System/Library/Frameworks/CoreImage.framework/CoreImage
0x32a8e000 - 0x32ae6fff CoreLocation armv7 <4107e94cdf043d6089e99cbd30631b07> /System/Library/Frameworks/CoreLocation.framework/CoreLocation
0x32b1b000 - 0x32b80fff CoreMedia armv7 <8592bdc268b83b8886acfc1fdab649ed> /System/Library/Frameworks/CoreMedia.framework/CoreMedia
0x32b81000 - 0x32c09fff CoreMotion armv7 <908cc54aecf5318e9719c4c9d70ef2e8> /System/Library/Frameworks/CoreMotion.framework/CoreMotion
0x32c0a000 - 0x32c60fff CoreTelephony armv7 <c5a2e59bb15d35b8a8e356e129b78b5e> /System/Library/Frameworks/CoreTelephony.framework/CoreTelephony
0x32c61000 - 0x32cc3fff CoreText armv7 <e135debbc8f937299f4986fc3e9459e3> /System/Library/Frameworks/CoreText.framework/CoreText
0x32cc4000 - 0x32cd3fff CoreVideo armv7 <00f18bb26e663da9ae251a6ec36a19ec> /System/Library/Frameworks/CoreVideo.framework/CoreVideo
0x32cd4000 - 0x32d88fff EventKit armv7 <99a7a1603323319f9e24f97e9f89bfd3> /System/Library/Frameworks/EventKit.framework/EventKit
0x32d89000 - 0x32e49fff EventKitUI armv7 <4fba5b9b61c53464b73b236bd24e4cf9> /System/Library/Frameworks/EventKitUI.framework/EventKitUI
0x32e58000 - 0x3301bfff Foundation armv7 <0179934581d13346aa7583165108b95c> /System/Library/Frameworks/Foundation.framework/Foundation
0x331d6000 - 0x3321ffff IOKit armv7 <a98ba9fefc7333e4a5a9169198848c62> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x33220000 - 0x333f8fff ImageIO armv7 <b5ce84bb074d3de4b07b55da9fd8bfd1> /System/Library/Frameworks/ImageIO.framework/ImageIO
0x33472000 - 0x3360cfff MediaPlayer armv7 <ce97a30e514d3a17ae93ba4a9d1d69d2> /System/Library/Frameworks/MediaPlayer.framework/MediaPlayer
0x3360d000 - 0x33887fff MediaToolbox armv7 <ed439fc5c9a03f8b9fae43af33de8a57> /System/Library/Frameworks/MediaToolbox.framework/MediaToolbox
0x33888000 - 0x3390efff MessageUI armv7 <8dbc0a8e6a253c8c8d6301064f23dfea> /System/Library/Frameworks/MessageUI.framework/MessageUI
0x3390f000 - 0x33968fff MobileCoreServices armv7 <77da8a9e7f813f5baf37eaa4a87fae84> /System/Library/Frameworks/MobileCoreServices.framework/MobileCoreServices
0x33a57000 - 0x33a5efff OpenGLES armv7 <f2ede6b206f336de82cc38619692e762> /System/Library/Frameworks/OpenGLES.framework/OpenGLES
0x33a60000 - 0x33a60fff libCVMSPluginSupport.dylib armv7 <2506af1c983f3f09ac69aca44f67e863> /System/Library/Frameworks/OpenGLES.framework/libCVMSPluginSupport.dylib
0x33a64000 - 0x33a66fff libCoreVMClient.dylib armv7 <af6ff28dce6031baaa850ccc79e5699b> /System/Library/Frameworks/OpenGLES.framework/libCoreVMClient.dylib
0x33a67000 - 0x33a6bfff libGFXShared.dylib armv7 <a6ac1673a088379aa512ba5cac301f5b> /System/Library/Frameworks/OpenGLES.framework/libGFXShared.dylib
0x33a6c000 - 0x33aa9fff libGLImage.dylib armv7 <b8b8f3a1bfd0345e86aa0c2952534949> /System/Library/Frameworks/OpenGLES.framework/libGLImage.dylib
0x341a4000 - 0x342b9fff QuartzCore armv7 <c086b6e6cd9d341399bcc3675c82f1fe> /System/Library/Frameworks/QuartzCore.framework/QuartzCore
0x342ba000 - 0x34307fff QuickLook armv7 <954e3a8bdaf337b085b30fd514ea5f3a> /System/Library/Frameworks/QuickLook.framework/QuickLook
0x34308000 - 0x34336fff Security armv7 <fbc24f15bd9e37539cdd6e3576bde938> /System/Library/Frameworks/Security.framework/Security
0x343b5000 - 0x343f4fff SystemConfiguration armv7 <410d69b356e533d6a1d538cf33059634> /System/Library/Frameworks/SystemConfiguration.framework/SystemConfiguration
0x343f7000 - 0x3494bfff UIKit armv7 <ad8b3ad23f413187a178179db39cfa6b> /System/Library/Frameworks/UIKit.framework/UIKit
0x3494c000 - 0x3498afff VideoToolbox armv7 <d2e8067306d9346ab4a448f10f336894> /System/Library/Frameworks/VideoToolbox.framework/VideoToolbox
0x34bd1000 - 0x34bd5fff AOSNotification armv7 <01860d2c546e349ea4bb73c16db162f6> /System/Library/PrivateFrameworks/AOSNotification.framework/AOSNotification
0x34c20000 - 0x34c2cfff AccountSettings armv7 <8db45acc4d3d3017af10fa5ee82c2306> /System/Library/PrivateFrameworks/AccountSettings.framework/AccountSettings
0x34c2d000 - 0x34c47fff AccountSettingsUI armv7 <9f84a0aaae6f360fbb0694b955aeeefe> /System/Library/PrivateFrameworks/AccountSettingsUI.framework/AccountSettingsUI
0x34c73000 - 0x34c76fff ActorKit armv7 <5dfc59258ea63006be9c542e5fafbc45> /System/Library/PrivateFrameworks/ActorKit.framework/ActorKit
0x34c78000 - 0x34c7bfff AggregateDictionary armv7 <a2170ad876f13ef1b944547913d05af2> /System/Library/PrivateFrameworks/AggregateDictionary.framework/AggregateDictio nary
0x34d64000 - 0x34d77fff AirTraffic armv7 <752b64045f4d3ea88a946b53b731ce1a> /System/Library/PrivateFrameworks/AirTraffic.framework/AirTraffic
0x350a7000 - 0x350e2fff AppSupport armv7 <921794b7d82a3558a0eb860979be199c> /System/Library/PrivateFrameworks/AppSupport.framework/AppSupport
0x350e3000 - 0x35107fff AppleAccount armv7 <c54536fbc0f235f693060be33d4d4749> /System/Library/PrivateFrameworks/AppleAccount.framework/AppleAccount
0x35114000 - 0x35121fff ApplePushService armv7 <8bad4a9300db3d4d8555535f25c32da4> /System/Library/PrivateFrameworks/ApplePushService.framework/ApplePushService
0x35155000 - 0x3515efff AssetsLibraryServices armv7 <de7ca29cd47433cd8eca9c04102f5508> /System/Library/PrivateFrameworks/AssetsLibraryServices.framework/AssetsLibrary Services
0x3515f000 - 0x35177fff AssistantServices armv7 <fdec07136e153720bc82f5fae4de5f77> /System/Library/PrivateFrameworks/AssistantServices.framework/AssistantServices
0x35178000 - 0x3518ffff BackBoardServices armv7 <585cc62d83c530ee82988de940c1e161> /System/Library/PrivateFrameworks/BackBoardServices.framework/BackBoardServices
0x35199000 - 0x351bdfff Bom armv7 <b5315d733e123a0781683efdc734064b> /System/Library/PrivateFrameworks/Bom.framework/Bom
0x351d0000 - 0x351fffff BulletinBoard armv7 <9f46015c5d263064901f7725f4bb93e0> /System/Library/PrivateFrameworks/BulletinBoard.framework/BulletinBoard
0x35200000 - 0x35234fff CalDAV armv7 <c4d9726df6bb3c5d8c4614e3fce4ec5a> /System/Library/PrivateFrameworks/CalDAV.framework/CalDAV
0x3523d000 - 0x35244fff CaptiveNetwork armv7 <a4f4b86cc84839f78ff746f013bcee6f> /System/Library/PrivateFrameworks/CaptiveNetwork.framework/CaptiveNetwork
0x35245000 - 0x3530ffff Celestial armv7 <a688df527b65382da586ebc87f28c061> /System/Library/PrivateFrameworks/Celestial.framework/Celestial
0x35310000 - 0x3531bfff CertInfo armv7 <e84bae052fa43a098a69044ac4eeec15> /System/Library/PrivateFrameworks/CertInfo.framework/CertInfo
0x3531c000 - 0x35320fff CertUI armv7 <ce979f715cdb3cb5a0f7935f14cc0b35> /System/Library/PrivateFrameworks/CertUI.framework/CertUI
0x353f3000 - 0x353f8fff CommonUtilities armv7 <f8fea9ee6ca236b0a7fa6c00eb8a0d24> /System/Library/PrivateFrameworks/CommonUtilities.framework/CommonUtilities
0x3547d000 - 0x354adfff ContentIndex armv7 <00ed488e47ee34ca9f01f2cc911f453c> /System/Library/PrivateFrameworks/ContentIndex.framework/ContentIndex
0x354ae000 - 0x354fefff CoreDAV armv7 <e5256ba3f96d35d9813c8262e230c04f> /System/Library/PrivateFrameworks/CoreDAV.framework/CoreDAV
0x356be000 - 0x356bffff CoreSurface armv7 <6065f7e040e93d6ea2837e929592cc30> /System/Library/PrivateFrameworks/CoreSurface.framework/CoreSurface
0x35727000 - 0x3572bfff CoreTime armv7 <5f0b123555f03d8aa76cc54314907942> /System/Library/PrivateFrameworks/CoreTime.framework/CoreTime
0x3572c000 - 0x35731fff CrashReporterSupport armv7 <03ee46e3ca3f3920a7174e62096723fb> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/CrashReporterS upport
0x35732000 - 0x3576efff DataAccess armv7 <11fd8622bd043bd9be0bd44dc762671f> /System/Library/PrivateFrameworks/DataAccess.framework/DataAccess
0x3577a000 - 0x357b2fff DACalDAV armv7 <b0b6bede81783ba48951c969922d4c16> /System/Library/PrivateFrameworks/DataAccess.framework/Frameworks/DACalDAV.fram ework/DACalDAV
0x357c4000 - 0x357c9fff DACardDAV armv7 <1ae19bf612a831e79d07285324c391c5> /System/Library/PrivateFrameworks/DataAccess.framework/Frameworks/DACardDAV.fra mework/DACardDAV
0x357e5000 - 0x357e6fff DACoreDAVGlue armv7 <0f4f748626a83b0e85323f8d838cb74e> /System/Library/PrivateFrameworks/DataAccess.framework/Frameworks/DACoreDAVGlue .framework/DACoreDAVGlue
0x3583d000 - 0x358cbfff DAEAS armv7 <5d00aeaf28e03d65b3a41274b52dd8f8> /System/Library/PrivateFrameworks/DataAccess.framework/Frameworks/DAEAS.framewo rk/DAEAS
0x35903000 - 0x35915fff DataAccessExpress armv7 <9e23220c1d503ce98bc915eba6daf444> /System/Library/PrivateFrameworks/DataAccessExpress.framework/DataAccessExpress
0x35929000 - 0x3593efff DataDetectorsCore armv7 <58352df07a0139de878e5e275e27ab52> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/DataDetectorsCore
0x35940000 - 0x35953fff DataDetectorsUI armv7 <331c11e50793340f9ce758435c9420ac> /System/Library/PrivateFrameworks/DataDetectorsUI.framework/DataDetectorsUI
0x35954000 - 0x35955fff DataMigration armv7 <5903e08348b83f119022cbbf83ad100a> /System/Library/PrivateFrameworks/DataMigration.framework/DataMigration
0x35958000 - 0x35971fff DictionaryServices armv7 <84669055e3e63d6ab56b8fe7b0476aaa> /System/Library/PrivateFrameworks/DictionaryServices.framework/DictionaryServic es
0x35979000 - 0x35991fff EAP8021X armv7 <82a73adcf1db3d2f9e57cd22f71e44c9> /System/Library/PrivateFrameworks/EAP8021X.framework/EAP8021X
0x359a1000 - 0x359a5fff FTClientServices armv7 <6354e5b30919340db3b976312b284fce> /System/Library/PrivateFrameworks/FTClientServices.framework/FTClientServices
0x359a6000 - 0x359e3fff FTServices armv7 &nbI've also had the same issues, after upgrading to IOS 6.0, the apps in my iPhone 4 were crashing and the battery life run out very fast.
The only solution worked for me was to remove all mail accounts (Exchange/Gmail) from my iPhone (in settings) and then add them back.
The crashing were stopped! also the battery was back to normal.
I found the solution by first looking at the crash logs (in IOS 6). you can find them at Settings -> General -> About (at the bottom of the About menu you will find the option that opens the logs).
There i saw many logs about Low Memory crash. 99% of the logs were pointed that the largest process (use the most memory) during the crashes is "dataaccessd".
I search in the web and found that this process is a deamon process that reponsible the Mail accounts (like Exchange/Gmail) and contancts list.
I've installed the app "System Status - activity monitor" which shows important system info like CPU usage, Memory usage and running processes.
Before apply my solution (deleting the mail accounts) i saw that the CPU usage was very high which consume the battery very fast. Also i saw that the memory (RAM) was run out.. which probably what cause the crashing..
After deleting the mail accounts (at Settings -> Mail, Contacts, Calendars) i check again with the System Status app, and saw that the memory and CPU were back to normal.
Adding the mail accounts back, still everything work ok
Hope this solution will help you too,
Enjoy! -
ITunes computer authorization failure ( tried all fixes )
Computer authrization problem in iTunes
Hi to all. I am having the common problem of computer authorization in iTunes, so i can't sync my iPad and transfer my purchases. I have read about all the "popular" fixes and none of them worked. I am listing them here for others to try ( google them for more info as i will not describe in detail ) :
1. Delete the SC info folder ( Users/Shared)
Comments from my problem : I do NOT have an SC info file!
2. Deauthorize/Reauthorize this or all computers and sign in again..
Comments from my problem : Did that, did not work.
3. Uninstall and reinstall itunes
Comments from my problem : Did not try that. Any comments on that?
This is a real problem of the apple community and apple should do something about that, as we are paying gold to buy their products. The support should be faster. This has been going on for a while now.
Thank you in advance,
George
Equip : Macbook Pro, Mac mini (Non active ), iPhone ( Non active ), iPad AirDoublechecking. In the course of your troubleshooting to date, have you also worked through the instructions from the following document?
iTunes: Missing folder or incorrect permissions may prevent authorization -
Wireless keyboard stopped connecting to iMac. Replaced batteries, restarted computer. Keyboard blinks green- cannot get steady green light. Computer does not recognize keyboard, nor connect. Tried deleting device and re-connecting, but keyboard is never seen by the Mac. Also tried same keyboard with a Macbook Air and keyboard was not recognized. other bluetooth device (mouse) works fine. Ideas?
For now, try a SMC reset.
DALE -
Disable Faulty FireWire Ports In 10.4.11
my powermac's firewire ports are fried, and it causes all kinds of problems (slow startup, random freezes, computer won't sleep).
i found this:
sudo -s
Password: (enter admin password)
cd /System/Library/Extensions
cd IOFireWireFamily.kext/Contents/PlugIns
mv AppleFWOHCI.kext AppleFWOHCI.null
touch /System/Library/Extensions
which disabled the built in firewire ports, and solved all of my problems...but it also disabled the firewire ports on the PCI card i put in.
is there a way to disable to built in ports, but not the ports on the PC card?
i know very little about this, so any help is appreciated.Hmmm, are your 10.4 Install Discs more than one?
Just tried my Mac Mini, 10.4.2 Install Discs which is a 4 or 5 set, and indeed AB was a generic icon & small, I believe more resides on other Discs in the set, likely #2.
Have you considered...
If all the above fails, then it appears to be time for a relatively painless Archive & Install, which gives you a new/old OS, but can preserve all your files, pics, music, settings, etc., as long as you have plenty of free disk space and no Disk corruption, and is relatively quick & painless...
http://docs.info.apple.com/article.html?artnum=107120
Just be sure to select Preserve Users & Settings. -
Firewire ports disappear on powerbook?
I've got a 1Ghz AlBook and after recently trying to share internet connections and use my ipod via firewire, I realized it wasn't working. I looked in system profiler and the firewire bus was blank...nothing there...I rebooted into target disk mode and connected it to my powermac, and it showed up without a problem...so how did Tiger forget of the existence of my firewire ports and how do I get them back? Thanks.
Hmm...
- Try resetting the FireWire ports by disconnecting all FW devices, disconnecting from AC and shutting down for 10-15 minutes. (This works once in a while, but it won't necessarily provide a permanent fix.)
- Try resetting PRAM ( http://docs.info.apple.com/article.html?artnum=2238 )
- Run Apple Hardware Test (in extended mode) by booting from the Install and Restore DVD that came with your PB while holding down the Option key. AHT may report hardware errors related to this issue.
I really don't like to suggest that people reinstall their system software except in extreme situations, but if you wanted to do that to rule out software as the cause of the problem, you also have that option.
Good luck.
Tuttle -
My IMac is dying a slowwwwww death. First I have the black screen, but was able to use an external monitor for the time being. My problem now is my firewire ports. They both are not working. When I open my system profiler it says "No info found". Anyone able to help me? Anyone know a "fix" for this?
Thought you could use this info about getting FireWire to work!
First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
If that still didn't get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
For those of you with Macs that are not PowerBooks or iBooks, a bad internal battery can cause FireWire to not be recognized, so make sure it's good! Also, here is Apple doc.#88338 on getting FireWire to work.
Here's some more FW tips.
Cheers! DALE
I have a little more but we need this.
p.s. It would help us, so we can advise you correctly, if you would fill in your Mac's specs. in My Settings over on the right, near your name and under the logout choice please.We don't know exactly what version of 10.3 your are running.
->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -
My firewire ports seemed to have died. Not only will my Lacie Drives no longer mount, my iPod won't either. The system profiler doesn't seem them. They don't mount on the desktop. However, it seems as if power is still getting to the devices.
I've tested the devices and cables in question on my powerbook. They all seem to work.
Any ideas?Thought you could use this info about getting FireWire to work!
First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
If that did'nt work, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try. Yours is the 10.4.3 Combo update. Others reading, download the Combo that applies to your system.
If that still did'nt get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
For those of you with Macs that are not PowerBooks or iBooks, a bad internal battery can cause FireWire to not be recognized, so make sure it's good!
Good Luck!
Cheers!
DALE -
Rear Firewire ports have left the building!
The rear firewire ports on my MacPro have stopped working (800 and 400)
Not recognizing hard drives or Audio devices.
The ones on the front still work but are making problems when connecting 400 and 800 together.
What can I do to solve this problem of fix it?
HELP!!Thought you could use this info about getting FireWire to work! Usually they all stop at the same time though.
First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
If that didn't work, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try.
If that still didn't get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
A bad internal PRAM battery can also cause FireWire to not be recognized, so make sure it's good!
Also, here is Apple doc.#88338 on getting FireWire to work.
Here's another Fw Faq.
DALE -
My Firewire port is not working: Is that a Hardware or Software issue? any suggestions?
Greetings Everybody,
I bought this Imac to use it only with audio applications and now I can't use my UAD -2 Duo Satellite because MAC OS tells me that "
No FireWire ports were found" Does any know how to deal with this problem?
Thanks in advanceUSB and Firewire information:
http://support.apple.com/kb/HT1151?viewlocale=en_US
USB:
http://support.apple.com/kb/HT4049?viewlocale=en_US
Firewire Port failure:
http://www.wiebetech.com/whitepapers/FireWirePortFailures.php -
My Firewire ports have suddenley stopped working.
I have several firewire peripherals and none of them will work.
Maybe a connection insde?Thought you could use this info about getting FireWire to work!
First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
If that did'nt work, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try. Yours is the 10.4.5 Combo update. Others reading, download the Combo that applies to your system.
If that still did'nt get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
For those of you with Macs that are not PowerBooks or iBooks, a bad internal battery can cause FireWire to not be recognized, so make sure it's good!
Good Luck!
Cheers!
DALE
Maybe you are looking for
-
Ok guys, I have a very simple question...but can't seem to find an answer. I there anyway I can download flash for my mac? I've found downloads for flash PLAYER on mac...but I don't really understand the difference. All I'm looking for is the version
-
Make call with CAD via third party
Hi friends, I am in a situation of implementing manual dialing from CAD in a UCCE environment from a 3rd party application. I have CISCO CAD 8.5 premimum and trying to explore different possibilities: Click-to-call with hyperlink dialing enabled Havi
-
OIF Authentication Failing - UserID : anonymous - Internal Error
Hi, We have implemented SSO in our environment. After credentials are entered in the login page (protected by OAM), we get 500 internal server error on the browser. In the OIF logs, we see the following exception: [2013-01-17T04:27:24.730-05:00] [wls
-
I'm trying to download a few Adobe programs (Illustrator, InDesign, Photoshop, etc) onto my new computer, and each time it fails, with a message saying that the download appears corrupted and to try again in a few minutes. I've tried uninstalling CC,
-
Are there any events associated with a Blocks Scrollbar?
I'm using a multirecord block and its associated scrollbar. When the records are scrolled using the scrollbar, record focus doesn't necessarily change but the position of the record within the block does. Are there any events available to monitor the