Network login script for Windows XP Home

I just needed a script to log in on a Windows 2003 Server from Windows XP Home. Of course you can enter your password each time you need to access the shares – or you could just drop this little script in your Startup folder (call it ‘network_login.vbs’ for example).


{codecitation class="brush:vb"}’ VBScript to map a network drive. And provide a message box
‘ Author Berend Dekens
‘ Based on code from Guy Thomas
‘ —————————————————————–

Option Explicit
Dim objNetwork
Dim strDriveLetter, strRemotePath, bSaveMapping, strUserName, strPassword
strDriveLetter = "Z:"
strRemotePath = "\\\sharename"
bSaveMapping = true
strUserName = "yourname"
strPassword = "mysecretpassword"
‘ Purpose of the script to create a network object. (objNetwork)
‘ Then to apply the MapNetworkDrive method. Result Z: drive
Set objNetwork = CreateObject("WScript.Network")
objNetwork.MapNetworkDrive strDriveLetter, strRemotePath, bSaveMapping, strUsername, strPassword
‘ Extra code just to add a message box
WScript.Echo "The networkdrive "& strDriveLetter & " is now available"
‘ End of MapNetworkDrive Example Logon Script. {/codecitation}

General blog entries

KBlogger moved to KDE 4.3

And yet another epic fail for KBlogger, the new blogging tool that was supposed to be in KDE 4.0. After KDE-PIM was not ready for the 4.0 launch, it was postponed to KDE 4.1 – understandable but as anyone running a blog and a PC using KDE4 knows, we don’t have any decent blogging tool on linux.

After an early alpha (which was a step in the right direction) is became very quiet around KBlogger. So when KDE 4.1 was released I was surprised to see the lack of info about the new blogging tool.

When I found KBlogger on the KDE 4.2 release schedule I sighed – another half year to wait on a decent replacement for Windows Live Writer (which is still – in my opinion – one of the best blogging tool out there, even when used in VirtualBox).

Now, at the dawn of 2009 and the coming of KDE 4.2 I found it weird that the beta of 4.2 lacked a preview of KBlogger.

I just found these mail conversations on the KDE mailing list pushing KBlogger to KDE 4.3…. which is supposed to come out end 2009. Once again a huge let down for the KDE fans.

Despite the statements that KDE 4 is feature complete it keeps lacking vital programs: KDE PIM has a screwed up Kitchsync support (which in itself is half broken if you ask me), power management just arrived in 4.2 (Powerdevil) and KBlogger is still not here (even though its core component KBlog – a WYSIWYG editor – is working pretty well for some time now). I am still using KDE 4.x but so far the thrill has become quiet the waiting game. Yay for open source I suppose…

General blog entries

Configuring custom remote buttons for XBMC

When you are the proud owner of a MCE remote, you are set for use with XBMC. However, if you are using a custom remote (like the one that came with my Thermaltake DH-101 MediaLab kit) – you might wonder how you are going to get all the buttons to work. Short answer: you won’t by using the Lircmap.xml file.

I configured my remote using Lircmap.xml like it stated on the site and it worked fine. I modified the bit in both Lircmap.xml and Keymap.xml until the point came where you want to add buttons that are not on the standard remote.

I figured, I could just add another button to the section of Keymap.xml – in my case XBMC.EjectTray() but although XBMC started fine, you wind up with this:

ERROR: Remote Translator: Can't find button eject

This is because XBMC uses a fixed map to determine which buttons are valid. Instead of simply adding buttons by name, they have identifiers for each button so adding your own buttons won’t work.

At this point, you have 2 options:

First, if you only have a few buttons you could recycle unused buttons. Open up and look for the function called ‘CButtonTranslator::TranslateRemoteString(const char *szButton)’; ctrl+f it if you can’t find it, right now it is at line 777. See the lines following it? Those are the valid button names. For example: ‘if (strButton.Equals(“left”)) wButtonCode = XINPUT_IR_REMOTE_LEFT;’ – in this line the name ‘left’ is specified. Look for buttons you are not using and override their action in Keymap.xml.

The second option is a bit trickier. First, create ‘advancedsettings.xml’ in de userdata folder and put ‘true’ inside the file. Restart XBMC and start monitoring the XBMC log (by default under /var/tmp/xbmc-user.log’).

Start pressing all remote buttons and note which obc code they produce. Add all these codes to Keymap.xml under the tag – create it if you have to. A valid piece would look like:


Note that I replaced the tag start and endings with ‘[‘ and ‘]’ because my site seems to eat the correct ones.

Good luck taming XBMC and if you can’t figure out how to read the source file with the button names, you can look at this wiki article from the XBMC website. Note that it is usually out of date.

Update: the OBC codes only worked when I was using my universal remote with the XBox setting – unfortunately, this does not seem to work for specific remotes. Drat.

General blog entries

Download videos from Crunchyroll

With Dattebayo dropping Naruto Shippuden because CrunchyRoll will legaly release just hours after TV Tokyo airs, I decided it was time to write some magic to download the videos from Crunchroll. You see, I have a HTPC in my living room and I don’t really fancy watching Naruto in a browser when the time comes.

Disclaimer: this will NOT allow you to download paid shows without paying. Personal use only, don’t be an **** and distribute the video.

This will only work in FireFox – also, it will only work on the H264 videos. Put the following code in a file and install it into GreaseMonkey:


