Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
17th May 2016, 05:35 | #2943 | Link |
Registered User
Join Date: Feb 2014
Posts: 2
|
Hi,
I just installed the latest stable version. I get this error when I launch the program: "Windows Common Controls 6.0 library (mscomctl.ocx) has not been found in your system. ... Do you want to install it?" I click yes, and I get the same message next time I launch the program. I am on Windows 8.1 Pro 64 bits. What can I do? Thanks in advance |
17th May 2016, 10:22 | #2944 | Link |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,079
|
Hi 8140david and welcome to the forum...
This message means that mscomctl.ocx is not registered in your system. Normally the AVStoDVD installer takes care of this automatically, but in your case it looks like this has been blocked. The file itself should be in the "AVStoDVD\Lib" folder, please verify if it really is there. To register it manually open a command window and run the following command as an administrator: "regsvr32 [filename]" Good luck manolito |
18th May 2016, 12:44 | #2947 | Link |
AVStoDVD Dev
Join Date: Apr 2006
Location: Italy
Posts: 1,302
|
Interesting, let me check why the error persists.
Meanwhile you can download and install the VB6 Runtime package https://www.microsoft.com/en-us/down....aspx?id=24417 Bye |
10th June 2016, 15:23 | #2948 | Link | ||
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,079
|
Quote:
Quote:
Was I too quick to make this change? I cannot test this myself since I absolutely refuse to let Win10 get close to any of my computers. Could some AVStoDVD users who are under Win10 please test at least one of the plugins and report her/his findings? Cheers manolito |
||
10th June 2016, 21:16 | #2949 | Link |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,079
|
After some research it seems clear that the Windows UAC is responsible for this issue. For some reason the compiled batch files trigger this UAC warning only if they were compiled with an included Administrator Manifest.
Personally I always disable UAC completely after every new Windows installation. But I would probably not recommend this to the average user. So I decided to recompile my batch files without Administrator Manifests. Please redownload if you have any UAC issues... http://www109.zippyshare.com/v/FThfn5UY/file.html Cheers manolito |
19th June 2016, 07:01 | #2950 | Link | ||
Registered User
Join Date: Jun 2014
Posts: 82
|
Hello, i have tested avs2dvd under wine. It's runs very well but in authoring must be an error. Is it possible that the script has error or did batchmux use any lib's?
if i want to start it via wine, batchmux did not start. Under windows i see an short windows. Under i wine, id did not do anything. Logfile Quote:
Quote:
And how can i change it? Last edited by Mister XY; 19th June 2016 at 10:38. |
||
19th June 2016, 22:48 | #2951 | Link |
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 948
|
Hello, Mister XY.
Regarding BM, you are working outside of the perimeter of its intended usage & OS environment. Furthermore my knowledge about wine is almost insignificant. However let me try to give some help at the best of my possibilities... First of all you should understand the purpose of BM, as a background information. BatchMux is simply a "compiler"; it creates one authoring "program" (e.g. the MuxMan mxp script file) from the directives and instructions provided by AVS2DVD. Of course, in order to be consistent (and to work properly), this mxp script is referencing and needs a series of inputs (the authoring assets). After creating the mxp script, BM tries to launch MuxMan, by feeding it with the just created mxp script file. OK? That's all! :-) Now, some hints. 1. BM does not need external libreries. To check BM is properly working, you may want to simply launch it FROM A CONSOLE window. After simply typing "BatchMux.exe", it should produce a basic help screen, both under Windows and in wine. 2. During the testing, obviously, it is important to work by instructing AVS2DVD to leave all temporary assets and temporary files in the working directories; otherwise these files are deleted at the end of the AVS2DVD session. 3. From your log file it seems to me that BM operates correctly until the step of creating the mxp file. After obeying to the recommendation of the step 2 above, could you please confirm that the file "Z:\home\thomas\DVD\Temp\DVD_MuxMan.mxp" exists? If so, you can open it with a text editor to get a look at the MuxMan script file... :-) 4. From your log file, BM reports that the preparation of the mxp script file was completed: "Completed preparation of --> MUXMAN SCRIPT", so I am almost sure that the step 3 above was carried out OK in the wine environment. 5. To launch MuxMan, in the the very final steps of the BM code, an OS call similar to "system ("Start /WAIT MuxMan.exe")" is executed, so IN MY UNDERSTANDING, two possibilities exist: or the system call executed by BM is failing under wine, or the system call is working, but MuxMan itself is not working in wine. For sure MuxMan did not start at all in your reported testing session, since it did not produce any log file, as reported in the log line: "BatchMux: ERROR opening Log File Z:\home\thomas\DVD\Temp\DVD_MuxMan.log". 6. Please carry our this test under wine: manually launch MuxMan (simply double click on it). The graphic GUI of MuxMan should start. If so, you please can do: File --> Load Project and open the mxp script file of the step 3. If you simply hit then "Start", you should be able to create manually, with a single click, the whole DVD!!! OK? Cheers, SD Last edited by Sir Didymus; 19th June 2016 at 22:52. |
20th June 2016, 04:51 | #2952 | Link | |||
Registered User
Join Date: Jun 2014
Posts: 82
|
This is the mxp script.
Quote:
Quote:
Quote:
I also have change the standard app from mono to wine. After this, muxman starts. |
|||
20th June 2016, 10:14 | #2953 | Link | |
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 948
|
Quote:
My conclusion is then that the piece of code, within BM, where the "system()" OS call is attempted, is not working in wine. May I ask what happens, under wine, if you type in a console window the command "Start /WAIT MuxMan.exe"? Edit. Hum... What do you mean with "After this, muxman starts"?!? Everything works now via avs2dvd? If so, yuppi! & forget my comments just above... Last edited by Sir Didymus; 20th June 2016 at 10:59. |
|
20th June 2016, 22:35 | #2955 | Link |
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 948
|
So, you confirm that in a wine terminal, if you type: "Start muxman" the MuxMan GUI starts, and if you type "Start /WAIT muxman" it gives an error instead?
If this is the case, frankly speaking, I am definitely non in favour of providing support to this case... The /WAIT argument is quite important for the Start command... What shall I do if it is not implemented in its full form in wine? Of course, in principle, the whole spawning mechanism adopted by BM could be changed, in order to avoid using the Start command. The idea could be to create a batch file, with the MuxMan C/L arguments and to launch this new batch file by means a different "system" call from within the code of BM. The point is that this change would be just beneficial to improve the compatibility with the wine envinonment, at the risk of introducing issues for other users running AVS2DVD in the Windows environment... Mhhh, I don't think it's a good idea to implement things in this way... Especially considering that you already have a working solution to complete manually the authoring session... Sorry, SD Last edited by Sir Didymus; 20th June 2016 at 22:43. |
21st June 2016, 10:27 | #2957 | Link |
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 948
|
Could you try this?
http://www10.zippyshare.com/v/rGVzWdp0/file.html It is a snippet of code doing this: Code:
#include <stdio.h> #include <process.h> main() { int ret = 0; printf ("Test1 - Using \"system()\" OS call\n"); printf (" - TP1 - before executing MuxMan...\n"); ret = system ("MuxMan.exe"); printf (" - TP2 - after executing MuxMan; \"system()\" --> %d\n", ret); } Last edited by Sir Didymus; 21st June 2016 at 10:36. |
21st June 2016, 18:22 | #2959 | Link |
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 948
|
This is very strange !?!?
Sorry, we can not see the direct attachments in the replies until they are approved by some mod, but this is not relevant anyhow. What you say is indeed very clear and very strange. Well, let see... The executable of BM acts exactly like the snippet of code in my previous post. So, you can do another test, if you wish... In the program folder of AVS2DVD there should exist one file named BatchMux.exe. In the temporary files assets ("Z:\home\thomas\DVD\Temp") there should exist one initialization file named "DVD_BatchMux.ini". Please copy BatchMux.exe into this directory, and then, from a console window, type "BatchMux.exe -arglist DVD_BatchMux.ini". Is MuxMan starting? Maybe some privileges should be attributed to the executable BatchMux.exe? What about changing the standard app from mono to wine also for BM? Last edited by Sir Didymus; 21st June 2016 at 18:30. |
|
|