Dv 1394 Capture Not Working After Xp Sp2 - Fixed

[ljraggy]

Just incase anyone is reading this , i have it working now. Had to
work the SP1 Firewire drivers in.


Go to C:\WINDOWS\Driver Cache\i386 in the sp1 cab copy out the
following files

1394bus.sys
arp1394.sys
nic1394.sys
ohci1394.sys

replace the new versions of them in the C:\WINDOWS\system32\dllcache
and C:\WINDOWS\system32\drivers

reboot

this should fix it.

Thanks to adam in MS Forums

[Floppy]

Hi ljraggy :)

Welcome to the forums at Digital-Digest.

Thank you for that important piece of information, I am sure it will be of use to some here at the forum.

bye :)

[RayK42]

Had the same problem, no video preview in 3 different programs.
Canon ZR85, new firewire card.
Tried several solutions, including removing SP2, different slot for the card, different cable, etc. etc. None worked.
Found this fix on another site:
Go to start, run,
type in:
regsvr32 %windir%\system32\qdv.dll
hit enter
(note: must be a space between regsvr32 and the first % sign.)
Got an OK box, and everything works great!
All programs capture and preview no problem!

[Floppy]

Welcome to the Forum RayK42.

Excellent

This is quality. I bet some users here will find this info usefull...

I sure will referr to it if needs be...

Thanks for your input...

[Muttley]

I've tried this fix but when I replace the files with older versions they seem to be automatically updated back to the originals!!!

Any ideas?

:smashead:

[ljraggy]

Make sure you replace them in the

Cache\i386

&

\WINDOWS\Driver

folders

goto [tools] [View] & show hidden files & untick Hide protected operating system files

if you can't see the Cache\i386 folder


If you still have problems booting up in safe mode should solve this

HOLD [F8]

during windows startup

& then try

[Muttley]

I feel very close to being able to fix this problem but not close enough.

Advice in previous referring to locations of drivers relating to 1394 do not match those on my PC.

I know I have to replace the offending drivers in

C:\windows\system32\drivers

but they also exist in 11 other directories

c:\i386\driver.cab
c:\i386\sp1.cab
c:\windows\driver cache\i386\drivers.cab
c:\windows\driver cache\i386\sp1.cab
c:\windows\driver cache\i386\sp2.cab
c:\windows\i386\driver.cab
c:\windows\i386\sp1.cab
c:\windows\ServicePackFiles\i386\
c:\windows\ServicePackFiles\i386\sp2.cab
c:\windows\$NtUninstallQ811789$
c:\windows\$NtServicePackUninstall$\sp2.cab

I do not have a c:\windows\system32\dllcache folder referred to in a previous post.

Also the Cache\i386 is actually
c:\windows\driver cache\i386\drivers.cab
c:\windows\driver cache\i386\sp1.cab
c:\windows\driver cache\i386\sp2.cab

But as you can see the files are in cabs.

Please note all file searches were made with show hidden files.

Thanks for the help so far.
:P

[ljraggy]

The Reason you cant see the "c:\windows\system32\dllcache" Folder is because windows is protecting the SYSTEM files

As i stated before change your viewing in the tools
"goto [tools] [View] & show hidden files & untick "Hide protected operating system files"

it is there.

Don't worry about the CAB folders

& Make sure you reboot as soon as you've replaced them as windows will replace them.

[Muttley]

Well.....

Tried all those things but...........

XP still overwrites the files in /dllcache & /drivers

Any more ideas???

:confused:

[ljraggy]

OK pull out your hard drive go to a friends house and copy the files using there system..

Install back into your system. This way Xp will not automaticly replace the files

[Muttley]

Anyone else who knows what they are doing have a more sensible answer?

:mad:

[ljraggy]

Originally posted by Muttley
Anyone else who knows what they are doing have a more sensible answer?

:mad:

Seriously what I have stated it exactly what I did to resolve the problem with my machine after installing SP2

If XP keeps replacing the files THATS WHAT YOU HAVE TO DO

Have you checked that the file Versions are SP2?
if they are the New SP2 files THATS the only way if this is your problem

and not other driver or hardware issues.

UNINSTALL SP2 this will fix it.:smashead:

[Muttley]

Sorry but I don't agree. Windows can only replace the files if it has a) a source and b) a method of doing it.

In either case I should like someone's advice on how to do it.

Due to warranty reasons I am not going to disembowel my PC just to restore a couple of drivers that support an older DV camcorder.

