How to play video on your TomTom navigation device

After my good old TomTom Go 700 passed away I got a new TomTom Go 740 Live and soon found out it’s really easy to play video on a TomTom navigation device. This way you can use your navigation as an in-car entertainment centre. With TomPlayer you are able to watch full screen video’s in AVI (divx or xvid) or MPEG video and listen to mp3 or ogg audio files.

The documentation on tomplayer.net can be a bit confusing and installation is not the same for all TomTom models. In this post I will explain how to install and configure TomPlayer on an external MicroSD memory card. This method will work for models Go 740/750/930 Live and will probably work for a lot of other models. At the end I will explain another configuration which might work for your model.

Continue reading →

2000-2009 Decade Mashup Mix

The best hits from the last decade in a three hour mashup mix! Dutch master of mashups Martin Pieters mixed this masterpiece for 538 radio and it’s truly great. Enjoy!

Continue reading →

Easy embedding: WordPress oEmbed plugin

oEmbed is a format for allowing an embedded representation of a URL on third party sites. The simple API allows a website to display embedded content (such as photos or videos) when a user posts a link to that resource, without having to parse the resource directly. Embedding made easy. More information about oEmbed can be found on the oEmbed website.

Thanks to Jan-Willem Eshuis oEmbed is now available for WordPress! The oEmbedder plugin makes it easy to use oEmbed services from websites like Flickr, Youtube, Qik, Revision3 and Vimeo into your weblog. I’ve tested the WP-oEmbed plugin on this blog and we will probably use it for the NOS weblogs soon.

Continue reading →

Modern Warfare 2 console enabler

mw21

Only one week after “Call of Duty: Modern Warfare 2″ went on sale, some PC players appear to have found a workaround solution to their dissatisfaction with Infinity Ward’s new IWNet system. When Infinity Ward announced that it would forgo dedicated servers for the new matchmaking setup similar to what console players experience, a large number of gamers signed a petition expressing their discontent. Now, some of those code-savvy complainers have reportedly recreated a dedicated server experience by unlocking the game’s developer console.

Well, you can’t keep a good PC gamer down. Certain cracks already allow some online play, and now the console has been enabled, allowing players to kick, change POV and FOV, and presumably do most of the stuff Infinity Ward decided had to stay in the cookie jar.

DOWNLOAD LINK for the MW2 Unleahsed console enabler tool (use at your own risk) (USENET)

Continue reading →

Yikes! The ieframe.dll dns error and how to solve it

Recently two seperate users mailed me about not being able to visit my website. They both reported blank screens or browser windows automatically closing.  One of them was able to tell me he was prompted with the following errors:

DUTCH ENGLISH
Rick says (5:53 PM):
“De website kan niet worden geopend”
Rick says (5:54 PM):
“de bewerking is afgebroken”
Rick says (5:55 PM):
onderin staat: wachten op res//ieframe.dll/dnserror.htm
Rick says (5:53 PM):
“This page can not be viewed”
Rick says (5:54 PM):
“process stopped”
Rick says (5:55 PM):
in the bottom bar it says: waiting for res//ieframe.dll/dnserror.htm

This is not an error generated by kaisersblog.com or any other website! These problems occur on the client (your local machine) side. Ieframe.dll errors are fairly varied and really depend on the cause of the problem. A few of the more common ieframe.dll related errors are shown here:

  • “Res://ieframe.dll/dnserror.htm#”
  • “File Not Found C:\WINDOWS\SYSTEM32\IEFRAME.DLL”

Most ieframe.dll “not found” or “missing” type of errors occur when using Internet Explorer 7 or while using Visual Basic 6. The “Res://ieframe.dll/dnserror.htm” and related messages are much more common and appear in the Internet Explorer 7 browser window itself.

Cause of Ieframe.dll Errors

The ieframe.dll DLL file is related to Internet Explorer 7. In many cases, the installation of Internet Explorer 7 causes ieframe.dll errors to appear. Other causes include viruses, certain Windows Updates, incorrect firewall settings, outdated security software applications, and more.

Solution

Important Note: Do not, under any circumstances, download the ieframe.dll DLL file individually from any “DLL download site.” There are many reasons that downloading DLLs from these sites are never a good idea.

