25 replies to this topic

[Smooth613]

try getting the updated Python. 289 and 290, installed in that order, worked for me. http://www.tesnexus....le.php?id=22368

So according to the post I quoted above, from another Wrye Bash problem thread, everything is working for you now. You have the correct version of Python and the latest working version of Wrye Bash. The process you listed, that worked, seems vaguely familiar, huh?

From my first response to your problem...

You should indeed update to v290 as mentioned above, but first...

Lets not get too far ahead of ourselves here folks. Altering the .ini and path names within the .ini may be a valid point, but at this point I think checking the fundamental installation components is the first step. You said...

EDIT: again, cant rebuild rebuild bashed patch. This all started when i installed Pyffi. its frankly fairly ridiculous that upgrading python breaks WB . . . =/

It's not that ridiculous at all. Wrye Bash requires special Python Libraries found in Wrye Python 03a

When you installed PyFFI did you change or "update" your Python libraries? According to the quote you did. This is a far to common mistake I've seen folks make when using PyFFI. This will cause Wrye Bash not to work properly, or not at all in some cases. You need to ensure that you have Wrye Python 03a installed. Install it again to be sure. That will likely solve your problems since the issues arose after using another program that may ask you to update, or change, your version of Python.

You can find some related, but slightly dated, information HERE. For a more up to date version of the Wrye Bash ReadMe check your Mopy folder. It contains an HTML version.

I'm glad everything worked out and everything is up and running for you again. Although I hope you can now see that there was no need to bite my head off and direct your frustration towards me. Everything I mentioned was the proper steps and in the end that's what you did to fix the problem. Hindsight is 20/20.

Have a good one.

[Elizinator]

you truly are insufferable, snide, and arrogant. i might suggest you read for objective content before declaring that you were right all along and i proved it. his problem was getting wrye bash to RUN. this was NOT my problem, until one of the suggestions i followed CAUSED it. and *I* fixed it, independent of the original problem, which NOTHING you said properly addressed. my frustration is not with Wrye Bash; it is with you. yet even after the chastisement i gave, you still condescend, and without cause. well, im done with you. ill figure out by myself, considering thats the only progress ive made.

have a good one.

[Shadowfen]

Thank you shadowfen for your suggestions, even though they havent resolved the problem.

The only other thought that I've had was that there might be a change in the way that Bash writes out it's data files that it uses between version 275 and version 290 that was not documented. In the "Oblivion Mods" directory that Bash uses, there is a "Bash Mod Data" which has within it a Table.dat file (and possibly a backup of it). You can try removing (or renaming) that Table.dat file. Bash will notice it is gone and rebuild it.

Hopefully that will help you.

[Elizinator]

i got it working by doing the following:

first, re-updating wb to 286 and 290 got it to start again, but it still had all the old problems. so i wondered, considering setting python.exe and pythonw.exe caused them to not run, if that werent happening elsewhere. i found this deeply mysterious, as when i first installed oblivion, i HAD to run as administrator, or it just would work. so i found OBSE_launcher, and sure enough, it was set to run as administrator. so i set it not to. and it started, but oblivion did not. i found the same with it, and remedied that also. Then, i used the WB 275 archive version to overwrite 290, and everything worked perfectly, as far as WB/OBSE is concerned. reverting everything to the pre-pyffi state and setting oblivion and obse to *not* run as administrator fixed that problem.

again, thanks shadowfen. your suggestion eventually lead me to the correct solution =/

[Shadowfen]

i got it working by doing the following:

first, re-updating wb to 286 and 290 got it to start again, but it still had all the old problems. so i wondered, considering setting python.exe and pythonw.exe caused them to not run, if that werent happening elsewhere. i found this deeply mysterious, as when i first installed oblivion, i HAD to run as administrator, or it just would work. so i found OBSE_launcher, and sure enough, it was set to run as administrator. so i set it not to. and it started, but oblivion did not. i found the same with it, and remedied that also. Then, i used the WB 275 archive version to overwrite 290, and everything worked perfectly, as far as WB/OBSE is concerned. reverting everything to the pre-pyffi state and setting oblivion and obse to *not* run as administrator fixed that problem.

again, thanks shadowfen. your suggestion eventually lead me to the correct solution =/

Thanks for letting me know what did work. Maybe it will help someone else along the line.

Glad you found a solution!

EDIT: In your saga of administrator/non-administrator did you check to see if OBMM could still launch Oblivion with OBSE? OBMM might need to be changed as well...

Although I like Win 7 - I really hate Win 7/Vista...

[Elizinator]

both OBMM and WB can run oblivion successfully. it doesn't often work well from there on in, but thats a separate issue =/