Tes4Mod:Wrye Bash/Installation

The UESPWiki – Your source for The Elder Scrolls since 1995

Jump to: navigation, search

Contents

[edit] How to Install

For general info on how to install Wrye Bash, read the Wrye Bash Installation Guide.

If you run into problems, then read the If Bash Won't Start section of the installation guide.

Most problems are addressed in the installation guide. This page is primarily for problems with Windows Vista and a few other issues.

[edit] Windows XP Shortcuts

To make a shortcut for launching Wrye Bash in WinXP, try this procedure.

Right-click anywhere on your desktop and select New->Shortcut. You should get the Shortcut Wizard. When it asks you to type in the location, you'll need to type in something like this:

   C:\Python25\pythonw.exe "D:\games\Oblivion\Mopy\bash.py"

Where C:\Python25\pythonw.exe is your actual path to python.exe and D:\games\Oblivion is your actual path to the Oblivion folder.

After this, click Next and it will ask you to give the shortcut a name. Type in "Wrye Bash" (or whatever you want to call it). Next you can click Finish. The shortcut will be on your desktop, but it won't work yet because the "Start In" field is wrong. Right-click the shortcut and select Properties.

Now you'll see that the "Start In" field probably says:

   C:\Python25

You need to change this to say:

   D:\games\Oblivion\Mopy

Or whatever your path to \Oblivion\Mopy is (depending on where you installed Oblivion).

After doing this, click Apply or OK and the shortcut should work.

[edit] Windows Vista

Windows Vista has quite a bit of security that seems to interfere with games and possibly python/wxPython. Wrye runs under Windows XP, and so misses all of that fun. Also he has a 32bit machine and so doesn't have the experience to comment on 64 bit machines.

[edit] Vista UAC Problems

Paraphrasing Strategy Master:

On Windows Vista, the UAC (User Account Control) protects the Program Files directory (usually c:\Program Files) against write by regular users. This can be a problem for Bash and other mod editing and management tools (TESCS, TES4View, OBMM).
Best Solution: Install Oblivion to somewhere other than under the Program Files directory. (E.g, install to c:\Games\Oblivion). Such an alternate directory is not subject to UAC control and won't have the same access and virtualization problems that the default install will have.
Alternate Solutions: Alternatively, you might always run as admin, or turn off UAC -- but both of those approaches are ill-advised.
If your version of Vista allows access to NTFS permissions, add your user account to the permission list for the Oblivion directory and give it Read/Write access. This can be done via the context menu: Properties > Security. Click Edit > Add. Type your account name, click Ok. Check the Full control checkbox in the permissions list, then click Ok.

[edit] Eastwind: Bash on Windows Vista

Eastwind has gotten Bash to run on a 64 bit Windows Vista machine, and gives the following advice...

I am successfully running Wrye bash on Vista Ultimate 64-bit (also obse_loader, obmm, OOO and Oblivion). Of those Wrye Bash was the most challenging to get working. As the doc indicates, you have to install python 2.5 and wxPython 2.8.0.1 ANSI. I installed 32-bit versions of these, and run Wrye bash in 32-bit mode. I don't remember the exact details, but I probably installed everything using 32-bit command prompts run as administrator. The 32-bit command prompt is C:\Windows\SysWOW64\cmd.exe. Make a shortcut to this on the desktop, then run it by right-clicking and choose Run As Administrator. Use that window to do the installs.
I installed everything in various dirs under E:\programs\ not because I'd heard that it made any difference to Vista (someone said that above; I'm skeptical) but because I wanted it on my E drive and because some things ported from Unix can't handle the space in Program Files. I'd not be surprised if Python has that problem. Vista does have additional protection against writing to C:\ (root), that may be the source of the rumor.
I can't run Wrye bash using the short cuts that come with Wrye bash. I didn't work on fixing that, its probably due to python being intalled for 32-bit only. I followed the directions in the wrye bash help and run bash.py directly, from a 32-bit command prompt (without administrator privs). To make this easy I made another shortcut with the command line:
C:\Windows\SysWOW64\cmd.exe /k e:\programs\oblivion\mopy\bash.py
(your path to your bash.py will vary).
That starts the prompt and runs wrye bash in it, I get an extra black window from the command prompt but that doesn't ruin my day.
On 32-bit vista you don't need to worry about most of the above (but I still suggest installing everything under paths without any spaces), you just run the regular command prompt; the same trick of right-clicking on the short cut (under Accessories for 32-bit Vista) and choosing 'run as administrator' when doing the installs will probably be necessary.

Wrye responds:

I'm not sure how much of the above is actually necessary. I would have thought that you would just run the installers in the usual way (doubleclick the installer). I'd like to see confirmation by someone else that this involved procedure is actually necessary. (My suspicion is that simply following the regular Vista advice about installing Oblivion to an alternate directory, and then installing python, wxPython and bash in the usual way works.)
In short, I'm a bit dubious of this advice, but I really don't know one way or the other.

Kinseek responds:

I`m running Vista 64-bit, and had no problems installing or running python and bash. I installed the python versions linked on Wrye`s site, which worked without problems. I do not know why the person above went through all that hassle.

responds:

if running on xp 64 make sure to install the 32 bit packages of python. because the x64 versions contain different .dlls. Also you will have to tweak your shortcut. i had to change the 'start in' part to "c:\program files (x86)\Bethesda Softworks\oblivion\mopy\" making sure to enclose your oblivion path with " " or else it won't recognize the spaces in the folder names.

[edit] Vista 32-bit

Wrye Bash is working correctly when Python is installed in C:\Python25 (or C:\Python24, depending on version) and Oblivion is installed in C:\Spel\Bethesda Softworks\Oblivion, i.e. a non-standard directory, therefore circumventing the above mentioned problems with UAC.

I didn't to run any command promts or anything, I just double-clicked the installers, specified the paths, and Windows did the rest.

[edit] Python/wxPython Version

The bash readme suggests running under python 2.5, but Wrye personally runs Bash under the python 2.4 combination. While theoretically the newer python should be faster, it seems to have a few problems (esp. wxWindows).

Sponsored Links
Personal tools