Closed GoogleCodeExporter closed 9 years ago
Odd. I'm running it on Win8 here, so I know at least one configuration works!
Is there a winauth.log created, it'll be in the same folder as the winauth.exe
program itself.
If you cancel the password (so don't try and import your old authenticator)
does it work? And how about if you try and add a new authenticator...a Google
one for example, just type anything into the key field?
If you can't get past there, and there is no log file, let me know and I'll
upload a debug version that might provide more information.
Original comment by winauth
on 10 Oct 2013 at 11:29
Hi. Thanks for your prompt response, but I just added a reply to my issue:
I just had to put WinAuth.exe into the same directory/folder as my
winauth.xml file.
Thanks.
Lester
[image: HomePage] <http://www.ingber.com/> [image:
HomePageMirror]<http://alumni.caltech.edu/~ingber>
[image: LinkedIn] <http://www.linkedin.com/in/ingber> [image:
GooglePlus]<https://plus.google.com/110089061886068132985/about>
[image: FaceBook] <http://www.facebook.com/lester.ingber> [image:
Twitter]<http://twitter.com/ingber>
Prof. Lester Ingber lester@ingber.com ingber@alumni.caltech.edu
Original comment by les...@ingber.com
on 10 Oct 2013 at 11:32
You shouldn't have to do that, as it creates a folder in your Windows roamind
profile. Something like "c:\users\<username>\AppData\Roaming\WinAuth". Is that
there?
I'd like to get to the bottom of it, if you could please help. Is the folder
there and where did you put the exe file originally?
Original comment by winauth
on 11 Oct 2013 at 2:03
Hi. Yes, I had 3.0.17 set up
in c:\users\<username>\AppData\Roaming\WinAuth\, with a shortcut on my
desktop to the exe in that folder.
When I got 3.0.19, I put the executable on the desktop to do the "install"
(actually forgetting that it was portable). That's when I go the popup
error. When i replaced the 3.0.17 exe in the WinAuth\ folder with the
3.0.19 exe, it works fine (using the same shortcut on my desktop).
I assume you're concerned about the behavior I saw, and that there should
have been some better warning or explanation in the popup?
Lester
[image: HomePage] <http://www.ingber.com/> [image:
HomePageMirror]<http://alumni.caltech.edu/~ingber>
[image: LinkedIn] <http://www.linkedin.com/in/ingber> [image:
GooglePlus]<https://plus.google.com/110089061886068132985/about>
[image: FaceBook] <http://www.facebook.com/lester.ingber> [image:
Twitter]<http://twitter.com/ingber>
Prof. Lester Ingber lester@ingber.com ingber@alumni.caltech.edu
Original comment by les...@ingber.com
on 11 Oct 2013 at 3:18
Yes, I am interested to know why you got the error, in case there is a problem.
I have uploaded a debug version to
https://winauth.com/downloads/3.x/WinAuth-3.0.19-DEBUG.zip, which will show
more information on a crash.
Can you please try it, putting it on the desktop like you did before and see if
it works? If it fails, can you post any errors and also include any text from
the file winauth.log, which will be either in the same directory as the exe or
in the AppData\WinAath folder.
Thanks.
Original comment by winauth
on 11 Oct 2013 at 2:07
I attach two screenshots and the log which was in the
AppData\Roaming\WinAuth folder.
Lester
[image: HomePage] <http://www.ingber.com/> [image:
HomePageMirror]<http://alumni.caltech.edu/~ingber>
[image: LinkedIn] <http://www.linkedin.com/in/ingber> [image:
GooglePlus]<https://plus.google.com/110089061886068132985/about>
[image: FaceBook] <http://www.facebook.com/lester.ingber> [image:
Twitter]<http://twitter.com/ingber>
Prof. Lester Ingber lester@ingber.com ingber@alumni.caltech.edu
Original comment by les...@ingber.com
on 11 Oct 2013 at 2:15
Doesn't look like the attachments made it. Could you email it me directly at
winauth@gmail.com
Original comment by winauth
on 11 Oct 2013 at 2:20
Original comment by winauth
on 18 Jun 2014 at 7:33
Original issue reported on code.google.com by
les...@ingber.com
on 10 Oct 2013 at 11:20Attachments: