Alright, I have a (virtual) machine on my computer which I have been using to try to find a fix for this, and I have a pair of things which will fix the two separate problems: one from my side and one from yours.
- My fix: taking care of the program not loading at all.
A beta release for 1.1.0 will be available in the next few days. Everything in the program that worked in 1.0.0 has not changed in 1.1.0, so upgrading shouldn't affect how current 1.0 features work. This version will, among other things, be using a different "jar wrapper" program which works fine in 64-bit Windows. And, as said earlier, it brings the program size down quite a bit, down to 200kb.
- Your fix: The database-connection issue for v4.
The fix for this is to have _only_ 32-bit Java installed on your machine. This can be done in no greater than two steps:
1: Go to your Control Panel -> Add/Remove Programs (Control Panel -> Programs in Win7) and see if there an entry along the lines of "Java (64-bit)". (the 64-bit is the important part) Uninstall this.
2: If there is not an entry still there for "Java" that doesn't say 64-bit, go here and download 32-bit Java. (Select "Windows" and NOT "Windows 64-bit" from the Platform drop-down)
Now, there looks to be a more permanent fix for this latter issue. However, it would require some two things for me to do:
- Pack RTools into an installer system, as I would need to run a command-line command that would make the WER database accessible by a Java program.
- Learn how to use a particular program's command-line interface.
Realistically, this looks like it'll be roadmapped for v.1.3ish, mostly because the issue isn't really a 100% dealbreaker now that I have a pretty solid understanding of what is really going on.
No comments:
Post a Comment