Comments

Caruso wrote on 12/18/2004, 12:17 AM
I was surprised that I was able to use Firefox 1.0 to follow your link and download that update. Usually, I get a message stating that I have to use MSIE.

Don't know if this update will fix my little aggravation. When running SP1 on my "old" 0.9 gHz machine, often, during power up, my firewire drives would not enumerate properly. I might spend half an hour unplugging and then re-connecting them before I could get XP-Pro to recognize them. There was a downloadable fix for that problem (heads-up for it I found on this forum, of course!!), and, once installed, that enumeration problem was vanquished permanently. Then, I purchased a new machine that was supplied with the XP SP2 update disc.

Since installing SP2, I have again been plagued with a similar enumeration problem. The update file that fixed the problem in SP1 would not install on SP2, so, I've been battling this goofy problem for a few months, now.

Here's a description of my current problem: I move my new setup about quite a lot. The processor is a PCX Shuttle 3.0 gHz machine to which I hook six external firewire drives. If I fail to hook the drives up exactly as they were when I last powered down my system, then, the system takes what seems like forever to power up (seems to hang on that black "Windows" screen with the green bars thingy running across the bottom). When the desktop finally appears, if I check MY COMPUTER, I may see one or two, or perhaps none of my six external drives in my list of drives.

At that point, my only choice is to disconnect all externals, and plug each drive in separately. Sometimes, it may take 30 seconds or so after I plug-in one of those drives before I hear that da-DUNK sound that signals XP's recognition of a newly hot-plugged external device. Then, I see the little window appear showing that the system is scanning the drive and offering me an option to open the folder, "play" a file, or do nothing.

I have to repeat this process with each of the six drives until all are properly "mounted" (I think that's the correct term). Once I've successfully completed this routine, I can power down and back up without a problem until the next time I inadvertently alter the setup (alteration can be as simple as forgetting to turn on one of the external drives before booting up).

If I don't pull all external drives when this happens, and simply try to unplug/re-connect those that have not enumerated, I might get them all mounted, but, then, they start randomly losing their connection, or Windows starts flashing these ridiculous "delayed-write" errors telling me that the data on drive "M" or whatever has been lost. Good thing I know not to take most Windows messages at face value.

Has anyone else experienced a similar problem - or is my little glitch unique to me?

I'm not panicked when this happens, since I now know exactly how to overcome the problem, but it can certainly set a client on edge if it occurs at the start of a recording session, and it is a huge waste of my time.

Thanks in advance for any tips.
Caruso
Caruso wrote on 12/18/2004, 12:30 AM
Well, I wanted to edit the previous message, but some gremlin will not allow it. I wanted to clarify my statement that alteration, as I called it, can be as simple as having one of the drives off during a subsequent boot up, or having the drives hooked up in a different order than they were when I powered down.

If, for instance, one of the drives is off, and I notice that hanging during boot up that I described in the previous post, it doesn't seem to matter whether I wait for boot up to complete or interrupt the process by turing off the computer - there is no way for me to re-establish the arrangement of those drives so that XP will recognize them all without going through the one by one exercise I described in my previous post.

When that fix was installed on my old SP1 machine, it didn't matter what was or wasn't plugged in during boot up, nor did Windows seem to care in what order the drives occurred on the daisy chain. Whatever was plugged in got enumerated, whatever wasn't would be enumerated as soon as I plugged it in.

Sorry to be so wordy, and I hope I've explained myself clearly. Most of all, I hope that, after installing the aforementioned SP2 update, I can briefly report back that IT WORKED!!

Caruso
Bill Ravens wrote on 12/20/2004, 6:34 AM
This fix won't work with my Pyro DV Drive. I had to copy all the 1394 drivers from SP1 over to SP2 to fix the problem.
NickHope wrote on 12/20/2004, 7:55 AM
There's a lot of discussion on this patch here:

http://www.neowin.net/comments.php?id=26338&category=main

Caruso, please do let us know if it fixes your problem. I get drives dropping off the bus and delayed write failures and nonsense like that, especially on my laptop, so I'm interested in this.
NickHope wrote on 12/20/2004, 9:48 AM
I took a read of the support article concerning this update at at http://support.microsoft.com/kb/885222

The speed of the host controller appears to be governed by a new DWord called Sidspeed. And I quote...

DWord value 0 = S100 speed
DWord value 1 = S200 speed
DWord value 2 = S300 speed (default value)
DWord value 3 = S400/S800 speed (Windows XP Service Pack 1 [SP1] value)

I was a bit concerned to see that the default value is S300 (DWord value 2). Surely IEEE 1394 cards are mostly faster than this, aren't they, and we should be changing this DWord to the value 3 (S400/S800)? And how would we find out what speed our IEEE 1394 cards are anyway?