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
➜ General
➜ Command Window Size
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Flyer-fox-delta
(8 posts) Bio
|
| Date
| Tue 09 Sep 2003 05:36 AM (UTC) |
| Message
| | After I got hit by a virus (which got cleaned out first), I noticed that my commadnd input window had drastically shrunk to the smallest size possible. At the time I thought it was one of my family messing with the settings as I had decided to clean it out in the morning and remember telling everyone not to use the computer all day (but some of my family are dumb and don't listen, such as my younger brother). I doubt it was my family that caused this issue, since I resized the command windows on all the worlds that I had set to automatically open when the program is run. However, it seemed that it didn't matter what I did with the command windows, they would continually shrink back to that tiny size on each reboot or re-opening after closing it. Mutiple instances seem to carry the exact same command window size as the first running instance but this problem has gone beyond a minor nuisance. This problem started in 3.26 which was the version I used for over a year without upgrading, and I was suggested to upgrade to a newer version to see if it helps yet even then it still kept shrinking. I was told this might be doe to the fact the program can't keep track of the command window size very well though if that's the case, why did it keep track of my window sizes for over two years before now? Is there some way to make it remember window sizes instead of having to resize the comamnd windows manually all the time? | | Top |
|
| Posted by
| Nick Gammon
Australia (23,162 posts) Bio
Forum Administrator |
| Date
| Reply #1 on Wed 10 Sep 2003 10:28 PM (UTC) |
| Message
| It remembers the command window size in the Registry. Maybe it is having trouble writing to the Registry.
You could try an uninstall (which will clear out the registry entries for MUSHclient) followed by a re-install.
As far as I know, I have not mucked around with the command window size in recent versions. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Shadowfyr
USA (1,791 posts) Bio
|
| Date
| Reply #2 on Thu 11 Sep 2003 12:38 AM (UTC) |
| Message
| | Yes, however, something seems to go wrong on some systems when you have more than one world open. It is possible it is failing to write the information, but on my computer at least it refuses to read that information again when you reload it. Imho, this should be part of the world file, not something kept in the registry, where it can be corrupted or things can and often do go wrong. This bug in one fashion of another came up several versions ago and was never actually fixed as far as I know. | | Top |
|
| Posted by
| Flyer-fox-delta
(8 posts) Bio
|
| Date
| Reply #3 on Thu 11 Sep 2003 08:39 PM (UTC) |
| Message
| That would make sense, because those files can be backed up and you'd always have a way to keep some settings that are MU* specific intact in the event of something mucking up the registry. I had a virus hit me, a Backdoor Trojan kind of worm which hid itself by making entries into the registry so it will be counted as a Windows Service and invisible to the close program box. I only figured out I had this virus when I kept seeing a program called dllmem32.exe crash via page fault eevry time I hopped online.
I took care of the problem with two virus scans and by editing my registry to remove any entries of "dllmem32" within it using a guide I found on Norton's page as a reference on what to do.
Immediately thereafter, this window size problem sprang up. This I know now since I thought back to before the virus and then after.
Doing a clean reinstall after backing up logs and world files helped to solve the problem of window size so far, but it does seem to be a good idea to experiment on making it write the window size of the command input directly to the world file instead of the system registry. | | Top |
|
| Posted by
| Shadowfyr
USA (1,791 posts) Bio
|
| Date
| Reply #4 on Thu 11 Sep 2003 09:15 PM (UTC) |
| Message
| Unfortunately there seem to be some things in windows that are 'basic' to its operation and 'incredibly' unstable. They never (or rarely) effect MS applications, but I have had this issue with the command window since I first installed things. No virus on my machine either. However I also have these issues:
Opera browser -
1. Won't correctly save all of the open windows in a session. It somehow marks them as "don't save" and from then on even creating a new session results in that window being saved in the session, but none of the link data or other info needed to reopen it. This appeared some time ago in 6.05 and upgrading to 7.0 didn't fix it.
2. Recently the print option got screwed up, now it won't allow me to print either Sub-frames or 'selection'. Instead it often only prints the main frame or the entire document.
These are the ones I have run into, since I use Opera every day. However, I suspect that a lot of similarly fun things are going wrong and deinstalling/reinstalling Opera and other effected programs doesn't do anything.
What I don't get though is how the bloody OS can continue to run more or less right and have some of these basic things still go wrong. I know it is Windows, because there is no reason why Opera 7 should have had the same problem as 6.05, they don't share any dlls that I know of, except the ones build into windows.
Anyway.. Relying on the system registry to keep track of something that is this much a part of the world itself is not too bright imho. It is even less bright apparently when using 98SE, which we are both using. | | Top |
|
| Posted by
| Nick Gammon
Australia (23,162 posts) Bio
Forum Administrator |
| Date
| Reply #5 on Thu 11 Sep 2003 10:43 PM (UTC) |
| Message
| I will seriously look at moving it to the world file. At the time I put the coordinates in the Registry it was before the XML world files, and I was reluctant to change the world file layout.
However one problem is - which you may or may not care about - that simply moving or resizing the window will then count as "changing the world file" so you will have to save it, even if nothing else has changed.
Thus, starting a session, moving the window a pixel to the left, and then closing it, will give the message "world file has changed - save it?" which you may find confusing. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Flyer-fox-delta
(8 posts) Bio
|
| Date
| Reply #6 on Thu 11 Sep 2003 10:49 PM (UTC) |
| Message
| | There's also a fix to that. As far as I know, all new worlds have the option of being automatically saved upon closing. For me, it's enabled on all the worlds I connect to so if even one thing changes, it'll be saved. However, it also comes toa point that it's also best to save immediately after making a change in the world configuration. So this won't be a problem for people like me who have the "save world upon close" option checked. But it can also be put into a FAQ if new users start asking about it (which they doubtlessly will). | | 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.
19,035 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top