WAN Load Balancing

We ran into an issue at work where we needed faster Internet (or more bandwidth,)…  The prices for our current ISP’s were higher than we had hoped for faster Internet, but we would like fail over as well as additional load balancing.  With teachers and students depending on the Internet so much we cannot afford not to have the Internet working well.  Our current provider’s downtime was unrealistically low (single digit hours a year) and we were VERY happy with the service.  Increasing our speed with that provider was not very cost beneficial compared to other providers.  So we started considering load balancing/fail-over with a second or third provider.

We investigated several commercial options as well as potential open source options.  We LOVE open source but something as critical as this we wouldn’t want to have to ever really troubleshoot.  We looked at solutions that were computers with specialty designed OS’s, as well as specialty hardware.

We had discussed deeply whether a standard computer hardware (with replaceable hardware) would be better than a hardware device designed to do what we wanted.  Ultimately we came to the conclusion that the software or features would make the decision.

We ended up going with a Ecessa Powerlink 600 which is a load balancer for both inbound and outbound connections,WAN fail-over, and Ecessa fail-over if two units are purchased.  We get the device setup with our current single 11Mb/11Mb fiber connection and were dieing to get more connections on the device.  A few weeks later we were able to get 100Mb/5Mb cable connection in and immediately saw the differences and how Ecessa was load balancing between the two connections.  Within the first week we had also had notices of our new cable modem dropping in and out however end user experience was not effected.

We were able to eventually load balance:

  • 11Mb down/11Mb up extremely reliable but expensive fiber connection
  • 50Mb down/50Mb up reliable wireless connection
  • 100Mb down/5Mb up least reliable cable connection

This provides us with a total usable bandwidth of 161Mb down/67Mb up, with the fastest potential download speed of 100Mb down, 50Mb up depending on the WAN interface you happen to fall on.  This also provides fail-over on any of the connections so that we can immediately fail-over to another connection without major interruption to end-users.

This link is also capable of load balancing incoming connections if set to an authoritative DNS server however we are currently not implementing that due to current network structure and time involved to implement that.  Although the time is not much, we are pressed to finish other projects right now.  That being said, we will be implementing this in the future.

I can say that installation was EXTREMELY easy with tech support.  Without the tech support the device would not be as straight forward as most would hope, advanced users ‘could’ struggle to get it setup.  We provided some simple information and they sent us a configuration file which was uploaded to the device.  They pretty well configured the device remotely and sent us the file.

We got it up and running and it has been running fantastic for over 100 days; even during ISP failures on our cable modem.  Our end users do not notice any issues when we fail-over.

When you setup Ecessa WAN links you type in the IP’s of 3 hosts to ping continuously.  When 2 of them fail the PL600 fails that link until they come back.  This ensures a good solid reliable connection for the end users.  We see out links during the day sporadically fail-over from time to time and have not had any complaints from end users.

During troubleshooting we can VERY easily see what WAN links are up and down, if there were problems, and what speeds are.  Screenshot - 01152013 - 09:30:12 PM

 

 

Jan 15 21:04:06 PowerLink PL600_00250725: Web authentication succeeded for root from ::ffff:68.190.160.87
Jan 15 19:11:05 PowerLink PL600_00250725: Web authentication succeeded for root from ::ffff:68.190.160.87
Jan 14 15:02:28 PowerLink PL600_00250725: Link Link3: Testpoint #1: Status change: PASS
Jan 14 15:02:12 PowerLink PL600_00250725: Link Link3: Testpoint #1: Status change: FAIL
Jan 14 14:43:17 PowerLink PL600_00250725: Link Link3: Testpoint #3: Status change: PASS
Jan 14 14:43:00 PowerLink PL600_00250725: Link Link3: Testpoint #3: Status change: FAIL
Jan 14 14:31:08 PowerLink PL600_00250725: Link Link3: Testpoint #2: Status change: PASS
Jan 14 14:30:50 PowerLink PL600_00250725: Link Link3: Testpoint #2: Status change: FAIL
Jan 14 12:45:59 PowerLink PL600_00250725: Link Link3: Testpoint #2: Status change: PASS
Jan 14 12:45:41 PowerLink PL600_00250725: Link Link3: Testpoint #2: Status change: FAIL
Jan 14 04:33:55 PowerLink PL600_00250725: Link Link1: Testpoint #3: Status change: PASS
Jan 14 04:33:48 PowerLink PL600_00250725: Link Link1: Testpoint #1: Status change: PASS
Jan 14 04:33:46 PowerLink PL600_00250725: PowerLink refresh - done
Jan 14 04:33:46 PowerLink PL600_00250725: PowerLink refresh - status
Jan 14 04:33:46 PowerLink PL600_00250725: Link: Link1: Status change: UP
Jan 14 04:33:46 PowerLink PL600_00250725: Link Link1: Testpoint #2: Status change: PASS
Jan 14 04:33:44 PowerLink PL600_00250725: PowerLink refresh - done
Jan 14 04:33:44 PowerLink PL600_00250725: PowerLink refresh - status
Jan 14 04:33:44 PowerLink PL600_00250725: Link: Link1: Status change: DOWN
Jan 14 04:33:41 PowerLink PL600_00250725: Link Link1: Testpoint #1: Status change: FAIL

