Register forum user name Search FAQ

Gammon Forum

Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the password reset link.

Due to spam on this forum, all posts now need moderator approval.

 Entire forum ➜ MUSHclient ➜ Bug reports ➜ Installer error: "Error opening file for writing: ...."

Installer error: "Error opening file for writing: ...."

It is now over 60 days since the last post. This thread is closed.     Refresh page


Posted by j0nas   (56 posts)  Bio
Date Fri 05 Jan 2007 05:26 PM (UTC)
Message
Hi, it's me again, with yet another installer-problem. I don't know what it's with me and these installers, maybe they just doesn't like me?

Anyway, I've just reinstalled windows on my machine, and when I try to install the latest MUSHclient I get the following error during the install, about 75% of the way through:

---------------------------
MUSHclient Installer
---------------------------
Error opening file for writing:

".\worlds\plugins\constants.vbs"

Hit abort to abort installation,

retry to retry writing the file, or

ignore to skip this file
---------------------------
Abort Retry Ignore
---------------------------

If that particular message is ignored, another similar one follows for the next file destined for that directory, and the next, and the next.

This seemed like a strange error to be having, so I tried a few older installers, and a few different install-paths. I've tried installing MUSHclient on two different drives, on several different paths, and I've tried the installer for v3.84, v3.82, v3.80. As the v3.80 installer worked for me last time I tried to install MUSHclient, that it won't work now is somewhat mystifying.

Do the installers work for everyone else? Any suggestions as to what I should be looking at, when trying to solve this problem locally? It does seem overwhelmingly likely that the problems I'm having are local, even though I've had no problems other than this as of yet.
Top

Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #1 on Sat 06 Jan 2007 03:57 AM (UTC)
Message
It seems likely that you have kept the old installation, but deleted the directories. The installer consults the Registry for where to put things, and if there are no Registry entries, makes default ones. However if there are Registry entries, and they point to what are now non-existant folders, then you will have a problem.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by j0nas   (56 posts)  Bio
Date Reply #2 on Sat 06 Jan 2007 05:34 AM (UTC)
Message
You were right, there was some stuff in my registry. I had used my old MUSHclient-install once, saved from my older windows-install, and apparently that one added some crud to the registry. Seems strange to me that it would cause this problem, since that MUSHclient was run from the exact directory where the new MUSHclient was being installed to, but no matter, things worked just fine once I deleted the old entries in the registry.

Thank you.
Top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.


11,279 views.

It is now over 60 days since the last post. This thread is closed.     Refresh page

Go to topic:           Search the forum


[Go to top] top

Information and images on this site are licensed under the Creative Commons Attribution 3.0 Australia License unless stated otherwise.