Last night I used jemplode (v36) in depth for the first time. Lovely. Absolutely lovely. Soooo fast....

-Zeke

I used it for the first time today...

Also major huge joy...many thanks for your efforts guys!

That's funny, we have the exact opposite opinion happening over in General.

YIKES! I've only just scratched the surface of it so far. Maybe it's time to reconsider using it, I don't wish to have THOSE kind of problems...thanks for the heads up Tony

No, I wasn't suggesting that you don't use it. I think it's great and I think you should continue using it.

I don't think that what he was saying over in that other thread is really Jemplode's fault. I think he might have either been running an old version (didn't hand-copy a new JAR into place after installing), or perhaps he's having disk trouble and Jemplode was only a coincidence.

I'll give it an honest go and see what happens. I always keep all of my software right up to date so I should be ok. Awfully nice looking GUI too...

I had some funky things going on last night, and jemplode got me through them with no problems.

In a nutshell, my serial port wouldn't respond, but the ethernet interface did. The culprit was that I had forced DC mode and forgotten about it. I saw many strange things, like the kernel updater in Logoedit semi-responding to the serial port with the error messages "Error status in readbyte 16" and "Error couldn't find product ID!"

I reflashed the 2.0 b11 with jemplode then reloaded hijack 273 (about 5 minutes before 274 rolled out). It was only when I saw my AC logo that I gave myself the big dope slap upside the head. Anyhow, jemplode managed to power through all my idiotry. The databases were rebuilt at least once and I think I had a fsck somewhere in there too.

I've found that jemplode has been more stable than emplode, although this probably has to do with my forgetting about forced DC mode.

Oh yeah, it's blazing fast too. :-)

I'm converted.

-Zeke