X2 crashes, Installation, Checks, and Suggestions
Hi all,
I aplogize in advance for the rants, but this issue has made me incredibly irate, especially when I found my solution last night. As I read posts, I have seen others with comments like "X2 has crashed on me more in one weekend than X1 did in 9 months!" I feel the pain of that! In fact, I have not been able to complete anything with X2 yet.
First... and the real problem... is that suddenly last night I went searching for hash checks ("thumbprints") of the installation files. I could not find any, so I downloaded them again. Low and behold, the hash check of "02_SONAR_X2_Producer.part1.exe" was different (although they were physically the same byte size)... so I had to download it a third time. The original file I downloaded was corrupted! Yet through the misery of installs, crashes during installs, and X2 having seizures (sometimes so unresponsive the bug report feature was locked as well)... X2 installed (with a corrupted file)!! (at times). Here are the hash values for the files I used to install that went "clean":
72B9F3321DA0D3C5243C888B77DB5C62 *02_SONAR_X2_Producer.part1.exe
F9A4C437FB26E7AFDDBDFF9E02E2204A *02_SONAR_X2_Producer.part2.exe
8D627745DC542CD2573C9ADDF2CD2C69 *02_SONAR_X2_Producer.part3.exe
A67975E72A2DDF8E68B3912CC2DBF415 *02_SONAR_X2_Producer.part4.exe
Second... in my search to find why certain plug-ins caused these crashes, I re-installed ONLY those plug-ins... yet needed to unpack ~9Gb of setup files to do this. Since the setup files themselves crash (and Norton has them flagged for causing crashes), a more elegant solution is needed. Taking an hour to reload a single component is not acceptable (bear in mind that the X2 "bug reporter" flagged the plug-ins and not the main program when it sent bug reports... which is why I went down this path in the first place).
Third ... as most of us are not connected to a corporate T1 or higher connection, I keep my downloads "just in case" and assume they are still valid. This alone caused me so much grief until I checked the hash checks last night. Three MONTHS of pain.
Suggested solutions:
1. The install files themselves should verify they are accurate before doing ANYTHING.
2. Rather than unpack everything, the setup should verify files, and go to the setup screen to prompt the user for what they want. After that it can unpack accordingly (so for folks needing to re-install only 1Mb, only that .bin will need to be processed).
3. For people like me who keep setup files just in case. The setup files could even unpack and stay in that form if the user chose. That way a re-install can be done more elegantly (optional, if #2 is done correctly).
End of rant, my apologies. Even when X2 catches itself seizing, those bugs have gone into a black hole. After seeing posts and reviews of these files I wanted to at least throw out my experience and things which would help an average end-user.
post edited by mettelus - 2014/03/22 00:08:35