We have found the Powerlink Extremely effective and  HUGE cost savings.  In about 1 year the device will pay itself off compared to if we would purchase a very fast reliable Internet connection.  We are looking for a second to setup as a redundant fail-over in the years to come.

Linux Vinyl Plotting With A Gerber enVision Plotter

I recently had the opportunity to work with an older Gerber enVision plotter from a township.  I had major difficulties getting the old version of Omega working with their USB licensing stick, and I knew that getting anything like this working on Windows without proper licensing would be an inadvisable, and rocky road ahead.

I decided to look into open source solutions, and I found out that Inkscape can do vinyl plotting with an extension called InkCut.

This tutorial will attempt to comprehensively explain how I got this working.  I am by no means an expert, but I found very limited web resources out there on this topic, and I am hopeful that someone will eventually stumble on this article and find it useful.

Background
A simple, free, and open source solution to an expensive and complex problem: How do we plot stuff with our vinyl plotter?

Assumptions
This tutorial will assume that you have some prior experience with the Linux terminal and the Linux desktop.  On my test computer, I was working with a clean installation of Ubuntu 12.04 (12.04.1) LTS.  However, any Ubuntu or Debian flavor should be acceptable.  I am also assuming you have an older Gerber enVision series plotter.  If this is not the case, I imagine most of these instructions will apply fairly well to any kind of vinyl plotter.

The Plotter
Here are some photos of the Gerber enVision plotter I was working with.

2013-01-01 13.20.33

2013-01-01 13.20.42

 

The plotter interfaced with the computer using a serial connection.

Ubuntu & This Plotter
In order to establish proper communications between the computer and the plotter, I had to ensure some things were true.  I reset my plotter to the factory default settings, which resulted in a condition where I could assume this about my serial connection:

Baud: 9600
Data Length: 8
Parity: None
Stop Bit: 1

In order to ensure communication with non-root users, I took a questionable approach, and I decided to:

chmod 777 /dev/ttyS0

This did not need to be a very secure environment (we didn’t even password protect the workstation’s desktop) so I figured this would be a reasonable approach, rather than troubleshooting why CUPS was getting permission denied errors while printing to the serial port.

Configure The Plotter In CUPS
To install this plotter in CUPS, you’ll want to open up your Printer configuration area from the System menu.

Click “Add” to add a printer.

CUPS Add A Printer

If you don’t have the option for “Serial Port #1”, then use the Device URI “serial:/dev/ttyS0“.

Serial Printer

 

You will want to select Generic as the make of printer.

Generic Printer

 

Then, select “Raw Queue”  This will work with InkCut providing the HPGL instructions.

Generic Printer - Raw Queue

Obviously, it doesn’t matter what you name your plotter, or what description you give it, just give it something that makes sense.

Finalize Printer Settings

Install Inkscape

Next, we want to install Inkscape.  You can do this from Apt on Ubuntu, as such:

sudo apt-get install inkscape

Once you’re done with the installation, start Inkscape for the first time.  This will create blank default configuration folders in your profile which are necessary for the next step.

Inkscape

 

Then, go ahead and close Inkscape, and move on to installing InkCut!

Install InkCut
You can download the latest version of InkCut from their website.  At the time of this writing, the version is 1.0, and can be found here.

Once you’ve downloaded InkCut, go ahead and extract the file using this command.  It will put the files right where they need to be for you!

tar -xzvf InkCut-1.0.tar.gz -C ~/.config/inkscape/extensions/

Now, when you start Inkscape, you should see InkCut on the Extensions menu, under Cutter/Plotter.

InkCut

Screencast How-To’s
 I have also created some screencasts to explain how to set up the document for your plotter, as well as how to plot some basic text.

Document Setup – Screencast
(Download OGV)

Let’s Plot Some Text! – Screencast
(Download OGV)

Remember, when plotting your text, you need to make sure your objects are converted to paths, by highlighting your text and going to Path > Object To Path.  You also want to make sure your paths aren’t grouped, by right clicking each block of text and clicking Ungroup.

