SPICA icon indicating copy to clipboard operation
SPICA copied to clipboard

My SPICA Won't Load when it is clicked on.

Open mm132 opened this issue 6 years ago • 14 comments

Whenever I try to run SPICA it doesn't work, it won't load up or show up on screen. It used to be able to start up on its own but now it doesn't seem to be able to do it, can someone help with this? I really need help and fast. image

mm132 avatar Oct 15 '18 02:10 mm132

Please don't create multiple issues on the same topic just because nobody answered. Everbody has his private life and doesn't have the time to solve every issue all the time. Please close the other issues to keep the issue tracker clean.

About your problem: I can not reproduce it and it is most likly to be an error on your site because the last time the code was changed was on febuary 28th. Did you change systems recently? Is .NET Framework 4.6.2 installed? (Is included if you install v4.7) I think the .NET Framework also needs DirectX. Is that installed?

This build runs on my Win7 machine just fine: https://drive.google.com/open?id=1PxSuomMgFFSs2FQQGkcxTzSjcsrZdFBM

You also could try clearing the folder "%APPDATA%/../Local/SPICA". If you have problems finding this folder just hit Win+R and paste it there.

waielal avatar Oct 25 '18 04:10 waielal

I have a Windows 10 and I have Direct X Installed, but I cannot find a Spica folder in appdata/local.

mm132 avatar Oct 25 '18 20:10 mm132

I also tried my build on an Windows 10 machine and it worked there fine too.

The Spica folder is only created, if Spica has run once successfully.

What about .Net Framework? https://www.microsoft.com/de-de/download/details.aspx?id=55170 And does the build I provided change anything in the behavior?

waielal avatar Oct 25 '18 21:10 waielal

Yes,   I have .NET framework that already came with the computer as well as DirectX,   and yes the program did run successfully once.  Your build unfortunately did not do anything.

On Friday, 26 October 2018 10:14 AM, Waiel Al <[email protected]> wrote:

I also tried my build on an Windows 10 machine and it worked there fine too.The Spica folder is only created, if Spica has run once successfully.What about .Net Framework? https://www.microsoft.com/de-de/download/details.aspx?id=55170 And does the build I provided change anything in the behavior?— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

mm132 avatar Oct 26 '18 01:10 mm132

Okay, I created another build that logs every error inside a Log-file. SPICA_log_build_20181027.zip

Please try this out and provide me the log. It should be created in the same directory as the application with a name similar to Log_636762316458000555.txt

waielal avatar Oct 27 '18 08:10 waielal

Tried that,   nothing happened. On Saturday, 27 October 2018, 9:08:23 PM NZDT, Waiel Al [email protected] wrote:

Okay, I created another build that logs every error inside a Log-file. https://drive.google.com/open?id=18RQ8pa918EIVQbnP61QcBSHfMIXZuDN6

Please try this out and provide me the log. It should be created in the same directory as the application with a name similar to Log_636762316458000555.txt

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

28/10/2018 9:33:02 AM.668: Starting SPICA 28/10/2018 9:33:02 AM.752: Exception hooks set up 28/10/2018 9:33:02 AM.768: --------------------------

mm132 avatar Oct 27 '18 20:10 mm132

That's weird. The first line of code is "Create the log-file" before anything SPICA related is created. If even this not executed then there has to be something fundamentally wrong on you system.

What happens if you run the application as an administrator? (right click > run as administrator)

waielal avatar Oct 27 '18 20:10 waielal

With the statement "fundamentally wrong" I assume that .NET Framework is installed correctly and runs correctly.

waielal avatar Oct 27 '18 20:10 waielal

With the statement "fundamentally wrong" I assume that .NET Framework is installed correctly and runs correctly.

It has worked before and framework has already been pre-installed, and I did run as administrator but nothing happened. Is it some other kind of problem?

mm132 avatar Nov 03 '18 00:11 mm132

I'm sorry, I have no idea what the problem could be. It is really weird that the program doesn't even run one line of the program... There has to be something blocking the execution. Do you have an anti virus program? Maybe it false positive marked SPICA as a virus? Otherwise I am out of ideas...

When was the last time SPICA ran normally?

waielal avatar Nov 03 '18 03:11 waielal

If I recall correctly the last time it ran was in September,  it worked all-throughout September and prior to that (around September 1-21st and beyond).   I don't seem to recall the anti-virus thing being a problem. On Saturday, 3 November 2018, 4:19:23 PM NZDT, Waiel Al [email protected] wrote:

I'm sorry, I have no idea what the problem could be. It is really weird that the program doesn't even run one line of the program... There has to be something blocking the execution. Do you have an anti virus program? Maybe it false positive marked SPICA as a virus? Otherwise I am out of ideas... When was the last time it ran?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

mm132 avatar Nov 03 '18 04:11 mm132

If I recall correctly the last time it ran was in September

That is not that far ago. Pretty weird...

Hmm okay.. coming back to the second build I linked, just to be on the same page. You did these steps and the log file still was not created?

image

Otherwise I'm sorry to tell you that I don't have any idea what the problem could be.

waielal avatar Nov 03 '18 06:11 waielal

Just to make sure, don't forget to unblock the ZIP before extracting, this has caused issues in the past capture

legoj15 avatar Nov 03 '18 08:11 legoj15

If I recall correctly the last time it ran was in September

That is not that far ago. Pretty weird...

Hmm okay.. coming back to the second build I linked, just to be on the same page. You did these steps and the log file still was not created?

image

Otherwise I'm sorry to tell you that I don't have any idea what the problem could be.

I did it just now...and it has been fixed. I am able to use it again.

mm132 avatar Nov 03 '18 08:11 mm132