i've got 2.0 beta11 and hijack 275 installed. today i wanted to upload some new songs and i always get a synchronisation error.

the error appears when trying to upload new tunes: i get the following details on the warnings:

-Chocolate Salty Balls could not be synchronized., An existing connection was forcibly closed by the remote host. (error 0x80072746)
- Chuckie Chan could not be synchronized., Read on socket failed (error 0x8004003d)
- I Stand Accused (Long Version) could not be synchronized., An established connection was aborted by the software in your host machine. (error 0x80072745)
...

i tried to completely reboot empeg, computer etcetc.. didn't work.. could it be the hijack-kernel?

Hehe. Chef's Chocolate Salty Balls might be causing the problem.

Actually I had similar sync problems before, and flashing an Empeg standard kernel did solve the problems. I can sometimes get syncs to work okay with Hijack, but for larger (hundreds of megs)syncs, I flash a stock kernel, do the sync, and re-flash Hijack. Takes some time but it's safer.

I second that. I had to flash back to the standard kernel to load my entire collection, then I upgraded to 2.011b then to HiJack. I have no problems whatsoever loading 10-15 songs with 2.011b and HiJack.

If you can reliably prove that Hijack is the culprit (i.e., removing Hijack allows a proper synch), you should let Mark know about it in the Programming forum.

There were problems with older versions of hijack before the frame pointers were readded (264). But I am not aware of any issues beyond that point.

ok, i'll try to install the 2.0beta11 kernel without highjack and try the sync again. i'll post the result.
thanks

so i installed 2.0b11 and i'm currently synchronizing - without any problem yet... so maybe this really is a problem with Hijack kernel...

Those error codes indicate a problem with the Microsoft software on the host machine. Install Linux instead, and all will be well.

Actually Mark, if the kernel crashes, the socket will be closed and generate errors similar to that... Those aren't necessarily client-side problems. They're the same error codes I was getting during this ordeal (see screenshot and kernel stack trace.)

So I don't think this is a client-side problem.

Well, I'll wait until more than one newbie has the problem, before I jump to any further conclusions.

And the problem you posted about back in April has long since been addressed.

Cheers

As with any problems with the player, the first thing to do is hook up the serial cable and monitor messages from the player software. So do that, and post the message log.

In this case, the player software is likely just crashing due to the current FID having been deleted/renumbered/whatever, or possibly some other issue to do with installing music BEFORE installing the beta software (it works better the other way around, unfortunately).

Cheers