Then you should be good to go to Extensions > Cutter/Plotter > InkCut v1.0 and start plotting!

Installing Zimbra Collaboration Suite On Ubuntu 12.04

Background
Zimbra Collaboration Suite is a fantastic email and collaboration solution made by VMware.   Zimbra is my email server solution of choice, because it’s very easy to setup, and the features you get are unmatched by other open source email solutions.  Ubuntu 12.04 is the current Ubuntu LTS, which will be supported for servers until 2017, so this is a great time to use it on a server you don’t want to have to take offline for frequent updates, like a mail server.

How is Zimbra different from SquirrelMail or RoundCube?
Popular open source solutions for webmail are SquirrelMail and RoundCube, which interface with an existing IMAP \ SMTP server to provide webmail access.  Zimbra is a fully integrated mail solution, which sets up a POP, IMAP, and SMTP server, and provides HTTP and\or HTTPS webmail out of the box.  Zimbra also provides a desktop AJAX, desktop HTML, and mobile HTML access option set.  No matter what device you’re on, you can access your webmail in a friendly way.

Other Features of Zimbra
Zimbra offers a number of other features, such as:

  • Address Book
  • Calendar
  • Tasks Management
  • File\Document Briefcase
  • File\Document\Folder Sharing
  • Incoming Email Filtering\Antivirus
  • Social Media Integration

You can look at the official list of features, and other information, on Zimbra’s website.  This is their page on the Open Source Edition.

 

Installing Zimbra Collaboration Suite 8.0.2 Open Source Edition on Ubuntu 12.04
If you’ve decided that you’d like to try Zimbra Collaboration Suite, let’s get on to the installation!

Install Dependencies
These packages will be necessary for Zimbra to be installed on your system.

sudo apt-get install netcat libidn11 libpcre3 libgmp3c2 libexpat1 libstdc++6 libperl5.14 sysstat sqlite3

Download Zimbra ZCS
At the time of this writing, you can use the link in the Code box below.  As this tutorial ages, and newer versions of Zimbra are released, you will want to go to the download page and get the latest link.

wget http://files2.zimbra.com/downloads/8.0.2_GA/zcs-8.0.2_GA_5569.UBUNTU12_64.20121210115059.tgz

zcs-wget

Extract The Downloaded Archive

tar -zxvf zcs-8.0.2_GA_5569.UBUNTU12_64.20121210115059.tgz

Enter The Folder You Extracted

cd zcs-8.0.2_GA_5569.UBUNTU12_64.20121210115059

DNS Configuration
If your DNS was not setup properly, you might get an error like DNS Error resolving yourhostname.com.  There is an error which will follow regarding your MX configuration.  These errors are OK to ignore, as long as you’re not planning on using your hostname to send\receive email.  You can add properly configured domains later.

However, you do want to make sure this domain name can be resolved.  Put it in /etc/hosts for 127.0.0.1 if necessary.  If you do not do this, you will encounter an error during the final setup stage.

Run The Installer

./install.sh

Press Y and hit enter to agree to the license agreement.

ZCS-install-1

 

Now, if you installed all the dependencies at the start of this tutorial, you should have everything you need!

ZCS-Install-2

 

If you aren’t sure what you want to install, then just install the items as suggested.

zimbra-ldap – Yes
zimbra-logger – Yes
zimbra-mta – Yes
zimbra-snmp – Yes
zimbra-store – Yes
zimbra-apache – Yes
zimbra-spell  – Yes
zimbra-memcached – No
zimbra-proxy – No

When asked if you want to continue, press Y and hit enter to proceed with the installation.

ZCS-Install-3

The Zimbra installer will take care of extracting and installing the packages for you.  This part of the process might take some time, depending on the speed of your machine.

 

Configuration Menu
Go through all of the items on the configuration and make sure they are what you want.  I like to make sure these options are set:

Don’t stress out about the domain names too much, you can add additional domains to your email server later, very easily.

  • Common Configuration > Hostname\Ldap Master Host — Should be your server’s main domain, like mydomain.com.
  • Common Configuration > LDAP Admin Password — The administrative password for Zimbra’s LDAP Server.  Make it something you’ll remember if you ever think you’ll want to integrate anything with the built-in LDAP later.
  • LDAP > Domain To Create — Should be your server’s main domain, like mydomain.com.
  • LDAP > LDAP Root\Replication\Postfix\Amavis\Nginx\Bes Searcher Passwords — I like to change these too.
  • Zimbra Store > Admin User\Password — These will be used to login to the Zimbra Admin Area.
  • Zimbra Store > Spell Server URL — Make sure this is a web address that can be accessed, it will be used when people press Spell Check.
  • Zimbra Store > SMTP Host — Should be your server’s main domain, like mydomain.com.
  • Zimbra Store > Version Update Email Addresses — Should be an email address for an administrator.

