Alaska Software Inc. - IDSC on DLLcall
Username: Password:
AuthorTopic: IDSC on DLLcall
Jan GroenesteinIDSC on DLLcall
on Thu, 19 Jun 2008 16:09:00 +0200
Dear collegues,

I encountered a problem on the computers of one of our clients. Every time
our .EXE tries to
call an external .DLL the error shown below occurs. The same .exe works
without problems on
other computers. The client uses WinXP on his computers, I think the problem
lies in some OS
setting. Has anyone seen something like this before ?

Kind regards,
Jan Groenestein


----------------------------------------------------------------------------
--
ERROR LOG of "C:\GB8\Boom.exe" Date: 18-06-2008 15:10:44

Xbase++ version     : Xbase++ (R) Version 1.90.331
Operating system    : Windows XP 05.01 Build 02600 Service Pack 1
----------------------------------------------------------------------------
--
oError:args         :
          -> VALTYPE: C VALUE: USER32.DLL
          -> VALTYPE: N VALUE: 32
          -> VALTYPE: C VALUE: GetSystemMetrics
          -> VALTYPE: N VALUE: 2
oError:canDefault   : Y
oError:canRetry     : N
oError:canSubstitute: N
oError:cargo        : NIL
oError:description  : Internal data structures corrupted
oError:filename     :
oError:genCode      :         41
oError:operation    : dllPrepareCall
oError:osCode       :          0
oError:severity     :          2
oError:subCode      :          5
oError:subSystem    : BASE
oError:thread       :          3
oError:tries        :          0
----------------------------------------------------------------------------
--
CALLSTACK:
----------------------------------------------------------------------------
--
Called from XBPGETSYSTEMMETRICS(294)
Called from XBPMULTICELLCANVAS:CREATE(128)
Called from XBPQUICKBROWSE:CREATE(352)
Called from KIESLIJST(2289)
Called from SELSPECKIEKEY(6405)
Called from (B)SELCRITINIT(644)
Called from GBBUTTON:LBUP(2365)
Called from RAPPORT(367)
Pascal BoivinRe: IDSC on DLLcall
on Thu, 19 Jun 2008 13:19:12 -0400
Try to run your app within "Dependency Walker".  Look at the log window
after you get the IDSC.  I'm pretty sure you will get more details
there.  Something like loading User32.dll from the temp folder instead
of system32 (pretty usual for virus infected computer!).