D2loader sets belownorm priority

[knifeside]

Ok this has pissed me off so much over the last few days. To simply put it d2loader when launched somehow causes diablo 2 to be automatically set to below normal priority and this causes all kinds of issues. I can change it in the task manager but thats not the issue. The issue is when the game is automatically restarted to do something like change the cd key. The game starts right back up with below normal set. Its driving me nuts. I started out on xp pro sp3 and that failed so I made a new partition, installed xp home sp2 and the problem still arises. The only way I can get it to not do that is launch the uncracked game.exe and it starts up just fine but sadly thats not a option. I have to use dloader.

I have no idea what to do next. I've gone as far as to create batch files to try to automatically set the priority when the game is started but that doesnt work for some reason. I've also got a program called prio I think that saves priority changes but it has no effect on d2 either.

Reason is because Im using 2 virtual os along side with diablo 2, and they are running a bot in each one. When I try to launch d2 in my main os since vmware has normal priority over diablo 2, the game slows down to a halt. I've also tried setting all processes to below normal but that causes instability in the system and things begin to crash.

If anyone has any idea to override this let me know

[sugadesu]

Upgrade your computer.

You're running three OSs at the same time... your computer is running low on resources. What do you expect to happen.