Infoseite // WinXP/SP2 - What to do to make firewire work?

Frage von Markus:


Hi,

regularly, the problem arises that not having Firewire WinXP/SP2 properly. An uninstall the Service Pack 2 is not always possible, and most users are not synonymous willing to buy an older WinXP version (without SP2) and / or install.

As a possible solution was usdiskutiert, the SP1 aufzuspielen-Drivers, which leads to my last knowledge, but not the desired result.

S.Euch My question: Who has WinXP/SP2 and thus had problems? How did you solve these problems?



Antwort von Markus:

The issue is still current.



Antwort von uifei:

Mmm, so it has proved to me the way quite well:

1. PC
2. Firewire devices to connect and switch on
3. Start PC

I use the Canopus ADVC 300 of as synonymous what is very interesting to the user guide:

Procedure as described above, and should any s.and unplug the Firewire connections to avoid during operation.
It can happen synonymous, that the calculator then can not boot when the machine is running while the PC s.and off or lies.

Windows XP prof. hinbekommen should have no problems (updates here, but very important) at home (well, an OS what the world does not need), but got replaced by a separate firewire port card, etc. .. because hubfunction



Antwort von DjDino:

There is a FireWire patch for XP SP2 to solve the synonymous with some device detection problems is: http://www.microsoft.com/downloads/details.aspx?FamilyID=ca0f2007-18b5-4112-8bd6-8bf4bd3130b9&DisplayLang = de s.30.03.2005 The patch has been reworked and is now in Version 2 (KB885222-v2) If the patch has not, or even the old first version might be worth trying to patch problems.

Also, there is an optional update which may STILL A trailer with SBS-2-fix devices (eg, Firewire) to: http://www.microsoft.com/downloads/details.aspx?FamilyID=a2091337-a0ea-4b34-b19f- b6ec04c1f2d2 & displaylang = en
"Optional" heist that is not offered via Windows Update as it is intended only for people with this specific problem has been around 07.10.2005 also in a newer version 2.Auch this update could help.

@ Markus Are these updates in the FAQs or the like anyway?

These updates help but only if the FireWire controller with the default WinXP drivers and not the manufacturer drivers running (many motherboard on-board controllers do).

If the updates do not help s.besten an external FireWire card to your PC and get stuck on always see the freshest producers in the INET driver to download and do not use (those on the supplied CD-ROM Drivers who may be already quite old and therefore less synonymous Compatibility fixes may be included) sometimes synonymous helps a firmware update if your camcorder supports.



Antwort von DjDino:

"DjDino" wrote:
@ Markus Are these updates in the FAQs or the like anyway?

WOW, since the stands and much more in it already:
http://forum.slashcam.de/wenn-firewire-nicht-richtig-funktioniert-vt27682.html
Sorry, overlooked! :)

What I have rausgefunden times:

For MAGIX video programs (Magix Video -Deluxe/Videos on CD and DVD, all versions), there is perhaps a useful DV Card Drivers Help Tool.

