Rebuilding MM under Windows - some issues

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Rebuilding MM under Windows - some issues

Graham Bartlett
Hi all,

I work for Prior Scientific.  MM has drivers for the old Prior NanoScanZ controller, but we've found out (during development for our new controller) that these drivers don't support auto acquisition and camera auto-focus - you can drive the Z stage up and down manually, but the driver throws an error if you hook it up to automation.  I'm looking at fixing those drivers.
 
Which of course means I need to be able to compile MM.  I've hit a few problems there which I think should go in your docs.  (Or of course if people can tell me where I've made a mistake, I'll make a note of that myself so that I don't make the same mistake twice.)

1) The Windows SDK 7.1 won't install out of the box on current Windows.  Note that this applies to Windows 7 as well - my PC runs Windows 10, but I do my development in a Windows 7 VM.  Windows 7 with full updates will not install the SDK either.  I found a fix for this at https://stackoverflow.com/questions/31455926/windows-sdk-7-1-setup-failure.  It involves some minor tinkering with registry entries, but it seemed to work OK.

2) Visual Studio 2010 Express is no longer supported by MS.  You can still download it (from the link in your docs), but MS have turned off the license server.  If you can't get a license for it, you've got 30 days to use it and then it stops working.  Someone asked this already on Reddit, and someone else responded with valid license keys which can be used - see  https://www.reddit.com/r/VisualStudio/comments/7xx6yb/cant_register_visual_studio_2010_express/.

Of course these license keys will be in use by other people somewhere too, but since the license server is down there's no way for the application to find out, so it's all good.  There are various other suggestions online, such as scheduling a task every day to tweak the registry entry which tracks the days left on the grace period, but it's much easier just to use those license keys.

For our development at Prior, we use Visual Studio 2013 Express.  This is also not supported by MS, but the license server for that still works.  I've considered moving us to Visual Studio 2017 Express for Desktop, but code built with Visual Studio 2013 still works on Windows 10 so I haven't had a strong reason to change.  Since Visual Studio 2010 is completely dead though, have you considered moving on?

3) Several device adaptors fail to build because they can't find files under the "3rdparty" directory.  The build instructions do not say how to get the "3rdparty" directory from SVN.  I suggest they should, because not only can people like myself not build MM completely, but also anyone wanting to add new "3rdparty" files can't tell whether they're going to clash with anything that's already there.

All that said though, the Prior device adaptor builds OK, so I can get on with my fixes. :)

Cheers,

        Graham.


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: Rebuilding MM under Windows - some issues

JonD
Administrator
Hi Graham,

Regarding Visual Studio check out these threads:

http://micro-manager.3463995.n2.nabble.com/Setting-up-MM-build-environment-on-Windows-10-td7590007.html
http://micro-manager.3463995.n2.nabble.com/Building-Device-Adapters-on-Windows-10-with-Visual-Studio-2015-Community-td7587098.html
http://micro-manager.3463995.n2.nabble.com/Building-Micromanager-on-Windows-td7589426.html

In my experience in a similar situation, I only build the specific device
adapter I am editing, not the entirety of MM.

Jon

-------------------------------------------
Jon Daniels
Applied Scientific Instrumentation
29391 West Enid Rd, Eugene, OR 97402
Phone: (541) 461-8181 x118
-------------------------------------------



--
Sent from: http://micro-manager.3463995.n2.nabble.com/


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: Rebuilding MM under Windows - some issues

Karl Bellve-3
In reply to this post by Graham Bartlett


On Wed, Oct 16, 2019 at 10:06 AM Graham Bartlett <[hidden email]> wrote:
Hi all,

I work for Prior Scientific.  MM has drivers for the old Prior NanoScanZ controller, but we've found out (during development for our new controller) that these drivers don't support auto acquisition and camera auto-focus - you can drive the Z stage up and down manually, but the driver throws an error if you hook it up to automation.  I'm looking at fixing those drivers.


Hi Graham, 

Just like Jon, I only compile the specific device adapter with Visual Studio 2010, and then drop that DLL into a working 1.4 µManager installation.

