Wrye Bash Launch Failure

[GooeyGungan]

I'm having (more or less) the same problem, except that I did install Python first.

 

Wrye Bash will start fine for the first few times, then, after some amount of times, it won't start. Period. I am running Windows 7 64 bit, I do have UAC disabled, but Oblivion is installed to Program Files (x86). I don't think that's the problem though, as I didn't have any problems until I upgraded from 275 to 290. Yes, I did install the full version of 289, then upgrade to 290.

 

I've figured out that I can fix this problem by just deleting the "Mopy" folder, and re-extracting the 289 and 290 archives, but that's a rather poor fix.

 

Also, sometimes if I go to delete the Mopy folder after closing Wrye Bash (if it won't start again), it says it's open in another program. I checked in the Task Manager, and pythonw.exe wasn't running. If I restart, Wrye Bash still won't start, but I can delete the folder.

 

On another (somewhat related) note, can you edit the ini to tell Wrye Bash to run a different program for a certain tool? I ask because the new version of BOSS wants you to run the .exe, while the older versions (that Wrye Bash is compatable with) want you to run the... .msi maybe? I don't have my computer with me, and I haven't tried the new version of BOSS yet, as the masterlist updates still work with the old version. Anyway, I'm sure that you're not supposed to run the .exe on the old version.

Sorry for being kinda off-topic, I just didn't want to start a new thread.

 

Thanks!

-GG

 

Edit: I forgot to mention that I haven't seen an error message. Am I not looking in the right place?

[Smooth613]

First when you install Wrye Bash you should avoid v289 completely. Instead go from 275 Self Installer > 287 Full > 290 Update. 288 and 289 are buggy and should be avoided completely. However this is unrelated to the issue you describe where Wrye Bash randomly won't launch.

 

With Wrye Bash 290 there is a very minor bug, very very minor, that happens where it doesn't properly delete a file when it closes. This file is pidfile.tmp. This file is created when Wrye Bash is running to let Wrye Bash know it's running to prevent you from opening multiple instances of the program. So all you need to do is go to your Mopy folder and delete pidfile.tmp when Wrye Bash randomly won't start. It will then start no problem.

 

This explains why when you delete the Mopy folder your problem would be "fixed", since you were deleting the temp file in the process. Usually this error only happens once and won't return after you delete pidfile.tmp. However if Wrye Bash, or Windows, crashes while Wrye Bash is open it's possible that this file gets left behind. Again, all you need to do is delete it so Wrye Bash doesn't think it's already open.

 

For your questions about BOSS. Wrye Bash 290 works just fine with the newer, 1.6x versions, of BOSS. These use the EXE. Wrye Bash 290 also includes options to set where BOSS will automatically update the Masterlist from the Google Repository every time you run BOSS. It's much more convenient than doing this manually every so often. Especially since the Masterlist is updated on a near daily basis. Under the Mods tab, right click the File header, place a check beside "BOSS disable Lock Times" and "Always update Masterlist prior to running BOSS".

 

I recommend using the newer versions of BOSS simply because of the Userlist feature. It's excellent for reordering mods or placing unknown mods in the proper places automatically. This way you don't have to hand place these mods every time you run BOSS.

[derilorn]

Wow, man you saved my life >< I could'nt start Wrye Bash anymore, and fell on this topic (i'm french forgive my bad english ^^) . I reinstalled Python quite a few times, then Wrye itself (from v287 to v290) but it still would'nt load !

So i checked if this "pidfile.tmp" was the source of my problem, and it was indeed !

it seems to still be in the folder even if you desinstall it well. I did have it because my computer shut off while playing to oblivion with wrye bash open.

This is a cool piece of advice for all those like me who struggle using this AWESOME TOOL without i would'nt like playing and modding oblivion at all (OBMM is really weak and has a lack of options).

So thanks again Smooth613, and if you could tell the men in charge of Wrye this problem causes annoying crashes that would be even greater ( i mean you seem to be know very well this programm ).

[PacificMorrowind]

So thanks again Smooth613, and if you could tell the men in charge of Wrye this problem causes annoying crashes that would be even greater ( i mean you seem to be know very well this programm ).

