How it was:

Step 1.

In short words, in my case the solution is set off : integrated audio, net card, usb controllers integrated in motherboard, usb controllers on pci card, PCI SATA RAID controller. and capture from Windows 2000 sp4 rus.


My camcorder is CANON MV901. i used it about half year. and until last time i do not know about problems with capturing in win xp sp2. At first i copy dv stream from CANON to notebook IBM R50 (Celeron 1400,256,40) WIN XP SP2 RUS (Windows is native with notebook) through PCMCIA FIRE WIRE ST-LAB (model do know remember- on controller is not signed, and controller `s box layed somewhere). <===== And with this hardware + Adobe Premiere 2 i capture dv stream without any problems. There is no any drpoped frames.

Later i bought ST-LAB F-114 PCI3+1 USB 2.0 +2 FIRE WIRE and plug it in my big :) comp (CELERON 1200 TUALATIN, 512, ASUS Ti4200). Now i can`t exactly say in what version WIN XP i can achive stable capture without drop frames etc. But i can exactly say that it was not WIN XP SP1. it was WIN XP SP2 or WIN XP SP0. Small remark: i have two ST-LAB RAID controllers on chips SILICON IMAGE 0680A-IDE RAID and SILICON IMAGE 3114-SATA RAID. Well... i bought SATA RAID not lately (but before upgrade. about upgrade see down) and i found problem. That controllers from this manufacter conflicts with each other if they both is plugged into motherboard. It was appeared problem with booting, when i bought ST-LAB PCI FIRE WIRE controller and plug into motherboard all three cards: SATA RAID, IDE RAID, FIRE WIRE. Controllers was determined by bios and then black screen and booting was stopped. It want boot even from cd-rom. black screen and that was all. i tryed plug cards into another slots and another variants. but eventually i did it :). but now i can not exactly said what was solution. But it is important that eventually WINDOWS XP was booted and capturing was work. It takes me several hours. Later i did upgrade (now i think that if i bought notebook it was more great) PENTIUM D-915, 512, GYGABYTE GE FORCE 7600 GS-256M and on new hardware i installed all PCI CARDS and they work without problem, great. But such it was happened that i forgot to try capture on new hardware until this day :)))))). I tried WIN XP SP0,SP2 , patches from Microsoft- but all this solutions was unseccessfull. In all cases the symptom was the same: camcorder was determined in program , capture was started and was continued 5-10 seconds, after this period program was fly away. Then i go to internet to read about this phenomenon and found that many people write about this , that is a real problem and there is no exactly solution. Wow. The main thing that it was suggested was to use WINDOWS XP SP1, and if you have SP2 then to replace some files from SP2 to SP1. But i did not have SP1. At first i replaced set of files from SP0 to SP2. it helped not me. Then i found needed files from SP1 (english version) and put them into SP2. it helped not me. - and i specially checked in device manager that windows do not replace my files on SP2 version files. Then i try drivers for FIRE WIRE from UBCORE and http://thesycon.de - program is named vhpd. Demo version from UBCORE must work 30 minutes. From thesycon.de must work 2 hours. I tryed both, but the result was unsuccessful. I do not know why, may be i do not understanded. I installed program from UBCORE, but when i power "on" my camcorder, in device manager is do not added nothing device. Ther are some interface programs in UBCORE programs , which is appeared after installation. One of this is designed how i suppose for camcorder. On this program i can not found any active camcorders when my CANON was set "on". Then i uninstalled UBCORE and installed vhpd. when i set power "on" in device manager was appeared device, but in section "FIRE WIRE device" and NOT in the section "video devices". In program interface of vhpd is difficult to understand how to... ==> From this i am interested if someone know how to successfuly work with this alternative drivers of FIRE WIRE + XP SP2 +camcorder. :)

