cannot connect Sony CamCorder

Not sure if this is the right group. I'm trying to connect a Sony TRV530
camcorder via FireWire 1394 cable to harvest video. I did this many months
ago, but now it doesn't want to work. I cannot get WinXP to recognize the
camcorder. This is what I've done so far...

1) removed and reinstalled the 1394 PCI D-Link card
2) bought a new cable
3) Spoke with Sony twice to confirm all camera settings
4) When connected and I switch the camera to VCR mode, WinXP will give the
sound that it detected something via Plug N Play. Sometimes the "What
Action.." dialog box will appear for a couple seconds, then immediately
disappear. Neither Movie Maker or Pinaccle Studio 9 will recognize the
camcorder.

All that's left is to condemn the camera. Sony doesn't believe the camera is
at fault and of course they want $269 to bench test it. Does anyone have any
idea on how I can test further? I don't know anyone else that has a 1394
setup.

thanks!

Problems, Problems; XP SP2 & Firewire Drivers.
You can find info here at Mr. Graham Hughes website.
'My Camcorder has stopped working since installing SP2'
(http://www.myvideoproblems.com/Probl...ngUnderSP2.htm)

Best,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

I'm failing miserably here.
I tried swapping out the msdv.sys file - no change.
I tried the hot fixes. Made it worse, so I reverted back.
Anyone know of any other KB articles or solutions?
thanks

"Treeman" wrote in message
...

Problems, Problems; XP SP2 & Firewire Drivers.
You can find info here at Mr. Graham Hughes website.
'My Camcorder has stopped working since installing SP2'
(http://www.myvideoproblems.com/Probl...ngUnderSP2.htm)

Best,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

Shank,
Since I'm running SP1 I don't have the firewire or camera problem. The
following has been a fix that has worked in the past for some. Your
mileage may vary.
It involves reverting back to SP1 drivers, by renaming the SP2.cab
folder so it doesn't automatically reinsert SP2 drivers on boot.
(you will have to have these SP1 files in a folder on your hard drive)
Go to C:\WINDOWS\Driver Cache\i386 & C:\dllcache in SP1 and copy out
the
following files
1394bus.sys is in C:\Windows\System32\Drivers
arp1394.sys is in C:\Windows\System32\Drivers
nic1394.sys is in c:\Windows\System32\Drivers
ohci1394.sys is in C:\windows\System32\drivers
enum1394.sys is in C:\windows\system32\drivers
Copy out the following files to a new folder you can call
"Firewirefix," (without quotes)
If you don't have these files they are on any SP1 CD in the i386
folder.
(none of them will have a date older than 2004)


In your case I would;
1. Rename the SP2.cab file folder to SP2old.cab, shut off the
computer.
2. Remove the 1394 PCI D-Link card.
3. Start the computer normally, let XP SP2 see the card isn't present.
If it still shows up in System, Hardware, Device Manager, now would be
the time to uninstall the device from the drop down menu.
4. Shut off computer.
5. Plug in the 1394 D-Link card, start the computer.
If XP finds the "new'" device and wants drivers, let it use the SP1
drivers you've saved in the Firewirefix folder.
The only other fixes I've seen work was the purchase of a new firewire
card, a clean install of SP2 & updates, uninstalling SP2, or just
giving up.
Please post back your success or failure for the benifit of others.
Best,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

I'm finally capturing footage! Woo Hoo! It was reverting back to SP1 drivers
that did it. I thought I did that before, but evidently missed 1 or
something. Not sure. What I did was ...
1) Renamed SP2.cab
2) Copied those 5 files from SP1 into a temp folder for convenience
3) Using Device manager, I uninstalled the 1394 card
4) Renamed those 5 files in the ../system32/drivers folder (so I could
revert if necessary)
5) Copied those 5 files into ../system32/drivers folder
6) Rebooted
7) Success!

thanks!


"Treeman" wrote in message
...

Shank,
Since I'm running SP1 I don't have the firewire or camera problem. The
following has been a fix that has worked in the past for some. Your
mileage may vary.
It involves reverting back to SP1 drivers, by renaming the SP2.cab
folder so it doesn't automatically reinsert SP2 drivers on boot.
(you will have to have these SP1 files in a folder on your hard drive)
Go to C:\WINDOWS\Driver Cache\i386 & C:\dllcache in SP1 and copy out
the
following files
1394bus.sys is in C:\Windows\System32\Drivers
arp1394.sys is in C:\Windows\System32\Drivers
nic1394.sys is in c:\Windows\System32\Drivers
ohci1394.sys is in C:\windows\System32\drivers
enum1394.sys is in C:\windows\system32\drivers
Copy out the following files to a new folder you can call
"Firewirefix," (without quotes)
If you don't have these files they are on any SP1 CD in the i386
folder.
(none of them will have a date older than 2004)


