|
|
VDubMod Matroska not working at all
I have posted this bug in the bug tracker but nobody pays attention to it.
Since the last VDubMod release (the first with matroska support), I am no more able to launch the application. It crashes right at the start. I get the a Visual c++ error message and that's all.
What's the matter? Never happened before! Neither with VDub nor VDubMod.Pirata
Sorry, I don't know what happens and can't debug since it doesnt happen here
I hope its gone in the next version.
I'll try to collect more info about both my system and the dll where the problem is. Maybe this can help you to detect what you changed that could be causing this.
Thank for answering so quick, anyway. I'll post later.
Pirata
Hi Belgabor. Sorry about the late.
My system: PIII@800MHz, Windows XP Pro (without SP1), 384MB RAM, GeForce2 MX 32MB, HD BarracudaIV 60GB. VIA chipset-based motherboard. Latest drivers.
VirtualDub and VirtualDubMod had never failed on my system until 1.5.1.1a. In fact. Latest VirtualDub (1.5.4 I think) works fine.
The problem in detail: when VirtualDubMod 1.5.1.1a is launched, it crashes right at the beginning (an error dialog of the Visual C++ library is issued and then the process dies). After removing all the dlls from the VDubMod folder, the executable does no more crash when it is run, but only complain because it lacks corona.dll, after which the process dies. When corona.dll is replaced back to the folder, the executable complains that it lacks ogg.dll, and afterwards, vorbis.dll. Once the latter is replaced back in the folder, the executable begins to crash again, so the problem somehow has to do with vorbis.dll.
I have tried to use the vorbis.dll from the last (working) version, but the erros happens again, so the bug must be within the VDubMod executable. Also, I have used the vorbis.dll from the 1.5.1.1a with the last (working) version and the application started up without a problem. So it seems the flaw is in the executable.
I have tried to start windows XP in safe mode using the administrator account, and then to start Virtualdubmod. I got similar error, so it seems not to have any relation to any resident program I use.
Could you tell me, Belgabor, what I should do? How can I further track down the problem?
Thanks for the info, unfortunately it doesn't really help
Those three dlls are linked statically into VDubMod. This means they are loaded by windows before any VDubMod code is executed. I'll think about what can be done to help you or what you can do to pinpoint the problem and come back to you.
Cheers
Belgabor
Hi Belgabor. Any news about this problem? Not being able to use this Matroska-capable version of VdubMod is killing me, I can tell you...
I wonder why this happens to me alone. It must be something that is running in the background, or that I have installed, that makes VDubMod crash. It doesn't crash in my brother's PC!!!
I don't understand why my info wasn't helpful. Now we know where the problem is, don't we?
No, we dont. Because of the way windoes and static linking (in windows) works, no virtualdub code is ever executed if those three dlls aren't found, so its no diffrence in vdubmod code execution between all three missing and only the last one missing, none is executed
Could you please pm me an email address? I'll make a test version for you.
Edit:
I was mixing up things, its not static linking, but one of the ways to link dynamically. This is only a matter of technic correctness, it doesnt change what I've said about findig the bug.
I just have pmed you my address, Belgabor.
But: maybe I didn't make myself clear. The three dlls are in the VDubMod folder when I start the executable. Enough dlls (3, corona, ogg and vorbis) can be reached and Windows begins executing VDubMod code. Then the crash comes.
It makes me feel unconfortable having you do extra work for me. I just can't understand what is wong with my computer, because you wonderful proggie works in anybody else's... anyway, thank you for paying so much attention to my problem.
Originally posted by pirata
I just have pmed you my address, Belgabor.
But: maybe I didn't make myself clear. The three dlls are in the VDubMod folder when I start the executable. Enough dlls (3, corona, ogg and vorbis) can be reached and Windows begins executing VDubMod code. Then the crash comes.Well, what I meant is you can't deduce the fault is with corona.dll because the error pops up when you add it, since before you add it no vdubmod code is executed.
I will come back to you probably un Tuesday since I'm not on my devel machine till then. No trouble about the effort, I'm quite curious what might be the trouble
Hey Belgabor !
Any news?
Hey Belgabor !
Any news? |
|