10.8.4  update firewire issues

10.8.4  update is not fixing the firewire issues that 10.8.3 caused with my macpro.  my printer (professional Epson)
hard crashes when accessed.   I'm reporting this because there are many people having firewire issues with firewire
printers and 10.8.3. 

Use the workaround until the FW issue is resolved:  use a USB cable.
OT

Similar Messages

  • Firewire Issues: External Hard Drives & DV  Deck Sony DSR 11 not recognized

    So, I have this brand new $6000 Mac Pro that will not recognize a simple DV deck, nor the external HD's.
    Thus, after spending seven hours searchig around last night, trying every configuration possible from updates, unplug power source, and everything else, I began making calls as of 4 am this morning.
    I was referred to FCP Europe where I was informed that I needed FCS friver updates. (unavailable for 1.0.1) or perhaps it was a Sony issue. The deck & drives work fine with my G4 & Powerbook G4. With six fire wire ports on the Mac Pro, and nothing being recognized via a single fire wire port, does anyone have a simple, expedient solution? Thank you.

    Ahhhh. Firewire issues. I'm convinced that these Macpros have some serious problems here. I am running a sony dsr11 also with a digi002. MY issues is bootup. . I have a mac pro with Tiger installed. My issue is I intermittently get a prohibitted error on bootup. The error looks like a no smoking sign without the cigerett. I have to re boot and sometimes the os boots right up othertimes not. I have sfound that I have to boot my sytem with noting hooked up first. It seems when you have high end firewire devices that the Bus just can't handle it. Real ****** for thos who bought the system for A/V work. Everything woks fine on my powerbook and my G5. Problem is with MACPRO! Do you also have other firewire devices hooked up? Are they daisychained together?
    Vito

  • FireWire Issues - anyone else?

    Have a PB G4, 1.67, with an Apple-repaired logic board [from Nov 08]. After latest Security updates, I have had trouble connecting either 800 or 400 FW drives. I've tried them on an iMac and iBook; both work. Tried different cables, three different drives [2 OCW, one Verbatim]. Nothing works. Wiggled cables. Used both bus and external power.
    HELP please. I don't want to spend another $350 [plus postage from UK via APO] to fix this a third time [was a refurb, used from PowerMax, they looked at logicboard once, and then I used Apple's fix it service]. The Apple repair warranty expired in Feb 09.
    I might try an $80 cardbus FW800/400 if I can find one still.
    Thanks in advance.

    Frustrating trying to get it to work .... You can zap the PRAM as well as reset the PMU anytime. At this point, if you haven't go ahead and do the PRAM and might as well do the PMU again. Reset PRAM. Note the effects are immediate, there's no advantage to waiting overnight:
    1. Shut down the computer.
    2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    3. Turn on the computer.
    4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    6. Release the keys.
    It sounds like you may have had hard drive issues that Drive Genius fixed for you. For comparison, did you run the Disk Utility disk repair after Drive Genius fixed the hard drive .. just to see if Disk Utility gives the drive a clean bill of health?
    When you ran the Apple hardware test, did you run the extended test? Do you have either of the TechTool programs available? They do similar testing to the Apple hardware test, it would be interesting to see if they also say the hardware is OK.
    You've reloaded the operating system a couple of times. Did you use the combo update to update to 10.4.11? I prefer that to letting Software Update make the updates, as sometimes it doesn't update correctly. Repair disk permissions before and after the update, too. Then run software update to pick up any other required updates.
    You've, by this time, reset PRAM and PMU, I assume the PRAM reset didn't change anything? If so, sorry, but I don't know what else you can do. At this point, I'd take it to a genius at the Apple store, and get their opinion.
    I didn't address sleep as I think you need to resolve the Firewire issue first, then see if there is a sleep problem.

  • IPad mini now terrible to use, apple support no help because warranty is up.  All cause by new ios8 update, wifi issues, many apps no longer work, apps that do work now crash regularly and sometimes take several instances and reboots to even open.

    IPad mini now terrible to use, apple support no help because warranty is up.  All cause by new ios8 update, wifi issues, many apps no longer work, apps that do work now crash regularly and sometimes take several instances and reboots to even open.

    need help uninstalling ios8 and going back to 7 where things worked please.

  • FSCM via WS-RM (without PI ) - Update termination issue

    Hello experts .
    We are trying to integrate SD with FSCM ( credit management) using WS-RM (without PI).
    Details of the issue and steps followed so far.
    Ideal Scenario :
    Once we create / change a sales order ( in SD ) , the interface Creditworthinessquery_out (WS Consumer ) gets triggered (in SD) and the subsequent response CREDITWORTHINESSQUERY_IN(Provider) is triggered from FSCM (with the details of creditworthiness).Once the query response in received an notification is triggered from SD to FSCM (asynchronous service).
    After receiving the query response the functionality of credit check happens while creating / changing the sales order .
    Configuration steps followed in SOAMANAGER
    We have created end points for all the relevant service interfaces (Providers) , and also created logical ports for the respective consumers.
    During the creation of logical ports - for the consumers we used the WSDL (of the providers) as the inbound message action.
    (This has been done to all the services query , notification that are relevant in our integration).
    Current behavior / issue .
    While creating sales order the sales order is not getting saved (getting updated in the database).System allows us to complete the sales order creation process and also we get a message as sales order saved successfully. But then there is a update terminated express document that pops up. Sales order is not getting updated in the database.
    When I see the logs/traces in SOAMANAGER I see that the query out is successful , query in has the right response (in warning state though) . But no notification is being triggered ?? 
    How to overcome this update termination issue ?
    When we see the SM13 log , it points to SLD issue (LCR 010: Internal error in SLD API). why do we need a SLD without PI

    Hi  ,
    Finally we are able to solve the update termination issue . But again we are using a work around .
    Situation :
    Once we executed the VA01 transaction we were getting update termination issue . After lots of debuggung we found that system was trying to get the Business system details ( Own business system data ) . The table lcrt_clntcache had no values.
    Solution
    We inserted appropriate values in the Table LCRT_CLNTCACH (business system data ) and now it works .This is a work around we got as of now.Credit checks are happening successfully and also integration is good .
    (typically if we define business system in SLD (PI) , and run SLD_CHECK , this table gets populated , but in our case we are not using PI instead we are using WS-RM)
    But now few questions arise .
    a) Why do we need a business system in case we are not using PI ( typically we define business system and technical system in PI )  and instead using WS-RM ?
    b) Is it a good practice to update the table ( as did in workaround above )?
    c) Is this any bug and needs to be consulted with SAP ?
    Please let me know your views .
    Edited by: Vedula Adeep on Jan 16, 2012 8:42 AM

  • CS5 support is falling down - the famous firewire issue

    As a loyal user of Adobe professioanl editing solutions for the last 10 years this past month has been a nightmare.  When I inquired about upgrading to CS5 from CS3 I was advised during an online chat with an Adobe person here on the site to upgrade to CS4 and because of the timing I would get a complimentary CS5 upgrade.  I purchased CS4 on April 14th and had so many issues it was never even used in the edit suite.  When CS5 became available I decided to cut my losses and decided if I was going to have to go through all the hoops I might as well only go through them once with CS5.  I have had numerous long discussions with Adobe "support" regarding various problems and now I am at the end of my rope.  Even though they say the are taking notes during our conversations each subsequent "support" person claims to not know most of the pariculars discussed in previous phone calls.  I didn't think I had to follow up each phone call with a note here but evidently that is the case.  Today I have a deadline to deliver content on TAPE to a national cable network and the series contract could be in jeapordy if I can't deliver the first of 26 episodes.  I CANNOT PREVIEW ON AN EXTERNAL TELEVISION MONITOR OR EXPORT THROUGH FIREWIRE TO MY MAIN DV DECK.  It is a deck I have used for YEARS with Premiere CS2 and CS3 and i NEVER had an issue like this.  I have been told repeatedly that the issue would be resolved and most recently on Tuesday of this week I was promised a callback between "1PM and 2PM" Central Standard time on Wednesday, THAT CALL NEVER CAME.  When I followed up with another call MOST of the days previous discussion was NOT in my case notes.  I was told my main Sony VTR and secondary JVC VTR were not HDV decks even though I have been using BOTH for many years for just that purpose and even though that didn't address the most pressing of all my issues which was just getting output through firewire to tape.  After a very frustrating call I was promised another callback "in an hour" by a "supervisor".  That call NEVER came.  Both Adobe "support" and PNY Quadro "support" claim that they have "never" heard of the firewire issue even though it is all over the forums at Adobe.  I will be posting this and every subsequent communication between me and Adobe on the forums, at Yelp and any other web sites that take reviews of professional video products.  For the record just some of my other issues include the inability to capture HDV from the Sony HDV deck I have been capturing from for years, Alpha Glow not working and no split screen when doing color correction in a number of effects where it is offered.   Also for the record I have tried turning off the MPE GPU acceleration to export to tape and that doesn't work either.  System is a Supermicro dual processor motherboard with lots of ram and a Quadro FX 3800 operating with 64 bit Windows 7.

    Read here:
    http://kc.flex-radio.com/KnowledgebaseArticle50433.aspx
    It may get firewire working again on your older deck with Windows 7.  If the solution on that page works, then the problem is down to Microsoft, not Adobe.
    FWIW, it's getting to be pretty well known around these parts that the current implementation of Adobe Customer Service is awful.  That said, several Adobe employees, including some Premiere Pro engineers, have been hanging out in the forums recently.  This is a big change from earlier releases of Pr, where an Adobe presence was rarely seen at all.
    These same folks have also said that Adobe is working to improve their Customer Service.  Like the inertia of a large ship forcing it to take a long time to change course, I suspect that it will take a bit longer for Adobe to make that improvement than it would for a smaller company.  Don't give up on 'em just yet.
    -Jeff

  • Muse update installation issues

    I have a monthly subscription to Muse and everytime I try to install the latest updates Ihave issues. When I try to install directly from MUSE it tells me to check my network connection - which is always fine. I have tried pausing my virus protection etc. I then try to get help from customer support and the fxes do not appear to work etiher. I haveuninstalled and reinstalled etc with no luck -any suggestions

    Try disabling any firewall or antivirus application and re-try updating, also try a different network connection. If that doesn't help, please uninstall and use the following direct download links to install Muse fresh.
    Mac - http://www.adobe.com/go/muse_latest_win
    Win - http://www.adobe.com/go/muse_latest_mac
    Thanks,
    Vinayak

  • When I try to update iPhoto it says that the update was issued to a different Apple ID

    I updated my Mac and then I lost access to my old iPhoto. It won't let me update the new one either and says that the update was issues to a different Apple ID. No other apple ID has ever been used on this computer....

    Check with the support people at the App Store via this link:

  • 10.5.6 firewire issue after update!!

    Hi
    After doing the software update to 10.5.6 recently, my audio interface (MOTU 828) started to behave strangely (cutting in and out). I though it was perhaps too old these days so I bought an Apogee Rosetta 200. However that has not solved the problem, it just doesn't seem like it wants to connect via firewire properly.
    I've seen a whole bunch of issue on various forums related to firewire after the 10.5.6 update but it doesn't look like everyone has it.
    Can anyone help? Or does anyone know if Apple have released a firewire driver patch or something?
    I am convinced there is a firewire driver problem in this update and I need them know about it!
    Many thanks
    Dave
    P.S. Have already tried: zapping PRAM. Repairing permissions. Re-installing combo updater. Unplugging all my external firewire devices.

    Sorted the issue. It was the firmware for the firewire card on the Rosetta 200. The FPGA wasn't communicating properly so had to re-install the firmware several times before it recognized it.
    Hope this helps someone.
    Thanks

  • Weird Firewire Issue since 10.5.6 update

    Hey guys!
    I'm a musician so I use an audio interface (Presonus FP10) to record my stuff. It's a firewire interface and it used to work perfectly fine.
    However, since the 10.5.6 update there seems to be something wrong with my firewire port and I haven't found anything on the web that fits my problem.
    If I plug in my interface into the firewire port, it doesn't work. It neither goes on nor is recognized by the OS.
    Although, once I plug in my ethernet cable for internet access, it works fine.
    Problem with this is that in my music room there is no possibiliy of pluging an ethernet cable.
    I hope somebody can tell me what to do in order to get this fixed, whether this problem is caused by Leopard or by my interface.
    Thanks,
    Mark

    That was my first guess, too. See, that's what makes it all so weird:
    I have the device plugged in with no other cable. Nothing happens. I have the ethernet cable plugged in without anything connected to that. Nothing happens. I then plug it into an internet router ét voilá! It works...Could it maybe be a lack of electricity coming from a damaged AC-Unit connected to the device?
    But then again, it all worked fine up to the 10.5.6 update. Did the apple people do something to the firewire driver?I hear the new Macbooks come without Firewire...

  • Firewire issue--Backup drive not found w/Time Machine after imac sleeps

    I've had a lot of problems with Time Machine on my G4 imac since starting to use it a month ago. I think I have isolated the problem:
    Time Machine functions properly while the computer is in use, and it has no problem after a restart or shut down, but if the computer goes to sleep and then TM runs its hourly backup, I get an error that it cannot find the Backup Drive. Once this happens, TM will no longer work until I've deselected the drive in TM, unplugged it, plugged it in again, and reselected the drive as the backup Drive. Sometimes this requires a shut down or restart too.
    Here's what I've tried:
    1. connected the drive via USB--it operated without a problem
    2. unplugged all devices from the computer, shut down, waited, 20 mins, restrted, plugged the external drive back in via Firewire--the problem persists as described above.
    3. deleted the TimeMachine.plist file, restarted--problem persists.
    I've read that the Firewire port can be reset with other procedures such as zapping the PRAM or updating the firmware. I've also read that new problems can arise after reseting the PRAM so I'm hesitant to do this. Can anyone shed some light on the PRAM option?
    I cannot find where the firmware updates are located on the mac site. Could someone point me in the right direction? I've looked under downloads and after searching, came up with a long list, but nothing was labeled clearly. Each listing mentioned firmware in the header, but it seemed to always pertain to a certain issue (eg. superdrive, or installing appleworks). I could not tell what was the most recent firmware released for my machine, and I fear installing something retrograde that will create new problems.
    If anyone has any thoughts on how to deal with the firewire problem, or if you think my issue with using a FW connected drive with Time Machine might be rooted with something else, please comment.
    Thanks!
    HM
    Message was edited by: imaginary_forest

    fzgy wrote:
    "Mac OS X can't repair the disk.  You can still open or copy files on the disk, but you can't save changes to files on the disk.  Back up the disk and reformat it as soon as you can."
    It's possible a heavy-duty 3rd-party disk repair app can fix it, but they're expensive (DiskWarrior is about $100), and there's no guarantee it can do it.
    Am prompted to reformat but I don't have a good understanding of what this means and how to do it.
    That will erase it.  See Time Machine - Frequently Asked Question #5.
    It sounds very much like the disk is beginning to fail, although it's possible there's a bad port, cable, connection or power supply (if it has its own).
    I'd suggest getting a new one, and using it for your Time Machine backups; once you have a good backup there, reformat the old one (and select Security Options to write zeros to the whole drive -- if that fails, you know the drive is toast).  Use it for secondary backups, per FAQ #27.   If it has failed, get a second new one for secondary backups. 

  • Firewire Issues Caused By Apple Isight!

    For months, I've been having an intermittent Firewire audio problem, which I initially thought was A) Quad G5 or B) RME Fireface 800!
    Testing the RME on another Quad G5 resulted in no errors, though for piece of mind a replacement RME was given! Back home the same intermittent problems occurred, it had to be the Quad G5???
    Livid, this time I persisted on Google searching for FW issues, (a few hours later) to my amazement I came across an article on MacFixIt, that pointed the finger to Apple's own iSight FW camera, which I had connected!
    The transcript below explains how to resolve this problem, it worked for me!
    Mini-Tutorial: Dealing with FireWire problems (drives not mounting, devices unrecognized, etc.)
    As an Apple-invented technology, FireWire (IEEE 1394a and IEEE 1394b) should be (and usually is) one of the most solid and efficient means for interfacing with external peripherals. Indeed Apple's "i"-branded devices -- the iPod and iSight -- have, in large part, been made possible by the quick transfer rates, power sourcing, and hot pluggability offered by FireWire.
    Occasionally, however, conflicts between FireWire-connected devices arise and can result in a variety of issues including DV cameras dropping frames, FireWire drives not mounting, and erratic behavior from the iPod (disappearing from iTunes, etc.). In the midst of these issues, you might also experience "buffer underrun" errors when trying to burn CDs or DVDs with FireWire-connected recorders.
    The iSight is especially notorious for causing issues of this nature, and exhibiting symptoms.
    There exist a number of methods for dealing with FireWire device interference, a few of which are explored here.
    Switching Ports The first procedure you should try when experiencing a problem that you believe to be caused by device interference is to simply reconfigure the arrangement in which your FireWire peripherals are connected.
    Try switching each device to a different port, or temporarily disconnecting one or more of the devices. In particular, if you are a PowerMac G5 owner, trying switching devices from the front to back ports or vice versa.
    Adding an external hub In some cases, it appears that FireWire devices are not drawing enough power from the computer. This can cause a sundry of strange issues, including apparent conflicts between devices and unexpected power-offs during device operation. In these instances, adding an externally powered FireWire hub can clear things up.
    One of the reasons an "under-powered" situation can occur is that different Mac models have varying power capacities available through their FireWire ports.
    PowerBooks and iBooks have the least, generating around 7 watts. The iMac G5 also generates a relatively low amount of FireWire power, sharing 8 watts between its two FireWire 400 ports.
    The Power Mac G5 shares 15 watts between its one FireWire 800 port and two FireWire 400 ports.
    Place devices on different FireWire busses/Isolate the iSight Similar to the above procedure, adding another FireWire bridge -- via an extra PCI-based FireWire adapter or another means -- can eliminate conflicts from devices that reside on the same bridge.
    Power cycling the system Simply cycling the power on your system may be enough to temporarily eliminate a few FireWire conflict issues.
    Shut down your Mac, and disconnect all FireWire devices as well as the computer's power cord. Leave the system off for about 10 minutes, then plug it back in. First turn your Mac back on, then re-attach the FireWire devices one at a time and check for the conflict to resurface.
    Disconnect the iSight As noted above, the most common cause of interference is Apple's own iSight. In case after case, simply disconnecting this single device has eliminated problems with other FireWire devices.
    Disconnecting the iSight has proved particularly successful for an issue where the iPod disappears from the Desktop and from the iTunes playlist, while the iPod status screen cycles from the Apple logo to a "Do not Disconnect" message over and over.
    The exact reasons why the iSight causes more than its fair share conflicts with other FireWire devices are many, and sometimes unclear. One potential source of conflict, however, could be the unit's high bandwidth usage.
    The iSight captures video at a 640 x 480 pixel resolution, at 30 frames per second in millions of colors. Such throughput uses a significant chunk of the standard FireWire port's 400 Mbps bandwidth. As such, when other devices are connected, the bandwidth requirements for satisfactory performance may not be met.
    Apply the latest updates Make sure that your FireWire drives are using the latest firmware (check the manufacturers' Web site) and the most recent iPod update has also been applied.
    Of higher importance, if you have an iSight, is the iSight 1.0.2 updater. In a large number of cases it has resolved conflicts caused by the camera.
    Re-apply the most recent Mac OS X combo updater In some cases, re-applying the most recent combo updater can resurrect seemingly defunct FireWire ports and allow devices -- drives included -- to be recognized again.
    The most recent combo updater is available from Apple's download page.
    Clear caches Try using a tool like Tiger Cache Cleaner or Cocktail to remove potentially corrupt system caches. Restart, then check if your FireWire devices are recognized.
    Ps. There was no iSight connected when testing the RME on another Quad!
    Power Mac G5 Quad 2.5 GHz   Mac OS X (10.4.4)   2x 2.5 GB HD, 2.5 GB RAM, iSight, iPod, RME Fireface 800 Audio Interface

    TA

  • 2011 MBP 13" i7, 10.6.8 update, no issues

    So, I bit the bullet and decided to run the 10.6.8 update on
    my MBP.  All went without a hitch.  Reboot after install was
    only somewhat longer than usual (typically what I have seen
    with past OSX updates).  Installed the new Parallels update,
    and all is good.  My Sony 19". DVI monitor works without
    any problems at all.
    My procedure was as follows:
    1.  Booted my system from my clone on a Firewire drive.
    2.  I used Disk Warrior to do a file scan on the internal drive
        to check for corrupt files.
    3.  Then used Disk Warrior to scan/repair/rebuild directories
          on the internal drive.
    4.  Then used Disk Utility to repair permissions on the internal
          drive.
    5.  Then, rebooted to the internal drive and updated my clone.
          (Wanted to make sure I had a nice clean backup, just in case)
    6.  Ran the 10.6.8 Combo updater.
    At this point, all seems to work well. No issues with external
    display, no issues plugging in peripherals.
    Also, no printing issues.  However, since my HP Laserjet 1022
    is plugged into my Airport Extreme, not sure if it that means anything
    for those who have had problems.

    Next time an Apple employee tells me, "People don't post when they don't have a problem.", I'll be able to say "LIAAAAARRRR!!! LOOK HERE!!!!"

  • 10.4 to 10.4.11 Combo Update (PPC) Issues - Will Not Sleep, Etc.

    I've been running Panther 10.3.9 successfully for a long time. There are a few programs I'd like to use that require Tiger and I realized that Tiger retail disks were getting hard to come by and expensive, so I decided to buy one when I found it for a decent price.
    I installed 10.4 (running repair disk and repair permissions prior) and then ran all the possible updates from Software Update. I did not select them all at once, most of them one at a time, while repairing permissions after each of them. Shortly after, things were not right.
    The first thing I noticed was that I could not put the computer to sleep with either the Apple > Sleep or through the settings in Energy Saver. Expose was flakey also, it seemed to work intermittently. The eject button on the keyboard also worked intermittently. Then, with Activity monitor I would see the following items not responding: loginwindow, System Preferences and Disk Utility (not necssarily at the same time, but at one time or another.) I suppose there may have been others issues, but these are just some of the things that I noticed.
    Startups, restarts and shutdowns took a long time. However, the progress bar on startups after the grey screen visually moved exceptionally fast and seemed odd.
    These issues also occurred in Safe Mode.
    An archive and install back to 10.4 produces a perfect running system, none of these problems occur.
    Since my initial update attempt, I've tried to update with the manually downloaded 10.4.11 Combo Update (PPC) with the exact same results (no sleep, expose issues, not responding issues, slow startups, restarts and shutdowns, etc.)
    I've archived and installed and updated four times - only keyboard, mouse, ethernet cable and apple speakers were attached. I'm currently sticking with 10.4 until I can find something I can do to troubleshoot this issue which may allow me to get a problem free update to 10.4.11.
    Note that my computer does lose the date and time settings when powered off and today I ordered a new PRAM battery. Could a dead battery be contributing to my issue, even though 10.4 is fine?
    Any suggestions would be appreciated!
    Julie

    ...only real low level kexts like old drivers for Universal Power Supplies & such, or real Haxies that dig into & change the OS somewhere.
    So, if old drivers and haxies might exist, how do I go about finding them? The only program that I have that I think may be considered a haxie is DockExtender 3.1.3, http://www.codetek.com/dockextender/ (stills seems to work.) It was in my startup items when I initially performed the combo update. Since then, only iCal related items are in my startup items. Subsequent update attempts have been ran when DockExtender was not active. Also, is it note worthy that I have a non-system icon for my hard drive?
    My feeling so far is that it's the HD or RAM, Tiger is twice as hard on & demanding of both.
    My hard drive is a Seagate 200 GB (utilizes only 128 GB) Ultra ATA/100 7200 RPM 8 MB Cache installed around March 2006. It still has a 2 year warranty. Are you speculating that it just may not be suited for Tiger?
    My memory consists of three strips of Corsair VS256MB133 G that I installed in February 2008 - these came as a warranty replacements due to a bad strip of another part number that they did not stock any more.
    I don't think it's any of the APPs you aren't running.
    In terms of my applications, so far I've updated Firefox (uninstalled some incompatible add-ons and themes.) Identified Font Doctor 5.1.2.9 has likely not being compatible, because it quits when selecting a folder to move troubled fonts to when diagnosing. I questioned Extensis Suitcase 10.2.2, but found out that if I trashed the Library/Caches/com.apple.ATS that the font activation errors were resolved. Safari has crashed on me a few times, but it is still version 2.0. It also crashed in 10.3.9, forcing me to use other browsers. Can I update Safari now? Software Update does not show Safari and I don't know if the combo update is the only was to update it. I'm still investigating other applications compatibility, but the true test won't happen until I run the combo update and am able to run my applications on 10.4.11.
    If you had a Firewire Drive to Install to & try, that would be great.
    I do have an external firewire drive, but it contains a bootable backup of my 10.3.9 system right now. I'd hate to tamper with it at this time, due to my current situation. I can check on borrowing one if necessary. Would this prove out the question regarding the hard drive and since it would be a clean install = no possible haxies or old drivers lingering around. I also have my old internal hard drive that I could use but, this would be the original from this mac and although it worked fine when I removed it, maybe it would not work well with Tiger.
    Thanks,
    Julie

  • Firewire issues after upgrading to 10.6

    I mentioned this is a prior post, and have really still not got a resolution to it. I have a 1st. gen Mac Pro 2 x 2.66 dual core. I have encountered several disturbing issues using Firewire 400/800 devices on my machine after the upgrade. When I boot into 10.5, I have all the access and performance of my Firewire devices (a LaCie 1 TB external drive, A Sony CD/DVD burner, and a WD Passport FW 800/USB) All devices work in both USB and Firewire natively... but only work properly under 10.6 when using USB. All firewire access on my machine is sketchy at best under 10.6. The devices show up.. and mount.. but when I attempt to use/I.O to them.. the speed moves in bursts.
    For example.. copying a folder that is 5GB to one of the FW 800 HDs takes about 2-4 minutes on 10.5... and under 10.6 it bursts. When under 10.6, I get fast transfers for about 200-300 mb, then about a 5-10 minute pause.... then another burst of normal performance for 200 Mb. Then another pause. Taking an estimated 3-4 hours to copy a 5GB folder.
    In a test... I switched to the USB interfaces of these devices, and the transfers are fast as expected. (2-4 minutes, no pauses) Furthering the test.. the FW interfaces perform as expected under 10.5.
    Anyone else experiencing this? (I have tried resetting PRAM, and total shutdown etc.)
    Any assistance would be most welcome.
    Thanks!

    I have had Firewire problems since moving to 10.6. Some optical drives in an enclosure containing the Oxford 934 chip will not mount disks unless I pull the Firewire cable and reinsert it. They work fine using USB 2.0. The problem is a result of Apple's update of the Firewire drivers. The problem extension is
    IOFirewireSerialBusPRotocolTransport.kext
    Replacing this extension with the one from 10.5 causes everything to work properly. If you do choose to replace this extension, you may wish to replace all five with those from 10.5. Additionally, after making the exchange, repair permissions and restart so as to make sure the replacement extensions are properly recognized. You must repair permissions BEFORE restarting. If you restart and then repair permissions, the replacement extensions may not get recognized, even after a subsequent restart, and you will have to repeat the procedure.
    During permission repair, I received alerts that one or more of these extensions could not be used. I ignored the alert with apparently no adverse consequences.
    My Firewire only hard drives, and one Firewire/USB 2.0 hard drive seem to have no problem.
    K

Maybe you are looking for