hi. researched from MS 64*. have page file pools set, and 10.5gb ready after 0S, and med. cache. so, everything is ready, do i need to change .32dll binary values for valve, bethesda.fonv(regedit)? . im just going to keep increasing .dll binary values for every thread....this is the same problem w/ the 3gb/4gb enabalers i believe. i have 12gb physical, have little commit for OS, want ALL for .exe 's of course. the 6 i am aiming for have DMR? are on GFWL, and STEAM. others have done what they called 3gb enablers for 32*systems, thus began my search. ex:FalloutNV.exe after commit adjusted STILL uses 780,000kbs,
out of let me see 1072152mb+....thats a huge problem for me.i should be loading the whole game up in virtual...and having a blast...
instead, with full res these games today, thats about 15' in front of me.=STUTTER...doesn't have to B! i am woking in regedit, with no refrences, and no one but
to answer, i've had this question for almost 10 days now.on multiple forums, just the Fallout nexus forum has almost 2.5million. what i need to know. prefetch/superfetch? can i assign a value, or is the value 0, or 1. can i just use this with say 8gb ram?
or do i need to go into Winreg--Allowed Paths--find steam?,. for falloutNV.exe, while fully active, and system w/ normal loaded programs running. tot,12279.cache 2309.avail 9335. free 7271 / paged 217 nopg 111 / pfr 22978 handles. 859 threads.54 proc.commit gb 3gb/569 . now falloutNV.exe .this is horrible:steam: commit 895,452 active 877,268 (puny little kibbles) share 30,020 reserved 847,248 (how can increase) cpu is at 0% and physical Mem is @ 23% . this at normal priority. when it says 92% i will be extatic....really
so, which thread is it? cuz minesisgettinFRAYED
c.s.

Perhaps Im misunderstanding what you want, but there is no way to do what your asking. You CANT load the whole game up in memory. I very much doubt your
going to get any kind of response other than what Im posting. Fallout new vegas will only use ~1.4GB or so (vanilla version). You should read about how virtual memory and paging works in windows because I think your misunderstanding. Your attributing stuttering to the fact that more of new vegas isnt loaded into memory and that isnt correct in my opinion. 12 GB is way overkill in gaming systems today.

hello. sorry to confuse you, I did not mean the whole game literally, as i have 8gb just in mods. you will get this if you read the book 1st. but, NO 12gb is not a waste on a system with w7 64* as i iterated for a forum i use. with quotes from MS System Internals. READ it, it is good.

". Virtual memory separates a program’s view of memory from the system’s physical memory,
so an operating system decides when and if to store the program’s code and data in physical
memory and when to store it in a file. The major advantage of virtual memory is that it
allows more processes to execute concurrently than might otherwise fit in physical memory.
While virtual memory has limits that are related to physical memory limits, virtual memory
has limits that derive from different sources and that are different depending on the consumer.
For example, there are virtual memory limits that apply to individual processes that run
applications, the operating system, and for the system as a whole. It's important to remember
as you read this that virtual memory, as the name implies, has no direct connection with
physical memory.
Windows assigning the file cache a certain amount of virtual memory does not dictate how much
file data it actually caches in physical memory; it can be any amount from none to more than
the amount that's addressable via virtual memory."(m.r.techblog wnds trblshoot)
he is saying all elements of a computer are given some virtual memmory, or process address space
which is used after the commited memmory, which is the amount specific for that application.this space
is writeable, and can be reused by the cpu. "Because the address space on 64-bit Windows is much larger
than 4GB, something I’ll describe shortly, Windows can give 32-bit processes the maximum 4GB
that they can address and use the rest for the operating system’s virtual memory.64-bit
processes use 64-bit pointers, so their theoretical maximum address space is 16 exabytes (2^64).
However, Windows doesn’t divide the address space evenly between the active process and the system,
but instead defines a region in the address space for the process and others for various system memory
resources,the file cache, and paged and non-paged pools. final limits related to virtual memory are
the maximum size and number of paging files supported by Windows. 32-bit Windows has a maximum paging file
size of 16TB (4GB if you for some reason run in non-PAE mode) and 64-bit Windows can having paging files
that are up to 16TB in size on x64 and 32TB on IA64. For all versions, Windows supports up to 16 paging files,
where each must be on a separate volume. "(m.r.techblog wnds trblshoot)
he says in order to get the most out of the physical memmory installed on system with 64* you have
to use registry values to change(lower) the cache, and to raise the page, and non-paged pools.
commit charge value is commit charge+woking. page file you get minimum by running your computer w/ most or all of
the processes you would use, giving you a kind of total system commit charge. max page safe is double that amount.
some people run NO page file, leaving windows no writable cache... some like, but leaves no crash dump etc.
.

