Does jEmplode run under Windows as well as Linux?

Using java vm 1.4.2-04-b04 on windows server 2003
Using java vm 1.4.2-04-b05 on debian testing

Linux version runs without any errors
Windows version gives me problems

just as an example anytime linux synchs just fine, i go to windows and do a synch there are a number of zero ref which are put into root directory, when i try to delete them all, jemplode will hang after deleting so many of them and i have to keep resynching and deleting until they are all gone.... any clues as to whats going on? Would XP run jemplode better than server 2003?

And you're running the same version of jEmplode on both linux and windows? I pretty much only run on Windows ... Can't think of a reason there would be any difference at that level. Certainly with UI there are differences, but protocol-wise it should be identical.

I am using jEmplode ver 69.

Are you using Windows XP? That HAS to be the difference. When i go from linux to windows server 2003 there is almost ALWAYS some kind of problem. Not to worry though, the linux version has been flawless, I will change to XP to get that kind of performance.

Are you running the jar directly in both cases, or do you have the ZeroG wrapper application, or what?

directly

I am XP, but I can't imagine what the diff would be between the two ...

So can you run this from the commandline -- java -jar jemplode.jar, and when it hangs, switch over to the console and hit ctrl-break (which should spit out a ton of stuff) and send it to me?

I have a copy of Win2003 Server Edition here, so I just now installed it in VMWare (under Linux), then installed whatever the current default Java thing is from the the link on www.jempeg.org, and finally the current jemplode.jar from www.jempeg.org.

Communicates just fine with my v2.01 player. The "rebuild database from memory" (or whatever it's called) option didn't work for me, but no issues with Jemplode retrieving/browsing data.

EDIT: ah.. I'll try a regular sync now..

Cheers

Okay, a regular (long) sync worked just fine from the Win2003SE "box".

Cheers

after creating artist and genre soup playlist on linux i went to windows server and tried to create album soup playlist (tag layer album sorted on album, tag layer album sorted on track#) and jEmplode hung. the attachment is the output.

MSCHRAG,

see attachment file of hung jEmplode under server 2003 under reply to mlord. i was careless and thought yours was the last post.

OK .. So it looks like it's using active mode FTP and your Empeg/Hijack is not able to connect back to your jEmplode to establish the connection (I believe that's how it works anyway).

Mark -- Should I be using passive mode instead? Could his Windows box be denying connections to whatever port is required for active mode?

you know what you're doing!
I did notice that zone alarm asked permission when i ran the command line instead of just double clicking jemplode.jar but i gave zone alarm permission immediately. later tonight, when i have time, i'll run it without zone alarm.
Thanks.

Hijack FTPd does not implement passive FTP, so it must use "regular" FTP. Most likely Win2003SE and/or ZoneAlarm are blocking "regular" FTP because it is known to be insecure.

Cheers

Alternatively, you can uncheck "Use Hijack when Available" in your Options, but that's obviously less than desirable.

What is the file with FID 2?

java.io.FileNotFoundException: There isn't a file with FID 2 on this device.

that's the player database ... you get that usually when a sync failed prior to this connection. it usually means that the database was rebuilt and you're seeing the error message that caused the rebuild, but if nothing appears on the left side, then it means something else went wrong.

Well, I think i finally have the answers. I was getting errors in jEmplode, after awhile, on every synch would be a "checking media". Using hyper terminal, i would see errors like:
VM: do try to free pages failed for player
Memory allocation failed while retrying to read bitmaps, etc.
So....
I read Tony's FAQ (Yeah!).....
After testing continuity on the ide/motherboard connection i discovered a pin whose pad could actually be jiggled a little left and right. I was going to fix this! I went to Walmart got a Lenk 25 watt soldering iron and decided i was going to resolder every pin. As by recommendation, i got a toothpick and made sure each connection had plenty of flux on it. i held a magnifying glass that had a nice little round extra magnifier in one hand and the solder gun (with the smallest tip) in the other, i put a small bead of solder on the tip and put it on the pad for 2-3 seconds leaving behind a very nice bead. if the hand got shaky, i took a break. i ended up doing all pins except 3 right above a computer chip. these 3 solders luckily looked like some of the best before i went in and fixed the others right. i was very confident about what i had done and although slightly nervous, when the empeg was put back together, it booted and worked fine. I then did a couple of ~ 10 gig uploads with jEmplode on win2000se with no problems. right now, i'm about 1/3 through a 50 gig upload with no problems. Anyway, my point is jEmplode works fine, it was the user and hardware with the problem.

Two hints for jEmplode i think do work are:
1)if alot of zero refcounts which are put in root come up try to delete them all and synch. if jemplode comes back and says unable to synch "such and such artist/album" .... wait about 30 seconds or until your harddrive makes a noise and resynch - should continue deleting then.
2)adding lots of gigs at one time? delete soup playlists first.