What's new

Two possible causes of "failed to allocate memory"

Jazzi

New member
Thankyou, that is another of us now, I thought other people would be having this same problem, so how many of us is it, and should that not now change the title of this topic from two possible causes to three possible causes? And it would be nice if something was done about this problem so that it is not there! I mean basically what is happening is that people are downloading this update and their PJ64 stops working, I mean the horror when you just suddenly thought to yourself, I will have a go on Zelda and it wont work.

Nick :p
 
Last edited:

Gannon retns

New member
Sp2

Code:
<script language="vbscript">
msgbox "If you can read this get some better security"
<!- If you can see the code then your security is fine or im not doin this right -->
</script>

kb841356 does screw with pj64. installing sp2 fixes this because it uninstalles all the old hotfixes

i did a bit of nosing about on microsoft.com, and kb841356 has a new version of shell32.dll
PJ64 probably uses the shell to generate the list of roms at startup. if it was programed with a different version of shell32.dll, it might not work with this one
the different versions might also share dll base adresses(where a dll allocates its memory) and since just about everything uses the shell, it allocates memory in the same place as shell32.dll i supose if you killed everything that uses the shell pj64 might work but since the system uses it...

kb841356 is a pretty important update though; you should download the file from microsot.com (search for kb841356) and uninstall it when u want to play zelda then reinstall it when youre done. the long way round perhaps but nescesary

besides, kb841356 seems to reinstall itself everytime you install other updates
 

Top