Graion Dilach
12.11.2010, 11:35:20
(This post was last modified: 12.11.2010, 11:37:00 by Graion Dilach.)
That could be fixed, but this didn't fixed my problems.
I reinstalled LaunchBase and started everything again. After I checked Advanced Mode, I did a Syringe-Ares update and I got constantly Ares update failure. I tried putting 0.1 P1 into the Resources folder manually, but I got verification failures. Then somehow I ended up with revision 666 binary.
The LaunchBase update screen shows that the stable is version 710 (Ares 0.1 P1, isn't it?), although I think the checksums the validation uses are still the 666 versions' one. I think this, because ares.mix passes the verifying, and in the SVN, it's revision is 544, while both the dll and inj has revision number 710.
I reinstalled LaunchBase and started everything again. After I checked Advanced Mode, I did a Syringe-Ares update and I got constantly Ares update failure. I tried putting 0.1 P1 into the Resources folder manually, but I got verification failures. Then somehow I ended up with revision 666 binary.
The LaunchBase update screen shows that the stable is version 710 (Ares 0.1 P1, isn't it?), although I think the checksums the validation uses are still the 666 versions' one. I think this, because ares.mix passes the verifying, and in the SVN, it's revision is 544, while both the dll and inj has revision number 710.