Yes, I could uninstall SP2 if only the uninstall .exe was still on my PC.

Seems like the MS programmers have worked hard to protect system files. If only they worked as hard to produce decent software that didn't have major security lapses requiring major updates.

[JerDrvr]

Before I go replacing drivers, I'm wondering if I have the same problem this thread started with.

I edit video on a Dell laptop. Plugged into it is a Maxtor External HD (D: drive). Connected to that is my video camera. Since SP2 I can no longer capture video on the external drive although normal camera operating functions work fine (my internal C: drive captures fine so I'm not sure if we're talking the same problem).

What I get is the following message:

Windows - Delayed Write Failed
Windows was unable to save all data for the file D:\$Mft.

Maxtor has a Knowledge Base page which basically sounds like the problem I'm probably having at:
http://maxtor.custhelp.com/cgi-bin/maxtor.cfg/php/enduser/olh_adp.php?p_faqid=2172

If I try the steps in your first post, what are the chances I could end up messing something else up? Would system restore save me?

[Muttley]

Appreciate your reply.

My problem is I have an older Sharp Viewcam that worked perfectly well over Firewire before the SP1/SP2 debacle (don't you just love MS?).

It seems perfectly logical to me that using the pre SP1/SP2 drivers would restore the ability to connect my Viewcam via Firewire.

However, as you know from the thread, whenever I replace the driver with the originals, Windows is overwriting them.

It's very frustrating that MS claim to have never supported Firewire but as my only use for it is to upload video from the Viewcam I'm not going to extract my hardrive just to restore the driver. Nor am I going to uninstall SP2.

As I said in my previous reply, I'm hoping someone knows enough about XP to identify how I can replace the current 1394 driver with the originalsand avoid the overwrites.

Hey, you never know, perhaps an MS employee will be compassionate enough to suggest something.

Now if only I had bought a MAC instead!!! Or perhaps I'll buy a DVD writer with i-Link

Cheers

[snowy owl]

For what its worth, I managed to avoid getting XP to replace the drivers by:

- doing the copy/paste as administrator under SAFE mode
- renaming the XP2.cab file (e.g. to XP2old.cab)
- rebooting

The copied drivers in \WINDOWS\SYSTEM32\DRIVERS and dllcache remain unreplaced by XP...

however - the bad news for me is that it didn't solve my problem. I still cannot capture more than 1-10 seconds under Pinace Studio 8 before the firewire connection freezes completely. Strange thing is that it suddenly stopped working around 2 weeks ago - but worked beautifully for several months under XP SP2 before that...

[Muttley]

Thank you.

I'll try that when I get the chance and will let you know the outcome.

Have you tried WIN DV? It's basic but might at least get your raw video onto your PC for later editting.

Cheers

[ljraggy]

Ok the inital problem in a nutshell

If you have noticed.....

before SP2
when you connect a DV device normally the system made the connection sound with a balloon stating the a new DV device has been connected then reconized the device as ie "Panasonic NV-GS120 Digital DV Camera is ready to use"

& away you go ie Capturing the video etc...

after installing SP2

when you connect a DV device you hear the Connection sound then a few seconds later hear the disconnection sound. Nothing more. No baloons no popups.

Thats the error in a nutshelll if your getting ballons etc this error is the same thing & might be drivers, cable... etc if your using an onboard DV a bios firmware update might be in order & your mother or card manufacture will have updates if there are errors after XPSP2

I hope this INFO helps

Regards

[Floppy]

mmmmm...

This is where I have to say something as a word of advice to all SP2 must have people out there....

Having experienced enough of my own problems with SP2 upgrade because that is not an simple update like SP1 and realizing all the implications of such a large scale security and much more implicated in that process, I have concluded the folowing....

Creating a Slipstreamed SP2 upgrade with Windows xp home or pro is a absolute must, this will greatly reduce the chances of conflicts and problems with the instalation of SP2 onto a current SP1 OS...

Having done this and wiped the drive clean and reeinstalled XP (faster by 10 minutes this time around) I found that all my "little" anoying problems went away....

How to slipstream SP2 instructions (http://www.helpwithwindows.com/WindowsXP/winxp-sp2-bootcd.html)

Now I know after reading the instructions you are gonna think this is a lot of time or work! it isnt really but consider that you will not spend so much time resolving issues with XP SP2 and instead enjoying the PC as it should.

It is simple as simple can be...

[Muttley]

Firstly a big thank you to Snowy Owl for the cab rename suggestion. May I suggest that he/she reviews the other steps I took i.e. 5) onwards in the hope I can return the favour and fix his/her problem.

I am in no way suggesting you do this on your machine but what I found may be of interest

1) Rename the cabs as suggested in Snowy Owl's post
2) Replace current 1394 drivers (as described in previous posts)with pre-SP1 ones
3) Ignore the XP warning re. old drivers
4) Reboot

