bozomustafa_68
Well Known Member
- Messages
- 16,935
EmuNation-sc rev 939.0
Code:
* Fix for bev bad key packets.
Last edited:
* Fix for bev bad key packets.
rev 939.1
Added set computer time and date from the sat stream. Never have a recording start at the wrong time again. New ini file entry needed under [Menu Options] SetClock=1 to set the clock on first channel tune. Menu item, under 'options', turns function on/off and menu item to set clock now.
N.B. Your computer is keeping its clock in UTC, formerly known as GMT. Windows calculates local time from UTC. Depending on your time zone, its 'tomorrow' around 7:00 or 8:00 in the evening. Console display of time set is in UTC, so don't be surprised by it being 'tomorrow' before it seems to be so, in your local time.
N.B. Vista users, program app must "Run As Administrator" for time set to work. If you have not already been running as admin you MAY need to copy the contents of \users\{yourusername}\appdata\local\virtualstore\program files\dvbprogramname\ including its subdirectories to \program files\{dvbprogramname} to maintain your settings. If you try to set the time in Vista without admin privileges, it will tell you that you have and the function will turn itself off.
[B]rev 939.2
Fix for freezing on map3c.
Fix for emm processing on startup in DVBPlus.[/B]
Fix for map 3d
You'll notice stubs for n3, it does NOT NOT NOT work with n3, you can log the encrypted ecm, but thats all.
[B]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.[/B]