When you’re satisfied with all of your settings, press “S” and hit enter to write your settings to the configuration file.   The default file location is fine.   Then press “A” and hit enter to apply your settings and start the server!

Zimbra will ask you to confirm the changes to your system.  Type “Yes” and hit enter.

Zimbra will now run through an installation procedure, which may take a few minutes, depending on the speed of your machine.

If all went well, Zimbra is now installed on your server.  If it didn’t, you will be given a log file location, where you can look and see what might have gone wrong.

 

Firewall Rules
Hopefully your server has, or is at least behind, a firewall solution.  If so, these are the ports you should definitely be unblocking for the proper use of your server.  These ports are assuming you’re running a default configuration, and you did not change your ports during the setup procedure.

Webmail: 80/tcp for standard access, 443/tcp for encrypted access.
Administration Console: 7071/tcp (can be blocked in the firewall if you only plan to do administration over VPN, locally, etc)
Aspell: 7780/tcp (Zimbra runs a spell check server on this custom port, which users will access when they press the Spell Check button on the web interface)
SMTP: 25/tcp for standard access, 465/tcp for encrypted access.
POP: 110/tcp for standard access, 995/tcp for encrypted access.
IMAP: 143/tcp for standard access, 993/tcp for encrypted access.

 

Accessing Your Zimbra Server
You can login to your Zimbra accounts for webmail access at your Zimbra server’s IP or DNS on the standard https port 443.  You can access your Administration Console over HTTPS using port 7071.

Point your web browser to http://your.zimbra.server.ip:7071/

Zimbra Admin Console

Once you’re logged in, your admin interface will look something like this.

Zimbra Admin 2

The Zimbra setup procedures in the web interface are very straightforward, and are up to you to play with on your own now that Zimbra is installed and working!

Installing Dragon Naturally Speaking 12 on Ubuntu 12.04 (Using PlayOnLinux)

After having very much difficulty installing Dragon Naturally Speaking 12 on Ubuntu 12.04 with the latest version of WINE (WINE 1.5.20) I decided to look again at the AppDB.  I found that Dragon Naturally Speaking had a Platinum rating for WINE 1.4, so I decided to give that version of WINE a try with PlayOnLinux, which I believe is a very effective tool for managing different WINE versions and profiles.

Obviously, PlayOnLinux is not a requirement for having WINE 1.4 installed on your machine.  You could install WINE yourself and obtain this version, but for the scope of this tutorial, we will be using PlayOnLinux to manage the installation.

Install PlayOnLinux
It will be to your benefit to grab the latest version of PlayOnLinux from their repository, as this will probably be more recent than the version in your distro’s repository.  This step is optional, but if you ignore it, you might not get the version of PlayOnLinux described in this procedure, and you might be missing new bugfixes and improvements.

sudo wget -q "http://deb.playonlinux.com/public.gpg" -O- | sudo apt-key add -
sudo wget http://deb.playonlinux.com/playonlinux_precise.list -O /etc/apt/sources.list.d/playonlinux.list
sudo apt-get update

Now, let’s install PlayOnLinux!

sudo apt-get install playonlinux

Install WINE 1.4 Inside PlayOnLinux
Go to the Tools menu, and select Manage WINE Versions.

1-PlayOnLinux

Select WINE 1.4, and press the Right Arrow to install the version.

2-PlayOnLinux

PlayOnLinux will download and install WINE 1.4 for you.

3-PlayOnLinux

Once it’s installed, it will appear to the right.

4-PlayOnLinux

 

Close out of the WINE installation screen.  Next, you’ll want to press the Install button in the PlayOnLinux window, to start installing a new Windows program.

5-PlayOnLinux

Select “Install a new program in a new virtual drive.”

6-PlayOnLinux

You can name your drive whatever you want.  I called mine “DragonNaturallySpeaking12”.

7-PlayOnLinux

Go ahead and check “Use another version of WINE” and hit Next.  This will allow us to manually select which version of WINE we want to use.

8-PlayOnLinux

If you have used PlayOnLinux for other things, you may have more than one version of WINE installed, and that’s OK.  We want to select 1.4.  If you don’t have this option, please go back to the beginning of the tutorial and make sure you’ve installed WINE 1.4 using the “Manage WINE Versions” option on the Tools menu.

9-PlayOnLinux

Now, PlayOnLinux will set up your virtual drive for you.