291 which is the in dev version (which I'm really really hoping to release by the end of the week) has had that fixed since a couple days after release of 2990.

Pacific Morrowind

(one Wrye Bash's developers if you haven't been following the developement of Bash lately - er last year and a half anyways)

[Drakeero]

Well, I'm having a very similar problem as the OP. I'm about to uninstall Oblivion and re-install it outside the (x86) folder, but when I played around trying to get Wrye Bash to launch I checked the properties of the launcher (no console) file and saw that it was supposed to open with Pythonw.exe

 

I attempted to start Pythonw.exe and it did absolutely nothing whatsoever. The Python.exe right above it starts a dos prompt that I don't know jackall about, but Pythonw.exe does zip, zero, null, zilch. Could this be part of the problem?

 

Here's the details of the steps I followed to try to get everything together. Please forgive me as I am not an experienced Oblivion modder or programmer. I'd be happy to stick with OBMM except there's an All Natural weather mod that requires Wrye Bash.

 

1: From what I could understand from the various Wrye Bash tutorials I started by finding an old copy of a wxPython2.8 installer. The full file name is wxPython2.8-win32-ansi-2.8.7.1-py25.exe

It was supposed to be 2.8.7.1 because I read that Wrye Bash was not compatible with any later versions. The installation went well.

 

2: Next up I read that I needed to install some sort of expansion or something called Wrye Python. After some time searching the best candidate I could find was Wrye_Python_03a-22368.exe. I'll be honest, I have no clue what that strange alpha-numerical code at the end of the file name means. Installation also seemed to go well.

 

3: Finally the Wrye_Bash_275_-_Self_Installer-22368.exe from the TES NEXUS website. Flew through the installation but I got the Wrye Bash Launcher.pyw file with (no console) in the file type description.

[Smooth613]

Well the first step you mention is unnecessary and I'm not sure which tutorial you got that from, unless it's an older one. All you need to do is install WryePython03a as far as Python is concerned. You should also refer to the ReadMe file included in the Wrye Bash download for Installation Instructions. It's located in the Mopy folder.

 

However the file you're looking for is located in your Oblivion\Mopy folder, Wrye Bash Launcher.pyw. When you hover over that with the mouse you'll see it says (no console). That is where you launch Wrye Bash from. You can create a shortcut of that file and send to desktop and you're good to go.

 

However I suggest you follow the following procedure to remove any unneeded files and ensure you have the most recent version of Wrye Bash running. Steps below...

 

1. Go to Control Panel and remove anything with the word Python in it.
   
2. Next, uninstall Wrye Bash and delete the Mopy folder. You used the installer version so you should have an uninstaller as well.
   
3. After you have removed everything related to Python and Wrye Bash it's time to reinstall, properly.
   
4. Install WryePython03a from the Wrye Bash page here on TESNexus
   
5. Install Wrye Bash 275 from the Self-Installer
   
6. Update to Wrye Bash 287 by overwriting the Oblivion\Mopy folder.
   
7. Finally, Update to Wrye Bash 290 by again overwriting the Mopy folder.
   
8. Go to your Oblivion Mopy folder and create a shortcut for Wrye Bash Launcher.pyw and send to desktop.
   
9. You're done! Double click the shortcut and Wrye Bash should launch and you're good to go.
   

 

The Wrye Bash Pictorial Guide for Newbies is also and excellent way to get your hands dirty with Wrye Bash. Check it out!

 

If Wrye Bash fails to start you need to post the bug dump information here, or in the Official Thread @ BethSoft for someone to look over.

 

Good luck.

[Drakeero]

Thank you, I followed your directions exactly using all the files provided on the TES NEXUS Wrye Bash page.

 

I still have the same problem. Wrye Bash will not start even using the desktop icon. The only difference is now I get the "thinking" mouse icon for a few moments before it reverts back to normal.

 

Because it does not even seem to start no bug dump is created. I've tried creating my own using the command prompt [as instructed by the Wrye Bash html documentation] but I am running Win7 and my Oblivion is still in the Program Files (x86) folder which I can't seem to get it to change directory to. It can find Program Files just fine but not Program Files (x86).

[Smooth613]

Because it does not even seem to start no bug dump is created. I've tried creating my own using the command prompt [as instructed by the Wrye Bash html documentation] but I am running Win7 and my Oblivion is still in the Program Files (x86) folder which I can't seem to get it to change directory to. It can find Program Files just fine but not Program Files (x86).

There's your problem. Reinstall Oblivion to another directory outside the jurisdiction of UAC. Windows is preventing access because it sees this as a security threat. You'll only run into more problems down the road if you leave your installation inside Program Files. I suggest something along the lines of <drive letter>\Games\Oblivion. You can use Bben's Installation Procedure to help you with proper installation.

Edited December 2, 2010 by Smooth613

[Drakeero]

Ah, wow. That worked very well. I re-installed the game, then instead of re-installing Wyre Bash or all my other mods I just dragged and merged the old (x86) folders with the new folders in the new directory. Everything's working fine so far. Cheers! And to good fortune with the future use of Wyre Bash!

[Jediron]

Took me a while to find this forum thread, as i have simular problems. Even worse, i guess. I did all of the above now, and still 290 will not load.

 

I am using Win 7 64bit, Oblivion is, like all my games on D:\games , i konw about UAC and that aint a issue for me. 275 installs and runs fine, 287 runs fine but as soon as i copy the 290 version, the party is over.

And i don't have that *.tmp file you speak off, so that ain't the issue either. I am just wondering, instead of let people trhow patch over another patch, would'n it be nice to have a FULL 290 installer, so that those issue's cannot even occur ? Or even mention it more clearly in the topic's at TES and in the guide (which is outdated anyway, with broken links and outdated information).

 

Sorry, but i am a little pissed...haha. No hard feelings though ;-)