I’m running Thunderbird 2 under Ubuntu Feisty Fawn (7.04) on the AMD64 architecture, and could not find a pre-compiled version of this that worked. So, I decided to give it a shot. It was pretty easy, and the result is a plug-in that works with the AMD64 version of Thunderbird! Since I had trouble finding it, I thought I would share it.

Since I have just started using it, I haven’t wrung it out, or tested all the options. Use at your own risk, etc.

You can download the plug-in here. Happy storming!

In the process of reconfiguring Thunderbird, I believe I may have found out how to share the address book across operating systems. The file ~/.thunderbird/default.[something]/prefs.js has a listing of all the preferences and settings. I modified this file to change the location of my mail files, and there is a setting there for an address book (which isn’t shown in the configuration dialog – after all, it is 0.7.3…) I’ll play with that later – right now I’m just elated to have Apache and MySQL working again.

MySQL was more complicated, but I was eventually able to get it working as well. I created the directory “D:\mysql\data” for the data, then configured /etc/my.cnf under Linux to look at “/mnt/drive_d/mysql/data”. I kept getting “Could not connect to server using socket /var/lib/mysql/mysql.sock”. After some digging, it appeared to be a permissions problem. All the documentation said that the default socket was /tmp/mysql.sock, so I changed my.cnf to point there instead, restarted mysqld, and it worked! So, I have no idea what a Unix socket it, but I know that now I have one!

I was also able to get DVDs playing using xine, compiling it myself, and using libdvdcss, I can even watch commercial DVDs. I’m really impressed with xine – it handles all kinds of media out of the box, including DivX and up to version 8 of WMV files. You can add codecs to it as well, to support almost anything you want to do from an audio or video perspective. Compiling the player took around 20 minutes, and compiling the front end took another 5. And, it was simple – download the .tar.gz file, do “tar xvfz [name].tar.gz”, “cd [name]“, “./configure”, “make install”. The “./configure” script is the key in the whole process – it looks at what you have installed, and creates make files that will work with your compiler.

Everything started going south, though, when I started having freezes. Eventually, I got to where I could not boot without a kernel panic, and then boot errors (which I detailed in this e-mail to the WBEL user’s list. Encouraged by my success over the past month, I decided to return to WBEL – it’s supposed to be more stable than FC2, and I bet that I can get ndiswrapper, the dual-booting web server, the common e-mail, and maybe even some other stuff working again.

The wireless network card still wasn’t recognized (phooey). I did some more searching, armed with the knowledge that I have an adm8211 chipset. One of the first hits under Google’s Linux search for “adm8211″ pointed me to a project called NDISwrapper. This is a “wrapper” that uses the vendor’s Windows DLL file, and converts the hooks from Windows to Linux. Doing this, this driver can (in theory) support most any network card, especially those that aren’t in the Linux Hardware Compatibility List (HCL). I downloaded it, compiled it, and followed the directions to install my driver under it. I still wasn’t able to create a connection, but on a hunch, I restarted the computer. NDISwrapper is also a kernel module, and I know that often those are only read at startup. Once the computer was restarted, I was able to create a connection, and now my network card works! YEA!!! (And it was only one night’s worth of work – much better.)

Now that I have networking working under both operating systems, I plan to try to get four things working the same, whether I’m booted to WXP or Linux – E-mail (using Mozilla Thunderbird), PHP (using Apache on Linux, IIS on WXP), MySQL (using the exact same version on both), and a web server that uses the same html root directory (again, Apache on Linux, IIS on WXP). If I didn’t already have IIS up, running, and configured under WXP, I’d probably just do Apache on both, but this will be interesting – it should work, as I don’t have many creative permission rules.