In your case I would;
1. Rename the SP2.cab file folder to SP2old.cab, shut off the
computer.
2. Remove the 1394 PCI D-Link card.
3. Start the computer normally, let XP SP2 see the card isn't present.
If it still shows up in System, Hardware, Device Manager, now would be
the time to uninstall the device from the drop down menu.
4. Shut off computer.
5. Plug in the 1394 D-Link card, start the computer.
If XP finds the "new'" device and wants drivers, let it use the SP1
drivers you've saved in the Firewirefix folder.
The only other fixes I've seen work was the purchase of a new firewire
card, a clean install of SP2 & updates, uninstalling SP2, or just
giving up.
Please post back your success or failure for the benifit of others.
Best,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

Shank,
Shhhhhh! I got some folks in the, "SP2 or die" camp p*ssed at me for
putting out this solution. But I'm glad it worked for you. It's great
that you can now be in the "Start Something" Experience, instead of
being in the "Fix Something" Experience!
Best,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

Shank !,
Thanks for the problem posted....and ur final success.

Treeman !,
Thanks for the patient in solving this problem. I myelf also having this
kinda problem after I re-install from fresh my pc with WinXP Pro Sp2 when my
DAMM so call branded digi video cam SONY cannot work with the famous OS held
by the richest person in the WORLD.
I was searching high and low for this solution myself also in MICROSOFT
servers.

I like this brainstorming communities...

-joshua siew

"Treeman" wrote:


Shank,
Shhhhhh! I got some folks in the, "SP2 or die" camp p*ssed at me for
putting out this solution. But I'm glad it worked for you. It's great
that you can now be in the "Start Something" Experience, instead of
being in the "Fix Something" Experience!
Best,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

But why does everyone blame Bill, it's not his fault, it's the camcorder
manufacturers not using the correct firmware in their camcorders, which is
why you have to roll back to old drivers from MS which allowed the use of
non-compliant firmware. Bill actually tried to be more compliant, poor chap

The solution is on micorsofts servers, KB893008
Now other problems may be his fault, but not this one

Also look at the mnay problems people face with Sony HC42's and Macs, they
don't work together because of Sony's firmware, and this can't be Bill's
fault can it???? LOL LOL

Graham

--
Graham Hughes
MVP Digital Media
www.myvideoproblems.co.uk
www.dvds2treasure.com
www.simplydv.com


"joshua siew" wrote in message
...
Shank !,
Thanks for the problem posted....and ur final success.

Treeman !,
Thanks for the patient in solving this problem. I myelf also having this
kinda problem after I re-install from fresh my pc with WinXP Pro Sp2 when
my
DAMM so call branded digi video cam SONY cannot work with the famous OS
held
by the richest person in the WORLD.
I was searching high and low for this solution myself also in MICROSOFT
servers.

I like this brainstorming communities...

-joshua siew

"Treeman" wrote:


Shank,
Shhhhhh! I got some folks in the, "SP2 or die" camp p*ssed at me for
putting out this solution. But I'm glad it worked for you. It's great
that you can now be in the "Start Something" Experience, instead of
being in the "Fix Something" Experience!
Best,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

Both Bill and manufacturers are to blame. What bothers me is the verbiage
that they made modifications that put them "closer" to 100% compliance.
Closer? What does that mean? We are speaking of world giants and they cannot
comply "dead on" with an established standard?!!! What gives? Is the
standard or guidelines that hard to comply with? That's the part I don't
get.



"Graham Hughes" wrote in message
...
But why does everyone blame Bill, it's not his fault, it's the camcorder
manufacturers not using the correct firmware in their camcorders, which is
why you have to roll back to old drivers from MS which allowed the use of
non-compliant firmware. Bill actually tried to be more compliant, poor
chap
The solution is on micorsofts servers, KB893008
Now other problems may be his fault, but not this one

Also look at the mnay problems people face with Sony HC42's and Macs, they
don't work together because of Sony's firmware, and this can't be Bill's
fault can it???? LOL LOL

Graham

--
Graham Hughes
MVP Digital Media
www.myvideoproblems.co.uk
www.dvds2treasure.com
www.simplydv.com


"joshua siew" wrote in message
...
Shank !,
Thanks for the problem posted....and ur final success.

