Wrye Bash short-circuit?

[Helchor]

UPDATE: Solved by deleting pidfile.tmp in the Mopy folder.

 

Sup TESboard :)

 

Installed stuff: ES IV (latest), Shivering Isles, all DLCs, Unofficial patches, OOO, OBSE, OBMM, WBL (with the whole package of python stuff), and some other mods (about 30-40 or so). Latest versions of everything.

 

I've been experiencing a rather strange issue with my Wrye Bash Launcher. I got a friend to help me install all necessary stuff, and gave me example of some mods he recommended I'd try (I had only played the game on my 360 so I had no idea where to begin). Anyway, after some noob faults made by me, we got pretty much everything to work. Then came the installation of some larger mods (Better Cities I believe), and we had to set up the bashed patch. In the midst of all the downloading and installation of the last mods I wanted, WBL just didn't want to launch anymore (nothing happened when I tried to run the program). After trying pretty much everything, I had to reinstall Wrye Bash and the bundle of applications that it requires to run. Then, it worked perfectly, and finally I was able to finalize the mod installations and run the game.

 

Now, after having played about 10 hours, and without installing any new mods or modifying anything at all, the problem is back. I launched the program successfully a couple of times, but I didn't change anything. And now, completely uncalled for, it refuses to run.

 

Any thoughts on this? I have absolutely no idea. It's as if it has a life of its own. The process doesn't show up in task manager, and I receive no errors when trying to launch the application.

 

 

Thanks in advance for any help.

Edited November 28, 2010 by Helchor

[Smooth613]

Delete pidfile.tmp from you Oblivion\Mopy folder.

 

Launch Wrye Bash.

 

Common bug.

 

Will be fixed in v291.

[Helchor]

Delete pidfile.tmp from you Oblivion\Mopy folder.

 

Launch Wrye Bash.

 

Common bug.

 

Will be fixed in v291.

 

Thanks dude, it worked like a charm :)