[RELZ] Wrye Bash -- Thead 56

Post » Wed Sep 01, 2010 10:27 am

Hey,
I once installed Wrye Bash just fine, but I needed to reinstall Oblivion and removed Wrye Bash and Python components. Now I tried to reinstall it, and I tried to follow instructions and readmes the best I could- I installed all the required Python components and Wrye Bash installer from TES Nexus, but now instead of launching Wrye Bash, it launches some License and Copyright Notice message. Also there is a green snake for the icon instead of the blue and yellow symbol that I'm used to.

I know this is probably a newbie oversight on my part and I'd hate to sound like I haven't read any readmes or attempted to figure things out. I've gotten it to work before and I don't know why I can't anymore. I tried my best to read the readmes and all that, so forgive me if it's just something I overlooked. I really don't understand this kind of stuff very easily.
User avatar
Big mike
 
Posts: 3423
Joined: Fri Sep 21, 2007 6:38 pm

Post » Wed Sep 01, 2010 10:40 pm

Hey,
I once installed Wrye Bash just fine, but I needed to reinstall Oblivion and removed Wrye Bash and Python components. Now I tried to reinstall it, and I tried to follow instructions and readmes the best I could- I installed all the required Python components and Wrye Bash installer from TES Nexus, but now instead of launching Wrye Bash, it launches some License and Copyright Notice message. Also there is a green snake for the icon instead of the blue and yellow symbol that I'm used to.

I know this is probably a newbie oversight on my part and I'd hate to sound like I haven't read any readmes or attempted to figure things out. I've gotten it to work before and I don't know why I can't anymore. I tried my best to read the readmes and all that, so forgive me if it's just something I overlooked. I really don't understand this kind of stuff very easily.

It's not the most intuitive kinda stuff, truth be told. ;)

Personally, I would opt for the archive (i.e., manual) version of Wrye Bash, then apply the latest update manually as well. After installing Wrye Python 3.0a completely, of course.

Just copy the Data and Mopy folders directly to Oblivion\ and say "yes" to over-writing at any stage.

Hope that helps, even a bit.
User avatar
Bonnie Clyde
 
Posts: 3409
Joined: Thu Jun 22, 2006 10:02 pm

Post » Wed Sep 01, 2010 6:27 pm

It's not the most intuitive kinda stuff, truth be told. ;)

Personally, I would opt for the archive (i.e., manual) version of Wrye Bash, then apply the latest update manually as well. After installing Wrye Python 3.0a completely, of course.

Just copy the Data and Mopy folders directly to Oblivion\ and say "yes" to over-writing at any stage.

Hope that helps, even a bit.


Yes, I've installed Wrye Python. What gets me is that the link on his website is broken, and so the only other link for Wrye Bash that I can find is the one in TES Nexus.

I'm led to believe that the Wrye Python package was somehow installed incorrectly... I also tried installing all the components individually but that didn't work either. The fact that all Python files are now a picture of a snake instead of the blue and yellow symbol that I used to have when it worked... really confuses me and ticks me off. I don't understand how I've installed any of this incorrectly or any differently from how I first did it.

The main difference is that the file that should be on http://wryemusings.com/Wrye%20Bash.html where it says "download and upzip" is broken... and I think that is where I got it last time back when it actually worked.

Where can I go about finding this archive and update? Tes Nexus? All I see is an update archive, but no single archive without an instlaler.
User avatar
Far'ed K.G.h.m
 
Posts: 3464
Joined: Sat Jul 14, 2007 11:03 pm

Post » Thu Sep 02, 2010 2:26 am

Not very helpfully, it's under "old versions". :shrug:

Even so, that's what I'm using (after applying the update from the same page at the Nexus). Seems OK.
User avatar
Rob Smith
 
Posts: 3424
Joined: Wed Oct 03, 2007 5:30 pm

Post » Wed Sep 01, 2010 4:57 pm

Thanks, I just tried to install this old version and the archive update, but neither of them fixed the problem. Again, the file type icon ITSELF seems to be different, which leads me to believe that downloading the Python package messed up smoehow, and I don't know what to do to fix it. Trying to run the Wrye Bash Launcher still brings me to this message.

Spoiler
# GPL License and Copyright Notice ============================================
# This file is part of Wrye Bash.
#
# Wrye Bash is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# Wrye Bash is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with Wrye Bash; if not, write to the Free Software Foundation,
# Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
#
# Wrye Bash copyright © 2005, 2006, 2007, 2008, 2009 Wrye
#
# =============================================================================

"""This module starts the Wrye Bash application. Basically, it runs some
initialization functions, and then starts the main application loop.

bash [-o OblivionPath] [-u userPath] [-p personalPath] [-l localAppDataPath] [-d] [0]
----
For all arguments:
Note that Python reads the backslash "\" as an escape character,
(that is, the backslash itself is ignored and the following character is read literally)
so for any paths you'll want to either use two backslashes (C:\\Folder\\)
or a forwardslash (C:/Folder/).

All arguments except the -d Debug can be set in the .ini file.
Arguments have precedence over ini settings.
You can use a mix of arguments and ini settings.
Ini settings don't require a double backslash and can have relative paths.
----
Oblivion directory argument (-o).
-o OblivionPath: Specify Oblivion directory (containing Oblivion.exe).
Use this argument if Bash is located outside of the Oblivion directory.
Example: -o "C:\\Games\\Oblivion\\"
----
User directory arguments (-u, -p, and -l).
These arguments allow you to specify your user directories in several ways. These
are only useful if the regular procedure for getting the user directory fails.
And even in that case, the user is probably better off installing win32com.
However, the arguments are:

-u userPath: Specify the user profile path. May help if HOMEDRIVE and/or HOMEPATH
are missing from the user's environgment.
Example: -u "C:\\Documents and Settings\\Wrye"

-p personalPath: Specify the user's personal directory.
If you need to set this then you probably need to set -l too.
Example: -p "C:\\Documents and Settings\\Wrye\\My Documents"

-l localAppDataPath: Specify the user's local application data directory.
If you need to set this then you probably need to set -p too.
Example: -l "C:\\Documents and Settings\\Wrye\\Local Settings\\Application Data"
----
Debug argument:
-d Send debug text to the console rather than to a newly created debug window.
Useful if bash is crashing on startup or if you want to print a lot of
information (e.g. while developing or debugging).
"""

