Jump to content

pls help wrye bash


gona91

Recommended Posts

Posted

 

@ germanicus : thanks you but it is BOSS 2.2 and im try install it still working and wryebash not launcher.

Posted

It is good to have newest program. Previous BOSS 2.1 didn't recognized some mods so I upgrade it to ver. 2.2 and it works fine now.

 

Here is the Wrye bash patch program that I'm using and it runs great. So, uninstall version you have and install this one. But, please, follow the instructions and make sure that you have all requirements because it won't work well or not work at all.

 

http://www.nexusmods.com/skyrim/mods/1840/?

Posted

Do you have latest update 1.9.31.0.8 for Skyrim? Also, if you're using Windows XP, Wrye Bash needs the MSVC++ 2005 SP1 Redistributable with ATL Security Update installed, the x86 version. This is required for the custom 7z executable that Wrye Bash uses to run. Later versions of Windows already have this installed.
 
If you're using the Standalone version, the only other thing you need to install manually is the MSVC++ 2008 Redistributable.   This is very important too: Note that the 32-bit versions are required even if you are on a 64-bit operating system
Then:

  • For manual installations of either the Standalone or Python versions, extract the archive in your Skyrim game folder so that the Mopy directory appears in the Skyrim directory
  • For Python versions, run by double-clicking on Wrye Bash Launcher.pyw
  • For WBSA (Wrye Bash StandAlone), run by double-clicking on Wrye Bash.exe

 

If you have all named dependencies, here is no reason for Wrye not to work properly. Check these. If you miss only one of them, the program will not work accordingly.

 

And the last tip:

If Bash Won't Start

•  If Bash refuses to start, or quits after quickly flashing up a window...

•  Most likely there is a problem with your setup. Alternatively there may be a bug with Bash.

•  You can usually figure out the problem by getting the bug dump and reviewing it. And if you can't puzzle it out, someone on the Elder Scrolls forums may be able to help.

•  Finding the Bugdump

•  Sometimes the error will be written to a file in the Mopy directory called bash.log. If that file is there, then that's the bug dump. You can open it with any text editor.

•  If it's not present, then you'll have to generate the bug dump yourself...

•  Generating the Bugdump

•  Open a command shell (Start: Programs: Accessories: Command Prompt).

•  chdir to the Mopy directory. "chdir" means "change directory". E.g.: chdir C:\Program Files\Bethesda Softworks\Oblivion\Mopy

•  Type: c:\python25\python.exe bash.py -d

•  If you have a different version/location of python, adapt the first argument accordingly.

•  Doing this will cause any error messages that Bash generates on start to spew to the command shell. This is the bugdump.

•  Dealing with Bugdump

•  First, look at it! – especially the last several lines – this will often give you a good clue as to what the problem is, and you may be able to resolve it on your own.

•  Second, see following section for common problems and their solution.

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...