I cannot open Metastream files that have been posted to my web page. I CAN open other image files there, and I can open Metastream files LOCALLY with my MetaStream-enabled browser. I suspect the MetaStream files won't open because when my *.mts files are FTP-ed to my web page they are locally renamed as *.mts;1 The same sort of thing happens with *.jpg, but I CAN open them, (Maybe the ";1" addition to the end of the files is some sort of Unix thing; I don't know.) Anyway, for some reason, all *.mts files that I put on my web page are un-openable. My server won't let me delete the ";1" end tags (even with the rename function) It seems to me that if Internet Explorer can open a *.jpg;1 (renamed) file, then a MetaStream-enabled browser should also be able to open a *.mts;1 file. MetaCreations has been informed by me of this problem; but, so far, they have not answered me. After e-mailing my web page service provider, I recieved a terse reply that their server didn't support MetaStream files. No kidding! So, BEWARE DEVELOPERS: some of your customers might no appreciate files created for them that when put on their web pages simply WON'T OPEN! Has anyone else out there experienced this problem? Any solutions? I hope someone may be able to shed some light on this situation!

The only problem I've had was with HUGE file sizes after uploading (It was kind of strange - each time I uploaded the image, I got MORE of it, but I had to put it in it's own section of my site (2 MB partition) to upload the whole file - looked VERY strange after a partial upload!).

The problem I am having is with a MetaStream file that is 42K. So I guess large file size isn't the problem in my case. Thanks for the tip, though. Seedpress

is is possible you ftp'ed it up as ascii instead of binary?

Fur--Thanks for the tip; but I did ftp it in binary instead of ascii. In the meantime I've put my files on another web server where they work fine. Seems to be a problem with just SOME web-server software. Now the question is: which kind? Also, since web-browserimage viewers for other common image file types don't seem to be stymied by my MetaStream-"problem" server, I think MetaCreations needs to tweek their MetaStream viewer software to be compatible with a broader range of server software. I've gotten no satisfactory answer yet from MetaCreations; but since MetaStream is their BIG up-and-coming company focus, you would think they would be responsive to such a problem. Many of my potential "MetaStream"-file customers are using a web-page server that won't allow me to display MetaStream files. Leaves me in the lurch!

The problem has nothing to do with extensions per se. The server has to have the MIME-type (also seen in the HTTP header as "Content-type:") defined as being associated with that extension, so that it adds the right line to the header when it sends it back out. I've successfully served MTS files from an IBM OS/390 CTS system that doesn't even know what a file extension is, because the server code gets the Content-type right. Your problem is that the sysprogs who run the server are not doing their job.

Also note that MetaCreations/MetaStream are not able to fix anything here. This is purely a Luddite attitude from the people responsible for the specific server installation.

Hey John W. Gosh! Thanks for the clear explanation. Now I have something to work with. I can't thank you enough. Your advise was very clear; based on your info I shall re-contact my "Luddite" server sysprogs, and try to motivate them to remedy the situation. Again, THANKS SO MUCH! As an afterthought I'm retorically wondering what percentage of servers out there may have the same problem with MetaStreamk files? Hmmm--tooo bad; there're such neat files!

I had a similar problem. Make sure you add the tag: Type="application/metastream" after the embed src="your file here.mts" This is explained in greater detail in the UsingMetaStream.pdf file. Good luck! You can see some simple models I've built at my site. http://www.teleport.com/~v3d/meta.htm