GeorgeK and all
Moderator: Ken Berry
-
Trevor Andrew
GeorgeK and all
Hi GeorgeK
Did you solve the problem relating to the Windows Installer and VS 9 crashing on video capture?
I am using Win 2 K.
I can capture ok provided I uninstall Windows Installer.
My problem seems to be related to VS 9, Win Installer, win 2K and may be my capture card (ati 128 pro )
I have had no positive response from Ulead
Just wondered if a solution has been found
E-Mail talamail2004-forum@yahoo.co.uk
All the Best
Thanks Trevor
Did you solve the problem relating to the Windows Installer and VS 9 crashing on video capture?
I am using Win 2 K.
I can capture ok provided I uninstall Windows Installer.
My problem seems to be related to VS 9, Win Installer, win 2K and may be my capture card (ati 128 pro )
I have had no positive response from Ulead
Just wondered if a solution has been found
E-Mail talamail2004-forum@yahoo.co.uk
All the Best
Thanks Trevor
-
THoff
Did you try again with the updated Windows Installer V3.1? Microsoft pulled it and re-released it as V2:
http://support.microsoft.com/default.as ... -us;893803
http://support.microsoft.com/default.as ... -us;893803
-
Trevor Andrew
-
Trevor Andrew
-
THoff
-
Trevor Andrew
-
THoff
You can find out where the log is being saved by running Dr. Watson -- select Start -> Run and enter drwtsn32. The first edit control in the Dr. Watson dialog is the location where the text file gets saved.
Go to the folder, and open up the file drwtsn32.log using Notepad. Go to the end of the file, then search for the string "FAULT" from the bottom up. The location shown is the fault location, and the "Stack Back Trace" section just below that will hopefully reveal additional information to tell how we got there.
Go to the folder, and open up the file drwtsn32.log using Notepad. Go to the end of the file, then search for the string "FAULT" from the bottom up. The location shown is the fault location, and the "Stack Back Trace" section just below that will hopefully reveal additional information to tell how we got there.
-
Trevor Andrew
Hi THoff
Thanks for the info.
Below is the Stack Back Trace, to me its just a load of numbers and means very little.
Although there is a reference to AVI and capture.
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0012E764 77E3A3D0 000803EC 00000081 00000000 0012E808 <nosymbols>
0012E784 77E14750 12F78259 000803EC 00000081 00000000 user32!SetWindowPlacement
0012E7A0 77E1CF3F 00EA6E28 00000081 00000000 0012E808 user32!TranslateMessageEx
0012E7D0 77F9FF57 0012E7E0 00000060 00000060 00000000 user32!SetScrollPos
0012E8E8 77E23C9D 00000000 130FE000 00000000 00000000 ntdll!KiUserCallbackDispatcher
0012E924 130F1E97 00000000 130FE000 00000000 54000000 user32!CreateWindowExW
0012E960 130F1EF7 00000000 54000000 00000000 00000000 avicap32!capCreateCaptureWindowW
0012E990 130E3905 00000000 54000000 00000000 00000000 avicap32!capCreateCaptureWindowA
0012EAEC 130E3CF9 08EB8BC8 00000000 130E0000 08EB3EB7 !<nosymbols>
0012EAFC 08EB3EB7 00000001 08EB8BC8 0012ECDF 00000001 !<nosymbols>
130E0000 00000003 00000004 0000FFFF 000000B8 00000000 !<nosymbols>
does that mean anything to you
Thanks Trevor
Thanks for the info.
Below is the Stack Back Trace, to me its just a load of numbers and means very little.
Although there is a reference to AVI and capture.
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0012E764 77E3A3D0 000803EC 00000081 00000000 0012E808 <nosymbols>
0012E784 77E14750 12F78259 000803EC 00000081 00000000 user32!SetWindowPlacement
0012E7A0 77E1CF3F 00EA6E28 00000081 00000000 0012E808 user32!TranslateMessageEx
0012E7D0 77F9FF57 0012E7E0 00000060 00000060 00000000 user32!SetScrollPos
0012E8E8 77E23C9D 00000000 130FE000 00000000 00000000 ntdll!KiUserCallbackDispatcher
0012E924 130F1E97 00000000 130FE000 00000000 54000000 user32!CreateWindowExW
0012E960 130F1EF7 00000000 54000000 00000000 00000000 avicap32!capCreateCaptureWindowW
0012E990 130E3905 00000000 54000000 00000000 00000000 avicap32!capCreateCaptureWindowA
0012EAEC 130E3CF9 08EB8BC8 00000000 130E0000 08EB3EB7 !<nosymbols>
0012EAFC 08EB3EB7 00000001 08EB8BC8 0012ECDF 00000001 !<nosymbols>
130E0000 00000003 00000004 0000FFFF 000000B8 00000000 !<nosymbols>
does that mean anything to you
Thanks Trevor
-
THoff
Yes it does. The crash occurs in some internal, unnamed function called by the SetWindowPlacement API, which determines whether a window is visible, hidden, minimized, maximized etc. This really shouldn't be causing a crash.
Are there any other Windows Updates that you haven't applied yet, or updated video drivers you could try?
Are there any other Windows Updates that you haven't applied yet, or updated video drivers you could try?
-
jgonick
Well I'm another one with the problem. Surely Ulead won't ignore everyone. I'm also running win2k with a geforce card. I've tried updating the installer to v2, but it still crashes on my system. Fortunately I have other software that can capture, but I hope Ulead comes out with a fix.
Side note: Here is my stack back trace to compare: (looks like the same)
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0012E248 77E3A3D0 00160106 00000081 00000000 0012E2EC <nosymbols>
0012E268 77E14750 0E628259 00160106 00000081 00000000 user32!SetWindowPlacement
0012E284 77E1CF3F 00E786F8 00000081 00000000 0012E2EC user32!TranslateMessageEx
0012E2B4 77F9FF57 0012E2C4 00000060 00000060 00000000 user32!SetScrollPos
0012E3CC 77E23C9D 00000000 0E7AE000 00000000 00000000 ntdll!KiUserCallbackDispatcher
0012E408 0E7A1E97 00000000 0E7AE000 00000000 54000000 user32!CreateWindowExW
0012E444 0E7A1EF7 00000000 54000000 00000000 00000000 avicap32!capCreateCaptureWindowW
0012E474 0E793905 00000000 54000000 00000000 00000000 avicap32!capCreateCaptureWindowA
0012E5D0 0E793CF9 08A88BC8 00000000 0E790000 08A83EB7 !<nosymbols>
0012E5E0 08A83EB7 00000001 08A88BC8 0012E7C3 00000001 !<nosymbols>
0E790000 00000003 00000004 0000FFFF 000000B8 00000000 !<nosymbols>
Side note: Here is my stack back trace to compare: (looks like the same)
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0012E248 77E3A3D0 00160106 00000081 00000000 0012E2EC <nosymbols>
0012E268 77E14750 0E628259 00160106 00000081 00000000 user32!SetWindowPlacement
0012E284 77E1CF3F 00E786F8 00000081 00000000 0012E2EC user32!TranslateMessageEx
0012E2B4 77F9FF57 0012E2C4 00000060 00000060 00000000 user32!SetScrollPos
0012E3CC 77E23C9D 00000000 0E7AE000 00000000 00000000 ntdll!KiUserCallbackDispatcher
0012E408 0E7A1E97 00000000 0E7AE000 00000000 54000000 user32!CreateWindowExW
0012E444 0E7A1EF7 00000000 54000000 00000000 00000000 avicap32!capCreateCaptureWindowW
0012E474 0E793905 00000000 54000000 00000000 00000000 avicap32!capCreateCaptureWindowA
0012E5D0 0E793CF9 08A88BC8 00000000 0E790000 08A83EB7 !<nosymbols>
0012E5E0 08A83EB7 00000001 08A88BC8 0012E7C3 00000001 !<nosymbols>
0E790000 00000003 00000004 0000FFFF 000000B8 00000000 !<nosymbols>
-
jgonick
-
Trevor Andrew
-
jgonick
Well I'm back to square one. I installed some other software and now I can't capture again. I called Phone support....useless. All I got was.. thats strange. Must not be compatible with your driver for the capture device....sorry... Which makes me wonder.....Why does it work the first time (and only once) after it is installed?...Why did it work for a while before I installed other unrelated software..(see above for brief work around)?
Its ashame..I think it is very good software for editing...to bad it is awful on capture..........
UPDATE: the above still works for me if I drag a clip to the timeline first in the edit tab, then import dvd in the capture tab, close. Then choose capture.
This is odd.. but it works.
Its ashame..I think it is very good software for editing...to bad it is awful on capture..........
UPDATE: the above still works for me if I drag a clip to the timeline first in the edit tab, then import dvd in the capture tab, close. Then choose capture.
This is odd.. but it works.
