Ever since the newest Java update...

[Lemon Pie]

Ever since I updated Java to the newest iteration (which, I'm pretty sure, fixed the massive security issues) I've been getting this error when I attempt to start ENIGMA;

Code: [Select]

Checking configuration
Scouring for Java
java version "1.7.0_11"
Java(TM) SE Runtime Environment (build 1.7.0_11-b21)
Java HotSpot(TM) Client VM (build 23.6-b04, mixed mode, sharing)
Calling `java -jar l*.jar`

Error: Unable to access jarfile l*.jar
Press any key to continue . . .
LateralGM starts up fine when if I execute the JAR directly. I've tried moving ENIGMA to the root & redownloading & such, but it still pops up with this error.

System Specs;
http://pastebin.com/2Prz7csa

[Josh @ Dreamland]

It's a Java issue. I've been hearing about it a lot, recently, and I wish people would start directing these posts to Oracle so they'd fix it. Basically, someone decided that wildcards in Java filenames was a bad idea, and so they randomly and unceremoniously dropped support for it.

I'm sure if I said that to the wrong person, I'd get a lecture about how this has been the plan since dinosaurs roamed the earth, because * is terrible practice and isn't anything like how the filesystem actually works, and causes security holes from ninjas who pretend to be the file you're trying to execute... but in the meantime, I'm going to be pissed that they broke it.

Also in the meantime, I'll see about rebuilding ENIGMA.exe for Windows to run it with the full filename.

[IsmAvatar]

On the other hand, I've always preferred LGM be called directly by name rather than by wildcard, but alas, butting heads with the writer of ENIGMA.exe, I won't win unless I write it myself.

Anyway, thanks for letting us know. We should have it fixed sometime soon. In the meantime, running LGM directly is a valid solution, provided you have already run ENIGMA.exe successfully once in the past.

[Lemon Pie]

On the other hand, I've always preferred LGM be called directly by name rather than by wildcard, but alas, butting heads with the writer of ENIGMA.exe, I won't win unless I write it myself.

Anyway, thanks for letting us know. We should have it fixed sometime soon. In the meantime, running LGM directly is a valid solution, provided you have already run ENIGMA.exe successfully once in the past.

Glad I could help.

[Josh @ Dreamland]

I've committed a fix to ENIGMA.exe. I am getting sick of this patch-maintenance bullshit; this is something this server ought to be doing for us. Or, if we must, EnigmaBot's server. Point is, compiling ENIGMA.exe is trivial, albeit not something Linux ought to do. Downloading a zip file from GitGub and packing in some files? That's trivial and something the server ought to be doing.

Anyone want to volunteer to write a PHP script to (optionally) compile ENIGMA.exe, download the repository from GitHub, and pack in the Additional files?

Would be great if it could generate deb/rpm packages, too.

[daz]

If your server has curl + the php module, I'd be up for writing a script for the Windows bits. A couple of things though

• This would be difficult to test without having server access. Not having linux or a cross compiling chain setup for that matter, there's only so much I could do. You could probably edit the script though
• I don't know how to call the cross compiler. If you give me the full command to do that, great.
• This bitch is gonna time out. You'd have to call the script from the CLI I'd guess, or pick a new language, hell you could set php's timeout to 8 years if you really wanted.

[Josh @ Dreamland]

It takes about .25 seconds to compile ENIGMA.exe. The download should not take that long (ENIGMA is less than 2MB), but in the event that it does, I suppose we can schedule it as a cron job and just offer the zips as they become available.

[Lemon Pie]

Point is, compiling ENIGMA.exe is trivial, albeit not something Linux ought to do. Downloading a zip file from GitGub and packing in some files? That's trivial and something the server ought to be doing.

Excuse my newbiness but how exactly does one compile ENIGMA for Windows? I've been trying with Code::Blocks for the past few days to no avail...
The search bar held no helpfulness on the matter... Of course I could just be an idiot.

[Josh @ Dreamland]

The compiler project is in CompilerSource. You're best letting LGM compile it, though.
ENIGMA.exe is in CompilerSource/stupidity-buffer. This is the shiny thing that runs LGM (but since broke).
The engine project is in ENIGMAsystem/SHELL. Compiling this with C::B will do you no good.

[TheExDeus]

I was able to do that. I ran C::B, at top chose Release and Compile (also set toolchain in options) and it worked. I don't remember what exactly I compiled, but I did compile something. But I haven't done this in about a year now.