You do not need to follow every step in this list. Just start with the first one and continue until the problem is solved:

  1. Restart your computer unless you’ve already done so. The ieframe.dll error might be a fluke and a simple restart could clear it up completely.
  2. Install the latest version of Internet Explorer. No matter if you’re missing ieframe.dll or if you’re receiving a browser error message about it, reinstalling or updating to the latest version of Internet Explorer has resolved many user’s issues with ieframe.dll.
  3. Using Visual Basic 6? If so, change the reference for Microsoft Internet Controls from the existing ieframe.dll to shdocvw.ocx. Save your project and then reopen it.
  4. Restart your router, switch, cable/DSL modem and anything else that’s used to communicate to the Internet or other computers on your network. There may be an issue in one of these pieces of hardware that a simple restart could solve.
  5. Scan your entire computer for viruses. Sometimes, the ieframe.dll error will show up when your computer is infected with certain kinds of viruses. Use your antivirus software to do a complete system scan for virus infections.
  6. Disable Windows Firewall in Windows XP if you have another firewall installed. Running two firewall applications at the same time can cause problems so if you have a firewall program installed like ZoneAlarm, Norton Personal Firewall, Comodo Firewall, etc., then you should not be running Windows’s built-in firewall simultaneously. Note: Even if you’re positive that the Windows firewall is disabled, check again. Some Microsoft security updates have been known to re-enable the firewall automatically even if you have an existing firewall enabled in another security software program.
  7. Update all non-Microsoft firewall and other security software on your computer. Certain security updates fromMicrosoft have been known to cause issues with security software from other vendors that those vendors are responsible for resolving. Check their websites for updates or service packs and install any that are available. Note: If you’re already running a fully updated version of your security software, try uninstalling and then reinstalling the software instead. A clean installation may stop that nagging ieframe.dll error message.
  8. Install any available Windows updates. It is true that some previous updates from Microsoft may actually cause some ieframe.dll errors, but installing more recent updates, especially those to the Windows Update software itself, may help resolve the problem.
  9. Clear the temporary Internet files in Internet Explorer 7. Some ieframe.dll issues may have to do with problems accessing existing temporary Internet files.
  10. Increase the frequency that Internet Explorer 7 checks for new versions of web pages. If the default setting is too infrequent and there are issues with certain pages, you may see ieframe.dll and related errors.
  11. Disable Internet Explorer 7 add-ons one by one. One of your installed add-ons might be causing the ieframe.dll issue. Selectively disabling them will show you which one, if any, is causing problems.
  12. Set Internet Explorer 7 security options back to their default levels. Some programs, even some updates from Microsoft, will sometimes make automatic changes to your Internet Explorer 7 security settings.Incorrect or overprotective security settings can sometimes cause ieframe.dll issues. Returning these settings to their default levels may correct your issue.
  13. Move the IE7 Temporary Internet Files Folder to its Default Location in Windows XP. If the Temporary Internet Files folder in Internet Explorer 7 has been moved from its original location, plus both Protected Mode and the Phishing Filter are enabled, the ieframe.dll error will occur.
  14. Disable the Phishing Filter in Internet Explorer 7. This isn’t a great long term solution if you don’t have another phishing filter installed, but disabling IE7′s phishing filter has been known to correct ieframe.dll issues in some situations.
  15. Disable Protected Mode in Internet Explorer 7. The Protected Mode feature in Internet Explorer 7 can, in some very specific situations, be involved in generating an ieframe.dll error message.

War on Embedding

It has been all over  the news; the Dutch news, at least: you have to pay to embed video in your website.

Righto……..

The BUMA/STEMRA (abbreviated BS, which is by coincidence also the abbreviation for bullshit) announced some new rules yesterday during their press conference for embedding videos from online media streamer sites (youtube, dailymotion, whatever). starting from 2010, EVERYBODY must pay 30 euros per year for EVERY clip that you embed from youtube; if the embedded video falls under the copyright list of bullshit/stemshit (to be known: 17k musicus in the Netherlands and 1,2 mil worldwide –source: SP!TS).

SP!TS - Youtube-tax for everybody

Here’s a screenshot of today’s SP!TS Newspaper where this news is covered.

The idea is that the BS will (if not already) develop a script/robot/crawler to go, multiply and overpopulate the internet with one mission: to index where on internet (copyrighted) videos are being embedded. Those bots will call home. For those who doesn’t have the permission (= did not pay) to embed the videos, are getting a warning letter to take off the embedded clip. If not? they will get the invoice (the Joel Tannenbaum-RIAA story is a similar story — go google).

