It takes three minutes for me to connect, as opposed to three seconds with my previous install of the NT 7 beta 18 with XP on the same machine.
After starting NT7, the splash screen appears and the connected ring sounds, but the splash screen disappears and NT7 hangs for several minutes using zero CPU in the task manager. Sitting there and doing nothing. When I disable connect on startup, Ninja loads fine but upon connecting to Zen manually, it still locks and idles for several minutes before loading. When it finally starts up and connects, loading various charts randomly sends it into a lock-up. So at that point it's unstable for me also.
I found two workarounds that jump start it immediately and allow it to work normally for me (so far).
1. Run in compatibility mode for Windows 98/ME (Sounds like a joke, but XP mode does not fix it for me for some strange reason)
2. Manually raise the CPU priority in task manager to High, it will then open the NT window immediately showing a successful Zen-fire connection and everything works fine afterwards. This is temporary because Windows 7 doesn't save CPU priority settings for future startups so it would have to be done manually every time.
Doing either of those makes it work instantly and returns it to how it was when I was using XP, back when it was flawless.
The problem is that I don't want to have to tweak the thing in silly compatibility mode or CPU priority.
I tried NT 6.5, and it works fine on this machine, but that's obsolete to me. And so is XP as far as I'm concerned.
I hope it's only my machine, but I'm afraid not since I also tested this on another comparable machine running Vista in my house, and the same problem occurred. It still took forever to connect to Zen-fire.
I think this might be limited to Ninja Zen-fire connection for me, because if I connect on startup to Yahoo it works without a problem, a few seconds to connect at most. Only starting the Zen connection has the thing hanging for minutes doing nothing.
I can reproduce this problem anytime by disabling the compatibility mode, or running it with normal CPU priority. My system is average, 1.8GHz, 2.5gb of ram. This should not be happening.
Thanks
Comment