# Imports ---------------------------------------------------------------------
import getopt
import os
import sys
if sys.version[:3] == '2.4':
import wxversion
wxversion.select("2.5.3.1")
import bosh
#--Parse arguments
optlist,args = getopt.getopt(sys.argv[1:],'o:u:p:l:d')
#--Initialize Directories and some settings
# required before the rest has imported
opts = dict(optlist)
oblivionPath = opts.get('-o')
if '-u' in opts:
drive,path = os.path.splitdrive(opts['-u'])
os.environ['HOMEDRIVE'] = drive
os.environ['HOMEPATH'] = path
elif os.path.exists('bash.ini'):
import ConfigParser
bashIni = ConfigParser.ConfigParser()
bashIni.read('bash.ini')
if bashIni.has_option('General', 'sUserPath') and not bashIni.get('General', 'sUserPath') == '.':
drive,path = os.path.splitdrive(bashIni.get('General', 'sUserPath'))
os.environ['HOMEDRIVE'] = drive
os.environ['HOMEPATH'] = path
personal = opts.get('-p')
localAppData = http://forums.bethsoft.com/index.php?/topic/1150534-relz-wrye-bash-thead-56/opts.get('-l')
bosh.initDirs(personal,localAppData,oblivionPath)
import basher
import bolt
import atexit

# adapted from: http://www.effbot.org/librarybook/msvcrt-example-3.py
from os import open as _open, O_CREAT, O_EXCL, O_RDWR

pidpath = bosh.dirs['mopy'].join('pidfile.tmp').s
lockfd = None

def exit():
try:
os.close(lockfd)
os.unlink(pidpath)
except OSError, e:
print e
return 0

def oneInstanceChecker():
global lockfd
try:
lockfd = _open(pidpath, O_CREAT|O_EXCL|O_RDWR)
os.write(lockfd, "%d" % os.getpid())
except OSError, e: # Already locked
print 'already started'
lockfd = None
return False
return True

# Main ------------------------------------------------------------------------
def main():
#import warnings
#warnings.filterwarnings('error')
#--More Initialization
if not oneInstanceChecker():
return False
atexit.register(exit)
basher.InitSettings()
basher.InitLinks()
basher.InitImages()
#--Start application
if '-d' in opts or (args and args[0] == '0'):
app = basher.BashApp(False)
bolt.deprintOn = True
else:
app = basher.BashApp()
app.MainLoop()

if __name__ == '__main__':
try:
args = sys.argv[1:]
if '-d' not in args and '0' not in args:
import psyco
psyco.full()
except:
pass
main()


User avatar
Jack
 
Posts: 3483
Joined: Sat Oct 20, 2007 8:08 am

Post » Wed Sep 01, 2010 6:37 pm

Did you follow the links from the OP
Requirements:

?It's easiest to just download the WryePython03a package from TesNexus unless you like to customize your install.
(Python 2.6.5 or Python 2.6.6), wxpython 2.8.11.0 ansi, ComTypes, psyco 1.6 for Python 2.6, and PyWin32 for Python 2.6
Older/Newer versions _may_ work but those are probably the most widely used and tested


Download: TesNexus or Sourceforge
User avatar
Cesar Gomez
 
Posts: 3344
Joined: Thu Aug 02, 2007 11:06 am

Post » Wed Sep 01, 2010 6:26 pm

Did you follow the links from the OP
Requirements:

?It's easiest to just download the WryePython03a package from TesNexus unless you like to customize your install.
(Python 2.6.5 or Python 2.6.6), wxpython 2.8.11.0 ansi, ComTypes, psyco 1.6 for Python 2.6, and PyWin32 for Python 2.6
Older/Newer versions _may_ work but those are probably the most widely used and tested


Download: TesNexus or Sourceforge


Yes, after I tried installing the Python package from Wrye's website I also tried to install it from TesNexus too.
User avatar
x a million...
 
Posts: 3464
Joined: Tue Jun 13, 2006 2:59 pm

Post » Wed Sep 01, 2010 11:43 am

Maybe the http://www.tesnexus.com/downloads/file.php?id=35230
User avatar
ruCkii
 
Posts: 3360
Joined: Mon Mar 26, 2007 9:08 pm

Post » Wed Sep 01, 2010 6:46 pm

Maybe the http://www.tesnexus.com/downloads/file.php?id=35230


I may be wrong but it seems to me that guide doesn't cover installing Wrye Bash, but USING it.

The thing is I have already once installed Wrye Bash successfully before. And I've read through the installation process multiple times. The fact that I can't install it right now, even while following instructions explicitally, it's really driving me crazy.

I've done everything essentially right- I've installed things in the correct orders, even uninstalled all the componentst and reinstalled them from different locations. Tried the installer form of Wrye Bash to the archive form and nothing works, I always get that annoying green snake icon for the Wrye Bash launcher, and it brings me to that notice instead of the actual program that I want.

I'm doing everything right, I'm almost positive I am. I don't know what's causing all this.

I've pretty much ruined my game, or at least how I want to play it- without Wrye Bash I can't get all the mods I want working properly together and I can't continue to repair my hard work at getting one of my characters back into the game... I feel stuck now on this Wrye Bash nonsense because I think I am doing everything right, but it is still coming out wrong. If anyone could help me some time I'd really appreciate it.



