This is definitely an XP SP2 problem which affects some of the older DV devices. I too have a DSR-30(P) PAL version and had the same problem but my PD-150 and Panasonic 100En worked fine.
In the end I found a reference to the fualt on the Microsoft Support site and it indicated that, without rolling back to SP1 you can replace the MSDV.SYS file that SP2 installed with the older SP1 version. If your SP2 is an upgrade from SP1 the orginal should have been backed up when you did the upgrade. Microsoft apparently have it scheduled for a hotfix but it's not high on their priority list.
Search the Microsoft Support forum for MSDV.SYS and you should find the message, posted by a Microsft Support Staff member which explains the fix.
It's relatively simple if you can copy and rename files, it points to a few locations where I didn't find the MSDV.SYS file but where I did find it I replaced it and I suddenly had capture again!!!!

Steve

Thanks for the info!
My machine is a new BOXX AMD so it's not an upgrade from SP1, I assume. I'll look for the info at MicroSoft. Strange but Canopus EDIUS Pro 3 is working just fine with my DSR on the same BOXX.
mp

This may sound like wierd advice but try the Windows Movie Maker and see if you are getting the same fault you get with Vegas.
If you do it points to the problem being the MSDV.SYS file compatibility.

It may be that the Canopus is using its own drivers which is why it works with the DSR30. I don't have experience with the Canopus hardware.

Vegas relies on the Microsoft OHCI drivers for DV (IEEE-1394).
If you need access to the older MSDV.SYS file let me know and I'll email it to you, it's quite small.

Steve

Experienced same problem with Veg5 after upgrading to SP2. Tried replacing the MSDV.SYS file as explained in a post on this forum.

Result: no more device errors, but it dropped frames and stopped capturing less than a minute into the tape. Disabled both audio and video preview with no improvement.

Rolling back to SP1 improved things considerably, but still getting occasional dropped frames and aborted captures.

FYI, my system has hardware RAID for both system and data drives and has never had a problem until the SP2 debacle.

I haven't had any dropped frames or capture problems and haven't needed to do the full roll back to SP1.

As your system is new and comes with SP2, as you indicated in an earlier reply, I try and source an earlier version of the MSDV.SYS file.

If you need an old one drop an email and I can send you one.

I've got a 2/17/2003 on my XP Pro machine.

If you have a copy of XP that comes with SP2 you'll need to source an earlier version of theMSDV.SYS file

You can download the SP1 version from

http://members.optusnet.com.au/newhope2/msdv.sys

Search your Windows directory for any versions of the file and rename them MSDV.OLD and then copy the downloaded version of the file into the same folder.

Main location for the file should be in C:\windows\system32\drivers

Please virus check the file for your own peace of mind.
I assure you it is clean and I run the latest Symantec antivirus software, but I wouldn't download and use any file before checking it.

Regards
Steve

Thanks everyone. Great advice. Since it's a new BOXX they said they will build me a new C drive with XP SP1 and since they forgot to partition the drive as I requested they will take care of that for me as well. I'll swap out the drive a see how SP1 performs

Great folks at BOXX I must say.
mp

Well...spoke too soon. BOXX can't build me a drive with XP SP1. Microsoft won't let them. So I guess I need to get the msdv.sys file.

Well if you have any time to help me out here. I have the old SP1 msdv file. It's clean.
I have found 3 locations of the SP2 msdv.sys file..in
C:\1386\SP2.cab,
C:\Windows\system 32\drivers (like you said) and
C:\Windows Driver Cache\1386\SP2.cab .
I was able to rename the file in the Windoes 32\ drivers location with no problem but I can't seem to rename the file in the other two locations. I've rebooted to see if that would help but it hasn't. Just to see, I started Vegas 6 and now can't even get the Firewire pass- through to work anymore. Any thoughts? Thanks!
mp

Of the locations you indicated you found the MSDV.SYS file the only one that is important to the functioning of the firewire connection is C:\Windows\system 32\drivers.

The other two are Cab files for SP2... where SP2 sources its drivers etc when installing so don't worry about them they can remain where they are and named as they are. Unless you reinstall SP2 they won't have any affect.

Did you download the MSDV.SYS file from the URL I posted in my earlier message?

That file was uploaded directly out of my C:\Windows\system 32\drivers folder and is a copy of the one I am currently using with my DSR-30P.

Renaming the file existing file in C:\Windows\system 32\drivers, makes it inactive, which is what you want to do before you copy the 'new' MSDV.SYS into the C:\Windows\system 32\drivers folder.

Having copied the file you should reboot and the system should be working.

If it doesn't then delete the 'new' file and rename the 'old' file back to MSDV.SYS.

Sorry I haven't answered earlier I've had my head down editing a new video.

regards
Steve

I'm having the same problem... GRRRRR!

Steve, following your instructions I was able to get the DSR-30 to connect. But when I stopped the capture after 30 seconds everything froze and I got an error message!

SonyEPM here is the content of the error message:

Sony Vegas 6.0
Version 6.0a (Build 99)
Exception 0xC0000005 (access violation) READ:0x18 IP:0x79C2B4
In Module 'vegas60.exe' at Address 0x400000 + 0x39C2B4
Thread: GUI ID=0x468 Stack=0x12F000-0x130000
Registers:
EAX=0012fc44 CS=001b EIP=0079c2b4 EFLGS=00010206
EBX=00000000 SS=0023 ESP=0012f820 EBP=00000000
ECX=00000000 DS=0023 ESI=001460f4 FS=003b
EDX=0012fc44 ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
0079C2B4: 8B 41 18 8B 08 56 8B 74 .A...V.t
0079C2BC: 24 08 52 8B 54 24 1C 52 R.T$.R
Stack Dump:
0012F820: 00612AFD 00400000 + 212AFD (vegas60.exe)
0012F824: 00000000
0012F828: 00000000
0012F82C: 00000000
0012F830: 00000000
0012F834: 00000000
0012F838: 0012FC44 00030000 + FFC44
0012F83C: 000201E0 00020000 + 1E0
0012F840: 01AC4900 01AB0000 + 14900
0012F844: 00030108 00030000 + 108
0012F848: 0012FC44 00030000 + FFC44
0012F84C: 0012FC44 00030000 + FFC44
0012F850: 00418024 00400000 + 18024 (vegas60.exe)
0012F854: 00146001 00140000 + 6001
0012F858: 00000000
0012F85C: 0012FC44 00030000 + FFC44
> 0012F864: 00416F90 00400000 + 16F90 (vegas60.exe)
0012F868: 0012FB08 00030000 + FFB08
0012F86C: 00000000
0012F870: 00000000
0012F874: 000003F1
> 0012F87C: 0041F3DC 00400000 + 1F3DC (vegas60.exe)
0012F880: 04291E00 041D0000 + C1E00
0012F884: 00000084
0012F888: 0012F914 00030000 + FF914
> 0012F88C: 0041F1B0 00400000 + 1F1B0 (vegas60.exe)
0012F890: 0012F914 00030000 + FF914
> 0012F894: 0041F1B0 00400000 + 1F1B0 (vegas60.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0087DCEC 00400000 + 47DCEC (vegas60.exe)
0012FFFC: 00000000

Well the file did come from a tech friend here in Nashville. He had SP1 and sent me the file. Everything else you say is what I did. I kinda figured the other msdv files didn't need to change but wasn't sure.
But I still don't have control of the DSR-30. But as I have said the pull-down menu ...Microsoft VCR properties ,in the capture screen, still lets me control the deck..
By the way the firewire pass-through is working just fine now.
Maybe I need to download your msdv file?

Did you not try what Steve suggested?