peace

ref:

m russinovich..sysinternals L.R.

there are only client .exe's with a bunch 0f .32Dll's not gaining full access to my commit charge. of YES this is no typo. control panel: bottom right, commit (GB) is 1/ 569GB , and w/ game is 2GB/569GB. at this point, it is only a digital rights barrier question, look on nexus, 2, other people are doing this, and it's getting squashed by steam, look up 3GB enabler, there is a 4GB enabler....w/ talk of 6gb, and 8gb enablers...so, again NO, 12gb is no waste " Windows can give 32-bit processes the maximum 4GB
that they can address and use the rest for the operating system’s virtual memory.64-bit processes use 64-bit pointers, so their theoretical maximum address space is 16 exabytes (2^64).
OUR game runs at less than 1gb people, that is an outrage...DMR(which is not DRM) stuff, i have this narrowed down to a few threads. ou all are talking physical...i'm speaking about virtual, and the values of the commit charge, IE: FalloutNV.exe LOOK at the resource monitor,,,,look in Memmory tab, look at commit value,woking value, share value. registry values can be inreaseed or decreased in many ways. read the book. thanks

Windows can give a 32-bit process the maximum 4GB yes if you use the large_address_aware flag. That however simpluy increases the size of the virtual m,emory space the process uses. Im talking from a programmers perspective. Even if the flag is set that doesnt mean the program will use 4 GB of physical RAM. The program will use the number of pages it needs in its current working set which is what the commit charge means. Its the number of committed pages that is pages that have a frame in physical RAM. Fallout 3 new vegas is a 32-bit program withe large address aware flag cleared (vanilla). That means 2GB address space.

12 GB depends on what you do on your computer. So maybe it isnt a waste. For a single game like falllout 3 new vegas you wont use most of it.

hi jasper/people, did some research on 32* prior to finding my 411 on 64*. yes, nice and easy 2/2, or 3/1. w/ large address flags on 32* sys. 64* sys is different, aside from it's reacting w/ 32* software.(.32Dll's) i can through the registry, or a .cpl adjust values obviously, you can't think of 64* in the same way as a 32*, a registry value for me, can be changed through yes page file, and cache, but...super and prefetch, kernal adjusters and pointers....32Dll Kernal can be changed...everything, how do you think it operates, it is told its parameters, those can be adjusted, gameoverlay.32Dll ...really, the world isn't on 64* is the cut and dry problem. i'll have to watch some data trails, but if you are trying to tell me, that even though it is written for both, i am limited to what, hardlined software, giving it a whopping 780,000 working kibbles...then, those programmers must perish, and both Fallouts...i'll stick in my potplantspots to reflect more sunlight. actually waiting to hear back from bethesda, they might not like the ?, but it is doable... gskill said, it was too indepth...but NEVER disagreed with me ,so think i'll stick with the MS book, and [censored] about steam, and pull apart one of those 4gb enabler modds for 64*systems i was talking about. like i said..they ran into steam...as i am. it's a computer, everything can be modded. it doesn't stutter really, that was all cut/paste from somewhere else. look, i will be extremely po'd if i am limited to the amount of memmory it is using at this point. that would be totally ridiculos. and, not a wise investment for any one. we may as well be playing xbox vanillerific with 25fps with an 8-track kicking the begees.....j, if you have a 64*, take a look at just this 1 page.
Windows assigning the file cache a certain amount of virtual memory does not dictate how much file data it actually caches in physical memory; it can be any amount from none to more than the amount that's addressable via virtual memory.

Process Address Spaces
Each process has its own virtual memory, called an address space, into which it maps the code that it executes and the data that the code references and manipulates. A 32-bit process uses 32-bit virtual memory address pointers, which creates an absolute upper limit of 4GB (2^32) for the amount of virtual memory that a 32-bit process can address.** However, so that the operating system can reference its own code and data and the code and data of the currently-executing process without changing address spaces, the operating system makes its virtual memory visible in the address space of every process. By default, 32-bit versions of Windows split the process address space evenly between the system and the active process, creating a limit of 2GB for each:



Applications might use Heap APIs, the .NET garbage collector, or the C runtime malloc library to allocate virtual memory,
blahblablah k here this is good64-bit processes use 64-bit pointers, so their theoretical maximum address space is 16 exabytes (2^64). However, Windows doesn’t divide the address space evenly between the active process and the system, but instead defines a region in the address space for the process and others for various system memory resources, like system page table entries (PTEs), the file cache, and paged and non-paged pools.

The size of the process address space is different on IA64 and x64 versions of Windows where the sizes were chosen by balancing what applications need against the memory costs of the overhead (page table pages and translation lookaside buffer - TLB - entries) needed to support the address space. On x64, that’s 8192GB (8TB) and on IA64 it’s 7168GB

you, jasper...this is good stuff huh, he wrote windows, people below him teach this

Yes alot of good informatuion. And I still dont know what your question is LOL.

i really gotta stop now. the values are strings of 70 plus, with variables(letters) and no refrences. just need it narrowed down,

thanks

for Jasper, and fellow Fallout people, its here!
hello. good guys win.The 2 day old. Fallout's .exe "the Configator". Allows me to use up to 10gb of physical RAM. he has multiple
adjustments all to reduce game stutter. it has a great user interface.it also has tons, tons of graphic settings, audio, and many
other performance features. i was right. they beat me to it. it is done through cells, you can even adjust the HAVOC threads...nice
there is even a Fallout 3 version.....huh....everybody WINS, and i am vindicated. Jasper was
the only person who was smart enough to just read the 1 page.lots of forum jockeys telling me "that can't be DONE" even G-SkILL,
anyways, glad we can ALL benefit, many settings...all systems, give them kudos on nexus,
peace
it's only at 2k downloads
http://www.newvegasnexus.com/downloads/file.php?id=40442

Looks interesting. Can you post screenies of your memory when you use it. Lol youll have to prove that one to me to believe it.
This allows you to use more physical ram because your fiddling with .ini files which allows you to tweak things like data buffers and
number of threads the game uses etc. It does alot and looks like a cool program. Im gonna check if they have something like it
for oblivion since im looking to do the same thing. they probably dont though.

hi. yes i know, i am the same way. that is why i was definetly quoting people with this info. will of course get some srnshts up, shortly. I have to unadjust some reg settings, but w/ it i was already getting the memmory to shoot up further than ever, using 4gb for the .exe. the game NEVER looked cleaner... seriously, more settings than falloutlauncher has. like i said , it was 5am, had to crash, this, THIS, is big for FO. mssg him about skyrim bro.... im sure it would be an easy rewrite at this point. has backup, save settings...really well done work. :disguise: lol, so i uninsstalled to adjust something, and my memmory is still being accessed, got crashdmp...just not familiar w/. it is listing all failures, right, think its a hiccup w/ a setting i changed. real quick ?, .ini is that considered a system executable, should i allow my os some more memmory? or can i just put system large address = 0000000001
thanks
c.s.

.ini should just be a configuration file. YOu can open them in most text editors. System large address? You can edit the fallout.exe to set the large address flag.
I use cff explorer to do that stuff. Dunnno about the crash.

ok, bear w/ me. i can adjust values in an .ini file w/ an app cff explorer ? ill get it. thanks. ok, i had changed all registry default values in (hmm)valve--steam--apps, --6 with enabled cache loading. pool sizes, and a few others. put all back to 0000 . now, have all mods except (detailednormalsTallergrass) the configator has a grass module too. now everything is working fine, except, i am getting a nonfailure "memmory acces violation", i think i am fixing things under a boulean string address error. the large addreess didn't work. with it , theconfigator out, the game crashes at >5gb. so, it is something stupid somewhere. i might just reinstall W7...isn't long, just 300 movies to move sux

ill keep you posted, but the stuff works, something i did probably.

c.s.

hello jasper/people.
everything is working..kinda. got pics. i have is a boulean value problem when physical gets up above 4.5-5gb. it happens when it is trying to load outside...all of it lol. the configator is on, woking..EXCEPT the piece that sets limits on the buffer size. once it trips it's "memmory access violation" that adjuster is removed. i reinstall, got tired. just going to play w/ anything that might be a cap. turn page on and off. dep is set to allow, and it's two files are in share...we'll seee what the author says. will get back. any help would be great. request for crshdmps etc ready. thanks

c.s.