The following new message has been posted on Phorm Support Forum at <http://www.phorm.com/support/>. *************************************************************************** MESSAGE: (#3849) Re: Installation Error <http://www.phorm.com/support/?rev=3849> AUTHOR: Holotech DATE: March 10, 2004 at 8:26 a.m. EST Reply To: (#3842) Re: Installation Error Author: cush Date: March 9, 2004 at 4:00 p.m. EST > OK. I went in and changed more permissions and figured > out how to start Phormation (note: A mention of the > Docs.rtf file in the readme would be a good idea). > However, Phormation installed several files in a > manner that now I can't change permissions or even > delete them and start over. This is why Phormation should be run under your user ID. If it's run under the user ID of the web server, the files it creates are going to belong to the web server. Unfortunately this isn't something I can handle by just being smarter about programming. This is the way server security is designed. If your host doesn't know what a script wrapper is, or insists they're a security hole, you should find a better host. A script wrapper is a security *measure*. There most likely is a way to delete files belonging to the web server on your system - there is on my system. But I don't know what it would be for you. You'll have to ask your sys admin. *************************************************************************** This is an automatically-generated notice. If you'd like to be removed from the mailing list, please visit Phorm Support Forum at <http://www.phorm.com/support/>, or send your request to webbbs@xxxxxxxxxx If you wish to respond to this message, please post your response directly to the board. Thank you! ------------------------------------------------- You are receiving this message because you are subscribed to the Phorm mailing list. To send messages to the mailing list, simply send email to phorm@xxxxxxxxxxxxx from the address you have subscribed. You may unsubscribe from the list by sending email to phorm-request@xxxxxxxxxxxxx with 'unsubscribe' in the SUBJECT field.