As far as license keys, I recall that after 30 days, Microsoft wanted me to upgrade to a different key, but still free, and MS Visual Studio 2010 Express still works for me. I think it was a cloud account, or something similar....it has been a few months so I don't remember.


--
Kia ora,

Karl Bellvé

Kia ora, a common Kiwi salutation, means to wish somebody life and health in the Maori language


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: Rebuilding MM under Windows - some issues

Nico Stuurman-2
In reply to this post by Graham Bartlett
Hi Graham,

> I work for Prior Scientific.  MM has drivers for the old Prior NanoScanZ controller, but we've found out (during development for our new controller) that these drivers don't support auto acquisition and camera auto-focus - you can drive the Z stage up and down manually, but the driver throws an error if you hook it up to automation.  I'm looking at fixing those drivers.

Great to hear that you are working on this!

> Which of course means I need to be able to compile MM.  I've hit a few problems there which I think should go in your docs.  (Or of course if people can tell me where I've made a mistake, I'll make a note of that myself so that I don't make the same mistake twice.)
>
> 1) The Windows SDK 7.1 won't install out of the box on current Windows.  Note that this applies to Windows 7 as well - my PC runs Windows 10, but I do my development in a Windows 7 VM.  Windows 7 with full updates will not install the SDK either.  I found a fix for this at https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_questions_31455926_windows-2Dsdk-2D7-2D1-2Dsetup-2Dfailure&d=DwICAg&c=iORugZls2LlYyCAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25Dt4I&m=f1SoyNficl1IWesWC6CZmqMjzeAxWJvYjKXJ6TNfUWA&s=Fg3qPH1Qys5BNMBnSkugoF30BqAeLwJSPjFO6vq2RyM&e= .  It involves some minor tinkering with registry entries, but it seemed to work OK.

I don't remember all the details, but last time I installed a full
development environment was on Windows 10, and things went unexpectedly
smoothly (should have taken notes and updated documentation), mainly
following the instructions on MM website.

> 2) Visual Studio 2010 Express is no longer supported by MS.  You can still download it (from the link in your docs), but MS have turned off the license server.  If you can't get a license for it, you've got 30 days to use it and then it stops working.  Someone asked this already on Reddit, and someone else responded with valid license keys which can be used - see  https://urldefense.proofpoint.com/v2/url?u=https-3A__www.reddit.com_r_VisualStudio_comments_7xx6yb_cant-5Fregister-5Fvisual-5Fstudio-5F2010-5Fexpress_&d=DwICAg&c=iORugZls2LlYyCAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25Dt4I&m=f1SoyNficl1IWesWC6CZmqMjzeAxWJvYjKXJ6TNfUWA&s=98nIMEauHkcFD_ZLzNTIFmSGFDXgvD5yrtLwfblEWK4&e= .
>
> Of course these license keys will be in use by other people somewhere too, but since the license server is down there's no way for the application to find out, so it's all good.  There are various other suggestions online, such as scheduling a task every day to tweak the registry entry which tracks the days left on the grace period, but it's much easier just to use those license keys.

I ended up doing the same, even though I have tens of license keys for
VS2010 already registered.

> For our development at Prior, we use Visual Studio 2013 Express.  This is also not supported by MS, but the license server for that still works.  I've considered moving us to Visual Studio 2017 Express for Desktop, but code built with Visual Studio 2013 still works on Windows 10 so I haven't had a strong reason to change.  Since Visual Studio 2010 is completely dead though, have you considered moving on?

The plan is to move to VS2019.  It should be pretty straight forward,
and hopefully this will happen in the not too distant future.

> 3) Several device adaptors fail to build because they can't find files under the "3rdparty" directory.  The build instructions do not say how to get the "3rdparty" directory from SVN.  I suggest they should, because not only can people like myself not build MM completely, but also anyone wanting to add new "3rdparty" files can't tell whether they're going to clash with anything that's already there.

