How hard would it be to have emplode audo-save an old copy of config.ini whenever changes are made? (I'm probably saying that wrong). But a new file would be made called "oldconfig.ini" containing the previous version whenever a new version is saved... This is what I do manually, but it this something that can be automated?

Damn, I've got too many threads in Wish Lists!

I like the idea of the automatic back-up. It would also be nice if it was possible to save the config.ini without having to do a full sync.

Not requiring a database rebuildt, it's pretty quick as is.

Quote:
3. But, that said, the player end of the protocol handler could be modified to do this

That'd work, saving the backup on the empeg. Then a simple script or ftp command could revert to the older version?

But, that said, the player end of the protocol handler could be modified to do this

Or Mark could do it (the keeping a backup copy of config.ini) in hijack

Mark, now that more players are going to have extended RAM and you have hinted in the past of adding features to Hijack for large memory players, would something like this be doable? What else do you have up your sleave?

The only big feature on my list now, is Rio Receiver support in Hijack. This will require a player to have more than 16MB, I suspect.

Cheers

Are you planning on working on the player binary switcher to achieve the Rio Receiver effect (since there is an empeg Rio Receiver player, but currently it requires a seperate upgrade, nullifying the ability to use the empeg hard drive), or doing your own implementation?

If it's the latter, I hope this means compatibility with the third party servers out there as well, since I could never get the Rio Receiver on empeg player to see anything beyond the Windows server.

I assume Mark's talking about a Receiver server -- I don't think a client would need a >16Mb player, especially as real Receivers only have 4Mb.

Peter