Quick question for everyone about the behavior of the latest updates on WinXP with Athena and Artemis et al. I manually unzipped all the updates and ran into the following error (which is likely due to my own problems). When I click on the hephaestus.bat file (WinXP), I get "The procedure entry point _FIIfexp_ could not be located in the dynamic link library DFORRT.dll." in a dialog box, then everything closes. This is also the case for Artemis.bat and Athena.bat. My version of IFEFFIT that was not updated does not have this problem. Copying the former version of DFORRT.dll from my working installation does not appear to help either. Going thru the updates from the start, I found that this error arises in update 007 and 008, but not 006. The same behavior happens for me if I use the autoupdater, rather than manually installing the updates. Sixpack seems to be unaffected. Anyone have any idea or seen this before? Sam ******************************************** Sam Webb SSRL/SLAC Bldg. 137, MS 69 2575 Sand Hill Rd. Menlo Park, CA 94025 Phone: (650)-926-3734 FAX: (650)-926-4100 E-mail: samwebb@slac.stanford.edu *******************************************
On Monday 10 May 2004 03:44 pm, Webb, Samuel M. wrote:
Quick question for everyone about the behavior of the latest updates on WinXP with Athena and Artemis et al. I manually unzipped all the updates and ran into the following error (which is likely due to my own problems). When I click on the hephaestus.bat file (WinXP), I get "The procedure entry point _FIIfexp_ could not be located in the dynamic link library DFORRT.dll." in a dialog box, then everything closes. This is also the case for Artemis.bat and Athena.bat. My version of IFEFFIT that was not updated does not have this problem. Copying the former version of DFORRT.dll from my working installation does not appear to help either. Going thru the updates from the start, I found that this error arises in update 007 and 008, but not 006. The same behavior happens for me if I use the autoupdater, rather than manually installing the updates. Sixpack seems to be unaffected. Anyone have any idea or seen this before?
Sam, One thing that occured to me just now is to make sure that the conmtents of the bat file all make sense, i.e. that the environment variables are all set and all point to sensible locations. B -- Bruce Ravel ----------------------------------- ravel@phys.washington.edu Code 6134, Building 3, Room 405 Naval Research Laboratory phone: (1) 202 767 2268 Washington DC 20375, USA fax: (1) 202 767 4642 NRL Synchrotron Radiation Consortium (NRL-SRC) Beamlines X11a, X11b, X23b National Synchrotron Light Source Brookhaven National Laboratory, Upton, NY 11973 My homepage: http://feff.phys.washington.edu/~ravel EXAFS software: http://feff.phys.washington.edu/~ravel/software/exafs/
Hi Sam, On Mon, 10 May 2004, Webb, Samuel M. wrote:
Quick question for everyone about the behavior of the latest updates on WinXP with Athena and Artemis et al. I manually unzipped all the updates and ran into the following error (which is likely due to my own problems). When I click on the hephaestus.bat file (WinXP), I get "The procedure entry point _FIIfexp_ could not be located in the dynamic link library DFORRT.dll." in a dialog box, then everything closes. This is also the case for Artemis.bat and Athena.bat. My version of IFEFFIT that was not updated does not have this problem. Copying the former version of DFORRT.dll from my working installation does not appear to help either. Going thru the updates from the start, I found that this error arises in update 007 and 008, but not 006. The same behavior happens for me if I use the autoupdater, rather than manually installing the updates. Sixpack seems to be unaffected. Anyone have any idea or seen this before?
I've never heard of this, and don't know what FIIfexp might mean. There wasn't much change between 006 and 007 -- certainly not to DFORRT.dll or ifeffit_10.dll, so it seems pretty strange. It does appear that the DFORRT.dll in ifeffit/sixpack/ is older than the one in ifeffit/. I'd be surprised if that had an affect, but it's easy enough to try both versions of the dll. There's also a MSVCRT.dll that you could try moving away, so that the system one gets used. Does this problem happen with ifeffit.bat? One thing that did change between 006 and 007 was that the perl-generated executables got smaller by a factor of 2. This might suggest that the perl codes depend more heavily on other dlls for code, but I don't know any of the details. --Matt
Sam,
I ran into this about a week before the APS Users Meeting. Right after I
upgraded to the newest version of Athena/Artemis/et al. I did find the
solution. Check in your system32 subdirectory (I think, it may be system) of
the windows directory. There could be a DFORRT.dll located there. The
DFORRT.dll file in that location was rather date, possibly from '99. This old
file was set in the windows path, and it was accessing it even though newer
versions were available. I found that replacing the old DFORRT.dll file with
the newer version fixed the problem. You might have to do a google search if
you don't have a newer version on your computer. If you can't find a newer
version of DFORRT.dll that works, I'll post the one that I am using up online.
Sorry guys, I guess I should have sent something to the list about this
immediately..
Aaron Stuckey
Quoting "Webb, Samuel M."
Quick question for everyone about the behavior of the latest updates on WinXP with Athena and Artemis et al. I manually unzipped all the updates and ran into the following error (which is likely due to my own problems). When I click on the hephaestus.bat file (WinXP), I get "The procedure entry point _FIIfexp_ could not be located in the dynamic link library DFORRT.dll." in a dialog box, then everything closes. This is also the case for Artemis.bat and Athena.bat. My version of IFEFFIT that was not updated does not have this problem. Copying the former version of DFORRT.dll from my working installation does not appear to help either. Going thru the updates from the start, I found that this error arises in update 007 and 008, but not 006. The same behavior happens for me if I use the autoupdater, rather than manually installing the updates. Sixpack seems to be unaffected. Anyone have any idea or seen this before?
Sam
******************************************** Sam Webb SSRL/SLAC Bldg. 137, MS 69 2575 Sand Hill Rd. Menlo Park, CA 94025
Phone: (650)-926-3734 FAX: (650)-926-4100 E-mail: samwebb@slac.stanford.edu ******************************************* _______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit
-- The best laid schemes of Mice and Men oft go awry, And leave us nothing but grief and pain,For promised joy! Robert Burns (1759 - 1796), To a Mouse
participants (4)
-
Aaron Stuckey -
Bruce Ravel -
Matt Newville -
Webb, Samuel M.