I believe I am getting this error because I have a runtime and developer subdirectory under the OImain directory.

I have removed all dlls and exes to both dev and run and put the appropriate engines in each.

Unless I copy all the dlls and exes back to the main directory I will get the Error 3 msg. I tried changing the registry settings to drive:\oimain\runtime or developer and stil got the same results.

I guess my question is, exactly what files need to be in the "WorkingDirectory" for an engine to be created using OECGI?

Thanks.

I think you are talking about these files…

OECGI.EXE

RCL3.DLL

REVCAP32.DLL

UTF8.DLL

Check OpenInsight help under "Open Engine", "The OECGI", "Setup", "Script Directory", "Using the Default Virtual Directory"

Well my understanding has been that those are the files needed in the cgi-bin directory which have been there. Do they need to be in both?

Bruce,

A tricky question…

I use "Apache" web server. My httpd.conf file looks like this…

  ScriptAlias /cgi-bin/ "C:/Program Files/Apache/htdocs/cgi-bin/"

  ScriptAlias /OInsight/ "c:/program files/openinsight/"

My registry settings for "My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\RevSoft\OECGI" "WorkingDirectory"=c:\program files\openinsight"

Those files "OECGI.EXE" "RCL3.DLL" "REVCAP32.DLL" "UTF8.DLL" are in my "c:\program files\openinsight" directory, and nowhere else.

Hope this helps.

Bruce,

I was looking at this the other day with another client who also uses a split dev/runtime system. To be honest I don't believe it's actually possible, as what you'd need to do is emulate the way the Windows Shortcut works, which has the "Start In" value as well as the actual link to the file in question. I think we'd need an extra entry in the registry for the location of the actual exe file, something like:

WorkingDirectory: c:\revsoft\oinsight

EngineDirectory: c:\revsoft\oinsight\dev

Then OECGI/REVCAPI could be modified to use it…

I think you'll have to ask RevSoft nicely for an enhancement :)

The Sprezzatura Group

World leaders in all things RevSoft

Richard,

I am not familiar with the inner workings of Apache but it looks like what you have done is essentially the same as a dos PATH command.

Thanks for the reply. I think Sprezz's idea is probably the answer in my situation. I am curious though as to the exact dll's exe's that would need to be in the main "working directory".

Thanks to all.

View this thread on the Works forum...