I can't find a folder for Oblivion in there. I did notice a few leftover processes from InstallSheild, though. Killing them didn't change anything, and neither does restarting the computer.
I'll see if I can find the GUID for Oblivion -- maybe it somehow ended up with the same one as Catalyst?
Hopefully not, though, because that would mean the demise of yet another thing that should not be broken, spilling us into another thing similar to "dll hell", all brought on by the worst driver ever devised by man.
Edit:
Removing Catalyst's directory in "Installsheild Installation Information" didn't change anything. That's probably almost a good thing.
Edit again:
GUID is 35CB6715-41F8-4F99-8881-6FC75BF054B0. Oblivion definietly doesn't have a directory yet... which tells me that something is really bugared.
Yet another edit:
I just had a sudden realization:
It never mentions Oblivion in the installer. When I open it, it says that it is preparing the ATI Catalyst Control Center installer.
So, I updated ATI Catalyst Control Center and tried an InstallShield updater that I found, but it still messes up. It seems to actually install the stupid control center program now, but then freezes when I hit finish. Actually, it doesn't really freeze, since I can end it easily with the task manager, but it doesn't close when I press Finish and I get the hourglass pointer for eternity. Upon killing that installer, it continues to try to install the Catalyst Control Center... so it's definietly not a friendly driver updater.
I haven't encountered the 1607 error since running the updater.
I just had a fond memory of the good old days of downgraded DirectX installations... Who would have thought installers could be this much trouble?
I bet this game doesn't even write registry keys beyond a "here I am" type thing.
Final Edit:
Oho! Anyone else who has this problem, try my above attempts at a solution, then boot setup.exe directly from the DVD. Do not run the startup exe.
No, I did not overlook this originally -- it only started working when I do that after the above fiddling. I wouldn't be surprised if this was because of Catalyst Control Center writing itself onto my PATH variable.
I hate installers.
I'll see if I can find the GUID for Oblivion -- maybe it somehow ended up with the same one as Catalyst?
Hopefully not, though, because that would mean the demise of yet another thing that should not be broken, spilling us into another thing similar to "dll hell", all brought on by the worst driver ever devised by man.
Edit:
Removing Catalyst's directory in "Installsheild Installation Information" didn't change anything. That's probably almost a good thing.
Edit again:
GUID is 35CB6715-41F8-4F99-8881-6FC75BF054B0. Oblivion definietly doesn't have a directory yet... which tells me that something is really bugared.
Yet another edit:
I just had a sudden realization:
It never mentions Oblivion in the installer. When I open it, it says that it is preparing the ATI Catalyst Control Center installer.
So, I updated ATI Catalyst Control Center and tried an InstallShield updater that I found, but it still messes up. It seems to actually install the stupid control center program now, but then freezes when I hit finish. Actually, it doesn't really freeze, since I can end it easily with the task manager, but it doesn't close when I press Finish and I get the hourglass pointer for eternity. Upon killing that installer, it continues to try to install the Catalyst Control Center... so it's definietly not a friendly driver updater.
I haven't encountered the 1607 error since running the updater.
I just had a fond memory of the good old days of downgraded DirectX installations... Who would have thought installers could be this much trouble?
I bet this game doesn't even write registry keys beyond a "here I am" type thing.
Final Edit:
Oho! Anyone else who has this problem, try my above attempts at a solution, then boot setup.exe directly from the DVD. Do not run the startup exe.
No, I did not overlook this originally -- it only started working when I do that after the above fiddling. I wouldn't be surprised if this was because of Catalyst Control Center writing itself onto my PATH variable.
I hate installers.