Treeman !,
Thanks for the patient in solving this problem. I myelf also having this
kinda problem after I re-install from fresh my pc with WinXP Pro Sp2 when
my
DAMM so call branded digi video cam SONY cannot work with the famous OS
held
by the richest person in the WORLD.
I was searching high and low for this solution myself also in MICROSOFT
servers.

I like this brainstorming communities...

-joshua siew

"Treeman" wrote:


Shank,
Shhhhhh! I got some folks in the, "SP2 or die" camp p*ssed at me for
putting out this solution. But I'm glad it worked for you. It's great
that you can now be in the "Start Something" Experience, instead of
being in the "Fix Something" Experience!
Best,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

"All that's left is to condemn the camera. Sony doesn't believe the
camera is
at fault and of course they want _$269_ to bench test it."
Graham,
I think we missed the boat on this one!
Best Wishes,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

Maybe I missed something....
Months ago, with SP1, I had no problems. Upgrade to SP2 and it does not
work. Referring to this statement: " Having spent some time conversing with
Microsoft, it appears that when SP2 was released they updated the ieee1394
drivers, so that they fitted more closely to the ieee1394 standards. Whereas
the SP1 drivers didn't match these standards so closely "

OK... I'm glad they decided it was time to "get closer" to the 1394
Standards. Sony's camcorder worked with the looser standards. That suggests
that both MS and Sony were not conforming to the standard. I don't know how
Sony approached the 1394 issue in the beginning, but I'm guessing they
tested using MS software and when it worked, they stamped the approval.
Otherwise, if they initially conformed to the 1394 standards 100%, without
consulting with MS, then they both would have found a flaw in the looser
standards... correct? That's were I blame both MS and Sony.

It's great that MS can provide a FREE SP2 download to conform. But I cannot
absolve them from the initial problem. I believe that both MS and Sony
conspired to slide by somehow originally.

My 2¢


"Treeman" wrote in message
...

"All that's left is to condemn the camera. Sony doesn't believe the
camera is
at fault and of course they want _$269_ to bench test it."
Graham,
I think we missed the boat on this one!
Best Wishes,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

Shank, it probably is a bit of both. I doubt very much if MS and Sony
conspire to do anything. It also doesn't matter whether MS had complied
fully or not. Some of Sony's new cams do not work with the inventors of
firewire, Apple. This is because Sony wish to implement their own
standards.........

Still we probably shan't agree

Graham

--
Graham Hughes
MVP Digital Media
www.myvideoproblems.co.uk
www.dvds2treasure.com
www.simplydv.com


"shank" wrote in message
...
Maybe I missed something....
Months ago, with SP1, I had no problems. Upgrade to SP2 and it does not
work. Referring to this statement: " Having spent some time conversing
with Microsoft, it appears that when SP2 was released they updated the
ieee1394 drivers, so that they fitted more closely to the ieee1394
standards. Whereas the SP1 drivers didn't match these standards so closely
"

OK... I'm glad they decided it was time to "get closer" to the 1394
Standards. Sony's camcorder worked with the looser standards. That
suggests that both MS and Sony were not conforming to the standard. I
don't know how Sony approached the 1394 issue in the beginning, but I'm
guessing they tested using MS software and when it worked, they stamped
the approval. Otherwise, if they initially conformed to the 1394 standards
100%, without consulting with MS, then they both would have found a flaw
in the looser standards... correct? That's were I blame both MS and Sony.

It's great that MS can provide a FREE SP2 download to conform. But I
cannot absolve them from the initial problem. I believe that both MS and
Sony conspired to slide by somehow originally.

My 2¢


"Treeman" wrote in message
...

"All that's left is to condemn the camera. Sony doesn't believe the
camera is
at fault and of course they want _$269_ to bench test it."
Graham,
I think we missed the boat on this one!
Best Wishes,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215

I know, I could charge $100 to test each one, then send it to you for a
further test at $100 LOL

--
Graham Hughes
MVP Digital Media
www.myvideoproblems.co.uk
www.dvds2treasure.com
www.simplydv.com


"Treeman" wrote in message
...

"All that's left is to condemn the camera. Sony doesn't believe the
camera is
at fault and of course they want _$269_ to bench test it."
Graham,
I think we missed the boat on this one!
Best Wishes,
Treeman


--
Treeman


------------------------------------------------------------------------
Treeman's Profile: http://www.msusenet.com/member.php?userid=1260
View this thread: http://www.msusenet.com/t-1870578215