Gammon Forum : MUSHclient : Bug reports : Installer Problem (3.42)

Log on

Gammon Forum

Entire forum

MUSHclient

Bug reports

Installer Problem (3.42)

Installer Problem (3.42)

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

Posted by

Saitir United Kingdom (3 posts)

bio

Date

Sun 29 Jun 2003 10:05 PM (UTC)

Message

Just upgraded from 3.32 to 3.42 and got a whole bunch of 'can't open file for writing' errors for all the files in worlds\plugins

Everything else was fine. Am on WinXP Pro with an admin level user, and to be sure it wasn't some bizarre security setting I deleted and re-made the plugins directory and tried again, then tried again just deleting the plugins directory and letting the installer make it itself.

top

Posted by

Nick Gammon Australia (22,975 posts)

bio Forum Administrator

Date

Reply #1 on Mon 30 Jun 2003 12:33 AM (UTC)

Message

I have a feeling it is a registry entry. You could try uninstalling MUSHclient totally (which should remove its registry entries) and then re-installing. However you will need to re-enter your registration code if you do that.

- Nick Gammon

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

top

Posted by

Loki (44 posts)

bio

Date

Reply #2 on Mon 30 Jun 2003 01:31 AM (UTC)

Message

I concur. I had the same problem with the upgrade.
I did waht Nick mentioned above and I had no problems
with installing afterwards.

-LºKi_
Founder
Endless Dreams

top

Posted by

Poromenos Greece (1,037 posts)

bio

Date

Reply #3 on Mon 30 Jun 2003 09:23 AM (UTC)

Message

This problem is also fixed if you run the installer from the MUSHClient dir, leading me to believe that the problem could be fixed with some error handling in the installer :P

Vidi, Vici, Veni.
http://porocrom.poromenos.org/ Read it!

top

Posted by

Saitir United Kingdom (3 posts)

bio

Date

Reply #4 on Mon 30 Jun 2003 11:25 AM (UTC)

Message

I don't know if its related to the problem or not by any means, but Promonenos' comment reminded me that the file shown was '.\worlds\plugins\<blah>'.

Is it as simple as a typo in the installer script that doesn't have the full path to install to? My understanding of various installers is that you would use a variable to point to the destination, rather than assume you were in the current directory, which the .\ would seem to indicate is the assumption?

Just a thought in the hope of helping.

top

Posted by

Poromenos Greece (1,037 posts)

bio

Date

Reply #5 on Mon 30 Jun 2003 03:50 PM (UTC)

Message

NSIS has a SetCurrentDir option, which sets the dir to whatever, so you can use relative filenames after that. If Nick gets that from the registry, and the entry is invalid, it will result to a write error. But there are functions which you can use to detect write errors and do whatever you want (such as change the output directory).

Vidi, Vici, Veni.
http://porocrom.poromenos.org/ Read it!

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.

14,997 views.

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

Go to topic: Search the forum

top

Quick links: MUSHclient. MUSHclient help. Forum shortcuts. Posting templates. Lua modules. Lua documentation.

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