1.1.9 on Windows Vista x64 doesn't start

[kbirger]

When I run any of the .cmd files, I get a blank dos prompt box for a quarter of a second, and then it closes and the program does not start.

I'm using Vista x64 Ultimate, UAC disabled. I've tried running the .cmd files from prompt to see if there is any output, but there is none. I don't have a settings directory in %appdata%\deluge (folder does not exist) and therefore have no logs.

Any suggestions?

[kbirger]

I hardly imagine that nobody has ever heard of this bug. Kind of a big deal, and bad form. So, a little help here?

[devians]

checking in that this is also a problem on win7 64bit

[kbirger]

There has been talk that it's an issue with the program files (x86) as an install directory, and the the regular progfiles is the one referenced in scripts, but moving the install to the normal one did not help me. Have you tried that? I wonder if your results will be different. Please check back, since it looks like we're on our own here:)

I wish I could figure out how to start a trouble ticket, because I think this would actually get noticed then.

[andar]

There has been talk that it's an issue with the program files (x86) as an install directory, and the the regular progfiles is the one referenced in scripts, but moving the install to the normal one did not help me. Have you tried that? I wonder if your results will be different. Please check back, since it looks like we're on our own here:)

I wish I could figure out how to start a trouble ticket, because I think this would actually get noticed then.

It wouldn't.. To be honest. The only windows version I test on is 32-bit XP.. Don't have the time or resources to purchase the bajillion different versions of Windows and test them. And getting the Windows port to work at all is a bit of a pain since Windows doesn't have a proper package manager like linux distros.

[kbirger]

So shall I give up, or do you have any suggestions?

[loki]

I'm not sure, seeing as you say UAC is disabled seems that might be the only main difference between your setup and mine. Since it's disabled I assume when you installed it it didn't ask you permission to install? It might be that it had default permission to install but didn't have permission to write the settings to the proper locations (your appdata folder).

You could try installing it as administrator, or alternatively, try enabling UAC and reinstall under UAC.

[kbirger]

I am *THE* administrator. Using this account is like running everything "as administrator". I've seen posts on the internet suggesting that you hardcoded some paths. I don't know how to mess with all the python sources, but perhaps it would be a worthwhile venture to use system variables instead. If it is indeed having trouble writing to settings, shouldn't it inform the user, or at the very least log it somewhere? I'm getting nothing.

I have also tried creating the deluge folder in appdata\roaming and appdata\local, where the FAQ says it should be. this way I surely have permissions. Still nothing.

[loki]

On a separate but related note, you really should consider a standard user account for everyday use. And why bother disabling UAC if you're using the administrator account anyway?

[kbirger]

I'm not sure how to understand the meaning of your last post Loki. You're not saying that it's not important for your software to work on my system just because I have different settings, are you?

I don't think you're very familiar with how UAC works on windows. Using the administrator account IS what is disabling it. I don't have it explicitly disabled. I choose to do this because I would much rather be careful about what gets on my computer rather than relying on a piece of software to do it for me. I don't use anti-virus either, on any of my computers, and I have not gotten as much as a popup on any of them.

UAC does not change directory structure of the computer. If it would make you happier, I could make a second account and install it from there, but I don't see that it would make any difference. I only mentioned UAC because I know the first order of troubleshooting with Vista is "Did you run the install as administrator? Are you sure?" (Just one more reason why I dislike it). This way, there's no question that lack of permissions due to UAC is a problem.