Jump to content
Sign in to follow this  
angelleye

Strange problem with runtime solution on 1 customer's machine...???

Recommended Posts

I've got a FM runtime solution that I distribute and the first step after you load it the first time is to change your password.

A new customer (hopefully) of mine is getting a message that the file is not modifiable when they try and change their password. It's the first time I've heard of this problem and I can't reproduce it on my own Macbook.

The runtime solution is wrapped up into a Mac Installer Package which is then zipped and placed on the server. You simply download the zip and extract, then run the installer and load the software. I've never had a problem with this until this guy.

I did a screen share with him and went through the whole thing myself and sure enough the software installs just fine (oh, by the way, you have to put in the admin password to install. not sure if that matters) and loads just fine, but when you try and change the password you get this file cannot be modified.

Immediately after that I did the same thing on my own Macbook. Downloaded the zip file fresh, extracted, installed, and I can change my password with any problems.

I have absolutely no idea what might be causing this and I'd appreciate any information on how to possibly fix the problem. Thanks!

Share this post


Link to post
Share on other sites

Is there a way to delete my own messages???

After I used my brain for a minute I told him to check the permissions on the runtime files and it was set to Read only. He switched that and all is well now. Not sure why his install was defaulting to read only...must have been something with his system settings I guess..??

Share this post


Link to post
Share on other sites

Not that I'm aware of Drew: I had my hand slapped by the Sysop here because I answered my own question and requested that the thread be deleted; he said it was more important for others to read and learn what a user did to solve a problem than to simply delete the post and have no one learn from the experience.

It makes sense.

Glad you got the runtime issue figured out. It's always a chore with those things since you can't make a quick fix with them--you have to re-burn the whole thing then reissue it to the customer; not the best user-friendly venue by any stretch of the imagination. :S

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.