This guy from twitter (@coenjacobs) developed the Block Buma Crawler WordPress plugin, and I quote:

“This plugin is capable of keeping computers outside of your WordPress installation, that are blacklisted via this plugin. You can download the Block Buma Crawler plugin right now, version 0.1 is available. Drop the folder that’s inside the download in your /wp-content/plugins/-folder, activate the plugin and enjoy!”

–source: http://coenjacobs.net/blog/steps-blocking-buma-crawlers-wordpress

Furthermore…

Alongside with @coenjacobs, @madbello covering a good tutorial to block BS’s IP address before they can crawl your site. Read the steps in his blog: http://madbello.nl/?p=6997 (in Dutch). The red lines is the following: block the IP belongs to BS by using .htaccess file in your website. If you are using wordpress and not sure what to do, you would be way better off using WP-Ban plugin.

From the comments in madbello’s blog, the suggested IP range is 213.208.242.160 – 213.208.242.167  (.160 and .167 are included!)

UPDATE – THE WAR HAS ENDED AND WE HAVE PREVAILED!!!

I must admit I was a bit late with this story as it has been hot news here in the Netherlands for a few days now. But, not nearly an hour after publishing this article BUMA/STEMRA has thrown in their towel and risen the white flag. They have stopped all active searches on embedded music and will not continue their hunt untill further notice. (Official statement / translation)Since the dutch government has also spoken against BUMA/STEMRA tactics we probably won’t hear from them on this subject for a while. Bye Bye zwaai zwaai!

Working on my social repository

Unlike a few years ago I don’t bother registering for websites or social services. Over these years I have registered for numerous social media websites, applications and services. The problem is I only use a very small percentage of them. I really like my Youtube and Flickr accounts but normally I find it to much trouble to keep track of all my social media profiles and updates. Therefore I wanted to do something about this problem, not only do I want my social networks to grow I also want to use them more actively. So I had to automate some stuff, for me as a user and for you as a follower.

First the ‘ easy updating’  part. I found a great service that does all the hard work for me, Pixelpipe. This great service allows you to upload messages and multimedia to a lot of services. More than 120 services as we speak! It works very simple, before you begin you have to add your profiles and services to PixelPipe and add some tags to them (eg. Photo, Family, Blog, FTP). After this first step which takes a bit longer to setup it is very easy to post to multiple destinations using the tags you have entered before. So when I want my family to see my newly uploaded photo I send my picture with the @family tag and Pixelpipe knows where to send it. Another big advantage of PixelPipe are the numerous possibilities for uploading your content, this can be done via e-mail, mobile phones, Firefox plugin, Picasa, Windows context menu plugins, sms/mms or the website itself.

So after making it a bit easier for me to post content to my social networks I want my networks to grow and be able to follow them easily. Here’s where my new lifestream comes in. This lifestream will be an automatically updated stream of all (well, at least most of) my online social activities. I currently have updates installed for Youtube, Twitter, Flickr, Delicious, Wakoopa, LinkedIn, Blip.fm and Hyves. My lifestream still needs a lot of tweaking before it’s finished but is working good enough for going public with. Be sure to add it to your favorites because I will be adding more social services and functionality soon! One of which will be a new website header showing generated polaroids from images found on my social accounts.

RSS feed for this blog Youtube Twitter Hyves Delicious
Flickr Picasa Netvibes Digg LinkedIn Yahoo! MySpace Facebook Reddit Blog

Picture Quality on BBC HD: a response

bbc-hd-television-channelOn the 5th of August BBC’s new transmission encoders were taken into operation. After some questions from viewers they have decided to respond on their Internet blog. The blogpost is actually a response from BBC’s head of BBC HD Danielle Nagler to an anonymous author. In my opinion this article gives a very interesting insight in the kitchen of world’s biggest high definition br0adcaster:

Hello Everyone

I thought that you might like to see the detailed response which I have sent to someone who contacted me regarding the picture quality issues which are under discussion here:

“…Your complaint refers to the introduction of the new transmission encoders for BBC HD which were introduced into operations on Wednesday 5th August. There was an extensive process of assessment in advance of the selection of new encoders for the BBC HD service, using both objective and subjective criteria. The encoders which were chosen then went through further testing in advance of operational use, not only for picture quality but for compatibility with the Sky and Freesat platforms and their ability to deliver other services such as subtitling and surround sound successfully.

