Slashdot Mirror
XP Service Pack 2 Breaks FireWire
Diluted writes "FireWire Depot is reporting about a problem with Service Pack 2 for Windows XP. Apparently not liking the competition from 1394b, Microsoft decided to limit S800 devices to a quarter of their speed capability."
I thought this was fixed in a subsequent patch?
Why the hell would Microsoft consider a device connection bus standard to be competition? That statement makes absolutley no sense.
Error: PANTS NOT FOUND. Press <F1> to continue.
I'm glad to see that they have a fix for the problem listed. I think it's nice that MS acknowledges the problem with a fix. Not sure how degrading the speed is a "fix" or a security feature...
"Patriotism is supporting your country all the time, and your government when it deserves it." Mark Twain.
"Apparently not liking the competition from 1394b"
Since when did Microsoft compete with FireWire? The only real competition to 1394 is USB, and that's an Intel technolog.
That, and Microsoft has already released a patch.
The only use i see for that much speed on a peripheral bus is for video applications and for high speed backups. for pretty much anything else, it's a lot of wasted bandwidth.
to be honoest, if all it broke on my machine was firewire I'd be okay, but it also takes down the internet while it's at it, forcing me to have to restart the dhcp service about every 30 seconds or so for it to actually allow me to get out on the net. Has anyone else had this problem, if so how did oyu solve it? (sorry, I'm a Debian person, not an XP person.)
-------
Support Indy Music. Buy
http://support.microsoft.com/kb/885222
Not fixed in a patch or released as a hotfix, but their 'fix' is for the person affected to edit their registry. Your average user is not going to want to edit their registry.
As far as the competition angle... USB is intel's protocol, firewire is largely driven by apple... that was my point about competition.
The real issue here is taht Ms's monopoly allows them to crush a protocol if they so desire.
Service Pack 2 has been out for what, 6 months?
And you just noticed that Firewire was broken?
Why are some people just starting to complain NOW, months after SP2 has been released?
For the record, I haven't had any noticable problems with SP2. It works fine for me.
Some of our developers had problems, but that's because they weren't smart enough to to deal with the integrated firewall. They were complaining when *spyware* was attempting to establish an outside connection.
Also for the record, I'm not the windows admin.
94% of Repubs and 21% of Dems voted to renew the Patriot Act
You really start to notice the difference with sustained file transfers, such as large files or backups.
If you're not one of the poor saps whose laptop has a 4-pin 1394 port, you also really notice not having to carry a power cord and wall wart for your external hard drive everywhere with you.
Seriously, though, digital camcorders make up the bulk of firewire-connected electronic devices. Why hamstring their performance under the auspices of a service pack? I'm sure the fix makes other things speedier while firewire transfers are going on, but at the expense of the transfer itself? Why?
"Murphy was an optimist" - O'Toole's commentary on Murphy's Law
I use it often to transfer video from my DV camera, and with my external DVD burner. I prefer it to USB 2.0. Also nice to use to link 2 pc's to tranfer files. I thought everyone used it.
You're kidding right? I use firewire everyday, at work and at home. Work: connect an ipod to, also my external firewire drive which I take between home and work. Home: video editing using my camcorder with firewire output on it. Beats the crap out of analog conversions using a haupauge card or something like that.
Could someone clarify?
I thought the problem with Firewire was resolved with a patch. But the resolution also mentions a Registry hack.
However, the Download page does not mention any registry hack.
Is this problem fixed by the patch, or by a registry hack? Either? Both? Neither?
94% of Repubs and 21% of Dems voted to renew the Patriot Act
Microsoft just dealt what many leading experts think will be a fatal blow to the primary competition of Windows XP, 1394b, also known as Firewire. Now that Firewire has been dealt with, Windows XP will have a much better chance of maintaining market share.
I used to bulls-eye womp-rats in my pants
Patched November 4, 2004.
http://support.microsoft.com/kb/885222
WinXP updates break Canon Multipass devices. This happened to my client. Their devices mystically stopped to work one day. After reinstalling WinXP, they resumed their operation for one or two days. Uninstalling "hotfixes" helped!
Now they have to use SP2. Say goodbye to canon multipass... Canon refuses to fix drivers.
I found this out the hard way.
I have 2 FW devices: a canopus media bridge (advc 100 - converts analog video to FW/dv) and a regular old external FW disk (ide bridge inside).
plug one in, wait till its seen, then plug the other one in. both are seen.
do some video capture to the external FW drive. works fine.
unplug the camera. leave the drive connected.
oops! drive goes from NTFS to 'raw' and loses its 'letter'.
have to reset the whole thing to get the drive to be seen again.
buggy buggy buggy. sigh. well, what do you expect?
lesson learned: don't share bus types on M$. I'm going to try using a hotswap SATA drive instead of FW drive. (from what I hear, even THAT isn't a guarantee - the intel SATA chipset doesn't ALLOW hotplug. so I'll have to get a promise controller or maybe my preferred brand, SiliconImage).
I'm hoping that by using diff bus types, I can plug and unplug the camera and NOT lose my disk device id.
--
"It is now safe to switch off your computer."
That's painful. The last S100 bus system I had only ran at 6MHz, and only had 64kb of RAM. But hey, those dual 8" floppy SSDD disk drives were schweet!
Why do you prefer it to USB 2.0? I understand if you don't like how USB 2.0 isn't always actually 2.0 but sometimes is set up as 1.1, but a true USB 2.0 interface is faster than firewire. 410 MB/s as opposed to 400 MB/s. Its not a big difference, but while firewire devices and even cabling are so much more expensive, I'll stick with USB.
Look on the page linked to in the article. They list a patch to set firewire back to its original speed.
This is old news. Next!
Don't thank God, thank a doctor!
Hmmm...XP SP2 has been out now how long? And, this problem was just "found"?
Peek into the Future:
Year 2025 - It's been reported that Microsoft's Windows XP SP2 has broken...THE SAN ANDRES FAULT. In-depth coverage at 11!
"It's not rocket science, Smithers! It's only brain surgery!" --Mr. Burns
"The open bias on Slashdot gets worse every day. I'm done with this POS site. News is supposed to be objective."
I love how the only observant post on this page was modded troll.
1394b (the affected item in this discussion) afaik is 800MB/s
Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.