Any reason why I can connect via ftp & http on my Rio-car Mk2a w/no problems but my Empeg-car Mk2 refuses? I can connect to it thru Emplode using Ethernet just fine I just can't ftp or http to it.
Running 2.0-b11 on both w/same Hijack versions (199).
I feel so lucky to get the ethernet to work first time out but surprised one player will connect while the other won't.
On another note would I be better off using a hub instead of switching the cable back & forth and could this be my problem of connecting with the other player?

Are the two players set to the exact same ethernet settings?

If your talking addresses NO. I wait for the IP address to appear& type it in the browser or ftp program.
I should say I only have one player connected at a time so there should be no confusion as to which is which.

Can you connect to the "bad" one via ethernet with Emplode?

Can you connect to the "bad" one via ethernet with Emplode?

Yes

Okay, on to the next diagnostic step: Is there anything in the config.ini of the "bad" player that might make Hijack choke?

This something I was just looking at, it is full of thousands of fav visuals duplicates. I'm deleting all of them now.

Ut oh, now my config.ini doesn't showup, nothing in the dialog box, but it does connect slowly to Emplode, hangs up at the retrieving player configuration but eventually connects.

Okay, read this FAQ entry and get back to us.

I don't know why or how it happened but I looked at the display and it was dim checked settings and it was in car mode ala Hijack, I don't think it was that way before but I can't be sure. I switched it back to normal setting to run on AC mode and now I can ftp/http the player. The config.ini is still blank in Emplode but the player still seems to work as well as http. Weird.
Well thanks for the talk thru Tony.

You still need to get your config.ini fixed up, per that FAQ entry, or else you'll have other problems down the road.

I've got it looking good now, I deleted via Favourite Visuals resynced and the config.ini looks like it should.

Well I spoke too soon, it appears that the fav visuals in the config.ini have doubled, my 26 has become 52.

Maybe time to switch to JEmplode (java version) instead.

-ml

I have never had much luck getting Jemplode to connect reliably yet & I've tried several times.

I've been fiddleing w/the config.ini and entering various amounts visuals ala 'fav visuals' menu. It seems everytime I sync after adding the first visuals (5) the visual amounts double each time I sync, after 3 syncs I get 20 from an original 5.
Crap I better stop syncing now I have over 200 visuals.

It seems everytime I sync after adding the first visuals (5) the visual amounts double each time I sync, after 3 syncs I get 20 from an original 5.

Did you do what I suggested in this FAQ entry? Or are you still hand-editing the favorite visuals list?

Emplode no longer supports hand-editing of the favorite visuals list, you must erase it and start over again using the tool that's built into emplode beta 11 now.

I've only added the favorite visuals through emplode but I am having the same problem. They keep multiplying. I removed them all and synched, added them back in and synched again. I checked the config.ini file and it seems to keep adding them again each time they play on the empeg. I checked in emplode and this time it listed each one only once but I haven't synched since the last time.

I am viewing the config.ini file through emplode after doing the registry edit. Am I going to have to delete the config.ini file and start over again? I didn't notice anything funny in the file besides the visuals.

I deleted thru the 'remove' option, then added visuals thru same dialog. I didn't edit the config.ini manually.
Yes I did as per the FAQ suggestion but every resync causes a doubling of visuals. It seems that no matter if you click OK or cancel once your in config.ini and want to leave then do a resync the visuals number doubles.

I'm in the midst of synching again. This time I'm not going to add any favorite visuals and see what happens. Maybe this is a bug?

Damn, okay, then this is an emplode bug.

Laura and Jwickis, if you can save off a copy of your config.ini files and send them to [email protected] with a note describing what emplode is doing to your files, then that would be cool.

Alright, I'll add the favorite visuals back on again. I added just image pan, synched, and went back to the iist and it was added 4 times without the empeg even being on. I'll copy the config.ini file from emplode and send it off.

Sent

Sent also. I also mentioned that emplode shows image pan 4 times on the list where the config.ini file lists it twice. Strange.

Yes your right, same here on both Mk2 & my Mk2a.

Maybe time to switch to JEmplode (java version) instead

I think Emplode still out does JEmplode by far as far as my machine. I have tried JEmplode several times sometimes it finds & connects, most times not. If it does connect it eventually freezes on a task halfway thru.

I have not looked at the ini file yet to see if my favorite visuals are multiplying, but I am having the same ftp/http problem. On my unit (80000539) I have 2.00-beta11 with hijack 199. ftp/http work fine when connected with AC, but do not work at all when connected to DC (emplode works fine either way). I have an extra docking sled that I built into a box so it sits in my home component stack. I built a bracket in the box so that the ethernet is connected when the empeg is docked.

I have not tried anything like docking the player and forcing AC mode through hijack to see if this changes things.



Wireless

add "dc_servers=1" under the [hijack] section. It defaults to off when on DC power, and that should re-enable it.

I'm working on the FAQ, should be fleshed out soon!

I just noticed that my emplode was taking a long time during the "retrieving player configuration" step. I checked, and sure enough, my config.ini has over 5000 favorite visual entries in it. I, too, have never edited the favourite visuals by hand.

The actual number was 5120. Anyone top this?


By the way Tony, maybe you want to edit that FAQ entry to point out this is now a known bug?