My query referenced the dialog where you can add "required files" for the
excecution permission of particular ISAPI module. The browse box gives you
filter options for DLL, CGI and "all files". After adding EVERYONE to the
security attributes of the file I needed to write to (thereby solving my
problem), I was able to remove all data and suporting files from that dialog
and just leave in the ISAPI DLL name.
My next task is to try to solve my remaining problem (and your problem) --
how an ISAPI module can CREATE a file in IIS6 mode.
Best
Harry
>> Stay informed about: IIS 6 + ISAPI + Win 2003