The new encoders were intended to help us in handling the wide range of material which the BBC broadcasts in HD, and to help to improve the picture quality of some of our most challenging programmes. These may combine progressive and interlaced shooting or where the BBC has limited control over some aspects of the broadcast chain. I believe that the new encoders have achieved this in relation to programmes such as the series of BBC Proms broadcast, Gardeners’ World, Rick Stein’s Mediterranean Escapes and the recent Athletics World Championships, for which our coverage using the host broadcaster feed was as good as and sometimes better than other broadcasters covering the same event. However we of course continue to assess coder settings against the wide range of material which they have to handle to determine the best settings on an ongoing basis.

Following the introduction of the new encoders, there were some issues around the handling of some pictures – primarily mixes and fades – which we acknowledged through the BBC HD blog on picture quality almost immediately. We have worked with our encoder supplier to address these issues in the long-term, and also put in place interim changes to minimise the difficulties. That the encoder change should generate problems for viewers watching BBC HD content is of course a matter for regret, but I do not believe that this was the result of errors in the preparation process.

You have also highlighted the issue of the bit-rate at which BBC HD broadcasts, and the changes to this over time. I do not believe that the problems that arose following the introduction of the new encoders had anything to do with the broadcast bit-rate, even though they coincided, as you have rightly identified, with a reduction in bit-rate for the channel.

One of the central issues in selecting new encoders for BBC HD was to deliver pictures at the same or improved quality while allowing a reduction in the channel bit-rate. As MPEG 4 coders have evolved, the relationship between bit-rate and picture quality has also shifted. This is not an issue that is specific to BBC HD, or to the encoders that we have selected.

The BBC has an absolute responsibility to use bandwidth efficiently – whether on digital terrestrial muxes or on satellite. Bandwidth is not unlimited, and on UK-footprint transponders the demand for capacity is very high. The current bit-rates were selected through a process which directly evaluated quality on the new and old encoders, using a wide range of programme material and both subjective and objective assessments.

Bit-rate is not the only factor affecting picture quality and a higher bit-rate will not automatically deliver higher picture quality.

HD is still an evolving production technology. A variety of production techniques are – in my view quite rightly – deployed as experimentation continues to explore what HD can delivery creatively.

As in standard definition, it is also important that HD delivers a range of “looks” for producers, appropriate to the nature of the subject matter. I do not prescribe a single standard for HD work for the BBC. Decisions regarding frame rate and progressive versus interlaced styles are the responsibility of individual producers. These choices do not impact on quality provided that the camera is set up properly and the shutter speed set correctly, issues on which the BBC HD team provides ongoing advice and guidance. As the discussion on the BBC HD blog suggests, there is a range of views around these issues, and the degradation or quality they may bring to HD pictures. It is worth noting that 25 frames progressive mode in fact has more resolution than a 25 frame interlace image, and is used by the majority of drama, documentary and natural history programmes to great effect.

While very clear, sharp images have become closely associated with HD, it is important not to confuse “sharpness” with resolution. The use of electronic sharpening on standard definition pictures can make images clearer but does not increase the amount of information in the picture, one of the defining features of HD.

Electronic sharpening is not a characteristic which BBC HD encourages since we prefer images to look more natural, and to allow directors to offer contrasting focus in order to highlight the key features in a scene. Indeed, some of our dramas are now using the latest large image format cameras.These cameras use an image sensor about the same physical size as a 35mm film frame that gives the image a very shallow depth of field. This will put all but the key subject out of focus and allows a director to use focus as a story telling tool.

HD picture quality is not purely about a crispness of image, but about a richness of image which comes from the amount of detailed information included.

Within the BBC HD team we work consistently to explore new HD technology with a particular view to enhancing picture quality across the range of programme projects with which we are involved. Filming in certain environments or using small cameras remains challenging, and where it is not possible to deliver HD pictures to the standards we set, we limit the use of lower quality images to a maximum of 25% of an individual title.

Finally, you raise the issue of surround sound and the number of programmes broadcast which offer a 5.1 sound mix. Wherever possible we buy series and films with surround sound tracks, and try to ensure that sound is captured in this format for outside events. But 5.1 sound is not always available, and a genuine surround sound mix can add substantially to production costs in HD at a time when we are concentrating the resources available to increase the total volume of programmes made in HD. At present we do not routinely “up-mix” programmes from stereo to surround.