10-PlayOnLinux

Assuming you have the Dragon Naturally Speaking 12 DVD, which I did, you want to select “CD-ROM” as the place to install your program from.  As shown here.  Then, hit Next.

11-PlayOnLinux

PlayOnLinux will do some steps to prepare for the installation.

12-PlayOnLinux

After a moment or two, the Dragon Naturally Speaking installer will start.  As with any normal installer, click Next to begin.

13-PlayOnLinux

Read the license agreement.  (Hah!)  Then check “I accept the terms in the license agreement” and press Next.

14-PlayOnLinux

In the next window, you’ll want to substitute my filler information with your own.  The serial number for my Dragon Naturally Speaking 12 installation was on the back of the paper DVD holder that contained my installation disk.  Yours will probably be there as well.  Once you’ve filled in your information, go ahead and hit Next.

15-PlayOnLinux

I chose to do a Typical/Complete installation.  I chose to leave the default location.  The location will not interfere with any other WINE programs, unless you didn’t create a brand new virtual drive.  If you did, then the default location should work just fine for you.  If you have no idea, just leave this screen how it is, and press Next.  (That will be fine for most cases.)

17-PlayOnLinux

The installer will now copy some files.

I got this error message.  I ignored it and pressed OK.

18-PlayOnLinux(Error)

 

I decided I didn’t want to have Dragon Naturally Speaking check for updates on its own, as I have no idea how those will be installed… and I am using my Dragon Naturally Speaking in a professional installation where I will not be the user.  I don’t want to put my end-user through a hostile upgrade experience later, I just assume update it myself down the road if necessary.

Once you’ve decided whether you want to risk the automated updates, hit Finish.

19-PlayOnLinux(Finished)

The installer created a .lnk file on my Ubuntu desktop, but I found that shortcut did not work, so I deleted it.  I created my shortcut using the PlayOnLinux shortcut maker.  You can find this by pressing the Configure button on top of your PlayOnLinux screen.

Select your virtual drive, and click the “Make a new shortcut from this virtual drive” button.

1-Shortcut-FromVdrive

Find “natspeak.exe” and press Next.

2-Shortcut-NatSpeak.exe

Obviously, you can name your shortcut whatever you want.   I chose to name mine “Dragon Naturally Speaking 12”.

3-Shortcut-TypeName

Close out of the shortcut maker when it’s finished, and you should now have a shortcut on your desktop to launch Dragon Naturally Speaking.  Go ahead and launch it.

On first run, I had to activate Dragon Naturally Speaking.  This process worked fine for me, so just press Activate Now.

 

 

1-Dragon-1strun-activation

 

Then, Dragon Naturally Speaking will fire up.  Everything looks like it’s working well so far.

2-Dragon-1strun-Splash

 

I did encounter some minor issues with Dragon Naturally Speaking, but all in all, it worked well enough that I am comfortable deploying it.

 

Some Issues I Had:

The Sidebar.  I disabled the sidebar, because it seemed like every other time it launched, it caused the application to crash.

Where You Can Dictate.  It seemed like dictation into Linux programs didn’t work.  I could only dictate into DragonPad and Dragon Naturally Speaking itself.  Even other WINE programs, like Notepad, seemed out of reach of Dragon’s dictation power.

 

I was quite surprised that some of the features like “Search Google for ____” actually worked, and actually launched my native Mozilla Firefox application.   I did not have a huge amount of time to test the installation, but it will be going into production, so I’m sure if there are any other issues, I will find out about them.  If anyone has any questions, please feel free to ask in the comments, and I will answer what I can.  Keep in mind, I did not install Dragon Naturally Speaking on my own laptop, and my work only had a single license.

The reason I created this tutorial was not as a comprehensive guide, but so that someone who is searching Google for these instructions can find something.  I was very disappointed at how little information I found on Dragon Naturally Speaking 12 with WINE.   I am by no means an expert, just someone who spent a little too much time trying to get this working (see my other two blog posts here and here)… I hope someone found this useful and that I saved someone some time!

Installing Dragon Naturally Speaking 12 Does Not Work With WINE 1.5.20

NOTE: This is NOT a how-to.  This was an effort to document the problems I ran into during installation.  This blog post did not end in a successful installation of Dragon Naturally Speaking 12 in WINE 1.5.20.

This post, like my previous one, also started as a How-to, until it didn’t work…  I did eventually get Dragon Naturally Speaking working, and that post will be coming shortly.  This post does not have instructions which work, but I will publish it anyway in the hopes that someone will find it on Google, and something I’ve written will be useful.

My Installation Experiences

