Starcraft on Win2k
Hi all, I just upgraded from Win98se to Win 2k pro a couple of days ago. I've been testing all of my programs and so far only one game has refused to behave properly. So far, whenever I've logged off battle.
Hi all,
I just upgraded from Win98se to Win 2k pro a couple of days ago. I've been testing all of my programs and so far only one game has refused to "behave" properly.
So far, whenever I've logged off battle.net from Starcraft the program will not completely close. It remains open on the task bar, and I can't close it using the task manager which says it is not responding either. The only way to kill the program is to hard boot the system. It seems like the program is waiting for the network connection to close because I can't open my network properties until the program is closed. Is there any fix out there? Can I do anything with the Compatibility tools Microsoft has up on their site? Or am I stuck just having to live without it?
Other than that, everything seems to run fine. I don't really want to dual boot 98, or go back, Win 2k is so much nicer. (No BSOD or Illegal operations yet)
In terms of my system:
Win 2k Pro with SP1, and the compatibility update
Direct X 8.0a
Dell XPS B733r
P3 733
128 mb RDRAM
20 GB
Geforce 256 (Detonator 3 drivers)
Realtek Network card (Win 2000 drivers)
-blake
I just upgraded from Win98se to Win 2k pro a couple of days ago. I've been testing all of my programs and so far only one game has refused to "behave" properly.
So far, whenever I've logged off battle.net from Starcraft the program will not completely close. It remains open on the task bar, and I can't close it using the task manager which says it is not responding either. The only way to kill the program is to hard boot the system. It seems like the program is waiting for the network connection to close because I can't open my network properties until the program is closed. Is there any fix out there? Can I do anything with the Compatibility tools Microsoft has up on their site? Or am I stuck just having to live without it?
Other than that, everything seems to run fine. I don't really want to dual boot 98, or go back, Win 2k is so much nicer. (No BSOD or Illegal operations yet)
In terms of my system:
Win 2k Pro with SP1, and the compatibility update
Direct X 8.0a
Dell XPS B733r
P3 733
128 mb RDRAM
20 GB
Geforce 256 (Detonator 3 drivers)
Realtek Network card (Win 2000 drivers)
-blake
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Though Its not exactly alot of help, I have this same problem whenever I either use Task Manager or Alt-F4 to close SC. If I exit the game normally, not just logging out of bnet, but using the Exit option in the game, then I never have the problem. Funny how this is the only game that gives me this problem...
I looked for DRWTSN32 in the task manager, and it isn't there. So there must be something else that's hanging the program. I still don't get it though, how a program written for both Win 9x and NT 4.0 refuses to run correctly on 2000, which is basically NT with some 9x enhancements. I've also tried Appcompat.exe to no avail, I can't simulate Win 98 because SC installed under a NT config, and a Win NT simulation just reproduces the same results, and also locks up appcompat.exe. This is very frustrating since everything else works(relatively speaking after I've practically reinstalled most of my apps to stop them returning errors to Win 2000).
-blake
-blake
Anybody have any idea what could be wrong with my configuration? I got a reply from Blizzard but it was a standard automated reply from the fixes it suggested.
What about the people out there with Starcraft working without a hitch? What's your system configuration like? Network settings etc? Maybe that could give me an idea for fixing this problem.
-blake
What about the people out there with Starcraft working without a hitch? What's your system configuration like? Network settings etc? Maybe that could give me an idea for fixing this problem.
-blake
