How to get windows and other programs to use more virtual memory

hey, i recently turned up my page file size for more virtual memory, and now my computer takes about 10 seconds to fully boot from the login screen where it used to take over a minute, what i'm wondering is, is there any way to get windows and other programs to use more virtual memory? the reason i'm getting such fast startup times is because windows and my startup programs and stuff are using 250mb out of my 350mb of physical memory, and after a while of using my computer, it used up more and more physical, until i have around 320mb physical used and only like 15mb of virtual, i want my pc to run more off of the virtual memory and less off of physical, i have 1.7gb of virtual memory total, so i want to use more of it, is there any way or any program that will make my computer run more on virtual memory?

 

thanks for the help

i have one more question, i'm currently debugging a program for somebody, and i found a resource problem with memory access, the program gives a memory allocation error, i ran it through a debug process, and it seems the error is coming from accessing ntdll.dll, many people have had no problems with this program, and i am one of the people who are having the problem, and being the only one who knows anything about programming, i was asked to help debug it, none of the people who made it have the problem, so they can't really fix it if they don't know what's wrong, the debug process said that the program is trying to read or write to a virtual address it does not have the appropriate access to and that address is located in ntdll.dll, does anybody know what might be happening here, or what ntdll deals with, it's something to do with memory. the program not being able to access an address in that dll is stopping the program from working for about 50% of the people using it, and i'm in a little over my head

any help at all with this would be greatly appreciated

 

The exact, complete errors would help quite a bit.

 

the debug program says: "the thread tried to read from or write to a virtual address which it does not have the appropriate access. At EIP 77CDE7F9 "

it says that the address 77CDE7F9 is in module ntdll.dll

 

ntdll.dll is innocent!

The debugger is telling you that the fault is in the addressing by the program you're debugging, not in ntdll.dll. There is probably a loop in the program you're debugging that has an incorrect counter.

 

the error the program gives when trying to run it is "Failed to Allocate Memory" and some people never have this problem, and there have been reports of people closing running processes or adjusting virtual memory to get it to work, if the fault is in the program, how come some people remain completely uneffected?


thanx for the help

 

Hello Fuzzy,

Perhaps you should look at what's starting up at boot - compare your applications and Windows services on these sites:

http://www.answersthatwork.com/Tasklist_pages/tasklist.htm For startup programs

http://www.liutilities.com/products/wintaskspro/processlibrary/system/ Windows System Startups

http://www.windowsstartup.com/wso/search.php Searchable DB by Windows Startup Manager people

http://www.blkviper.com/WinXP/servicecfg.htm For XP services

Regards - Charles

 

any more errors?

Now that's a second (or third?) error. Are there any more? It's certainly an unusual situation for a commercial program. If it's been written in-house, the programmer who wrote the code should be debugging it. In fact, that should be a part of writing programs. I feel that too much is being expected of you to debug code you haven't written yourself, unless this is an educational project.

The suggestions for increasing virtual memory will not correct incorrect programming; that memory can be addressed incorrectly too.

Sounds to me like they ARE effected.

 

there is only one error, the first error message i posted was what the debug program said, and the second one is what to program itself says when you run it, and the people that said closing running processes and stuff helped were people who were also having problems but then it started working for them, some people who use the program run it with no problems at all. like the guy who originally programmed it.

and thanks for those links Charles, very good info to have

 

Only because the original programmer should be doing this if he's available.

All you should have to do is show the original programmer the debug message re addressing and he should know what the problem is.