09-13-04 10:56 PM
David,
Your comments have been reviewed by the vendor and we're now receiving
their support. They've sent me the DLL source code which you wanted to take
a look at, but I'm not sure how to get it to you. Also these
amplifications:
- The apps do NOT use STDIN/STDOUT. They are WIN-CGI apps, not Standard
CGI. Win-CGI apps use an INI file created by the server to get the CGI
data. NOT StdIn/StdOut IS2WCGI.DLL translates the data between the Server
and the INI file. I guess it actually creates the ini file from data it
retrieves from the server.
- The apps using the WIN-CGI protocol are 16-bit exe's. Maybe there is
some new restriction for 32 bit only?
Thanks for your support. It looks like we are on the road to resolving
this one.
Phil
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:ObZdwU6lEHA.2968@TK2MSFTNGP14.phx.gbl...
>I do not think that XPSP2 is preventing IS2WCGI.DLL to run. Based on its
> description (I wish I can look at the source code from somewhere), it
> sounds
> like it is a simple ISAPI DLL that is calling CreateProcess to execute
> some
> other EXE, which does the real work. Lots of "Simple ISAPI DLLs"
> definitely
> continue to work on XPSP2.
>
> Thus, it is far more likely for the EXE to be failing on XPSP2 due to
> security changes (it's doing the "real work", after all) than IS2WCGI.DLL
> since IS2WCGI.DLL is a simple wrapper. You need to find support for the
> wrapped EXE.
>
> FYI: All recent IIS versions are perfectly able to run the CGI EXE
> directly -- there is no need to "shim" the CGI via a wrapper ISAPI -- so
> you
> may be able to run clogin.exe directly. If it doesn't work, obviously
> IS2WCGI is not necessarily "the problem".
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "Phil Borod" <miamipab1@(nospam)aol.com> wrote in message
> news:eVs%23VszlEHA.712@TK2MSFTNGP09.phx.gbl...
> Has anybody been able to get the ISAPI IS2WCGI.DLL to run on XP-SP2?
> I'm
> sure that there are some security settings that have to be changed but I
> can't figure out which ones they are. It ran fine before SP2, but now with
> the tighter SP2 security IIS-5.1 starts to load the page but then the OS
> stops it from returning the html output.
>
>
>
>
>
>
>
[ Post a follow-up to this message ]
|