Wrye Difficulties

[Elizinator]

i maed a post a few weeks ago about wrye bash problems. it seems to have been removed, so im starting a new one.

 

apropos to the suggestions in the previous post, i reinstalled Python. and it totally broke Wrye Bash.

 

now i get THIS:

 

Traceback (most recent call last):

File "C:\Bethesda Softworks\Oblivion\Mopy\basher.py", line 9229, in Execute

App_Button.Execute(self,event)

File "C:\Bethesda Softworks\Oblivion\Mopy\basher.py", line 9178, in Execute

os.spawnv(os.P_NOWAIT,exePath.s,exeArgs)

OSError: [Errno 22] Invalid argument

 

every time i try to start the game through wrye bash. i can do it normally through OBMM, but this is an inconvenience i dont need or deserve. please, does anyone understand what this means, or better yet, how to ACTUALLY fix it?

[Shadowfen]

i maed a post a few weeks ago about wrye bash problems. it seems to have been removed, so im starting a new one.

 

apropos to the suggestions in the previous post, i reinstalled Python. and it totally broke Wrye Bash.

 

now i get THIS:

 

Traceback (most recent call last):

File "C:\Bethesda Softworks\Oblivion\Mopy\basher.py", line 9229, in Execute

App_Button.Execute(self,event)

File "C:\Bethesda Softworks\Oblivion\Mopy\basher.py", line 9178, in Execute

os.spawnv(os.P_NOWAIT,exePath.s,exeArgs)

OSError: [Errno 22] Invalid argument

 

every time i try to start the game through wrye bash. i can do it normally through OBMM, but this is an inconvenience i dont need or deserve. please, does anyone understand what this means, or better yet, how to ACTUALLY fix it?

 

Which version of Wrye Bash do you have? I am certain that it is not version 290 - the line numbers don't match up. :)

 

Be that as it may, you might be having a problem with the default locations in the bash.ini file (or a missing bash.ini file). I have seen this error when the full path for the oblivion directory is wrong so that wrye bash cannot find the obse_loader.exe to run. You can create a bash.ini if you need to by copying and renaming the bash_default.ini and then using the editor of your chose to go in and modify the paths however you need to.

 

EDIT: bash_default.ini is in the Mopy directory. bash.ini is supposed to be in Mopy also.

[Elizinator]

i have 275. which ought i have? =/

 

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

[Shadowfen]

i have 275. which ought i have? =/

 

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

 

Please pull down Wrye Bash 289 - Full Archive and Wrye Bash 290 - Update Only . Install version 289 and then install the 290 update on top of it.

 

Have you checked the bash.ini file and the pathnames inside yet?

[Smooth613]

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.

[Elizinator]

well, im not a programmer or a a techie. the internal logic of programs and computers is opaque to me xD

 

i actually already went to that link, and downloaded the wrye python there, and ran the .exe, and . . . it changed nothing =/

 

right now, ive tried uninstalling totally and re-installing, with hope this will work. ill update when its done.

 

EDIT: no change. updating wrye python as linked has produced no effect. i still get the above problem, and another different one when i attempt to rebuild Bashed Patch.

[Elizinator]

EDIT: bash_default.ini is in the Mopy directory. bash.ini is supposed to be in Mopy also.

 

Bash.ini isnt anywhere on any of my harddrives. Copy -> rename Bash_default.ini to Bash.ini didnt work either. im trying to update wrye bash . . . do i have to worry about losing load orders and active lists and such?

 

UPDATE: installed those things. i conclude it was done properly, because WB looks a little different now. BUT,

 

[Errno 22] Invalid argument

Used Path: C:\Bethesda Softworks\Oblivion\obse_loader.exe

Used Arguments: ('obse_loader.exe',)

 

Traceback (most recent call last):

File "C:\Bethesda Softworks\Oblivion\Mopy\basher.py", line 11666, in Execute

App_Button.Execute(self,event)

File "C:\Bethesda Softworks\Oblivion\Mopy\basher.py", line 11559, in Execute

raise

File "C:\Bethesda Softworks\Oblivion\Mopy\basher.py", line 11553, in Execute

os.spawnv(os.P_NOWAIT,exePath.s,exeArgs)

OSError: [Errno 22] Invalid argument

 

T_T

 

i have tried editing Bash.ini, except that it doesnt exist. renaming the default, copy -> rename, editing either, or both, doesnt work. i might not be using the proper syntax, which i dont know, but telling it exactly the directory structure produces no change.

 

HALP! D:

[Shadowfen]

EDIT: bash_default.ini is in the Mopy directory. bash.ini is supposed to be in Mopy also.

 

Bash.ini isnt anywhere on any of my harddrives. Copy -> rename Bash_default.ini to Bash.ini didnt work either. im trying to update wrye bash . . . do i have to worry about losing load orders and active lists and such?

 

No, the load orders and active lists are kept elsewhere by oblivion itself so they are safe.

 

Once you have updated your bash version, you'll need to copy/rename your bash.ini in the Mopy directory from bash_default.ini - so that you have the new version of the ini that matches the new version of bash.

 

EDIT: Umm, just a thought - you do have OBSE installed don't you?

 

[Errno 22] Invalid argument

Used Path: C:\Bethesda Softworks\Oblivion\obse_loader.exe

 

Does the file named in the "Used Path" above exist?

[Smooth613]

Good point about OBSE. The invalid argument seems to indicate it cannot locate obse_loader.exe.

 

Do you happen to have a check mark in the green box as pictured? http://img839.imageshack.us/img839/8753/wbtoolbar.png

 

Actually do you even have the green box with your Launch Buttons? If not then it would indicate that you do not have obse_loader.exe in the proper location.

[Elizinator]

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.