Crash apun startup

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start up the program
2.
3.

What is the expected output? What do you see instead?
It starting

What version of the products are you using?
OS: Windows 7 Home Premium 64bit
Transmission: 1.91 (build 10268)
Remote: 3.20

Please provide any additional information below. Feel free to
attach screenshots or sample code which demonstrates the issue being
described.

The client crashes on my system as soon as it starts. It doesn't even have 
the time to connect to my Transmission Daemon (or if it does, I never told 
him where it runs :) )

I saved an xml-file and a files that I THINK is a memory-dump. I can attach 
it if you like? (or maybe e-mail them?)

Original issue reported on code.google.com by lenna...@gmail.com on 23 Feb 2010 at 4:23

[GoogleCodeExporter]

By the way.
I also tried two of the 3.13 beta, 3,12 and 3.11.
All give the same issue for me.

Original comment by lenna...@gmail.com on 23 Feb 2010 at 4:25

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I found the issue. The issue is my 64bit OS.

(as was stated by someone else in the forum)
I forced the .net framework to 32bit:

C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe setwow

Now the program works normally. The installer also tries to install itself to 
the 
64bit Program Files directory. (this means that it doesn't say to Windows that 
it's 
actually a 32bit package I think)

Original comment by lenna...@gmail.com on 24 Feb 2010 at 7:27

[GoogleCodeExporter]

Can you make a stace when crash?

Original comment by elso.and...@gmail.com on 24 Feb 2010 at 7:42

[GoogleCodeExporter]

Lennardw I'm using 64-bit win7 and had no problems with launching TR. And i'm 
using
x86 framework along with x64 and no probs even with building my own version 
from sources.

Original comment by ml.ci...@gmail.com on 24 Feb 2010 at 8:38

[GoogleCodeExporter]

I don't understand... I can't reproduce it now.
It starts normally now. Very strange... I had problems with it two days. 
Multiple 
reboots were between them.

Fact does remain that it tried to install itself to C:\Program Files, rather 
then 
C:\Program Files(x86) - But in anyway...
I'll let you know if it returns in a few days. If not. Please close this. 
Thanks for 
the quick reply :-)

(btw - How do I make a stace?)

Original comment by lenna...@gmail.com on 25 Feb 2010 at 7:04

[GoogleCodeExporter]

I added a crash report in r538. Pls test with that version 
(http://elbandi.net/transmission-remote-dotnet/). and attach the report files 
to 
this issue.

Original comment by elso.and...@gmail.com on 27 Feb 2010 at 12:56

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Where does it write it's crashreport files? They are not getting written in the 
Program 
Files directory...
I also tried installing it to a 'world-writeable' location. (in case it has 
something 
to do with permissions for writing there) but also no log files there.
I also tried running it 'as administrator' and that also did not provide any 
log files 
that I could find.

Original comment by lenna...@gmail.com on 1 Mar 2010 at 7:42

[GoogleCodeExporter]

When a unhandled exception is throwed, you can find the crashlog in your 
desktop 
(trdcrash_DATE.log).

Original comment by elso.and...@gmail.com on 1 Mar 2010 at 2:59

[GoogleCodeExporter]

No logfiles are generated by that name anywhere on my computer.
The only way for me to get the program running is by using the LDR64.exe command

(with setwow it works, with set64 it breaks apun startup)

C:\Windows\system32>C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe
Usage:  Ldr64 [query] [set64] [setwow]

        query:  display current status
        set64:  sets COMPLUS_ENABLE_64BIT flag
        setwow: clears COMPLUS_ENABLE_64BIT flag

Original comment by lenna...@gmail.com on 2 Mar 2010 at 12:30

[GoogleCodeExporter]

No idea, I run TRD on a win7 64bit with no error.

Original comment by elso.and...@gmail.com on 3 Mar 2010 at 1:58

[GoogleCodeExporter]

Well, I can run it with no error as long as I give the command above. Does it 
work for 
you if you set the LDR64 thing to set64?

Original comment by lenna...@gmail.com on 3 Mar 2010 at 8:59

[GoogleCodeExporter]

yes:

C:\>C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe query
loading kernel32...done.
retrieved GetComPlusPackageInstallStatus entry point
retrieved SetComPlusPackageInstallStatus entry point
Current status is: 0x00000001

C:\>C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe setwow
loading kernel32...done.
retrieved GetComPlusPackageInstallStatus entry point
retrieved SetComPlusPackageInstallStatus entry point
Setting status to: 0x00000000
SUCCESS

C:\>"d:\transmission-remote-dotnet\TransmissionClientNew\bin\Debug\Transmission 
Remote.exe"

C:\>C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe set64
loading kernel32...done.
retrieved GetComPlusPackageInstallStatus entry point
retrieved SetComPlusPackageInstallStatus entry point
Setting status to: 0x00000001
SUCCESS

C:\>"d:\transmission-remote-dotnet\TransmissionClientNew\bin\Debug\Transmission 
Remote.exe"

C:\>

Original comment by elso.and...@gmail.com on 3 Mar 2010 at 9:49

[GoogleCodeExporter]

mmm.. Very strange then...
But in any case. It appears to be working now, so might as well close the 
ticket I 
suppose? (I just reinstalled my computer, (made a booboo), and it works out of 
the box 
now. It does however still install itself to the 64bit "Program Files" 
directory by 
default)

Thanks for your quick responses!! :-)

Original comment by lenna...@gmail.com on 8 Mar 2010 at 8:00

[GoogleCodeExporter]

Original comment by elso.and...@gmail.com on 8 Mar 2010 at 9:48

• Changed state: Invalid