http://site.magix.net/deutsch/startseite/support/patch-download/ -> Register as a client-> bottom then on the main folder: "Download" -> MAGIX tools (tools) -> Misc .-> DV Drivers Correction> Description:
[code: 1:956 c35b3c4]
Description
The tool eliminates "false" DV Card Drivers.
Also known as IEEE1394, FireWire or i-link.
[/ code: 1:956 c35b3c4]
(not for e-versions of "appropriate video)



Antwort von Markus:

---> Ruck

Maybe someone else knows a workaround or a trick that can help in certain cases?



Antwort von Markus:

Dto.



Antwort von Charly23:


1. I've been trying for several weeks to reach a solution themselves to this posting here is seen as a desperate act in terms of requests for help to * g *, as my research on the net has not been until now the solution of the Probs, not laziness so;)
2. What I could find out:

The Windows Service Pack 2 and the FireWire standard is - purely on principle - an ambivalent affair, as the passing thoughts of various users seeking help in various forums.

My experience with Windows XP Prof. SP 2 incl: null Probs, but I have my old PC do not need to use a Firewire hub of the motherboard (because such did not exist), but a separate Firewire card (which was installed had) with their own drivers in use. Now: new PC with Asus motherboard [asus A8N32-SLI Deluxe (chipset: nforce slix16, pci: 3, pci-e x16 lan (2) x4 (1): 2x1000 mbit / s). 6xSATA (-raid), Firew, headpipe], ie, including Firewire.

The point I want: It's a software problem that is probably caused by an incorrect driver configuration) (my conclusion. About the assistance that provide the network and most of this board, I have indeed received some evidence, however,'s has not so far been enough to find solutions. The hardware is in order: the day I cam via firewire from a friend (I mean "old" PCs have sold, tried with Firewire card as I said). The cam is instantly recognized. The question now is whether I even arrived to a software technology solution or whether I should buy a Firewire card (and I still do not know whether I have the necessary space for such in the Tower, is quite cluttered).

So far tried:
Hardware: Camcorders-/Firewire-Kabel tested camcorder is immediately recognized.

Software: See synonymous: Wenn Firewire nicht (richtig) funktioniert

Mögliche Ursachen:

1st Operating system Windows XP with SP2
2. Wackelkontakt s.4-pol. Firewire times
3. Virus scanner (or other program) running in the background
4. The hard drive is highly fragmented
5. Not enough free space on the hard drive
6. Unsuitable Capture Software
7. Conflict of Firewire card with other PC components
8. DirectX version is not currently
9. Firewire cable defective
10. DV port s.Camcorders broken
11. OHCI FireWire card is not capable of
12. Misc.

1. can be excluded, since on the PC of my friend Prof. synonymous Windows XP is installed including SP2, Cam will be recognized over FW.
2. deto
3. sampled, because it does not lie.
4. it is not
The points 5 and 6 assume that the cam is at least recognized auto.
7. I suspect it's located.
8. DirectX 9.0 c installed
9. so
10. so
11. no "firewire card"
12. Misc. That would be synonymous ne way: D

So far, so bad. Although I am now better informed by my research a little bit, but not exactly a solution closer. At the moment I am with the following solutions:

After the Microsoft hotfixes (see thread "WinXP/SP2 - Was tun, damit Firewire funktioniert?", die eine tadellose Firewire-Funktionalität synonymous unter SP2 ermöglichen sollen, installiert wurden, jedoch keine Problemlösung erbrachten, entdeckte ich den Kommentar eines Users [thread siehe url ebd., beitrag vondjdino]:

Diese Updates helfen aber nur wenn der FireWire-Controller with den WinXP-Standardtreibern and nicht den Herstellertreibern läuft (bei vielen Motherboard-OnBoard-Controllern der Fall).

Quote: "WinXP/SP2 - Was tun, damit Firewire funktioniert?", die eine tadellose Firewire-Funktionalität synonymous unter SP2 ermöglichen sollen, installiert wurden, jedoch keine Problemlösung erbrachten, entdeckte ich den Kommentar eines Users [thread siehe url ebd., beitrag vondjdino]:

Diese Updates helfen aber nur wenn der FireWire-Controller with den WinXP-Standardtreibern and nicht den Herstellertreibern läuft (bei vielen Motherboard-OnBoard-Controllern der Fall).

[...] If the updates do not help s.besten an external FireWire card into the PC and put on drivers to always see the freshest producers (in the download and do not ever use INET



Antwort von steveb:

It is the Firewire Firewire card in the glossary explains the system correctly identified, or is already the error? Then maybe the drivers of TI on Microsoft to change or how zerc times wrote exchange the PCI slot. Do not take the slot next to the graphics card!

That sounds plausible for me, just as I do that? Maybe someone can help me, Oh yes:)

something like this:

Control Panel - Device Manager, select Properties Select Hardware-Other Drivers - drivers of disk can not select / search and replace but rather specify your own source drivers.






Antwort von Charly23:

"steveb" wrote: It is the Firewire Firewire card in the glossary explains the system correctly identified, or is already the error? Then maybe the drivers of TI on Microsoft to change or how zerc times wrote exchange the PCI slot. Do not take the slot next to the graphics card!

That sounds plausible for me, just as I do that? Maybe someone can help me, Oh yes:)

something like this:

Control Panel - Device Manager, select Properties Select Hardware-Other Drivers - drivers of disk can not select / search and replace but rather specify your own source drivers.

Thanks for the answer, but I now stand completely on the line as it seems, for where is the "own source" .. where am I to get the drivers?



Antwort von Charly23:

"Charly23" wrote: "steveb" wrote: It is the Firewire Firewire card in the glossary explains the system correctly identified, or is already the error? Then maybe the drivers of TI on Microsoft to change or how zerc times wrote exchange the PCI slot. Do not take the slot next to the graphics card!

That sounds plausible for me, just as I do that? Maybe someone can help me, Oh yes:)

something like this:

Control Panel - Device Manager, select Properties Select Hardware-Other Drivers - drivers of disk can not select / search and replace but rather specify your own source drivers.

Thanks for the answer, but I now stand completely on the line as it seems, for where is the "own source" .. where am I to get the drivers?

As I have described a buddy a few minutes ago via ICQ the problem, he said I ought to hire tackle the problem on the motherboard. Have an Asus A8N32-SLI Deluxe. Have a problem with FireWire AND googled and came across the following link might prove helpful:





Antwort von Gast1:

My firewire card regularly denied) (all 4 to 8 weeks multiplied by the service. I operate on ussynonymous an external FireWire hard drive and note the failure of typical s.Fehlen the drive.
I then delete the drivers in Device Manager, the firewire card, which is then automatically reinstalled the next time and Firewire working again.



Antwort von mcmeikel:

It's become crazy.

Win XP Pro SP2
Panasonic DV NV-GS17 is displayed in Device Manager under Imaging Device.
Start Pinnacle Studio 9.3 to connect and go - no DV device error.

Time it is detected times not. Who found ne solution?
(Studio V.7 Deluxe Retrail D)

If the cam is detected Pinnacle crashes during the recording.



Antwort von Lilo:

Have found no functional response.

Can watch my movie with Firewire while s.Laptop, not capture, however.

Laptop: SonyVGN-FE28B
Camera: SonyDCR-HC40E PAL

Who can help?

Thank you



Antwort von beno:

Had the same problem with the above water MV20i.
Only with SP2 and then with SP3 also was the spitting away!

Previously, I had to work without the protection of SP2, if I wanted to make movies with the Pinnacle and Magix of the camera in the Compila.

Vile happiness and fun
mfGruss Beno



Antwort von beno:

Had the same problem with the above water MV20i.
Only with SP2 and then with SP3 also was the spitting away!

Previously, I had to work without the protection of SP2, if I wanted to make movies with the Pinnacle and Magix of the camera in the Compila.

Vile happiness and fun
mfGruss Beno