Bernhard:

   did you receive my messages via the mailing list? Somehow I am not 
receiving the copies via BLACKBOX. I am wondering if these messages are 
distributed or lost.

Thanks,
Wojtek

On Wed, 13 Jan 2010, Wojtek Skulski wrote:

> Bernard:
>
> I thought the attached e-mail would go to the list, but somehow it did not.
>
>  Thank you for the suggestions. Here is the "solution" to my DLL problem. I 
> say "solution" because it is a dirty fix which works for a reason which is 
> beyond my level of understanding.
>
> Wojtek
>
> ---------- Forwarded message ----------
> Date: Tue, 12 Jan 2010 19:46:20 -0500 (EST)
> From: Wojtek Skulski <skulski@pas.rochester.edu>
> To: Douglas G. Danforth <danforth@GREENWOODFARM.COM>
> Cc: BLACKBOX@LISTS.OBERON.CH
> Subject: Re: [BLACKBOX] Calling DLL's
>
> OK, I "solved" the problem. I right-clicked the BlackBox 1.5 icon on the 
> desktop, selected "Properties", opened the Compatibility tab, and selected 
> Compatibility mode "Windows 2000".
>
> Then I launched BB, opened the DDCtApi panel, and it started OK. Here is the 
> message in the BB Log:
> DDCtDisk loaded rev: 04/02/09
> DDCtApi loaded rev: 03/30/09
>
> These are messages from the Init section of my BB modules. In particular, the 
> Api is loaded and all the interactors are populated as expected.
>
> I then unchecked the compatibility and voila! The DLL is not loaded. I then 
> set the compatibility again, and voila! DLL is loaded.
>
> Now, can anyone explain to me, why BB used to load the DLL on September 25 
> 2009 when I last ran the data acquisition, then stopped loading the DLL, and 
> now it requires compatibility mode?
>
> Note, no other changes! I did not touch the PATH. The DLL files are in the 
> same places with and without the compatibility.
>
> I am running Windows XP Professional on this laptop. After Sept 25 there must 
> have been Windows Update. Probably more than one. This could have screwed up 
> the DLL loading process. But how is that possible?
>
> W
>
> PS: I turned the compatibility on/off a few times to make sure it makes the 
> difference. It does. With compatibility not set the DLL is not loaded. With 
> compatibility set to Win 2k it is loaded and the Api panel works as it used 
> to in September 2009.
>
>
> On Tue, 12 Jan 2010, Douglas G. Danforth wrote:
>
>> Wojtek Skulski wrote:
>>       command error: code file for DllToFx not found
>> 
>> Hence the search path used by BB has changed
>> (or the system is completely screwed).
>> 
>> You have put the dll in every location claimed to be searched
>> by BB so the internal search process must have changed.
>> 
>> The error message originates from Std/Mod/Loader
>> which isn't much help.  Perhaps making a copy of the Kernel
>> and placing an ASSERT where it is attempting to call the loader
>> for your dll might give an indication of what path it is attempting
>> to search.
>> 
>> -Doug
>> 
>> 
>> 
>> ---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to 
>> LISTSERV@LISTS.OBERON.CH
>> 
>M-AS