RoyBatterian

I realize it's simple logic and math, I just failed to see what memory allocation had to with it when it returns a pointer (void). However the stackflow article explains the pitfall when comparing two pointers more than 2GB away from each other. Still it's coder error if an application fails, but that's neither here nor there as you said. I'll test New Vegas with the top down memory allocation then and if it causes issues I'll take it under advisement and rethink/investigate what needs to be done.

I'm not surprised VISTA had issues with anything, I skipped that OS because it was hunk of garbage from day one.

Anyways, I also don't mean to hijack your thread, so I'll "get lost".

Apologies if I offended you, it wasn't my intent. I did get your point, "also the value returned by malloc is inherhently an unsigned integer" this is clearly stated in any description of the API I have seen. If some programmer is dumb enough to put it in an int, that's neither my fault nor yours. Please remain calm.

Prideslayer: While it's true that you cannot allocate a SINGLE buffer with a size greater than 2GB with a standard malloc (you can by other means of course, CreateFileMapping for ex), that in no way affects the amount of ram that can be addressed. This is entirely handled by the kernel's memory manager which can in fact address a great deal of RAM indeed. Additionally calling malloc with with a negative value will return NULL, also the value returned by malloc is inherently an unsigned integer, but of course you know this. Any coder treating it as a signed integer fails to understand the API (and architecture in general) and has no business programming.

I'm not sure where you get such FUD, but it should be disregarded as completely untrue. There are plenty of examples (msdn, gcc documents), papers and blog posts on this very subject which are but a google search away.

Additionally I certainly don't need a lesson in binary or hexidecimal, I've been programming on various platforms for > 20 years so let us not be condescending to each other.

Now, let me thank you for the updates and improvements to FOMM, it's great that someone has picked up the torch and continues developing it. I look forward to future improvements.

Yes I am a programmer or rather was, I am a bit rusty still as have not done it seriosly for years. Not sure what signed or unsigned integer has to do with Windows XP's (and below) horrible memory manager contraints since physical address extension has been present in x86 processors since the first pentium. Anyways that's a discussion for another forum, hehe. I was hoping you had some technical paper you could point me to.

Ah well I never liked BOSS or LOOT, as long as I'm not forced to use it that's cool with me.

As for FNV4GB I've tried to fix that hang bug already since MonochromeWench did not setup a WinMain properly but it seems to hang waiting for the terminate message from the debugged process. In fact it should detach and terminate immediately after creating the child process. It probably hangs because it's still hooking GetTickCount which I think interferes with Steam and NVSE. Enabling Fast Exit in NVSR gets around the problem for some reason... I don't have the source for that so I couldn't say why. I just need to rewrite it rather than try to patch it any further. It's a pasted together mess from various sources anyways.

I would be interested to see any articles or instances of the LAA flag being unsafe.

That's excellent news on updating the load order system. We won't be forced to use LOOT I assume? The tool is primarily designed for Skyrim and is not entirely friendly with the Fallout games or mods for them.

I plan to completely re-write FNV4GB sometime this year to give it a more friendly interface for the options, and to make it automatically know which SteamAppId to use based on hashing the executable. I will also remove the Skyrim part of it as it's no longer needed, and perhaps make it into a library that can be included in other tools like FOMM and MO.

Prideslayer: It's an issue with the 7zip library (ran into the same issue with the TTW installer), patching FOMM to enable 4GB address space fixes the issue with installing large mods like TTW. Scorpion fixed the 7zip lib for use with the TTW installer. It's easy enough to enable the flag in the compiler options, and I don't really see a reason not to as it doesn't affect 32 bit operating systems.

NMM has the same bug, and it's with any very large mod not just TTW.

Feature request, can you add time stamp sorting method for load order rather than the plugin list method, so it's more compatible with wrye and for those who have migrated from NMM.

Does anyone have a link for non moddb one that doesn't use 4shared? I don't really want a bunch of ad spam showing up in my mailbox.

:edit:

Nevermind, the mediafire links work again.