Is it me, or will Tux v2.0 not run on Windows 7 ???

[When-Life-Gives-You-Limes]

I've tried both the installer and the .zip package on 2 different Win 7 x64 computers. It installs fine, but when I try to run the program all that happens is that javaw.exe starts briefly and then closes. I saw this in Task Manager - nothing happens visually.

Does anyone have any thoughts? I installed & ran v2.0 on a Win 10 PC and really liked the ability to customize the toolbar and the "Show Measure Errors" tool and would really like to use v2.0 on my Win 7 PC.

Years ago when I was using Win XP I used a program called Dependency Walker whenever I couldn't get a program to run, and I'd end up finding out that my system was missing a needed .dll or .ocx file. I dusted it off and tried finding a solution to my current problem with Tux, but haven't gotten anywhere. In fact, when I ran it on tuxguitar.exe it showed the exact same info for both the v2.0 and v1.6 executables, and yet I can run v1.6 but v2.0 is a no go.

Would appreciate any thoughts or insight. Thanks.

[guiv42]

I don't know much about Windows, and even less about Win 7, but a priori I don't see anything in TuxGuitar code itself that may have such consequences. Possibly this could come from an updated dependency (java, or swt?)

Just by curiosity, could you have a try with a JFX version? These are not officially released with stable versions, but you can find them in the latest pre-release.

And another question: do you get any error msg when launching from a cmd window?

[When-Life-Gives-You-Limes]

When I click on the .bat file all that happens is a command window appears and disappears instantly..... but the same thing happened when I clicked on the .bat file in the v1.6 folder. Neither .bat file will start the program on its own.

[guiv42]

Do you get an error msg when starting the .bat from a cmd window?

• launch "cmd" from windows start menu (or type Windows+R then "cmd" then Enter)
• type cd path_to_your_tuxguitar_folder
• type tuxguitar.bat

[When-Life-Gives-You-Limes]

Sorry, I wasn't thinking straight and double-clicked the .bat files instead of using a command window.

When I used the command window to run the stock .bat file in my working v1.6 install folder, I got the following error message:

"Error: Could not find or load main class app.tuxguitar.app.TGMainSingleton
Caused by: java.lang.ClassNotFoundException: app.tuxguitar.app.TGMainSingleton"

When I ran the stock .bat file in the v2.0 install folder, I got the following error message:

"OpenJDK 64-Bit Server VM warning: Attempt to query job object information failed: The parameter is incorrect
Incompatible OS: Minimum Windows build version is 14393 but current is 7601"

When I ran the edited .bat file in the v2.0 install folder, nothing happened. The command window just brought up a new line and awaited the next command.

I get the feeling this isn't going to work.

[guiv42]

Two different problems

1. For 1.6.6: I don't understand the error message, it seems inconsistent with the delivered version (that ignores the existences of a module "app.tuxguitar.app"). Did you mix the .bat files from 1.6.6 and 2.0.0?
   But let's say this question is not important, and try to focus on 2.0.0

2. For 2.0.0: the error msg is consistent with the windows version check implemented by swt. Have you modified the .bat file of 2.0.0 as I proposed just above? (add -Dswt.disableWindowsVersionCheck in one line)?

[When-Life-Gives-You-Limes]

Sure....

TuxBatchFiles.zip

[When-Life-Gives-You-Limes]

1. No, I didn't mix them. I didn't understand the message either since I can run the program without issue with the .exe

2. Yes. I said I ran the edited (modified) .bat file in the v2.0 folder, and nothing happened. The command window just brought a new line on the screen and awaited the next input from me. I think I modified it properly. Those are "weird" batch files to my eyes. I'm used to seeing one line per command. Even with word wrap on it's just a sea of commands.

[When-Life-Gives-You-Limes]

Thank you. I'll give it a try shortly.

[guiv42]

My 2 cents: it's not worth the effort (sorry @When-Life-Gives-You-Limes). Whatever we may do to tweak this version, next dependency update will break it all again. I don't think we can do anything for an OS not even maintained by its developer.

[When-Life-Gives-You-Limes]

@guiv42 - I can't say. Since I'm not a programmer I'm saying this out of complete ignorance, but I'm assuming that helge17 saw this thread and released the legacy version above. Did that take a lot of effort or was it a quick fix? I have no idea.

@helge17 - thank you so much! The legacy version seems to work perfectly. I REALLY appreciate you making the effort. If you don't mind making updated legacy versions available as pre-releases in the future, I would appreciate that as well. Thank you again.

[helge17]

It's not that much work to make a single build, but as guiv42 already said, we can't support old OS versions because there already exist too many variants of TuxGuitar.

When the next version of TuxGuitar is released, I'll try to remember to also create an SWT 4.26 version for Windows, as long as it builds in my environment. If I forget, you can remind me here ;-)

[When-Life-Gives-You-Limes]

Thank you again.