"What's with that?"

CessnaPilotBarry, on Windows, case CAN matter, but usually doesn't. If there is a GPO strictly enforcing the POSIX subsystem, then yes, case makes all the difference in the world. HOWEVER… Usually I find with GUI HTML editors that the problem is not case variation, but relative versus absolute pathing. It has been a LONG time since I even bothered with any WYSIWYG HTML editors, mostly because I can knock that code out in my sleep anymore, but I recall Front Page used to put a path in the .htm file something like..

c:\Documents and Settings\bjones\My Documents\My Pictures\photo.jpg

Now this is a path to a file kept on a local Windows computer, and belongs to a specific users profile (in this case bjones, sorry Bob you are getting mentioned again!) which means absolutely diddly squat on the internet. Also the slashes are pointing the wrong way (those are Windows UNC slashes, not URL or Unix type slashes which is the standard on the web). There usually is an option for the WYSIWYG editors to make it use relative paths. So let's say your working your HTML in your Windows workstation, and you have a folder under My Documents called HTML, and under that HTML folder you have a sub folder called images. Your absolute path would look like…

c:\Documents and Settings\bjones\My Documents\My Pictures\HTML\images\photo.jpg

But if you tell your editor to use relative paths, you will see something more along the lines of

./images/photo.jpg

Broken down, the dot slash means "subfolder from HERE" which is where the file being read is, and then define the subfolder, and file.

Hopefully I haven't lost you.

Lastly, make certain that the files you want to pull up are really in the directory they are supposed to be in, and that the web server has rights to read those files (ask your system administrator for help with that…)