Updater/patcher crashing after installing Steam client (XP)
By
Texas Justice,
Posted on: 2010-10-08 12:00 in ALL ACCESS Gameplay Technical Issues Bugs
Update: I've tried the "fix" from another thread, the one where you Copy the PIGGs folder, uninstall COH, reinstall COH, then paste the PIGGs folder back in and run patcher.
It keeps crashing every time it tries to Verify Image
I've deleted the PIGGs folder this time and am letting it reload them through the patcher.
STRANGELY, when I tried the copy/uninstall/reinstall/paste trick with the PIGGs and CohUpdater.exe, it FORCED installation to the C drive (instead of the separate partition I want my programs on) and THAT loaded fine! When the prompt came up to select a different location to install, I pointed it to where I wanted it (a folder already created) and it came back saying No. Re-ran it and it didn't even prompt, just went ahead to installing in C. I can't have it running on the main drive, there's just enough space in the partition for Windows and a few other core programs.
If I come back from work later to find that my latest attempt is working, then the problem must be a corrupted PIGG file. That corrupted after trying to run CohUpdater while Steam was going full steam (pardon the pun). If it doesn't work, then I have NO clue what else to do, because I've just done the equivalent of a complete uninstall/reinstall.
Has *anyone* had issues with COH after working with Steam?
The Beta is full of bugs?
How can that be?!
It's not the equivalent of a complete uninstall/reinstall from what you've posted. During an uninstall/reinstall the registry keys are removed during the uninstall and then rewritten during the reinstall.
Your registry entries are likely showing the installation location to be on the C drive which is why it keeps reinstalling there.
If the game spit out 20 dollar bills people would complain that they weren't sequentially numbered. If they were sequentially numbered people would complain that they weren't random enough.
Black Pebble is my new hero.
Quote:
But the installer was used, so the registry keys should have been removed. Anyway, that wasn't what caused that. It was that the directory it wanted to make (e.g. E:\Programs\City of Heroes\City of Heroes) already existed and the installer/patcher didn't know how to just make it work with that.|
Originally Posted by Texas Justice
It's not the equivalent of a complete uninstall/reinstall from what you've posted.
|
also, UPDATE: the last thing I tried has worked, the patcher runs without crashing. I'm afraid to even try to force file verification right now. All I can think is that it was some sort of corrupt PIGG file
Everything else aside, WHY would all this suddenly happen after trying to run along-side Steam?
The Beta is full of bugs?
How can that be?!
Quote:
Running the installer doesn't always cause it to overwrite existing registry entries, which is why it isn't the same as uninstalling (which does remove the registry keys) and then running the installer (which finds no existing registry keys so it writes totally new ones).
|
Originally Posted by Tiger_Lady
But the installer was used, so the registry keys should have been removed. Anyway, that wasn't what caused that. It was that the directory it wanted to make (e.g. E:\Programs\City of Heroes\City of Heroes) already existed and the installer/patcher didn't know how to just make it work with that.
|
If the game spit out 20 dollar bills people would complain that they weren't sequentially numbered. If they were sequentially numbered people would complain that they weren't random enough.
Black Pebble is my new hero.
Quote:
Sorry, meant to type that the UNinstaller was used, which would have removed the registry values. Anyways, that part's not an issue anymore, because I got the game running back like normal.|
Originally Posted by Texas Justice
Running the installer doesn't always cause it to overwrite existing registry entries, which is why it isn't the same as uninstalling (which does remove the registry keys) and then running the installer (which finds no existing registry keys so it writes totally new ones).
|
Now, i just REALLY want to know the why for all this to happen. That bugs me more than having to completely reinstall the game. WHY would this happen in the first place when it shouldn't have? Any techie's wanna try banging their heads up against that one?
The Beta is full of bugs?
How can that be?! I've heard too many odd things from people using Steam to even hazard a guess. Not just with this game, but with other games as well.
If the game spit out 20 dollar bills people would complain that they weren't sequentially numbered. If they were sequentially numbered people would complain that they weren't random enough.
Black Pebble is my new hero.
I rarely have crash issues with COH at all, and when I did it was usually something very easy to fix. That said, this latest series of crashes is driving me insane.
It started as I tried to run the COHupdater (patcher) while Steam was running and downloading 3 separate games. Internet choking aside, my computer should/would be able to handle all the processes going at once. But as the Updater connected and was checking the version, it crashed. "Report/Don't Report to Microsoft" prompted. I figured it was just the updaters clashing heads over shared resources, so I put COH aside and left Steam to download and install overnight.
Fast-forward to the next night (today), and I turned off Steam, made sure the process was not still running in the background, and restarted COHupdater. It connected and started to verify files, then crashed again.
I've tried deleting the checksum files and it still crashed. Transferring the COHupdater.exe along with PIGG folder to a new location and executed the copied COHupdater, and it still crashed. Now I've made a new directory and downloaded the client from my NC account page, and am in the process of installing a new version to the new folder.
From what I can understand of the error log, the error is an Access Violation of the COHupdater.exe file. "EXCEPTION: 0xC0000005 at address: 0x0041A5E6: ACCESS VIOLATION write attempt to address 0x238EDC36"
Why did Steam/Dead Rising 2/Left for Dead/2 pooch-screw me like this?? Is there anything else I'm missing here? This is seriously annoying the @#$% outta me. And I have to wait overnight just to find out if this last attempt even does anything.
Info/Specs: Windows XP Home SP3 32-bit, Intel Core 2 Duo 3GHz, DX 9.0c, >2 GB RAM, plenty of hard drive space, installed on a separate physical memory from Windows directory. (None of these things have changed and the game & updater were working perfectly well 2 weeks ago when I last played)
The Beta is full of bugs?