MSSharedMem doesn't support more than 1 slave

[excaliburtb]

MSSharedMem has a couple of issues:

1. the memory layout of the data in the shared memory block is not explicitly padded to avoid issues with a slave that compiles differently.
2. the proj_id within the tsm library is a static int that increments regardless of user input. so a second slave cannot get the same shm key.

The result of the above is that a 32-bit slave is unlikely to connect correctly even as the sole slave.

If more than 1 MSSharedMem slave is used, the second slave can generate a key and both master and slave think they were successful but they will not communicate with each other properly