EDIT: More details. Just to be sure I was installing it right, I installed it onto my laptop the exact same way I did it on my desktop. Lo and behold- it worked just fine on my laptop. So there is definitely something going on here on my Vista machine vs. my XP Laptop.

I have User Account Controls disabled so that Vista won't do any weird conflicts. It was the unrecommended option to fix the UAC issue that Oblivion has, but it was still listed on the Wrye page as an option.


EDIT AGAIN: The delimma continues. I found that Python v2.5, which I had in my hard drive when I originally installed Bash, was still there sitting right next to the new 2.6 that I installed. So I deleted it and 2.6, once again I uninstalled every Python component using add/remove programs. Then I tried to reinstall everything... and now Windows doesn't recognize any Python files at all! I SWEAR I installed everything correctly, just as I did on my laptop when it worked... now I can't even launch Wrye Bash at all... At least earlier it had SOME sort of recognition, but now when I launch the Wrye Bash Launcher.pyw file, Windows doesn't know what to do with it at all.

I had uninstalled all Python components and looked around in my program files for any left-over things before I attempted to reinstall again, but to no avail. I must've uninstalled/reinstalled it over and over so many times by now and there's absolutely no way for me to know what will work and what won't... My laptop is not powerful enough to actually run oblivion, and so this is really depressing me. >.<

I really hope someone has a solution... because at this point I have no idea what I'm doing wrong or what my system is messing up with. I swear I did everything right- I know for sure because I did the same thing on my laptop that I'm doing on my PC.

The issue might reside somewhere in the fact that I have installed Wrye Bash before, a long time ago- and it worked *fine*. It was probably using an older build of Python and something might be conflicting somewhere. I have no idea what, or how... I really hope someone knows...
User avatar
Travis
 
Posts: 3456
Joined: Wed Oct 24, 2007 1:57 am

Post » Wed Sep 01, 2010 6:13 pm

There's a 291 Installer version floating around somewhere, otherwise, the latest was 275, then you'd need to drop ~285 ob top and 29x on top of that, but make sure if you've got Python ibstalled properly, then Right Click on "Wrye Bash Launcher.pyw" in your Mopy directory, and select "Open With", and navegate out to your pythonw,exe program... :shrug:
User avatar
Elizabeth Falvey
 
Posts: 3347
Joined: Fri Oct 26, 2007 1:37 am

Post » Wed Sep 01, 2010 1:45 pm

There's a 291 Installer version floating around somewhere, otherwise, the latest was 275, then you'd need to drop ~285 ob top and 29x on top of that, but make sure if you've got Python ibstalled properly, then Right Click on "Wrye Bash Launcher.pyw" in your Mopy directory, and select "Open With", and navegate out to your pythonw,exe program... :shrug:


As for telling Windows to force it to open with pythonw.exe, I've already tried that and to no avail. But your first suggestion, I haven't tried. Could you perhaps be a little more specific such as the timing of what you think I need to do? I personally don't see how it would make a difference- but I will try it if I can make more sense of it, I'm a little slow with this kind of thing and would need a bit more specific instruction and clarification, if you have time time to provide it.
User avatar
Niisha
 
Posts: 3393
Joined: Fri Sep 15, 2006 2:54 am

Post » Wed Sep 01, 2010 5:18 pm

As for telling Windows to force it to open with pythonw.exe, I've already tried that and to no avail. But your first suggestion, I haven't tried. Could you perhaps be a little more specific such as the timing of what you think I need to do? I personally don't see how it would make a difference- but I will try it if I can make more sense of it, I'm a little slow with this kind of thing and would need a bit more specific instruction and clarification, if you have time time to provide it.

You may have registry errors. I suggest you get a registry cleaner / checker and verify you do not have any left over entries for python.
Then try another install using the http://tesnexus.com/downloads/file.php?id=22368.
FYI, Python 2.5 and Python 2.6 work fine together, but I also did as you did and removed 2.5.

I don't know if you are running 64 bit Vsta, but if you are, do not install the 64 bit version of python. Wrye Bash only works with the 32 bit version.
User avatar
Strawberry
 
Posts: 3446
Joined: Thu Jul 05, 2007 11:08 am

Post » Wed Sep 01, 2010 3:53 pm

You may have registry errors. I suggest you get a registry cleaner / checker and verify you do not have any left over entries for python.
Then try another install using the http://tesnexus.com/downloads/file.php?id=22368.
FYI, Python 2.5 and Python 2.6 work fine together, but I also did as you did and removed 2.5.

I don't know if you are running 64 bit Vsta, but if you are, do not install the 64 bit version of python. Wrye Bash only works with the 32 bit version.


I believe I am running 32 bit Vista. I just downloaded a Free Windows Registry Cleaner. I am just now running a scan, so... I'll have my fingers crossed.
User avatar
Oscar Vazquez
 
Posts: 3418
Joined: Sun Sep 30, 2007 12:08 pm

Post » Wed Sep 01, 2010 9:28 pm

Somehow my version of bash_default.ini is corrupted and it only has two examples - the code for the file path for the Oblivion Mods directory and the code for the settings for Tes4Gecko.jar.

All the other entries withexample lines of code are missing from my bash_default.ini. This is very problematic because I can't create a proper bash.ini file and the only way I can launch Wrye Bash is by deleting the bash.ini file, in which case I'm able to create a bashed patch but not able to import specific mods from the Bash Installers folder that require this for installation, such as the All Natural mod.

The following is the entire text of my bash_default.ini file

Spoiler
;--This is the generic version of Bash.ini. If you want to set values here,
; then copy this to "bash.ini" and edit as desired.

