Cygwin usage

Hi...

I am new to DeVeDe. I really like it; it is nice and simple to use.

I noticed that Cygwin is used under the hood and included directly in the install. For users that use Cygwin for other things (like me), this can cause a problem. With the 1.5 series Cygwin, there should only be one version of the cygwin1.dll open at a time, because the dll maps shared memory and multiple cygwin1.dlls open can cause memory corruption.

The current version, 1.7 series, avoids this problem, by setting everything up relative to the absolute path to the cygwin1.dll file. Multiple cygwin1.dll files run from different locations do not interact. Would you please update to the current version. I am a long time Cygwin user, so I can help, if you like.

Also, I could not find the source code on your website for the version of Cygwin and tools linked with it. The GPL requires that you have source code available for the version you distribute. A link to the source on another website is not good enough to meet the requirement.

Thanks for making DeVeDe available to Windows users!

...Karl

I will see about updating to

I will see about updating to cygwin 1.7 this weekend or next weekend. All source code links are on the devede development page or found http://www.majorsilence.com/open_source_deps. Any GPL code I am using should have matching source packages for download there.

Thanks

Thanks

I have updated cygwin to 1.7

I have updated cygwin to 1.7 and uploaded a new installer (3.16.8 build2).

3.16.8 build2 / W7 Problems

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....

Thanks, ...Karl

Thanks,

...Karl