NT4 Error with local HTML files (WNT)

[SishKebab]

When viewing locally stored HTML files, IE5.5 doesn't display images. If I then look at the properties of those images, the address looks like: 'file:///path/file.jpg' i.e. there is one / too many in the path, right after file. This also applies to links etc., but there it has no (noticable) impact. But where can i find this so I can remove this fault. I'm using NT4 with SP6a by the way.

[jdharm]

If I understand your situation correctly:

That isn't too many /'s. That is the protocol (file://) followed by a path (/path/file.jpg). The problem is that if these html files were saved from the net then the html code was saved but the source files for the pictures were not. The protocol, path and filename are good on the server with the appropriate files and directory structure, but they aren't good on your local drive unless you download the pic files and store them in the same relative directory structure. Links are no problem because the properties on them refer to a "http://" protocol which the computer correctly interprets as a request to go to the internet, not a nonexisted local file, as in the case of the pics. Pics that are stored on a different server than the html code (like advert. gifs) should work because they will be refered to with "http://" addresses too, not reletive local addresses. Or if they do have "file://" protocols they work because you did download the html files the links refer to locally and in the proper relative directory.

Hope that helps clear things up.

Josh

"Some mornings it just doesn't seem worth it to gnaw through the leather straps."

[jdharm]

That last line, starting with "Of if they do...", is refering to links that work. Sorry for the confusion.

Josh

"Some mornings it just doesn't seem worth it to gnaw through the leather straps."

[SishKebab]

I did as you suggested and verified all the links, but without result. So I tried to view the same page with Netscape, which worked fine. Then did the obvious: uninstall IE5, and then reinstall.... Now everything is fine again....

Thanks anyway for your reply.