[General]
;--sOblivionMods is the Alternate root directory for installers, etc. You can
; use absolute path (c:\Games\Oblivion Mods) or relative path, where path
; is relative to Oblivion install directory. It is strongly recommended that
; you do NOT put it anywhere under the Oblivion install directory itself,
; since (due to a bug), Oblivion.exe will at times search through every directory
; under the install directory. This "directory thrashing" can then cause performance
; problems during gameplay. sOblivionMods is defined specifically to circumvent
; this bug by storing files elsewhere.
sOblivionMods=..\Oblivion Mods
;--sTes4GeckoJavaArg is the memory size argument used for launching Tes4Gecko if it's
; present. (Note the Tes4Gecko.jar file must be in the Oblivion install directory.
sTes4GeckoJavaArg=-Xmx1024m


I would prefer not to reinstall Wrye Bash again using the installer for fear of corrupting something else or affecting one of the mods or the bashed patch. Would it be possible for someone to paste here the complete text of the correct bash_default.ini file?

EDIT: I figured out what was preventing me from launching Wrye Bash - I was missing the line "[General]" at the top.

Here is the complete text of my current bash.ini file - using this I am able to launch Wrye Bash properly, but on the installers tab, Wyre Bash does not recognize any of the mod archives that have been placed in the Bash Installers folder. Is there a different example line of code I need to add that instructs Wrye Bash where to find these archive files?

Spoiler
[General]
sOblivionMods=C:\Program Files (x86)\Steam\steamapps\common\Oblivion Mods\
sOblivion=C:\Program Files (x86)\Steam\steamapps\common\oblivion\
sBashInstallers=C:\Program Files (x86)\Steam\steamapps\common\Oblivion Mods\Bash Installers
sTes4GeckoJavaArg=-Xmx1024m

User avatar
Kevin Jay
 
Posts: 3431
Joined: Sun Apr 29, 2007 4:29 am

Post » Wed Sep 01, 2010 9:02 pm

I would prefer not to reinstall Wrye Bash again using the installer for fear of corrupting something else or affecting one of the mods or the bashed patch.

I would not worry about these things. WB is perfectly simple to install and/or reinstall once you have the Wyre Python package 03a installed. And the Bashed Patch is always a temporary file anyway - only valid until the next rebuild. So I would just erase everything (other than arcives in the BAIN installation folder) and reinstall everything (not on the C: path). I think that is better than manually editing the .ini file.

What I would do is make backup copies of all the archives in your BAIN install folder, just in case. Especially if you have hand-built any BAIN projects or archives there.
User avatar
GabiiE Liiziiouz
 
Posts: 3360
Joined: Mon Jan 22, 2007 3:20 am

Post » Thu Sep 02, 2010 2:33 am

I would not worry about these things. WB is perfectly simple to install and/or reinstall once you have the Wyre Python package 03a installed. And the Bashed Patch is always a temporary file anyway - only valid until the next rebuild. So I would just erase everything (other than arcives in the BAIN installation folder) and reinstall everything (not on the C: path). I think that is better than manually editing the .ini file.

What I would do is make backup copies of all the archives in your BAIN install folder, just in case. Especially if you have hand-built any BAIN projects or archives there.


Thanks for the tip. I went ahead and deleted the previous files and reinstalled Wrye Bash.

Unfortunately, I got exactly the same bash_default.ini file with exactly the same text. Isn't it missing some of the other entries? There are only two example entries included in the text - one entry with the file path for the oblivion mods folder and the other entry with the setting for Tes4Gecko.jar.
Spoiler
complete text of bash_default.ini as follows:
;--This is the generic version of Bash.ini. If you want to set values here,
; then copy this to "bash.ini" and edit as desired.

[General]
;--sOblivionMods is the Alternate root directory for installers, etc. You can
; use absolute path (c:\Games\Oblivion Mods) or relative path, where path
; is relative to Oblivion install directory. It is strongly recommended that
; you do NOT put it anywhere under the Oblivion install directory itself,
; since (due to a bug), Oblivion.exe will at times search through every directory
; under the install directory. This "directory thrashing" can then cause performance
; problems during gameplay. sOblivionMods is defined specifically to circumvent
; this bug by storing files elsewhere.
sOblivionMods=..\Oblivion Mods
;--sTes4GeckoJavaArg is the memory size argument used for launching Tes4Gecko if it's
; present. (Note the Tes4Gecko.jar file must be in the Oblivion install directory.
sTes4GeckoJavaArg=-Xmx1024m


Aren't there additional missing entries here? For some reason, even after re-installation, Wrye Bash does not acknowledge any of the mod archives placed in the Bash Installers folder. The Installation tab within Wrye Bash is completely blank.

It would be much appreciated if anyone else can paste the text of their bash_default.ini file here , or provide any guidance on how to get Wrye Bash to recognize the correct path for the Bash Installers folder and/or recognize archive files placed in the bash installers folder.
User avatar
Lil Miss
 
Posts: 3373
Joined: Thu Nov 23, 2006 12:57 pm

Post » Thu Sep 02, 2010 1:00 am

@BootySweat
First, make sure you have the latest stable version of Wrye Bash (either version 287, 290 or 291 beta). If you already do, you can either try redownloading (recommended) or copy my bash_default.ini:
Spoiler
; ____ _ _ _ ___ ___ _____
; | _ \ | | (_) (_) |__ \ / _ \ | ____|
; | |_) | __ _ ___| |__ _ _ __ _ ) || (_) || |__
; | _ < / _` / __| '_ \ | | '_ \| | / / > _ < |___ \
; | |_) | (_| \__ \ | | |_| | | | | | / /_ | (_) | ___) |
; |____/ \__,_|___/_| |_(_)_|_| |_|_| |____| \___/ |____/

;--This is the generic version of Bash.ini. If you want to set values here,
; then copy this to "bash.ini" and edit as desired.

; Bool option (b*****) - use any of:
; True, 1, Yes, On
; False, 0, No, Off

; Paths - You can use either:
; Absolute Path
; Example=C:\Games\Oblivion Mods
; Relative path, where path is relative to the Oblivion install directory
; Example=Tools\Tes4Files.exe
; _____ _
; / ____| | |
; | | __ ___ _ __ ___ _ __ __ _ | |
; | | |_ | / _ \| '_ \ / _ \| '__|/ _` || |
; | |__| || __/| | | || __/| | | (_| || |
; \_____| \___||_| |_| \___||_| \__,_||_|

[General]
;--sOblivionMods is the Alternate root directory for installers, etc.

; It is strongly recommended that you do NOT put it anywhere under the
; Oblivion install directory itself, because Oblivion.exe will search through
; every directory under the install directory.
; This "directory thrashing" can then cause performance problems during gameplay.
; sOblivionMods is defined specifically to circumvent this bug by storing files elsewhere.
sOblivionMods=..\Oblivion Mods

;--OblivionPath is the Oblivion directory (containing Oblivion.exe).
; Use this argument if Bash is located outside of the Oblivion directory.
; If using a relative path, will be relative to the Mopy directory
; Example=C:\Games\Oblivion
sOblivionPath=.

;--User directory arguments.
; These arguments allow you to specify your user directories in several ways.
; These are only useful if the regular procedure for getting the user directory fails.
; And even in that case, the user is probably better off installing win32com.

;--UserPath is the user profile path.
; May help if HOMEDRIVE and/or HOMEPATH are missing from the user's environment.
; Example=C:\Documents and Settings\Wrye
sUserPath=.

;--PersonalPath is the user's personal directory.
; Must be used in conjunction with the -l argument.
; Example=C:\Documents and Settings\Wrye\My Documents
sPersonalPath=.

;--LocalAppDataPath is the user's local application data directory.
; Must be used in conjunction with the -p argument.
; Example=C:\Documents and Settings\Wrye\Local Settings\Application Data
sLocalAppDataPath=.

; _____ _ _ _
; / ____| | | | | (_)
; | (___ ___ | |_ | |_ _ _ __ __ _ ___
; \___ \ / _ \| __|| __|| || '_ \ / _` |/ __|
; ____) || __/| |_ | |_ | || | | || (_| |\__ \
; |_____/ \___| \__| \__||_||_| |_| \__, ||___/
; __/ |
; |___/
[Settings]
;--For various options in Bash

;--sScriptFileExt is the extention that will be used for the exported scripts
; when running 'Export Scripts' (defaults to .txt)
sScriptFileExt=.txt

;--iKeepLog: is how much log to record- set to a number in between 0 and 4
; with 0 being no log, and 4 being maximum logging (not fully implemented yet)
iKeepLog=0

;--sLogFile: where to save the log to, defaults to Mopy/bash.log
sLogFile=mopy\bash.log

;--iIconSize is the size (in pixels) for the tool launcher icons. Valid entries
; are 16 and 32. Or if you want a different size create new icons with the same
; names as the *32.png but with the 32 changed to whatever size you want.
iIconSize=16

;--bEnableWizard: whether or not to enable the scripted installation ability
; if enabled Bash REQUIRES the Python WinAPI to be installed -- or Bash will not start
; (1 or 0 or True or False)
bEnableWizard=False

;--bSkipResetTimeNotifications: whether or not to skip notification about mod
; modification times reset by Lock Times.
; (1 or 0 or True or False)
bSkipResetTimeNotifications=False

;--bShowTextDifference****: toggles display of a text difference in the mods tab for that type of mod
bShowTextDifferenceMergeable=True
bShowTextDifferenceNoMerge=True
bShowTextDifferenceRegular=True
bShowTextDifferenceESM=True

;--o*****TextColour: what colour of text to display in the mods tab for that type of mod
; can be any valid wxPython colour or an RGB tuple
oDeactivateTextColour=wx.BLACK
oESMTextColour=wx.BLUE
oMergeableTextColour=(0x00,0x99,0x00)
oNoMergeTextColour=(153,0,153)
oRegularTextColour=wx.BLACK

;--s*****TextStyle: What style of text to display in the mods tab for that type of mod
; can be any valid wxPython text style.
oDeactivateTextStyle=(8, wx.NORMAL, wx.SLANT, wx.NORMAL)
oESMTextStyle=Default
oMergeableTextStyle=Default
oNoMergeTextStyle=Default
oRegularTextStyle=Default

;bAutoItemCheck: determines whether to automatically check new items in the bashed patch
bAutoItemCheck=False

;bSkipHideConfirmation: determines whether the hide confirmations are shown
bSkipHideConfirmation=False

; _______ _ ____ _ _
; |__ __| | | / __ \ | | (_)
; | | ___ ___ | | | | | | _ __ | |_ _ ___ _ __ ___
; | | / _ \ / _ \ | | | | | || '_ \ | __|| | / _ \ | '_ \ / __|
; | || (_) || (_) || | | |__| || |_) || |_ | || (_) || | | |\__ \
; |_| \___/ \___/ |_| \____/ | .__/ \__||_| \___/ |_| |_||___/
; | |
; |_|
[Tool Options]

; all tool launcher options for paths can be absolute paths or relative from the head
; of the oblivion folder (that's the one with your Oblivion.exe in it). Any others are explained with the option.

;--Whether or not to show the various larger non core tool launcher segments
bShowTextureToolLaunchers=True
bShowModelingToolLaunchers=True
bShowAudioToolLaunchers=True

;==================================================;
;=========ESM/ESP/LOD/NIF Tool Launchers===========;
;==================================================;

;--sTes4GeckoPath is the path to look for Tes4Gecko (defaults to Tes4Gecko.jar).
; sTes4GeckoJavaArg is the memory size argument used for launching Tes4Gecko.
sTes4GeckoPath=Tes4Gecko.jar
sTes4GeckoJavaArg=-Xmx1024m

;--sTes4FilesPath is the path that Bash will look for Tes4Files (defaults to Tes4Files.exe).
sTes4FilesPath=Tools\Tes4Files.exe

;--sTes4EditPath is the path that Bash will look for Tes4Edit\View\Trans (defaults to Tes4Edit.exe).
sTes4EditPath=Tes4Edit.exe

;--sTes4LodGenPath is the path that Bash will look for Tes4LodGen
; (defaults to Tes4LodGen.exe).
sTes4LodGenPath=Tes4LodGen.exe

;--sNifskopePath is the path that Bash will look for Nifskope (defaults to
; C:\Program Files\NifTools\NifSkope\nifskope.exe).
sNifskopePath=C:\Program Files\NifTools\NifSkope\nifskope.exe

;==================================================;
;===========3D Modeling Tool Launchers=============;
;==================================================;

;--sArtOfIllusion is the path that Bash will look for Art of Illusion.
sArtOfIllusion=C:\Program Files\ArtOfIllusion\Art of Illusion.exe

;--sAutoCad is the path that Bash will look for AutoCad.
sAutoCad=C:\Program Files\Autodesk Architectural Desktop 3\acad.exe

;--sBlenderPath is the path that Bash will look for Blender (defaults to
; C:\Program Files\Blender Foundation\Blender\Blender.exe).
sBlenderPath=C:\Program Files\Blender Foundation\Blender\Blender.exe

;--sGmaxPath is the path that Bash will look for Gmax (defaults to
; C:\GMAX\gmax.exe).
sGmaxPath=C:\GMAX\gmax.exe

;--sMaxPath is the path that Bash will look for 3dsMax.
sMaxPath=C:\Program Files\Autodesk\3ds Max 2010\3dsmax.exe

;--sMayaPath is the path that Bash will look for Maya.
sMayaPath=C:\not\a\valid\path.exe

;--sMilkShape3D is the path that Bash will look for MilkShape 3D.
sMilkShape3D=C:\Program Files\MilkShape 3D 1.8.4\ms3d.exe

;--sWings3D is the path that Bash will look for Wings3D.
sWings3D=C:\Program Files\wings3d_1.2\Wings3D.exe

;==================================================;
;==========Texturing/DDS Tool Launchers============;
;==================================================;

;--sArtweaver is the path that Bash will look for Artweaver.
sArtweaver=C:\Program Files\Artweaver 1.0\Artweaver.exe

;--sDDSConverter is the path that Bash will look for DDSConverter.
sDDSConverter=C:\Program Files\DDS Converter 2\DDS Converter 2.exe

;--sDogwaffle is the path that Bash will look for Dogwaffle.
sDogwaffle=C:\Program Files\project dogwaffle\dogwaffle.exe

;--sGenetica is the path that Bash will look for Genetica.
sGenetica=C:\Program Files\Spiral Graphics\Genetica 3.5\Genetica.exe

;--sGeneticaViewer is the path that Bash will look for Genetica Viewer.
sGeneticaViewer=C:\Program Files\Spiral Graphics\Genetica Viewer 3\Genetica Viewer 3.exe

;--sGIMP is the path that Bash will look for GIMP.
sGIMP=C:\Program Files\GIMP-2.0\bin\gimp-2.6.exe

;--sGimpShop is the path that Bash will look for Gimp Shop.
sGimpShop=C:\Program Files\GIMPshop\bin\gimp-2.2.exe

;--sInkscape is the path that Bash will look for InkScape.
sInkscape=C:\Program Files\Inkscape\inkscape.exe

;--sPaintNet is the path that Bash will look for Paint.Net.
sPaintNET=C:\Program Files\Paint.NET\PaintDotNet.exe

;--sPhotoshopPath is the path that Bash will look for Photoshop.
sPhotoshopPath=C:\Program Files\Adobe\Adobe Photoshop CS3\Photoshop.exe

;--sPixelStudio is the path that Bash will look for Pixel Studio Pro.
sPixelStudio=C:\Program Files\Pixel\Pixel.exe

;--sTwistedBrush is the path that Bash will look for Twisted Brush.
sTwistedBrush=C:\Program Files\Pixarra\TwistedBrush Open Studio\tbrush_open_studio.exe

;--sPhotoScape is the path that Bash will look for PhotoScape.
sPhotoScape=C:\Program Files\PhotoScape\PhotoScape.exe

;--sPhotobie is the path that Bash will look for Photobie Design Studio.
sPhotobie=C:\Program Files\Photobie\Photobie.exe

;--sPhotoFiltre is the path that Bash will look for PhotoFiltre.
sPhotoFiltre=C:\Program Files\PhotoFiltre\PhotoFiltre.exe

;--sPaintShopPhotoPro is the path that Bash will look for Paint Shop Photo Pro.
sPaintShopPhotoPro=C:\Program Files\Corel\Corel PaintShop Photo Pro\X3\PSPClassic\Corel Paint Shop Pro Photo.exe
;==================================================;
;=========General/Modding Tool Launchers===========;
;==================================================;

;--sBSACMD is the path that Bash will look for BSA Commander.
sBSACMD=C:\Program Files\BSACommander\bsacmd.exe

;--sEggTranslator is the path that Bash will look for Egg Translator.
sEggTranslator=C:\Program Files\Egg Translator\EggTranslator.exe

;--sISOBL is the path that Bash will look for ISOBL.
sISOBL=ISOBL.exe

;--sISRMG is the path that Bash will look for Insanity's ReadMe Generator.
sISRMG=Insanitys ReadMe Generator.exe

;--sISRNG is the path that Bash will look for Random Name Generator.
sISRNG=Random Name Generator.exe

;--sISRNPCG is the path that Bash will look for Insanity's Random NPC Generator.
sISRNPCG=Random NPC.exe

;--sMAP is the path that Bash will look for Interactive Map of Cyrodiil and Shivering Isles.
sMAP=Modding Tools\Interactive Map of Cyrodiil and Shivering Isles 3.52\Mapa v 3.52.exe

;--sOblivionBookCreatorPath is the path that Bash will look for Oblivion Book Creator
sOblivionBookCreatorPath=Data\OblivionBookCreator.jar
sOblivionBookCreatorJavaArg=-Xmx1024m

;--sOBMLG is the path that Bash will look for Oblivion Mod List Generator.
sOBMLG=Modding Tools\Oblivion Mod List Generator\Oblivion Mod List Generator.exe

;--sOBFEL is the path that Bash will look for Oblivion Face Exchange Lite.
sOBFEL=C:\Program Files\Oblivion Face Exchange Lite\OblivionFaceExchangeLite.exe

;--sRADVideo is the path that Bash will look for RAD Video Tools.
sRADVideo=C:\Program Files\RADVideo\radvideo.exe

;==================================================;
;======Screenshot/Benchmarking Tool Launchers======;
;==================================================;

;--sFraps is the path that Bash will look for FRAPS.
sFraps=C:\Fraps\Fraps.exe

;--sIrfanView is the path that Bash will look for Irfan View.
sIrfanView=C:\Program Files\IrfanView\i_view32.exe

;--sXnView is the path that Bash will look for XnView.
sXnView=C:\Program Files\XnView\xnview.exe

;--sFastStone is the path that Bash will look for FastStone Image Viewer.
sFastStone=C:\Program Files\FastStone Image Viewer\FSViewer.exe

;==================================================;
;============Sound/Audio Tool Launchers============;
;==================================================;

;--sABCAmberAudioConverter is the path that Bash will look for ABC Amber Audio Converter.
sABCAmberAudioConverter=C:\Program Files\ABC Amber Audio Converter\abcaudio.exe

;--sAudacity is the path that Bash will look for Audacity.
sAudacity=C:\Program Files\Audacity\Audacity.exe

;--sMediaMonkey is the path that Bash will look for Media Monkey.
sMediaMonkey=C:\Program Files\MediaMonkey\MediaMonkey.exe

;==================================================;
;=========Text/Development Tool Launchers==========;
;==================================================;

;--sNPP is the path that Bash will look for Notepad++.
sNPP=C:\Program Files\Notepad++\notepad++.exe

;--sWinMerge is the path that Bash will look for WinMerge.
sWinMerge=C:\Program Files\WinMerge\WinMergeU.exe

;--sFreeMind is the path that Bash will look for FreeMind.
sFreeMind=C:\Program Files\FreeMind\Freemind.exe

;==================================================;
;========Other/Miscellaneous Tool Launchers========;
;==================================================;

;--sAniFX is the path that Bash will look for AniFX.
sAniFX=C:\Program Files\AniFX 1.0\AniFX.exe

;--sFileZilla is the path that Bash will look for FileZilla.
sFileZilla=C:\Program Files\FileZilla FTP Client\filezilla.exe

;--sIcoFX is the path that Bash will look for IcoFX.
sIcoFX=C:\Program Files\IcoFX 1.6\IcoFX.exe

;--sLogitechKeyboard is the path that Bash will look for Logitech G11 Keyboard Profiler.
sLogitechKeyboard=C:\Program Files\Logitech\GamePanel Software\G-series Software\LGDCore.exe

;--sSteam is the path that Bash will look for Steam.
sSteam=C:\Program Files\Steam\steam.exe

;--sEVGAPrecision is the path that Bash will look for EVGA Precision.
sEVGAPrecision=C:\Program Files\EVGA Precision\EVGAPrecision.exe

;;;==============================================;;;
;;;============CUSTOM Tool Launchers=============;;;
;;;==============================================;;;

;--sCustom# is the path for custom tool launchers
; sCustom#opt is the option switch(es) used for launching that tool.
; sCustom#txt is the tool tip text to show for that launcher.
; Can be an .exe file, Java app, or anything that can be double-clicked
; ...opt works a bit differently depending on what you're launching:
; exe: Acts as a command line option
; Java apps: Like .exe, but note that it applies to the .jar rather than JavaW (as opposed to Tes4Gecko above)
; Others: Acts as Microsoft's "command verbs" as seen in Explorer (i.e., print, edit, find, explore)
; All icons have to be in Mopy\images and named custom#16.png or custom#32.png
; (where # is replaced by a number between 1 and 18)

sCustom1=C:\not\a\valid\path.exe
sCustom1opt=-Option(s)
sCustom1txt=Tooltip Text

sCustom2=C:\not\a\valid\path.exe
sCustom2opt=-Option(s)
sCustom2txt=Tooltip Text

sCustom3=C:\not\a\valid\path.exe
sCustom3opt=-Option(s)
sCustom3txt=Tooltip Text

sCustom4=C:\not\a\valid\path.exe
sCustom4opt=-Option(s)
sCustom4txt=Tooltip Text

sCustom5=C:\not\a\valid\path.exe
sCustom5opt=-Option(s)
sCustom5txt=Tooltip Text

sCustom6=C:\not\a\valid\path.exe
sCustom6opt=-Option(s)
sCustom6txt=Tooltip Text

sCustom7=C:\not\a\valid\path.exe
sCustom7opt=-Option(s)
sCustom7txt=Tooltip Text

sCustom8=C:\not\a\valid\path.exe
sCustom8opt=-Option(s)
sCustom8txt=Tooltip Text

sCustom9=C:\not\a\valid\path.exe
sCustom9opt=-Option(s)
sCustom9txt=Tooltip Text

sCustom10=C:\not\a\valid\path.exe
sCustom10opt=-Option(s)
sCustom10txt=Tooltip Text

sCustom11=C:\not\a\valid\path.exe
sCustom11opt=-Option(s)
sCustom11txt=Tooltip Text

sCustom12=C:\not\a\valid\path.exe
sCustom12opt=-Option(s)
sCustom12txt=Tooltip Text

sCustom13=C:\not\a\valid\path.exe
sCustom13opt=-Option(s)
sCustom13txt=Tooltip Text

sCustom14=C:\not\a\valid\path.exe
sCustom14opt=-Option(s)
sCustom14txt=Tooltip Text

sCustom15=C:\not\a\valid\path.exe
sCustom15opt=-Option(s)
sCustom15txt=Tooltip Text

sCustom16=C:\not\a\valid\path.exe
sCustom16opt=-Option(s)
sCustom16txt=Tooltip Text

sCustom17=C:\not\a\valid\path.exe
sCustom17opt=-Option(s)
sCustom17txt=Tooltip Text

sCustom18=C:\not\a\valid\path.exe
sCustom18opt=-Option(s)
sCustom18txt=Tooltip Text

User avatar
Philip Lyon
 
Posts: 3297
Joined: Tue Aug 14, 2007 6:08 am

Post » Wed Sep 01, 2010 11:42 am

@BootySweat
It is still a strange problem you have in that upon fresh install of WB, it is normally born with a working .ini... :shrug:
So yeah, do like JdeRau said and be sure to have at least WB 287 installed, or better yet 290.
User avatar
jaideep singh
 
Posts: 3357
Joined: Sun Jul 08, 2007 8:45 pm

Post » Wed Sep 01, 2010 11:37 pm

great :)
yes there is - a Python list by the name of badDlls. hmm I definitely should make that to be accessible... also found a slight security hole (BAIN was remembering only the name of the dll/dlx rather than the name and crc and source pkg; so install a valid plugin and forever after that would be remembered) so a bunch more improvements coming shortly.
Pacific Morrowind
Thanks - I saw it in the svn but afraid of nassty sserpents
Still I do believe that oblivion\data\OBSE\plugins\plugin.dll should be installable (a lot come in this format) - or even also more dlls that come loosely packed as\plugin.dll
Have a look at my previous post on format and my suggestion on Is OBSE plugin menu item - for installing documentation and/or extra files(though this may wait ofc).
Also still no joy 7z with command line - have a look in my prev posts for suggestions

Thanks :)

EDIT : svn 762 - will check latest late today
User avatar
Benji
 
Posts: 3447
Joined: Tue May 15, 2007 11:58 pm

Post » Wed Sep 01, 2010 10:46 pm

Just pushed a change that should help with some of the issues with merge mods not being patched properly when CBash is enabled. Cells are also more likely to be patched properly...was using some test code that was never finished.

Haven't gotten to any of the 7z argument issues yet.
User avatar
maria Dwyer
 
Posts: 3422
Joined: Sat Jan 27, 2007 11:24 am

Post » Wed Sep 01, 2010 12:45 pm

Sorry to bother.
I don't know if it is a known issue, but when I tried to rebuild the bashed patch, the program crashed saying "pythonwx has stopped working".
After that bash could not open anymore.
I tried to generate a bugdump, as stated in the readme, with the command prompt, but it said "already open" (or something like that), but it was not true.... I tried to check the task manager, but there was no python process or something recalling Wrye Bash.
I tried first installing wxpython, with no result, then I tried to reinstall bash. The bugdump was always saying that the program was already open (or something like that, I repeat).
I tried again a couple of times after restarting Windows, but no result.
At the last restart of Windows, clicking the shortcut of Wrye Bash has no result, clicking the launcher has no result, but the command prompt I use to generate the bugdump starts the program and makes it work properly.
it is a really strange thing and I don't know how to solve this.
Anyone which could help me?

EDIT: now the launcher works, but I can't say how I did it. What can I do if the problem presents itself again?
User avatar
Cartoon
 
Posts: 3350
Joined: Mon Jun 25, 2007 4:31 pm

Post » Wed Sep 01, 2010 10:14 pm

Don't know anything about wxPython crashing. It certainly isn't supposed to happen, but it is probably a bug in wxPython itself and beyond our control.

If Bash ever refuses to start, try deleting pidfile.tmp from the Mopy directory. Bash uses that file to determine if it is already running so that it can prevent you from starting multiple instances of Bash. If Bash crashes, it isn't able to properly clear the file...so it thinks that it is still running.
User avatar
Kelly Upshall
 
Posts: 3475
Joined: Sat Oct 28, 2006 6:26 pm

Post » Wed Sep 01, 2010 9:32 pm

So that was the problem. Next time I'll delete pidfile.tmp... I noticed that it was in the directory when I tried the launcher without making it work. Now it should work anyway.
Thank you :)
User avatar
Yonah
 
Posts: 3462
Joined: Thu Aug 02, 2007 4:42 am

Post » Wed Sep 01, 2010 10:37 pm

Where can we get these SVN builds? I'd like to wring out the new code too.
User avatar
Veronica Martinez
 
Posts: 3498
Joined: Tue Jun 20, 2006 9:43 am

Post » Wed Sep 01, 2010 12:29 pm

Where can we get these SVN builds? I'd like to wring out the new code too.


http://oblivionworks.svn.sourceforge.net/viewvc/oblivionworks/Programs/Wrye%20Bash/
User avatar
Mel E
 
Posts: 3354
Joined: Mon Apr 09, 2007 11:23 pm

PreviousNext

Return to IV - Oblivion