After failing to get Dragon Naturally Speaking 12 working on Ubuntu 10.04, I decided to try it in Ubuntu 12.04 where I would have access to a more recent version of WINE.  I decided to grab the latest version of WINE from the PPA.

Install WINE 1.5 from the PPA

sudo apt-add-repository ppa:ubuntu-wine/ppa
sudo apt-get update
sudo apt-get install wine

Install Microsoft .NET Framework 4.0 (Winetricks)

winetricks dotnet40

I was asked to download a file from Mediafire and put it in a location. Follow all on-screen instructions.

Dragon - 3 - Dotnet Error

The .NET Framework installer failed and produced error code HRESULT 0x80070643.  I found this bug report which led me to these other Winetricks.

When installing the other Winetricks, pay attention to their instructions, as some of them will have you download and run other scripts.  This is supposed to satisfy the missing .NET Framework requirements.

winetricks gecko
winetricks windowscodecs
winetricks ie7
winetricks msxml3
winetricks msxml4

Create a 32-bit WINE Prefix As described from this thread, I followed these steps.

export WINEARCH="win32"
export WINPREFIX="/home/folder/.wine"

Run Dragon Naturally Speaking Installer

wine setup.exe

Dragon - 1 - Install Starting

Dragon - 2 - License Agreement

 

I still got an error when executing the MSI installer…

Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x6840c928).
Register dump:
 CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
 EIP:6840c928 ESP:0033f860 EBP:0033f8a8 EFLAGS:00010246(  R- --  I  Z- -P- )
 EAX:00000000 EBX:68475ff4 ECX:0033f750 EDX:00000000
 ESI:00852580 EDI:008525a4
Stack dump:
0x0033f860:  0013eb08 6846146c 00000016 683fd2a1
0x0033f870:  00000000 00000002 00011000 00000000
0x0033f880:  00000000 00000000 008527b8 007fac68
0x0033f890:  001506bc 00150680 0033f948 68475ff4
0x0033f8a0:  0066c158 00150680 0033f948 683fe5b8
0x0033f8b0:  00150680 00000001 00852580 68475ff4
Backtrace:
=>0 0x6840c928 in msi (+0x5c928) (0x0033f8a8)
  1 0x683fe5b8 in msi (+0x4e5b7) (0x0033f948)
  2 0x683c38e9 in msi (+0x138e8) (0x0033f998)
  3 0x683d5776 in msi (+0x25775) (0x0033f9e8)
  4 0x683d59ef in msi (+0x259ee) (0x0033fa38)
  5 0x6841f4c0 in msi (+0x6f4bf) (0x0033fa78)
  6 0x683c2862 in msi (+0x12861) (0x0033fac8)
  7 0x683c38e9 in msi (+0x138e8) (0x0033fb18)
  8 0x683d5776 in msi (+0x25775) (0x0033fb68)
  9 0x683d59ef in msi (+0x259ee) (0x0033fbb8)
  10 0x6841f4c0 in msi (+0x6f4bf) (0x0033fbf8)
  11 0x683d6056 in msi (+0x26055) (0x0033fc48)
  12 0x684108bd MsiInstallProductW+0x8c() in msi (0x0033fc98)
  13 0x6839caa4 WinMain+0x673() in msiexec (0x0033fd78)
  14 0x6839e3bf main+0xae() in msiexec (0x0033fe08)
  15 0x6839e2fc in msiexec (+0xe2fb) (0x0033fe58)
  16 0x7b85f8ec call_process_entry+0xb() in kernel32 (0x0033fe78)
  17 0x7b860b6f in kernel32 (+0x50b6e) (0x0033feb8)
  18 0x7bc77130 call_thread_func_wrapper+0xb() in ntdll (0x0033fed8)
  19 0x7bc79cad call_thread_func+0x7c() in ntdll (0x0033ffa8)
  20 0x7bc7710e RtlRaiseException+0x21() in ntdll (0x0033ffc8)
  21 0x7bc4c82e call_dll_entry_point+0x61d() in ntdll (0x0033ffe8)
0x6840c928: movzwl	0x0(%edx,%eax,1),%ecx
Modules:
Module	Address			Debug info	Name (126 modules)
PE	  460000-  46e000	Deferred        msi3ae7.tmp
PE	  9e0000-  a14000	Deferred        msi8158.tmp
PE	  a20000-  a43000	Deferred        msi855f.tmp
PE	  a50000-  a93000	Deferred        msi8568.tmp
PE	  ac0000-  ac7000	Deferred        msi897d.tmp
PE	  d90000-  f43000	Deferred        msi414e.tmp
PE	10000000-10036000	Deferred        msi3a4e.tmp
ELF	20014000-20052000	Deferred        libgssapi_krb5.so.2
ELF	20052000-20064000	Deferred        libavahi-client.so.3
ELF	20064000-20133000	Deferred        libkrb5.so.3
ELF	20133000-20138000	Deferred        libcom_err.so.2
ELF	20138000-2014a000	Deferred        libtasn1.so.3
ELF	2014a000-20193000	Deferred        libdbus-1.so.3
ELF	20214000-20228000	Deferred        shfolder<elf>
  \-PE	20220000-20228000	\               shfolder