3rdparty contains libraries/code that we are not allowed to make public
by the owners of that code (as opposed to the code in 3rdpartypublic). 
So, if you really want to compile those device adapters (but why should
you, you can always get the binaries from our build servers), you will
need to get those dependencies yourself and place them in a 3rdarty
directory that sits next to your micro-manager source code tree, and has
the files in the same organization as the ones in our 3rdparty directory
(which you can glean from the project file).  .

> All that said though, the Prior device adaptor builds OK, so I can get on with my fixes. :)

Perfect!  Email me (off-line) a patch when you are done.  Also, I can
give you write access to the Prior code in our svn repository, so that
you can update the code yourself.


Best,


Nico


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: Rebuilding MM under Windows - some issues

Graham Bartlett
Cool, thanks Nico.  Good to hear that a Visual Studio upgrade is on the way - I won't worry too much about that then.

Cheers,

        Graham.

-----Original Message-----
From: Stuurman, Nico <[hidden email]>
Sent: 16 October 2019 17:43
To: Micro-Manager General <[hidden email]>
Subject: Re: [micro-manager-general] Rebuilding MM under Windows - some issues

Hi Graham,

> I work for Prior Scientific.  MM has drivers for the old Prior NanoScanZ controller, but we've found out (during development for our new controller) that these drivers don't support auto acquisition and camera auto-focus - you can drive the Z stage up and down manually, but the driver throws an error if you hook it up to automation.  I'm looking at fixing those drivers.

Great to hear that you are working on this!

> Which of course means I need to be able to compile MM.  I've hit a few
> problems there which I think should go in your docs.  (Or of course if
> people can tell me where I've made a mistake, I'll make a note of that
> myself so that I don't make the same mistake twice.)
>
> 1) The Windows SDK 7.1 won't install out of the box on current Windows.  Note that this applies to Windows 7 as well - my PC runs Windows 10, but I do my development in a Windows 7 VM.  Windows 7 with full updates will not install the SDK either.  I found a fix for this at https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_questions_31455926_windows-2Dsdk-2D7-2D1-2Dsetup-2Dfailure&d=DwICAg&c=iORugZls2LlYyCAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25Dt4I&m=f1SoyNficl1IWesWC6CZmqMjzeAxWJvYjKXJ6TNfUWA&s=Fg3qPH1Qys5BNMBnSkugoF30BqAeLwJSPjFO6vq2RyM&e= .  It involves some minor tinkering with registry entries, but it seemed to work OK.

I don't remember all the details, but last time I installed a full development environment was on Windows 10, and things went unexpectedly smoothly (should have taken notes and updated documentation), mainly following the instructions on MM website.

> 2) Visual Studio 2010 Express is no longer supported by MS.  You can still download it (from the link in your docs), but MS have turned off the license server.  If you can't get a license for it, you've got 30 days to use it and then it stops working.  Someone asked this already on Reddit, and someone else responded with valid license keys which can be used - see  https://urldefense.proofpoint.com/v2/url?u=https-3A__www.reddit.com_r_VisualStudio_comments_7xx6yb_cant-5Fregister-5Fvisual-5Fstudio-5F2010-5Fexpress_&d=DwICAg&c=iORugZls2LlYyCAZRB3XLg&r=UwP8SWqih8VHO1LwZpgcx83I4o21yLj6V6QD-25Dt4I&m=f1SoyNficl1IWesWC6CZmqMjzeAxWJvYjKXJ6TNfUWA&s=98nIMEauHkcFD_ZLzNTIFmSGFDXgvD5yrtLwfblEWK4&e= .
>
> Of course these license keys will be in use by other people somewhere too, but since the license server is down there's no way for the application to find out, so it's all good.  There are various other suggestions online, such as scheduling a task every day to tweak the registry entry which tracks the days left on the grace period, but it's much easier just to use those license keys.

I ended up doing the same, even though I have tens of license keys for
VS2010 already registered.

> For our development at Prior, we use Visual Studio 2013 Express.  This is also not supported by MS, but the license server for that still works.  I've considered moving us to Visual Studio 2017 Express for Desktop, but code built with Visual Studio 2013 still works on Windows 10 so I haven't had a strong reason to change.  Since Visual Studio 2010 is completely dead though, have you considered moving on?

