SRIM, “The Stopping and Range of Ions in Matter” is an useful program for Nuclear Physicists and Engineers, and now it comes in the 2008 version. But…
Unfortunately if you try to run on wine, your mileage may vary. It’s a pity because a lot of Nuclear Engineers colleagues run Ubuntu on their PCs, or just Linux.
As from version 2011, SRIM installation does not need any manual operation after installation. Installing is extracting an SFX file and the VERSION file issue on WINE is not there anymore.
I’m leaving all the past notes here for anyone using the older versions.
Thanks to everyone who will report sucess and issues here or directly to the wine APPDB page.
UPDATE (14/Jan/2009): thanks to Stano Antalic(smyonpa on Gmail e-mail) and this post http://bugs.winehq.org/show_bug.cgi?id=10558 I was able to find an alternate fix that does not involve creating a new VERSION file or taking it from a windows installation. The file is reguarly created under a Data\verXXXX.tmp name, the installer probably just fails renaming it or copying it into VERSION that remains empty. Simply copying it over the empty VERSION fixes the issue.
Read a step by step HOWTO about it on the winehq mantainer page (myself)
it should be ok for SRIM2006 too, but cannot confirm. Someone can?
Before applying the following steps, please read the HOWTO above.
While recovering between study sessions, I tried to find some info about the issue. After a bit of Googling, I found this post @WineHQ (t.t xerox_xerox2000 at yahoo.co.uk), where an explanation of the issue is given. The problem is file SRIM 2008/Data/VERSION that is created empty during the Wine installation. If you replace it with the proper file, say from the same windows installed version, SRIM will run flawlessy.
File content for my Windows file where
SRIM software version.
See VERSION.rtf for details.
Of course it may not work if you have a different version. I think it should. I suspect I must be running version 2008.4 on wine but I used VERSION file from 2008.3. I will look better into this later. As a matter of fact, I’ll try to see if we can solve the problem…
More on this later. HANW.
Tested on wine-1.0.1, SRIM 2008.4, Ubuntu Intrepid Ibex 8.10 on x86 32bit.
UPDATE: I can confirm the file data/VERSION is used during program operation. An intro screen is displayed the first two times you run the program, and the Version value in the right upper corner is fetched from data/VERSION. In turn, I strongly suspect the first row from version.rtf is fetched during installation using ADO to determine program version. Thus, installation over “stock”WINE probably fails opening correctly version.rtf and fetching the first row, giving birth to a 0 bit data/VERSION file, which in turns, wreaks havoc when the splash screen tries to show the program version the first two times we run the program after installation.
The shortest path to victory seems to me asking James Ziegler to use a different method to determine the program version during runtime, or resort to creating the correct file manually.
I’d like to do some regression tests to confirm everything is actually running well under WINE.
More on this later.BB
Another useful information from daid:
“Another useful tip is that the TRIM.DAT input files must be in DOS format (End of File with ^Z) and not UNIX format (End of File with ^D). For files created by SRIM through wine, this should be no problem.
However, if you have code to create TRIM.DAT files (say, C++ routines for input into TRIM), then you’ll need to convert the file type. This can be done many ways, for example with the command line tool dos2unix, or in many editors, such as vim, by :set ff=dos”