ELF	20228000-20253000	Deferred        netapi32<elf>
  \-PE	20230000-20253000	\               netapi32
ELF	20253000-20277000	Deferred        iphlpapi<elf>
  \-PE	20260000-20277000	\               iphlpapi
ELF	20277000-202a6000	Deferred        secur32<elf>
  \-PE	20280000-202a6000	\               secur32
ELF	20b14000-20b26000	Deferred        libp11-kit.so.0
ELF	21d6d000-21dc0000	Deferred        libcups.so.2
ELF	25089000-250bc000	Deferred        ws2_32<elf>
  \-PE	25090000-250bc000	\               ws2_32
ELF	29ce3000-29cfd000	Deferred        sxs<elf>
  \-PE	29cf0000-29cfd000	\               sxs
ELF	2aa63000-2aa8b000	Deferred        libk5crypto.so.3
ELF	2c11e000-2c122000	Deferred        libkeyutils.so.1
ELF	362dd000-362eb000	Deferred        libavahi-common.so.3
ELF	3d6e9000-3d798000	Deferred        winmm<elf>
  \-PE	3d6f0000-3d798000	\               winmm
ELF	48efc000-48fc0000	Deferred        libgnutls.so.26
ELF	4c164000-4c1c3000	Deferred        dbghelp<elf>
  \-PE	4c170000-4c1c3000	\               dbghelp
ELF	4e730000-4e739000	Deferred        libkrb5support.so.0
ELF	53ee2000-53efa000	Deferred        libresolv.so.2
PE	5dca0000-5dce5000	Deferred        iertutil
ELF	5e608000-5e611000	Deferred        librt.so.1
PE	603b0000-60416000	Deferred        mscoreei
PE	604a0000-604ac000	Deferred        fusion
ELF	605a8000-605ad000	Deferred        libgpg-error.so.0
PE	61410000-61534000	Deferred        urlmon
ELF	63a94000-63ab7000	Deferred        imm32<elf>
  \-PE	63aa0000-63ab7000	\               imm32
ELF	63ca7000-63cab000	Deferred        libnss_mdns4_minimal.so.2
ELF	68000000-68022000	Deferred        ld-linux.so.2
ELF	68022000-68164000	Dwarf           libwine.so.1
ELF	68164000-6817f000	Deferred        libpthread.so.0
ELF	6817f000-68329000	Deferred        libc.so.6
ELF	68329000-6832e000	Deferred        libdl.so.2
ELF	6832e000-6835a000	Deferred        libm.so.6
ELF	6835a000-68363000	Deferred        libnss_compat.so.2
ELF	68363000-6837d000	Deferred        libnsl.so.1
ELF	6837d000-6838a000	Deferred        libnss_files.so.2
ELF	6838a000-683a8000	Dwarf           msiexec<elf>
  \-PE	68390000-683a8000	\               msiexec
ELF	683a8000-68491000	Dwarf           msi<elf>
  \-PE	683b0000-68491000	\               msi
ELF	68491000-68526000	Deferred        msvcrt<elf>
  \-PE	684a0000-68526000	\               msvcrt
ELF	68526000-6863b000	Deferred        ole32<elf>
  \-PE	68540000-6863b000	\               ole32
ELF	6863b000-686a0000	Deferred        advapi32<elf>
  \-PE	68650000-686a0000	\               advapi32
ELF	686a0000-687e7000	Deferred        user32<elf>
  \-PE	686b0000-687e7000	\               user32
ELF	687e7000-688f2000	Deferred        gdi32<elf>
  \-PE	687f0000-688f2000	\               gdi32
ELF	688f2000-6890c000	Deferred        version<elf>
  \-PE	68900000-6890c000	\               version
ELF	6890c000-68a26000	Deferred        oleaut32<elf>
  \-PE	68920000-68a26000	\               oleaut32
ELF	68a26000-68a3c000	Deferred        libz.so.1
ELF	68a3c000-68a62000	Deferred        mpr<elf>
  \-PE	68a40000-68a62000	\               mpr
