Calling winexec() in OI7 vs OI413 (OpenInsight 32-bit Specific)
At 09 JUN 2004 06:11:23PM Wilhelm Schmitt wrote:
In OI413 anything like: CALL WINEXEC("OINSIGHT.EXE",1) will work, in OI7 it won't, because, apparently, we can't configure write privileges, so anything that has to write to disk doesn't execute.
We currently use winexec to zip XML data on the server and send them to the client, past the CGI. Therefor, the call to utility("RUNWIN"…) is no alternative, because it will execute only locally, not through OECGI calls.
Any clues or workarounds?
Regards
Wilhelm
At 09 JUN 2004 07:25PM Pat McNerthney wrote:
Wilhelm,
I am not aware of any changes in the code between OI 4.1.3 and OI 7.0 that should cause such a symptom.
I strongly suspect it has something to do with how your web server is configured.
Pat
At 10 JUN 2004 12:04AM Wilhelm Schmitt wrote:
Pat,
we are going to take a look at the server configuration. The problem however is, that running OI7 and OI413 on the same server & same settings produces different results.
In the case of the zipping routine: OI413 creates an OS file (USRnnnn.ZIP) with filesize ] 0, while in OI7 the OS file (USRnnnn.ZIP) appears with filesize=0.
Other example: Running CALL WINEXEC("oinsight.exe",1) from within OI413 creates another instance of itself, in OI7 it doesn't.
Regards
Wilhelm
At 10 JUN 2004 02:38AM Pat McNerthney wrote:
Wilhelm,
Try terminating the string passed to WinExec with a null byte. For example:
CALL WINEXEC("oinsight.exe":\00\ ,1)
Pat
At 10 JUN 2004 06:29PM Wilhelm Schmitt wrote:
Pat,
a lot of thanks for this null-byte trick.
Wilhelm