jEmplode observation (may be a known fact)

Pulled a never used RioCar off the shelf (v1.x firmware). Wired it up on ethernet and serial.

jemplode 45 (launched from full install executable .exe with integrated java environment) could see it on both serial and ethernet. However, I let it try to do the initial handshake for more than an hour and a half before telling it to give up.

jemplode 45 (launched directly from jar file with most recent Sun JVM) couldn't see it on serial at all.

jemplode 54 (launched from jar file with most recent Sun JVM) couldn't see it on serial at all.

I used emplode to upgrade the unit to v3a7 final (developer image). Then I used upgrader.exe that came with the Logo Editor app to install the hijack kernel (whatever today's release version is!).

Now both jemplodes can see it and interact with it on serial...doing an upload now (and all night) with v54 under sun's jvm.

Not sure what the integrated vs. sun jvm issue was, but it also appears that Jemplode also had an issue with v1 empeg firmware. Known issue?

-brendan

The deal with serial is probably that the lax file loads an extra class to get serial to work, but that's just a guess.

Serial requires more than just jemplode.jar to work properly. In fact it requires native code to do its thing (which gets installed as part of the jEmplode installer on Windows). If you take your 45 install and replace the jar file with 54's, I think it should work (though you just won't have the most recently VM ... though you could actually try replacing the JRE in the installer folder with a newer one -- no promises that will work, but it might).

Actually, you say "both jemplodes can see it" -- do you mean the .jar launched one can too? That would really surprise me if that's true.

And yes, it's a known isue that jEmplode does not support 1.0 firmwares. A known and will-never-be-fixed issue.

ms

From the front jEmplode page:

> Your player has to have a 2.0 kernel on it to use jEmplode!

Well then, that's it.

-brendan

> Actually, you say "both jemplodes can see it" -- do you
> mean the .jar launched one can too? That would really
> surprise me if that's true.

Hmm. I'll experiment a bit later. My recollection is that I couldn't just replace the 45 jar with the 54 jar and actually get the .exe to launch it: it threw out some errors and refused to load. So the lib directory has jemplode.jar (45) and jemplode.new.jar (54) in it, and I've been launching each one by double clicking. Before I say I'm sure they both see the empeg on serial, I'll double check.

-brendan

Ohh right .. I think the main class got moved ... Edit jemplode.lax and search for "lax.main.class" and change it to:

lax.main.class=org.jempeg.empeg.manager.Main

ms

Oh man -- That's for your own good .. There's some impure and evil about an Empeg without a 2.x kernel on it.

Then I used upgrader.exe that came with the Logo Editor app to install the hijack kernel (whatever today's release version is!).

Just so everyone knows... If you associate ".zimage" files with logoedit.exe, you can double-click on a zimage to have it install to the empeg. No trips to the menus or working on the command line.

> Ohh right .. I think the main class got moved ...
> Edit jemplode.lax and search for "lax.main.class"
> and change it to:
>
> lax.main.class=org.jempeg.empeg.manager.Main

Hmm...still throwing an error...

-brendan

what error + details?

---
Unable to locate the application's 'man' class. The class 'org.jempeg.empeg.manager.Main' must be public and have a 'public state void main(String[])' method. (LAX).
---

I click on Details and get:

java.lang.ClassNotFoundException: org/jemepg/empeg/manager/Main
at java.lanc.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at com.zerog.lax.LAX.launch(Unknown Source)
at com.zerog.lax.LAX.main(Unknown Source)

I installed the full environment, and then made these chages:
1. renamed jemplode.jar to jemplode.jar.old in lib subdir (that's the 45 version)
2. move the jemplode.jar (54 version) into lib subdir (it's 1,963,869 bytes)
3. Commented out the old LAX.MAIN.CLASS setting in jEmplode.lax.
4. Added the following LAX.MAIN.CLASS setting in jEmplode.lax:
lax.main.class=org.jempeg.empeg.manager.Main

-brendan

Perhaps there's something wrong with the steps I followed above?

-brendan

"java.lang.ClassNotFoundException: org/jemepg/empeg/manager/Main "
did you type this line or copy-and-paste it, because it says "jemepg" instead of "jempeg" in it .... But it doesn't match the other line, which IS spelled right. This looks like it should work. Must be something funky with InstallAnywhere. I'm going to put up new installers for 54 sometime soon, so you can try those when I do.

I typed the error messages by hand from the dialog boes, didn't realize I could copy/paste them. That's probably how that issue showed up in my post.

I'll go back and check to make sure I have everything, character-by-character, correct.

-brendan