ELF	68a62000-68c7b000	Deferred        shell32<elf>
  \-PE	68a70000-68c7b000	\               shell32
ELF	68c7b000-68c9b000	Deferred        cabinet<elf>
  \-PE	68c80000-68c9b000	\               cabinet
ELF	68c9b000-68d35000	Deferred        libfreetype.so.6
ELF	68d35000-68dbf000	Deferred        winex11<elf>
  \-PE	68d40000-68dbf000	\               winex11
ELF	68dbf000-68dc8000	Deferred        libsm.so.6
ELF	68dc8000-68efc000	Deferred        libx11.so.6
ELF	68efc000-68f02000	Deferred        libuuid.so.1
ELF	68f02000-68f23000	Deferred        libxcb.so.1
ELF	68f23000-68f27000	Deferred        libxau.so.6
ELF	68f27000-68f2e000	Deferred        libxdmcp.so.6
ELF	68f2e000-68f32000	Deferred        libxinerama.so.1
ELF	68f32000-68f3c000	Deferred        libxrender.so.1
ELF	68f3c000-68f45000	Deferred        libxrandr.so.2
ELF	68f45000-68f49000	Deferred        libxcomposite.so.1
ELF	68f49000-68f59000	Deferred        libxi.so.6
ELF	68f59000-68f5f000	Deferred        libxfixes.so.3
ELF	68f5f000-68f93000	Deferred        uxtheme<elf>
  \-PE	68f70000-68f93000	\               uxtheme
ELF	6936d000-6938b000	Deferred        libgcc_s.so.1
ELF	6b9ef000-6b9f6000	Deferred        libnss_dns.so.2
ELF	6bf38000-6bf55000	Deferred        fusion<elf>
ELF	711fa000-71272000	Deferred        rpcrt4<elf>
  \-PE	71210000-71272000	\               rpcrt4
ELF	71c59000-71c73000	Deferred        libice.so.6
ELF	73149000-731ce000	Deferred        libgcrypt.so.11
ELF	73e00000-73e0c000	Deferred        libnss_nis.so.2
ELF	74470000-74499000	Deferred        msacm32<elf>
  \-PE	74480000-74499000	\               msacm32
ELF	74501000-74575000	Deferred        wininet<elf>
  \-PE	74510000-74575000	\               wininet
ELF	76722000-76728000	Deferred        libxxf86vm.so.1
ELF	76736000-76741000	Deferred        libxcursor.so.1
ELF	77665000-77679000	Deferred        psapi<elf>
  \-PE	77670000-77679000	\               psapi
PE	77f60000-77fd6000	Deferred        shlwapi
ELF	78a36000-78a48000	Deferred        libxext.so.6
PE	79000000-7904a000	Deferred        mscoree
PE	79060000-7911e000	Deferred        msvcr100_clr0400
PE	79140000-797af000	Deferred        clr
ELF	799a8000-799bb000	Deferred        gnome-keyring-pkcs11.so
ELF	7b149000-7b245000	Deferred        comctl32<elf>
  \-PE	7b150000-7b245000	\               comctl32
ELF	7b800000-7ba33000	Dwarf           kernel32<elf>
  \-PE	7b810000-7ba33000	\               kernel32
ELF	7bc00000-7bcca000	Dwarf           ntdll<elf>
  \-PE	7bc10000-7bcca000	\               ntdll
ELF	7bf00000-7bf04000	Deferred        <wine-loader>
Threads:
process  tid      prio (all id:s are in hex)
0000000e services.exe
	00000028    0
	00000027    0
	00000020    0
	00000010    0
	0000000f    0
00000014 explorer.exe
	00000015    0
0000001d winedevice.exe
	00000025    0
	00000022    0
	0000001f    0
	0000001e    0
00000023 plugplay.exe
	00000029    0
	00000026    0
	00000024    0
0000002a setup.exe
	0000002b    0
0000002c (D) C:\windows\system32\msiexec.exe
	0000005f    0
	0000005d    0
	0000005b    0
	00000059    0
	00000055    0
	00000053    0
	0000004f    0
	0000004d    0
	0000004b    0
	00000049    0
	00000011    0
	0000001b    0
	00000033    0
	00000009    0
	00000017    0
	00000013    0
	00000016    0
	00000046    0
	00000044    0
	00000042    0
	00000040    0
	0000003e    0
	0000003c    0
	0000003a    0
	00000038    0
	00000036    0
	00000034    0
	00000032    0
	00000031    0
	0000002d    0 <==
System information:
    Wine build: wine-1.5.20
    Platform: i386
    Host system: Linux
    Host version: 3.2.0-35-generic