Windows Firewire Issue!

[Blinddot]

You don't give any details on what you are trying to do, or if is FW800 o FW400... but anyway there is a known issue with firewire on Win XP SP2, that could be the reason of your mysterious problem

RME Tech Info - FireWire 800 under Windows XP SP2



regards

[theblue1]

Originally Posted by Blinddot

You don't give any details on what you are trying to do, or if is FW800 o FW400... but anyway there is a known issue with firewire on Win XP SP2, that could be the reason of your mysterious problem

RME Tech Info - FireWire 800 under Windows XP SP2



regards

Interesting read but as I read it, it would result in severely degraded performance, not failure to recognize.

(BTW, the ish is with FW800, as per that RME write up.)

[Bob Olhsson]

Sounds like a cable. Pee-Cees sem to be more sensitive to cable problems than Macs. I jumped through hoops before I discovered a huge percentage of brand new firewire cables are defective right out of the package.

[Blinddot]

oops!!

I just did not read the last sentence on the first post... That is why I called the problem mysterious, I guess I should have paid attention when reading, sorry

If it's a problem with FW HD drives Id try to boot from linux to check that it is not a hardware problem


regards

[Blinddot]

Originally Posted by Bob Olhsson

Pee-Cees sem to be more sensitive to cable problems than Macs.

Saying that, doesnt make any electronic sense to me, or at least by reading it quick, since there is a wide variety of FW controllers, and motherboard manufactures in the market, It's like putting all PC manufactures in the same pot.. or saying that aple motherboard manufacuturing is much superior than any other motherboard or FW controller in computer world, which to be honest is hard to believe for me.. You might just be talking about personal experiences with poorly built FW controllers or PC motherboards, in fact most of the best controllers manufaturers make drivers for both OSX and Win (i.e. Adaptec)

Besides that, Doesn't apple build PCs, since intel swap?

I think the thing is that in non-apple-PC world ther is any kind of manufaturer, from bad to good, so you have to choose well, in mac world there is only one mufacturer, apple, and they better do things properly or mac users will suffer from it.. fortunatly I personally think they make good computers hardware-wise, not very silent but good anyway.


regards

[theblue1]

I'll be the first to stick up for Windows PCs when I think they're being unfairly picked on but I have to say that -- while I don't have any specific info or knowledge of such problems and I don't seem to have any such issues with the FW interface on my laptop or tower and my MOTU 828mkII (except for an isolated issue with regards to "mouse/video" noise when both the laptop's internal audio and the MOTU audio are both routed to the same control amp -- which is easy to work around and clearly not software related) -- it's not hard for me to understand how a given OS could have a more or less robust handling of a set of i/o protocols.


Also, I've read a lot of posts by Bob and, not only can I not recall, off the top of my head, any with significant factual errors, but I've never really seen any platform bias, either. FWIW.

[Bob Olhsson]

The thing about both Firewire and USB is that there is tons of error correction buffering going on that makes the symptoms of an intermittent cable very non-intuitive. I have both Macs and Pee-Cees and prefer the latter because of the software available for mastering.

The first time I tried using firewire with a Pee-Cee my computer couldn't see the drive yet it came right up when I plugged the cable into my old Mac. After reinstalling XP twice, my wife asked if I had checked the cables. I told her yes, the cable worked fine with the Mac so I assumed it must be ok. Finally in desperation I swapped in another cable and the drive came right up. A trip to Comp USA yielded another defective cable and it took five tries to find one that worked with the PeeCee.