3.16.8 build2 / W7 Problems
Mon, 06/07/2010 - 10:49 — Jem
New problem ever since updating to 3.16.8 build2 on a new build W7 Ult. machine. Basically DeVeDe fails to start. The process is running in Task Manager but no DeVeDe GUI. Tried it three times last night and eventually the GUI appeared, at which point DeVeDe successfully converted a movie file. Today, after restarting the machine and trying to use it again - exactly the same problem. Uninstalled build2 and reverted to build1 - no problem, starts every time, so I can only assume that this has something to do with the cycwin 1.7 update. I notice on the cygwin site that there are some configuration changes and some related 'warnings' there, but I'm no cygwin expert so it's hard to interpret. I'm only guessing that's where the problem lies....
AddThis
Syndicate
Popular content
Recent comments
- I installed DeVeDe;
2 days 11 hours ago - First you will need a
5 days 13 hours ago - Sorry, but that is most
5 days 13 hours ago - ok thank you very much.
6 days 17 hours ago - For each video that you want
1 week 16 hours ago - I'd be grateful if you get
2 weeks 19 hours ago - I am not sure what the 'Force
2 weeks 19 hours ago - Thanks for the update Peter -
2 weeks 4 days ago - Thanks, glad it is working.
2 weeks 5 days ago - Thanks Peter!
2 weeks 5 days ago
I was having the same problem
I was having the same problem before the update to cygwin 1.7. It is probably hanging when checking if the backend programs exist and thus never shows the gui. I could take out the code that checks for mencoder, vcdimager, spumux ..... since they will always exist when install from the devede.msi.
If I get some free time tonight I think I will comment out that code and upload a new package to see if that is what is causing the problem. I am almost sure that is the problem since devede is written in python and subprocess handling on windows using python is very good (or I am just no good with python and windows). I believe that is supposed to be fixed in python 3.2, see http://www.python.org/dev/peps/pep-3145/.
Solved...?
In the past couple of days (out of desperation), I tried starting DeVeDe (Build2) using devede.exe directly rather than DevedeLauncher.exe - bingo! (so it seems...). DeVeDe starts and completes the job (creating an ISO in my case) perfectly and has started ever since. Go back to using the launcher....nothing. I believe this is the first build using the Launcher...? Why the need for it?
The only purpose of
The only purpose of DevedeLauncher.exe is so devede displays its proper icon in the windows start menu on Windows Vista/7. This is only a temporary measure until py2exe supports creating python exe that display icons on vista/7. DevedeLauncher is not the cause of the problem. I can run devede.exe with or without the launcher, either way it only opens about 75% of the time now.
That's curious...
Well, firstly I have created a 'devede.exe' shortcut for the start menu, 'borrowing' the icon from DevedeLauncher (common method), so that's no issue. Otherwise, I would say that DeVeDe is starting 100% of the time on this Win7 system - I test it every time I boot to make sure!