Mike,

Issue resolved. I was shown the glories of OnStartPage and do not need FoxISAPI. Thanks for the help, it was a learning experience.

>>Mike,
>>
>>My apologies for the curt reply. Peace?
>
>I'm cool.
>
>>4. I then reread the MSDN doc (past the Foxweb example) and saw the FoxISAPI commands like "Status" and stuff. I thought, "aha, a way to test FoxISAPI itself and narrow down the problem." I tried http://localhost/scripts/foxisapi.dll/Status and got the 500 error.
>
>Here's where we need to look, IMO. You should at least be able to get this far. So the question is, why are you getting an internal server error? Is there any information on the error page that you get (there should at least be a clue)? If foxisapi.dll were in the wrong directory, you'd get a "can't find file" error, or something like it, so we know it's in the right place. My SWAG is that something in the Init failed. I'll have to check at work tomorrow to see what the possible failures are (home machine is so hosed right now).
>
>> Tried the more explicit http://192.168.0.1/... and no go. Tried my actual web address as well, no go, still getting 500 error.
>
>If localhost doesn't work, nothing else will either.
>
>>5. Again, since this is a simple example, I began to lean heavily on the idea that my environment must be hosed.
>
>I'm still skeptical about this one.
>
>>6. FWIW, between each of these I shut down the IIS server, then restarted it,
>
>IISRESET from a command window (no, not that command window) is your friend.
>
>>7. I have not yet done this next step, which is recompiling FoxISAPI from the source,
>
>Won't do you any good. I'm not certain, but I'll bet the source is older than the latest update, and the compiler will yack about not finding version.rc (which you can safely ignore).
>
>> since I don't yet have a serious justification for doing so, and am likely to get bogged down in C++ for a couple of hours.
>
>Actually, even a C++ novice could compile it in about five minutes. Again, though, there's no need.
>
>>8. It was at this point that I searched MSDN online for FoxISAPI+2000, wondering if there was a known issue with Win 2000.
>
>See my previous message. If there were a known issue, I'd be one of the first to know. :-)
>
>>Thanks for the holiday replies.
>
>Heh, I have no life until we ship 7.0. Might as well send a few RTFM flames on the UT while I'm waiting on tests to run. :-) I'll check the foxisapi source tomorrow to see what we can do to get you running.