thrillseeker3242 Posted January 11, 2011 Share Posted January 11, 2011 I've been using Wrye Bash for a long time, including the computer I'm currently using it on, and it was working fine, until some time recently. Before I couldn't get it to start, unless I did the procedure to generate a bugdump...at which point it would start and seemed to function normally. But it didn't actually create a bugdump. Now when do the same thing, it just says "already started" and then exits. Still no bugdump. (It's supposed to be a file called bash.log in ~/Oblivion/Mopy, right?) I don't know what I did recently to cause the change. Any ideas? Using Win7 64, Wrye Bash 290(?), Python 2.6 Link to comment Share on other sites More sharing options...
Smooth613 Posted January 11, 2011 Share Posted January 11, 2011 Delete pidfile.tmp from your Oblivion\Mopy folder. Link to comment Share on other sites More sharing options...
thrillseeker3242 Posted January 12, 2011 Author Share Posted January 12, 2011 It worked! Thanks! Link to comment Share on other sites More sharing options...
Ichiurto Posted January 12, 2011 Share Posted January 12, 2011 Is there anyway to make Wrye Bash auto-delete that file? It does it upon a normal (Hit X in corner) exit, but when you have Auto-Exit on (Because there is no reason to have it running while Oblivion is running as far as I know) it doesn't. Very annoying, but harmless. Link to comment Share on other sites More sharing options...
Gogmogog Posted February 3, 2011 Share Posted February 3, 2011 I have the same problem (same specs and everything) but i have no pidfile.tmp to delete? I can't find anyone else with the same problem, it just says "started already" in the bugdump. Link to comment Share on other sites More sharing options...
Hickory Posted February 3, 2011 Share Posted February 3, 2011 Is there anyway to make Wrye Bash auto-delete that file? It does it upon a normal (Hit X in corner) exit, but when you have Auto-Exit on (Because there is no reason to have it running while Oblivion is running as far as I know) it doesn't. Very annoying, but harmless. The latest version of Wrye Bash (291) addresses this issue. Link to comment Share on other sites More sharing options...
Recommended Posts