Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

crash at start #106

Closed
phate89 opened this issue Feb 1, 2017 · 15 comments
Closed

crash at start #106

phate89 opened this issue Feb 1, 2017 · 15 comments

Comments

@phate89
Copy link

phate89 commented Feb 1, 2017

Hi.. I have a weird error with this screensaver.
I followed the readme to install it and it gets added to the list but it doesn't start. the screen flash to the black and returns normal and I can't open screensaver settings. So I checked in appdata\Local and I saw there was no Aerial folder but there was a folder CrashDumps with several Aerial.scr.***.dmp.
So I downloaded the source code to test it in vs 2015 and debug it but I got a weird error. At start (before it loads every code) directly in _corexemain I get a System.ArgumentException in mscorlib.dll with message (translated by me from italian): The path can't be an empty string or composed by only spaces.
Do you have any idea what might trigger this error?

@alistairmcmillan
Copy link
Collaborator

@phate89 Could you try v5.1 for me? Does that have the same error?

@phate89
Copy link
Author

phate89 commented Feb 1, 2017

v5.1 works but I can't compile it, I get a different error System.BadImageFormatException (not a valid 32 bit application).. Might be something wrong in my env.

@alistairmcmillan
Copy link
Collaborator

:( Might be my fault then.

Could you attach one of the dmp files here please?

@phate89
Copy link
Author

phate89 commented Feb 1, 2017

sure here it is
Aerial.scr.13456.zip

@alistairmcmillan
Copy link
Collaborator

@phate89 Could you attach a screenshot of the Aerial Settings dialog from the latest version please?

@phate89
Copy link
Author

phate89 commented Feb 1, 2017

with the latest version I can't open settings at all

@alistairmcmillan
Copy link
Collaborator

@phate89 Are you familiar with Regedit? Could you show us the values you have under HKEY_CURRENT_USER\Software\AerialScreenSaver on your PC?

@phate89
Copy link
Author

phate89 commented Feb 1, 2017

I don't have that at all..

@alistairmcmillan
Copy link
Collaborator

@phate89 I'm confused then. If you've run any version of the screensaver that key should exist.

How about something like HKEY_USERS\S-1-5-21-1229272821-231175127-839231175-135808\Software\AerialScreenSaver? The long GUID number will be different but if you open regedit there should only be one or two so it shouldn't be difficult to locate yours.

@phate89
Copy link
Author

phate89 commented Feb 1, 2017

I searched in the regedit and I didn't find anywhere the reg key.. Yes v5.1 works but no reg key

@alistairmcmillan
Copy link
Collaborator

@phate89 I'm not having much success trying to recreate the problem you're having.

Do you have .Net Framework 4.6 installed? https://www.microsoft.com/en-us/download/details.aspx?id=48130

@alistairmcmillan
Copy link
Collaborator

alistairmcmillan commented Feb 1, 2017

@phate89 Are you running a old preview version of Windows 10 from July last year?

@phate89
Copy link
Author

phate89 commented Feb 1, 2017

I use windows 10 stable with the latest udpate so net framework 4.6 is included and I have it installed..

@phate89
Copy link
Author

phate89 commented Feb 1, 2017

This is really weird.. I wasn't able to compile (both 5.1 and 6.0) or make work the 6.0 version but now everything works (20 minutes ago I checked again and 6.0 still wasn't working).. No Idea what changed.. I tried to use dependency walker to see if there was some problem in the dll linked and compile 5.1 with x86 processor destination but I don't think that might fixed something since now it compiles also with "any cpu".. Now I also have regedit keys.. weird.. Thanks for your help anyway. Great screensaver :)

@cDima
Copy link
Owner

cDima commented Feb 5, 2017

@phate89 a new version 6.1 is out with a small fix;
I compile the version for all as "Any CPU" and "All" configuration. For debugging, this is switched to "x86" and "Debug". If you have the same debugging issues, lets write up a readme about dev setup as to help others. Glad it magically started working for you. :)

@cDima cDima closed this as completed Feb 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants