Jump to content
  • 0
Jamoid

Launching the 4GB enabler through MO 1.2.1

Question

Hi!

 

I'm unable to launch FNV4GB 1.9 (or 1.6) through Mod Organizer 1.2.1 on Windows 8.1. It does however work perfectly using version 1.1.1. Just thought I better report that incase nobody else has!

 

The error I get is:

 

"Failed to write to memory of child process

Access is Denied."

 

Is this the right place to report MO bugs? Should I post on the Skyrim Nexus page instead?

 

EDIT: UAC is completely off, I made sure I had admin privileges to the 4GB enabler both inside and outside MO and I also made sure the contents of my NV folder were not read-only.

Edited by Jamoid

Share this post


Link to post
Share on other sites

14 answers to this question

Recommended Posts

  • 0

This needs to be brought to tannnin's attention. He has an issue trailer for MO that you can report issues and also bring it to his attention on the nexus thread I guess.

Share this post


Link to post
Share on other sites
  • 0

Ok I'll do that.

 

Oh and thanks for your Fear and Loathing guide. : )

Share this post


Link to post
Share on other sites
  • 0

Please add the following to the arguments line of the 4GB shortcut in MO: -laaexe .FalloutMO.exe

 

Be aware there is no way for me to tell if this is actually working and MO is loading the modified executable. It does however get rid of the error and the game launches with NVSE for me.

 

Please consider this a hack until Tannin can corroborate this information.

Share this post


Link to post
Share on other sites
  • 0

Awesome, thank you. Means I won't have to avoid the heavy hitting texture mods on this playthrough.

Share this post


Link to post
Share on other sites
  • 0

From the testing I did, it looks like the current version of MO has a problem seeing the 4Gb "exes" folder and / or the modified executable inside. In theory changing the 4GB output to the root game folder will only work if the executable is renamed to something else, you can't have two files with the same name, and let MO see the new modified executable.

 

Hopefully Tannin will see this and provide more input.

Share this post


Link to post
Share on other sites
  • 0

I'm having this same problem with MO 1.2.5. I wasn't having this problem with MO 1.1.1, although I also had fewer plugins being loaded. I added the arguments from above and I was able to get it to load Fallout NV.

Share this post


Link to post
Share on other sites
  • 0

I'm having this same problem with MO 1.2.5. I wasn't having this problem with MO 1.1.1, although I also had fewer plugins being loaded. I added the arguments from above and I was able to get it to load Fallout NV.

Since the betas started we've had to add the argument.

Share this post


Link to post
Share on other sites
  • 0

Please add the following to the arguments line of the 4GB shortcut in MO: -laaexe .FalloutMO.exe

 

Be aware there is no way for me to tell if this is actually working and MO is loading the modified executable. It does however get rid of the error and the game launches with NVSE for me.

 

Please consider this a hack until Tannin can corroborate this information.

I am suffering from the same issue. This has partially solved for me - the game launches now, but it immediately CTD's after the first of the initial loading screens. Do you know if Tannin has this on his to do list by chance? Thanks.

Share this post


Link to post
Share on other sites
  • 0

This is happening to me as well? I thought I had this fixed, but now it is back and nothing seems to get it to work. I've tried all the arguments, etc. One fix that worked for me was to install enb and put d3d9.dll's in both folders, the install folder and the exe's folder that 4gb creates. Don't know why this worked but it did. However nothing is working at the moment. 

Share this post


Link to post
Share on other sites
  • 0

This is happening to me as well...I know for absolute certainty it's becuase I switched to Windows 8.1....running as adminstrator...ran shortcut exe as adminstrator, tried running it in compatibility mode for 7 and 8.....and of course tried the added argument suggestion posted in a few places. I either get something about a child process error or nothing at all depending on which 4gb patch I'm using, it's location, and whether or not I am running as adminstrator (despite being an administrator account *rolls eyes*) The patch works fine outside of MO though...along with loading NV in any other way. I also can use NVSE through MO...but I quickly run into out of memory errors without the increased memory.

Share this post


Link to post
Share on other sites
  • 0

Hi, post 8 in Mod organizer not installing any mods, tool button not working may be of some interest to you. It adds the fallout game path to the windows environment variable to help in running 4gb from MO. Just a warning, you are modifying the Windows environment variable, so make a restore point before doing this. If you are not comfortable doing this find a someone that is and have them do it.

 

In any case please report back if it helps.

Share this post


Link to post
Share on other sites
  • 0

Windows 10 users might want to know that adding the "-laaexe FalloutMO.exe" argument was all it took to get the game to launch through FNV4GB for me. It even uses FalloutMO.exe and loads NVSE!

Share this post


Link to post
Share on other sites
  • 0

Ide hate to revive an old post but with the offical release of windows 10 ide like to verify that the post stating above adding "-laaexe FalloutMO.exe" argument still does work with windows 10 :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.