Experimental Physics and Industrial Control System
|
Hi,
I’m not familiar with this particular device setup, but in general errors like this can mean that the system was able to find the original file requested but not able to load some of its dependencies. This can
be because the dependency is missing/inaccessible on the system, but also because an older/incompatible version of the requested dependency is already loaded by the IOC. A good starting point might be to run a program like dependency walker
http://www.dependencywalker.com/ on gbif64.dll and see if it detects a missing Visual Studio runtime library that you just need to install. If it doesn’t find anything missing, try starting the dependency walker
program from the same command window you would run the IOC from but after you have run dllPath.bat – that way it should then be using the same search path the IOC would later be using and it might indicate if you have any DLL incompatibilities.
Regards,
Freddie
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of CORNALL, Terry via Tech-talk
Sent: 03 February 2021 06:44
To: tech-talk at aps.anl.gov
Subject: PerkinElmer Area Detector on Windows 10 [SEC=OFFICIAL]
Hi All.
I’m running the perkinElmerIOC from the Windows 10 ADPerkinElmer areaDetector-3-8 binary distribution and I get the error:
PerkinElmer::initializeDetector, error=39 calling Acquisition_GbIF_Init(&hAcqDesc_=000001E40F1ACB40, nChannelNr=0, bEnableIRQ_=1, uiRows=1024, uiColumns=1024,bSelfInit=1, bInitAlways=0, IDType_=1, IDValue_=000001E40F1B5FC0)
Can anyone shed light on this?
I have found that error=39 means ‘Can’t load driver’ but as far as I can tell the gbif64.dll is in the right place (assuming that is the driver in question) so I don’t know how to proceed in solving this issue.
Thanks,
Terry
OFFICIAL
This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.
|
- References:
- PerkinElmer Area Detector on Windows 10 [SEC=OFFICIAL] CORNALL, Terry via Tech-talk
- Navigate by Date:
- Prev:
Base 3.16.1.0 Mogamad Amien Crombie via Tech-talk
- Next:
Re: Base 3.16.1.0 Mark Rivers via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
- Navigate by Thread:
- Prev:
PerkinElmer Area Detector on Windows 10 [SEC=OFFICIAL] CORNALL, Terry via Tech-talk
- Next:
Re: PerkinElmer Area Detector on Windows 10 [SEC=OFFICIAL] Mark Rivers via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
|
ANJ, 03 Feb 2021 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|