>Dragan,
>
>Are the files there in the location you're loading from?
>
>There shouldn't be anything you have to do with static files of known types. What happens if you create a simple HTML page and reference those same scripts?
>
>Just make sure that the links are correct (although you would end up with 404 errors if they weren't found).

Found a few things I did wrong - for one, there was no * handler for static files - the above error vanished when I added that... so I got pretty much everything in order now.

Two things still confuse me:

- the version of index.html, with immediate redirection, still fires. I have edited it to require a click to link (just to see that it actually loads), but it still loads this old version

- when I switch to file mode, the server still loads two instances of my exe as a COM server. Never seen it do that in earlier versions. Any explanation?

- When I restart the IIS, these instances get stuck, and two more are loaded etc (they don't load immediately, so I don't know when exactly do they load - when the app pool is recycled, when the website is restarted or only when the whole IIS is). I have seen some references to a dll_unload in the error logs. Is it possible that my executable gets stuck on an error somewhere (just discovered that I do get some unhandled errors). I guess this will go away once it's bullet proof again (works fine on two other servers, so this is probably caused by a nearly empty database, few things are missing), without any cancel-ignore dialogs. Am I guessing right?