Hadu - CCcam DVB plugin

Changelog:
----------
0.1.2.7:
-(partial) support for DreCrypt EMMs,
-EMM PIDs associated to ECM PIDs (based upon the CAID and provider criteria) are now all displayed into the concerned column ("Monitor" window),
-an option has been added to display all the other EMM PIDs (i.e. EMM PIDS not associated to ECM PIDs; see "DispAllEMMs" option);
-"EMMCAID" option has been extended, in order to include an optional EMM PID (see "EMMCAID" option),
-bug fix for the non correct display of indexed nodes (when the list of the nodes is sorted by user),
-Hadu is considered back as a 2.1.4 version client by default. You can of course still modify the client version sent to the server (see "Version" option),
-minor modification into the possible levels of informations to log (see "LogMessLevel" option),
-display of the "Server Infos" window has been optimized (it's now a bit more reactive, while using less CPU resources),
-an option has been added when Hadu is used within the DVBViewer recording session. It's now possible to start the connection with the server(s) only if the channel is encrypted (see "DVBViewerEncrServ" option),
-support for the new CCCam commands introduced in CCCam version 2.2.0 or above (i.e. commands 0F for the node data, and commands 0C, 0D for the new CCCam "checks"). An option has been added to authorize or not the Node SID assignment/rejection feature present in commands 0F (see "UseNodeSID" option). The Node SID assignment/rejection feature will be activated by the server, only if Hadu is also declared as a CCCam client version 2.2.0 or above (see "Version" option). But, as there is a bug concerning the new CCCam "checks", declaring Hadu as CCCam client version 2.2.0 may conduct to an improper channel decoding (see the new workaround menu "Switch DCW Last Byte"),
-support for the OSCAM Partner handle, and its Node SID assignment/rejection feature (the Extended ECM Mode is also checked but currently not used). Several options have been added to authorize them or not (see "OSCAMPartner", "OSCAMExt" and "OSCAMSID" options). Furthermore, when activated these features are displayed at the bottom of the "Server Infos" window, as for the build of the OSCAM server,
-2 new features have been added: a list of ECM PIDs used (i.e. ECM PIDs cache; see "Hadu-Cache.txt" file), and a list of manual ECM PIDs (see "Hadu-Manual.txt" file). These features may be activated/deactivated directly from the main menu of Hadu (see "Cache" sub-menu, and "CacheUse", "CacheUpdate", "ManualUse" options),
-an new column (title "Opt") has been added in the list of the nodes into the "Server Infos" window (to display eventual additional infos concerning the nodes),
-all the log files (i.e. 'Hadu-Mes.log', 'Hadu-EMM.log', 'Hadu-PIDxxxx.log' and 'Hadu-Dump.txt') are now always put in the same directory as the plugin itself (no more in path indicated by "Keypath2", if this option is used). "Keypath2" is reserved for files possibly shared within several occurs of Hadu (like the files for the ECM PIDs used and the manual ECM PIDs),
-support for Nagra Tiger EMMs,
-TID and SID for the current channel are displayed into the "Monitor" window,
-an option has been added when providers/ChIDs used within CCCam messages are rejected by the server (see "DontUseProvFor" option),
-usual minor bug fixes and enhancements

Hadu-Cccam DVB plugin V 0.127(2).Zip

I have built a ubuntu cccam server that i am not sure i know how to put in proper use.

I have an HTPC on windows 7 with a dvb-s2 card but it seems to me i am missing something, because i keep hearing or reading about 'card' that needs to been read by CCcam, the only card i have in my system is a DVB card.

Dvb card is TBS 8922

I am using Hadu in my dvbdream plugin direcory.

Questions:
1. Do i need another card with my setup, if i do need one how do i go about it.
2. I scan with my dvb card and i get good signal but no channels found, what am i doing wrong.
3. How can i tell if my dvb card / or cccam is working fine when i scan.
4. If you have figured out how to make cccam work with dvb card please could be kind to share the info

thanks

the "card" is a subscription card to view whichever channels you wish to.
Are you scanning the right sat ?? I know it sounds crazy but a "good signal" can be found on the same frequency but different sats.
you need to also install CCcam if you want to "share your card from your living room to your bedroom" for example..
within HADU , you have options to use just as a server ( Cline) but later add the Fline to CCcam..

Introduction:
-------------




Hadu is a CardSharing Client plugin for DVB softwares on PC using DVB TV-Cards (Windows).




It works as a MD plugin, a DVBCore plugin or as a DVBViewer plugin.




Currently, it only supports the CCCam protocol (without the AU option).

Installation:
-------------
Just put Hadu.dll and Hadu.ini into the directory relative to plugins, regarding your current DVB software. It can be the directory of the software (i.e. for old versions of ProgDVB), or a given subdirectory (i.e. ./Plugins for MyTheater and Alt-DVB, ...).




As it is compatible with the DVBCore API, use it as a DVBCore plugin (for DVBCore softwares) instead of using it with MDWrapper. With DVBViewer, use it as DVBViewer plugin instead of using it with SoftCSA.




Don't use two or more CardSharing Clients and/or SoftCam Emulators at the same time (like Yankse, S2Emu or VPlug), unless you know perfectly what you are doing.







Directories of installation for the main DVB softwares:
-------------------------------------------------------
Put all the files (i.e. only Hadu.dll + Hadu.ini currently) in the same directory , as indicated hereafter:




-ProgDVB : main directory of the DVB software (or /Plugins subdirectory for version 4.38 or later of ProgDVB)
-Alt-DVB : /Plugins (or /Plugins/av0) subdirectory, and/or /Plugins/pip subdirectory for the pip, and others (/Plugins/av1 to Plugins/av2
-MyTheater, RitzDVB: /Plugins subdirectory (to use Hadu as a DVBCore plugin). Try to avoid the solution MDWrapper.dll in /Plugins subdirectory and Hadu in /MDPlugins subdirectory (MDWrapper is a workaround to make old MD plugins working with MyTheater and other DVBCore softwares)
-DVBDream 0.xx: /Modules subdirectory since version 0.85 (to use Hadu as a DVBCore plugin). /Plugins subdirectory (to use Hadu as a MD plugin) for precedent versions
-DVBDream 1.xx and above : /Plugins/pip00 and others (/Plugins/pip01 up to /Plugins/pip19) subdirectories, to use Hadu as a MD plugin
-WatchTVPro: /Plugins subdirectory (Hadu is using the TT Trick automatically if it is possible)
-HispaDVB: main directory of the DVB software for old versions, and /Plugins subdirectory since version 2. Hadu is no more using the TT Trick automatically for this software, because it is no more needed for HispaDVB version 2 and above
-MultiDec: main directory of the DVB software (Hadu supports natively the different versions of the SS1 firmware)
-DVBViewer: /Plugins subdirectory. Avoid the solution SoftCSA.dll in /Plugins subdirectory and Hadu in /MDPlugins subdirectory. Please, note that the CSA.dll (coming with the SoftCSA package coded by Pikachu) is recommended for faster unscrambling, though not absolutely mandatory. The CSA.dll must be located into the /Plugins subdirectory (or KeyPath2) or into the main directory of the DVB software. Otherwise, Hadu will use its own internal CSA algorithm (code kindly provided by courtesy of Pikachu. Thanks!). With DVBViewer version 3.4 and above, you can also use the FFDeCSA.dll (both with the CSA.dll) : depending of your DVB card, the 'Open whole Transponder' Hardware option in DVBViewer will have to be checked or not, to optimize the video/audio CSA unscrambling treatment.
The 'Has CI module' entry option into the hardware options of DVBViewer must be checked.
-DVBViewer recording service: /Plugins/Plugins1 to /Plugins/Plugins31 subdirectories. Allow this recording service to interact with the Desk, and set "Systray=1" for the concerned Hadu.ini files. Don't forget that it's impossible to connect to the same server twice (double login are rejected by CCCam servers).
-***View: /MDPlugins subdirectory
-DvbTn: /Plugins subdirectory (to use Hadu as a DVBCore plugin)
-WinSTB: /MDPlugins subdirectory
-DiavloB: /Plugins subdirectory (to use Hadu as a MD plugin, though the software is based upon the DVBCore SDK)
-MajorDVB: /Plugins subdirectory
-TSReader: /MDPlugins subdirectory
-WinClip: /Plugins subdirectory




Caution: For DVB softwares based on the DVBCore SDK, don't install Hadu as a MD plugin and as a DVBCore plugin (choose either the first or the second solution, but not both !). Same thing for DVBViewer.




Do not use the DLL TTTrick.dll: Hadu has its own TT Trick implemented.




Each time it is possible (Alt-DVB2 and DVBDream 1.xx, for instance) set the packet size for plugins to 184 bytes, to minimalize the delay for the decoding process.







Other Files used :
------------------
None currently.







Main Menu:
----------
-Active: If checked, the plugin will use the incoming ECMs to try to decode the current encrypted channel (i.e. by sending the ECMs and requesting the needed DCWs to the server(s)). Furthermore, connections with servers will only start if the plugin is active.




-Use PSI Tables: If checked, the plugin will analyze the PMT (for the list of ECMs) and the CAT (for the list of EMMs). If not checked, it will take data obtained from the DVB software. It "costs" a little more time to begin the decoding when you change of a channel, but it is strongly advised to use this option for better results. Data given by DVB softwares are often incomplete, erroneous and are not continuously updated.




-Monitor ...: Display the Monitor window to see the current analysis work and results.




-Log Messages: You can log the main actions and the incoming/outgoing messages with the servers.The log files are stored, either in the KeyPath2 directory if used, or in the directory of Hadu. Note that this option may have a negative impact on the response time.




-Log a PID...: You can log any given PID, using this submenu. Logs are made in text format. To stop the logs, just uncheck the corresponding menu. Note that by default frames of data which are transmitted are "truncated" to the usual 184 bytes size (only the payload of the TS, without the 4 bytes header). Active log is automatically closed if a channel switch occurs. The log files are stored either in the KeyPath2 directory if used, or in the directory of Hadu.




-Systray: If checked, an icon for Hadu is displayed in Systray. Right-click on this icon shows an extract of this main menu. To stop it, uncheck the corresponding menu.




-About...: Not much to say about it: version of the plugin and kind of DVB-API can be found here. You can also find some infos for special DVB softwares (i.e. "- TT xxxxxx" if the TT Trick is currently used, and "- MDROOT xxxxxx" for MultiDec).







Options:
--------
In the Hadu.ini file (same location as the plugin), you can find the following options (values in brace [] are default values) :




[General] Section




-PluginActive ([1=Yes] or 0=No) : Same as "Active" option in the main menu.
-KeyPath2: Files loaded and written by the plugin are stored in KeyPath2. If KeyPath2 is not used, only the directory of the plugin is used for loading and writing files.







[Options] Section




-UsePSITables ([1=Yes] or 0=No) : Same as "Use PSI Tables" option in the main menu. This flag is conditional for some other options.
-SurveyPMT ([1=Yes] or 0=No) : Flag to indicate the plugin to "survey" the changes in the PMT. Only active if UsePSITables option is active. Its main use is to detect when a given channel change : non encrypted (for advertisements) to encrypted (in many pay-session channels for instance).
-UsePATforPMT (1,2 or [0]) : Flag to indicate the plugin to obtain the PMT directly from the PAT and not from the DVB software. Only active if UsePSITables option is active. Necessary if PMT data given by the DVB software is erroneous or missing. 0=Auto, 1=Forced to Yes, 2=Forced to No. If Auto is selected, the PAT will be scanned only if the PMT data are unavailable (in case of a change for the PMT PID): but it takes several seconds more.
-DontUpdViewer (1,2,3 or [0]) : Flag to don't update DVB software when ECM PID changes and/or Don't Send DCWs (Decoded Control Words). 0=Do both, 1=Don't update DVB software, 2=Don't send DCWs, 3=Don't update DVB software and Don't send DCWs. Note that if the TT Trick is used, the DCWs are not "really" send to the DVB software anyway but directly to the device.
-UseDVBTime ([1=Yes] or 0=No) : Flag to use UTC time in DVB stream (currently unused). The time displayed in the Monitor window is the local time computed from the computer system time (if it's within parenthesis), or from the last UTC DVB time received (if authorized and available).
-MaxECMPIDs (1-10. Default is [4]) : Maximum number of simultaneous ECM PIDs in use. Only one ECM PID can be active at the same time for one given server.
-MaxConnections (1-32. Default is [4]): Maximum number of simultaneous connections (i.e. sockets). Only one connection can be active at the same time for one given server.
-DisplayIPorURL ([1=IP Address] or 0=URL) : flag to display IP Address or URL in the Server list (Monitor window).
-ECMTimeout (2-20 seconds. Default it [3]) : if no ECM is received during this time, Hadu will consider that a timeout has occurred, and will swith to another possible ECM PID. This option is mostly to be used with "wrapper" applications like SSSP Plug, .... In these cases, use a value higher than the ECM change frequency (12 or 14 seconds should be enough, for instance). Of course, increasing this value will slow the start decoging process, if a possible ECM PID is processed, while there is no stream for it; so use this option wisely.
-MaxCAIDLoops (0-n. Default is [4]): Maximum number of loops for CAIDs and nodes for a channel before giving it. 0 means no limits.
-LogMessages (1=Yes or [0=No]) : Same as "Log Messages" option in the main menu.
-LogMessLevel (0-4. Default is [1]) : Level of informations to log into the text file called Hadu-Mes.log. The levels are cumulative: which means that level 0 stands for only level 0, level 1 stands for levels 0 and 1, and so on.
-Systray (1=Yes or [0=No]): Same as "Systray" option in the main menu.







[Specific] Section




-DVBViewerAPI (1=Yes or [0=No]) : Flag to force the plugin to the DVBViewer 3.2 API Type, if DVBViewer version is 3.4 and above. 0=Auto, 1=Forced to 3.2 API Type.
-DVBViewerAllAudio ([1=Yes] or 0=No) : Flag to decode all the Audio PIDs of the current channel, if more than one is present. 0=Only the current Audio PID, 1=All the Audio PIDs. Available only for DVBViewer version 3.4 and above, and if the "Use PSI Tables" option is active. This flag is also used to decode eventually the TeleText/VideoText PID : 0=No, 1=Yes (if scrambled).
-DVBViewerCSAStat (1=Yes or [0=No]) : Flag to display some CSA statistics in the Monitor window (below the PMT and CAT status line). 0=No statistics, 1=Display some statistics. The statistics concern the number of calls to the different CSA types, and the number of video/audio encrypted TS received into the last packet.







[Device] Section




-MDRoot (1,2 or [0]) : Flag to analyze the root firmware in case of MultiDec, to determine automatically DescrCommand, XorEven and XordOdd (see hereafter). 0=Auto (for Multidec), 1=Forced to Yes, 2=Forced to No. This concerns only premium DVB Card "TT-compatible". Note  the values for the following options prevails from the one determined by this option.
-DescrCommand : 2 Bytes (4 hex chars)
-XorEven : 8 Bytes (16 hex chars)
-XorOdd :  8 Bytes (16 hex chars)
Don't use them unless you know exactly what you are doing.
-UseTT (1,2 or [0]) : Flag to use the TT Trick. 0=Auto (for WatchTVPro), 1=Forced to Yes, 2=Forced to No. This is only needed for DVB softwares which don't accept to send Direct DVB Commands. You need to have a premium DVB Card "TT-compatible" (like Technotrend DVB-S, Hauppauge Nexus-S, TechniSat ***Star1) and a patched root firmware.







Servers Sections:
-----------------




For each server declared, the convention for its declaration is to create a section with :
[Serv_whateveryouwishforyourservername]   (note the "Serv_" string at the beginning).




Then comes the different parameters for the server. Only the "Server" parameter is mandatory.




Syntaxe for the "Server" parameter : 
Server=Protocol:Server:Port:(unused):Username:Password




Sample: Server=CCCam:MyServer.com:12000:0:MyUsername:MyPassword, where
-CCCam: Declaration for a CCCam server (other protocols currently not available),
-MyServer.com: URL or IP address for the server,
-12000: Port for the CCCam server (decimal value),
-0: Caid/mask. Not used (may be empty), see "CAIDProv" and "NoCAIDProv" parameters instead,
-Myusername: Name of the user (limited to 20 characters for CCCam protocol),
-Mypassword: Password for the user.




Others parameters (each of them is optional):




-Active ([1=Yes] or 0=No): Server active or not active. A non active server cannot be started.
-Timeout (0=None, or 3-7 seconds. Default is [5] seconds): Timeout value if the server is not answering,
-PadTime ([0=None], or (Timeout+2)-N seconds): interval of time for which a "pad" command is sent to the server if no other commands has already been sent (usually must be kept to 0),
-WantEmus (0=No or [1=Yes]): similar to WantEmus option in CCCam.cfg. If set, friends emus are also used (if the server has authorized them for the user).
-MaxHop ([0=None], or 1-N): nodes with a hop value superior to this limit are not used. A null value indicates no limits. Even if they are disabled with this rule, the concerned nodes are displayed into the list of nodes, but are not available.
-CAIDProv ([None]): list of CAID/Providers ONLY used to make requests to the server(s). Each entry may concern a whole CAID, or just only one provider for this CAID. Entries are separated using a comma character. Samples:
CAIDProv=0100,1801 : only CAIDs 0100 and 1801 will be used.
CAIDProv=0604,0100:0084,0100:006A : only CAID 0604 and CAID/Providers 0100/84,0100/6A will be used.
-NoCAIDProv ([None]): list of CAID/Providers EXCLUDED. Syntax similar to the "CAIDPRov" option. Samples:
NoCAIDProv=0604,0500 : CAIDs 0604 and 0500 won't be used.
NoCAIDProv=0100:6A,1810,0500:032100 : CAID 1810 and CAID/providers 0100/6A,0500/32100 won't be used.
-NoNodeCAID ([None]): list of Node/CAIDs excluded. Each entry may concern a whole server (i.e all nodes belonging to this server), or just only one CAID for this server (i.e. usually only one node of the server). Entries are separated using a comma character. Samples:
NoNodeCAID=0102030405060708,1A1B1C1D1E1F2021 : these 2 servers won't be used.
NoNodeCAID=0102030405060708:0100,1A1B1C1D1E1F2021:500 : CAID 0100 won't be used for the first indicated server, and CAID 0500 won't be used for the second server.
-CAIDTunnel ([None]): list of CAID tunneling entries, currently limited to Betacrypt<--->Nagra3 CAIDs. Each entries are separated by a comma, and data within an entry are separated with a colon character. Syntax for each entry :
.CAID to use within ECMs stream (mandatory),
.CAID to use when requesting the server (mandatory),
.Provider (not used; null value),
.SID concerned for the tunneling feature (optionnal). If this value is not filled or null, all the channels using the first CAID value are possibly concerned.
Samples:
CAIDTunnel=1833:1702 (all the channels)
CAIDTunnel=1833:1702:0:81,1833:1702:0:82 (channel with SID=$0081 or $0082).
-NoSID ([None]): list of SIDs not to processed. Entries are separated using a comma character. Sample:
NoSID=0001,0002,0ABC
-PrioGenRules (default is [Hop]): general rules for priority. All entries are separated by a comma. General rules always applied first, and concerned all the nodes. Currently, only the hop level and the emulator status are used. Possible values for the the first option: Hop, RHop, NHop. Possible values for the the second option: Emu, REmu, NEmu
For all of them, xxxx means rule xxxx, Rxxxx means inversed rule for it, and Nxxxx means no rule for this option.
.Hop: priority for nodes with lesser hop levels,
.Emu: priority for emulator nodes (applied after the former rule).
Here are a few samples (option values are not case sensitive):
.PrioGenRules=NHop : no priority rule concerning hop values
.PrioGenRules=REmu : emulator nodes used after non emulator nodes (but remember that the default value PrioGenRules=Hop is still applied for this sample)
.PrioGenRules=Hop,NEmu: priority for nodes with lesser hop levels, and no rules for emulator nodes.
-PrioCAIDProv ([None]): list of CAID/Providers for node priority. Syntax similar to the "CAIDPRov" option. The first CAID[/Provider] has priority over the second one, and so on; and all the CAID/Providers present into this list have priority over the other ones (i.e. those not present in the list).
Samples:
.PrioCAIDProv=0500,0100 : CAID 0500 has priority over CAID 0100, and above all other ones,
.PrioCAIDProv=0100:006A : CAID 0100, provider 006A has priority over all CAID/Providers.
Manual ECM PID selection modifies all these rules (see corresponding infos into the "Display" paragraph).




So, for each new server to add with by default values, add these 2 lines in your .ini file, modifying the concerned data with your own ones:
[Serv_MyServer]
Server=CCCam:MyServer.com:12000:0:MyUsername:MyPassword




The above sample is corresponding to this C line for a CCCam server .cfg file: 
C MyServer.com 12000 MyUsername MyPassword







Display:
-------
There are two kinds of display.







The "Monitor" window (called from the main menu), used to display general and CAID informations for the channel, and general informations for the server(s).




Double-clicking on an CAID row (i.e. ECM PID) will force the plugin to try to use this ECM PID entry. If it's not compatible for a given server, the following next compatible ECM PID entry will be used instead. It's important to note that node priorities are modified when this functionality is used: ECM PID selection becomes the first priority rule, and then only are applied all the other node priorities (i.e. general rules and CAID/provider for nodes). Change or re-select the corresponding channel will cancel the temporarily effects of the manual ECM PID selection; as for the "Cancel manual ECM PID selection" entry within the server menu.  




Double-clicking on an server will display the "Server Infos" window (see hereafter).




Right-clicking on an server will display a menu to:
-Start/Stop a server (if the server is active). Same as the "Active" option in the configuration file,
-Activate/Deactivate a server,
-Ask to retry all the possible ECMs again (if the server is started),
-Cancel the temporarily effects of the manual ECM PID selection.




The meanings for the main status of the servers are:
-"Started." : connected and logged to the server; channel not encrypted,
-"Stopped." : not connected to the server,
-"Started. Send ECM..." : started and ECM request sent to the server,
-"Started. Got DCWs." : started and positive result given back by the server,
-"Started. (None)" : started, encrypted channel but no possible decoding using this server ; either because there is no corresponding CAID/provider for this channel, or because all the possible CAI/providers requested from the server have given negative results,
"Stopped (already in use)." : not connected to the server. The same server (i.e. same IP address and same port) is already in use and connected.







The "Server Infos" window (called from the server list in the "Monitor" window) is used to display informations for all the nodes of the server. Columns inside the nodes list:
-S (for Status): indicates the status of the node. [Empty] = not available (because of the configuration restrictions -see "MaxHop" options-; or because it has been declared disconnected by the server). Furthermore, unavailable nodes are grayed. "....." = node available, but forced by the user to be ignored. " +" = node available. "**" = node available and currently in use.
-Req/Got: numbers of ECM requests sent to the node, and of DCWs received from it.
-Hop, CAID and Providers: common informations for a node.
-DCWs (ms): last time response for DCW received from the server for the node.
-Neg (ms): last time response for negative answer received from the server for the node (i.e. 'No decoding' messages). Both for DCWs and Negative time responses, there is a first latency for multiple I***** ECMs (if several ChIDs are used).
-Timeout: number of timeouts for ECM requests.
-Discon: number of disconnections (and eventual re-connections).
-Index and Node ID: identification of the node.




Right-clicking on an node will display a menu to:
-toggle its state between "to use" and "to ignore" (if the node is available).
-enable or disable the selected CAID for the selected server. This may correspond to one or several nodes for the concerned server,
-enable or disable all the CAIDs for the selected server. 
Depending of the current status for the concerned node/CAID/server, these different entries for this menu are available or not. Enable/Disable a CAID or all CAIDs are equivalent to the "NoNodeCAID" option into Hadu.ini.




In the nodes list, providers included in parenthesis (e.g. "(0000)") or CAIDs included in parenthesis, means that these providers or CAIDs can't be used.




When they are included into brackets (e.g. "[0500  123450 6789A0]") or into braces (e.g. "{0604  00000}"), the corresponding node is no more connected or excluded according to various options present in the .ini file; in these 2 last cases, the node status can't be modified (by double-clicking on it).




The meanings for the main status of the nodes are:
-[Nothing] : node can't neither be used nor having its status modified,
-"....." :  node has been its status set to "ignore" by the user,
-" +" : node can be used,
-"**" : node currently in use.




Data in the "Server Infos" window are refreshed each 4 seconds. You can force an extra refresh with the "Refresh" button.




The clipboard button serves to copy data of the window into the clipboard (text format).




At the bottom of the window, the total numbers of nodes and CAID/providers are displayed: the first number of both of them indicates the whole total number, will the second number indicates the total number of available items.







Limits:
-------
Here are the main current limits applied into the plugin:
-Maximum number of CCCam servers (active or not active): 6
-Maximum number of nodes per server : 2048
-Maximum number of providers per nodes : 16
-Maximum number of hops per node : 16 (though more than 3 or 4 is probably useless)
-Maximum number of CAID/providers entries into to "CAIDProv" and "NoCAIDProv" options : 32
-Maximum number of nodes/CAID entries into to "NoNodeCAID" option : 32
-Maximum number of CAID/CAID/provider/SIDs entries into to "CAIDTunnel" option : 32
-Maximum number of SIDs entries into to "NoSID" option : 64
-Maximum length size for server name and URL/IP address : 128
-Maximum length size for user and password: 20 for the user, 128 for the password
-Maximum number of CAID/providers entries into to "PrioCAIDProv" option : 32.




To not overload CCCam servers, it's not allowed within the plugin to have 2 active connections with the same server at the same time. Same server meaning here: same IP address and same port.

Thanks for your reply and the link provided.
I have already read the info you provided. Let me make myself a little clearer....

1. I have already built an ubuntu Cccam server.
2. I have a dvb card tbs 8922, running dreamdvb with HADU plugin in place.
3. I scan 110w, 61.5w, and 2410 i do get good signal and quality 99/70% respectively but no channels.
4. I do no have 'card' to share or do i have one. If i do how do in get one the US. or can i still scan and get channels with it.
5. How to i test my Cccam server on my htpc as they are two different machines on the network/subnet.

don

Quote from cazuela

the "card" is a subscription card to view whichever channels you wish to.
Are you scanning the right sat ?? I know it sounds crazy but a "good signal" can be found on the same frequency but different sats.
you need to also install CCcam if you want to "share your card from your living room to your bedroom" for example..
within HADU , you have options to use just as a server ( Cline) but later add the Fline to CCcam..

Code

Code

Introduction:
-------------




Hadu is a CardSharing Client plugin for DVB softwares on PC using DVB TV-Cards (Windows).




It works as a MD plugin, a DVBCore plugin or as a DVBViewer plugin.




Currently, it only supports the CCCam protocol (without the AU option).

Display More

Code

Installation:
-------------
Just put Hadu.dll and Hadu.ini into the directory relative to plugins, regarding your current DVB software. It can be the directory of the software (i.e. for old versions of ProgDVB), or a given subdirectory (i.e. ./Plugins for MyTheater and Alt-DVB, ...).




As it is compatible with the DVBCore API, use it as a DVBCore plugin (for DVBCore softwares) instead of using it with MDWrapper. With DVBViewer, use it as DVBViewer plugin instead of using it with SoftCSA.




Don't use two or more CardSharing Clients and/or SoftCam Emulators at the same time (like Yankse, S2Emu or VPlug), unless you know perfectly what you are doing.







Directories of installation for the main DVB softwares:
-------------------------------------------------------
Put all the files (i.e. only Hadu.dll + Hadu.ini currently) in the same directory , as indicated hereafter:




-ProgDVB : main directory of the DVB software (or /Plugins subdirectory for version 4.38 or later of ProgDVB)
-Alt-DVB : /Plugins (or /Plugins/av0) subdirectory, and/or /Plugins/pip subdirectory for the pip, and others (/Plugins/av1 to Plugins/av2
-MyTheater, RitzDVB: /Plugins subdirectory (to use Hadu as a DVBCore plugin). Try to avoid the solution MDWrapper.dll in /Plugins subdirectory and Hadu in /MDPlugins subdirectory (MDWrapper is a workaround to make old MD plugins working with MyTheater and other DVBCore softwares)
-DVBDream 0.xx: /Modules subdirectory since version 0.85 (to use Hadu as a DVBCore plugin). /Plugins subdirectory (to use Hadu as a MD plugin) for precedent versions
-DVBDream 1.xx and above : /Plugins/pip00 and others (/Plugins/pip01 up to /Plugins/pip19) subdirectories, to use Hadu as a MD plugin
-WatchTVPro: /Plugins subdirectory (Hadu is using the TT Trick automatically if it is possible)
-HispaDVB: main directory of the DVB software for old versions, and /Plugins subdirectory since version 2. Hadu is no more using the TT Trick automatically for this software, because it is no more needed for HispaDVB version 2 and above
-MultiDec: main directory of the DVB software (Hadu supports natively the different versions of the SS1 firmware)
-DVBViewer: /Plugins subdirectory. Avoid the solution SoftCSA.dll in /Plugins subdirectory and Hadu in /MDPlugins subdirectory. Please, note that the CSA.dll (coming with the SoftCSA package coded by Pikachu) is recommended for faster unscrambling, though not absolutely mandatory. The CSA.dll must be located into the /Plugins subdirectory (or KeyPath2) or into the main directory of the DVB software. Otherwise, Hadu will use its own internal CSA algorithm (code kindly provided by courtesy of Pikachu. Thanks!). With DVBViewer version 3.4 and above, you can also use the FFDeCSA.dll (both with the CSA.dll) : depending of your DVB card, the 'Open whole Transponder' Hardware option in DVBViewer will have to be checked or not, to optimize the video/audio CSA unscrambling treatment.
The 'Has CI module' entry option into the hardware options of DVBViewer must be checked.
-DVBViewer recording service: /Plugins/Plugins1 to /Plugins/Plugins31 subdirectories. Allow this recording service to interact with the Desk, and set "Systray=1" for the concerned Hadu.ini files. Don't forget that it's impossible to connect to the same server twice (double login are rejected by CCCam servers).
-***View: /MDPlugins subdirectory
-DvbTn: /Plugins subdirectory (to use Hadu as a DVBCore plugin)
-WinSTB: /MDPlugins subdirectory
-DiavloB: /Plugins subdirectory (to use Hadu as a MD plugin, though the software is based upon the DVBCore SDK)
-MajorDVB: /Plugins subdirectory
-TSReader: /MDPlugins subdirectory
-WinClip: /Plugins subdirectory




Caution: For DVB softwares based on the DVBCore SDK, don't install Hadu as a MD plugin and as a DVBCore plugin (choose either the first or the second solution, but not both !). Same thing for DVBViewer.




Do not use the DLL TTTrick.dll: Hadu has its own TT Trick implemented.




Each time it is possible (Alt-DVB2 and DVBDream 1.xx, for instance) set the packet size for plugins to 184 bytes, to minimalize the delay for the decoding process.







Other Files used :
------------------
None currently.







Main Menu:
----------
-Active: If checked, the plugin will use the incoming ECMs to try to decode the current encrypted channel (i.e. by sending the ECMs and requesting the needed DCWs to the server(s)). Furthermore, connections with servers will only start if the plugin is active.




-Use PSI Tables: If checked, the plugin will analyze the PMT (for the list of ECMs) and the CAT (for the list of EMMs). If not checked, it will take data obtained from the DVB software. It "costs" a little more time to begin the decoding when you change of a channel, but it is strongly advised to use this option for better results. Data given by DVB softwares are often incomplete, erroneous and are not continuously updated.




-Monitor ...: Display the Monitor window to see the current analysis work and results.




-Log Messages: You can log the main actions and the incoming/outgoing messages with the servers.The log files are stored, either in the KeyPath2 directory if used, or in the directory of Hadu. Note that this option may have a negative impact on the response time.




-Log a PID...: You can log any given PID, using this submenu. Logs are made in text format. To stop the logs, just uncheck the corresponding menu. Note that by default frames of data which are transmitted are "truncated" to the usual 184 bytes size (only the payload of the TS, without the 4 bytes header). Active log is automatically closed if a channel switch occurs. The log files are stored either in the KeyPath2 directory if used, or in the directory of Hadu.




-Systray: If checked, an icon for Hadu is displayed in Systray. Right-click on this icon shows an extract of this main menu. To stop it, uncheck the corresponding menu.




-About...: Not much to say about it: version of the plugin and kind of DVB-API can be found here. You can also find some infos for special DVB softwares (i.e. "- TT xxxxxx" if the TT Trick is currently used, and "- MDROOT xxxxxx" for MultiDec).







Options:
--------
In the Hadu.ini file (same location as the plugin), you can find the following options (values in brace [] are default values) :




[General] Section




-PluginActive ([1=Yes] or 0=No) : Same as "Active" option in the main menu.
-KeyPath2: Files loaded and written by the plugin are stored in KeyPath2. If KeyPath2 is not used, only the directory of the plugin is used for loading and writing files.







[Options] Section




-UsePSITables ([1=Yes] or 0=No) : Same as "Use PSI Tables" option in the main menu. This flag is conditional for some other options.
-SurveyPMT ([1=Yes] or 0=No) : Flag to indicate the plugin to "survey" the changes in the PMT. Only active if UsePSITables option is active. Its main use is to detect when a given channel change : non encrypted (for advertisements) to encrypted (in many pay-session channels for instance).
-UsePATforPMT (1,2 or [0]) : Flag to indicate the plugin to obtain the PMT directly from the PAT and not from the DVB software. Only active if UsePSITables option is active. Necessary if PMT data given by the DVB software is erroneous or missing. 0=Auto, 1=Forced to Yes, 2=Forced to No. If Auto is selected, the PAT will be scanned only if the PMT data are unavailable (in case of a change for the PMT PID): but it takes several seconds more.
-DontUpdViewer (1,2,3 or [0]) : Flag to don't update DVB software when ECM PID changes and/or Don't Send DCWs (Decoded Control Words). 0=Do both, 1=Don't update DVB software, 2=Don't send DCWs, 3=Don't update DVB software and Don't send DCWs. Note that if the TT Trick is used, the DCWs are not "really" send to the DVB software anyway but directly to the device.
-UseDVBTime ([1=Yes] or 0=No) : Flag to use UTC time in DVB stream (currently unused). The time displayed in the Monitor window is the local time computed from the computer system time (if it's within parenthesis), or from the last UTC DVB time received (if authorized and available).
-MaxECMPIDs (1-10. Default is [4]) : Maximum number of simultaneous ECM PIDs in use. Only one ECM PID can be active at the same time for one given server.
-MaxConnections (1-32. Default is [4]): Maximum number of simultaneous connections (i.e. sockets). Only one connection can be active at the same time for one given server.
-DisplayIPorURL ([1=IP Address] or 0=URL) : flag to display IP Address or URL in the Server list (Monitor window).
-ECMTimeout (2-20 seconds. Default it [3]) : if no ECM is received during this time, Hadu will consider that a timeout has occurred, and will swith to another possible ECM PID. This option is mostly to be used with "wrapper" applications like SSSP Plug, .... In these cases, use a value higher than the ECM change frequency (12 or 14 seconds should be enough, for instance). Of course, increasing this value will slow the start decoging process, if a possible ECM PID is processed, while there is no stream for it; so use this option wisely.
-MaxCAIDLoops (0-n. Default is [4]): Maximum number of loops for CAIDs and nodes for a channel before giving it. 0 means no limits.
-LogMessages (1=Yes or [0=No]) : Same as "Log Messages" option in the main menu.
-LogMessLevel (0-4. Default is [1]) : Level of informations to log into the text file called Hadu-Mes.log. The levels are cumulative: which means that level 0 stands for only level 0, level 1 stands for levels 0 and 1, and so on.
-Systray (1=Yes or [0=No]): Same as "Systray" option in the main menu.







[Specific] Section




-DVBViewerAPI (1=Yes or [0=No]) : Flag to force the plugin to the DVBViewer 3.2 API Type, if DVBViewer version is 3.4 and above. 0=Auto, 1=Forced to 3.2 API Type.
-DVBViewerAllAudio ([1=Yes] or 0=No) : Flag to decode all the Audio PIDs of the current channel, if more than one is present. 0=Only the current Audio PID, 1=All the Audio PIDs. Available only for DVBViewer version 3.4 and above, and if the "Use PSI Tables" option is active. This flag is also used to decode eventually the TeleText/VideoText PID : 0=No, 1=Yes (if scrambled).
-DVBViewerCSAStat (1=Yes or [0=No]) : Flag to display some CSA statistics in the Monitor window (below the PMT and CAT status line). 0=No statistics, 1=Display some statistics. The statistics concern the number of calls to the different CSA types, and the number of video/audio encrypted TS received into the last packet.







[Device] Section




-MDRoot (1,2 or [0]) : Flag to analyze the root firmware in case of MultiDec, to determine automatically DescrCommand, XorEven and XordOdd (see hereafter). 0=Auto (for Multidec), 1=Forced to Yes, 2=Forced to No. This concerns only premium DVB Card "TT-compatible". Note  the values for the following options prevails from the one determined by this option.
-DescrCommand : 2 Bytes (4 hex chars)
-XorEven : 8 Bytes (16 hex chars)
-XorOdd :  8 Bytes (16 hex chars)
Don't use them unless you know exactly what you are doing.
-UseTT (1,2 or [0]) : Flag to use the TT Trick. 0=Auto (for WatchTVPro), 1=Forced to Yes, 2=Forced to No. This is only needed for DVB softwares which don't accept to send Direct DVB Commands. You need to have a premium DVB Card "TT-compatible" (like Technotrend DVB-S, Hauppauge Nexus-S, TechniSat ***Star1) and a patched root firmware.







Servers Sections:
-----------------




For each server declared, the convention for its declaration is to create a section with :
[Serv_whateveryouwishforyourservername]   (note the "Serv_" string at the beginning).




Then comes the different parameters for the server. Only the "Server" parameter is mandatory.




Syntaxe for the "Server" parameter : 
Server=Protocol:Server:Port:(unused):Username:Password




Sample: Server=CCCam:MyServer.com:12000:0:MyUsername:MyPassword, where
-CCCam: Declaration for a CCCam server (other protocols currently not available),
-MyServer.com: URL or IP address for the server,
-12000: Port for the CCCam server (decimal value),
-0: Caid/mask. Not used (may be empty), see "CAIDProv" and "NoCAIDProv" parameters instead,
-Myusername: Name of the user (limited to 20 characters for CCCam protocol),
-Mypassword: Password for the user.




Others parameters (each of them is optional):




-Active ([1=Yes] or 0=No): Server active or not active. A non active server cannot be started.
-Timeout (0=None, or 3-7 seconds. Default is [5] seconds): Timeout value if the server is not answering,
-PadTime ([0=None], or (Timeout+2)-N seconds): interval of time for which a "pad" command is sent to the server if no other commands has already been sent (usually must be kept to 0),
-WantEmus (0=No or [1=Yes]): similar to WantEmus option in CCCam.cfg. If set, friends emus are also used (if the server has authorized them for the user).
-MaxHop ([0=None], or 1-N): nodes with a hop value superior to this limit are not used. A null value indicates no limits. Even if they are disabled with this rule, the concerned nodes are displayed into the list of nodes, but are not available.
-CAIDProv ([None]): list of CAID/Providers ONLY used to make requests to the server(s). Each entry may concern a whole CAID, or just only one provider for this CAID. Entries are separated using a comma character. Samples:
CAIDProv=0100,1801 : only CAIDs 0100 and 1801 will be used.
CAIDProv=0604,0100:0084,0100:006A : only CAID 0604 and CAID/Providers 0100/84,0100/6A will be used.
-NoCAIDProv ([None]): list of CAID/Providers EXCLUDED. Syntax similar to the "CAIDPRov" option. Samples:
NoCAIDProv=0604,0500 : CAIDs 0604 and 0500 won't be used.
NoCAIDProv=0100:6A,1810,0500:032100 : CAID 1810 and CAID/providers 0100/6A,0500/32100 won't be used.
-NoNodeCAID ([None]): list of Node/CAIDs excluded. Each entry may concern a whole server (i.e all nodes belonging to this server), or just only one CAID for this server (i.e. usually only one node of the server). Entries are separated using a comma character. Samples:
NoNodeCAID=0102030405060708,1A1B1C1D1E1F2021 : these 2 servers won't be used.
NoNodeCAID=0102030405060708:0100,1A1B1C1D1E1F2021:500 : CAID 0100 won't be used for the first indicated server, and CAID 0500 won't be used for the second server.
-CAIDTunnel ([None]): list of CAID tunneling entries, currently limited to Betacrypt<--->Nagra3 CAIDs. Each entries are separated by a comma, and data within an entry are separated with a colon character. Syntax for each entry :
.CAID to use within ECMs stream (mandatory),
.CAID to use when requesting the server (mandatory),
.Provider (not used; null value),
.SID concerned for the tunneling feature (optionnal). If this value is not filled or null, all the channels using the first CAID value are possibly concerned.
Samples:
CAIDTunnel=1833:1702 (all the channels)
CAIDTunnel=1833:1702:0:81,1833:1702:0:82 (channel with SID=$0081 or $0082).
-NoSID ([None]): list of SIDs not to processed. Entries are separated using a comma character. Sample:
NoSID=0001,0002,0ABC
-PrioGenRules (default is [Hop]): general rules for priority. All entries are separated by a comma. General rules always applied first, and concerned all the nodes. Currently, only the hop level and the emulator status are used. Possible values for the the first option: Hop, RHop, NHop. Possible values for the the second option: Emu, REmu, NEmu
For all of them, xxxx means rule xxxx, Rxxxx means inversed rule for it, and Nxxxx means no rule for this option.
.Hop: priority for nodes with lesser hop levels,
.Emu: priority for emulator nodes (applied after the former rule).
Here are a few samples (option values are not case sensitive):
.PrioGenRules=NHop : no priority rule concerning hop values
.PrioGenRules=REmu : emulator nodes used after non emulator nodes (but remember that the default value PrioGenRules=Hop is still applied for this sample)
.PrioGenRules=Hop,NEmu: priority for nodes with lesser hop levels, and no rules for emulator nodes.
-PrioCAIDProv ([None]): list of CAID/Providers for node priority. Syntax similar to the "CAIDPRov" option. The first CAID[/Provider] has priority over the second one, and so on; and all the CAID/Providers present into this list have priority over the other ones (i.e. those not present in the list).
Samples:
.PrioCAIDProv=0500,0100 : CAID 0500 has priority over CAID 0100, and above all other ones,
.PrioCAIDProv=0100:006A : CAID 0100, provider 006A has priority over all CAID/Providers.
Manual ECM PID selection modifies all these rules (see corresponding infos into the "Display" paragraph).




So, for each new server to add with by default values, add these 2 lines in your .ini file, modifying the concerned data with your own ones:
[Serv_MyServer]
Server=CCCam:MyServer.com:12000:0:MyUsername:MyPassword




The above sample is corresponding to this C line for a CCCam server .cfg file: 
C MyServer.com 12000 MyUsername MyPassword







Display:
-------
There are two kinds of display.







The "Monitor" window (called from the main menu), used to display general and CAID informations for the channel, and general informations for the server(s).




Double-clicking on an CAID row (i.e. ECM PID) will force the plugin to try to use this ECM PID entry. If it's not compatible for a given server, the following next compatible ECM PID entry will be used instead. It's important to note that node priorities are modified when this functionality is used: ECM PID selection becomes the first priority rule, and then only are applied all the other node priorities (i.e. general rules and CAID/provider for nodes). Change or re-select the corresponding channel will cancel the temporarily effects of the manual ECM PID selection; as for the "Cancel manual ECM PID selection" entry within the server menu.  




Double-clicking on an server will display the "Server Infos" window (see hereafter).




Right-clicking on an server will display a menu to:
-Start/Stop a server (if the server is active). Same as the "Active" option in the configuration file,
-Activate/Deactivate a server,
-Ask to retry all the possible ECMs again (if the server is started),
-Cancel the temporarily effects of the manual ECM PID selection.




The meanings for the main status of the servers are:
-"Started." : connected and logged to the server; channel not encrypted,
-"Stopped." : not connected to the server,
-"Started. Send ECM..." : started and ECM request sent to the server,
-"Started. Got DCWs." : started and positive result given back by the server,
-"Started. (None)" : started, encrypted channel but no possible decoding using this server ; either because there is no corresponding CAID/provider for this channel, or because all the possible CAI/providers requested from the server have given negative results,
"Stopped (already in use)." : not connected to the server. The same server (i.e. same IP address and same port) is already in use and connected.







The "Server Infos" window (called from the server list in the "Monitor" window) is used to display informations for all the nodes of the server. Columns inside the nodes list:
-S (for Status): indicates the status of the node. [Empty] = not available (because of the configuration restrictions -see "MaxHop" options-; or because it has been declared disconnected by the server). Furthermore, unavailable nodes are grayed. "....." = node available, but forced by the user to be ignored. " +" = node available. "**" = node available and currently in use.
-Req/Got: numbers of ECM requests sent to the node, and of DCWs received from it.
-Hop, CAID and Providers: common informations for a node.
-DCWs (ms): last time response for DCW received from the server for the node.
-Neg (ms): last time response for negative answer received from the server for the node (i.e. 'No decoding' messages). Both for DCWs and Negative time responses, there is a first latency for multiple I***** ECMs (if several ChIDs are used).
-Timeout: number of timeouts for ECM requests.
-Discon: number of disconnections (and eventual re-connections).
-Index and Node ID: identification of the node.




Right-clicking on an node will display a menu to:
-toggle its state between "to use" and "to ignore" (if the node is available).
-enable or disable the selected CAID for the selected server. This may correspond to one or several nodes for the concerned server,
-enable or disable all the CAIDs for the selected server. 
Depending of the current status for the concerned node/CAID/server, these different entries for this menu are available or not. Enable/Disable a CAID or all CAIDs are equivalent to the "NoNodeCAID" option into Hadu.ini.




In the nodes list, providers included in parenthesis (e.g. "(0000)") or CAIDs included in parenthesis, means that these providers or CAIDs can't be used.




When they are included into brackets (e.g. "[0500  123450 6789A0]") or into braces (e.g. "{0604  00000}"), the corresponding node is no more connected or excluded according to various options present in the .ini file; in these 2 last cases, the node status can't be modified (by double-clicking on it).




The meanings for the main status of the nodes are:
-[Nothing] : node can't neither be used nor having its status modified,
-"....." :  node has been its status set to "ignore" by the user,
-" +" : node can be used,
-"**" : node currently in use.




Data in the "Server Infos" window are refreshed each 4 seconds. You can force an extra refresh with the "Refresh" button.




The clipboard button serves to copy data of the window into the clipboard (text format).




At the bottom of the window, the total numbers of nodes and CAID/providers are displayed: the first number of both of them indicates the whole total number, will the second number indicates the total number of available items.







Limits:
-------
Here are the main current limits applied into the plugin:
-Maximum number of CCCam servers (active or not active): 6
-Maximum number of nodes per server : 2048
-Maximum number of providers per nodes : 16
-Maximum number of hops per node : 16 (though more than 3 or 4 is probably useless)
-Maximum number of CAID/providers entries into to "CAIDProv" and "NoCAIDProv" options : 32
-Maximum number of nodes/CAID entries into to "NoNodeCAID" option : 32
-Maximum number of CAID/CAID/provider/SIDs entries into to "CAIDTunnel" option : 32
-Maximum number of SIDs entries into to "NoSID" option : 64
-Maximum length size for server name and URL/IP address : 128
-Maximum length size for user and password: 20 for the user, 128 for the password
-Maximum number of CAID/providers entries into to "PrioCAIDProv" option : 32.




To not overload CCCam servers, it's not allowed within the plugin to have 2 active connections with the same server at the same time. Same server meaning here: same IP address and same port.

Display More

First of all ,if you are in the US ,then you need to know of local cards there,depending in which state you live or live nearby...according to lyngsat they are nagra3 cards : DirecTV 5 & EchoStar 10/11 at 110.0°W - LyngSat
you are getting signal strengths, so i imagine you have the right KU LNB/horn for these KU channels??
reading some forums ,apparently you have to eliminate or edit the TPs (transponders) that you have leaving only the ones that say CONUS ..but clear the "spotbeams" ,,so that the channels can start to enter properly..they dont say why, but a few users have recommended this..

Antenna setup - 110w exit and save
 Choose Channel Scan (not auto scan)
delete all other transpnders,
repeat this till all transponders are deleted EXCEPT transponder #1
highlight transponder #1 and push ok to scan, it will fill in all transponders direct from sat (if auto transponder is turned on)
when all done scanning hit exit and yes to save.
 repeat these steps to update all sats you have running
 now turn OFF auto transponder to reduce freezing
EXit out and watch TV
before i did this i was not even scanning half the HD channels
now i get them all and some SD channels that i never had before also
I use TP 12224 with Frequency 11250 (I try others TP's, such as 12559 etc.., but they haven't given me any new channels)
Trans=11820 H, SR 20000, DVB-S
PENTAGON HD
PENTAGON Dolby
PENTAGON
BackHaul
also a couple new channels on Trans>12020 30000 H DVB_S2

Thanks for your reply again.
Nagra 3 card where will i put that in my HTPC given that i have a DVB-S2 card that does not have a ci slot?
The big question is whether i do really need to be able to scan for channels with my dvb card and if i do how
do i go about using it. Can the card be gotten on ebay or on the net.? I am really sorry guys if i am just
full of nothing but questions.

What will be the real purpose of a Nagra 3 card in my setup, given that i do not have DSS Receiver. I am using dreamdvb, progdvb and mytheater.

On the issue of transponders, i want to be absolutely my not being able to scan for channels has anyting to do
with not having a 'card'. I will take your advice on fine tuning my transponders, i have already done so on Dreamdvb.

With regards to installing Dreamdvb i have followed your instructions to the tee except for the questions
below:

5. Download & Unzip the latest Emunation file ( for example 3.0.3.2) - I read this is no longer being used
and i was adviced to get HADU and pair it up with CCcam.....
8. Download and unzip the latest Vplug (exp.vplug 2.01.2). - Using HADU....okay.
12. Plug the power of Genpix***walker-1 as well as the USB plug in your PC. --- Using TBS 8922 DVB-S2 card will
that work too.....

Quote from cazuela

Code

Watch High Definition TV in the PC – setup with Windows XP Pro+ XP Service Pack 2 ss well as HD Video card with 256 MB (best is 512 Mb).
-------------------------------------------------------------------
1. Install DVB Dream (Note: Do not run it!)
2. Download & Install vcredist_x86.exe from ://www.microsoft.com
3. Download & Install Mpeg2 codecs (Cyberlink DTV+Interviedeo codecs ONLY)
4. Download, unzip and install CoreAVC v 1.6.5.0 2008
5. Download & Unzip the latest Emunation file ( for example 3.0.3.2)
6. In this folder Copy 2 files Microsoft Visual C++2005SP1 and pthreadVC2.dll and paste them into DVB Dream in C: drive.
7. From Emunation folder copy the content of Plugins folder and paste them
into pip00 folder (located in Plugins folder).
8. Download and unzip the latest Vplug (exp.vplug 2.01.2).
9. Copy the content of vplug folder you just opened and paste it into pipo00 and close it.
10. In Plugins folder then click on copy_all batch file.(This action will copy the whole content of the pip00 folder in all pipo folders).
11. Close Plugins and DvbDream folder.
12. Plug the power of Genpix***walker-1 as well as the USB plug in your PC.
13. Follow Driver installation procedure.
14. Check for gp1.0.1 file in Device folder located in DDream folder in drive C:.
15. Reset your PC by turning it…..OFF and restart it.
16.Open DVB Dream program and follow instruction for your favor setup.
a. Click Options tab click on Video and select Cyberlink DTV codec for video and Interviedeo codecs for audio. On Renders select Generic Video Render and Default Direct Sound Device, as well as CoreAVC v1.6.5.0 2008 for HD.
b. In Diseqc setup your switch as well as satellite,LNB,frequency,port etc.
c. Click on Channels tab in Manual setup and make your Transponder choices for scan.
17. Scan all possible channels from your satellite.

Display More

Something has just come to my attention :Forum Gateway - Powered by DnP Firewall is a good place to start !!
Now, as far as n3 cards,,,in your case (being in the states) you have 3 options as far as I can tell :

1: you subscribe to whichever platform you wish to view(which only partially covers 1 sat )then go about a ci cam.
2: subscribe to a private server in which the both parties agree to help one another ( sharing)
3: subscribe to ( in the states its called:make a donation to ) a scumbag payserver.
*In Europe we abhor these servers as we don´t understand why pay a server which uses others´ cards to benefit economically
when it is possible to simply share each other´s cards.* At least this is the common thinking.
After saying all of this,,, you´ve got PM :43_002:

Any information provided on this site is not guaranteed in any way. Some articles may discuss topics that are illegal, so this information is provided for educational purposes only, your use of the content, downloads and files, or any part thereof, is made solely at your own risk and responsibility. Viewing Pay TV without a valid subscription is illegal. !! Linuxsat-Support.com cannot be held responsible for the content of any information stored or posted on this forum.