However, MS Moviemaker still gave an error message and refused to acknowledge my Sharp Viewcam. WinDv would accept it but playback/capture gave a broken image.

I then reviewed the Driver details for the Viewcam under Imaging Devices in Device Manager which showed some SP2 drivers.

5) I replaced msdv.sys and stream.sys in windows\system32 with those in driver.cab in windows\driver cache\i386.

Now I can view and capture successfully using WinDV.

For the record:

a) I never had any problem with XP recognising the Sharp Viewcam. The problem was always to do with playback/capture.

b) As I suggested in a previous post, I suspected XP was self healing i.e. replacing drivers. Again, thanks to Snowy Owl for that workround.

I urge anyone reading this or any other thread to think carefully about the advice offered, its suitability and the consequence of following it.

With due respect and accepting the advice was given with best intent, if I had followed some of the recommendations I could have removed my disk drive and/or uninstalled XP SP2 when all that was required was a simple file rename and a bit of research.

[JerDrvr]

ljraggy

I love you!

No, I mean, I LOVE YOU MAN!!

I did everything you told me to in your first post and I just ran the trial test run and the video capture worked flawlessly.

Here's hoping for continued success and thank you so much for your post.

JetDrvr (not JerDrvr - I was really tired when I registered)

[SHP]

:smashead:

[snowy owl]

Before typing in control commands - it would be useful to know what it does!!! Could someone please elaborate?

[Muttley]

Don't know what it does but it didn't work for me

[ljraggy]

It's generally a DirectX or ASPI update that is required.

qdv.dll = DSH DV Video Encoder

[The_mack]

Gentlemen, you are all stars!
This is the only place that has managed to help me sort this problem out.
Replacing those 4 sys files
[found in c:\windows\system32\drivers, c:\windows\system32\dllcache and c:\windows\servicepackfiles\i386]
and then renaming the sp2.cab files
[found in c:\windows\driver cache\i386 and c:\windows\servicepackfiles\i386]
fixed it with no problems.

I can use my camera again!:bglaugh2:

[DMW]

Please help me guys.

I have tried everything in this thread (and many others) to fix the problem of not being able to capture from my Canon MV550i. Like some others I have full control of the camera but just cant capture. MM gives and unknown error, Windv gives a runtime error, same with pinacle and Nero.
I have 2 pc's both running XP, I used to capture DV on the old pc (pre sp1 & sp2) without any probs. The old pc has a pci 1394 card. I tried replacing the 4 drivers with no avail. I even rolled that 1 back to SP1, still nothing.
I took the pci card out of that one and put it in the new pc (another forum suggested onboard 1394 maybe the prob.)
With the pci card the only installed 1394 I have been able to use the pre sp1 drivers (thanks to eirlier posts). In all the folders the drivers are dated 17th August 2001 in device manager they show as version 5.1.2535.0 until you click "driver details" where they show as 5.1.2600.0 but they no longer say sp2 there. Mutley suggested replacing 2 other .sys files but I have not been able to change the stream.sys without it going back to december 2002.

I have been working on this for days now and seem to have tried everything suggested.

Please help a man who is at the end of his wits.

[ljraggy]

Like some others I have full control of the camera but just cant capture.

This issue is not concearned with you as the PC sees your Dv Device

I Suggest seeing if there are updated drivers at the DV cards website or forcing the XP DV .SYS files in other words dont let XP find them. You choose the files in the .CAB folder to get back to XPSP2 DV .SYS files

This seems to be a XP driver issue and not an issue with XPSP2 itself.

have you tried other programs with your Dv Device? Software may also be the Key.

Good Luck ljraggy

[DMW]

Originally posted by ljraggy
This issue is not concearned with you as the PC sees your Dv Device

I Suggest seeing if there are updated drivers at the DV cards website or forcing the XP DV .SYS files in other words dont let XP find them. You choose the files in the .CAB folder to get back to XPSP2 DV .SYS files