The plan is to move to VS2019.  It should be pretty straight forward, and hopefully this will happen in the not too distant future.

> 3) Several device adaptors fail to build because they can't find files under the "3rdparty" directory.  The build instructions do not say how to get the "3rdparty" directory from SVN.  I suggest they should, because not only can people like myself not build MM completely, but also anyone wanting to add new "3rdparty" files can't tell whether they're going to clash with anything that's already there.

3rdparty contains libraries/code that we are not allowed to make public by the owners of that code (as opposed to the code in 3rdpartypublic). So, if you really want to compile those device adapters (but why should you, you can always get the binaries from our build servers), you will need to get those dependencies yourself and place them in a 3rdarty directory that sits next to your micro-manager source code tree, and has the files in the same organization as the ones in our 3rdparty directory (which you can glean from the project file).  .

> All that said though, the Prior device adaptor builds OK, so I can get
> on with my fixes. :)

Perfect!  Email me (off-line) a patch when you are done.  Also, I can give you write access to the Prior code in our svn repository, so that you can update the code yourself.


Best,


Nico


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general

_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: Rebuilding MM under Windows - some issues

Gordon Scott-3
In reply to this post by Graham Bartlett

This may be  completely irrelevant, but I offer it as I just spent many
hours learning it.

Apparently Windows 7 will not install onto series seven CPUs, but it
doesn't say that, at best it simply aborts with an error 0xc0000225.

There are lots and lots of potential reasons why one might see that
error and finding the real cause took time.

I wonder if a similar problem might exist with SDKs.  Probably not, but...


FWIW, I had been trying to _reinstall_ Win7 onto a machine on which it
was previously working apparently just fine after a motherboard change,
but which used to pop up "nag" regular boxes saying that the CPU "was
made for a later version of Windows", and inviting me to buy a newer
copy. ... I was trying to test and prove applications on Win7, _not_ a
newer version.

I'll mention also that Win7 installed and ran well on the same machine
in both the VisualBox and VMWare Player virtual machines, except that
DirectX was not fully supported under Linux on my rather old graphics card.

Gordon.



_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: Rebuilding MM under Windows - some issues

Graham Bartlett
Thanks Gordon.  FWIW I'm running Win7 in a VirtualBox VM too, so not something I'm likely to run into.  Eventually I'm going to have to update those VMs, but for now it's not top of my priority list so long as they're still working.

Thanks Karl and Jon for your advice too.

        Graham.

-----Original Message-----
From: Gordon Scott <[hidden email]>
Sent: 17 October 2019 08:50
To: [hidden email]
Subject: Re: [micro-manager-general] Rebuilding MM under Windows - some issues


This may be  completely irrelevant, but I offer it as I just spent many hours learning it.

Apparently Windows 7 will not install onto series seven CPUs, but it doesn't say that, at best it simply aborts with an error 0xc0000225.

There are lots and lots of potential reasons why one might see that error and finding the real cause took time.

I wonder if a similar problem might exist with SDKs.  Probably not, but...


FWIW, I had been trying to _reinstall_ Win7 onto a machine on which it was previously working apparently just fine after a motherboard change, but which used to pop up "nag" regular boxes saying that the CPU "was made for a later version of Windows", and inviting me to buy a newer copy. ... I was trying to test and prove applications on Win7, _not_ a newer version.

I'll mention also that Win7 installed and ran well on the same machine in both the VisualBox and VMWare Player virtual machines, except that DirectX was not fully supported under Linux on my rather old graphics card.

Gordon.



_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general

_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: Rebuilding MM under Windows - some issues

joroy
In reply to this post by Nico Stuurman-2
Hi Nico,

I'm also interested to move to VS2019 in order to recompile the Python
bindings for Python3(>3.4).
Can I be of any help to assist you with that task?

If I were to do it on my side, do you have any recommendation of any
knowledge of pitfalls I should avoid?

Regards,

Jonathan



--
Sent from: http://micro-manager.3463995.n2.nabble.com/


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Reply | Threaded
Open this post in threaded view
|

Re: Rebuilding MM under Windows - some issues

Herricks, Thurston
Hello

I have recently gotten Micromanager to build on windows and it seems to work so far.  I was also able to build the MMCore and MMCorePy_wrap in VS2019 community but I haven't gotten around to trying the files yet.

Here is how I got it to go in VS2010 using information from threads in the MicroManager General list as well as a few github repositories.

#######
Notes on building MM in both VS2010 express and VS2019 community

Download and install your favorite python flavor.  I used Anaconda and installed it for only me as a user.

But make sure you understand where the anaconda environments are stored as you will need to link to these directories
For me this was based on the install Anaconda for users only and not system wide.
C:\Users\{MYUSERNAME}\AppData\Local\Continuum\anaconda3\envs\{my veritual enviroment}

Remember the directory path for later.

Notes on Building Micromanager

Refer to notes from:
primary instructions are listed here: https://micro-manager.org/wiki/Building_MM_on_Windows

Supplemental notes on installing software are here: https://github.com/LEB-EPFL/ht-storm/wiki/Micro-Manager-Windows-Build-Instructions

How to get Visual Studio 2010

go to
https:\\visualstudio.microsoft.com/downloads/

Scroll down to Older downloads.  This will take you to a list of older visual studio versions.
In order to download you must join the Microsoft Developer community.
Once you create a developer account and verify it, all required Microsoft software and software packages are available through this portal.

For building Micro-Manager MMCore-pywrap.

Follow the instructions given go to add remove programs

Remove all Microsoft SDKs, Microsoft Visual C++ 20XX redistributables, Microsoft SQL Server features etc.

Download but don't yet install:

Visual Studio 2010 express (en_visual_studio_2010_express_x86_dvd_510419.iso)
Windows SDK 7.1 (winsdk_web.exe),
Visual C compiler (VC-Compiler-KB2519277.exe).
Microsoft .Net 4.0 (dotNetFx40_Full_setup.exe)
appache-ant (apache-ant-1.8.1-bin.zip)
Java SDK 6 (jdk-6u45-windows-x64.exe)
Swig v4 (swigwin-4.0.1.zip)
vcpkg (https://github.com/microsoft/vcpkg)

Download and install a svn client (eg TortoiseSVN-1.13.1.28686-x64-svn-1.13.0.msi):
Use the svn to download and install the 3rdpartypublic folder from https://valelab.ucsf.edu/svn/3rdpartypublic

Set up a directory stucture:
Projects\micromanager (the latest micromanager version from github)
Projects\3rdpartypublic

Install Java SE DK 6
Unzip appache-ant and place in a known directory
set up environmental variables:  Control Pannel->System->Advanced system settings -> Enviroment Variables
Install Visual Studio 2010.
Install the Visual C compiler update.

Add New system variable named ANT_HOME with the path to the appache-ant directory
Add New system variable named JAVA_HOME with the path to the java jdk directory (eg C:\ProgramFiles\Java\jdb-XXXX where XXXX is the version)
Add edit user variable PATH to %PATH%;%ANT_HOME%\bin
Now install Windows SDK7.1

Building Micro-Manager with Python arbitrary python version

extract swigwin-4.0.1.zip and place the swigwin-4.0.1 folder into 3rdpartypublic
edit the file MMCommon.props that is located \micro-manager-mm2\buildscripts\VisualStudio\MMCommon.props
edit the variable MM_SWIG to update the path newer version of swig.exe. Check the path to make sure it is correct.
<MM_SWIG>$(MM_3RDPARTYPUBLIC)\swigwin-4.0.1\swig.exe</MM_SWIG>

Also edit the Python.Props file \micro-manager-mm2\MMCorePy_wrap\Python.props
and change the variable PythonTwoDigitVersion to the version of python you want to swig. In my case this variable was changed from 27 to 37.
<PythonTwoDigitVersion>37</PythonTwoDigitVersion>
Also change the <PythonDir> directory to the anaconda directory or the virtual environment with the python version you want to interface with micromanager. In my case I just used user anaconda directory:
<PythonDir>C:\Users\therri\AppData\Local\Continuum\anaconda3</PythonDir> but this will be a different directory depending on how you installed anaconda or python.

From my limited testing the newer version swig-4.0.1 is needed for python>=3.7 and the version of swig supplied by the val lab in the 3rdpartypublic works for python=<3.6

Additional notes:
I got MMCorePy-wrap to build succesfully on Visual Studio Community 2019 with Windows SDK 10.0, Platform toolset v142, Java SE DK 13, appache-ant 1.10.7

Change the ANT_HOME path to point to the latest version
Change the JAVA_HOME path to also point to the updated version
install unzip and place vcpkg folder in the root directory (eg C:\ though I am not sure how to organize the libaries very well)
Use the Windows PowerShell to install the boost library (and if needed openCV with Cuda or eigan super fun times)
while in the vcpkg directory eg C:\vcpkg>
type the command .\vckpg install boost:x64-windows though if you are on a 32 bit machine use .\vckpg install boost:x86-windows
This takes about 30-40 minutes
Then type the command .\vcpkg integrate install
Now any library installed by vckpg should be available to Visual Studio (I think?).

The newer version of VC++ has the correct snprintf function so the definitions of define snprintf _snprintf will cause a conflict with the compiler.  Do a search replace of   " define snprintf _snprintf" with "#define snprintf _snprintf" throughout the whole solution.  Not really too sure if that is the best idea but it worked for me.  Also you may need to follow this advice https://github.com/zfphil/micro-manager-python3 and open "pyport.h" and replace "inttypes.h" with "stdint.h".  I tried adding other stdint.h files that are supposedly compliant but they didn't work.

edit MMCommon.props though I am not sure if these are needed after using the integrate install command or not.
I may just be breaking the path and causing the compiler to search for compatible libraries.
<MM_BOOST_INCLUDEDIR>C:\vckpg\installed\x64-windows\include\boost</MM_BOOST_INCLUDEDIR>
<MM_BOOST_LIBDIR>C:\vckpg\installed\x64-windows\lib</MM_BOOST_LIBDIR>



-----Original Message-----
From: joroy <[hidden email]>
Sent: Thursday, January 30, 2020 11:48 AM
To: [hidden email]
Subject: Re: [micro-manager-general] Rebuilding MM under Windows - some issues

Hi Nico,

I'm also interested to move to VS2019 in order to recompile the Python bindings for Python3(>3.4).
Can I be of any help to assist you with that task?

If I were to do it on my side, do you have any recommendation of any knowledge of pitfalls I should avoid?

Regards,

Jonathan



--
Sent from: https://urldefense.proofpoint.com/v2/url?u=http-3A__micro-2Dmanager.3463995.n2.nabble.com_&d=DwICAg&c=aBkXpkKi7gN5fe5MqrMaN-VmRugaRb1IDRfSv2xVRy0&r=h4YfiGR4aAHMi43yVq0IFshuV6TYJe0V-y3FYW2uPfYdRbjPLVk_9Z10ag8oU3IR&m=6jCsNQquzZepEb3nTvYggoG8QdtkZthcvl5kWyBxsCM&s=T73TF-XPKJAe6Zx_ZxZSS-YKx05YJuuMY3DpmETcJ-8&e=


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_micro-2Dmanager-2Dgeneral&d=DwICAg&c=aBkXpkKi7gN5fe5MqrMaN-VmRugaRb1IDRfSv2xVRy0&r=h4YfiGR4aAHMi43yVq0IFshuV6TYJe0V-y3FYW2uPfYdRbjPLVk_9Z10ag8oU3IR&m=6jCsNQquzZepEb3nTvYggoG8QdtkZthcvl5kWyBxsCM&s=hwlo47Yy0mWitxmVjHXk3XuA1A8N-DadJQqVA5h7Rro&e=
CONFIDENTIALITY NOTICE: This e-mail or fax message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information protected by law. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general