I have EmacsW32 23.1.50.1 emacs working on my windows XP machine. It hangs randomly for 5 to 8 seconds and quite frustrating.
Any one has solution?
I even trie
After disabling global-auto-revert-mode, the system does far less I/O. For me, this seemed to have solved the problem.
I had exactly the same problem using EmacsW32 23.1.50 on WinXP. One change I made that had a significant improvement (for me anyway) was to add the following to my .emacs
file:
; try to improve slow performance on windows.
(setq w32-get-true-file-attributes nil)
It seems this variable was changed to default to "true" relatively recently and is known to cause some slow-down problems around file access. I still get some random hangs now and then (probably due to my .emacs
customisations) but it is much better now.
I was having similar issues and traced it to network timeouts on Windows. In my particular case, it was due to ido.el, which keeps a cached list of directory contents. At startup, ido was trying to check the cached directories, which included network shares on both my home network and my work network – there were always some nonexistent hosts, no matter which network I was on.
Because my problem was originating with ido (sort of), the solution for me was to set ido-max-dir-file-cache to 0 (via customize-variable or init.el), then exit Emacs, delete ~/.emacs.d/.ido.last, and restart Emacs. Based on what I saw in another thread, it's important to make sure all instances of Emacs are closed before trying to delete .ido.last. There may be other ido variables that need to be changed, but so far, this solution is working for me.
Without some debugging output it will be difficult to say what is causing the delay.
Since delays are often caused by IO operation timeouts, I recommend running Process Monitor to see what Emacs is doing while it is hanging.
Please try stopping Netlogon service in "Services" control panel. That solved the problem in my case. See the excellent article http://www.hydrus.org.uk/journal/emacs-netlogon.html that saved me from the agony.
This only applies to a small (yet increasing?) group of users that:
I have windows 7, that was happening to me because i was using Classic Windows UI, once i changed to the default theme it worked great, maybe also Themes service has something to do with that, so if you stopped it, try running it.