This seems to be a XP driver issue and not an issue with XPSP2 itself.

have you tried other programs with your Dv Device? Software may also be the Key.

Good Luck ljraggy

I have tried about 8 different programs on 2 different PC's (both running XP sp2/sp1). I know it used to work with pinnicle 8 on the old PC before SP1. I have searched the website and forum of the on board 1394 card in the new pc (VIA chipset) but there are no drivers there. I have no way of finding out the chipset of the pci card (that I know of).

Right now I am running the pre sp1 drivers (see other post) and it has made no difference at all, could you please explain what you mean by "getting back to XPSP2 DV .SYS files"?

I also need to find a PC this will work on so I can rule out the cable or cam I guess.

BTW if its any help the stills capture works with usb but not 1394 either.

It's at times like this when someone who thought they new a thing or two about pc's finds out just how little they actually know. :(

[Speedy2]

I am also having the same problems as previous poster. I have tried a few of the above suggestions to no avail. I don't see the camera at all on the system. I have a gigabyte motherboard with the via chipset and both 1394a and 1394b built into the motherboard. System used to work before with my Canon Elura2 MC without any problems. Tried uninstalling SP2 last night but still same results. I can't remember if the firewire stopped working with SP1 or if it was with the SP2 upgrade. I wanted to do a Christmas video for the kids but as of a few days ago I haven't had much luck getting it to work.

Anyone have any more suggestions?

Speedy2

[ljraggy]

could you please explain what you mean by "getting back to XPSP2 DV .SYS files"?

In the first post i mention 4 files concerned with the main issue at hand.

These files I say to replace from the SP2 Cab file with the older versions that you replaced with SP1

OK..... Your system sees the USB thats fine mine did the same thing when i first came across this issue.
But the fact that your system sees the Camera points to another issue. Pluging the camera into another system would be a good idea. Make sure you use the same cable.

I myself had never had this problem....(Controlling Devices)
I suggest looking at what other users are saying with your exact problem.

Not the fact that the DV Device can see the PC but fact that controlling the device from the PC & capturing the video is the main problem at hand

Try unloading from memory everything but what you need to capture the footage ie chat progs, antivirus, net connection etc etc .

Hope this is of some help

Merry Xmas :D

[ljraggy]

Originally posted by Speedy2
I can't remember if the firewire stopped working with SP1 or if it was with the SP2 upgrade.

Since your PC dosent see the DV Device at all try repeating the the SP2 Fix in the First post and I suggest renaming the SP2 CAB folder like snowwy owl suggested

Do you hear the device connect & then disconnect when you plug it in?

Thats the Key... to this issue.

Also try unloading from memory everything but what you need to capture the footage ie chat progs, antivirus, net connection etc etc.

Thats all i can think of ATM

Dose anyone else have a suggestion?

[ljraggy]

Some IDEAS for Capture ISSUES

Video Capture detects the camera, but the Play button does not work

This means that Video Capture does not have device control of your camcorder. If the camera is not in VTR (playback) mode, this could be because it is using the wrong device control software driver. Choose a different device control driver (e.g. Microsoft DV Cam and VCR) from the Video menu. Even if device control fails, you may still be able to use Video Capture to manually capture video by using your camcorder's controls to control playback.

Video Capture does not detect the camera

Ensure Smart Preview Video or Always Preview Video is selected on the Options menu.(if applicable)

If the Status Bar does not display your device when it is correctly connected and turned on, try turning the camera on first and then running Video Capture, or try running Video Capture first and then turning on the camcorder. The detection process should not take longer than thirty seconds

Dropped frames during capture or playback
General advice
Use a dedicated hard disk. Modern hard disks (EIDE, UDMA, SCSI, etc.) can all handle DV capture and playback. Faster disks that spin at 7,200 RPM are recommended. Most importantly, you should always capture to a dedicated, physically separate hard disk. Dedicated means that it is used primarily for storage purposes and does not have any applications on it that may interrupt the capture process. Physically separate means that Windows is installed on a different disk. This is not the same as a different partition on the same disk. Windows frequently needs to write to the hard disk it is installed on, and this can interrupt the capture process. Actually, Windows will write to the disk specified in your Virtual Memory settings. Make sure this location is physically different from your capture hard disk. See Windows Help for more information.

Defragment your video capture hard disk.

Do not run any other programs during capture. You should not be doing anything else with your computer during capture. Other programs can easily interrupt the high rate of data flow to the hard disk during capture that can cause dropped frames. Press Ctrl+Alt+Del and view the Task Manager to see a list of applications that are running. Any unnecessary operations (e.g. most applications other than Explorer or Systray) can be stopped by selecting the process and clicking the End Task button.

From Sony Help Files

[Speedy2]

Originally posted by ljraggy
Since your PC dosent see the DV Device at all try repeating the the SP2 Fix in the First post and I suggest renaming the SP2 CAB folder like snowwy owl suggested

Do you hear the device connect & then disconnect when you plug it in?

Thats the Key... to this issue.

Also try unloading from memory everything but what you need to capture the footage ie chat progs, antivirus, net connection etc etc.

Thats all i can think of ATM

Dose anyone else have a suggestion?

I have tried all the suggested solutions to no avail. A buddy of mine suggested uninstalling SP2 and reinstalling SP1. I think SP1 worked great for me on two computers.(laptop and desktop) I don't think memory is a problem as I have 1 gig of memory and never had any problems with anything before. Processing power isn't a problem either as I have a AMD 3400+ and it kicks ass. I think I'll take my friends suggestion and will post results. I ready tried just uninstalling SP2 without much luck. I don't want to wipe the drive and reinstall XP Pro so I hope I can figure this thing out.

I also do not hear the connecting and disconnecting.

Speedy2

[Floppy]

I think that people that upgrade from sp1 to sp2 should really slipstream the sp2 onto a new xp home installation disk...

This will ensure a stable installation of windows upgraded as it installs...

It resolved for me several issues I had with USB 2.0 devices and overall program stability wilst working under windows xp sp2...

http://www.helpwithwindows.com/WindowsXP/winxp-sp2-bootcd.html

[DMW]

OK, This is getting stupid now.

I formatted and reinstalled xp (no service packs). I connected my Canon DV, windows found it, installed the drivers then asked me if i wanted to open movie maker. I did and I got an error message about the device being in use or the output format not being supported. WTF is going on????

I am totaly lost here.

If it was a prob with the cam or the cable would I still have control (FF & RWD etc etc) ??

HELP !!

[Floppy]

Slipstream my friend the answer is slipstream...

[JerDrvr]

DMW,

Try another editing program. I recommend Sony Vegas. Download the trial version and see if your computer behaves any different. WMM2 caused me great stress as well but for me it was problems with transferring video back to my camera. The video would "hiccup" every few seconds. The final fix came when I switched editing programs.

Godspeed!

[DMW]

I have solved the problem with capturing DV from my Canon MV550i.
I will tell you the answer (incase anyone else is having probs) as long as nobody laughs.

As I said in my earlier post, I could control the camera via the pc but no matter which program I used I got an error when ever I tried to capture. I tried the old drivers, I tried another PC, I tried on-board firewire and PCI, I even formatted one of my drives and tried a pre SP version of XP, none of this made any diff.
Out of desperation I phoned Canon (who where not very helpful) and explained all this to them and asked if there was anything else that could give me a problem when trying to capture. They went through all the things I had done and still no idea.
Deciding it must be a prob with the firewire cable or camera I bought a new cable today, still the same thing. GRRRRRR.

Now I dont know what made me do this (probably because I had tried everything else) but I noticed that I had recorded my movie in ESP mode, the MV550i has ESP, SP, LP and ELP modes. I swiched to SP mode and tried again, OMG, at last I got a different error, it captured but this time it said the captured file was corrupt. I put in a different tape, one that had been recored in SP mode and tried again. SUCCESS.
So all this time it was just that I was trying to use the ESP mode of the camera. Now dont you think Canon would have know that it would not have worked????

Anyway, thank you for your help guys, I hope this will help some other poor soul who is at their wits end.

[JerDrvr]

It does amaze me how weak tech supporters can be with troubleshooting there own products. I guess they are so knowledgeable they can't see the trees in the forest.

[doitplease]

My PC came shipped with SP2 and does not have sp1.cab files. Where can I get those 4 sys files to fix the problem?

[Backspace]

My problem is that the video is choppy and the sound is skipping. Is this the common problem, with SP2?

[Backspace]

What other problems are people having with SP2? Will USB2.0 solve a choppy video problem?

[joelp]

I have read all these posts with great interest, and have tried everything suggested here with no success. Curiously enough, the only thing that works for me (that I don't see in this thread) is rebooting with the camcorder on. It probably has no bearing on the subject, but I have a JVC GR-D33U. I have not yet tried reinstalling XP with only SP1. Another suggestion I have see in another forum is only using firewire cards with TI chipsets, which makes sense to me, as the drivers appear to be TI. I only have a cheap generic firewire card, and don't know what chipset it has, but it's probably not TI. I will mention that when I bought the camera, I bought a lovely-looking $25 1394 cable at radio shack, which I first tried on my laptop which has a mini 4 pin 1494 port, with absolutely no success. When I bought the cheap firewire card for my desktop computer, I tried the RadioShack cable, but it didn't work at all. I then tried the ugly cable that came with the firewire card, and if I reboot with the camcorder on, it works. I'm keeping my eyes open for another firewire card with a TI chipset to see if that solves the problem.

[Phantadla]

When connected, icon appears in system tray but windows autoplay does not appear. If I click on the icon, it appears but only some programme options are there and one option has question marks. If I select an option, it does not connect to programme.
If I go into programmes (WMM, Power Prod/ Dir etc), I can get it to function. But how can I get it back to autoplaying- I don't know if it was SP2 installation (it works on machines with SP2 pre-installed) or when I loaded Studio 8.

[personguy]

my laptop was shipped with service pack 2, and i don't have an sp1.cab file.

i found a site:
http://www.videredesign.com/xp2_workaround.htm

where i can download the sp1 files
ohci1394.sys
1394bus.sys

but i can't seem to find the other two files, or a place where i can download the sp1.cab file.

i realise this thread was started two years ago, but i'm having this exact problem (pc doesn't recognise the dv camera at all and says the firewire card is functioning properly).

maybe there's a better/different solution for this problem by now?
using an acer laptop with a roper ieee1394 pcmcia adapter to connect a canon mv790 camera.

thanks.

[ljraggy]

ohci1394.sys
1394bus.sys[/B]



I don't know where to locate these on the web.... did a google but no luck you might be lucky....

I could send you these files if you like via email.....

digital-digest@thegyde.com

[nandanmv]

I got it to work and wanted to share how I did it. I had my 1394 capture and it had stopped working for some reason. I tried everything on the post:
1) Replacing Sp2 with Sp1 files
2) Registering DLL

