:O say what??Quote:
Originally Posted by Pyong Kawaguchi
Printable View
:O say what??Quote:
Originally Posted by Pyong Kawaguchi
Limited: Yeah, all the GFWL games (up to some point in time) use the same set of keys.
Syuu: Don't forget to run the SecuROM removal tool when you're done with Batman. No sense in creating more problems than you already have. :P
securrom is credit to anti-piracy hawhawhaw
Also running selective startup with only original boot configuration worked.
but i had no internet
So i decided to bootup normally with no initial internet conneciton and BAM it worked.
And sure enough when I connect to the interweb, the error comes back
and batman works
wtf is xlive's problem. So just for fun I used skarma's "xliveless" xlive.dll and of course it worked.
what the hell.
look at all you noobs gettin into halo2 :p
from what i've experienced is sometimes Windows Live messenger screws with h2v but that hasn't happened to me in a good while.
you have halo too
i dont even have windows live messenger
Besides a reinstall (as the long solution where you do not learn the true answer to your problem) it sounds like it could be networking issue. Network drivers? Any other problems with any other apps when you are online?
You mentioned selective startup so you may know but:
START -> RUN -> MSconfig
and
START -> services.msc
...will show you the services and apps that come online during Windows startup. Here is a web site that lists different types of service settings. May help but can also hurt, so note your changes.
http://www.blackviper.com/Windows_7/servicecfg.htm
are you sure that "fix" over at gamesforwindowslive didn't help. Did you restart the comp after you did it?
Halo 2 Windows 7 Workaround Thread
Method 1
Method 2
Method 3
Method 4
Try these out. I doubt it's a network issue because they you'd be having problems with your internet (which clearly you can post fine) It's just an issue with the LIVE game thinking you are already running it.
I'm going to end up reinstalling Windows 7 anyway.
well try those methods first if you want.
Pretty sure I got the same issue. open the disk and run the setup from there, I think that's how I got that working
though I'm on 32, the error sounds familiar