DamnVid doesn't start on Windows 7

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install DamnVid on Windows 7
2. Click the DamnVid shortcut

What is the expected behavior? What do you see instead?
Expected: DamnVid starts.
Seen: DamnVid doesn't start.

Original issue reported on code.google.com by Jens.K.L...@gmail.com on 28 Jun 2010 at 10:32

• Merged into: #82

Attachments:

• damnvid.log

[GoogleCodeExporter]

Duplicate of issue 82: You probably have an invalid PATH environment variable.
To fix it, open the dialog to edit it:
http://damnvid.googlecode.com/svn/trunk/img/win32-setpath.noinclude.png
And remove the empty path component that it probably has.

This has been fixed in trunk, so the next release won't fail so pathetically 
when facing that problem, hopefully. Thanks~

Original comment by windypo...@gmail.com on 28 Jun 2010 at 10:38

• Changed state: Duplicate
• Added labels: Priority-High, OpSys-Windows, Usability
• Removed labels: Priority-Medium

[GoogleCodeExporter]

There is no empty path component AFAICS:

C:\Program Files\Common Files\Microsoft Shared\Windows 
Live;C:\Tcl\bin;C:\Ruby\bin;C:\Program Files\Mercurial;C:\Program Files\MiKTeX 
2.8\miktex\bin;C:\Program Files\PHP\;C:\Program Files\ed\bin;C:\Program 
Files\sed\bin;C:\Program Files\Python;C:\Program 
Files\SVN\bin;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\msls;C:\Program 
Files\NcFTP;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Pro
gram Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Swiss File 
Knife\;C:\Program Files\Console2\;C:\program files\FAR Manager\;C:\program 
files\vim\vim72\;c:\Program Files\Microsoft SQL 
Server\90\Tools\binn\;C:\PROGRA~1\NcFTP;C:\Program Files\GnuPG\pub;C:\Program 
Files\Git\cmd;C:\Program 
Files\SVN\bin\;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program 
Files\Mercurial\;C:\Program Files\TortoiseSVN\bin;C:\Program Files\Dell\DW WLAN 
Card;C:\Program Files\Windows Live\Shared

No invalid ; contained.

Original comment by Jens.K.L...@gmail.com on 28 Jun 2010 at 10:50

[GoogleCodeExporter]

Well damn, that's weird. Are you sure you didn't omit a trailing semicolon or 
something like that? Or that things like ";%SystemRoot%;" don't become ";;" (if 
%SystemRoot% is undefined)?

If not, then just to confirm, edit your path temporarily to only have the 
basics (just one or two path components) and see if DamnVid runs, then edit it 
back.

Original comment by windypo...@gmail.com on 28 Jun 2010 at 10:57

[GoogleCodeExporter]

%SystemRoot% pretty much /is/ defined. No, I copied it directly from that 
dialog.

With %SystemRoot%;%SystemRoot%\system32 DamnVid starts. But why?

Original comment by Jens.K.L...@gmail.com on 28 Jun 2010 at 11:05

[GoogleCodeExporter]

Ah; according to the log file, my PATH variable is "too long"; so it is 
definitely a problem in your string handling.

Original comment by Jens.K.L...@gmail.com on 28 Jun 2010 at 11:09

[GoogleCodeExporter]

Yes, should be fixed in the next release already. You can try building from 
source if you want the fix now, but it's really a pain to do in Windows.
Though, looking at your PATH, I'd say you're a developer, so it probably won't 
be that hard for you :)

Original comment by windypo...@gmail.com on 28 Jun 2010 at 11:14

[GoogleCodeExporter]

Haha, yes, probably.
Any README on how to compile?

Original comment by Jens.K.L...@gmail.com on 28 Jun 2010 at 11:18

[GoogleCodeExporter]

Here: BuildingFromSource

Original comment by windypo...@gmail.com on 28 Jun 2010 at 11:26

[GoogleCodeExporter]

Hmm, Py2exe does not like my Python version as it is "too new", obviously; so, 
anyway, I'll better wait for DamnVid 1.7 then. :-/

So far: Thank you for your work, the sneak peek I took already looked 
promising. :)

Original comment by Jens.K.L...@gmail.com on 28 Jun 2010 at 11:33