I can assure you that picture quality is a very important part of the work that we are doing in BBC HD. We clearly have different views on the picture quality that is delivered and the factors that contribute to it, but I do believe that we share a perspective that the quality of images is central to delivery of HD television.

I want to add that the BBC HD blog is a very important discussion and communications forum for us, but as you have clearly observed we don’t respond to every single comment raised on it. We do take on board all the views expressed, and look seriously at substantive issues that are highlighted, whether they attract one comment or many.

I am sorry that in this case you feel that your original contribution did not receive the attention which you believed that it should have done.”

Danielle Nagler Danielle Nagler | Danielle Nagler is Head of BBC HD, BBC Vision


IE7 CSS fixes, The most common css solutions for Internet Explorer 7

ie_bugs

The <!–[if IE]> Tag

Problem: Various sizes, margins and padding attributes can display differently in Internet Explorer, this coded snippet can help you sort out these problems.

Add this code with your required settings underneith your pages <style> or external style link:

<!–[if IE]>
<style>
.item {
margin: 5px;
padding: 10px;
}
</style>
<![EndIf]–>

These setting will now only be loaded when your page is viewed in Internet Explorer. I often use this setting to tweak areas of my layout that do not quite display the same as in other browsers.

Margin Auto Centering

Problem: When centering div tags via either the margin-left: auto; or margin-right: auto; settings, this will not work in Internet explorer unless you add the following to your style sheet for the html body:

html, body {
text-align: center;
}

Don’t forget to now add this to your paragraphs and headings as the above setting will now cause these to also center.

p {text-align: left;}

Minimum height bug

Problem: When trying to create a DIV tag and the height will not go below about 12px

Simply add the following attribute to the DIV tag

{line-height: 0px;}

If this does not work try adding the line-height attribute to a <p> paragraph tag within the <div> tag itself.

Your final code should resemble one of the following:

<div style=”line-height: 0px; height: 5px;”></div>

<div style=”height: 5px;”><p style=”line-height: 0px;”></p></div>

Margins appear larger in Internet Explorer

Problem: Setting the margin attribute for any CSS element in Internet Explorer it will often appear either double the size or with added width, which can seriously disrupt detailed layouts.

Simply use the {display: inline;} attribute on the tag containing your margin setting.

Your final code should resemble the following:

<div style=”display: inline; margin-left: 5px;”></div>

CSS Light box Adobe Flash fix

Problem: The CSS Light box script will not appear on top of a Flash movie, this disrupts the actual function of the script.

Add the following setting(s) to the Flash HTML code:

<param name=”wmode” value=”transparent”/>

Also add this to the <embed> tag

wmode=”transparent”

Be sure to add both of these settings for this to work properly, your final flash code should look similar to this:

<param name="allowScriptAccess" value="sameDomain" /><strong><param name="wmode" value="transparent" /></strong><param name="movie" value=" movie.swf" /><param name="quality" value="high" /><param name="bgcolor" value="#000000" /><embed src=" movie.swf" quality="high" bgcolor="#000000" <strong>wmode="transparent"</strong> width="232" height="218" name=" movie" align="middle" allowScriptAccess="sameDomain" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer" /> </object>

Hadu CCCam client Plugin for windows

While I’m testing my new satellite setup for a HTPC that has yet to be build I found a really usefull DVB plugin everybody should hear about. Finally a CCCam client for windows is available. First tests were very succesfull for me. Version Beta 0.1.0.0 was released June 23, 2009 this was a initial Beta Test release. The current version is 0.116. Find latest release and changelogs here.

Download Hadu 0.116

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 (eg. ProgDVB) 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 affected 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.
    It is also possible to use Hadu with the recording service of DVBViewer, if you install first the Wrapper for recording service of Pikachu. Caution : currently, this option might lead to unstable behaviors of DVBViewer (especially when closing this software).
  • SkyView: /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.

Server Configuration (Hadu.ini):
—————–

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

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:Pass word

Sample: Server=CCCam:MyServer.com:12000:0:MyUsername:MyPas sword, 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] or 0): 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). Even if WantEmus is not set, the concerned nodes are displayed into the list of nodes, but are not available.
  • MaxHop ([0=None], or 1-N): if WantEmus is set, nodes with a hop value superior to this limit are not used. A null value indicates no limits.
  • 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.

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 numbers of CAID/providers entries into to “CAIDProv” and “NoCAIDProv” options : 32
  • Maximum length size for user and password: 20 for the user, 128 for the password.