Wrye Difficulties

[Smooth613]

I have to stick with my first assertion of the problem then. If everything was fine until you used PyFFI then it must be your python libraries at fault. There is no other explanation. Python is the only thing Wrye Bash and PyFFI have in common. I suggest you completely remove Python from your PC, including registry entries with a cleaner, and reinstall the proper version needed for Wrye Bash as mentioned earlier, Wrye Python 03a.

[Elizinator]

I have to stick with my first assertion of the problem then. If everything was fine until you used PyFFI then it must be your python libraries at fault. There is no other explanation. Python is the only thing Wrye Bash and PyFFI have in common. I suggest you completely remove Python from your PC, including registry entries with a cleaner, and reinstall the proper version needed for Wrye Bash as mentioned earlier, Wrye Python 03a.

 

=/

 

be that as it may, im not comfortable with that. theres too much likelihood for something going wrong - worse than it is now.

 

thanks for the help. i guess ill have to just deal with this as it is. im not going to try to reinstall the program i dont even understand myself.

[Smooth613]

Too much likelihood for something going wrong? Surely you can go to control panel and click Add or Remove Programs and uninstall anything named with Python right?

 

Then you simply install Wrye Python 03a with the self installer provided, it's an exe.

 

Surely you can do that right? That's the most basic of ways to install and remove anything on a PC.

[Shadowfen]

definitely have the green box, and its checked. obse_loader.exe is in the proper folder, i never touched it. i can use WB to run OBMM, and OBMM can run obse, and it works. i can play Oblivion in this way, with my tons of obse-dependent things (Deadly Reflexes, etc) =/

 

as i said, all this is fairly recent. Pyffi mangled it all. prior to that, i was running OBSE from WB without difficulty. ive had obse longer than obmm or wb =O

 

copy - > rename bash_default.ini doesnt seem to work, even when i specify the proper filepath. Bash.ini never existed, so far as i can tell. i never got a prompt to overwrite it, and before this update, did not exist anywhere that i could see. so prior to this, i got along fine without it. =/

 

C:\Bethesda Softworks\Oblivion is my installpath in its entirety. I didnt put it in Games or ProgramFiles or anything. This is the same place Mopy is, and obse-loader is =/

 

EDIT: interestingly enough, although that is the correct file path, i cant get it to look anywhere ELSE, even if i try. it just doesnt seem to be looking at bash.ini.

 

Have you tried setting the properties of c:\python26\python.exe (and pythonw.exe) to "Run as Administrator"?

 

EDIT: Bash does get along just fine without a bash.ini file when it is installed in an Oblivion that is installed in the default location. It is only when directories start changing from the defaults (such as when you are running on windows 7/Vista) that you have to worry about if the defaults still work.

[Elizinator]

set Python.exe and pythonw.exe to run as administrator. now WB cant start. period. i set them to NOT run as administrator. and it still cant start.

[Elizinator]

Too much likelihood for something going wrong? Surely you can go to control panel and click Add or Remove Programs and uninstall anything named with Python right?

 

Then you simply install Wrye Python 03a with the self installer provided, it's an exe.

 

Surely you can do that right? That's the most basic of ways to install and remove anything on a PC.

 

not ONLY is that not what you said above, but as i said, ive already done that more than once.

[Elizinator]

having performed every action i can imagine, my wrye bash has been very thoroughly destroyed. it cannot run under any circumstance. uninstalling Python does NOT reset the settings on python.exe and pythonw.exe, which are unable to activate WB AT ALL. starting the program produces a warning from windows, asking me if i want to allow this program to make changes, which i NEVER HAD before setting python.exe et al to "run as administrator". that setting is now permanent, unalterable, indelible, and has completely incapacitated Wrye Bash. im just glad i managed one more Bashed Patch before doing this, because i believe i wont ever be doing that again.

 

if anyone has ideas, i suppose it cant get much worse. every program involved with Python is dead dead dead, having been multiply reinstalled or uninstalled (like Pyffi, which STARTED this whole problem).

 

bugdump produced this:

 

c:\Bethesda Softworks\Oblivion\Mopy>c:\python26\python.exe bash.py -d

Traceback (most recent call last):

File "bash.py", line 95, in <module>

bosh.initDirs(personal,localAppData,oblivionPath)

File "c:\Bethesda Softworks\Oblivion\Mopy\bosh.py", line 28439, in initDirs

dirs['app'] = dirs['mopy'].join(dirs['app'])

File "c:\Bethesda Softworks\Oblivion\Mopy\bolt.py", line 437, in join

return GPath(os.path.join(*norms))

File "c:\python26\lib\ntpath.py", line 73, in join