Unfortunately they did not work. I finally opened up my PC and moved the card to another PCI slot (http://lifehacker.com/software/feature/how-to-install-a-pci-card-135479.php) and Voila! It worked!! Got the "Ding Dong" after restart of PC with the camera plugged in.

Thanks to all members for the contributions.

Cheers!
Nandan

[sinclair75]

I've done everything suggested here, but my issue is slightly different. My camera works just fine - records and plays back on the small lcd screen. The last video I have transferred was on the 17th of July this year and really did very little video work until mid September. The problem is, like most in this post, Windows does not detect my camera now. It is a Canon IXY DVM (Optura 200MC in the states) and I contacted Canon about the issue, they said,

"When connected to your computer by Firewire and turned on to the TAPE/PLAY(VCR) mode, the words "DV IN" should appear in the camcorder's LCD display. The appearance of the "DV IN" message indicates that the camcorder has detected your Firewire port and is waiting for a signal from the video editing software to begin the transfer of footage. The remainder of the transfer process is controlled by that software; we would suggest reviewing the instructions for that program for further information.

If the "DV IN" message does not appear, or if it flashes, then there may be an issue with the camcorder's DV IN/OUT port, the Firewire cable, or the Firewire port on your computer. To rule out the camcorder and cable as the source of the issue, we would suggest connecting the camcorder to a different computer via Firewire. If the "DV IN" message still does not appear, or continues to flash, then you may try a different Firewire cable, or have the camcorder examined by a service technician."

When I turn on the camcorder and don't have it plugged in, I get nothing but with the cable attached, the dvin flashes. My difficulty is testing it on another computer as firewire cards are not in great use in the small town where I live in Poland - at the high school where I teach, there are none in the comp. lab and none of the staff laptops have them either. I hope it's my firewire card if it's anything... Any chance it could be a software issue though? The camera hasn't been dropped and no water etc. has been spilled on it. It's used, but to go from working to not without warning seems odd...
:please:help

[ljraggy]

If you get NO Audio acknowledgment to say you have even plugged the camera in it might be the Cable try getting another cable to use, or see if you can install your card in another machine, Any Machine it should not matter as if the specs are to low you just won't be able to copy your Tape -> Disk.

You Just want to see where your problem lies. Trying other Software is a good idea, I use Sony Vegas, you can get a trial from here http://www.softpedia.com/progDownload/SONY-Vegas-Download-33684.html

Hope this helps. Try Another Cable, then Other Machine, use your card in another machine. Most Laptops have Firewire Ports.

Good Luck...

[dal1980]

I read through threads and to me none it makes any sense!!!

I tried replacing the files as stated in the begging of the thread but

a/ dont know if I actually did correctly

b/ nothing happened

Under device manager I can see the IEEE device is seen by the computer but the camcorder is not being seen anymore.

Could be becuase of an automatic windows update??

i tried asystem restore to when I know it worked. No go there either
To say I am becoming confussed and starting to get a headache over it all is to say very little. Can some one explain in basic english what has happened and how to rectify. I would extreamly appreciate it.:smashead:

[gonwk]

Hi dal1980,

Welcome aboard ... could you tell us a bit more about your set-up ... what OS are you using ... and what are you doing or what did you do before your problems started.

Thanks,

G!:)

