Fallout Mod Manager error, tried contacting Timeslip

[Cronyx]

I've got a fresh install of FOMM here. I tried PMing Timeslip but it said I couldn't PM him for some reason. If anyone knows how to get ahold of him, or knows how I should proceed with addressing this problem, I'd really appreciate it. I've spent more time this weekend trying to play Fallout than actually playing Fallout. :P

 

Error is in the quote, as well as the post I was trying to originally send to him.

 

 

Hey man :smile:

I just downloaded FOMM and after installing it, I'm getting this crash dump.

Saturday, March 09, 2013 - 5:11:15 PM

Fomm 0.13.21

OS version: Microsoft Windows NT 6.1.7601 Service Pack 1

System.NullReferenceException: Object reference not set to an instance of an object.

at Fomm.PackageManager.ModInstallLog.InstallLog.InitMods()

at Fomm.PackageManager.ModInstallLog.InstallLog.Load()

at Fomm.PackageManager.ModInstallLog.InstallLog..ctor()

at Fomm.Program.Main(String[] args)

Any assistance you could provide would be appreciated :smile:

Edited March 10, 2013 by Cronyx

[M48A5]

You need to navigate to the installed location of the file "GeMM" and open the file. Look for FOMM.exe and right click on it. In the drop-down menu, left click "Properties". Left click the "Compatibility" tab. Look for "Run this program as an administrator", left click the box and exit out. It appears that you have installed Fallout 3 in the "Program FIles". Your best solution would be to uninstall Fallout 3 and reinstall it at a location on your hard drive other than "Program FIles".

[Cronyx]

Fallout's actually installed in "G:\Arcade\Steam\SteamApps\common\Fallout 3 goty" and I have UAC and Action Center turned off, along with having full Administrator's Group ownership of C:\Windows, C:\Program Files, and C:\Programdata.

 

Running as administrator in this instance, as expected, produces no different outcome. :/

 

Do you have any other ideas?

 

Thanks for replying, btw :)

Edited March 10, 2013 by Cronyx

[M48A5]

From the FOMM ReadMe: "If you have multiple installations, or you are running a downloaded version of fallout from D2D or steam, you will need to either install fomm into the same directory as the fallout3.exe of the game you want to run it with, or manually edit the settings.xml file to add the node '<strValue name="FalloutDir">add the full path to your fallout directory here</strValue>'."

 

"If fomm crashes on startup with a generic windows error then you likely have a problem with your .NET installation; fomm requires .NET 2.0 to run. Among the other third party gunk that the fallout 3 installer installs alongside the actual game is the original prepatched version of .NET 3.0, which under some circumstances can cause .NET 2 applications to break. In this case visiting windows update and installing the .NET 3 patch it offers you is sufficient to get fomm working."