I've just installed EmpegFace on my XP laptop (lastest version of Hijjack also installed on the RioCar). Installed the .OCX file. No error messages anymore except that it says "Connection Error" in the config options tab and that I can't see anything on the screen of the EmpegFace.
I've entered the IP adress, tried also the network name.
But I can perfectly connect with Internet Explorer (using the network name as well as the IP adress) and have a look at the playlists and so on.
So, what's the problem ?

Didier

Are you connected via a docking station?

if so, try adding DC_Servers=on to the [Hijack] section of your config.ini

EDIT: Nevermind...you can connect from a browser

Quick sanity check...

When you entered the address of the player in the configuration screen, did you do it like this?
192.168.0.123

Or did you do it like this?
http://192.168.0.123

The second one will not work and will produce the exact error you describe. Make sure it's entered the first way.

Hang on.

In another thread on a different forum, you said that you changed the HTTPD port to 82. I don't know if that would even work with EmpegFace.

Why do you need to change the HTTPD port? Are you doing some sort of fancy port-forwarding scheme? Or are you going through a proxy server or NAT? EmpegFace doesn't support any of that, it expects the player to be on your local LAN.

The http port set on 82 in config.ini was the source of the problem. Could perhaps be nice to add a port option in the next version of the EmpegFace options tab for the geeks that want to make their player answer on another port than 80 !
Very nice tool by the way. Makes it even easier to access the player than charcoalgray99's Web Interface.

Could perhaps be nice to add a port option in the next version of the EmpegFace options tab for the geeks that want to make their player answer on another port than 80 !

Back in the old days, adding a ":82" to the end of your URL would have worked because I was using URLDownloadToFile. But that had problems and I updated Face to use direct TCP calls. Perhaps a future release will offer the Port as a separate option. It's just a question of getting up the gumption to do another release, it's a pretty simple fix.

There's probably a way to binary-hack the existing EXE and change the 80 to an 82, but I wouldn't know how to go digging to find it.