Ok. I decided to apply myself in the direction of WIN 2000, in which i have read on this moment there is no problems. I thinked: sounds good :). I installed WIN 2000 SP4. Then did capture and in the preview screen i saw video + some squares. And after capture, when i saw video material then i saw video + some squares. Then I read about such thing as "several devices on one IRQ". Ok. Let`s try this.:). I opened device manager and saw several cases when one IRQ is associated several devices. Ok. Set off integrated audo, netcard, and all usb controllers. After this i got situation - one IRQ-one associated device.But! :) After this i did capture and see again squares . Then i remember that in the past i had problems with RAID controllers. I set of one of RAID controllers from this i did no boot. And then I did capture and squares was disappeared. I capture 30 min without any dropped frames, squares and any other problems. :) After this i made iso image of windows 2000 and decide to apply myself to WIN XP SP2 again. And I DID IT :))!!!!


Chapter 2.

The solution for WIN XP SP2 is to use drivers and .inf files for FIRE WIRE controller and camcorder versions: windows 2000 sp4, windows xp sp1, windows xp sp2.


I will describe in what conditions i have exactly working system. I checked several times by reinstalling WIN XP SP2 from zero. Here i want to pay attention to the fact, that you have another sound card then me and your process will something differ from process described here. I want to point to right way. I have two core processor. I used windows xp sp2 rus, windows xp sp1 rus, windows 2000 sp4 rus. windows xp sp2 worked in demo mode (30 days without activation).


It is done like:


1) install xp sp2 with core "multiprocessor MPS" (now i think this is not critical needed condition)

2) install all needed drivers, then if it is install from cd-rom, then remove cd-rom. if it is install from from folder, then rename folder. another words - remove source of distributive windows and drivers.

3) in device manager set off all devices which is associated to the same IRQ as FIRE WIRE controller

4) rename sp2.cab

5) remove files in folder dllcache


Here i describe folders with name and versions of files that i used. files


in this folders is described files that is used in installation process

c:\inst files\[camera+zvuk]

ksclockf.ax 5.00.2165.1 not depend from language W2000SP4

ksdata.ax 5.00.2134.1 not depend from language W2000SP4

ksinterf.ax 5.00.2134.1 not depend from language W2000SP4

ksproxy.ax 5.00.2134.1 not depend from language W2000SP4

kstvtune.ax 5.00.2134.1 English (USA) W2000SP4

ksvpintf.ax 5.00.2134.1 not depend from language W2000SP4

kswdmcap.ax 5.00.2134.1 English (USA) W2000SP4


ksxbar.ax 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

iyuv_32.dll 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) Russian XPSP2

ksuser.dll 5.3.2600.2180 (xpsp_sp2_rtm.040803-2158) not depend from language XPSP2


msyuv.dll 5.00.2134.1 English (USA) w2000SP4


tsbyuv.dll 5.1.2600.0 (XPClient.010817-1148) English (USA) XPSP0

vfwwdm32.dll 5.1.2600.1106 (xpsp1.020828-1920) Russian XPSP1

msh263.drv 5.1.2600.2180 Russian XPSP2


ks.inf DriverVer=03/16/2000,5.00.2195.1

kscaptur.inf DriverVer=03/16/2000,5.00.2195.1

ksfilter.inf DriverVer=03/16/2000,5.00.2195.1

msdv.inf DriverVer=03/16/2000,5.00.2195.1


(I do not remember from what windows versions i used .inf files, but i give string DriverVer, which is contained within needed .inf files. In according DriverVer it can determine from which windows version is used .inf files.)


ks.sys 5.1.2600.1106 (xpsp1.020828-1920) not depend from language XPSP1

msdv.sys 5.00.2195.6655 English (USA) W2000SP4

stream.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1


c:\inst files\[camera+zvuk]\[posrsinhpot]

MSPCLOCK.sys 5,008 байт 5.00.2134.1 Microsoft(R) Windows (R) 2000 Operating System not depend from language



c:\inst files\[fire wire nec]

1394.inf DriverVer=07/01/2001,5.1.2535.0

1394bus.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

arp1394.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

enum1394.sys 5.1.2600.0 (xpclient.010817-1148) English (USA) XPSP0

nic1394.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

ohci1394.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1


c:\inst files\[zvuk karta]


ksuser.dll 5.3.2600.2180 (xpsp_sp2_rtm.040803-2158) not depend from language XPSP2

drmk.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

portcls.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

stream.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1


(drivers of sound card indicate that it is absent in windows distributiv)


files in this folders must be in properties of driver of device in device manager. In according this files it can check set and versions of files.



c:\[ustanovlennoe]\[camera]

msyuv.dll 5.00.2134.1 English (USA) w2000SP4

msdv.sys 5.00.2195.6655 English (USA) W2000SP4

stream.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1


c:\[ustanovlennoe]\[fire wire]

1394bus.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

arp1394.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

enum1394.sys 5.1.2600.0 (xpclient.010817-1148) English (USA) XPSP0

nic1394.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

ohci1394.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1


c:\[ustanovlennoe]\[zvuk karta]

a3d.dll -driver sound card

ksuser.dll 5.3.2600.2180 (xpsp_sp2_rtm.040803-2158) not depend from language XPSP2

wdmaud.drv-driver sound card

aeaudio.sys-driver sound card

drmk.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

portcls.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1

senfilt.sys-driver sound card

smwdm.sys-driver sound card

stream.sys 5.1.2600.1106 (xpsp1.020828-1920) English (USA) XPSP1


6) replace files which is contained in properties of sound card on suchlike from folder c:\inst files\[zvuk karta] и c:\inst files\[camera+zvuk].

such as:

drmk.sys

ks.sys

portcls.sys

stream.sys

ksproxy.ax

(wdmaud.drv and ksuser.dll it may not replace because we need such versions as is sp2).

That is in other words we replace only common windows sound driver files, and do not touch specific sound card files. If windows something say when we replace files we answer "cancel-yes" ,here and later.

Reboot. After this replacement sound card must continue work properly.

7) remove from windows/inf all files which names is the same as in folder c:\inst files\[camera+zvuk].

such as:

ks.inf

kscaptur.inf

ksfilter.inf

msdv.inf

8) install new drivers for FIRE WIRE controller from folder c:\inst files\[fire wire nec]. Do this by such method: device manager-your fire wire controller-right button click-upgrade driver-no not this time-installation from pointed place-do not make finding i choose needed driver myself-installation from disk-review-make finding c:\inst files\[fire wire nec]\1394.inf-choose in pop up windows model your fire wire controller, in my case it is nec ohci 1394-when windows will answer about ohci1394.sys and others =>choose ohci1394.sys from the same as above folder (c:\inst files\[fire wire nec]), when windows will answer "replace?" => we answer "yes" in all cases-reboot.

9) now we have fire wire controller drivers versions as : 5.1.2600.0 и 5.1.2600.1106 (check it in device manager)

10) plug in and power on camcorder. if .inf files was removed properly (see 7) then windows do not find drivers and will answer us to point properly drivers, by pop up windows "Wizard of new hardware". Choose like described above our custom installation path for drivers : c:\inst files\[camera+zvuk]\msdv.inf, and choose "microsoft dv -камера и VCR", camcorder is installed.

11) after this windows will find new device "closed caption decoder", windows will not find driver for it. go device manager-sound and game controllers and will see new device "not identified device" is signed -"!" . Click update driver, path to new driver is c:\inst files\[camera+zvuk]\ks.inf, in the appeared window choose "посредник of synchronization flows Microsoft". After if windows will not find driver MSPCLOCK.sys then it must point path to new driver c:\inst files\[camera+zvuk]\[posrsinhpot]\MSPCLOCK.sys. If windows will find itself driver MSPCLOCK.sys, then it must replace it on c:\inst files\[camera+zvuk]\[posrsinhpot]\MSPCLOCK.sys. Reboot.

12) It is very wanted to check versions of files between windows and c:\inst files\. The versions must coincide with each other.

13) That is all. It may check capture.


I checked it in ulead dvd media factory and adobe premiere 2.0

While i push "play" in camcorder and see the result on preview windows in ulead , then i see that picture in preview window not moving. But I mark that I only "play and see" and i do not capture in ulead in this case. But while i capture in ulead then all be great :) picture was moved in preview screen and was not any problem.

In adobe premiere all was be great :).

I must said that in case of win xp sp2 (such as was in case windows 2000) i set off one of my RAID controller , because if i did not this , i got squares in captured dv stream. But it is very simple to do through device manager before capturing and it is small problem for me :)

enjoy :)



Chapter 3


you may to try more small and fast solution (may be it run, may be not)- by dismiss 1,3,5,6,8 and this set of files.

Сайт управляется системой uCoz