CASPER
New member
Emunation-sc rev 939.6
Latest Change:
================================================== ==============
rev 939.6
Fixed a lil error I introduced into map3e while fixing map46.
Configurable priorities, see 938.7 below, fixed to now work with multiple system ids.
Providers.conf never worked right and support has been dropped.
Radegast and newcamd cardclients fixed. Sample .conf file added.
New [SC] ini entry CCDump turns on/off raw data dumps to console for cardclient and smartcard.
ST19Com and ST19Echo settings activated in ini. Set ST19Com to nonexistant port if the smartcard interface is not in use. You can ignore the Com port opening error if not in use.
Be sure you have a Nagra3=-15 or something, as there are n3 stubs that show as a valid protocol (wishful thinking). N3 ca-ids are valid for cardsharing, if supported by your server. Be careful of unintended consequences, on gc irdeto is sometimes a valid protocol, but i bet you don't have valid keys. Check your ini against the distribution file. All priorities are negative numbers. -3 is higher than -5. No number may be less -20 nor higher than -1.
You can change between smartcard, cardclient and native code on the fly by inserting/removing card and retuning the channel, if priorities are set appropriately. You can not change priorities on the fly.
Finally, before you say cardclient doesn't work, check your firewall settings.
Latest Change:
================================================== ==============
rev 939.6
Fixed a lil error I introduced into map3e while fixing map46.
Configurable priorities, see 938.7 below, fixed to now work with multiple system ids.
Providers.conf never worked right and support has been dropped.
Radegast and newcamd cardclients fixed. Sample .conf file added.
New [SC] ini entry CCDump turns on/off raw data dumps to console for cardclient and smartcard.
ST19Com and ST19Echo settings activated in ini. Set ST19Com to nonexistant port if the smartcard interface is not in use. You can ignore the Com port opening error if not in use.
Be sure you have a Nagra3=-15 or something, as there are n3 stubs that show as a valid protocol (wishful thinking). N3 ca-ids are valid for cardsharing, if supported by your server. Be careful of unintended consequences, on gc irdeto is sometimes a valid protocol, but i bet you don't have valid keys. Check your ini against the distribution file. All priorities are negative numbers. -3 is higher than -5. No number may be less -20 nor higher than -1.
You can change between smartcard, cardclient and native code on the fly by inserting/removing card and retuning the channel, if priorities are set appropriately. You can not change priorities on the fly.
Finally, before you say cardclient doesn't work, check your firewall settings.