elif isabs(b):

File "c:\python26\lib\ntpath.py", line 57, in isabs

s = splitdrive(s)[1]

File "c:\python26\lib\ntpath.py", line 125, in splitdrive

if p[1:2] == ':':

TypeError: 'Path' object is unsubscriptable

 

c:\Bethesda Softworks\Oblivion\Mopy>

 

UPDATE: re-copy/pasted the wryebash 289 and 290 files ontop of themselves in Mopy . . . and WB activates again, but surprise surprise, the exact same error string shows up when i try to start obse oblivion from the button. were back to square one, and ive done everything: even as was suggested, scraping Python out, and regcleaning it. Like everything else, after fixing the new problems that introduced, no change was made to the original problem.

[Smooth613]

Too much likelihood for something going wrong? Surely you can go to control panel and click Add or Remove Programs and uninstall anything named with Python right?

 

Then you simply install Wrye Python 03a with the self installer provided, it's an exe.

 

Surely you can do that right? That's the most basic of ways to install and remove anything on a PC.

 

not ONLY is that not what you said above, but as i said, ive already done that more than once.

That's exactly what I said above...

 

I suggest you completely remove Python from your PC, including registry entries with a cleaner, and reinstall the proper version needed for Wrye Bash as mentioned earlier, Wrye Python 03a.

The only thing I didn't mention again was a registry cleaner. You seemed to be unsure about simply removing a program so I chose not to elaborate on the registry cleaner. Which is also a basic tool. Either way you claim to have done all of that now and still have problems.

 

I suggest you head over to the official Wrye Bash [RELz] Thread, it's where the devs hang out, and post your latest bug dump there. They'll take over and point you in the right direction.

 

**Additional note**

I just want to clear things up regarding the following...

(like Pyffi, which STARTED this whole problem).

It's impossible that PyFFI started this problem. PyFFI is completely independent from Wrye Bash, and all other utilities. The only thing they share are resources. In this case those resources are Python Libraries. So PyFFI is not to be suspected as the culprit. However, as you mentioned you did early on, changing or updating Python can cause problems with Wrye Bash. Since Wrye Bash needs specific libraries included in the Wrye Python 03 package. We've covered this already but I want it to be clear since you apparently still blame PyFFI.

[Elizinator]

1: the registry cleaner was obviously what i was talking about. as i am a basic user, some things that are obvious and/or simple to you are not to me. so the only part of your prescribed action i had not already done was beyond my comfort, especially considering you didnt bother to explain it.

 

2:ive noticed this is a bizarre trend with techies, to demand FLAWLESS technical terminology. PyFFi is an entity i downloaded that came with multiple components, one of which is the program or resource or WHATEVER properly named Pyffi. other parts are what caused the problem. that much i concede. those parts came with Pyffi, inseparable from one another, so that in getting Pyffi to work, i NECESSARILY cause this problem. in a very real sense, Pyffi was responsible.

 

in both cases, you knew what i meant. dont be obtuse. youve been utterly unhelpful, becoming rapidly belligerent, denigrating and condescending.

 

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

[Smooth613]

First I'd like to say I only tried to help you, as I do with many others around here on a daily basis. Many times I succeed in solving the problem, sometimes I fail. That's how troubleshooting works. But you can bet if I do fail I'll point you in the right direction and follow through so I'll also learn more for future reference.

 

Take what you will from it, I can't change your opinion or make you believe something you have chose not to. Either way I only tried to help you with your problems. You get mad because I didn't elaborate on the Registry Cleaner but you were stating you were uncomfortable with certain aspects. If I would have elaborated it's likely you would have taken issue with that, wondering why I would elaborate on something you've already mentioned you didn't understand. See, that's a no win situation.

 

I never talked down to you, like you are doing me, nor did I demand anything from you, as you stated. Never once did I steer you wrong nor did I give you bad advice. I merely offered potential solutions to your problem. If stating that a Registry Cleaner is a basic tool is an insult, that's new to me.

 

In the end I only tried to help a random person who seems to get aggravated because they are having problems and don't understand something. That's fine, at one point we all didn't understand this. The difference is I didn't blame others or direct my frustration at them. I tried my very best to learn what was going on, and seek out solutions. When my suggestions were tapped out I even pointed you in the right direction. The link directs you to the development team, a top notch resource since they know the ins and outs, to further assist you with your problem. What you do with the information and resources provided is up to you. In the end I hope you get it working. I just hope you'll be more pleasant towards the next person trying to help you. I'm not sure why you decided I was the one you'd let your aggravation out on but again, I can't change that. I can however choose not to offer assistance to certain folks in the future.