Is it possible to install a mod from a folder instead of an archive?

Yes using the package manager so I can use the fomm format.

I've been trying to find out why the FOOK fomod won't install properly. It turns out the FOOK files contain some Thumbs.db files and Vista is denying access to replace the .db files already present in the Program Files folders. I've tried to unzip the FOOK files using WinZip and the "Run as Administrator" command for .zip files (Look it up on the net) and that works fine. The problem is that the package manager needs to run as administrator or get special privileges to overwrite files in the Program Files folders. I know that the FOMM can be "Run as Administrator" but this doesn't seem to work. I'm no programmer or coder but is it possible to make the package manager a seperate application or .exe that can be run as administrator?

I've been trying to find out why the FOOK fomod won't install properly. It turns out the FOOK files contain some Thumbs.db files and Vista is denying access to replace the .db files already present in the Program Files folders. I've tried to unzip the FOOK files using WinZip and the "Run as Administrator" command for .zip files (Look it up on the net) and that works fine. The problem is that the package manager needs to run as administrator or get special privileges to overwrite files in the Program Files folders. I know that the FOMM can be "Run as Administrator" but this doesn't seem to work. I'm no programmer or coder but is it possible to make the package manager a seperate application or .exe that can be run as administrator?

The package manager is fomm. If you've set fomm to run as admin, then there's nothing else you can do.

Post the exact error message you get; if it's an unhandled exception, I need the exception message and stack trace. Also what version of fomm are you using? Any recent version will ignore any thumbs.db files it comes across while creating fomods.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: Illegal characters in path.
at System.Security.Permissions.FileIOPermission.HasIllegalCharacters(String[] str)
at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, AccessControlActions control, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
at System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
at System.IO.Path.GetFullPath(String path)
at Fomm.PackageManager.ScriptFunctions.InstallFileFromFomod(String file)
at Fomm.PackageManager.ScriptFunctions.BasicInstallScript()
at Fomm.PackageManager.fomod.Activate()
at Fomm.PackageManager.PackageManager.bActivate_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3074 (QFE.050727-3000)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Fomm
Assembly Version: 0.9.10.0
Win32 Version: 0.9.10.0
CodeBase: file:///C:/Program%20Files%20(x86)/Bethesda%20Softworks/Fallout%203/fomm/fomm.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3074 (QFE.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:





When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Im using 0.9.10 and the error is:

So now that I've released 2 mods with BSA replacments and soon to be a third with UF3P I've run into some strange issues with the BSA's... with my "Hi-Res Weapons & Ammo Textures.bsa" (contains nifs and 1 texture) loading before "Unofficial Fallout 3 Patch.bsa" (contains nifs and textures) it caused any replaced mesh in the BSA that was used as a "container" not to be replaced and just use the default mesh and now with G4WLD.bsa (Games for Windows Live Disabler, contains 1 xml) loading before "Unofficial Fallout 3 Patch.bsa" stopped any of UF3P's replaced meshes from loading at all...

Anyhow after messing around with the BSA flags in BSA Commander I think i found the "universal flag" which is xml+ctl (104), I recreated all my bsa's with that flag and now they work perfectly fine including any meshes\textures that are unique ect (I haven't tested all file types). So it maybe nice if FOMM had this "universal flag" as an option in the BSA Creator.

Edit: seems the G.E.C.K handles BSA's a little different... it couldn't load textures from those BSA's with 104, so I threw all the flags on (1FF) and everything is working.

Quarn...is there any "secret" to BSA's? compression, ect? I was hoping to use the BSA format for one of my mods but I'm in the dark as how to go about using it. How does the game/geck/what-not decide which BSA loads when?

thanks,
TheDamned

IMO never use any compression, you'll get better compression results (7z\rar) later on when you package up your mod for release.

With Fallout 3 v1.1+ it will automatically load any BSA that has the same name as an active plugin eg. "My Plugin.esp" will load "My Plugin.bsa" "My Plugin - Textures.bsa" ect. If you're looking to replace existing content (excluding textures) with a BSA you'll need to add its name to the start of SArchiveList, before Fallout - Meshes.bsa ect.

Awesome, thanks!

Just so I'm clear on this.
If I have a mod that adds a new gun to the game named TheDamned.ESP it will load TheDamned.BSA?

On the other hand...what if I release a texture replacer...I have to tell people to edit their fallout.ini?

TheDamned

Correct.


My tests showed that using BSA to replace textures from other BSA didn't work reliably... BUT now I've put all the flags on the BSA the texture replacements "seem" to be working, I need to do some more testing, I'll get back to you.

Thanks again Quarn, I really appreciate your help and patience ^_^

TheDamned

Ah well it is one of my goals to try and get people to use BSA's more... anyhow after testing texture replacements from BSA's they do seem relyable after all just not when trying to replace bodymod\facemod textures (I'm guessing anything within the fallout3.esm directory, which includes voices too).

Edit: Ah did more testing... seems like some textures can be replaced with ones in BSA's but others can't... best not to use BSA's for texture replacements.

Ah that sounds disappointing they could have had a lot of promise there. I guess we just have to do texture replacer's the old fashioned way?

Still, they should have a lot of use for anything that adds new textures/meshes/sounds/ect right?

TheDamned

Yes all new unique named\pathed files will work perfectly fine. Oh another thing to remember too if all your mod's files are in a BSA you won't have to worry about setting bInvalidateOlderFiles to 1.

Aww...but that would mean that we can't use the awesome ArchiveInvalidation Invalidated!

Do you see any disadvantages to using a BSA style mod?...I personally can't but, you never know :shrug:

TheDamned

EDIT: aww damn...sorry Timeslip if I(we) kinda hi-jacked the thread here. I grovel at your feet for forgiveness :bowdown: