Much client overrides notepad for opening the .txt files. that's annoying since although mush client is fast mud client it ain't the best way to view and edit .txt files and I have to be messing with the window file associations all the time.
mush client tries to override notepad
Posted by Aggressio on Wed 09 Oct 2002 01:47 PM — 6 posts, 20,848 views.
What operating system are you using? I use MUSHclient all the time, but my txt files are not associated with it.
I use windows 98. And every time I start mush client, it associates itself with .txt files. I tried if the problem was that the checkbox "do you want to use mush clients own inbuild notepad to edit scriptfiles" was checked, but it didn't help it. other problem is that when it associates itself with .txt files it doesn't know how to open them. windows gives you the error message "cannot find the file c:\example\example.txt was not found, make sure that..." and mush client tries to connect at "C", but no port is specified. it also opens a new instance of mush client every time.
This is quite odd.. First off, mushclient can't associate itself with text files. The only possible way this could happen is if somehow the entry for .mcl files in file options was written to by another program by accident and reassigned it. I have seen this happen and it is a major pain. Otherwise the only thing I can think of would be some secondary program that you are running that in designed to watch and make sure associations don't get reassigned by obnoxious programs. Unfortunately such a program would not be able to tell you appart from something that does make such changes without permission.
In general though.. Unless there is a duplicate entry for .txt that got incorrectly written into the registry some place and it is overriding your changes or some other program that loads at startup is trying to 'fix' the problem, mushclient itself cannot and does not make such a change. If you want to blame something, blames Microsoft and Windows for replacing the simple INI file in Windows 3.1 with two copies, with 3-16 data entries for every bloody file type in the 'improved' system registry. I am often surprised it ever works right. ;) lol
In any case, that would be where to look, in the actually mushclient file type for a duplicate .txt declaration, in the system registry (carefully) for any suspicious things that could cause it or for a watchdog program that is trying to prevent other programs from rearraging your file type associations. The odds of mushclient being in any way involved in causing this glitch is ironically about 0.0000001%. Making the job of finding the real source very difficult.. :p
Hmm.. Actually one other possibility I forgot.. Are you just turning off the computer or actually going through the Start:Shutdown menu? If you simply turn off the computer then windows won't write some non-critical data to the permanent copy of the system settings. Such supposedly non-critical data probably includes changes you make to file associations. So what could be happening is that each time you restart the computer it either finds:
A) a corrupted registry, (which can even happen during a normal shutdown), and loads an older non-fixed version that still has the incorrect setting or
B) finds and loads loads the last saves registry, which if you didn't do a proper shutdown, won't contain any changes you made.
If (A) is the case then you can try to make your change, then immediately shutdown the machine and restart. That 'should' leave you with a valid backup in case something else is corrupting the registry and preventing a proper save. It may not solve the problem though if the backup loaded before you make the change also had errors. :p I just love Microsloth Winblows, don't you? Great OS, until the instant something goes wrong, then it is like fighting a 20 foot boa constrictor. lol
In general though.. Unless there is a duplicate entry for .txt that got incorrectly written into the registry some place and it is overriding your changes or some other program that loads at startup is trying to 'fix' the problem, mushclient itself cannot and does not make such a change. If you want to blame something, blames Microsoft and Windows for replacing the simple INI file in Windows 3.1 with two copies, with 3-16 data entries for every bloody file type in the 'improved' system registry. I am often surprised it ever works right. ;) lol
In any case, that would be where to look, in the actually mushclient file type for a duplicate .txt declaration, in the system registry (carefully) for any suspicious things that could cause it or for a watchdog program that is trying to prevent other programs from rearraging your file type associations. The odds of mushclient being in any way involved in causing this glitch is ironically about 0.0000001%. Making the job of finding the real source very difficult.. :p
Hmm.. Actually one other possibility I forgot.. Are you just turning off the computer or actually going through the Start:Shutdown menu? If you simply turn off the computer then windows won't write some non-critical data to the permanent copy of the system settings. Such supposedly non-critical data probably includes changes you make to file associations. So what could be happening is that each time you restart the computer it either finds:
A) a corrupted registry, (which can even happen during a normal shutdown), and loads an older non-fixed version that still has the incorrect setting or
B) finds and loads loads the last saves registry, which if you didn't do a proper shutdown, won't contain any changes you made.
If (A) is the case then you can try to make your change, then immediately shutdown the machine and restart. That 'should' leave you with a valid backup in case something else is corrupting the registry and preventing a proper save. It may not solve the problem though if the backup loaded before you make the change also had errors. :p I just love Microsloth Winblows, don't you? Great OS, until the instant something goes wrong, then it is like fighting a 20 foot boa constrictor. lol
Quote:
First off, mushclient can't associate itself with text files
First off, mushclient can't associate itself with text files
Actually it could be doing this, because as part of its initialisation it associates itself with .MCL files. However I use it all the time on Windows NT, 95, 98 etc. and I have never seen this happen. I would make sure that the text files are associated with (say) Notepad, and then they should not get reassigned.
Quote:
Great OS, until the instant something goes wrong, then it is like fighting a 20 foot boa constrictor.
Great OS, until the instant something goes wrong, then it is like fighting a 20 foot boa constrictor.
40-foot.
thanks for suggesting checking up the registry.
I checked both associations for .txt and .mcl in explorer, but with regedit i found out that .txt had value default "mush client file". so i just cleared that one out, and then tried double-clicking a .txt file. nothing happened so i then had to associate .txt files with notepad with the open with... dialog in explorer, and for now it seems to work. i can now run mushclient.exe and .txt files stay associated with notepad. wyrd.
when i checked the registry i noticed that the mush client made entries for the unsuccesful file opens also, so every time i clicked a text file it tried to make a world out of the first letter of the path. so i had worlds C, D, E etc..with default windows-stuff in the registry.
but it works now. thank you. woulnd't have thought about the registry.
I checked both associations for .txt and .mcl in explorer, but with regedit i found out that .txt had value default "mush client file". so i just cleared that one out, and then tried double-clicking a .txt file. nothing happened so i then had to associate .txt files with notepad with the open with... dialog in explorer, and for now it seems to work. i can now run mushclient.exe and .txt files stay associated with notepad. wyrd.
when i checked the registry i noticed that the mush client made entries for the unsuccesful file opens also, so every time i clicked a text file it tried to make a world out of the first letter of the path. so i had worlds C, D, E etc..with default windows-stuff in the registry.
but it works now. thank you. woulnd't have thought about the registry.