The XP SP2 patch should be rolled up into SP3.

To suggest the next step, we need to know which iMac you have.

Please advise "early 2009" etc., or the Apple model number on the back of your iMac (looks something like "M604LL/A"

I can't find anything on the back. But in the hardware overview it says

Hardware Overview:

Model Name: iMac
Model Identifier: iMac8,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.8 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: IM81.00C1.B00
SMC Version (system): 1.30f1
Serial Number (system): YM8336SUZE4
Hardware UUID: E23D9FF9-1A6E-5C94-88A9-0F01E4AD1DEF

For Firewire bus it says "unknown device."

I bought it from Best Buy last December. Maybe that's why the Apple Store dweeb got testy with me.

By the way... I cut this http://www.vimeo.com/6870509 in Vegas last week. It's all shot within 15-minutes of my house, Too bad I can't print it to tape without taking it into FCP first.

[Quote]
I called the Apple Store to talk to a service guy about the possible Firewire port issue. HIs reply: Why would you want to waste a good Mac on Windows software, anyway?"[/quote]

Unfortunately you will probably only face more smiling Geniuses™ who are beginning with the premise that what the user wants is the problem.

This might help with the model number...
http://support.apple.com/kb/HT1463#301724

"iMac8,1" means the 2008 Aluminum iMac.

I have never seen Apple Store employees worry about where the hardware was bought, and neither has any of a number of other people I checked with.

When I needed help, they never asked where I bought it, they just provided quick and competent help (about the Mac side, alas).

Have you tried connecting your camera to the FW800 jack via a small FW 400-800 adapter?

I don't know if Windows even sees the FW800 jack, but if so, it may have a separate Firewire chip.

Yes, sadly I have tried both ports, with an adaptor in the 800 port, all possible hardware solutions (including cables), everything short of a new port. But I don't see how that would make a difference, because both ports work fine to and from the external hard drive, I can capture, external preview and print to tape just fine from both ports on the Mac side, and I can capture from both ports on the Windows side. I just can't do an external preview via firewire or print to tape on the Windows side.

The comment from the Mac snob at the Apple Store surprised me, too. In the beginning, Apple Support actually guided me through setting up Boot Camp and Windows. They even tried to help me with this issue, but wound up dubbing it a Windows problem. They've never been rude before. I think I may call the guy's store manager and complain.

You know, I really don't print to tape that often... maybe four times a year. So I suppose I could live with doing it from Final Cut. But I like working in Vegas, especially on jobs I have to turn quickly. Not being able to preview externally is a pain in the butt. And, it's a matter of principle. The damn thing should work.

But I don't see how that would make a difference, because both ports work fine to and from the external hard drive, I can capture, external preview and print to tape just fine from both ports on the Mac side, and I can capture from both ports on the Windows side. I just can't do an external preview via firewire or print to tape on the Windows side.

It would appear that Windows doesn't have a driver that is fully compatible with the chip used in this particular iMac model, so the PTT is missing the right interpretation of some signal.

When Win XP had firewire problems on PCs, I thought I saw third party drivers that fixed it before Microsoft got a round tuit? Anyone?

UPDATE:

I visited a friend last week who also has an iMac of the same exact vintage... except it had a different Firewire card. Mine just says "device unknown." Reckon I need to call Apple before the warranty expires.

Good idea!

Also add 2 years of AppleCare (from eBay at $75.00, or $69.00 if you go via live.com) before your warranty runs out.

This is more important when you have a more "laptop-like" computer that is trickier to work with because of the more compact build.

You could also try booting into the EFI ("BIOS") and issue a 'reset nv-ram and reset all' which has apparently helped some people give their iMac firewire cards a new life.

Ordered the Apple Care extended warranty this morning. It was $169.00 from Apple. Had a bad experience w/Ebay. Took FOR-EVER to fix. Won't ever make that mistake again.

Thanks again.

Well, you do have to be a little bit careful on eBay, but trouble is usually easy to spot.

When you buy AppleCare in a store, you get a box containing a card with a number on it.

You go to Apple's web site and register the number, presto you're covered.

I've bought Applecare on eBay twice in the last year, and picked sellers that e-mail you the Agreement number immediately (usually listed as "Local Pickup").

Apple confirmed that it was OK each time, and I have checked with others.

I of course make it a point to pay by credit card so that if there is a problem, I get the charge reversed the same day. Been there, done that, it worked.

Paypal has their own dispute process, but it takes a month.

I am going to assume you are using Boot Camp and not Parallels.

Have a look at this.

It outlines a problem related to performance on Windows with Firewire. Essentially the firewire is slowed down by a reg setting.

I don't know if this is the cause of your problems, but it is worth a look.

Peter

Oh, the classical S100 bug, brings back memories. First seen with some Creative (of Soundblaster fame) product I think.

That is certainly a possibility, especially if this didn't get rolled up into SP3 (I assume he got SP3 running).

The NVRAM reset may also be needed.

This is exactly the kind of thing that made me switch to Mac.

The following file is available for download from the Microsoft Download Center:

Download the Update for Windows XP (KB885222) package now.

Release Date: December 17, 2004

For more information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Prerequisites
To install this update, you must have Windows XP SP2 installed.
Restart information
You must restart your computer after you install this update.
Update replacement information
This update is not replaced by any later hotfix or update.
Registry information
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows


After you install this update, if you add a host controller for a new 1394 device to your computer, you must add or modify the SidSpeed entry in the Windows registry for the new 1394 host controller. To do this, follow these steps:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\1394_hc_hw_id\1394_instance_id\Device Parameters
If the SidSpeed value does not exist in the right pane after you click the Device Parameters subkey in step 2, create it. To do this, point to New on the Edit menu, click DWORD Value, type SidSpeed, and then press ENTER.
Right-click SidSpeed, and then click Modify.
In the Value data box, type one of the values that are shown in the following table, and then click OK.
Value Speed
0 S100 speed
1 S200 speed
2 S400 speed (default value)
3 S400/S800 speed (Windows XP Service Pack 1 [SP1] value)
Note If you try to use a value that is larger than 3, SidSpeed will use a value of 0 (S100 speed).
Quit Registry Editor.
To locate the FireWire controller information, follow these steps:
Open Device Manager. To do this, right-click My Computer on the Start menu, click Manage, and then click Device Manager under System Tools. You can also click Properties under My Computer, and then click Device Manager on the Hardware tab.
Locate your FireWire controller in the IEEE 1934 Bus host controllers section.
Right-click the FireWire controller entry, click Properties, and then click the Details tab.
Click Device Instance Id. You see a string of letters and numbers that is similar to the following:
PCI\VEN_104C&DEV_8020&SUBSYS_00D81028&REV_00\4&19FD8D60&0&60F0
The information between the two slash marks (\) is the “1394_hc_hw_id". “VEN_104C&DEV_8020&SUBSYS_00D81028&REV_00” is the hardware ID in this example. The information that follows the second slash mark (\) is the “1394_instance_id”. “4&19FD8D60&0&60F0” is the instance ID in this example.
File information
The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
-----------------------------------------------------------------
04-Nov-2004 20:59 5.1.2600.2549 6,656 Cstupd1394sidspeed.dll
04-Nov-2004 19:33 5.1.2600.2549 61,184 Ohci1394.sys

It could make your head explode.

I did the KB 885222 update a long time ago.

SP 3, thanks to your help, is now installed.

The problem persists. I suspect it is the Agere Firewire card, as you mentioned.

I live 120 miles from the nearest Apple tech, but I'm planning a trip soon.

Thanks again.

Did you try the 'reset nv-ram and reset all' from the EFI ("BIOS")?

This has apparently helped some people with your symptoms (nameless firewire interface).

did the KB 885222 update a long time ago.

Did you verify that the correct Firewire device is set for S400? I have had situations where after the SP3 update, the settings were reverted/lost.

Peter