// ==UserScript== // @name           Provide download link on Crunchroll videos // @namespace // @description    This script extracts the file name from the player code to allow the user to download it. // @include*/*.html?h264=1 // ==/UserScript== // Get the div holding the player object var div = document.getElementById('showmedia_left_col_new'); // Grab the script in that div which constructs the player var script = div.getElementsByTagName('script')[0]; // Extract the configuration array from the script content var config_str = /"config":"([^"]+)"/.exec(script.innerHTML); // Decode the URI encoding which is used on the config parameter, we now have some XML structure var html = decodeURI(config_str[1]); // Grab the file tag from the XML content var filename = unescape(/([^<]+)/.exec(html)[1]);  // Find the message box on this page var msgbox = document.getElementById('message_box'); // Remove the style which hides it msgbox.setAttribute('style',''); // Get all divs inside the message box var divs = msgbox.getElementsByTagName('div'); // Set this to the div which should hold the message var msgdiv = null; // Loop through all found children to find the right one, with a class name 'message-list' for(i = 0; i < divs.length; i++) { 	if(divs[i].className == 'message-list') { 		msgdiv = divs[i]; 		break; 	} }

Compiling Courier 0.60.0 into RPMs for CentOS 5.2

In this article I will explain how to build RPM packages from the tar.gz packages on the Courier site in order to install Courier and/or its components using the RPM based installer in CentOS.

Server crashes always come when you least expect them. My trusty server just came down with a bad case of broken SATA controllers (don’t know how to cure that). Of course, the socket A cpu (Athlon 2600XP) motherboard is long out of fashion and so we wind up with the purchase of a new server (technically an HTPC but I’ll post something about that later on).

One of the key packages I use for years is Courier MTA. This software is supported fine by Gentoo but because the number of servers that I need to maintain is steadily growing, the drive for cutting edge kernels and software is fading as upgrading Gentoo systems can be a time consuming process.

So in the reinstall I decided to drop the mail, web and ftp services into a virtual CentOS machine so I could move the server to a different computer in case of the physical host failing.

The first thing that became obvious was the lack of Courier RPM’s out there, simply because the Courier package from the site can be converted into RPM’s with ease. If you are reading this then you probably have not compiled packages before and you need some help.

Disclaimer: I am using a setup which uses MySQL based authentication so I will remove the other database packages as soon as I am done – if you need those, be sure to omit those commands.

Start out by installing ‘rpmbuild’ as we will use it to build the packages:

yum install rpm-build

Next, get the latest source tarball from here.

As a normal user (running as root will give you an error so don’t bother) run the following:

rpmbuild –ta courier-0.60.0.tar.bz2

In my case I got this error telling me I don’t have enough permissions to write where the rpmbuild tool wants to put its files:

error: Failed to rename /usr/src/redhat/SPECS/rpm-spec.uykL0j to /usr/src/redhat/SPECS/rpm-spec.uykL0j: Permission denied: No such file or directory

This is a bother because Courier requires you to be non-root and rpmbuild requires you to be root. I solved this by temporarily changing the /usr/src/redhat owner to be me:

chown berend:users /usr/src/redhat –R

Running rpmbuild again now shows us a list of missing dependencies, in my case I had to install:

yum install expect libtool-ltdl-devel gdbm-devel pam-devel gnutls-devel mgetty-sendfax pcre-devel openssl-perl gamin-devel

One of the missing requirements is the ‘/usr/lib/ltdl.h’file – this is part of the libtool-ntdl-devel package. Another is ‘/usr/include/fam.h’ which is provided by gamin-devel.

The primary missing package however, is courier-authlib-devel. We can solve this by going back to the download page and downloading the courier-authlib tarball. After grabbing it, run rpmbuild on it:

rpmbuild –ta courier-authlib-0.61.1.tar.bz2

On my system the following was required to be able to build the RPM:

yum install libtool libtool-ltdl-devel openldap-devel mysql-devel zlib-devel postgresql-devel gcc-c++ redhat-rpm-config

Note that if you skipped installing the dependencies for courier itself, some of those packages are needed for courier-authlib as well.

After calling rpmbuild again on the courier-authlib tarball, the compiler should kick in and the build will complete on its own. After the build is complete, install courier-authlib-devel to be able to build Courier itself (you can later remove this if you don’t need it), you need to run this as root:

rpm –i /usr/src/redhat/RPMS/i386/courier-authlib-0.61.1-1.i386.rpm rpm –i /usr/src/redhat/RPMS/i386/courier-authlib-devel-0.61.1-1.i386.rpm

If did everything right, calling rpmbuild on the courier tarball will now fire up the compiler on courier itself, resulting in a neat pile of RPMs in ‘/usr/src/redhat/RPMS’ – most of which have self-explanatory names or are dependencies of each other.

Before installing Courier, lets clean up the mess we had to make to get here, run this as root again:

yum remove libtool libtool-ltdl-devel openldap-devel mysql-devel zlib-devel postgresql-devel gcc-c++ redhat-rpm-config gdbm-devel pam-devel gnutls-devel mgetty-sendfax pcre-devel openssl-perl gamin-devel courier-authlib-devel  chown root:root /usr/src/redhat –R

Note that we omit ‘expect’ from the remove command as it is needed by courier and its packages.

And there you have it, a complete guide to building your own Courier RPM packages on CentOS 5.2. All that is left is to actually install the RPM’s and set up Courier but that is beyond this little howto.