Re: firewire problem
- From: "Mark" <Mark@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 5 Jun 2005 14:10:01 -0700
Here is a transcript of my latest conversations with Graham Hughes for those
interested:
"I just tried his Sony Digital 8 on my computer’s firewire and it connected
like it was supposed to. (mine won’t)
He does have sp2 installed. I will let you know what else I find.
Mark
Graham: Mark,
Thanks for the info.
It is important to find out for sure that your friend’s pc is either running
sp1 or 2. If his is running SP1 and it doesn’t work, it does point away from
SP2 causing the trouble, but not definitely, as different pc’s etc etc…….
I will await your testing cam and asking him about sp2.
Cheers
Graham
--------------------------------------------------------------------------------
Mark: I will answer your questions in the order asked.
How old is the cam? - Under 1 year
Is it PAL /NTSC? - NSTC
Has the cam ever worked on your pc or any other pc? - Not that I am aware
of, but it does work with USB
When was the last time? -
Can you remember if anything odd happened when it was last connected? -
Nothing
Do you use mains power when connecting? - Tried Both
Is your friend’s pc sp2 as well? - Unsure, but likely. New PC’s in the
store I tried unknown as well.
Can you try his cam on your pc, just for confirmation the pc is fine? I
will try and let you know
Can you find a friend with an SP1 pc to try your cam on? This should rule
out the firewire port being damaged on the cam, which does happen quite often
unfortunately. -- I will try to find one and let you know
Can you try the fixes listed on my site, or the ones you fell happy doing
and let me know if anything improves? I tried all the fixes and replaced the
sp2 drivers with sp1 ones and then changed the name of sp2.cab to sp2.ca_.
newer drivers were not reinstalled. The names and dates of the files are
below. There are no other locations with these files dated differently on my
computer.
1394bus.sys is 5.1.2600.1106 (xpsp1.020828-1920) August 29, 2002
arp1394.sys is 5.1.2600.1106 (xpsp1.020828-1920) August 29, 2002
nic1394.sys is 5.1.2600.1106 (xpsp1.020828-1920) August 29, 2002
ohci1394.sys is 5.1.2600.1106 (xpsp1.020828-1920) August 29, 2002
enum1394.sys is 5.1.2600.0 (xpclient.010817-1148) August 17, 2001
msdv.sys 5.1.2600.0 (XPClient.010817-1148) August 17, 2001
"Treeman" wrote:
>
> Mark, it may have been your renaming of SP2.cab to SP2.ca_
> A .cab file (cabinet file) is a valid XP subset of drivers compressed
> within the cabinet. Check which drivers got loaded in device manager,
> are they Sp1 or SP2 versions? The dates are the clue. If SP2 drivers
> got put back, you should change the SP2.cab folder to SP2old.cab
> Best,
> Treeman
>
>
> --
> Treeman
>
>
> ------------------------------------------------------------------------
> Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
> View this thread: http://www.msusenet.com/t-1870490627
>
>
.
- References:
- Re: firewire problem
- From: g
- Re: firewire problem
- From: Mark
- Re: firewire problem
- From: Graham Hughes
- Re: firewire problem
- From: Mark
- Re: firewire problem
- From: elleno
- Re: firewire problem
- From: Treeman
- Re: firewire problem
- Prev by Date: Re: Repair Windows Movie Maker 2
- Next by Date: RE: Cannot Capture Video - its an XP SP 2 problem
- Previous by thread: Re: firewire problem
- Next by thread: Re: firewire problem
- Index(es):
Relevant Pages
|