Most recent edit on 2007-01-27 13:04:00 by DavidMeeker
Additions:
You may have to define this path differently depending on your Wine setup.
Deletions:
You may have to define this path differently depending on the location of your Wine setup.
Edited on 2007-01-27 12:59:49 by DavidMeeker
Additions:
Running FEMM on Linux via Wine
FEMM 3.4
FEMM 4.0.1
OctaveFEMM
Deletions:
Running FEMM on Linux via Wine
FEMM 3.4
FEMM 4.0.1
OctaveFEMM
Edited on 2007-01-27 12:58:23 by DavidMeeker
Additions:
Many of the examples Octave scripts on the FEMM website refer to the "c:\Program Files" directory using the alternative form "c:\progra~1". While these two directories are equivalent on native Windows systems, they may not be in Wine. This situation can be remedied by creating a symbolic link to "Program Files" from "progra~1", e.g.dmeeker@labrat:~/.wine/drive_c$ ln -s "Program Files" progra~1
Edited on 2007-01-27 00:32:53 by DavidMeeker
Additions:
Next, the Octave search path needs to be amended to find the OctaveFEMM functions. This can be done by creating/editing the .octaverc file in your home directory. Add the line:
Last, the openfemm.m function in the OctaveFEMM function needs to be modified in two ways:
Deletions:
First, the Octave search path needs to be amended to find the OctaveFEMM functions. This can be done by creating/editing the .octaverc file in your home directory. Add the line:
Second, the openfemm.m function in the OctaveFEMM function needs to be modified in two ways:
Edited on 2007-01-27 00:32:05 by DavidMeeker
Additions:
Amazingly enough, OctaveFEMM works under Linux and will allow a native Linux implementation of Octave to interact with FEMM 4.0.1 running under Wine. To get OctaveFEMM running correctly, the first download and run the OctaveFEMM self-installing executable distribution. The OctaveFEMM functions will then be stored in the OctaveFEMM directory of your Wine implementation's c-drive.
First, the Octave search path needs to be amended to find the OctaveFEMM functions. This can be done by creating/editing the .octaverc file in your home directory. Add the line:
Second, the openfemm.m function in the OctaveFEMM function needs to be modified in two ways:
Deletions:
Amazingly enough, OctaveFEMM works under Linux and will allow a native Linux implementation of Octave to interact with FEMM 4.0.1 running under Wine. To OctaveFEMM running correctly, the first download and run the OctaveFEMM self-installing executable distribution. The OctaveFEMM functions will then be stored in the OctaveFEMM directory of your Wine implementation's c-drive.
First, the Octave search path needs to be amended to find the OctaveFEMM functions. This can be done by creating/editing the .octaverc file in your home directory. Add the line:
Second, the openfemm.m function in the OctaveFEMM function needs to be modified in two ways:
Edited on 2007-01-27 00:29:46 by DavidMeeker
Additions:
OctaveFEMM
Deletions:
OctaveFEMM
Edited on 2007-01-27 00:28:59 by DavidMeeker
Additions:
OctaveFEMM
Amazingly enough, OctaveFEMM works under Linux and will allow a native Linux implementation of Octave to interact with FEMM 4.0.1 running under Wine. To OctaveFEMM running correctly, the first download and run the OctaveFEMM self-installing executable distribution. The OctaveFEMM functions will then be stored in the OctaveFEMM directory of your Wine implementation's c-drive.
First, the Octave search path needs to be amended to find the OctaveFEMM functions. This can be done by creating/editing the .octaverc file in your home directory. Add the line:
LOADPATH = [ '~/.wine/drive_c/OctaveFEMM//', LOADPATH ];
You may have to define this path differently depending on the location of your Wine setup.
Second, the openfemm.m function in the OctaveFEMM function needs to be modified in two ways:
- The path to the femm binary directory needs to be modified to point to the location of the femm binary directory as seen by Linux;
- The system call that starts up femm needs to be modified so that it starts up femm.exe using Wine.
Here is an example modified version of openfemm.m. You may have to change the paths slightly, depending on the configuration of paths in your installation of Wine.
Edited on 2007-01-26 09:50:15 by DavidMeeker
Additions:
The only functionality that appears to be broken with FEMM 4.0.1 and Wine 0.9.12 is the materials library. The materials library works correctly if Wine is run with a native version of comctl32.dll.
Deletions:
The only functionality that appears to be broken with FEMM 4.0.1 and Wine 0.9.12 is the material library. The materials library works correctly if Wine is run with a native version of comctl32.dll.
Edited on 2007-01-26 09:49:24 by DavidMeeker
No differences.
Edited on 2007-01-26 09:49:10 by DavidMeeker
Additions:
FEMM can be run on Linux machines using Wine. Performance of the program is about the same running on Linux with Wine compared to running natively on Windows. To get the program to look right visually, you will also have to find copies of arial.ttf and symbol.ttf and install them in Wine's windows/fonts directory.
Deletions:
FEMM can be run on Linux machines using Wine. Performance of the program is about the same running on Linux with Wine compared to running natively on Windows.
To get the program to look right visually, you will also have to find copies of arial.ttf and symbol.ttf and install them in Wine's windows/fonts directory.
To get the program to look right visually, arial.ttf and symbol.ttf are needed.
Edited on 2007-01-26 09:48:23 by DavidMeeker
Additions:
An archive is available which contains FEMM 3.4.2 executables and source that have been modified in small ways to work around imperfections in Wine. Knoppix 3.7 with Wine 20040813 was used as the test platform. The only change noticeable to the user is that the materials library has been rolled back to the v3.3 form. The treeview used in the v3.4 version causes the program to hang when it runs in Wine.
Deletions:
An archive is available which contains FEMM 3.4.2 executables and source that have been modified in small ways to work around imperfections in Wine. Knoppix 3.7 with Wine 20040813 was used as the test platform. The only change noticeable to the user is that the materials library has been rolled back to the v3.3 form. The treeview used in the v3.4 version causes the program to hang when it runs in Wine. Overall, there appears to be no significant speed difference running natively on a Windows machine versus running on a Linux machine under Wine.
Edited on 2007-01-25 22:06:54 by DavidMeeker
Additions:
FEMM can be run on Linux machines using Wine. Performance of the program is about the same running on Linux with Wine compared to running natively on Windows.
Deletions:
FEMM can be run on Linux machines using Wine.
Edited on 2007-01-25 22:06:08 by DavidMeeker
Additions:
The only functionality that appears to be broken with FEMM 4.0.1 and Wine 0.9.12 is the material library. The materials library works correctly if Wine is run with a native version of comctl32.dll.
Deletions:
The only functionality that appears to be broken with FEMM 4.0.1 and the testbed version of Wine is the material library. The materials library works correctly if Wine is run with a native version of comctl32.dll.
Edited on 2007-01-25 22:05:15 by DavidMeeker
Additions:
Running FEMM on Linux via Wine
FEMM can be run on Linux machines using Wine.
FEMM 3.4
An archive is available which contains FEMM 3.4.2 executables and source that have been modified in small ways to work around imperfections in Wine. Knoppix 3.7 with Wine 20040813 was used as the test platform. The only change noticeable to the user is that the materials library has been rolled back to the v3.3 form. The treeview used in the v3.4 version causes the program to hang when it runs in Wine. Overall, there appears to be no significant speed difference running natively on a Windows machine versus running on a Linux machine under Wine.
FEMM 4.0.1
FEMM 4.0.1 was tested using Knoppix 5.1.1 with Wine 0.9.12. The standard self-installing executable distribution works well under this installation of Wine, as long as the suitable version of msvcrt.dll and mfc42.dll are installed in the same directory as the femm.exe executable (c:\Program Files\femm40\bin in a regular Windows installation).
The only functionality that appears to be broken with FEMM 4.0.1 and the testbed version of Wine is the material library. The materials library works correctly if Wine is run with a native version of comctl32.dll.
To get the program to look right visually, arial.ttf and symbol.ttf are needed.
Deletions:
Running FEMM 3.4 on Linux under Wine
FEMM can be run on Linux machines using Wine. An archive is available which contains FEMM 3.4.2 executables and source that have been modified in small ways to work around imperfections in Wine. Knoppix 3.7 with Wine 20040813 was used as the test platform. The only change noticeable to the user is that the materials library has been rolled back to the v3.3 form--the tree used in the v3.4 version causes the program to hang when it runs in Wine. Overall, there appears to be no significant speed difference running natively on a Windows machine versus running on a Linux machine under Wine.
Oldest known version of this page was edited on 2006-11-29 01:00:04 by DavidMeeker []
Page view:
Running FEMM 3.4 on Linux under Wine
FEMM can be run on Linux machines using
Wine. An
archive is available which contains FEMM 3.4.2 executables and source that have been modified in small ways to work around imperfections in Wine.
Knoppix 3.7 with Wine 20040813 was used as the test platform. The only change noticeable to the user is that the materials library has been rolled back to the v3.3 form--the tree used in the v3.4 version causes the program to hang when it runs in Wine. Overall, there appears to be no significant speed difference running natively on a Windows machine versus running on a Linux machine under Wine.
To get the program to look right visually, you will also have to find copies of arial.ttf and symbol.ttf and install them in Wine's windows/fonts directory.