[pfloyd]

How are you hooking up the camcorder? Firewire cable?

[dal1980]

I am trying to connect via Firewire IEEE 1394, and am running windows XP home. the problem just occured I mean it wasnt like was using the devie and it all stopped working there was about six weeks were I didnt use the device then the next time I tried to use it nothing.

My first thought was thatI may have downloaded or done somthing to the computer that may have caused a typical "user Error" so I tried a system restore from the date I knew it was working. This did not do anything, other than make me frustrated it never worked.

I spoke to one technical premium rate numbe and they have told me to download SP3 as this should correct the problem??

Thanks fo helping in advance.

Regards
Dal

[Robbiebobbie]

Hi,

Looks like this thread went quite in March but I'll give it a try anyway. I'm having similar troubles except that this is the first time I've tried to plug my cancorder into my laptop via firewire.

I'm on Windows XP Home SP2 and have installed an IEEE1394 pc card. My camera is a Samsung VP-D371W MiniDV camera.

I plug the firewire lead in, the camera makes a 'bing bong' noise and the computer does......... nothing! I've successfully replaced the system files with sp1 versions as advised at the beginning of the thread and have disabled the 1394 card in the network settings. Still nothing. I'm guessing the card, camera and lead are ok cos the camera is making a noise every time I connect and disconnect.

Please help cos I need to put video of our soon to arrive baby on the web for my faraway parents to see. Please!

Many thanks,
Rob.

[paglamon]

Which software are you using to try to capture/transfer the video to PC ?

[Robbiebobbie]

Hi Paglamon,

Thanks for replying so quickly. I'm just using Windows Movie Maker 2.1.4026.0 at the moment. Must admit the only thing I hadn't tried was different software - but that was cos I thought the system itself would do something to recognise that the camera was attached first.

Still I'm brand new to digital video so I know very little and welcome all advice!

[paglamon]

Try WinDV (http://windv.mourek.cz/) and let us know what happens.And please make sure that your cam is in PLAYBACK mode.

[Robbiebobbie]

Just tried WinDV but still nothing - WinDV reports error, no device found.

Camera still making connection sound when plugged into IEEE1394 card and have checked that the card is working properly in device manager.

Hmmnn!

[paglamon]

Maybe try another firewire cable ? And you are sure about the settings in the cam itself? It is in "Play" mode ? After connection,is your cam showing in Windows Explorer ?

[Chewy]

The reason sp2 files gave problems is because they raised the standard on 1394 up to it's original specification which allows video capture without dropping frames. I went thru all this quite some time back with a friend and his Samsung mini dv camcorder.

We replaced files, tried different computer setups, and only got a laptop with builtin firewire to work, it turns it out it had a TexasInstrument firewire chipset. He finally broke down and bought a TI card for his desktop, everything worked fine for a couple of years till his motherboard and ram died. We moved the TI firewire card to a newer computer, he's back in business.

I spent days searching threads on this, some cams require firewire that fully supports the standard.

[Robbiebobbie]

Tried another cable but still the same. Camera is definitely in "Play" mode, and no, nothing in Windows Explorer. I'm going to get a friend who has it all working for his camera to try mine and the leads on his pc and see what happens.

Many thanks for all your help so far everyone. I'll let you know how it goes.