So. Computer crashed and I got a new one... Comeplete with Vista... Which seems to have a problem with TinyMush. I use MUSHClient... Any ideas on how to get me to where I can connect with settings or anything? HELP!
Cannot reach a TinyMush server with Vista.
Posted by FenrisJedi on Fri 27 Apr 2007 02:25 AM — 14 posts, 56,849 views.
This might help:
http://www.mudconnect.com/tmcfaq.html#Answer46
http://www.mudconnect.com/tmcfaq.html#Answer46
Quote:
Windows Vista enables something called AutoTuning by default which earlier windows versions had disabled, to bypass this problem login to your computer as an Administrator and open a command shell (Start -> Run -> type cmd ) and enter this text and then hit return:
netsh int tcp set global autotuninglevel=disable
You will need to do this each time you restart your machine until Microsoft resolves the issue in a later patch.
Windows Vista enables something called AutoTuning by default which earlier windows versions had disabled, to bypass this problem login to your computer as an Administrator and open a command shell (Start -> Run -> type cmd ) and enter this text and then hit return:
netsh int tcp set global autotuninglevel=disable
You will need to do this each time you restart your machine until Microsoft resolves the issue in a later patch.
I tried that and it gives me...
Set global command failed on IPv4 The requested operation requires elevation.
Okay. I'm lost now.
Set global command failed on IPv4 The requested operation requires elevation.
Okay. I'm lost now.
Are you perhaps not running as administrator? I have no idea what might be wrong since I've hardly even seen Vista much less worked on it.
Quote:
Which seems to have a problem with TinyMush. I use MUSHClient ...
Which seems to have a problem with TinyMush. I use MUSHClient ...
What was the nature of the problem, exactly?
He bought something with Vista on it just prior to when several major companies decided to remove it and put XP back on their systems and MS more or less admitted the failure of Vista by deciding to release a version for only $3 in some countries?
Sorry, couldn't resist. lol But, almost no one **wants** Vista on their systems.
Still, we do need a clearer idea of just what the actual problem is. I am betting its something in one of the famous, "If you install it in the default 'C:\Program Files\' location, it won't work right, because Vista won't let you change data in there", issues. We recently ran into that with POVRay 3.6, though mainly do to the fact that some program settings are in .ini files for that. Solution was, "Don't install it in that path, so Vista doesn't try to *protect it* from you." People are just having more and more problems the longer they use that monster.
Sorry, couldn't resist. lol But, almost no one **wants** Vista on their systems.
Still, we do need a clearer idea of just what the actual problem is. I am betting its something in one of the famous, "If you install it in the default 'C:\Program Files\' location, it won't work right, because Vista won't let you change data in there", issues. We recently ran into that with POVRay 3.6, though mainly do to the fact that some program settings are in .ini files for that. Solution was, "Don't install it in that path, so Vista doesn't try to *protect it* from you." People are just having more and more problems the longer they use that monster.
We can't help resolve this problem until you describe what is going wrong if you try to run under Vista. For example, the error message or nature of the problem.
The main MUSHclient web page (http://www.gammon.com.au/mushclient/mushclient.htm) says:
Since it does not claim to run under Vista this is not, strictly speaking, a bug.
However if you can tell us what is happening, and we can fix it, we will be glad to do so.
The main MUSHclient web page (http://www.gammon.com.au/mushclient/mushclient.htm) says:
Supported Operating Systems
Runs under Windows 95/98/ME/NT/2000/XP.
Since it does not claim to run under Vista this is not, strictly speaking, a bug.
However if you can tell us what is happening, and we can fix it, we will be glad to do so.
Basically, I connect to a newly revamped TinyMush server. It says I connect. The people on the other end, all my friends, can see me type and pose and everything. On my end, it stays just at the connection point. Obviously, I can send but not recieve. It's probabably noting with MUSHClient but I am just desperate to be able to be on this place. It's something between the new TinyMush and Vista. I'm beginning to think that I need to format and install XP. There are some things about Vista that I like... But a whole lot I don't. That software is SO not ready for the market.
(Sorry I didn't get back to you all sooner. Went out of town.)
(Sorry I didn't get back to you all sooner. Went out of town.)
OH. And I was running as Admin. Only one account.
Does this work if you use plain telnet?
Thanks for clarifying. It doesn't totally surprise me that you can send but not receive, for the simple reason that sending and receiving take somewhat different paths in the program. Sending is in response to (usually) something you type, whereas receiving is asynchronous (that is, we don't know when something is going to arrive), and the Winsock DLL (Windows Sockets) raises an event to let the client know there is data waiting.
If this event is not raised, or swallowed up somehow, then the client will just sit there quietly.
It might be worth trying to do what was suggested earlier, from a command window, enter:
If that doesn't work (that is, an error message), try Googling for the error message, or using the inbuilt help, to work out why, and keep going until it accepts that command.
Then I would try this:
I have been browsing the web a bit to try to get clarification. A few postings suggest that a lot of people are having problems with Vista because "routers are not Vista compatible". (Imagine how long Macintosh or Linux would last if they released a new version that required everyone to update their routers).
I haven't yet seen a really good solution for the problem - the autotuninglevel stuff sounds more like a speed issue than fixing a total absence of incoming data.
It might help if other users of this forum could also respond to these questions:
Thanks for any information anyone can provide.
If this event is not raised, or swallowed up somehow, then the client will just sit there quietly.
It might be worth trying to do what was suggested earlier, from a command window, enter:
netsh int tcp set global autotuninglevel=disable
If that doesn't work (that is, an error message), try Googling for the error message, or using the inbuilt help, to work out why, and keep going until it accepts that command.
Then I would try this:
- Try telnet that comes with windows (Start Menu -> Run -> telnet). See if that works.
- Try another client (eg. zMud, SimpleMu). If they all work, but MUSHclient does not, you have narrowed the problem down to something MUSHclient is doing.
- Ask around (eg. on the MUD, although I know it is hard if you can't connect). Are other people using Vista? Are other people using Vista and MUSHclient succesfully?
I have been browsing the web a bit to try to get clarification. A few postings suggest that a lot of people are having problems with Vista because "routers are not Vista compatible". (Imagine how long Macintosh or Linux would last if they released a new version that required everyone to update their routers).
I haven't yet seen a really good solution for the problem - the autotuninglevel stuff sounds more like a speed issue than fixing a total absence of incoming data.
It might help if other users of this forum could also respond to these questions:
- Are you running on Microsoft Vista (and if so, which version - home, business etc.)?
- Are you using MUSHclient?
- Does it work?
- Did you have to change anything to make it work (eg. tweak configurations, install something), and if so, what?
Thanks for any information anyone can provide.
I've done a lot of reading up on the web tonight, and I've finally gotten both MUSHclient and SimpleMu to load reliably on Vista Home Premium edition. I've got them both starting up reliably, and nothing crashes.
I tried three things.
The first was disabling the autotuning, since that seems to be the most common suggestion. (FYI, I used the instructions here: http://computerbits.wordpress.com/2007/02/14/vista-auto-tuning/ which also has a link to explain how to get to the elevated command prompt.)
The second was saving the program in a path other than C:\Program Files, as suggested above by Shadowfyr.
Third, before I opened the program for the first time, I rightclicked on the shortcut icon, went to Properties > Compatibility, and told it to run with admin privileges, and to run in Windows XP compatibility mode.
I went back in and turned the autotuning off, and it is still working. I think it's the combination of the path, the privileges, and telling it that it's still in Kansas^HWindows XP, that are the key.
I tried three things.
The first was disabling the autotuning, since that seems to be the most common suggestion. (FYI, I used the instructions here: http://computerbits.wordpress.com/2007/02/14/vista-auto-tuning/ which also has a link to explain how to get to the elevated command prompt.)
The second was saving the program in a path other than C:\Program Files, as suggested above by Shadowfyr.
Third, before I opened the program for the first time, I rightclicked on the shortcut icon, went to Properties > Compatibility, and told it to run with admin privileges, and to run in Windows XP compatibility mode.
I went back in and turned the autotuning off, and it is still working. I think it's the combination of the path, the privileges, and telling it that it's still in Kansas^HWindows XP, that are the key.
Thanks for that clarification. Since I don't have Vista I didn't know about the "compatability" option, but that makes a lot of sense.
I seem to remember that Windows 95 had "backwards compatability" options too, so it is worth knowing this. I'll update the FAQ page shortly to mention this.
I seem to remember that Windows 95 had "backwards compatability" options too, so it is worth knowing this. I'll update the FAQ page shortly to mention this.
Exactly. You have to run the window as Admin. I finally figured this out. Thank you so much for all of your help. It makes a big difference.