Closed GoogleCodeExporter closed 8 years ago
Hi,
I am really baffled by this one.
Can you send through some details:
Windows 7 64 or 32bit
Are you running as administrator?
Does this happen with 0.0.3?
Do you have the latest version of .net 4 installed on your machine?
Can you send me the debugfinfo.log from v0.0.3?
Sorry for all the questions!
Thanks for the help, we will get this sorted ASAP!
Original comment by original...@gmail.com
on 20 Feb 2013 at 7:40
0.0.2 sorry for not including that. I just installed win 7 this week but it
says everything is up to date and that i have net .4 installed. I will run
0.0.3 now and should i relink it here or open a new one if there's a problem?
I know you're busy so unless you say so I'll just relink here.
Original comment by ebentonm...@gmail.com
on 20 Feb 2013 at 8:37
new debug, 0.0.3
Original comment by ebentonm...@gmail.com
on 20 Feb 2013 at 8:38
Attachments:
sorry and 32 bit win 7
Original comment by ebentonm...@gmail.com
on 20 Feb 2013 at 8:39
Update, here is my debug after I "repaired net .4" same exception window.
Original comment by ebentonm...@gmail.com
on 20 Feb 2013 at 8:45
Attachments:
We are looking into this, but might only be able to get back to you tomorrow.
We will update as soon as we can!
To confirm, do you get this error as you try run the application? As in, you
can't even get to the login screen?
Original comment by stickymaddness
on 20 Feb 2013 at 9:14
correct, I've seen the opening window once for a split second and the never
again. Since the second attempt, I only get this window.
Original comment by ebentonm...@gmail.com
on 20 Feb 2013 at 11:10
We're still trying to track down the cause of this.
Do you have .NET 4 Client Profile or full .NET 4 installed?
Original comment by stickymaddness
on 21 Feb 2013 at 5:24
Bingo. I googled "full" .net 4 and installed, and title screen loaded! thanks,
guys.
Original comment by ebentonm...@gmail.com
on 21 Feb 2013 at 5:47
[deleted comment]
Excellent, glad it's sorted!
Original comment by stickymaddness
on 21 Feb 2013 at 5:57
Original issue reported on code.google.com by
ebentonm...@gmail.com
on 20 Feb 2013 at 7:02Attachments: