Running PfE off-line on a single PC to process data from JEOL and CAMECA epmas

[David Steele]

My current off-line (laptop) setup enables me to process PfE data acquired on the QUT JEOL 8530F EPMA.  However in the near future I hope to be acquiring data from Karsten's CAMECA SX100 at UTas (running PfE) and would like to be able to post-acq process this data on the same laptop (running Win7-64).

Obviously I have to have the two different 'sets' of config and standard, setup files (motors.dat, scalars.dat, crystals.dat, probewin.ini, etc.) for the individual instruments.

My question is how is it best to organise this on a single PC or laptop?  I presume it is not possible to install and use "C:/Probe Software - JEOL" and C:/Probe Software - CAMECA" directories (and run PfE-JEOL and PfE-CAMECA icons/shortcuts....).  However, is it possible to have specific JEOL and CAMECA probewin.ini files in the normal C:/Probe Software directory and simply rename one or the other as needed? What about crystals.dat and the other instrument specific .dat and .mdb files?   

I figure very few of us actually have access to both sides of the EPMA instrument fence so most PfE don't have to concern themselves with this, but John and a few others in Probe Software have to deal with mdb files from both PfE users of instruments, if only in demo mode, so I assume there is an answer 'out there'!

Many thanks in advance,

David

[John Donovan]

My current off-line (laptop) setup enables me to process PfE data acquired on the QUT JEOL 8530F EPMA.  However in the near future I hope to be acquiring data from Karsten's CAMECA SX100 at UTas (running PfE) and would like to be able to post-acq process this data on the same laptop (running Win7-64).

Hi David,
Well if you just want to re-process data in Probe for EPMA you don't need to do anything at all. Simply click "No" to the first question to connect to the instrument, and all the software data re-processing features are there for you for files from either instrument type.

Now, if you really want to have two different "instrument" configurations for running PFE in "demo" (why do you need this?), you can first open a probe run in off-line mode as mentioned above, and then use the File | Export Probe Configuration Files menu to export the MDB file config files to the current app folder, then exit PFE and run it again and this time answer "Yes" to the first question to connect to the instrument in demo mode as described here:

http://smf.probesoftware.com/index.php?topic=42.msg659#msg659

On the other hand, what I do usually, since I often just want to switch between a generic Cameca config vs a generic JEOL config, is simply write a small batch file to do this for me.  Then I make two shortcuts on the desktop, one for a JEOL configuration and the other for a Cameca configuration, to switch EPMA gears as it were!

copy scalers.dat "c:\probe software\probe for EPMA\scalers.dat"
copy motors.dat "c:\probe software\probe for EPMA\motors.dat"
copy probewin.ini "c:\probe software\probe for EPMA\probewin.ini"
copy detectors.dat "c:\probe software\probe for EPMA\detectors.dat"
copy crystals.dat "c:\probe software\probe for EPMA\crystals.dat"
copy elements.dat "c:\probe software\probe for EPMA\elements.dat"
copy standard.mdb "c:\probe software\probe for EPMA\standard.mdb
del "c:\probe software\probe for EPMA\probewin.elm"
del "c:\probe software\probe for EPMA\probewin.pha"
del "c:\probe software\probe for EPMA\probewin*.cal"
pause

Just create two of these batch files, each one in a folder containing a set of the appropriate config files... the stage map WMF files can just reside in the PFE app folder.

[David Steele]

Thanks John.

Since the data from the two instruments uses very different standard.mdb files and different hardware configurations I'll probably opt for your batch file approach to 'toggle' between appropriate files for each 'data source'.  Alternatively I guess the two standard database files could be 'selected' manually as needed. 

Cheers,
David

[John Donovan]

Since the data from the two instruments uses very different standard.mdb files and different hardware configurations I'll probably opt for your batch file approach to 'toggle' between appropriate files for each 'data source'.  Alternatively I guess the two standard database files could be 'selected' manually as needed. 

Hi David,
Actually it's even better than that.   

If you open a probe database file that was created using a different standard.mdb file from another lab for instance, the program will detect that as seen here:



and then offer you the following choice:



So simply click "Yea" and you will be able to open the probe MDB file and be happily on your way!

[Probeman]

Just a summary for re-processing data from Probe for EPMA on a remote computer in your office or home:

1. Install CalcZAF.msi
2. Install ProbeforEPMA.msi.
3. Run both CalcZAF and Probe for EPMA one at a time, and using the Help menu update the apps.
4. Copy your probe run MDB file (and BIM file if present) to the remote computer (in a subfolder of UserData).
5. Start Probe for EPMA.
6. Use the File | Export Probe Configuration Files menu to export the probe config files from your probe computer to your remote computer (only need to do once).
7. Re-start Probe for EPMA (usually answer No to the question: Do you want to interface to the microprobe hardware, unless you want to play with the simulation mode in Probe for EPMA).
8. Open your probe run MDB file and re-process your probe run data.

[Probeman]

Just a summary for re-processing data from Probe for EPMA on a remote computer in your office or home:

1. Install CalcZAF.msi
2. Install ProbeforEPMA.msi.
3. Run both CalcZAF and Probe for EPMA one at a time, and using the Help menu update the apps.
4. Copy your probe run MDB file (and BIM file if present) to the remote computer (in a subfolder of UserData).
5. Start Probe for EPMA.
6. Use the File | Export Probe Configuration Files menu to export the probe config files from your probe computer to your remote computer (only need to do once).
7. Re-start Probe for EPMA (usually answer No to the question: Do you want to interface to the microprobe hardware, unless you want to play with the "simulation mode" in Probe for EPMA).
8. Open your probe run MDB file and re-process your probe run data.

For those interested in learning more about using Probe for EPMA in "simulation mode" to teach students the theory and practice of EPMA (off-line and/or remotely), see this topic here:

https://smf.probesoftware.com/index.php?topic=837.0

[Probeman]

Just a summary for re-processing data from Probe for EPMA on a remote computer in your office or home:

1. Install CalcZAF.msi
2. Install ProbeforEPMA.msi.
3. Run both CalcZAF and Probe for EPMA one at a time, and using the Help menu update the apps.
4. Copy your probe run MDB file (and BIM file if present) to the remote computer (in a subfolder of UserData).
5. Start Probe for EPMA.
6. Use the File | Export Probe Configuration Files menu to export the probe config files from your probe computer to your remote computer (only need to do once).
7. Re-start Probe for EPMA (usually answer No to the question: Do you want to interface to the microprobe hardware, unless you want to play with the simulation mode in Probe for EPMA).
8. Open your probe run MDB file and re-process your probe run data.

After following the above steps, when re-processing probe data on an "off-line" PC, I should add that to avoid the message that the standard database is missing some standards, one should copy the standard.mdb file from the "on-line" PFE PC to the "off-line" PC.

This file is found in the C:\ProgramData\Probe Software\Probe for EPMA folder.

This copy operation should be performed again whenever the standard database has been edited on the "on-line" PC.

[John Donovan]

Just a summary for re-processing data from Probe for EPMA on a remote computer in your office or home:

After you obtain the CalcZAF.msi and Probe for EPMA.msi installers from our Resources page:

https://www.probesoftware.com/resources/

1. Install CalcZAF.msi
2. Install ProbeforEPMA.msi.
3. Run Probe for EPMA to create all the default folders
4. Copy your probe run MDB file (and BIM file if present) to the remote computer (in a subfolder of UserData).
5. Use the File | Export Probe Configuration Files menu to export the probe config files from your probe computer to your remote computer (only need to do once).
7. Re-start Probe for EPMA (usually answer No to the question: Do you want to interface to the microprobe hardware, unless you want to play with the simulation mode in Probe for EPMA).
8. Open your probe run MDB file and re-process your probe run data.

In addition to the above steps one might also want to copy their standard.mdb file over to the off-line computer for re-processing data.   The standard.mdb file is located in the C:\ProgramData\Probe Software\Probe for EPMA folder.

Note that the ProgramData folder may be hidden from view and so you may need to click the "show hidden files and folder" option in File Explorer.

Note that copying the standard.mdb file over to the re-procesing computer is not strictly necessary as Probe for EPMA keeps a local copy of the standard compositions used in each probe run MDB file, but having your default standard.mdb database on the re-processing computer means a couple of less mouse clicks.

[John Donovan]

Recently a colleague of ours was trying to install Probe for EPMA on an off-line computer in order to re-process data from their probe computer, and ran into some difficulties installing the software on this off-line PC.

They downloaded the CalcZAF and Probe for EPMA installers from our web site:

https://www.probesoftware.com/resources/

but when they tried to run the installers they had difficulties. It turns out the computer was running an "institutional" version of Windows that had been "locked down" by their IT department. 

Normally we always recommend to install CalcZAF/Probe for EPMA on a "standard" Windows user account, but as you all know, in order to install any new software on a Windows computer, you will need administrative access to get past the Windows User Access Control. 

This is a good thing normally (as it keeps students from installing any ol' software on your lab computers!), but in this recent instance the IT department would not give our colleague administrative access (to the computer in his own lab!), and insisted that they do the software installation themselves.

In addition, when Probe for EPMA starts up on a new computer for the first time, it creates the C:\UseData, C:\UserImages, C:\UserEDS, etc. folders and sub folders, but in this case it was unable to do so, because this computer was so "locked down".  Of course, Probe for EPMA can use any drive or folders that are specified in the Probewin.ini file (for example on drive D:\), but drive C:\ is the default.

We don't know all the details, but after several attempts the IT people were apparently unable to install our software (which simply boggles the mind) and told him it was our problem!   

Now, generally when we (or our customers) install our software on a new computer for connecting to their microprobe, we do ask that people install a normal "retail" version of Windows, for example, Windows 11 Professional. This is because we have seen instances where using an "institutional" version of Windows prevents our software from connecting to the microprobe private sub net for communication with the instrument.

But we had never seen a problem installing the software on an off-line computer for re-processing data, because as you all know, we allow our software to be installed on any computer or laptop for data reprocessing or even running the software in simulation mode for teaching or modeling:

https://smf.probesoftware.com/index.php?topic=837.0

But now, as IT departments seem to be getting more aggressive about locking down any and all computers within their reach, perhaps we need to quote what we recommend when installing Probe for EPMA on a new computer for connecting to your microprobe instrument:

-Do *not* attempt to install an "institutional distribution" of Windows from your IT department. These versions are generally "locked down" and will *not* allow the software to make network connections to your instrument. You should instead install a normal retail version of Windows 11 Professional.

even for simply installing our software on an off-line computer for re-processing your microprobe data! See attached pdf below.  It is also worth mentioning that all these computers should have Internet access just you you can update Probe for EPMA whenever you want by using the Help | Update Probe for EPMA menu...

However, attached below is a document with instructions for updating Probe for EPMA on a computer without Internet access.