I found out 2 things - but am looking at how to move forward.
About the 500 Error:
My XP Pro setup C:\Inetpub\Scripts when I installed IIS. I first tried to copy foxISAPI to C:\Inetpub\scripts. This scripts directory is not available through the Default Web Site tree, but it [C:\Inetpub\Scripts] can be seen in DOS or Explorer. Calling foxISAPI.DLL from there pushed the 500 error page.

So I set up a virtual direcory [foxISAPI] in the path C:\Inetpub. The virtual directory is not available through explorer. For some reason, the copy of foxISAPI.DLL and INI [in C:\Inetpub\Scripts] showed up there. So I deleted them from C:\InetPub\Scripts, and viola - they were gone from the virtual folder [localhost/foxISapi/scripts]. So I copied the original foxISAPI files from VFP 7 to the virtual directory. I used explorer to "copy", then went into IIS manager, selected the foxISAPI/Script [virtual] folder. I then right clicked and clicked open and was able to paste to the virtual folder.

The files then also showed in the physical folder C:\Inetpub\Scripts - so I am trying to understand this in relation to the new error when I address the call:

//localhost/foxISAPI/Scripts/foxISAPI.DLL/tfoxserver.tfoxisapi.helloworl

My struggles have now evolved to this error:
FoxISAPI failed CoCreation Error 8000????? - I have the actual error somewhere.

Any Ideas on how to approach the CoCreation error?

Thanks


The documentation I am working from is W2K and NT4 - nothing relating to XP at all.


>Hi Terry,
>
>>Thanks - I have moved from HTTP 400, 404 and now I am at HTTP 500 - I guess thats progress {:-)!
>
>500 is an internal server error. If the web server is otherwise working, this usually indicates a crash in the ISAPI extension. You can check the eventlog for these type of errors. The original FOXISAPI sample contains a lot of code that would cause such a crash when anything went wrong.
>
>Christof